Database Develop

New to the scene, a couple questions if you don't mind.

Well I did google, I always here people talking about JfV and whatnot, but I can't seem to find a definitive resource letting me know exactly what it is and what it does? I know where to find it and see the instructions on how to install it, but noone seems to ever say what it has/does.
Another question I have is about auto starting apps. On Android, is it possible for me to set an app to auto start when i boot my device? this would be useful for some of the apps i use like Hello IM, twidroid, email, etc. I don't post much here but I'm hoping you guys can help me out and get me settled with Android and the G1. Thanks
- Q

The JesusFreke builds are edits of the official builds with root access along with a couple of useful applications like a terminal. Root lets you take advantage of some things like tethering and gives you control to edit and break your phone at your hearts desire.
Autostart seems to be app specific. My weather app autostarts and stays in the background but others don't. Not sure how to make them do it but maybe someone else know.

+1
welcome. JF's modified roms also add auto rotate for your browser and multi-touch which is nifty.

Lite Glossary...
I've seen a lot of questions like this and I vaguely remember someone trying to give a quick explanation in another thread but I couldn't find it.
So here's my attempt to clear some things up based on terminology.
Android OS - Like Windows Mobile but based on Linux, using a Java based front end.
Linux - Open Source operating system used instead of Windows XP/Vista, Mac OSX etc... it's free (as in beer).
Root (as in access)- root is like the administrator account on a windows machine. It allows you to have complete access to the underlying OS of a linux or *nix based machine.
Root (as in location)- the 'root' of a folder or drive is the top most area of that location. In windows, C:\ is the 'root' of your hard drive. The 'root' of your SD card just means you haven't moved into any subfolders.
JFV1.## - Is a specific Version of a JesusFreke ROM. JesusFreke is a developer on this website that has graciously spent his time to modify the G1 OS to allow us to have root access to our phones. This gives us the ability to explore and modify our phones via a command line. It allows for the use of themes, native backup functionality, manually selecting which apps can utilize root access, auto-rotate screen, multi-touch in browser, moving applications/caches to the sd card and I'm sure some other things I'm forgetting.
That's all I can think of right now. Maybe I'll add more later.

skri11a said:
I've seen a lot of questions like this and I vaguely remember someone trying to give a quick explanation in another thread but I couldn't find it.
So here's my attempt to clear some things up based on terminology.
Android OS - Like Windows Mobile but based on Linux, using a Java based front end.
Linux - Open Source operating system used instead of Windows XP/Vista, Mac OSX etc... it's free (as in beer).
Root (as in access)- root is like the administrator account on a windows machine. It allows you to have complete access to the underlying OS of a linux or *nix based machine.
Root (as in location)- the 'root' of a folder or drive is the top most area of that location. In windows, C:\ is the 'root' of your hard drive. The 'root' of your SD card just means you haven't moved into any subfolders.
JFV1.## - Is a specific Version of a JesusFreke ROM. JesusFreke is a developer on this website that has graciously spent his time to modify the G1 OS to allow us to have root access to our phones. This gives us the ability to explore and modify our phones via a command line. It allows for the use of themes, native backup functionality, manually selecting which apps can utilize root access, auto-rotate screen, multi-touch in browser, moving applications/caches to the sd card and I'm sure some other things I'm forgetting.
That's all I can think of right now. Maybe I'll add more later.
Click to expand...
Click to collapse
Thanks a lot for the nice overview! I'm going to go ahead and do my G1 first thing in the morning (I don't wanna do it at night while I'm a tired mess and end up bricking it ) The auto-rotate is something I wished the G1 had. Does the autorotate in JesusFreke's rom go multiple directions? or is it just the 2 directions like on the default android rom?
And does it work for every app at all times? I know that the functionality exists in the phone as one of my apps implements the auto rotate feature, as well as several games in the android market that utilizes the accelerometer for gameplay. Would be cool to be able to roate my phone at any time using any app (espcially the browser). Thanks for any more help. And I already head RC33. Does that mean I have to downgrade or has an easier method arisen for RC33?

