Database Users

Let's face it: HD2 has many problems.

No need to hide. This phone has many problems, still many people seems to ignore them completely. No need to start the "It's your phone, it's strange, I use it a lot and it never happens" saga. The problems are there. And for everyone. The fact you don't notice some bad behaviours doesn't mean the phone is perfect or that your baby is exempt from problems. Let's start:
1) Suboptimal WI-FI performance. On a 802.11g wireless network, connected to an 8Mbps internet connection, the phone can't even saturate the badwidth of the network. Speedtest.net reports an approximate 2Mbps download capacity (EDIT for those who cannot distinguish: 2 megabits, not megabytes). Test it yourself: try to download something from a fast website and try to figure out which is your maximum download transfer speed. You will be disappointed. As a comparative, this means the phone can use 1/4 of the available bandwidth. A SonyEricsson Satio can fully use the available bandwidth, instead (someone told me "tell me a phone that can do it. Now you have one).
2) Stanby freeze: it's there. The phone freezes randomly while in stanby draining all your battery juice. Sometimes happens rarely, sometimes happens frequently.
3) Poor memory space handling: after just 20 days of use from a fresh ROM update, my free memory space on ROM is just 36MB. Without installing big things or hacking anything. Sure, there are fixes produced by the community, log cleaners, temp files deletion utilities, etc. etc. Still, it's a quite a disappointement: it means this phone can't work properly in a "factory state" for much time.
4) "Always on" features: nice, apart the fact in random periods of time the services just stop to download data. The Twitter client doesn't work well. Sometimes you can hear a tweet sound, sometimes it downloads data without the sound, sometimes it downloads nothing until reboot.
5) Poor stability in general: the OS crashes frequently. Less frequently than the first shipped rom. Still it's not very stable.
6) Poor support in general with the updates: finally the SMS stuck problem has been fixed but they spent 3 months for it without a valid solution. The camera fix doesn't hide the fact the sensor is defective.
I don't say this to start a flame, of course, but only because I'm frustrated with these problems. And people, instead of spreading words about them, just pump the hype, including some notorious web sites that have no scope but pushing the hype even further. But the truth is another: this phone doesn't work as expected.

I honestly do not have the problems you're describing..
Your "truth" is very different from mine, but ne1 is allowed to have no

Can't comment on all those, but i hear you, defo had some of them and i'm on my 2nd unit after 2 weeks.
With Nokia it took them at least 6 months to iron out the flaws in their released phones, defo the case with N95 & N96, i didn't expect it to be the case on this phone.
SMS fix? is it? or only in 1.66, because the hotfix's don't work on the 1.44 ROM
I would like to add the Audiobooster problem to that list

well, I don't pretend mine is perfect but there are more things to love than to hate about it. regarding the problems, I think you cannot generalize because I've never experienced some of your issues but I'm bothered by other myself. finally I guess it's just a subjective call anyway...

I had some of your problems when my HD2 was on the original 1.48 WWE Hong Kong ROM. However, since I flashed HSPL, Merlion LEO V1.90 ROM and Radio version 2.07.50.27_2, it's been faster and absolutely stable. No more freezing/"Sleep of Death"/etc...

jonbaker76 said:
I would like to add the Audiobooster problem to that list
Click to expand...
Click to collapse
That one really annoys me too. Still can't find a way to get video and audio in sync without manually adjusting the offset whilst encoding. And HTC still can't get the hang of getting Audiomanager to handle AAC files properly (ie sort albums in track order, or show.their album art). Still, it's a lot quicker than my Touch Pro was ; )

Yeap! I'm very happy that I could be refunded. Too many bugs for such a device.

^
If you want something that works out the box, get an iPhone

I have none of your issues and i can prove it with tests and videos.
I wish i had an "unlike" button to use it here. You are frustrated because either you don't know how to work with this phone or you have some bad software or even a bad phone. Replace it!
You are emitting false statements here!
PS: I have the phone for 2 months.

I'd love to see a phone or device that was perfect.
Every piece of hardware has its own problems.

I've been waiting for so long for someone to start a thread entitled as "Let's face it: HD2 has many problems". Eagerly watching this thread for some positive and negative input.
All in all, HTC Sense is at it infant stage. This "is" the culprit. Perhaps by end of this year, we will worship it someday...
To the developer/creator of HTC Sense, please use your common "sense" when trying to convince people to buy your idea. The first major mistake was SMS failure. Totally non-Sense.

1. have to say the WiFi (at work) is slow (2.2Mbps) but speedtest.net is SO unreliable I'll hold off commenting until I try at home tonight on my O2 LLU connection.
2. never had it
3. doesn't happen to me, currently got 107MB free of storage and 266MB of program memory free
4. other than Twitter client being a bit crap it's fine
5. mine doesn't crash
6. updates are fine but I've not had any of the issues others have had in the first place, less so now running a custom ROM

Return your phone and get an iphone/android device.
This kind of issues, even if I haven't myself had most of those you list, have been around with EVERY WM phone that has been made.
Of course WM is far from perfect, but as someone already said to me the advantages far outweigh them, and I can live with them and the need for tweaking.
1) Wifi speed, show me one phone that can transfer at full G speed. The processing power/memory bandwidth/flash memors speed can't handle that.
It also depends a LOT of the software used.
I do get 1-1.5MB/s (8-12Mbps) transfer on wifi between the HD2 and one of my home computers, with WiFi remote access, and on balanced wifi performance. With Resco explorer, I get 150kB/s...
2) Never had one.
3) Depends... could be just normal, now that the album and browser caches have reached their limits, and would stop there. Stock ROM has a lot of useless stuff on it.
etc...

dgtel2 said:
To the developer/creator of HTC Sense, please use your common "sense" when trying to convince people to buy your idea. The first major mistake was SMS failure. Totally non-Sense.
Click to expand...
Click to collapse
Sense is fine, but the vanilla Win6.5 fails hard.
And if this thread gets to about page 5, it would probably just turn into another Leo vs iPhone flame war.

