Quote:
Originally Posted by Reefmagnet
<snip>
I have made some cliff notes on the installation specific for my device and also have guides I put together previously for both rooting the P1000 and for returning it to standard should it all go belly up. I'll emphasize that these are for my particular device which is a Galaxy Tab P1000 but if anyone's interested you can pm me and I'll make them available on a download link somewhere on the condition you try at your own risk.
|
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.
As much as I'd like to include this kind of information in my instructions:
Building on Motorola Xoom | Official OpenCPN Homepage , it's difficult enough to include information necessary to complete a problem free installation without distracting users with asides specific to different android models. Most people tend to scan instructions in an attempt to develop a sense of complexity, time necessary to perform the steps involved and decide whether or not they want to proceed. So, I've tried to keep things as compact as possible. Not easy.
On the other hand, it would definitely be a plus If I received more feedback. Good and bad. Without feedback I can't know if an error in syntax, or wording in my instructions is a source of frustration for anyone following the instructions.
Can a section pertaining to model specific issues be created at opencpn.org? Don't know, but I'll
poll the powers that be to find out.
The other alternative is to visit XDA Developers
Android Forum for Mobile Phones, Tablets, Watches & Android App Development - XDA Forums to investigate known issues related to your android model. For example, a custom ROM for the Galaxy P1000 is here:
[ROM][CM11][P1000] Official CM11 Galaxy Tab … | Samsung Galaxy Tab | XDA Forums
There is a good reason there's device specific development going on in the android community of developers. In some cases manufacturers introduce methods designed to reveal if "as built" specifications, software and
hardware have ever been altered. Even if a factory reset is performed intermediate changes to an "as built" configuration can be retained for the purpose, I presume, of determining whether a warranty remains in force. There are methods to defeat these schemes and can be found at XDA and other development sites on the web. Boot processes, partioning schemes, permissions and more can vary between models. The latter is more likely to complicate a successful completion of my instructions than anything else, and should be the primary suspect if problems arise. Best practice is to immediately ask me for help. Don't frustrate yourself by trying to solve the problem alone.
Searching the
internet using suitable key words will frequently lead you to one of my threads. Odds are you'll find the solution to a problem someone else encountered, there...
Finally, anyone concerned with how to recover from an unlikely android device failure must create a "nandroid backup" now, not later. In most cases the name of the backup folder will depend upon your "recovery", typically either CWM (Clockwork Mod) or TWRP for custom ROMS. They are full featured and hugely superior to OEM recoveries. Copy the entire folder to a different device/computer for safekeeping.
If you're going to root your android, seriously consider switching to a custom ROM. For android they are basically OEM ROMS very skilled developers customize for use on your particular model, adding very cool features OEM ROMS don't have. The other advantages include the ability to request a driver you need be included in the next update; ability to download a ROM update and perform the update manually. Doing this enables avoiding the risks associated with OTA updates. If you want, you can still update OTA, but I don't recommend it.
Concerning the installation of Linux with Linux Deploy and OpenCPN either from source or by using one of my binaries. The best safeguard against hardware or software failures is to install Linux and OpenCPN with Linux Deploy default settings which will install Linux as a "file" on the sdcard. Then, using a computer prepare an external micro sdcard by formatting the primary partition as FAT and a second partition in a linux "ext" format; ext2, ext3 or ext4. Then use Linux Deploy to install your preferred Linux distribution in a "partition" on the ext_sdcard, which will probably be /mnt/fuse/sdcard1_real. Install OpenCPN on the ext_card using whatever approach you prefer, from source or with a binary. You can use the external micro sdcard on any android device with the installed android apps you downloaded in the course of following my instructions.