JF's roms V1.41 and up have autorotate in the browser. DroidSans has the app for root users that impliments autorotate for the rest of the phone except your stock picture viewer. both rotate to the same landscape direction like when you open the keyboard.

Don't forget the ability to move apps to your SD card

No, the auto-rotate only goes landscape like 13bjunkie said and he is also right that you need to download DroidSansTweak to actually activate the feature, accept for the browser (once you have root, of course).
It doesn't work on all apps at all times. Apps/games can disable the feature.
You will have to downgrade to RC29 still... Just follow the sticky in the development forum and you can't go wrong. Just follow it to the letter or all bets are off.

Compcache on Nexus One - worthwhile or not...?

I've just posted a new Beta of my MoDaCo Custom ROM here with 128MB Compcache by default.
I'm interested to hear thoughts on whether it's going to be worthwhile!
The RAM use on my N1 is always near 100%, and with the CC enabled, I see it being used...
I'm no Compcache expert, so i'm interested to hear what others think...?
P

The best thing about the Nexus One is how fast it goes, and the RAM that allows to have lots of programs at the same time. For example, my browser almost never need to rechargue the page after using gmail or some other app and then returning to the browser, while my G1 does it almost always.
Sometimes I use advanced task manager to kill all apps and it does kill 15-19 apps! On the G1 it never killed more than 4-8.
So, I don't think this is really needed on the Nexus, if it improves things even more, cool, but I would dedicate your developer efforts to other things.
Sorry for my non-native english.

Off topic, but your "non-native english" is a lot better that that of many native speakers!
Back on topic, I' sure it would get used, since Android will keep filling RAM until it needs to clear some down (correct me if I'm wrong here), but as for whether it's needed? I'm not so sure. The Nexus seems to cope with keeping pretty much all the apps / data I am generally using in memory no problem (as juan says above 15+ apps no problem).

I dont think any form of A2SD, CC, or Swap is needed on the N1. It has more than enough RAM, and keep in mind that not all of it is unlocked yet! 100-200MB more RAM will be unlocked when Google fixes the kernel and sends out an update (or maybe cyanogen will implement it into his ROM?)

Compcache will probably help a little. The configuration is going to be key. DO NOT USE backing swap with it. If I wasn't getting my N1 replaced, for the second time, for dust under the screen I would do some benchmarking for you and give you actual numbers. Maybe when I get my new one and unlock it I will spend some time on it.

with the 1G CPU CompCache should not slow down the UI. For heavy use it should help...
I think that Linux Swap would be nice too since it could unload some of the memory that is not used on to it. If we set swappiness at 0-30 it would hardy use it but instead of dumping the processed data it would just cache it on the swap partition.
I guess the only way to say what works would be to do some testing and see.

i DEF need A2SD i dont like that everyone is saying its not needed...i am at the end of my app storage space and get a notice im running low on space, and when it gets to that point i cant recieve any more text messages

modaco said:
I've just posted a new Beta of my MoDaCo Custom ROM here with 128MB Compcache by default.
I'm interested to hear thoughts on whether it's going to be worthwhile!
The RAM use on my N1 is always near 100%, and with the CC enabled, I see it being used...
I'm no Compcache expert, so i'm interested to hear what others think...?
P
Click to expand...
Click to collapse
hey man ... I've already experimented a little myself with cc.
In my experience for the "android experience" on nexus1 (and considering how android will always try to grab what you throw at it) ... there could be some minimal improvements when utilizing it.
What I've seen thus far ...
In order to leverage cc without a significant performance impact ... changing the way the CPU performs CPU frequency samping/scaling is something that should be addressed in concert. Unfortunately we then begin to encroach on the battery draining issues.
With some minimal tweaking, cc can add a *huge* amount of available RAM.
But in the end .. I think for the typical user the benefit will be minimal.
However, for me personally ... (just for fun) ... I ran a test debian linux distro loaded up with Xorg+WindowMaker (my lightweight favorite combo) ... and the increased RAM made a significant difference. I *almost* had a fullly functional linux desktop in my hand!! Was quite neat compared to the old days of trying the same on g1.
Anyhow, just my 2 cents for now on the matter ... I'm still toying with these implementations myself. If I have anything more to add later that has significance I will.
~enom~

