Originally Posted by Wrong
Thanks for keeping notes related to rooting and recovery for Galaxy Tab P1000 owners. If you can remember, let me know what kinds of problems you encountered following my instructions.
Ok Wrong, here is my critique (and my apologies for sounding like a New York
Post film critic):
Rather than refer users to Wikipedia to determine their ARM processor type, it's probably easier to first guide them the their tablet or phone's Settings>About Phone>CPU info which should provide this.
In general, I think you are offering too many app options e.g. 2 GPS
apps, 2 VNC apps, multiple deployers and Linux
distro's etc. Decide on one that does the job and stay with it. You can advise more technical users of alternatives (perhaps in a "Notes for Advanced Users" section, or whatever).
information you mention is early into your installation
guide. This is probably best covered last as it seems a few people don't bother with GPS. Talk of GPS capability in relation to the generation of NMEA
sentences at this point is wasted on most users. Best to just go with something that will work in any case, I think.
Another thing that would be best to avoid if possible is referring to other sites to complete parts
of the process. The problem I see with this is that the linked sites often have too much information which is both confusing and can make the relevant information difficult to find and digest.
It's so easy to download the source from GitHub, compile and install that I'd almost forget about trying to build installation
packages. If anything, perhaps develop a script that will download, compile and install in on operation. I purposely went with no compilation options and didn't change to any specific folders after opening the terminal except for the mkdir build
and cd build
prior to compiling.
Continuing on with the theme of too many options, listing installation instructions for both installation packages and source code compiling on different Linux
flavours is to me the bit that makes the whole installation look just too difficult. The section is also before the section on Linux Deploy which, too me, places it out of step. I'd suggest sticking with Linux Deploy's default options (maybe explaining alternatives in the before mentioned Advanced section at the end of the guide) and limit to specific guide instructions only
for that configuration (in the present case that would be Debian/Wheezy)
Linux Deploy is easy to install and configure. I think the instructions needed for an OpenCPN
install should just be included in the guide. Don't bother mentioning anything else (except again for the "Advanced" section). The average user won't care as long as the selected choice works.
Again stick with the better of the two VNC viewers and just list alternatives in the Advanced section if required.
Too much technical mumbo-jumbo. I don't care what a "loop" file system is. I just want to be reassured that it won't brick my device.
When I installed Linux Deploy, I changed no options. I have no idea where the 4GB partition size would have been set as I couldn't find this option. I still don't know what size partition was created, but I would conclude whatever the default is is ok and any reference to changing this should be included if required in the Advanced section.
This entire piece of text:
Once the installation is complete mount the loop filesystem following the steps below.
Open the android terminal.
Type 'su' at the prompt
Copy/paste or type:
and press <enter>
Create a root password:
Type at the terminal prompt
Supply a password you will not forget! Re-enter the password as requested. You will need this password when logging into a terminal from within the linux vnc desktop.
Your Linux file system is now 'mounted' and fully accessible.
Made absolutely no sense. I used the "Android Terminal" installed by CyanogenMod ROM and no matter what I tried, even finding that "linuxdeploy" was within a different folder didn't work. I very nearly gave up at this point, but because I am familiar with Linux (I use Ubuntu on my work PC) I changed the "su" password in a Linux Terminal using sudo passwd root
. However, because I've never been asked to enter the password again during any sudo command, I'm not even sure this is used on the particular Debian distro at all??? Even now I don't know if guide was trying to instruct me to change the Android OS su password or the Linux distro's su password.
The other point from this step is that I didn't need to use FX file manager at all and didn't need to move, copy or change permissions of any files.
Again, if OpenGL doesn't work - don't mention it in the guide. Include in the Advanced section if required.
Way too many options. focus on one that works and just show the instructions for that. In my experience, the whole of section 4 could be summarised as:
Run this command in LXTerminal to install prerequisites...
sudo apt-get install libgtk2.0-dev gettext git-core cmake gpsd gpsd-clients libgps-dev build-essential wx-common libwxgtk2.8-dev libglu1-mesa-dev libgtk2.0-dev wx2.8-headers libbz2-dev libtinyxml-dev libportaudio2 portaudio19-dev
I ignored this step entirely and instead and used the instructions from the main site for installing OpenCPN
from source using the GitHub repository, summarised as:
Run these commands in LXTerminal to compile and install OpenCPN
git clone git://github.com/OpenCPN/OpenCPN.git
sudo make install
It's actually the commands shown above in 4 & 5 that I think could be put into a script to really simplify the installation if working with a specific installation.
Using bVNC Free setting "servername" and "password" values was all that was required.
No problem here
Although setting up charts
inside OpenCPN is part of the main OpenCPN documentation
, I think a section here needs to include installing charts
in a nice simple way to the device. IMO the easiest method is to copy to the external SD and then make reference how to find this SD card using the File Manager located in the Linux distro. Trying to explain how to copy and move is confusing for new chums and old hands will already know how to do this if that's what they want to do.
And my BIGGEST gripe. There is no information shown on how to actually hook up the GPS to OpenCPN. If you understand the tech involved this is probably really easy. If you're dopey like me it is really hard. Once I'd figured out that "Turbo GPS 3" no longer includes an NMEA
server and doesn't work and that "GPS Share Wifi" doesn't really explain what it does but has an NMEA server feature and had fiddle I got it to work and it only requires a few steps that is easy to follow, even for us dummies. Unfortunately the guide does not include these steps.
And finally, perhaps versioning these guides to allow for changes over time as the associated apps evolve along with an included list of devices and android versions the guide has been successfully applied to would also help give the less tech savvy among us the confidence to give it a go on a spare or superseded tablet, at least.