For the WiFi "problem": ~ 2 MByte /s is just the normal average speed, even with my laptop I won't get much more on 802.11g .. It also depends on with how many other devices you share your WiFi-channel.

btyeh said:
Sense is fine, but the manilla Win6.5 fails hard.
Click to expand...
Click to collapse
What is manila win6.5?!?! Do you even know what manila is? manila = sense!!!

I think there are a lot of 'duff' units, this must be the case with the 'sleep of death' and the crackley call as many of had it but most don't.
I took mine back, got a new one yesterday, no crackles no sleep of death... yet
But true, there are always gonna be problems, it will take months before a near perfect firmware, sorry, rom is out

Thank god for my HTC HD2. No problem here beside the screen shaking. But I hardly notice it.

kilrah said:
1) Wifi speed, show me one phone that can transfer at full G speed. The processing power/memory bandwidth/flash memors speed can't handle that.
It also depends a LOT of the software used.
I do get 1-1.5MB/s (8-12Mbps) transfer on wifi between the HD2 and one of my home computers, with WiFi remote access, and on balanced wifi performance. With Resco explorer, I get 150kB/s...
Click to expand...
Click to collapse
SonyEricsson Satio, for example. I download at 900Kb/s with it on the same network (using the same browser, Opera Mobile 10 Beta 3). Poor implementations doesn't mean it's not possible. Do we need 4Ghz quad core processors to use a wireless g network? Obviously not.
3) Depends... could be just normal, now that the album and browser caches have reached their limits, and would stop there. Stock ROM has a lot of useless stuff on it.
etc...
Click to expand...
Click to collapse
A bad behaviour, even when happens at factory settings is still a bad behaviour. You have a strange definition of "normal". Surely a phone that in 20 days saturate all the available space on the rom cannot be considered "normal". It's a poor implementation of things. A good implementation would have addressed it from the start by allowing the user WHERE to store that files or giving him an option to clear that files without an hard reset. No, it's not normal. Software design it's a much more complicated thing than those "normal" things.

You know you have problems when your best programs are Hd2tweaks, Bsbtweaks and Resco registry editor. And you are continually wiping out your system and trying new roms. Although Xannytech evolution was a good one.

Bad battery life is typically not because of the hardware

Hi,
I'm posting this in return for all the information I found about the HD2 and poor battery performance. I read every thread I could find and every single post in them. I learned a lot and that allowed me to solve my problem.
I got no more than about 10 hours of use out of my battery with average use. Initially I thought this was the norm, reading a number of threads on this issue. I could however not believe that the performance was so poor, even taking the large screen into account.
I decided to try and determine exactly what it was that caused the battery to drain to quickly. I loaded BattLog and found it invaluable (see http://forum.xda-developers.com/showthread.php?t=444920).
I immediately noticed that my phone was drawing 85 mA even when it was in standby (or what I thought was standby). Based on what I was reading, the current draw should not be more than 5 mA while the phone is in standby.
I noticed in one of the threads that there were complaints about G-Profile causing battery drain. Since I had it on my phone I thought that might be a logical place to look. I uninstalled it a lo and behold... the current draw fell to below 5 mA when the phone was in standby!
In addition I loaded Bandswitch which switches off my 3G connection after it has not been used for 60 seconds.
Now I have about 48+ hours of battery life. When not using the phone a lot it extends to a lot more than 48 hours.
The long and short of it is that if you get poor battery performance, chances are it is because of some software that is installed on your phone.
Here are a couple of usefull things I have found in helping resolve my battery issues:
1) Use Batlog (http://forum.xda-developers.com/showthread.php?t=444920) to log the current your phone draws. If it draws more than 5 mA during standby you have a problem, most probably related to a piece of software on your phone
2) Your phone should not be drawing much more than about 150 mA when in 'active' mode with the screen at 40% brightness.
3) If you are running G-Profile, uninstall it and recheck your current draw. Chances are that it is the culprit.
4) Having an active data connection does draw power from the battery. In my case this is about an additional 130 mA. Load something like Bandswitch to disable the data connection when it is not needed.
I hope this information helps somebody. I realise that the situation is different for everybody out there because of all the variants such as age of the battery, sofware loaded and use. However, the reality is that the battery issues are most probably not because of a bad battery or the hardware but rather because of software on the phone.
BTW I am running:
OS Version: 5.2.21869
Manilla version: 2.5.19211619.0
ROM version: 1.48.421.2 (71294) WWE
Radio version: 2.05.51.05_2
Regards

gerhardvr said:
Hi,
I'm posting this in return for all the information I found about the HD2 and poor battery performance. I read every thread I could find and every single post in them. I learned a lot and that allowed me to solve my problem.
I got no more than about 10 hours of use out of my battery with average use. Initially I thought this was the norm, reading a number of threads on this issue. I could however not believe that the performance was so poor, even taking the large screen into account.
I decided to try and determine exactly what it was that caused the battery to drain to quickly. I loaded BattLog and found it invaluable.
I immediately noticed that my phone was drawing 85 mA even when it was in standby (or what I thought was standby). Based on what I was reading, the current draw should not be more than 5 mA while the phone is in standby.
I noticed in one of the threads that there were complaints about G-Profile causing battery drain. Since I had it on my phone I thought that might be a logical place to look. I uninstalled it a lo and behold... the current draw fell to below 5 mA when the phone was in standby!
In addition I loaded Bandswitch which switches off my 3G connection after it has not been used for 60 seconds.
Now I have about 48+ hours of battery life. When not using the phone a lot it extends to a lot more than 48 hours.
The long and short of it is that if you get poor battery performance, chances are it is because of some software that is installed on your phone.
Here are a couple of usefull things I have found in helping resolve my battery issues:
1) Use Batlog to log the current your phone draws. If it draws more than 5 mA during standby you have a problem, most probably related to a piece of software on your phone
2) Your phone should not be drawing much more than about 150 mA when in 'active' mode with the screen at 40% brightness.
3) If you are running G-Profile, uninstall it and recheck your current draw. Chances are that it is the culprit.
4) Having an active data connection does draw power from the battery. In my case this is about an additional 130 mA. Load something like Bandswitch to disable the data connection when it is not needed.
I hope this information helps somebody. I realise that the situation is different for everybody out there because of all the variants such as age of the battery, sofware loaded and use. However, the reality is that the battery issues are most probably not because of a bad battery or the hardware but rather because of software on the phone.
BTW I am running:
OS Version: 5.2.21869
Manilla version: 2.5.19211619.0
ROM version: 1.48.421.2 (71294) WWE
Radio version: 2.05.51.05_2
Regards
Click to expand...
Click to collapse
and imagine that your rom version is accused of massive batt draining!
an upgrade to 1.66 / 1.72 should make a difference..or a custom rom