Please enomther, can u share with us your debian distro ready to run under the N1?
because i want to try port Archlinux like debian under the n1.
Im using it on my desktop, and is realy more light and faster than debain

Driskol said:
Please enomther, can u share with us your debian distro ready to run under the N1?
because i want to try port Archlinux like debian under the n1.
Im using it on my desktop, and is realy more light and faster than debain
Click to expand...
Click to collapse
It's a chroot'd environment/setup ... running of ext3 on the sdcard ... (still too big for the NAND) ...
Then I run Xorg through a localvnc script setup ... I then use a android VNC app from the Market to vnc into it and control it.
Still interested?
~enom~

enomther said:
It's a chroot'd environment/setup ... running of ext3 on the sdcard ... (still too big for the NAND) ...
Then I run Xorg through a localvnc script setup ... I then use a android VNC app from the Market to vnc into it and control it.
Still interested?
~enom~
Click to expand...
Click to collapse
Yes of course, i have a thread ready on arch forums but i want to try first debian and see how much stable and functional can be on the n1.
If u can use it like a desktop really, then arch, must be almost 3 times faster deleting packages, daemons, etc...
Im a newbe on linux of course, but i can try it with help
Here is the project: http://www.archmobile.org/trac/wiki/AM/Installation/Guide
Im using arch for 1 year and im really happy with it, beats ubuntu hard! hehe

Driskol said:
Yes of course, i have a thread ready on arch forums but i want to try first debian and see how much stable and functional can be on the n1.
If u can use it like a desktop really, then arch, must be almost 3 times faster deleting packages, daemons, etc...
Im a newbe on linux of course, but i can try it with help
Here is the project: http://www.archmobile.org/trac/wiki/AM/Installation/Guide
Im using arch for 1 year and im really happy with it, beats ubuntu hard! hehe
Click to expand...
Click to collapse
Disclaimer: It's *almost* as functional as a desktop
Limited by the android vnc client of course. When running with Xorg the resources are juiced (thus the need for compcahe, and why I posted it ... slight relevance) ... but sure ... I need to set one up from scratch for arm (as mine are riddled with custom data/packages) ... and I put something up for you. I'll PM you about it ... give me a couple/few days (got a big weekend comin up).
Neat project btw .. I'm definitely going to pull it down, check it out and play!
@modaco ... sry for the 4-post thread hijack
~enom~

Of course dude, when u want and when u can
By now, i just have a 500mb ext3 partition on my sdcard, with the base system of archmobile ready
As i said, im newbe, and now i need to know how can i boot it hehe

never tried it on android, but the usual way is to mount-bind /proc, /sys, /dev from the running android into the new root and then just chroot into the new system.
like
mount -o bind /dev /sdcard/arch/dev
... /proc
... /dev
chroot /sdcard/arch
then you can start services like vnc.
i doubt that arch will be so much faster though.
don't get this wrong, i used arch for over a year and really like its concept. but in the end when you compare fully customized installations of arch and for example ubuntu, the speed difference is rather minimal.
(with focus on customized, meaning on arch you install what you want and on ubuntu you remove what you do not want )

Thansk xkonnim i'll try to give it a shot
enomther, how you boot the debian?
I men if you are using it natively trought fastboot or a img from the sdcard partition ?

