Database Users

Android build?

I'm looking to try out an android build. Can someone recommend a build to use that's easy to set up. I need data, and gps to work. Also would I be able to flash back to WM if I don't like the build?

Not sure of an Android build to meet your needs, though I would like it too!
To flash back to WM is easy once I did a lot of reading. Just power your phone off, then turn power on with the camera button depressed too. This brings up the bootloader screen, then just flash your favourite WM ROM.

ski21 said:
I'm looking to try out an android build. Can someone recommend a build to use that's easy to set up. I need data, and gps to work. Also would I be able to flash back to WM if I don't like the build?
Click to expand...
Click to collapse
Hi ski21,
I was in your shoes just a few weeks ago. I now have a great Android build running on my Touch (Bell Mobility). Everything works and it “feels” like a native build like it was meant for this device.
With any of the Android builds you can always flash back to Windows Mobile. You just need to make sure you have an up-to-date (ie. GPS enabled) Windows Mobile ROM to return to. I am with Bell and use the most recent official Bell update so I can go back to a “supported” configuration.
If you have never flashed a custom Windows ROM before then you will need to install the “HardSPL” provided by ImCoKeMaN. This is an alternate boot loader that allows you to flash unsigned (non-official) ROMs. This is really the key to doing anything cool with your Vogue. Without this you can only every install an official ROM released by your carrier. I recommend version 2.31. If you have installed a custom Windows ROM before then you have already done this. You can find the information on this over at PPCGeeks in the link below:
http://forum.ppcgeeks.com/showthread.php?t=20370
Once you have the CoKe SPL 2.31 installed you will be able to flash any custom ROMs including Android builds. Flashing Android is a little different then flashing Windows ROMs. You will need a bunch of files:
First things first, you will need a copy of the ROMUpdateUtility. This is a Windows program that you use for flashing your Vogue. You can get this here:
http://cid-e5302e6abd554cb9.skydrive.live.com/self.aspx/XDA/ROMUpdateUtility.rar
Download and unpack this into a folder called ROMUpdateUtility.
Next you will need a Linux kernel with a screen size (resolution) appropriate for your device. This is the one I am using and it works great in conjunction with the ROM I am going to suggest next.
http://it029000.massey.ac.nz/vogue/files/voguimg-240x320-17-12-09.nbh
Download this file, copy it to the folder you unpacked the ROMUpdateUtility in. Rename it to RUU_signed.nbh.
Next you will need to download some “base files” as well as a system image (which is the main ROM). You copy these files to the SD card on the Vogue. You can get the “base files” here:
http://cid-e5302e6abd554cb9.skydrive.live.com/self.aspx/XDA/Androidstuff.rar
You will then need to select your favorite Android build. I am using plemen's “Eclair themed” build. You can get this here:
http://forum.xda-developers.com/showthread.php?t=591104
Rename the system file you download to system.sqsh when you copy it to your SD card. Also download the data.img file and place it on your SD card (should be provided in the thread that you get the build itself from). In the “end” (just before you flash) you should have the following files sitting in the root of your SD card:
datafstonand
rootfstonand
systemfstonand
rootfs.img
data.img
system.sqsh (or system.img depending on the build you download)
Then you put your Vogue into boot loader mode. You do this by holding down the power & camera buttons and pressing the reset button with the stylus. Then run the ROMUpdateUtility.exe from your ROMUpdateUtility folder.
That just about covers it I think. I am a little unclear what all these different parts do but this should get Android 1.6 (if you download plemen's build) up and running on your Vogue. Enjoy.
Best regards,
The Fish

Excellent directions, thank you. I followed them but it comes up as T-Mobile when it loaded Android. I think I messed up the rootfs.img, this i got from the http://sourceforge.net/projects/androidhtc/files/ plemen's “Eclair themed” build page. Any idea where I went wrong, for I am also a Bell user.

krwilson said:
Excellent directions, thank you. I followed them but it comes up as T-Mobile when it loaded Android. I think I messed up the rootfs.img, this i got from the http://sourceforge.net/projects/androidhtc/files/ plemen's “Eclair themed” build page. Any idea where I went wrong, for I am also a Bell user.
Click to expand...
Click to collapse
that's normal

Well if it's normal then there's a problem. It will not let me connect, shows 2 bars, but says I have no network so I cannot connect to Google. If thefish123 is connected on Bell then I must have something wrong. I followed the directions exactly, but was somewhat unsure over the rootfs.img file for it is not too specific in the directions??? Anyway, flashed back again to NSFans. I have had another Android working but could not get tethering working correctly, I was hoping this one might do it. Using PDnet it just wouldn't work for me.
Also, sorry ski21, wasn't my intention to hijack your thread.

krwilson said:
Excellent directions, thank you. I followed them but it comes up as T-Mobile when it loaded Android. I think I messed up the rootfs.img, this i got from the http://sourceforge.net/projects/androidhtc/files/ plemen's “Eclair themed” build page. Any idea where I went wrong, for I am also a Bell user.
Click to expand...
Click to collapse
Hi krwilson,
It is indeed normal for plemen's build to show T-Mobile. It was most likely extracted from a T-Mobile device at some point. However when you drag the notification area down from the top of the screen it should show Bell Mobility. Just slide your finger from the top of the screen down as if dragging the top bar down.
I also did not have data immediately after flashing plemen's build. I did a soft reset and then it worked perfectly. Regarding the rootfs.img... I downloaded the rootfs.img mentioned a little further into the same thread that mentions an update to get GPS working under Android.
If it shows that you have reception the first thing to try is calling *BELL and see if you get the “your test call was successful” message. If so then you are on the network.
The next thing is a data issue. I would suggest poking your stylus in the reset hole and rebooting. That solved it for me.
Also, I had issues with missing calls on some Android builds (most notably the cupcake 1.5 build). My phone would not ring till 3 or 4 rings on the other end and then very quickly go to voice mail. These issues have disappeared using plemen's “ 1.6 build.
I have everything working except perhaps maybe Bluetooth (not sure I don't really use it). The phone works fine as a phone (calls come through), GPS and data all work. I am very pleased with it.
Best regards,
The Fish

Thank you for the followup.................IT WORKS beautifully! I have not tested BlueTooth yet, no big deal to me either, but it tethers and it does work seamlessly, and fast...........as if it was made for our Vogues.

krwilson said:
Thank you for the followup.................IT WORKS beautifully! I have not tested BlueTooth yet, no big deal to me either, but it tethers and it does work seamlessly, and fast...........as if it was made for our Vogues.
Click to expand...
Click to collapse
What application are you using to tether your Vogue?

PdaNet 2.16

Need some serious hel.

Hi everyone, I'm new to installing Android to the Vogue and I haven't the slightest idea where to start. I've tried multiple times but always seem to mess up with everything. Can anyone give me a step by step tutorial or even make the folders for me so that i can put it in my SD card, let me know and thank you guys for your help. Also if possible and anyone would want to help and make the folders for me I would like an eclair build.

were you planning on running android on NAND (which is where windows mobile is now) or off your sd card.

I was planning on running it off NAND, any suggestions?

Gere200 said:
I was planning on running it off NAND, any suggestions?
Click to expand...
Click to collapse
Your phone is already unlocked?
Seeing that you have never run Android before you may want to try a few builds on SD card first to see which one you like, and have the flexability to go back to Windows Mobile. A class 6 microSDHC card is pretty comparable to NAND speedwise in my opinion.

would recommend one of the donut builds (plemen, myn). both guys make a fast and stable donut, GPS and bluetooth work great. since I've got a bit of time, here's a step by step with links to take you from a ground zero unlocked vogue to running android on your nand (fastest way, replaces windows mobile). this has been written up a few times before, but today is your lucky day
read the entire set of instructions before getting started.
BEFORE STARTING
1. know that there are multiple ways to flash a rom to your phone. here are a few
a. using windows, get a flashing package from one of the xda devels, and replace the RUU_signed.nbh file in that package with whatever you are trying to flash (try NFSFAN's package, it has always worked well for me for this; some carrier packages don't work), renamed the same way
b. use a 2GB or smaller micro SD card with the .nbh named VOGUIMG.NBH in root, then place the phone in bootloader mode (see #2)
c. use linux and HTCFlasher - don't know much more about this method, find it here
2. if flashing from a computer, I always recommend flashing from the bootloader, NOT through active sync. enter bootloader: hold down power and camera, then press and release reset, wait for the tricolor screen. then connect to usb, and flash away
3. Flashing etiquette: I always flash everything twice, back to back, for good measure. while the phone is flashing, don't move it, don't open programs, don't surf the internet, just leave your phone and computer alone, hands off. and don't flash from a virtual machine; trust me, just don't.
4. Have patience. There are steps that will take minutes to complete. Just wait. If you are not sure is something is happening or if the phone is frozen, put the phone down and go do something else for at least 10 minutes.
GET STARTED
1. unlock your phone (cokeman's unlocker, hardSPL 2.31).
2. flash a "GPS capable shipped rom" from post 1 here. make sure you have working phone, working data, and working GPS (if you are on verizon and have problems getting GPS to work, see here - thx drewden123.
3. upgrade to the bell 3.42.50 radio, find the radio only version here. flash it the same way you flash any other ROM - you can use a rom package to flash it, just rename it to RUU_signed.nbh and replace the one in the package with it, then flash away)
4. download the necessary files. you'll need:
a. a rom in the form of androidinstall.tgz from this forum. a couple of great donut options are myn's and plemen's and plemen's
b. a .nbh found at sourceforge. the sourceforge page contains both stable builds, and the latest betas - don't know what to use? see this thread. choose your resolution based on the recommendations of the chef (the rom builder), also read here.
5. create a folder on the root of your micro sd card called andboot
6. place your androidinstall.tgz file in the andboot folder
7. flash your .nbh file by placing your phone in bootloader mode, and using one of the above flashing methods
8. as soon as the phone reboots (it should vibrate), hold down this button to enter the install menu like your life depended on it until the boot menu pops up
9. in the top half of the boot menu are your booting/file storage settings. for nand, select "sys on nand" and "data on nand" (other options will work too, but for your standard nand install, I would go with this)
10. go down to "1. install system" and click it. at this point it doesn't matter, but on the second screen that pops up go ahead and choose wipe data as well. when swapping between builds in the future, it is recommended to start with a new data file for best results. however, if it is the same class of build (i.e. between two donut builds), keeping your data.img file and simply using the "clear dalvik cache" should keep you running smooth without having to change all of your settings again.
11. wait for the install menu to re-appear. when it does, scroll down to "9. quit" and click it.
12. wait. keep waiting. in fact, step away from your phone. when you come back, turn the screen on, you should see the Donut lock screen!
OTHER NOTES
1. to reflash windows, simply enter bootloader mode, and flash your windows rom
2. buttons in android: see here.

wow thank you so much, this is exactly what I needed, once I get everything going I will let you know, currently I'm running NFSFAN's Final 6.5 ROM, its great and all but I need me some Android. Thanks again for your help and I will keep you posted.

tatnai said:
would recommend one of the donut builds (plemen, myn). both guys make a fast and stable donut, GPS and bluetooth work great. since I've got a bit of time, here's a step by step with links to take you from a ground zero unlocked vogue to running android on your nand (fastest way, replaces windows mobile). this has been written up a few times before, but today is your lucky day
read the entire set of instructions before getting started.
BEFORE STARTING
1. know that there are multiple ways to flash a rom to your phone. here are a few
a. using windows, get a flashing package from one of the xda devels, and replace the RUU_signed.nbh file in that package with whatever you are trying to flash (try NFSFAN's package, it has always worked well for me for this; some carrier packages don't work), renamed the same way
b. use a 2GB or smaller micro SD card with the .nbh named VOGUIMG.NBH in root, then place the phone in bootloader mode (see #2)
c. use linux and HTCFlasher - don't know much more about this method, find it here
2. if flashing from a computer, I always recommend flashing from the bootloader, NOT through active sync. enter bootloader: hold down power and camera, then press and release reset, wait for the tricolor screen. then connect to usb, and flash away
3. Flashing etiquette: I always flash everything twice, back to back, for good measure. while the phone is flashing, don't move it, don't open programs, don't surf the internet, just leave your phone and computer alone, hands off.
4. Have patience. There are steps that will take minutes to complete. Just wait. If you are not sure is something is happening or if the phone is frozen, put the phone down and go do something else for at least 10 minutes.
GET STARTED
1. unlock your phone (cokeman's unlocker, hardSPL 2.31). make sure whatever ROM you end up with on your phone has working phone, working data, and working GPS.
2. upgrade to the bell 3.42.50 radio, find the radio only version here. flash it the same way you flash any other ROM - you can use and rom package to flash it, just rename it to RUU_signed.nbh and replace the one in the package with it, then flash away)
3. download the necessary files. you'll need:
a. a rom in the form of androidinstall.tar from this forum. a couple of great donut options are myn's and plemen's and plemen's
b. a .nbh found at sourceforge. the sourceforge page contains both stable builds, and the latest betas - don't know what to use? see this thread. choose your resolution based on the recommendations of the chef (the rom builder), also read here.
4. create a folder on the root of your micro sd card called andboot
5. place your androidinstall.tar file in the andboot folder
6. flash your .nbh file by placing your phone in bootloader mode, and using one of the above flashing methods
7. as soon as the phone , hold volume up like your life depended on it until the boot menu pops up
8. in the top half of the boot menu are your booting/file storage settings. for nand, select "sys on nand" and "data on nand" (other options will work too, but for your standard nand install, I would go with this)
9. go down to "1. install system" and click it. at this point it doesn't matter, but on the second screen that pops up go ahead and choose wipe data as well. when swapping between builds in the future, it is recommended to start with a new data file for best results. however, if it is the same class of build (i.e. between two donut builds), keeping your data.img file and simply using the "clear dalvik cache" should keep you running smooth without having to change all of your settings again.
10. wait for the install menu to re-appear. when it does, scroll down to "9. quit" and click it.
11. wait. keep waiting. in fact, step away from your phone. when you come back, turn the screen on, you should see the Donut lock screen!
OTHER NOTES
1. to reflash windows, simply enter bootloader mode, and flash your windows rom
2. buttons in android:
-top power: short press = turn on power, wake screen, menu. 1-second long press = toggle keyboard. 2-second long press = toggle portrait/landscape orientation
-volume slider: volume
-camera: short press = back. 1-second long press = home
-green: short press = call log. long press = voice dialer
-red: short press = sleep screen. long press = phone option menu (power off, airplane mode, silent, etc)
-enter, direction keys = standard functions
Click to expand...
Click to collapse
If only we had someone to sticky this. Great post only need to add info about the market and resolution and I bet this forum would be 95% reduced in clutter.

berardi said:
If only we had someone to sticky this. Great post only need to add info about the market and resolution and I bet this forum would be 95% reduced in clutter.
Click to expand...
Click to collapse
see my new signature

When i just try to run haret it says that mkdir: cannot create directory '/system'
:File exists
sh: 2: unknown operand
it also says that it cannot find the system directory in the SD card??

tatnai said:
see my new signature
Click to expand...
Click to collapse
nice

tatnai said:
see my new signature
Click to expand...
Click to collapse
[borat voice] Very nice!
Now you'll just have to post in every thread "please see my signature"

Tatnai, I just want to thank you for your post. I was able to flash myn's build of andriod to nand yesterday after going through maybe five different threads(all with slightly differing methods). After reading your instructions, I am relieved that I did it correctly.
Quick a question just to verify. When I want to reflash to a newer build of andriod in the future, I'd just have to place the correct .nbh file in root, androidinstall.tar file in the andboot folder and hold volume up?

wfp said:
Tatnai, I just want to thank you for your post. I was able to flash myn's build of andriod to nand yesterday after going through maybe five different threads(all with slightly differing methods). After reading your instructions, I am relieved that I did it correctly.
Quick a question just to verify. When I want to reflash to a newer build of andriod in the future, I'd just have to place the correct .nbh file in root, androidinstall.tar file in the andboot folder and hold volume up?
Click to expand...
Click to collapse
they may be changing around the .nbh file stuff, so this answer is depending on what happens with that, BUT... you shouldn't need to flash a new .nbh to change your system unless you need to change resolution. if you don't, read on.
NOTE: the process is the same whether running on NAND, or on SD card (ext2 or regular sd). Just don't mess with the boxes at the top of the install menu that say where your sys and data are installed.
TO RUN AN UPDATE that someone has provided in their thread for their build:
1. place the androidupdate.tar in the /andboot folder on your sd card
2. reboot your phone, hold this button until you see the install menu
3. from the bottom portion of that menu, select "Install update". click yes on the popup menu that notifies you that this will adjust the system files.
4. wait. it will eventually finish and kick you back to the install menu
5. go to "quit" and click it.
TO CHANGE FROM ONE ROM TO ANOTHER (same class, i.e. donut to donut)
Note: if you have a data.img, you technically should be able to keep it while moving between ROMs of the same class (i.e. donut rom to a donut rom, or eclair to eclair rom). just make sure to clear the dalvik cache before the new one boots up. however, if there are any problems, the first thing you should then do is wipe your existing data.img using the install menu and the boot your new system allowing it to create a fresh one.
1. place the new ROM file (androidinstall.tgz) into the /andboot folder on the root of your sd card, overwriting any previous install file that was there before
2. reboot your phone, hold this button until you see the install menu
3. from the bottom portion of that menu, select "backup /data", then select "yes" to overwrite old backups (btw, you can rename any databackup.img in the /andboot folder to anything you want to keep multiple backups; when you want to revert to a particular data.img backup, just rename it to databackup.img before going to the install menu). this will give you a backup of your current data just in case something goes wrong. it will take a while to complete, and eventually take you back to the install menu.
4. from the bottom portion of that menu, select "clear dalvik cache". allow this to run, it will return you to the install menu when complete.
5. from the bottom portion of that menu, select "Install system". click "yes" on the popup menu that notifies you that this will overwrite the system files. a second popup will open asking if you want to wipe your /data, select "no" for this to keep your current data file. once it installs, you will be returned to the install menu.
6. select "quit" from the bottom of the menu. this should boot android. first boot after clearing the dalvik cache, installing a new system, or wiping a data.img will take a while, just be patient
TO CHANGE FROM ONE ROM TO ANOTHER (different class, i.e. donut to eclair, or cupcake to donut)
Note: I would not recommend keeping your data.img while switching between different versions of android.
1. place the new ROM file (androidinstall.tgz) into the /andboot folder on the root of your sd card, overwriting any previous install file that was there before
2. reboot your phone, hold down this button until you see the install menu
3. from the bottom portion of that menu, select "backup /data", click ok to overwrite old backups (btw, you can rename any databackup.img in the /andboot folder to anything you want to keep multiple backups; when you want to revert to a particular data.img backup, just rename it to databackup.img before going to the install menu). this will give you a backup of your current data for future use, i.e. if you decide to return back to that version of android. it will take a while to complete, and eventually take you back to the install menu.
4. from the bottom portion of that menu, select "Install system". click "yes" on the popup menu that notifies you that this will overwrite the system files. a second popup will open asking if you want to wipe your /data, select "yes" to delete the current data file. once it installs, you will be returned to the install menu.
6. select "quit" from the bottom of the menu. this should boot android. first boot after clearing the dalvik cache, installing a new system, or wiping a data.img will take a while, just be patient.

Thanks again for the information. I and I'm sure others appreciate it. I hope your FAQ thread will get stickied.

I keep get an error when I am trying to install from NAND, it says Kernel panic - not syncing: Fatal exception in interrupt, anyone have any clues?? I am trying to install SenseHERO 1.4 and I am using the NAND kit posted with the UpdateROM utility. Any suggestions?

Nice work

Is there anyone in nj that can help me install this damn android on the vogue.. ive tried all the methods and nothing seems to work.. can it be the microSD card?? the files im using?? ive been trying to use every single build out there and nothing seems to work..

Android installation guide and tips.

First thing, If you smoke, go grab your smokes, if you drink coffee, go grab a cup. This is usually a painless process but not always.
You will need HSPL installed, as well as a Class 4 or better sd card.
Before i begin i want to thank the following; with out them it would not be possible.
cr2
NetRipper
dcordes
Markinus
LeTama
Cotulla
dan1j3l
tsamolotoff on s200
Parad0XUA
Cass
http://forum.xda-developers.com/showthread.php?t=719646
THANKS GUYS!!
What you will need is the installation copy of the build that you will be using, the latest zImage and your sdcard.
The latest Android build can be found here: Its under the standard builds section.
http://gamesquare.co.uk/
And the latest Zimage can be found here:
http://cotulla.pp.ru/leo/Android/
I personally recommend the dan1j3l's Froyo build.
Down load both the zimage and the build.
Format your sdcard, select default settings and unselect the quick format option.
After the formatting is done (about 20 mins)
extract the contents of the Froyo build to your sdcard.
Located in the folder "android" you will find a file names zimage, replace it with the one you downloaded.
WITH YOUR USB PLUGGED INTO A POWER SOURCE, reboot your phone.
As soon as you can, using the built in file manager if u have one, navigate to the android folder, select the program CLRCAD, (it will not do anything that you can see)
Then select the Zharet program.
Lay the phone down!
Sit back and wait, you will see text fly across the screen, the flash might flash, screen might fade and then come back.
Once linux is done loading and mapping out the hardware, android should be up and running.
Sign in to google and your contacts will sync if you have any on there.
Android is not perfect yet BUT it has come an amazing way since the beginning of the month.
I am using the current settings in WM, if you can do the same and you should have no problems.
SA TMOBILE HD2
HSPL2, I know HSPL3 is/has been out and is recommended, but is there any advantage in using it, i don't want to change if i don't need to
Radio 2.10.50.26
O.S. 5.2.21908 (21908.5.0.93)
Manila 2.5.20161332.0
Energy.Leo.21908.Sense2.5.Cookie.Jul.16 (absolutely love the energy roms, always updated and he includes the program to back up all settings making the update flashes a pleasant experience)
i ALWAYS TASK 29 before all roms!
CLASS 4 or better sd card.
When ever you want to load android, you must do so by selecting the two files mentiond above after a clean boot and always clrcad.exe first.
Sometimes android will not boot correctly, remember it was not designed for this phone.
Also all settings you make, programs you download, ect will stay in android
Pictures and such will be shared between android and wm.

Trying...
I'm installing it now per your instructions. A couple of concerns you might be able to help me with. I could not find the program CLRCAD in any folder, ok I couldn't find an android folder either. I went to my SD card where I had extracted the froyo & copied over the Zimage, I didn't see a Zharet program but I did see a haret file that looked like a program so I clicked on it and it started to download Linux! I hope I did it correctly even though it seemed slightly different. am I going to run into trouble not having run the CLRCAD?
Thanks for all your hard work.
Guess I answered part of my question. It did not install correctly. I'll look for a CLRCAD and retry.

cant believe im back in the winmo forum once again.ran HARET froyo last night on my HSPL2 Leon RoM,and wow.with wifi i was browsing,playing 3d games(flawless compare to my EVO 30fps capped),and watching youtube.really loving it.glad no one bought my HD2 but now its a keeper.

BigB4400 said:
I'm installing it now per your instructions. A couple of concerns you might be able to help me with. I could not find the program CLRCAD in any folder, ok I couldn't find an android folder either. I went to my SD card where I had extracted the froyo & copied over the Zimage, I didn't see a Zharet program but I did see a haret file that looked like a program so I clicked on it and it started to download Linux! I hope I did it correctly even though it seemed slightly different. am I going to run into trouble not having run the CLRCAD?
Thanks for all your hard work.
Guess I answered part of my question. It did not install correctly. I'll look for a CLRCAD and retry.
Click to expand...
Click to collapse
I Found CLRCAD ( I think I was just a little sleepy last night when I was trying this) I ran it and it loaded correctly. Wow it seems to run great! I am running Touch-X Extreme ROM and have some issues with the phone(it doesnt work, I have no antenna). I will try loading energy's rom (since so many people have got the phone to work well with his) and see how well it works out.
Good luck!

Do we really need to format our SD card? If we don't what would happen to the data already on there?

is the "zimage" provided for both dan's froyo and desire v4?
which files do i replace with the new zimage?

After a few days of use, this build seems to run fine. Except for a few things. 1) my phone tends to run real *hot* after using Android. And second, after about 5 min of idling the screen goes black and there seems like there's nothing I can do about except to reboot. I can't even push any of the bottom buttons, that doesn't work either. on. It will run just fine as long as I don't let it sit to long without touching the screen. Is this normal or am I doing something wrong? I can't wait for a even more stable build.

why cant i sign into google and other networks and why is it running overclocked? help me out yall got daaaamn lol. thanks

Is Paradoxua's Froyo build more stock than daniel's? Because daniels' uses ADW, which I'm not too fond of.
Also, is anyone else experiencing weird scrolling issues? Like you flick down a list and it's supposed to go flying down, but it only goes down like a tiny bit.
Another issue, when the screen turns off while you're connected to PC, the phone seems to disconnect too. I assume this is a WinMo issue because in WinMo when you connect your phone to your PC the screen is always on.

Thread moved to General.

i got my hd2 to load android just fine.. but the screen is very dim.. any ideas??

maybe you can toggle the backlight settings in winmo.. idk. it works for the tp2.

I always get the green screen or death or it enters android and quickly says powering off. And shuts off.

jaadamoo said:
i got my hd2 to load android just fine.. but the screen is very dim.. any ideas??
Click to expand...
Click to collapse
you need to make sure automatic light is off in win mo before you boot up android and i always leave it at around 60% and it works fine.

I have also been having some scrolling issues. It goes down a tad bit and if you hold the screen for a fraction of a second too long after first setting your finger on the screen, then it acts as if you did a holding touch.
Also the 3g is very very slow, kinda makes the market place useless since it takes for ever to download something. Wifi downloading is working.

New zimage file
Try replacing your current zimage file with this one.
http://cotulla.pp.ru/leo/Android/Cotulla_zImage_CABDET_NOSPEEDDY.rar
Just replace/override it on your sd card.
Also delete your cache folder and your data file.
You will loose your information inside of android, like doing a reset of the OS.
Check this http://cotulla.pp.ru/leo/Android/ often, fair warning many people are having problems with the newer image marked(7-25)

Some roms or radios wont work for sure!
I am now running MIRI rom wm6.5 V17.6 with radio 2.12.50.02.2 and I must say very impressive how far you devs have come in a few weeks. Phone is working with audio and WIFI. I had stock rom TMO 2.13 installed with radio 2.10 and although Android loaded and ran fine I did not have audio during calls,they sounded robotic at times or no audio at all. I am not sure if it was the radio upgrade or switching the ROM to MIRI that did the trick. I have been playing with phone for approximately six hours nonstop and it has been solid...

Gen. Y DualBOOT Implementation
Does the app work well the newer builds?
Btw a very BIG thank you all the guys working on this, you guys are freaking AWESOME!

acessford101 said:
Try replacing your current zimage file with this one.
http://cotulla.pp.ru/leo/Android/Cotulla_zImage_CABDET_NOSPEEDDY.rar
Just replace/override it on your sd card.
Also delete your cache folder and your data file.
You will loose your information inside of android, like doing a reset of the OS.
Check this http://cotulla.pp.ru/leo/Android/ often, fair warning many people are having problems with the newer image marked(7-25)
Click to expand...
Click to collapse
Thanks, I was using the Jul 19 zImage.rar file. I'm about to try this one and see if it makes a diff.

anyone know how to get the data connection to work for T-Mobile on the Android desire v5? I go into APN settings but it always requires a username and password but t-mobile doesnt use a username/password for apn.

[TROUBLESHOOTING] SOLUTION for:Random freezes, Poor battery life, SoD, WSoD,Robovoice

I am updating this post constantly with all the solutions that I find useful so please keep checking the first post.
Details of my Phone
Model: T-mobile US with 16GB class 2 card
Windows ROM: Energy WinMo ROM 01/08
Android ROM: Mattc Froyo 1.5
Radio: 2.12.50.02_2
1. Possible solution for Random freezes
As everyone is discussing here, Random freezes are caused by the G-sensor so I decided to do some experiments on my own. Here's what fixed my problem.
Go to Windows mobile-->settings-->system-->G-sensor, Put your phone on a leveled surface and hit the calibrate button. Now shut down and boot to Android.
This fixed the problem of random freezes on my android. Try this and let me know if this works.
Some users also reported that disabling Auto-rotation option in Android display settings solves the problem. But when I tried it, it didn't work for me. But worth a try since it did work for some users
If none of the above two work please try the following solution at your own risk. Some users reported that this has messed up their system and had to re-install WinMo but most of the people got it working with this solution.
1. Back up your registry
2. In windows mobile go to Registry Editor, search for "gsensor.dll" and remove the whole keyset. Reboot your phone. This step should disable your Gsensor in WinMo but it will still function in Android.
Please share your experiences after doing so.
Another possible solution(credits to ......)
Install flip n shake app from the market place ,go to advanced setting and change the sensitivity.
Please report if it worked for you or not.
There are many reasons for the freezes but the most common one should be solved by one of the above solutions.
1a. Momentary unresponsive touchscreen (hard buttons work but the touchscreen doesn't)
Theory behind the touchscreen insensitivity
The Gsensor drivers in Android are unstable and momentarily it uses a lot of CPU randomly and thats when you get the momentary touchscreen insensitivity.
Temporary solution 1(Credits to shadiku for the development)
The quickest solution would be to disable G-sensor completely. And it works 100%. Use the Kernel developed by shadiku which disables G-sensor completely. Click here for more info
Temporary solution 2(If you don't want to disable G-Sensor)
This solution won't fix the freezes 100% but it will reduce the freezes to a considerable amount.
1. Using setCPU overclock your phone to 1.1 GHz(or whatever highest frequency available). Create profiles as you wish but make sure to put all profiles to conservative mode.
2. Disable "background data" by going to Account & Sync settings.(So there would be minimum load on CPU)
3. Kill all running applications (every hour) using Advanced task killer.
4. Disable Auto rotation.
All the steps mentioned above will surely help you with the battery life as well. You will still get some rare touchscreen freezes like once every two or three hours. But it is very very very less compared to once every 5 to 10 minutes before doing the tasks above. This is due to more CPU available for the culprit application (Gsensor driver)
2. Poor battery life
This isn't my work. This is copied from Bakedbread's thread here
1. Install BSB tweaks 1.6 and turned ON "Power Savings"
2. Go to registry editor and edit the following keys as under
HKLM\Comm\AsyncMac1\Params
DisablePowerManagement=0
HKLM\Comm\PPTP1\Params
DisablePowerManagement=0
HKLM\Comm\L2TP1\Params
DisablePowerManagement=0
HKLM\Drivers\SDCARD\ClientDrivers\Class\SDMemory_C lass\High_Capacity
DisablePowerManagement=0
HKLM\Drivers\SDCARD\ClientDrivers\Class\MMC_Class\ High_Capacity
DisablePowerManagement=0
HKLM\Drivers\SDCARD\ClientDrivers\Class\SDMemory_C lass
DisablePowerManagement=0
HKLM\Drivers\SDCARD\ClientDrivers\Class\MMC_Class
DisablePowerManagement=0
It helped me. so try your luck.
Also some people have reported that underclocking(using SetCPU or other programs) help in increasing battery life too.
Changing to the latest kernel also helps with battery life. Please find below the procedure for changing the kernel.
1. Download latest Kernel(zImage) from here. You need to download the regular one and not the usbhost one.
2. Rename the downloaded file to zImage.
3. Go to your phone's android folder and rename the zImage there to zImage.old(just incase the newer zImage gives you trouble). Copy the downloaded zImage to the Android folder.
4. Boot Android.
Trouble booting or connecting to wifi after updating to the latest Kernel?
check out the post here for booting problem. and checkout the post here for wifi problems.
Here is also another observation. When you charge the phone in Android it doesn't charge fully(even though it shows 95% or 96%) and it drains the battery really quickly. If you charge the phone while its switched off or while its in WinMo the battery life seems to be improved. But I need some confirmations for this from users.
Check out this thread as well regarding standby current which affects your battery life as well.
http://forum.xda-developers.com/showthread.php?t=770903
3. SoD(Sleep of Death)
I had the problem of SoD while using 2.09.50.02_2 radio. Once I changed my radio to 2.12.50.02_2 the problem of SoD was gone. Please try changing your radio and report back.
If changing radio doesn't help then try this it might help (Credits to fi3ry_icy)
http://forum.xda-developers.com/showpost.php?p=7531752&postcount=16
Also another possibility is in WinMo change the sleep time to never/maximum possible and see if that helps.
4. WSoD(White screen of death)
Not my work. Not sure whose finding this is.
When u get stuck at white screen while rebooting open startup.txt and change set cmdline to set cmdline "rel_path=Android lpj=638976" and reboot again.
Edit: If the lpj=638976 is already there when you open the startup.txt and you are getting WSoD then try removing "lpj=638976" from the line and reboot.
Another possible solution(Credits to ....)
copy the whole sdcard (backup to PC), format it the with 'SD formatter' (total write, erase and format process) and afterwards, start with a fresh install of the android folder. Copy all other folders back from the backup.
do not use automount in android, but only use 'diskdrive option' when booted back to WinMo if you want to transfer files to the SD card. If you need to transfer smaller files to SD while in Android then use a wifi file explorer(Search market place for one that suits you).
5. Robotic voice
I believe this problem is associated with the combination of WinMo and Android rom. Changing the WinMo rom helps get rid of this problem. So try new combination until you find one thats working.
It is said that Windows mobile Base rom 2.14 and higher does not cause this problem. Users have reported that they had the problem with 2.14 and when they tried 2.13 it eliminated the problem. So not sure if it has anything do with the Base ROM or not. But one thing is for sure that it is the combination that creates/solves the problem.
6. Taking long time to wake up from stand by
When pushing the end call button on ur mobile, it will go in standby and when u push it again, u get lockscreen.
7 off the 10 times it take a few seconds for the screen to wake up, and sometimes it freeze longer (5seconds).
Possible solution:
The problem is caused by Advanded task Killer. here's what solved my problem of screen not coming back on for couple seconds.
In advance task killer I changed the "Auto kill frequency" to 30 minutes instead of "when screen off" and it solved the problem.
If you want to try different lock screen go to market place and download 'finger scanner lite'. I know its a stupid program but at least something to experiment with.
Another temporary solution(Credits to Bazman123)
try pressing the power button for a few seconds, this will bring up the shutdown screen kicking your phone back into life instantly.
7. Unable to mount SDCARD error Thanks to shu8i for solution
If you get unable to mount sdcard plz replace set cmdline "rel_path=Android" with set cmdline "rel_path=Android loop_partition=mmcblk0" in startup.txt
8. Mount SD card to PC for file transfer
I knew this trick since the days of Kaiser Android but never needed to use it on my HD2 but for anyone who wants to mount the SD card to PC for file transfer here's a quick trick.
Download and install "Auto Mount Your SD Card" made by JR Studio from market.
Unplug your phone
Open the Auto Mount App
Check Enable SD Card Auto-Mounting and exit the app
Plug the phone in
Or you could just use a wifi file explorer type program for transferring small files.
9. Error while installing certain apps
There are some particular apps which gives an error while trying to install (e.g. Neocore)
All you need to do it go to setting and unmount the SD card. Install the app and remount the SD card and you are good to go.
If you find anything wrong or if you want me to add your solutions to this post. Please PM me.
Also check out the third post below by fi3ry_icy for more solutions.

And please add this to the thread for what people have to report to the developers if they experience problems.

Unable to mount SD card
set cmdline "rel_path=Android" with set cmdline "rel_path=Android loop_partition=mmcblk0" in startup.txt
SOD (Sleep of Death) related, and generally setting up phone and SD card for booting into android properly ( http://forum.xda-developers.com/showpost.php?p=7531752&postcount=16 )
fi3ry_icy said:
how can i do that if i am using chuckydroid rom for booting android? it is very stripped down and has very little function as a winmo os..
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
in addition, i would like to add that i think i have found a way to overcome the SOD (at least for now for me), hopefully, it will continue to work as i have not have any SODs since i tried what i did..
this is what u need to do:
reformat ur SD card but before u click the format button, change the allocation size from the setting u see, to the largest possible...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
after u format ur SD card, only copy in the Android boot file of the android of ur choice..
next up, prepare the phone by doing task 29, flashing a 2.08 and above radio.. i am using 2.12.50.02.2 radio from ( http://vbnfiles.com/HD2 Common/Radios/Radio_2_12_50_02_2.rar )
then, install chucky rom lite for android booting ( http://forum.xda-developers.com/showthread.php?t=734238 )
next, start up the phone and do a hard reset without the SD card inside..!
after the hard reset, boot back into winmo and change the date and time settings..
off the phone..
insert the SD card then on the phone..
run android and set up froyo..
hopefully it stops the SODs for good..
so far so good for me, its 2 hrs, and i've not have SODs.. previously the longest time b4 SOD hit me was 35 mins..
----------------------------------------------------------------------------------------------------------------------------------------------------------------
ADDED: added a pic to show what i mean..
Click to expand...
Click to collapse
Battery Related
Use one or more of these program together:
SetCPU ( http://forum.xda-developers.com/showthread.php?t=734886 )
OR try
Juice Defender ( http://www.talkandroid.com/9599-extend-your-battery-life-with-juice-defender-for-android/ )
OR try
Overclockwidget (need root) by billy cui (from android apps market)
OR try
Tasker: a program or android for users who want almost total control over their system ( http://lifehacker.com/5599116/how-to-turn-your-android-phone-into-a-fully+automated-superphone )
Possible winmo setting tweaks which may or may not help improve battery life: ( http://forum.xda-developers.com/showthread.php?t=749753 )
Robot Voice
Use another WinMO Rom-Radio Combination
Possible improvement in SD card performance
Use special SD card formatting program ( http://forum.xda-developers.com/showthread.php?t=748961 )
Laggy screen/phone/android when using the phone while walking or when phone is not stationary
Turn off auto-rotation in froyo ( http://forum.xda-developers.com/showpost.php?p=7579476&postcount=21 )
a way to possibly increase ur DATA connection speed (worked for me)
memin1857 said:
Nice find!
For other users:
What warrenb213 means in simple English is:
3G/EDGE speed tweak for shubcraft 1.4:
1) Launch Astro File Manager
2) Goto /system and find file named build (build.prop)
3) Tap and hold and select edit -> copy
4) Goto /sdcard/Android/root/system
5) Tap Paste
6) Tap and hold build file and select open as -> text -> file editor
7) Scroll down and find these lines
ro.ril.hsxpa=2
ro.ril.gprsclass=12
Those lines are correct.
Look 6-7 lines further and you will find:
ro.ril.hsxpa=1
ro.ril.gprsclass=10
Delete these two lines.
(shu8i tweaked values are 2 and 12)
SAVE (click back button and tap save when asked)
8) REBOOT android. Now you should get faster 3G/EDGE data.
Notes:
-If you directly edit build file within /system folder IT WILL revert back after reboot.
-You may want to delete /sdcard/Android/root/system/build.prop after one reboot so in the future you don't forget it. It gets copied to real /system on first reboot.
-You may want to backup the original build.prop file incase you have problems with data. (Or you can change the values back to 1 and 10)
Click to expand...
Click to collapse
Crashes and how to help kernel coders by submitting logs for them to troubleshoot and debug
moorgogel said:
Come on guys, you wont help developers if you just write "ok i will help you" Nobody need that besides this thread is going to be confusing. Please help Cotulla and provide him your logs.
How to create logs:
Download the tool Andlog on Cotullas Homepage: http://cotulla.pp.ru/leo/Android/andlog.exe
After you detect Problems in Android (Sleep of Dead or something) you need to reset your device with the red reset button on the back of your HD2
Don't remove battery!!!
Once WM is booted you can run andlog.exe and it will create a andlog.txt file on the root of your device. Be aware that Andlog dont show any message! (like CLRCAD)
Paste the content here: http://pastebin.com
and link it here in this forum with detailed information
Ok i will start with providing logs:
Got SOD while LEO was in Standby. Waited any seconds but screen stayed black
Log: http://pastebin.com/DPPAd6ep
Click to expand...
Click to collapse
Cotulla said:
moorgogel, nice guide, thanks!
other method (for non-fatal errors) possible to use ADB from Android SDK.
just put in command line
Code:
adb shell dmesg > dmesg.txt
and u got current kernel log in dmesg.txt.
basically it's not obviously.
some bugs won't show anything in log. for example if BT isn't working in some android build, kernel log won't show anything.
Click to expand...
Click to collapse
General questions answered in FAQs already
HD GEEK said:
[WARNING] ***ANDROID ON HD2 IS STILL AT EARLY STAGES NO 1 CAN BE HELD RESPONSIBLE FOR ANY DAMAGE CAUSED TO YOUR DEVICE ***
From what i have found there are at the moment 3 main builds that are running well -
HTC SENSE (DESIRE ROM)
FROYO BUILD BY dan1j3l
Froyo 2.2 Android Build by Parad0XUA
FROYO 2.2 WITH SENSE
Android 2.1 Eclair (Senseless)
all these can be found at http://gamesquare.co.uk allways keep a close eye on this site as new builds come out fairly frequent as development is quick.
★★★NOW HOW TO GET ANDROID ON HTC HD2★★★
Download a build of your choice
htc sense desire build
or froyo build
**THERE ARE ALSO NEW BUILDS BEING ADDED TO HD2 ANDROID SECTION ALL THE TIME WITH INFO AND LINKS AVALIBLE WITHIN THE THREAD **
Prepare your device
windows rom - windows rom has been linked with issues within the android builds so for the first time im going to compile a list of working roms here that have no issues within android
i have been using ChuckyROM GTX + CHT 1.8.5 - 23128 from the start of android development and have yet to have an issue below is a list of other roms and links that are working well with android :-
BARE BONES WM ROM FOR ANDROID BY NRG
[ROM][WWE]★★★Astraios Roms★★★[REG/BUUF/GTX][23569][22nd July]
ELEGANCIA ROM Series™
ChuckyROM GTX + CHT 1.8.5 - 23128 ~ 2.10.1
¸¸.·´¯`·.¸¸.- Energy -.¸¸.·´¯ |Jul 21| 21911||23121 * Sense 2016
★★★ PLEASE LEAVE LINKS AND INFORM ME OF ANY ROMS YOU HAVE TRIED AND HAD NO ISSSUES ★★★
FOR INFORMATION ON HOW TO FLASH A ROM PLEASE GO TO FLASHING GUIDE.
THE RADIO
RADIO IS SIMPLE USE ONLY RADIO FROM 2.08 ~ 2.12 DONT USE A RADIO LOWER THAN 2.08 AS IT WILL NOT BOOT I CAN NOT SAY WHICH IS THE BEST RADIO AS IT IS DIFFRENT IN DIFFRENT AREAS THE BEST THING WOULD BE TO TEST DIFFRENT RADIOS WITH ANDROID I HAVE TESTED 2.12 AND HAD NO ISSUES.
HOW TO INSTALL A RADIO : -
For installing a RADIO ROM you need HardSPL installed to your device.
Rename the extracted file to "RUU_Signed.nbh" and flash with the CustomRUU
RADIOS THAT WORK WITH ANDROID : -
Leo_RADIO_2.12.50.02_2: MegaUpload
Leo_RADIO_2.11.50.26**: MegaUpload
Leo_RADIO_2.11.50.20**: MegaUpload
Leo_RADIO_2.10.50.28_2: MegaUpload
Leo_RADIO_2.10.50.26**: MegaUpload
Leo_RADIO_2.10.50.19_2: MegaUpload
Leo_RADIO_2.08.50.05**: MegaUpload
FOR REF USE RADIO THREAD
HSPL
You must have hspl 2 or 3 for android to run well please use HSPL GUIDE
Memory Card
all though not nessecery re-formating your memory card is a must - i had problems with android builds in the past but re-formating memory crad solved nearly all crashes and and slow downs.
BACK UP ALL DATA BEFORE RE-FORMATING
RE-FORMAT TO FAT32
COPYING ANDROID ACROSS
SENSE BUILD - copy all files to the ROOT of your memory card not a subfolder i.e haret boot loader should be in E:/HaRet.exe not E:/android/HaRet.exe
FROYO BUILD - Copy all files to a folder called android on the root of your memory card i.e haret boot loader should be in E:/android/HaRet.exe
**SOME NEW BUILDS ARE BEING ARE BEING PLACED IN FOLDERS WITH NEW NAMES IF THIS IS THE CASE IT WILL BE STATED WITHIN THE README**
BOOTING ANDROID
easyiest way to boot is to boot windows then go to a file explorer and run CLRCAD.EXE then run HaRet.exe ALWAYS REMEMBER RUN CLRCAD.EXE FIRST AS THIS GIVES ANDROID SOUND DONT WORRY IF IT DOES NOTHING ITS NOT SUPPOSED TO
YOU MUST BOOT ANDROID THIS WAY WITHIN 30 SECOUNDS OF WINDWOS BOOTING OTHERWISE ANDROID WILL RUN IN TURBO MODE AND BE VERY UNSTABLE.FIXED WITH NEW ZIMAGE
DUEL-BOOT PROGRAMS -
GEN.Y DUEL BOOT - QUOTE FROM NRG -
Hi All,
I changed the dual boot cab from yozgatg.
It now puts clrcad.exe to the startup folder so if you boot android you'll have sound. I also put the skin in from sk8inmonk.
So credits for yozgatg and sk8inmonk.
Only boots android directly from the root of the storage card!
This has an autoboot option in 10 seconds or in 3 seconds.
LINK
jmz Android Dual-Boot for HD2 v4 --- 19JUL10
LINK TO THREAD
***IMPORTANT THINGS WHEN BOOTING ANDROID***
WHEN BOOTED GO TO ANDROID MARKET AND DOWNLOAD ADVANCED APP KILLER I HAVE FOUND THIS THE MOST IMPORTANT APP TO HAVE ATM AS IT KILLS APPS YOU DONT WANT RUNNING THUS SAVING BATTERY
POWER MANAGMENT IS A BIG ISSUE AT THE MOMENT BUT I HAVE FOUND THAT LEAVING PLUGED IN ON CHARGE WHILE BOOTING ANDROID WILL CHARGE THE PHONE BUT THE LED WILL STAY PERMENANTLY ON! EDIT - USE LATEST ZIMAGE LOCATED IN 3RD POST AND ALL CHARGING PROBLEMS ARE SOLVED
ALL QUESTIONS WELCOME IN THIS THREAD NO MATTER HOW NOOBISH ALL WILL BE ANSWERED F&Q SECTION COMING SOON ALONG WITH A TROUBLESHOOTING CHART FOR NOW I HAVE WORK
.
Click to expand...
Click to collapse
HD GEEK said:
TROUBLESHOOTING
THE PROBLEM - The linux kernel did not finish booting.
/ failed to mount the sd card. cannot continue
/ bin/sh: can't access tty; job control turned off
/
SOLUTION -
What I did was download and install the SDFormatter tool and formatted my SD card. I've had formatted my card a lot of times but this tool did the trick.
You can locate it here: http://www.sdcard.org/consumers/formatter/sdfv2000.zip
(PROBLEM AND SOLUTION PROVIDED BY WOUSIPX
ANDROID TIPS AND TRICKS
LONG PRESSING HOME BUTTON OPENS A TAB SHOW ALL APPS THAT ARE OPEN SO YOU CAN SWITCH BETWEEN THEM
Click to expand...
Click to collapse
[HOWTO] Backup ALL Settings and Prefs When Upgrading Android (Homescreen/SMS/etc)
Fmstrat said:
This method requires ROOT, but will allow you to backup all settings quickly and easily for a full restore to a different build. This is handy when running Android on a Windows Mobile device such as the HD2, since it allows us to easily switch to one of the many builds that come out weekly. However, this method can be applied to any Android device.
Ops, if you’d rather move this thread to a general Android discussion, no problem. I just thought it was pertinent here given all the ROM changing people are doing.
It can back up everything, from home screen widget positions to SMS messages. If you’re using keyboards like SwiftKey, it will even save your learned DB.
Backup:
Acquire Titanium Backup” from the Market
The first time you run the program, hit the “Problems?” button. This will download the latest version of Busybox, a set of command line utilities used to backup data.
Tap “Backup/Restore”
Press the “Menu” button (hard button)
Choose “Batch”
Press “Run” next to “Backup all user apps + system data”
Leave everything selected on this screen. We will selectively choose what to restore in our new build. Having everything backed up means you won’t miss anything.
Ensure “Kill active apps” is selected
Press “Run the batch operation”
While this is running, tap the screen every now and again to ensure your phone doesn’t time out. (just to be safe for any auto-killers that may be running)
Reboot your phone
Restore (after switching builds):
Note: For those running on a WM device, you can download the APK for Titanium Backup here and place it in your AndroidApps folder for it to be accessible on your first boot.
Skip as much of your new Android Setup screens as possible. No need to waste time here when it will be restored with Titanium.
Go into settings and set up your Google Account.
After adding the account, set it to NOT sync.
Do this BEFORE entering the Market, or the syncing will happen automatically. The reason for doing this is that you’re going to overwrite it all with Titanium data anyway, so why waste the resources and time.
Go into “Settings -=> Applications” and check “Unknown Sources”
Re-acquire Titanium Backup (unless you had the APK in your AndroidApps folder) and hit the “Problems?” button to install in your new build.
Tap “Backup/Restore”
Press the “Menu” button (hard button)
Choose “Batch”
Press “Run” next to “Restore missing apps + all system data”
If you are restoring the exact same Build:
Click “Select All”
Choose “App+Data”
If you are restoring a different Build or upgrading to a new version of a Build:
Click “Deselect All”
Choose “App+Data”
Select all Green items (These are your settings)
Select all Crossed out items (These are the apps not included in your build)
Select any other items you know are the same within your build, and that you want to restore settings for
Press “Run the batch operation”
For every application that the install prompt comes up for, hit “Install” and then “Done.”
Reboot your phone
On next boot, if you get “Problem Loading Gadget” on some widgets, you will have to remove them from the home screen and re-add them manually. This has only occurred a couple of times for me, usually things go smooth.
Click to expand...
Click to collapse
for people and devs who want to try messing around with desire apks (sense apks)
rheza02 said:
http://rapidshare.com/files/353766794/Desire-apk.zip
Click to expand...
Click to collapse

Yes I will report to developers once everyone confirms what works and what not because things that work for me might not work for everyone.
Sent from my HTC HD2 using XDA App

robotic voice.
i use a 2.14 base and 3.04 ext packs but still have robo. now i use andriod bootcamp and when i make it auto load andriod on boot. i get clear voice but then second call back to robo. using radio. 2.12.50.02.2. if i disable sense reboot blah blah still the same. playing music and other sound apps are perfect but all goes mad once made a call, shuts sound off and gets laggy. so is it down to clrcad whatever it actually does? can't say its oemdrivers as it worked once. must get to bottom of it.

richmondo said:
i use a 2.14 base and 3.04 ext packs but still have robo. now i use andriod bootcamp and when i make it auto load andriod on boot. i get clear voice but then second call back to robo. using radio. 2.12.50.02.2. if i disable sense reboot blah blah still the same. playing music and other sound apps are perfect but all goes mad once made a call, shuts sound off and gets laggy. so is it down to clrcad whatever it actually does? can't say its oemdrivers as it worked once. must get to bottom of it.
Click to expand...
Click to collapse
same here.
got the latest goatrip-rom (gtx) - GER
radio 2.12.50.02_2
shubi-android-rom 1.2b
no matter which way i boot into android, i got the robo-voice or sometimes cant hear a thing on calls (no ringing, no voices etc.).
this really makes the whole android useless for me. its working really smooth, except the phone-calls. any help?

Trying your recommendation for calibrating the G-Sensor in WinMo, I'll report back if I get anything conclusive.
As for Radio, I'm using 2.10.50.08_2 - I've only ever had the echo, and once Cotulla put out the volume fix etc, it went away, but as already mentioned it's also down to the WinMo, the amount of combinations possible is always going to be a pain in the arse!
Phil

i am at work at mo but seems like stuff from 2.10 wavedev.dll rilphone.dll is reported to fix the robo. sneaky suspition that it maybe rilphone.dll which relates to the radio. like said earlier in thread mine did work once with complete 2.14 base. when i get back i will try many combinations and let you know of my findings. ******ing phones lol. but personally prefer winmo at mo especially on leo with sense. better weather animation, but like the live wallpapers on android. AHHHHHGGHGHGHH

Any conclusions on the G-sensor solution yet?? Can somebody please report back if it worked for them or not??? It will surely help a lot of people.
kerman19 said:
Trying your recommendation for calibrating the G-Sensor in WinMo, I'll report back if I get anything conclusive.
As for Radio, I'm using 2.10.50.08_2 - I've only ever had the echo, and once Cotulla put out the volume fix etc, it went away, but as already mentioned it's also down to the WinMo, the amount of combinations possible is always going to be a pain in the arse!
Phil
Click to expand...
Click to collapse

I'm trying to test the solution based on erase "gsensor.dll" keys from registry in windows mobile and no freezes yet....it looks so good. Still testing...

proalius said:
I'm trying to test the solution based on erase "gsensor.dll" keys from registry in windows mobile and no freezes yet....it looks so good. Still testing...
Click to expand...
Click to collapse
Did you try the calibration solution? did it work?
Let us know how the gsensor.dll solution works over days. Also does your Gsensor work in Android after deleting the key from WinMo?

hardik119 said:
Did you try the calibration solution? did it work?
Let us know how the gsensor.dll solution works over days. Also does your Gsensor work in Android after deleting the key from WinMo?
Click to expand...
Click to collapse
I didn't do the calibration, i directly did the ajusts over registry. I still without freezes at this moment

This may be a silly question but why would deleting the wm Gsensor file affect android at all, because android doesnt run adjacent to wm ?

When pushing the end call button on ur mobile, it will go in standby and when u push it again, u get lockscreen.
7 off the 10 times it take a few seconds when the screen responds, and sometimes it freeze longer (5seconds).
I noticed when u install a different lockscreen (i used for fun fingerprint lockscreen)
No freeze at all, quick responding..
Can someone check this..? If it really helps..
Maybe it's the lockscreen that is the problem..
When u use Fingerprint lockscreen, it;s not loading the standard lockscreen..
Greetz Jordi..

Batskoning said:
When pushing the end call button on ur mobile, it will go in standby and when u push it again, u get lockscreen.
7 off the 10 times it take a few seconds when the screen responds, and sometimes it freeze longer (5seconds).
I noticed when u install a different lockscreen (i used for fun fingerprint lockscreen)
No freeze at all, quick responding..
Can someone check this..? If it really helps..
Maybe it's the lockscreen that is the problem..
When u use Fingerprint lockscreen, it;s not loading the standard lockscreen..
Greetz Jordi..
Click to expand...
Click to collapse
I had the same problem that you are talking about with the screen not coming on for couple seconds when locked. But that problem is different than the freezing problem(atleast for me)
Do you have Advanced task killer installed? here's what solved my problem of screen not coming back on for couple seconds.
In advance task killer I changed the "frequency to kill (I don't remember the exact word)" to 30 minutes instead of "when screen gets off" and it solved the problem.
Please let me know if this works for u too so that I can add it to the first post.

tinmanjo said:
This may be a silly question but why would deleting the wm Gsensor file affect android at all, because android doesnt run adjacent to wm ?
Click to expand...
Click to collapse
Android doesn't run adjacent to wm but it sure uses some drivers from WinMo. And I am sure about that because I get Robotic voice when using certain WinMo roms. Also changing some settings in wm helps with the battery life. So it is certain that Android uses some drivers from WinMo.

Radio
Thanks for helping out guys. Everything is going smooth with Android but the only thing that I'm having problems with is the SOD. I currently have radio 2.10.50.26 and I'm reluctant on changing radio to the one recommended (2.13.xx.02 radio). My question is: What is the difference between these two radios? What changes? Will I get better/worse signal and data speeds? BTW Im using a tmobile hd2 with energy rom. Thank you for your help.

hardik119 said:
Android doesn't run adjacent to wm but it sure uses some drivers from WinMo. And I am sure about that because I get Robotic voice when using certain WinMo roms. Also changing some settings in wm helps with the battery life. So it is certain that Android uses some drivers from WinMo.
Click to expand...
Click to collapse
I tried to delete hklm/drivers/builtin/gsensor but resco reg editor says "the key cannot be deleted".So i went inside key and in the value dll gsensor.dll i wrote something else.I did soft reset.In winmo boots correctly.But in android doesnt boot again.It stucks in white screen with htc logo.I correct the value,but still nothing.I made hardreset but no luck.Now i restore from spb backup my winmo installation and i am going to do a new clean install of android.

mustang_3kgt said:
Thanks for helping out guys. Everything is going smooth with Android but the only thing that I'm having problems with is the SOD. I currently have radio 2.10.50.26 and I'm reluctant on changing radio to the one recommended (2.13.xx.02 radio). My question is: What is the difference between these two radios? What changes? Will I get better/worse signal and data speeds? BTW Im using a tmobile hd2 with energy rom. Thank you for your help.
Click to expand...
Click to collapse
I am not sure what are the differences between the radios and the better/worse signal depends on the area and network you are using. with the same radio some ppl get better reception while some get worse. So you will have to experiment yourself.
clio94 said:
I tried to delete hklm/drivers/builtin/gsensor but resco reg editor says "the key cannot be deleted".So i went inside key and in the value dll gsensor.dll i wrote something else.I did soft reset.In winmo boots correctly.But in android doesnt boot again.It stucks in white screen with htc logo.I correct the value,but still nothing.I made hardreset but no luck.Now i restore from spb backup my winmo installation and i am going to do a new clean install of android.
Click to expand...
Click to collapse
I am sorry to hear that. Some people have reported that they got the freezing problem solved by deleting the registry key. Did you try the calibration trick???

Hi there...
Thx for the advice about the screen freezing...i tryed the calibration but still freezes then i deleted the gsensor.dll and till now evrything going right..for about 3-4 h of using the phone without freezes...thx dude for the advice!!!!
Cheers!!!
EDIT: The thing to deleting gsensor.dll definetly work...before when i was playing UNO it was freezing evry 5 min. and now playing for 40 minutes without a single FREEZ...amaizing suggestion.... Thx

[Q] Multiple Android Installations At Once.

Hey guys, I'm pretty new to the Android scene, but have been happily using FroyoStone for quite some time now. That being said, I have been looking around the Android Forum and have seen a lot of very pretty and exciting builds.
Being a man who cannot make up his mind, and too lazy to try them all one at a time, I was wondering if it was at all possible to install more than one Android build at any given time on my SD card. It's 16GB in size, so that wouldn't be an issue, I am just wondering what steps I would have to take to insure that none of the builds would conflict with each other. Would it be as simple as to put them all into their own seperate folders? ( I was under the impression that you HAD to run it from a folder named Android, would it require a Reg hack to change this? )
If anyone has any ideas or suggestions on this matter, I would like to hear from them.
I will update my post with any successes I achieve if anyone else is interested in hording builds
Edit
Wow I joined in October 2007 and this is my first post!

I currently have 3 builds on my phone. There are a couple of android loaders in that tell you how to load multiple builds. Check the development forum.

Will do, thanks for the speedy and to the point reply.

help setting up mulitiple builds
I've been having a problem with loading multiple builds. I've tried the multi build loader and was unsuccessful. I named each folder specifically (sdcard/android; sdcard/android evo; etc.) just to differentiate. I even changed the startup txt to reflect the folder accordingly. But the loader would always load the one that's in the "android" folder. Even when I go into the specific folder of a separate build and run clrcad and haret, it will still load the other build.
Using Shubcraft stock 1.5, Mdeejay evo sense 1.6, and darkstone. Any help appreciated. Thank you for your patience and time with me.

Each builds startup.txt should reflect its folder name.
This is example line from startup.txt
set cmdline "rel_path=Android_evo nand_boot=0"
(Change the red word to reflect yours)
You can use Exceller Multiple Build Loader for Android
http://forum.xda-developers.com/showthread.php?t=737001
You can tap to change which build to load.
With this setup you can have unlimited number of android builds in your sd card at the same time and they won't conflict with each other. (Well, of course sd card capacity is the limit )