batlog?
Hi Gerhardvr,
What is the batlog software you used?
I'm very interested about your post.
Thanks.
J6B.

Very useful findings, gerhardvr. Thanks!

found BattLog
ok, I found BattLog
It's just in showthread.php?t=444920
Have a nice day guys.
cu
J6B.

When I ran the Test, it said that I was using up 242mA in standby! I dont believe I have G-Profile installed, unless it was pre installed on the device. I have the latest versions of the ROM, Radio, Manila, and OS version, so I know the culprit cant be the ROM version... Any ideas? I bought this phone from T-Mobile US.... Sooo yeah

Folks, I've been trying to get to the bottom of this as well. I have a number of cab files which do seem to help a little. One of the bigest culprits I've found is the screen lockers. Disable them and see how you fair!

soopahsteve said:
When I ran the Test, it said that I was using up 242mA in standby! I dont believe I have G-Profile installed, unless it was pre installed on the device. I have the latest versions of the ROM, Radio, Manila, and OS version, so I know the culprit cant be the ROM version... Any ideas? I bought this phone from T-Mobile US.... Sooo yeah
Click to expand...
Click to collapse
Soopahsteve,
I suggest you use Battlog to log to file. This is very useful as it will log the time stamp, the current temp of the battery and the current draw at the point in time. In addition it logs arious events on the phone, in particular the startup and shut down of applications, data connectivity, when you make or receive a call, whether you are talking or receiving on the call, etc. This can be opened in Excel and then analysed and if you are very lucky, you will pick up some patterns allowing you to link some programs to the battery drain.
However, the situation is typically slightly more complex to resolve since the culprit software are usually software that is loaded as TSR application at reboot. The result of this is that Battlog will not show the startup of these applications in the log file since they are already running at the time you are starting Battlog.
You should look at programs that manage phone profiles, screen lockers, screen calls or SMS messages, etc. In other words, any program that does work behind the scenes.
The reason you are seeing 242 mA in "standby" is because your phone is not really in standby. Although the screen is blank, something is preventing your phone from going into true standby, the processor is still active. The trick is to find what this is.
Sometimes the only approach is to uninstall the applications you suspect one by one and see if it makes a difference until you either find the culprit or can prove that none of the them are an issue. Then reinstall the ones you think are "safe" one by one and check whether the probelm pops up again. unfortunately you have to do the double sided approach because there could be more than one application that cuases your issue.
Painful I know but worh it when you have two days worth of battery time with some to spare.
Regards

See no reason to upgrade to the latest ROM
chris2busy said:
and imagine that your rom version is accused of massive batt draining!
an upgrade to 1.66 / 1.72 should make a difference..or a custom rom
Click to expand...
Click to collapse
You know it. In reality I would love to upgrade to the latest and greatest but I've customised my phone to the Nth degree (did obviously not upgrade the ROM) by installing all the little apps I find useful, Cookies Home tab (best thing since sliced bread), etc. My phone is now just the way I like it.
It would take me quite some time to upgrade the ROM and to customise it again from scratch and I really don't see the benefit. I might be force to do it when I get to a stage where there are software that I would like to load that only works on the later ROMs but until such time I'm not gonna try to fix that that ain't broke.
Regards

is this the bandswitch u are using? if not, can i check where to get the program?
http://forum.xda-developers.com/showthread.php?t=286844

gerhardvr said:
It would take me quite some time to upgrade the ROM and to customise it again from scratch
Click to expand...
Click to collapse
I just upgraded my ROM and did a Level 1 restore with Sprite Backup ... everything comes back except (I think) for wifi passwords.

i am drawing 180mA on standby..
im using custom rom, energy rom so thats very strange, but i have to agree that my battery life is terrible.. so i got to find a way to cut down on the 180mA drain..

I've always had good battery life on stock 1.66 rom losing 3% overnight with wifi and bluetooth turned off. Had to do a hard reset and started losing 15% overnight with the same everything. Did further resets and got nowhere. Ended up giving up on 1.66 although it had been fine previously after numerous hard resets - makes no sense but this is what happened. Just flashed to 1.72 and back to losing 3% overnight what it should be. And that is out of the box, to be honest all the battery saving registry tweaks are not worth the time installing and I leave 3G on all the time with updates coming through.
So it's all a bit random and shame on HTC for not sorting it out. My advice is do a hard reset, switch the wifi and bluetooth off and see in the morning if you have a reasonable battery life (or use the batt consumption program to verify standby consumption is sensible). Do this first before installing everything, getting frustrated and starting over again like I did when you discover that you're still experiencing high battery drain. This ensures that your starting point is a good flash and the phone is getting good life before adding any apps that could be causing a problem.