xkonni said:
never tried it on android, but the usual way is to mount-bind /proc, /sys, /dev from the running android into the new root and then just chroot into the new system.
like
mount -o bind /dev /sdcard/arch/dev
... /proc
... /dev
chroot /sdcard/arch
then you can start services like vnc.
i doubt that arch will be so much faster though.
don't get this wrong, i used arch for over a year and really like its concept. but in the end when you compare fully customized installations of arch and for example ubuntu, the speed difference is rather minimal.
(with focus on customized, meaning on arch you install what you want and on ubuntu you remove what you do not want )
Click to expand...
Click to collapse
Hi dude again
Finally i got chroot on my arch partition
I have it under /system/sd
and i have the minimal bash working
Now, its time to get it more deepper hehe
EDIT: Now i can start the sshd daemon and try to login into with ssh BUT i can't change the sudo pass with passwd cuz says Not enough permisions. Also, i cant find the damn it sudo binary...
I have the USBNetwork working by default on eth0, but that's all i can do cuz i can't start too the bash.
Any hint?
Bye!

Driskol said:
EDIT: Now i can start the sshd daemon and try to login into with ssh BUT i can't change the sudo pass with passwd cuz says Not enough permisions. Also, i cant find the damn it sudo binary...
Click to expand...
Click to collapse
well those steps are similar to a regular arch install, what exactly is your problem? no sudo in package sources? can't run visudo? you have a root account, just use it instead of a user account for now
edit: can you start an own topic for linux on nexus? we really should leave paul's thread alone

Yes i think it too hehe Sorry enom

Too much to Process..Help Wanted..

Process
From Wikipedia, the free encyclopedia
Process or processing typically describes the act of taking something through an established and usually routine set of procedures to convert it from one form to another, as a manufacturing or administrative procedure, such as processing milk into cheese, or processing paperwork to grant a mortgage loan, or converting computer data from one form to another.
Ok first off I'm the biggest noob at all things root as could be. I have managed to make some custom clocks for my old LG voyager way back in the day and have even jailbroke some Ipod touch's so I was able to load bootleg games and apps.
But this root thing has got my brain traped in a vortex and I really want to not just know how to root my droid (That info is everywhere) but I want to know how it all works. What terms like kernel mean and how they relate to clock speed. What is the difference between all the custom rom's? What happens when I root my phone and can't figure out what rom I should use? Do I have to reset all my apps and preferences every time i want to try a new rom?
I understand the how-to's I'm sure when I try to root my phone that I will not have much trouble doing so. But there are so many things I want to learn and know before I do anything.
I would like to say I'm not looking for links to tech reports on rom's that I will not understand I'm looking for alink (or someone who knows the things I wish to learn,) something that will explain the terms what they mean, how they relate to my phone and what outcome I should expect from loading custom rom's.
I understand that most users of this forum fall into one of two category's ONE ether super wonder techs that know exactly what they are doing and know how things work, TWO people who can read follow directions and root there phones while trying NOT to sound like noob's when they ask for help.
And then there's me I'm a number two, now I know that kinda makes me sound like **** but I really want to be a number ONE
So who want's to teach me ? Who's got some time to kill or link's to post? I'm even willing to go buy a android programmers book if there's one that would be recommended reading to help me understand the OS better.
I want to learn from the masters and this is where they all live. So will someone apprentice me ?
To close my rant out I would like to say I'm a 37 year old man with a masters in chemistry 119 IQ and ex-stream case of OCD that drive's my compulsive need to learn how things work, So I make for a good student
Thanx
ö

