Related
So, I figured with Android getting ported quite nicely and is fairly well along, we should start working on getting it flashed directly to NAND. Eliminate Windows Mobile all together. So here are my notes. All this stuff combined in some order and sense will make it able to flash NAND with Android. But for some reason I just can't piece it all together and make the puzzle fit. I am posting this in hopes that someone with enough skill can take the information and build what is needed.
Working Tinboot - This is what the core of NAND android flashing is.
NBH for installation (Examples) - Needed to install android. Flash nbh, install android, reboot
To test all of this we need the RESUMEADDR of the HD2. Then we can pass RESUMEINTOBOOT to haret. Then we can check if there is enough low-level hardware support to even boot Android yet. This can be gotten by using haretconsole. But I have yet been able to get the RESUMEADDR because of issues with my computer.
Thanks goes to dzo for pointing me in the right direction for all of this.
They still need WinMo to boot to initialize some of the hardware... that's why most winmo phones that have android ports can't flash to nand yet... and the couple that do have flashable roms took a long time to develop.
What's the big deal about flashing it to nand anyways? Do you really want to take away your phones ability to run 2 os's to make it just another android phone that doesn't run it as well as a native android phone? Flashing to nand doesn't improve performance much, if any. Some people think that haret emulates android and thatg winmo is still running in the background, but that's not true. HaRET shuts down the windows kernel and starts the linux kernel. The only speed increase that you would see is the difference in data transfer speed from the nand or memory cards to ram, which would probably only be noticeable during certain tasks, but probably even then wouldn't make much of a difference.
I would prefer to have a dual-booting powerphone than to make it just another android phone that doesn't run as well as native android phones. If I wanted just android on my phone, I'd get an android phone.
i agree but...
zarathustrax said:
They still need WinMo to boot to initialize some of the hardware... that's why most winmo phones that have android ports can't flash to nand yet... and the couple that do have flashable roms took a long time to develop.
What's the big deal about flashing it to nand anyways? Do you really want to take away your phones ability to run 2 os's to make it just another android phone that doesn't run it as well as a native android phone? Flashing to nand doesn't improve performance much, if any. Some people think that haret emulates android and thatg winmo is still running in the background, but that's not true. HaRET shuts down the windows kernel and starts the linux kernel. The only speed increase that you would see is the difference in data transfer speed from the nand or memory cards to ram, which would probably only be noticeable during certain tasks, but probably even then wouldn't make much of a difference.
I would prefer to have a dual-booting powerphone than to make it just another android phone that doesn't run as well as native android phones. If I wanted just android on my phone, I'd get an android phone.
Click to expand...
Click to collapse
i agree with you, but this guy is asking for help do do a certain task.
I second you on your idea but there are people that would prefer to have a win mo. phone running android even if it runs slower or worst because some people just dont like wm. software.
By the way i cant help you jmztaylor because i just dont know...
zarathustrax said:
They still need WinMo to boot to initialize some of the hardware... that's why most winmo phones that have android ports can't flash to nand yet... and the couple that do have flashable roms took a long time to develop.
What's the big deal about flashing it to nand anyways? Do you really want to take away your phones ability to run 2 os's to make it just another android phone that doesn't run it as well as a native android phone? Flashing to nand doesn't improve performance much, if any. Some people think that haret emulates android and thatg winmo is still running in the background, but that's not true. HaRET shuts down the windows kernel and starts the linux kernel. The only speed increase that you would see is the difference in data transfer speed from the nand or memory cards to ram, which would probably only be noticeable during certain tasks, but probably even then wouldn't make much of a difference.
I would prefer to have a dual-booting powerphone than to make it just another android phone that doesn't run as well as native android phones. If I wanted just android on my phone, I'd get an android phone.
Click to expand...
Click to collapse
well running android from sd card creates higher battery consumption. Am I right? this is a good argument.
jojo_angelov said:
well running android from sd card creates higher battery consumption. Am I right? this is a good argument.
Click to expand...
Click to collapse
Yeah, that is true. Reading about the nand ports for other winmo devices show that battery is improved, but it still isn't no where near as good as winmo is with batteries. Power management is one of the issues that almost all android ports have.
At this point, i don't believe nand flashing is possible for the hd2... like i said, they need winmo to initialize many things. Also, once it is possible to flash nand, it probably won't have as much working hardware as the haret version until they get drivers that initialize all that hardware. If you look at some of the other nand flashable ports on other phones, things like wifi, bluetooth, camera, gps, etc don't work while they work when you use the haret bootable version. We're still a long way away from booting from nand... at least a version functional enough to want to get rid of winmo.
I'm really curious as to what peoples reason is to want a nand flashable version so bad.... I've heard people say that winmo is still running in the background with haret, but thats just not true. You generally have a much more functional android when run of storage card than the nand flashable ports are. There may be a small increase in battery life and small increase in speed when flashed to nand, but you will lose a lot of functions until they find ways to initialize the hardware without winmo. And from what i've seen with the hd2 ports so far, I don't think we will have any issues with speed like they did with other devices, so I don't see nand being needed to increase speed.
cmon people, lets support the motion.. remember we are dealing with one of the best htc-winmo devices here, the one of a kind htc-hd2..
for me the point is not "what is the need of doing this", the point is "it can be done "
maybe one shouldnt rush to start flashing android on hd2, thats why alpha and beta versions are made, where one understands the risks but does it anyways for the fun experience.. n remember this is just the beginning of android on hd2, i think there is room for a whole lot of improvement
zarathustrax said:
Yeah, that is true. Reading about the nand ports for other winmo devices show that battery is improved, but it still isn't no where near as good as winmo is with batteries. Power management is one of the issues that almost all android ports have.
At this point, i don't believe nand flashing is possible for the hd2... like i said, they need winmo to initialize many things. Also, once it is possible to flash nand, it probably won't have as much working hardware as the haret version until they get drivers that initialize all that hardware. If you look at some of the other nand flashable ports on other phones, things like wifi, bluetooth, camera, gps, etc don't work while they work when you use the haret bootable version. We're still a long way away from booting from nand... at least a version functional enough to want to get rid of winmo.
I'm really curious as to what peoples reason is to want a nand flashable version so bad.... I've heard people say that winmo is still running in the background with haret, but thats just not true. You generally have a much more functional android when run of storage card than the nand flashable ports are. There may be a small increase in battery life and small increase in speed when flashed to nand, but you will lose a lot of functions until they find ways to initialize the hardware without winmo. And from what i've seen with the hd2 ports so far, I don't think we will have any issues with speed like they did with other devices, so I don't see nand being needed to increase speed.
Click to expand...
Click to collapse
why dont we just have it running from internal memory without flashing? it would solve the speed and battery problems and we would still get to keep winmo . or is there a reason this cannot happen?
Well, knowing that android builds (system and user data) take about 530MB, it would be a tad hard to stuff in the HD2's 512MB, of which about 300 are used by Winmo...
Maybe on the 1GB TMOUS though....
kilrah said:
Well, knowing that android builds (system and user data) take about 530MB, it would be a tad hard to stuff in the HD2's 512MB, of which about 300 are used by Winmo...
Maybe on the 1GB TMOUS though....
Click to expand...
Click to collapse
but most of us have the 512 mb version
i would be interested in getting android stored on the device memory (Not a ROM flash). NRGZ28 released a winmo version that is very small (50 or 60MB) leaving me with 800Mb+ of internal storage. what must be changed to get HaRET to look in internal storage for the files and store information there?
This should be a very good discussion..btw ive been running off of sd card for a while now and battery consumption isn't that bad at all
As far as I see it, a major problem is for any non TMOUS HD2 owners an SD card will always be mandatory. Even if you are able to fit the whole system into the half sized NAND, there wouldn't be much room left for anything else.
And even on the TMOUS, it would be good to put Android and the Apps on internal memory, and have everything else on the storage card, like pics and such.
Main reasons I see for doing this, is once it's working a version that doesn't need to use WinMo can boot faster, and might be able to solve some issues eventually, like not needing a specific file in WinMo or specific ROM just to get calls working correctly.
As well, It gets annoying when even with bootloader it takes longer to boot back up, and I still sometimes get a voicemail or text message while HaRET is loading, and I have to reset, boot windows mobile, remove CLRCAD, reboot, and check the voicemail and texts. If I don't clear it in WinMo, sometimes I get a voicemail message notification every time I boot android even if I don't have any voicemail.
cavemaneca said:
as far as i see it, a major problem is for any non tmous hd2 owners an sd card will always be mandatory. Even if you are able to fit the whole system into the half sized nand, there wouldn't be much room left for anything else.
And even on the tmous, it would be good to put android and the apps on internal memory, and have everything else on the storage card, like pics and such.
Main reasons i see for doing this, is once it's working a version that doesn't need to use winmo can boot faster, and might be able to solve some issues eventually, like not needing a specific file in winmo or specific rom just to get calls working correctly.
As well, it gets annoying when even with bootloader it takes longer to boot back up, and i still sometimes get a voicemail or text message while haret is loading, and i have to reset, boot windows mobile, remove clrcad, reboot, and check the voicemail and texts. If i don't clear it in winmo, sometimes i get a voicemail message notification every time i boot android even if i don't have any voicemail.
Click to expand...
Click to collapse
agreed..then maybe after studying the 1gig version they can find a solution for the 512 version
Battery life isnt great on current builds but it is usable. Much of the issue is due to it being an a sd card. Once they put it on nand, battery life will be even better. As good as winmo? You never know until you try.
I dont get why people are all too ready to rain on someones parade. I say, if there is a possibility of making android boot on this thing, why not try it? WinMo is dying, some of want to jump ship and take our hd2s with us.
It seems that getting nand to run is a priority to devs. Check out the first 7/23 post at http://robsbay.co.uk/
These guys have been making a port much faster than others have anticipated. According to doom-sayers, we shouldnt have been at this point for another few months at least. Im willing to bet this thing will be booting on its own and running efficiently well before the doom-sayers would have expected us to even have this thing running on a sd card.
zarathustrax said:
What's the big deal about flashing it to nand anyways?
Click to expand...
Click to collapse
- Reliability
- Speed
- Battery life.
- Access to memory card as a removable device while Android booted.
Even a class 10 card can't compare to the speed of the internal nand.
Pagnell said:
- Reliability
- Speed
- Battery life.
- Access to memory card as a removable device while Android booted.
Even a class 10 card can't compare to the speed of the internal nand.
Click to expand...
Click to collapse
I completely agree. As others have noted, the main issue is initializing hardware. As an interim step to 100% Android, why not build an extremely slim WinMo with Android cooked into the NAND ROM.
I'm using desire v5 with latest Cotulla zImage it's pretty fast even off of a class 2 microSD. I really think my HD2 would be just as fast as my wife's EVO if the same thing were on the NAND.
nand boot tmous
any tmous user actually copy all of the files over to their phone's memory and try and boot haret? Or would this be detrimental to the life your WM phone?
I am a T-Mobile HD2 user and I think flashing from NAND would have many benefits. Lets do it up.
I am a T-Mobile HD2 use and this is great because we can boot both winmo and android from the nand, which is insane. All the non US users want to shut this down, because they are left out.
Leader2light said:
I am a T-Mobile HD2 use and this is great because we can boot both winmo and android from the nand, which is insane. All the non US users want to shut this down, because they are left out.
Click to expand...
Click to collapse
so have you booted it from the nand with your hd2?
I have not heard of no one posting this problem I am about to post. I hope I can get help with it. The last Standlone android build I used that worked for me was the first one by dan1j3l called LeoFroyo-1.0. I have been trying to test out everyone's android build and for some reason for each build after it creates the data store and I see the boot screen the android screen say's "powering down" and my hd2 automatically shuts off and then i have to turn it back on which then makes it go back to windows mobile. It is annoying to having tried each build and the end result is my device auto- shutting down on me after the boot screen. What should I do to resolve this problem.
This problem reccurs on every single build you use? odd.
and it actually boots into android? past the boot logo/splashscreen?
Hmmm... its most likely not androids fault, make sure youve HSPL'd your device, update your radio ROM to something past 2.08 and throwing on ChuckyROMdroid (as your windows mobile ROM) would perhaps help.
Also, format your SD card to FAT32 BEFORE using any android build, and make sure your battery is charged?
My personal setup is:
HSPL3
ChuckyROMdroid
2.10 radio
ShubCRAFT 1.4c
make sure to run clrcad before HaRet, and that's about as much help as i can give off the top of my head
I have a Tmobile hd 2. It has hard spl on it. Can I go higher than hdspl 1 on my tmobile hd2? I tried the formatting numerous tiimes. I thiught it had to do with something in the startup file. It's just weird how as soon as the boot screen finish loading and I see the android screen interface my device vibrates then it notifies me on the android screen that it is powering down or it just vibrated then power down automatically. It's a real tease.
It is mind-boggling that this single model can cause so many different type combination of problematic behavior, isn't it?
Makes me feel guilty sometimes, that I suffer no serious setbacks running android with my combination so far.
Sent from my HTC Desire using XDA App
Same with me, the so called robot voice, never had it once. And I've been using android from the beginning, also every build have always loaded up for me with no problem.
What battery are you using.. i had the same issue with the official extended battery.. it;'s a known issue if it's that ...
The whole time I have been using the official extended battery. I think when I started using the very first build I had the original battery. I will swap it and see if any there is any change. That is a good point.
There are some workarounds for extended batteries though:
You could ignore the readings from the battery in the kernel
Pro's: No need to swap batteries, able to charge while running android
Cons: Unsafe to charge while running android, inaccurate battery readings if they work at all
http://forum.xda-developers.com/showpost.php?p=7700703&postcount=1
Or you could cover the middle pin of the battery with a little piece of paper or tape
Pro's: Completely safe
Con's: you won't be able to charge under android, you'll have to reinsert the battery and boot windows every time you want to charge, inaccurate battery readings
It worked. Who would have thought the official Htc exteded battery would cause somethng like that to happen. I hope future builds have a way around this problwm. I am suprised nobody posted spmething regarding this. This phone is the best yet but I know having an extended battery is essential to it's longevity use in the day.
extended battery BP-E400 caused the Auto-Shutdown problem
hi guys, I got exactly the same problem you you guys encountering. I accidently swap back the original SLIM battery and the Android Froyo boot smoothly without auto-shutdown. I can somehow confirmed that the auto shutdown is caused by the extended battery BP-E400.
New ROM eliminated Auto-Shutdown problem
try this Android Mdeejay Froyo Sense v2.3 NextSense ROM:
(sorry, the link cannot be posted. Moderator disallowed. But you can google around with the keyword above.)
Works flawless with my extended battery. No more auto-shutdown. YeeHah....
ive been playing around with android a lot recently, but i seem to be getting the same or similar errors with every build. i think the problem comes down to an unformatted memory card. i want to start with a fresh phone and memroy card.
my question is which WM build is best for android? i would be using android as my main os but windows mobile would serve as a'backup' os incase android dies on me. i already have a build of android i want to use so just need some advice on which WM build to use. once i have done that i can format the memory card and re-install android.
not sure if it matters, but i would be using a boot loader to get into android. i have radio 2.15.
matthewharmon102 said:
ive been playing around with android a lot recently, but i seem to be getting the same or similar errors with every build. i think the problem comes down to an unformatted memory card. i want to start with a fresh phone and memroy card.
my question is which WM build is best for android? i would be using android as my main os but windows mobile would serve as a'backup' os incase android dies on me. i already have a build of android i want to use so just need some advice on which WM build to use. once i have done that i can format the memory card and re-install android.
not sure if it matters, but i would be using a boot loader to get into android. i have radio 2.15.
Click to expand...
Click to collapse
I'll try to answer the question by sharing my own experience:
I have T-Mobile US HD2 model and tried several builds under "stock" ROM and Radio 2.08 and most of them worked with really bad battery life. Anyhow, I finally decided to move on with installing Hard SPL 2.08 so I can flash custom ROMs into my device. After that following happened:
1. I tried ChuckyDroid ROM lite - barely occupied any space after boot in WinMo - but did not affect Android and how it worked AT ALL! I had shubcraft 2.0 at the moment;
2. Finally after all the chasing I wanted to have fully functional WinMo Rom and fully functional Android build and here is my setup:
Energy 2.5 GTX WinMo ROM based on 3.14 latest TMOUS Update (with the start button on the top);
Android HyperDroid 1.7 with mychprima's kernel (240 lcd density);
Radio is 2.15.50.xx
Re-formatted 16GB stock SD Card I got with my HD2
Results:
Super-smooth Android operation at all times;
Without SetCPU installed (since kernel is already OCd and UVd) my battery life has been AWESOME! I get constant 3-6mA battery stand-by and that alone gives me really good battery life. I am getting one day and few hours after 1.5hr re-charging - that I did not beat with anything I tried on my hd2 before this setup. I have reseted phone last time several weeks ago and not a single force close message so far (to knock on wood hihi) ... No reason to lie - but if you have some time it may be good combo to try our. BTW I do not offer any guarantees on what you do with your phone lol - that's my "fine print" lol
eenbox said:
I'll try to answer the question by sharing my own experience:
I have T-Mobile US HD2 model and tried several builds under "stock" ROM and Radio 2.08 and most of them worked with really bad battery life. Anyhow, I finally decided to move on with installing Hard SPL 2.08 so I can flash custom ROMs into my device. After that following happened:
1. I tried ChuckyDroid ROM lite - barely occupied any space after boot in WinMo - but did not affect Android and how it worked AT ALL! I had shubcraft 2.0 at the moment;
2. Finally after all the chasing I wanted to have fully functional WinMo Rom and fully functional Android build and here is my setup:
Energy 2.5 GTX WinMo ROM based on 3.14 latest TMOUS Update (with the start button on the top);
Android HyperDroid 1.7 with mychprima's kernel (240 lcd density);
Radio is 2.15.50.xx
Re-formatted 16GB stock SD Card I got with my HD2
Results:
Super-smooth Android operation at all times;
Without SetCPU installed (since kernel is already OCd and UVd) my battery life has been AWESOME! I get constant 3-6mA battery stand-by and that alone gives me really good battery life. I am getting one day and few hours after 1.5hr re-charging - that I did not beat with anything I tried on my hd2 before this setup. I have reseted phone last time several weeks ago and not a single force close message so far (to knock on wood hihi) ... No reason to lie - but if you have some time it may be good combo to try our. BTW I do not offer any guarantees on what you do with your phone lol - that's my "fine print" lol
Click to expand...
Click to collapse
thanks for that, Energy ROMs seem to come up a lot, and as development for my current WM build (CleanEx DSE 6.1) seems to have stopped, il give that a go. im currently getting a lot of force close messages revolving around the sync features. also my HTC calender doesnt work and contact images do not display (I assume because it cant sync them from facebook). im currently using MDJ FroYo Sense Revolution v.1.7 as my android build, but il try your setup. battery life has become a bit of an issue for me, but i am a 'heavy' user.
is it better to format the memory card through WM or through the PC? and should i be setting any options or just leave them at default values?
matthewharmon102 said:
thanks for that, Energy ROMs seem to come up a lot, and as development for my current WM build (CleanEx DSE 6.1) seems to have stopped, il give that a go. im currently getting a lot of force close messages revolving around the sync features. also my HTC calender doesnt work and contact images do not display (I assume because it cant sync them from facebook). im currently using MDJ FroYo Sense Revolution v.1.7 as my android build, but il try your setup. battery life has become a bit of an issue for me, but i am a 'heavy' user.
is it better to format the memory card through WM or through the PC? and should i be setting any options or just leave them at default values?
Click to expand...
Click to collapse
What I did was reformatting under multimedia card reader - I do not think it matters but that's what I did.
I did find some registry tweaks that manages sd card power a while ago and tried them under stock rom and radio - it did not work but I never bothered to go back since my battery is not really getting drained - lasts enough for me.
I only installed BSB Tweaks and disabled EVERYTHING and left only power-saving ON. I have no clue whether this helps at all or not but just did it as a preventive measure ... also, make sure auto-lock is DISABLED under Windows. That was one of the old issues to get un-wake-able screens ... however, so far I have not really had any problems.
Keep in mind: if you want to install many apps that you would like to test - do not do it in massive installations one after another. Some apps are known to screw up battery life and stand-by mAs. Therefore, install couple at the time - after reboot if you get low mA - then app is not draining the battery.
So far I have experienced Extended power widget to drain the battery a lot and also any type of news browsers like e-buzz, pulse, etc - they seem to constantly pull data and remain active. However, they may work for you if you have data disabled for the most part (which is probably not the case) - forgot to mention mine is on 3/3.5G at all times.
- Background Data is checked (ON);
- Auto Sync is unchecked (OFF);
- Brightness disabled under very strong light (110 lumens of my flashlight hihihi) and set on 35-40% I think - somewhere around there.
- I have three home-screens and do not feel I need more
- Weather widget, current widget and google search widget - I do not have any clocks for simple reason - when the phone is locked I can easily see the time by clicking the hardware buttons - so what's the point of the background one ...
If I remember any other tips and tricks I'll let you know.
Ok, im a bit fustrated with this.
i have a Spanish Vodafone HD2, unlocked with proper code, has cotulla HSPL, currently running on a dutty 3.14 based rom with radio 2.15.50,
the thing is after some hours on standbym the phone just decides to not come back out of sleep, and the phone has to be reset (red botton) or pull the battery out,
i´ve used several MicroSD cards, both formated with windows 7 or the panasonic SD formatter (could windows 7 be the issue ? )
my main microSD cards were a Apacer 8GB class 4 card and a sony 8GB class 4 Card, i also have a 16GB class 2 Sandisk to experiment on.
anyways, phone stats
Cotulla HSPL 2.08
tried with artemis, dutty and energie roms
used both mdeejay and hastarin kernels same issue in both.
Using radio 2.15.50
formating the microSD´s using windows formater and panasonic SD formatter using a hama multicard reader
adding andlog from last crash.
thank you in advance for any comment or help.
I'm not an expert but...here goes....which android build did you try? I have great result with mdj's revolution and hd2one build...sleep of death seems to be caused by mt sd card, in my case anyway. Try to have only the android build on the card to see if it makes a different. Also, have you try one of the "lite" android friendly rom?
Aevum said:
Ok, im a bit fustrated with this.
i have a Spanish Vodafone HD2, unlocked with proper code, has cotulla HSPL, currently running on a dutty 3.14 based rom with radio 2.15.50,
the thing is after some hours on standbym the phone just decides to not come back out of sleep, and the phone has to be reset (red botton) or pull the battery out,
i´ve used several MicroSD cards, both formated with windows 7 or the panasonic SD formatter (could windows 7 be the issue ? )
my main microSD cards were a Apacer 8GB class 4 card and a sony 8GB class 4 Card, i also have a 16GB class 2 Sandisk to experiment on.
anyways, phone stats
Cotulla HSPL 2.08
tried with artemis, dutty and energie roms
used both mdeejay and hastarin kernels same issue in both.
Using radio 2.15.50
formating the microSD´s using windows formater and panasonic SD formatter using a hama multicard reader
adding andlog from last crash.
thank you in advance for any comment or help.
Click to expand...
Click to collapse
Following has served me in the past to find and troubleshoot the issue you above list to have:
1. Install BSB Tweaks in WinMo and have Power Saving turned ON but everything else turned OFF... biggest option you want OFF is AUTO-LOCK feature under Windows Mobile. Many people will tell you how this does not matter since WinMo is not loading blah blah - just go ahead and disable this - it will not hurt anything.
2. Under WinMo disable Brightness Automatic option while you have phone sensor under direct strong light bulb and choose manually to have 10-15% - more is not needed in WinMo since you will be using Android.
3. When you get into Android, do the same: disable Auto-brightness under strong light bulb into manual percentage which suits you the best.
4. Another tip is to have G-Sensor tested; this mainly depends on kernels whether they include G-Sensor fix but go ahead and disable it completely. Fors testing purposes I recommend that you test the device under certain option for a few days instead of few minutes.
What conf I have? Energy GTX 2.5 WinMo 3.14 based; Radio 2.15.50.xx; Android HyperDroid 1.7 with mychprima's kernel OCd and UVd; No setCPU is installed nor I am using any of it's profiles naturally. Auto-Killer is set to system default since it came with the Android Buiuld I am using. Never experienced the no-wake-up screen under this setup even with G-Sensor ON.
Hope some of these tips help you at least to figure whether you have good configuration ...
Question: Spanish Vodafone HD2 you said? That means you have HTC HD2 and not T-Mobile US HD2 (more memory, etc) ... If I were you I would check whether that device needs 2.15.51.xx version and not the "50" version...
I´ll try the light sensor thing. but i think theres no 2.15.51 radio,
is that the differance between .50 and .51 radios ? US vs EUR radios ?
Followed instructions.
got SoD after 2 and a half days insted of 12 hours.
New death.
New log,
If anyone can examine it, i would me most thankful.
I also get lot of sod. I have tried more than 10 builds, different kernels, 3 microSD and couple of wm Rom & radio combos. still after various time sod will come. Disabling auto brightness and G-sensor does not help. Are there anyone who can really help for this problem? Is it sdcard problem or kernel? Android is running great and smooth only one problem is SOD.
I've switched from windows to android for my htc hd2 and I've been experiencing a lot of freezing/hanging issues. I had no choice but to pull out my battery to restart my phone a lot of times.
Does anyone encounter the same problem after they change to android? Or is it like this? It's like, when i play a game, it'll hang sometimes. playing music halfway, it'd hang. or even using GPRS and it'll hang. =.= help!
btw, i'm using the SD builds. It doesn't really matter which sd builds cuz i tried quite a few and I'm still getting a lot of hangs randomly here and there.
evilwz said:
I've switched from windows to android for my htc hd2 and I've been experiencing a lot of freezing/hanging issues. I had no choice but to pull out my battery to restart my phone a lot of times.
Does anyone encounter the same problem after they change to android? Or is it like this? It's like, when i play a game, it'll hang sometimes. playing music halfway, it'd hang. or even using GPRS and it'll hang. =.= help!
btw, i'm using the SD builds. It doesn't really matter which sd builds cuz i tried quite a few and I'm still getting a lot of hangs randomly here and there.
Click to expand...
Click to collapse
Care to tell us more ?
Radio?
WM ROM ?
Android ROM version ?
Hi, I've been experiencing the same problems. I'm booting android through WM 6.5 through the SD card method. I've tried the AmericanAndroid (http://forum.xda-developers.com/showthread.php?t=957652), a HTC sense ROM (http://forum.xda-developers.com/showthread.php?t=954030), a MIUI ROM (http://forum.xda-developers.com/showthread.php?t=1058809) and Darkstone's superRAM froyo. They all tend to crash randomly after a while, and there's no way to solve the problem but pull out the battery... One reason suggested on the forums was that hot weather tends to make the HD2 overheat and crash, which makes some sense because I live in Singapore (that's tropical, btw). But my WM6.5 doesn't crash nearly as often...
O another thing: whenever I boot into android through SD, I tend to get high battery drains of about 60mA. One solution I've found was to shut down the phone, then hold the volume down button while booting in WM6.5. This brings me into a multi coloured screen (is it called the bootloader or something?), and I pull out the battery. After which I boot into WM6.5 normally and boot android from the SD card. That normally brings down the battery drain to about 10mA, but I'm not sure how this works/why it works that way/what side effects this may have... Besides this I follow all the standard procedures, so I'm not sure why android crashes on me so often...
Flash NAND Android ROM and all your troubles will disappear.
Please ensure rom you flashed is the appropriate one. Check ur devicd model, choose rom for ur device, read faq/explanation from chef who built thd rom. Check recovery partition required for your choosed rom. Yesss flash nand rom and flash into ur nand. If u prefer sd rom ensure ur sdcard is in good condition
Sent from my HTC Incredible S using XDA App
likewei92 said:
Hi, I've been experiencing the same problems. I'm booting android through WM 6.5 through the SD card method. I've tried the AmericanAndroid (http://forum.xda-developers.com/showthread.php?t=957652), a HTC sense ROM (http://forum.xda-developers.com/showthread.php?t=954030), a MIUI ROM (http://forum.xda-developers.com/showthread.php?t=1058809) and Darkstone's superRAM froyo. They all tend to crash randomly after a while, and there's no way to solve the problem but pull out the battery... One reason suggested on the forums was that hot weather tends to make the HD2 overheat and crash, which makes some sense because I live in Singapore (that's tropical, btw). But my WM6.5 doesn't crash nearly as often...
O another thing: whenever I boot into android through SD, I tend to get high battery drains of about 60mA. One solution I've found was to shut down the phone, then hold the volume down button while booting in WM6.5. This brings me into a multi coloured screen (is it called the bootloader or something?), and I pull out the battery. After which I boot into WM6.5 normally and boot android from the SD card. That normally brings down the battery drain to about 10mA, but I'm not sure how this works/why it works that way/what side effects this may have... Besides this I follow all the standard procedures, so I'm not sure why android crashes on me so often...
Click to expand...
Click to collapse
hi,
1. try booting into WM6.5 stock rom, w/o any modifications. you should be able to download through the htc website
2. try using WM6.5 a while, see if it hangs/restarts itself. there shouldn't be the case if you're using stock rom.
3. if you still face the restarting/freezing problems even using stock WM6.5 rom. send your phone for servicing.
As my warranty was still valid, i sent my phone for servicing and they changed the whole motherboard of my HD2. Now my phone is running smoothly on both WM6.5 and Android.
The service that HTC offers in Singapore is quite good. You can call them to come to your house and collect the phone personally. If you need, you can ask for a loan phone. They'll repair and return your phone to your doorstep in about a week's time. I'm pretty happy with their efficient service Tell me which company will come and collect your phone at your doorstep and send it back to you when it's all good. Thumbs up all the way for them!
Hope this helps.
Thanks for the replies. I switched to NAND with hyperdroid by pongster, but the crashing persisted for a while. It seems that the connection between the SD card and the phone is the problem. There was once that I got ~60mA of battery drain, then I pulled out the SD card and the drain went down to ~10mA (I was running on NAND of course). I then went on to try a difference SD card (a 4GB sandisk), and the the HD2 stopped crashing. It has also never crashed with the SD card removed. Moral of the story: a very stable SD connection is essential if you want to use SD builds...