i have found my hd2 really does not like being in a poor or no coverage area. other phones i've owned have normally coped pretty well with no or very little signal. but not the hd2.
also noticed more drain in areas where there is only poor 3g coverage and its switching between 'g' and 'h' coverage.

fi3ry_icy said:
i am drawing 180mA on standby..
im using custom rom, energy rom so thats very strange, but i have to agree that my battery life is terrible.. so i got to find a way to cut down on the 180mA drain..
Click to expand...
Click to collapse
Energy ROMs, just like the name goes, use a lot of Energy
They are baked in with a lot of performance tweaks so it's not unusual to get lower battery life per charge compared to other more down to earth vanilla ROMs.

Thanks for this thread, a lot of interesting information about the battery life of my HD2.
Just to mention: battconfig shows the power consumption directly in the task bar, a good way to find power guzzlers while they are active.
It's a pity we have no central place in this forum with a list of background applications that are known to drain the battery faster.
Or, also a needed information, a list of applications that are known not to do this (like PhoneAlarm, PocketShield).

I'm using the official rom only and have non fancy apps running or installed while I'm using the test bat program. As I speak the SD card is removed and celular radio is turned off.
Acording to program there is an indicator which is switching from -229ma to +78ma is that what its drawing of power?

Euroman28 said:
Acording to program there is an indicator which is switching from -229ma to +78ma is that what its drawing of power?
Click to expand...
Click to collapse
+78ma??? That must mean you are charging the battery. The best way to test current draw is when it is only on the battery.
I get about -5ma draw on standby and it tops out at around 180ma when I have the screen on, but usually hovers around 130 - 150ma. I have my screen brightness at the lowest setting possible.
@OP, I wanted to say this earlier... great topic, very insightful.
I have a few suggestions for everyone posting in this thread. Let's try and get some common data together that is more tangible in order to give us a more similar & common perspective for these discussions.
I suggest the following
1) Soft Reset. Once the device is on, do not run ANY applications. In fact don't do anything except for following the below instructions.
2) Turn your screen brightness all the way DOWN! (Turn off Auto Backlight and manually set it to the lowest setting)
3) Check your power settings and make sure that while your phone is on battery, that it is set to dim the backlight after 30 seconds and turn off after 1 minute
*** I have attached 2 REG files below for both Backlight and Power. Please use them instad of doing it manually.***
4) Turn off all the radios (Phone, Wi-Fi, Bluetooth). Let's make our first round of tests with the Radio's off. Radio ON complicates things a bit as there are several applications to keep track of that use the Data Connection. I'll come up with a more comphrehensive list later so we can do the Radio ON tests.
Screenshots
Use a program like Shave&Save and get the following screenshots
1) Use any Task manager and get a screenshot of all the processes running. Sometimes the number of processes displayed is longer than the screen size can accomodate. Take 2 screenshots in this case making sure that you capture all processes. Edit the image with MS Paint or some other Image Program and attach it here as one image. See the example in the post below this one.
2) Goto \Windows\Startup and get a screenshot of the folder contents
3) If you are using Sense, drag the slider all the way to the end (settings) and goto About Phone. Goto Software Information and get a screenshot of that.
Monitoring the Battery
1) Make sure your phone is not connected to the charger or to the computer.
2) Open BattLog (can be found here), set the refresh rate to 1 second and Start Logging.
3) After you start the logging process do not touch the screen / the phone again for exactly 2 minutes.
TIME THIS with a stop watch. As soon as the 2 minutes it complete, turn the phone back on and stop the logging.
Information to post here
1) All the screenshots from above.
2) The current draw (both on standby and while active). Also, please attach the file that logged all the information in this format: Forum ID - BattLog - dd-mmm-yy.txt
3) ROM - Whose ROM? Release Date? Does it have Cookie's Home Tab Installed or any other MAJOR Sense Modifications.
Click to expand...
Click to collapse

SAMPLE POST
HTC HD2 (T8585)
OS: WM 6.5
ROM: Energy * Build 21907 * Release 01.JULY.10 * CHT v1.8.5 - Dinik Edition
RADIO: 2.07.50.27_2
Current Draw (mA)
Idle: -3 to -7
Screen On (w/o Radios): -83 to -117

Those figures look normal to me. You should be getting about as good a battery life as a device like this can achieve.

[Q] Phone signal

I've installed Android on NAND and am very impressed as everything seems visually better suited to the new format. I'm even happier now Copilot is working. However, I don't understand the signal bars properly. On WM I understand if I have 3G+ or at least a good signal. The signal bar in Android never looks particularly healthy although ironically as I type it is showing full bars with a 'G' beside it (I've just turned off wireless and the G appeared, this is presumably how data transfer is configured). Is there any reason why the signal might not be so good running Android instead of WM? Is there any way of improving the signal? Ultimately I need the thing to be a phone!
The Android I'm running is for Desire - whatever is linked to in the 'NAND for noobs' thread.

Trying flashing different radios. Search up our HD2 radio thread, and you'll see. Also, follow the requirements meant for your device to run android. Meaning don't flash a radio lower than 2.08 for EU HD2, for a TMOUS HD2, i'm not sure.

I used the latest (biggest number) radio before I put Android on - does flashing Android change the radio and in any case how do I find out what radio version I currently have?

Latest sure isn't always best when it comes to radios. You can check your radio in bootloader, or in android/settings/about phone, somewhere at the bottom
Flashing Android does not change your radio.

Stock Android uses 4 bars for signal while Sense ROMS use 6. I'm not sure how it equates between the ROMs but I can assure you there is no loss of signal.

First off, ignore the suggestions about updating your radio. You said that your signal appears weaker under Android than WM, so it's obviously not the radio as installing Android does not affect that.
All I can really say is that you may want to just ignore the signal bars and judge it by call quality. It may be that the build you are using is not reflecting the signal strength correctly. That's more likely than you actually having a weaker signal in a different OS since the OS has nothing to do with it!
Just see how you get on with it and if there is a problem then that's a different matter.