Thank you so much, I was hoping to be able to reply first, (this sh*t is my crack)
Ok, First off, the kernel is the basic system that controls how the cpu reacts, as well as how programs interact with the hardware on your phone, such as the screen, wifi and bluetooth modules, accelerometer, gps, ambient light and the battery. When a dev wants to overclock their android, add a module for EXT, or TUN, or add wifi support, this is where the magic happens. this is probably the most important part of the firmware. It also controls battery life via voltage, as well as cpu speed.( the average droid can be overclocked to 1200-ish, depending on the randomness of processors, though I've heard of a ridiculous version called OMAP Ti39 or something that could be stable at 2ghz, even 2.3. As I think you may know, Fat32 doesn't support file transfers of more than about 4 gigs at a time, which is why add in ext support is so important, especially since someone made a video player that reads matroska video files (blu-ray) Ive tried it, its beautiful, (V player - on the market) after kernels is framework, the framework is what renders the gui, basically everything that you see on the screen is thanks to the framework-res. We edit it either manually, or through the use of an app called metamorph, which swaps the xml files the framework uses with edited ones, such as one I recently used to give my droid a circular battery, however these xml files can change anything you could need them to visually about your droid, you just have to find what you need. Now on to shell. shell is the engine that is accesible through command prompt and terminal using the android sdk and adb, more on that can be found easily on the google android homepage. however, much use is made through devs and an app called terminal emulator that is basically a straight to shell terminal screen app. Uses for shell may include but are basically limitless, include moving any app to your sd-card to conserve rom (rom is the phones total system memory, apps usually go in there, but before froyo, and ext partition could be used, and with froyo stock support for most apps was allotted, and without the need of an ext partition.) Ram is basically ram, if you use a rom that originally came with a larger ram supported device, something called a swap partition must be implemented, otherwise it won't boot, there is an app or two that will do that for you, manual swap creation is also possible. Swap basically creates virtual ram on the sd-card. Root access, which can be acheived manually through the recovery flashing of specific zip files, or via free apps that do it with one click, basically allows you to flash kernels, change the framework, or allow tethering which I will cover next, is possible because the kernel the phone uses is linux, the unlocking of which is called granting super user access, in ubuntu a linux distribution, typing su, and your admin password will give you access to your computers system files, much in the same way we apply it to android. (However, it is unlikely you would try to flash an alternate kernel to your desktop, as it runs on either ie36 or x64 architecture, whereas phones run altogether seperate architectures , for instance android runs on ARM, and that is the base and primary reason your phone won't run windows.) Since android is free (open-source) there is an x86 version of android, including a froyo port that you can use on laptops and desktops. (Really quickly I would like to interject that recovery is an option on all phones android based that is usually accessible by holding volume up while booting, however the droid requires you press x while booting to get to recovery, which btw is what you flash a custom version of after rooting that allows you to flash roms and kernels. It also allows for backing up all of your phones firmware and data in the event of a problem. Basically its your new best friend, get familiar.) Also there is another form of booting called bootloader, it allows you to flash specific system files that are normally untouched, a guide to using that and a program called rsd lite will help you if you've bricked your phone ( Bricked- term used to describe the state of a phone that is unable to be recovered to an earlier condition and is essentially a brick or "expensive paperweight".) by allowing you to flash a completely untouched sbf (firmware) file. note that you can also use it to change your boring m boot logo with any image that fits 480x182 bytes through a slightly difficult, but fun proccess, a guide to which ,can be found here at xda, including a file that allows for the flashing of just the logo, whereas previously you had to reactivate your phone (you just have to follow the instructions on the phone) reroot, and restore the rom you previously backed up. Now on to tethering, the most important feature available to root users, which, if carriers have anything to do with it, would normally cost an extra 10 dollars a month. (Tethering- using shell or an app with the proper kernel to allow the use of your phones mobile network via usb connection, or the creation of a wifi hotspot with your desktop or laptop.) However thanks to devs who believe that what you pay for should be used how you want, most roms will tether, even in the settings, without carriers any the wiser. Windows 7 and almost all linux will automatically tether, vista is the most difficult, and xp has a quick install init file that works like a charm. The only reason we root is because we believe in the freedom to change our phones to fit us personally, and lets face it, because we can, because its fun, because its not illegal, and it brings a sense of satisfaction and pride in pushing the limits of technology. (P.S. I tried not to take to long so I couldn't really look it over, so sorry for grammatical or vocabulary based errors.)
(P.P.S. I recommend any book to do with android programming, but you'll need programming experience in linux, especially eclipse.)
Oh, and I'm a 17 year old junior with a vocabulary skill level of 139, just in case you wondered.

There are plenty of applications on the market where you can backup apps and data once you root, I personally use titanium, but I never restore system data if I'm flashing roms, only apps n data that comes with apps. Youre gonna have to search around other forums and whatnot to find the right roms.
Sent from my ADR6300 using XDA App

Starting with Development...

I hope this is the right place to post this, if not my apologies. I've had my Droid X for two weeks now, and have done a few customizations to it (NexTheme, root, BusyBox) and to be honest I'm bored already even though I'm still getting used to this phone...and even though it's my first Android powered device, and second smartphone.
Anyways, I want to dig into the guts of this and possibly contribute. I have been working with some form of Unix since the early 90's, and I'd like to think I'm quite experienced with it.
This is where I need assistance. Even though I'm quite adept with my Google-Fu, I'm still not able to point myself in the correct direction. I have a terminal app on the phone, and adb on my pc, however...to be frank...they both suck. Perhaps it's the limits of a mobile Linux platform and not having proper term types defined, but I can't get a decent working environment setup to navigate the filesystem in a comfortable and easy to read way. It's making it extremely difficult to see where I am, where I've been, and the files/directories and their permissions, etc etc. Have tried setting and resetting various TERM env types, but nothing seems to change the layout/display.
I had found an SSHd how to hoping I could install SSHd on the phone and just SSH in from a proper terminal, but it's from 2008 and deals with the G1. I wasn't able to get the steps to work for me.
Short of what I've already tried, what other options are there...if any? I don't know what, if anything, I could contribute to the community...but I'd like to give it a real go, and I *really* do love to mess with things heh heh....

The easiest way i have seen to navigate through your file system is using root explorer on the market.

Since you have adb set up, you should be able to execute "adb shell". Also, there seems to be an emulator included in the sdk, though I haven't used it myself.
Sent from my DROIDX using XDA App

mattyboy1013: I'm looking for a non-gui shell based method of navigation. A terminal is a lot easier and quicker for me.
pchop: Yea, I've used adb shell when manually rooting, and I wasn't too keen on how it laid things out. Particularly in a single column making navigation difficult. I'll take a look at the emulator though, and see what it does. Thanks.

I may be wrong but isn't android a java platform sitting on top of unix?

That's my understanding as well, and I'd like to navigate it as if it were a Linux box, ie: through a console. Problem is, the two terminal apps I have access to (as mentioned above - terminal emulator and adb shell) present the file system in a single column and with no sorting. It makes navigating and seeing whats available quite difficult.
What I'm looking for, if it even exists, is a terminal app that will display in rows and columns, and sorting alphabetically with directories first then files. Basically how most Linux distributions do by default and have for years.
I tried some more with my attempts at getting SSHd on the phone by compiling dropbear myself via the android source, but no go. The compile bails on me even after several fixes and attempts. Was hoping SSH in via a gnome-terminal, xterm, eterm, etc on one of my Linux boxes would set a proper TERM environment that the phone would respect, but I may be barking up the wrong tree there as well.
Dunno, I'm just in search of something to play with, and heck...doing all of the above has kept me pretty busy anyways lol.

Dualboot Questions

Hi,
I am awaiting delivery of a 32Gb Touchpad within the next couple of days and will probably want to root it fairly soon after getting it. I have rooted 2 android phones before, so rooting doesn't hold too many fears for me lol. However, I obviously haven't come across dualbooting a device after it has been rooted, so I have a couple of questions, which I have done a search for, but couldn't get any definative answers for.
First of all, am I right in thinking that on booting the device, I will end up with a slight pause during which I can choose to boot into the other operating system. Something like the way windows will pause to give you a chance to boot from the CD drive before continuing to load windows.
Also, I have noticed that Android seems to need some of the WebOS files to be able to run. If this is the case, does sharing these files slow down WebOS in any way and also will I be able to optimize the WebOS system without causing problems with the Android OS.
Any help and advice will be very welcome.
Many thanks
Ian

gizmo001i said:
Hi,
I am awaiting delivery of a 32Gb Touchpad within the next couple of days and will probably want to root it fairly soon after getting it. I have rooted 2 android phones before, so rooting doesn't hold too many fears for me lol. However, I obviously haven't come across dualbooting a device after it has been rooted, so I have a couple of questions, which I have done a search for, but couldn't get any definative answers for.
First of all, am I right in thinking that on booting the device, I will end up with a slight pause during which I can choose to boot into the other operating system. Something like the way windows will pause to give you a chance to boot from the CD drive before continuing to load windows.
Also, I have noticed that Android seems to need some of the WebOS files to be able to run. If this is the case, does sharing these files slow down WebOS in any way and also will I be able to optimize the WebOS system without causing problems with the Android OS.
Any help and advice will be very welcome.
Many thanks
Ian
Click to expand...
Click to collapse
Yes, there is a boot menu that allows you to choose webOS or Android. And, no, Android won't interfere with the operation of webOS or vice/versa.

gizmo001i said:
Hi,
I am awaiting delivery of a 32Gb Touchpad within the next couple of days and will probably want to root it fairly soon after getting it. I have rooted 2 android phones before, so rooting doesn't hold too many fears for me lol. However, I obviously haven't come across dualbooting a device after it has been rooted, so I have a couple of questions, which I have done a search for, but couldn't get any definative answers for.
First of all, am I right in thinking that on booting the device, I will end up with a slight pause during which I can choose to boot into the other operating system. Something like the way windows will pause to give you a chance to boot from the CD drive before continuing to load windows.
Also, I have noticed that Android seems to need some of the WebOS files to be able to run. If this is the case, does sharing these files slow down WebOS in any way and also will I be able to optimize the WebOS system without causing problems with the Android OS.
Any help and advice will be very welcome.
Many thanks
Ian
Click to expand...
Click to collapse
First off its a tablet not a phone so its not really called rooting. In order to have the dual boot option you need Moboot. Do some research on google and you tube. Key words your looking for, How to install abdroid on hp touchpad. You will find what you need fairly quick. If all fails private message me with your email and I will supply you with the instructions personally via email
Core droid htc glacier

Another option for directions
Google YouTube for Reverend TV (or Rev TV)
He provides exellent video step by step instructions for almost all touchpad android setups

If you're a mod junkie much like myself, read up on how to enable the testing feeds in preware and do it prior to installing preware via novaterm. It may look tough, but its really easy if you follow instructions exactly. I personally always do all the web os tweaks prior to installing android, as I feel it makes for a better web os experience, as well as a better tuned fall back os if you wish to use android as a primary os. There's also an app in WebOS that allows for tweaking the boot menu called cyboot, so you can change delay time for selection, as well as pick which os will be your default boot option.

Thanks for all your replies and advice. I think I already have most of if not all the info I need to be able to dual boot my touchpad. But you have answered my last few questions, thank you.
Ian

rpomponio said:
First off its a tablet not a phone so its not really called rooting. In order to have the dual boot option you need Moboot. Do some research on google and you tube. Key words your looking for, How to install abdroid on hp touchpad. You will find what you need fairly quick. If all fails private message me with your email and I will supply you with the instructions personally via email
Core droid htc glacier
Click to expand...
Click to collapse
rpom: Rooting means getting access to the root of the Android OS...it doesnt matter if its a phone or tablet...even on tablet its called rooting

viny2cool said:
rpom: Rooting means getting access to the root of the Android OS...it doesnt matter if its a phone or tablet...even on tablet its called rooting
Click to expand...
Click to collapse
Take a hike
Core droid htc glacier

Well guys, my self I'm not boithered whethere it is called rooting on the device or not lol. I now have a dualboot touchpad and I must say, it was a hell of alot easier than rooting an android phone. Thank you all for your advice.
Ian

gizmo001i said:
Well guys, my self I'm not boithered whethere it is called rooting on the device or not lol. I now have a dualboot touchpad and I must say, it was a hell of alot easier than rooting an android phone. Thank you all for your advice.
Ian
Click to expand...
Click to collapse
it sure is!!! I recommend classic nerd in the dev section. Out was public release today and its awesome, its android 4.0
Core droid htc glacier