OK I don't seem to have any real issues with signal.
BUT (running Android NAND Desire Rom of some sort) after a few days a few problems:
1. The phone seems reluctant to charge in the car cradle if the charge level is low
2. Sometimes freezes in Copilot and needs battery removing to re start
3. Battery usage much more severe than WM
4. Lots of minor wobbles that I can't think of now I am typing.
The upshot is that I would now like a Desire HD but am thinking of going back to WM6.5 on the HD2 purely for reliability.

800jimbo said:
OK I don't seem to have any real issues with signal.
BUT (running Android NAND Desire Rom of some sort) after a few days a few problems:
1. The phone seems reluctant to charge in the car cradle if the charge level is low
2. Sometimes freezes in Copilot and needs battery removing to re start
3. Battery usage much more severe than WM
4. Lots of minor wobbles that I can't think of now I am typing.
The upshot is that I would now like a Desire HD but am thinking of going back to WM6.5 on the HD2 purely for reliability.
Click to expand...
Click to collapse
Well every build will have some minor hick up... Try different builds, there are plenty of build which have everything working and also the battery life is at par with win6.5

jalshah05 said:
Well every build will have some minor hick up... Try different builds, there are plenty of build which have everything working and also the battery life is at par with win6.5
Click to expand...
Click to collapse
Can you point me to one? There are an overwhelming number available and I simply don't know how to judge one against the other

800jimbo said:
Can you point me to one? There are an overwhelming number available and I simply don't know how to judge one against the other
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=877777 is a good one... Try mdeejay's builds... they are good ones... There are also other good and better ones out there. But I like his better.
Also read this post:- http://forum.xda-developers.com/showthread.php?t=929324

my signal bars go up and down all the time in droid

why is dead battery causing so much issues on custom roms?

original roms dont seem to suffer from these issues.
every custom rom i tried(nand and SD) had same issues after battery went dead.
isnt there a safety shutdown feature that can be added to prevent this?

Nand roms shouldn't be so bad, I have run my battery dead a bunch of times on my phone with UD 3.0.0 RC1, and never has it caused a problem. But running the battery dead on an SD build is where you can get big problems, because the entire system loads from the SD card, and by letting the battery run dead, Android doesn't get a chance to unload properly, as the card is still being written to when shutdown takes place, alot of the time corrupting the sd card or the Android directory or the data.img
Sent from my HTC HD2 using XDA App

The issue isnt the ROMs, its a MAGLDR bug. Phone cant charge under magldr.
Workaround: Boot into MAGLDR and then into CWM. Charges under CWM.
OR
Change from MAGLDR to CLK
Andy

Boradan said:
The issue isnt the ROMs, its a MAGLDR bug. Phone cant charge under magldr.
Workaround: Boot into MAGLDR and then into CWM. Charges under CWM.
OR
Change from MAGLDR to CLK
Andy
Click to expand...
Click to collapse
Wasn't the question...
Anyway, some apps store data on the sd card, when it shuts down suddenly due to empty battery, this data can get corrupted (That's why most roms don't use DATA2Ext but App2SD+, to prevent this). That's why most (if not, all) NAND Roms don't have this issue (at least, It never occurred to me) but SD roms do, as huggs explained.

isnt it possible to make an app that shuts off the phone i nstead of letting it die?

I use an ext4 with DarkTremor's A2SD script and never had corruption from running out of battery. I could just be lucky, idk.
Sent from my HTC HD2 using XDA App

man this is BS it has to be plugged inconstantly in order to keep it alive its like my sony laptop with a 2.4 ghz pentium processor and bigass screen.
the battery only lasted 3 hours.
i go to work and leave the phone untouched for the whole day the battery goes to half thats the ONLY way i can make it last till the end of work day.
if i even think about txting or writing an email or god forbid browse internet that **** drops to almost dead batery instantly.
and sometimes i dont have a charger so the phone dies because it cant shut down on its own.
and to add to that theres a GREAT!!!!! feature that conveniently turns the screen on and turns off all the power saving features such as dim screen.
so it turns the phone on starts buzzing and screen on full brightness, to let me know that my battery is dying WTF really???

fuzzysig said:
man this is BS it has to be plugged inconstantly in order to keep it alive its like my sony laptop with a 2.4 ghz pentium processor and bigass screen.
the battery only lasted 3 hours.
i go to work and leave the phone untouched for the whole day the battery goes to half thats the ONLY way i can make it last till the end of work day.
if i even think about txting or writing an email or god forbid browse internet that **** drops to almost dead batery instantly.
and sometimes i dont have a charger so the phone dies because it cant shut down on its own.
and to add to that theres a GREAT!!!!! feature that conveniently turns the screen on and turns off all the power saving features such as dim screen.
so it turns the phone on starts buzzing and screen on full brightness, to let me know that my battery is dying WTF really???
Click to expand...
Click to collapse
We at XDA made Android available for an aging phone of yours at *NO COST* involved, If you have a problem live with it until we learn how to fix it. And if this seems too unbearable, just STFU and stay with HTC stock WM6.5 rom.

if you make a ruler you make it exact.
even if you give it away for free.
you dont make a ruler that measures 1 inch short...because people depend on it.
i just hate all these BS claims about the system beeing stable when its not even close.
i installed android because i thought it was ok for everyday use by someone that doesnt sit here on this board for hours trying to keep up to speed with all the latest updates.
im very happy that this android development extended the life of a factory crippled phone but dont tell me that im the only one having this issue.
u have no idea how many times this thing freezes up right when i need it. when im in the car driving and need to use google maps but cant because this **** is bugging out.
or now for example it doesnt even load up sense it gives me the com.htc.bgp force close.
im very fn tired of this loading and unloading of cooked roms and actually looking for a phone that came with android.
like i said if you make something, EVEN IF ITS FREE, you are still responsible for making it work because people depend on it. and i dont have 2-3 hours a day to spend reading through this board trying to make my phone work again.
you can hate me or disagree i dont give a faq this is my opinion.

fuzzysig said:
if you make a ruler you make it exact.
even if you give it away for free.
you dont make a ruler that measures 1 inch short...because people depend on it.
i just hate all these BS claims about the system beeing stable when its not even close.
i installed android because i thought it was ok for everyday use by someone that doesnt sit here on this board for hours trying to keep up to speed with all the latest updates.
im very happy that this android development extended the life of a factory crippled phone but dont tell me that im the only one having this issue.
u have no idea how many times this thing freezes up right when i need it. when im in the car driving and need to use google maps but cant because this **** is bugging out.
or now for example it doesnt even load up sense it gives me the com.htc.bgp force close.
im very fn tired of this loading and unloading of cooked roms and actually looking for a phone that came with android.
like i said if you make something, EVEN IF ITS FREE, you are still responsible for making it work because people depend on it. and i dont have 2-3 hours a day to spend reading through this board trying to make my phone work again.
you can hate me or disagree i dont give a faq this is my opinion.
Click to expand...
Click to collapse
Wow, you're an ungrateful bastard (to quote the 'you are a noob on XDA Developers video) IMO. How can you not appreciate what the Devs here are doing? They put in hours and hours of work, and you still don't appreciate how brilliant it has made the HD2?! Please, make us a perfect ROM, and share it with us, so that you can show us your perfect skills. Don't you read up on the issues of each ROM before flashing it?
Also, the system is EXTREMELY stable. My CM7 HD2 is far faster than my friend's DesHD. I get better battery life and it's just faster in general. You should really be more appreciative of the hard work of the brilliant devs here and also, before accusing people of BS and lying, think about whether it may be a problem with you.
Please, give your HD2 to someone with the mental capability to use it.

fuzzysig said:
the battery only lasted 3 hours.
...
if i even think about txting or writing an email or god forbid browse internet that **** drops to almost dead batery instantly.
Click to expand...
Click to collapse
fuzzysig said:
u have no idea how many times this thing freezes up right when i need it.
Click to expand...
Click to collapse
faulty phone/battery.

yea thats what comcast says every time i make a trouble call
oh ur modem is bad... only to find out that their network has problems again and again.
my battery is fine and so is the phone.
it worked without a hitch for 4-5 months untill battery died first time. since then the problems just been piling up.
and finally today it wouldnt even show the home screen.
so again for the 4th time i lost all my new contacts and whatever information i had on it because it cant shut down properly when its dead.
im picking up an htc sensation that has android already on it so i dont have to deal with this bs no more.
and **** you MR public defender i never said i hate the developers and in any way ungratefull. i was trying to figure out how to deal with this problem untill people started accusing me of beeing ungratefull.
i know what it takes to make this work and have alot of respect for people that do it. but you put urself in my shoes maybe for a second.
i have my office on this phone and whenver it doesnt work i cant do **** anymore.
i had txt messages, notes, phone numbers etc saved here that i wasnt able to recover and had to reset my phone in order to make it work again.
spent 5 hours trying to make it work since yesterday so now tell me how the faq am i supposed to feel after dealing with this crap.
i switched to this phone because everyone claims its STABLE. yea stable untill your battery dies and then **** starts happening...
i went through 6 different roms that means every time i have to spend hours setting my customizations etc and saving the data that i have on it.
how convenient is that.
beeing faster doesnt mean its more stable btw...

[A] What REALLY improves Android battery life on the HD2

Thought I'd just share this. I had been stuck with this issue for a while; basically needing to fully recharge twice a day. I tried a lot of things recommended on here and elsewhere; all of them either made minor differences, none at all, and some made things worse. Things in that category are wifi, 3g, bluetooth, gps, setcpu, task-killers, screen-dimming, resetting battery stats, starting Haret with the key lights on, etc. All these things can potentially make a difference, but didn't help much. Plus, most of them involve de-smart-ing a smartphone, and what's the point of that? I tried changing SD card, as I have a 16GB Transend class 6 card which I believe draws a few more mW than e.g. Sandisk cards, and that didn't really help either.
As an indicative measure, I could charge to 100% (and green LED) at 11pm, put the phone into Airplane mode (GPS off as well), kill all tasks that are not needed, go to bed, and by 7am the battery was on around 50%. So that's with NO comms, NO screen, nothing. Android battery use showed most of this usage was the screen. Er, no. I installed CurrentWidgit (from App Market) and got it to log; during this overnight lack of activity it averaged around 65mW, and was never below 60mW.
So after all that rambling, the answer is: radio ROM version. When I installed Android, I installed the latest radio ROM available at the time (still the latest I think); i.e. 2.15.50.14, from http://forum.xda-developers.com/showthread.php?t=611787. After pulling my hair out trying all the above, I flashed the radio ROM with 2.12.50.02_2, and as if by magic, current draw under similar conditions to above is about 7mW; i.e. 10% of what it was, and an overnight period as above goes from 100% to 96%. Much better
I should point out a few extra things:
a) I arbitrarily chose that radio version. I don't really have time to try them all, so if anyone cares to test and post here, perhaps another version gets even better results. To make them meaningfully comparable, install CurrentWidget, get it to log every minute, put the phone into airplane mode, GPS off, kill any obvious large apps like Maps, camera, email polling, and don't run any "battery-saver"-category apps (I had just Messaging, Google Services and Android Keyboard under Settings > Applications > Running Services), turn the screen off for a few minutes (don't move the phone either), then turn it back on and look at the CurrentWidget log. If you post your results here, include which network you're on.
b) This "secret" is sort-of hidden in a few other threads about this, but only in passing and not really prominent. I thought it deserved its own thread so people can find it a little quicker.
c) I don't know if there are other dependencies at play here; e.g. perhaps 2.12.50.2_2 is best with O2 (which is who I'm with), and maybe others are better with other networks. I don't know enough about radio ROMs to know. If people post their results with their network we might figure it out.
d) Changing radio seemed to also cure another problem I was having, namely the data connection on both 2G and 3G regularly disappearing, even though I had a 2G/3G signal. (I used to fix this by switching between 2 virtually identical APNs, while cursing and muttering...)
e) I'm using AmericAndroid GB233 CyanogenMod7 on SD.

Very usefull info indeed! i use the latest radio too and i face the same battery issues. I've tried all kind of stuff (task killers etc) but with no luck, mb i"ll try a couple of radio vers. hope yours doesn't carry any robo voice incidents (I use the CoreDroid v0.8 one)

Stop using SD, flash android directly to your nand, my battery according to Battery Diviner, lasts 25hrs with a full charge not on airplane mode. I used to do SD but I got tired of the slowness and huge battery drain, NAND is the way to go.

I am thinking of going NAND now, but it wasn't really an option while I might have needed to go back to WM just to make it through a single day without access to a charger. What radio version are you using?

But if radio version is the key, i see no point why we should abandon the sd option & move to the nand one. And the 25h -no charge- nand duration isn't such a big deal, is it ?

I have to version 2.15 and I am on nand.... my battery drain is around 3-5ma standby.... which I think is pretty good.... so I think nand is the key..... not radio
Sent from my HTC HD2 using XDA App

It would be interesting if you now flashed to 2.15 again and record your consumption, you might find the early high consumption is not repeated, your original radio may have been very slighty corrupt? I'm using AmericAndroid on SD and get 3mA drain in standby with radio 2.15.50.14, battery widget predicts 12hrs use with 3g phone on and fairly frequent use or 4 days in standby (doubt I'll ever test that one but the 12hrs is about right).
My only temptation to go for NAND is speed, SD is very slow unless using a RAM build and there are too few of those. Can't quite leave WinMo just yet so sticking with RAM on SD.

Yea... even I'm curious... flash back to 2.15 and let us know your results..
Sent from my HTC HD2 using XDA App

I have also the 2.12 radio since january with different NAND roms (mostly sense) and had always 3-5mA in standby. WIFI and 3G off, GPS On/Off makes no difference. Had never the robot voice problems at the first call and no other problems that 2.15 users not have.
There was already a thread where some android nand users confirm the better battery life of 2.12, but not such a big difference like in your case.
Have found a similar thread of WP7 users with the same results.

Any sd android users around with positive battery results? my battery gets raped in almost 15h with normal use! And yeah my stock winmo 6.5 rom does pretty well, while my Leo stays alive & kickin for about 4 days. And just to get a bit off topic, neither Froyo/Gingerbread got me crazy as an OS, nor the "old ship" winmo 6.5 can keep anyone excited anymore. I hope Honeycomb port will be developed in a stable well working level for our Leos.

I think part of the issue here is different peoples' expectations are different. If you are already getting say 12-24+ hours with ANY type of usage, you are probably in a different category to the one I was addressing. The issue I was addressing in my OP is getting extremely poor battery life, of the order of perhaps 6-8 hours with light usage. Several people seem to experience this; i.e. charging required 2 or 3 times a day.
The WM thread mentioned a few posts back is interesting, as there seems to be a clear trend of 2.12 giving better battery life over 2.15 (some anomalies though - be nice if someone who really knows these things intimately could suggest what the dependencies might be).
When I have some time I'll try flashing a few different radios and measuring in an at-least semi-scientific manner. When I have a little more time I'll try NAND with different radios as well. (Anyone with time feel free to go ahead and post results in the meanwhile though!)

nand that killed battery life
I have been using nand roms for a few months now, ever since mdeejay blessed us with his gingerbread builds.
presently using ginger-honeycomb theme rom.
Battery has to be charged twice a day with minimal usage. 2 hours of kindle/music is enough to fry the battery. radio is 2.15.
the rom is superb in appearance and functionality but battery is a real eyesore.
suggestions appreciated.

@fx.dcny: have you tried 2.12 radio as I suggest in my OP?

Hi All,
I'm using Radio 2.15.50.14 and when I use WinMo (ROM Elegancia 2.0), my battery lasts longer than 24h, with a few phone calls and mails and sometimes use of GPS.
With Android on SD, I must charge my battery 2 or 3 times a day. Even in Airplane mode, drain is very high (losts 40-50% overnight). I'm currently with Rafdroid HD 4.2 SD build, but things are same with all other Android SD builds I've tried.
I've just installed current widget, and drain is 60 mA in standby, which seems very high ! and I frequently kill apps with Advanced Tasks Killer (apps like Maps, Soundhound that always reappear !) but maybe this Task Killer makes more bad that good...
As suggested by the OP (thanks for the tip!), I'll tried another radio when I have some time, I still have a backup of radio 2.10.50.28_2, and report to you...
Do someone know how to find the culprit app from Current Widget log? I just see a long list of running apps, but no clue about which one(s) is/are eating the battery.

@thivi: my experience was that the apps listed by CurrentWidget were not helpful (in this context), and like I say when I was getting ~50% battery loss in airplane mode overnight there were no unnecessary apps running, and Android was reporting the majority of the battery use as "Display". Something else must be happening under the radar of the various battery monitors (both native Android and not). I'm guessing (only guessing at this stage) that something in the radio ROM code causes it to draw more current.

Hi folks, this is a first post for me but battery use seems to be a never-ending holy grail to Android users!! I have a HD2 running HyperDroid CM7 V2.0 Fearless Falcon on NAND with radio 2.15.50.14. The phone is a branded TM UK handset and have to say that the biggest battery-eater I ever met was Google Maps. Once uninstalled (installed it on first setup), and with carefull widget management, I can just get 3 days between charges. I must point out though that I am not a heavy data user or anything, I just like to have a good functional handset that I know will do everything I need effortlesly. The HD2 is just the thing. Just as an edit, with Google maps being installed, even if force closed, I only ever got 6 to 8 hours from my battery.

I have found this out from master rom thread. Most of the build recommend 15 but i recommend 2.12.50.02_2 if you have battery drain issue on standby.
sellotape said:
Thought I'd just share this. I had been stuck with this issue for a while; basically needing to fully recharge twice a day. I tried a lot of things recommended on here and elsewhere; all of them either made minor differences, none at all, and some made things worse. Things in that category are wifi, 3g, bluetooth, gps, setcpu, task-killers, screen-dimming, resetting battery stats, starting Haret with the key lights on, etc. All these things can potentially make a difference, but didn't help much. Plus, most of them involve de-smart-ing a smartphone, and what's the point of that? I tried changing SD card, as I have a 16GB Transend class 6 card which I believe draws a few more mW than e.g. Sandisk cards, and that didn't really help either.
As an indicative measure, I could charge to 100% (and green LED) at 11pm, put the phone into Airplane mode (GPS off as well), kill all tasks that are not needed, go to bed, and by 7am the battery was on around 50%. So that's with NO comms, NO screen, nothing. Android battery use showed most of this usage was the screen. Er, no. I installed CurrentWidgit (from App Market) and got it to log; during this overnight lack of activity it averaged around 65mW, and was never below 60mW.
So after all that rambling, the answer is: radio ROM version. When I installed Android, I installed the latest radio ROM available at the time (still the latest I think); i.e. 2.15.50.14, from http://forum.xda-developers.com/showthread.php?t=611787. After pulling my hair out trying all the above, I flashed the radio ROM with 2.12.50.02_2, and as if by magic, current draw under similar conditions to above is about 7mW; i.e. 10% of what it was, and an overnight period as above goes from 100% to 96%. Much better
I should point out a few extra things:
a) I arbitrarily chose that radio version. I don't really have time to try them all, so if anyone cares to test and post here, perhaps another version gets even better results. To make them meaningfully comparable, install CurrentWidget, get it to log every minute, put the phone into airplane mode, GPS off, kill any obvious large apps like Maps, camera, email polling, and don't run any "battery-saver"-category apps (I had just Messaging, Google Services and Android Keyboard under Settings > Applications > Running Services), turn the screen off for a few minutes (don't move the phone either), then turn it back on and look at the CurrentWidget log. If you post your results here, include which network you're on.
b) This "secret" is sort-of hidden in a few other threads about this, but only in passing and not really prominent. I thought it deserved its own thread so people can find it a little quicker.
c) I don't know if there are other dependencies at play here; e.g. perhaps 2.12.50.2_2 is best with O2 (which is who I'm with), and maybe others are better with other networks. I don't know enough about radio ROMs to know. If people post their results with their network we might figure it out.
d) Changing radio seemed to also cure another problem I was having, namely the data connection on both 2G and 3G regularly disappearing, even though I had a 2G/3G signal. (I used to fix this by switching between 2 virtually identical APNs, while cursing and muttering...)
e) I'm using AmericAndroid GB233 CyanogenMod7 on SD.
Click to expand...
Click to collapse

sellotape, you're the boss !
now with radio 2.12.50.02_2 I have 4-7 mA drain in standby instead of 62-66 with radio 2.15.50.14... And last night I only lost 7% battery (and I was not in Airplane mode), it was 40-50% with radio 2.15.50.14 (and in Airplane mode !)
So this radio 2.15.50.14 seems to be the culprit for high battery drainage in Android, at least for some users...
I was happy with the RAFDROID HD 4.2 build but had 2 problems : 1.high battery drainage which is now solved thanks to sellotape thread, and 2.heavy lags that were caused by my SD-Card, problem detected thanks to this thread :
http://forum.xda-developers.com/showthread.php?t=1048649
so now I'm enjoying a very fine Android experience with my HD2, even with a SD build
@GPZ550: it's true that Google Maps is almost always in memory, even after killing it. But I'm a heavy user of it so I don't want to desinstall it. And with radio 2.12.50.02_2 it seems that I can have a decent battery life even with google Maps installed.

I don't want to add confusion here, but my experience as in the OP came to an end about 2 days ago, for reasons I couldn't really associate with anything in particular, except *perhaps* an app update from the market. So... what I did is flashed 2.15 again (to at the same time answer boomboomer and fahd_freak's questions), and I am now back to <10mA standby (down from ~60). I suspect if I'd flashed 2.12 again it would also have fixed it, but I'm out of experimental options in that direction for now. This leaves me rather confused. I would have thought that apps (even under SU) would almost certainly not have sufficient access to alter the Radio ROM.
As a dev myself I struggle with the idea of the ROM becoming "a bit corrupt". I would have thought *any* corruption would have been fairly catastrophic. And yet, mysteriously, re-flashing the ROM seems to be an answer (for now). Perhaps there is some state data that the Radio ROM stores that gets corrupted or invalid and this is overwritten with a re-flash?
Personally I'm not too fussed if I have to reflash the ROM every month or so for now, ridiculous as I find it in principle. It does perhaps mean it's not just radio version that's at issue, but perhaps the action of flashing itself.

I managed to get 5mA draw in standby mode on the NexusHD2 for SD builds (3G on but GPS and Wifi off), with some spikes (when data is being pushed). Able to last a whole day with moderate usage. (Radio version in my sig.)
But really, the NAND builds are much better overall. I managed to get a very similar battery usage pattern as above with the latest NexusHD2 Gingerbread ROM V2.7, 3G, GPS and Wifi all on.