Related
Dear mobile friends,
Recently i have installed NBD on my MDA vario t-mobile Aku2 phone.
I like it alot!
For the chef cook who made this wonderful recipe, A big thanks for all the effort!
I do have one little question...my battery is empty after one day
Any idea how to fix this¿
Thanks in advance.
Regards, Rogier.
mobile-eenheid said:
Dear mobile friends,
Recently i have installed NBD on my MDA vario t-mobile Aku2 phone.
I like it alot!
For the chef cook who made this wonderful recipe, A big thanks for all the effort!
I do have one little question...my battery is empty after one day
Any idea how to fix this¿
Thanks in advance.
Regards, Rogier.
Click to expand...
Click to collapse
get a different phone?
Are you saying your battery is dead 1 day after continuously having this program activated? If so, I'm amazed the battery lasted that long! How old is your device and battery? Does the battery charge o.k. when it's plugged to a charger?
Hi Hotdog,
Thanks for your reply.
My device is 1 year old and the battery drains even when the phone is inactive(battery charges just fine).
Before installing NBD, the battery lasted like 3 days (not really an active user of the phone) and now only 1 day.
Am i the only person experiencing this issue around the forums??
Device info:
ROM version 6.6.6.666 WWE
ROM date 8/23/07
RADIO version 02.19.11
Protocol version 4.1.1309
MDA Vario T-mobile AKU2 model.
Thx.
mobile-eenheid said:
Hi Hotdog,
Thanks for your reply.
My device is 1 year old and the battery drains even when the phone is inactive(battery charges just fine).
Before installing NBD, the battery lasted like 3 days (not really an active user of the phone) and now only 1 day.
Am i the only person experiencing this issue around the forums??
Device info:
ROM version 6.6.6.666 WWE
ROM date 8/23/07
RADIO version 02.19.11
Protocol version 4.1.1309
MDA Vario T-mobile AKU2 model.
Thx.
Click to expand...
Click to collapse
Ive seen many people with this problem. all I can suggest to you is, lower rom numbers on WM6 use up the battery faster. I dont know why that is but that is the trend.
Im not suggesting you go out there and get 2.69 radio rom. the higher you go the more unstable the rom is. all Im saying is, it might be the radio rom mixed with WM6. try a reflash back to wm5 and see if battery is back to 3 days.
One other thing you can try is drain the battery completely, recharge it fully, drain it a second time and recharge it fully again. sometimes when you flash the battery memory gets messed up, it's happened to me once.
elmetal said:
Ive seen many people with this problem. all I can suggest to you is, lower rom numbers on WM6 use up the battery faster. I dont know why that is but that is the trend.
Im not suggesting you go out there and get 2.69 radio rom. the higher you go the more unstable the rom is. all Im saying is, it might be the radio rom mixed with WM6. try a reflash back to wm5 and see if battery is back to 3 days.
One other thing you can try is drain the battery completely, recharge it fully, drain it a second time and recharge it fully again. sometimes when you flash the battery memory gets messed up, it's happened to me once.
Click to expand...
Click to collapse
Thanks for the reply elmetal!
That brings me to my second question,
Is there a Radio ROM out there for my T-mobile that is stable and runs smooth under NBD 8.0?
What comes after RADIO version 02.19.11? 2.69 radio rom?
I did actually flash back to the original T-mobile NL ROM (latest version)
And there the battery is functioning as expected.
(you can really tell, in the afternoon, the battery is almost at 50% with NBD)
Thank you so much for your help! really appreciated.
mobile-eenheid said:
Thanks for the reply elmetal!
That brings me to my second question,
Is there a Radio ROM out there for my T-mobile that is stable and runs smooth under NBD 8.0?
What comes after RADIO version 02.19.11? 2.69 radio rom?
I did actually flash back to the original T-mobile NL ROM (latest version)
And there the battery is functioning as expected.
(you can really tell, in the afternoon, the battery is almost at 50% with NBD)
Thank you so much for your help! really appreciated.
Click to expand...
Click to collapse
hmm.. I never focus much on tmobile users with radio problems, more cingular users. some say the 2.47 works, some say the 2.69 is flawless, I personally use the cingular 2.25.11. it's the stock cingular rom and it works fine.
Im gonna give the forum a good look for tmobile radio rom threads and ill redirect you
I suggest you try the cingular 2.25.11 (being that tmobile in the us uses a lot of cingular towers) since its really really stable.
EDIT
http://forum.xda-developers.com/showthread.php?t=314235&highlight=t+mobile+radio+rom
try that, its a decent thread on the ROM workin in the UK, Im not exactly sure where you're stationed but the point is this, there's probably an existing thread out there.
Only thing is, many different people have many different results. Updating Radio ROMs is a little dangerous for me cus the calls I receive can be very important so I try not to mess with it.
Install a new radio rom, leave your phone in standby for a few hours and test texting and calling to see if itll wake up on its own, some roms wont work well. trial and error
Goodluck!
elmetal said:
hmm.. I never focus much on tmobile users with radio problems, more cingular users. some say the 2.47 works, some say the 2.69 is flawless, I personally use the cingular 2.25.11. it's the stock cingular rom and it works fine.
Im gonna give the forum a good look for tmobile radio rom threads and ill redirect you
I suggest you try the cingular 2.25.11 (being that tmobile in the us uses a lot of cingular towers) since its really really stable.
EDIT
http://forum.xda-developers.com/showthread.php?t=314235&highlight=t+mobile+radio+rom
try that, its a decent thread on the ROM workin in the UK, Im not exactly sure where you're stationed but the point is this, there's probably an existing thread out there.
Only thing is, many different people have many different results. Updating Radio ROMs is a little dangerous for me cus the calls I receive can be very important so I try not to mess with it.
Install a new radio rom, leave your phone in standby for a few hours and test texting and calling to see if itll wake up on its own, some roms wont work well. trial and error
Goodluck!
Click to expand...
Click to collapse
Point taken
Will do some more research on Tmobile Dutch(Netherlands) Radio Roms to see if that helps.
Thanks for all the effort elmetal!
Nope it's not the Radio Rom 2.19 is the most stable and loses less energy.
The 2.69 radio Has more problems keeping the signal so it uses more energy to maintain the signal, and of course you might lose some calls here and there.
Earlier posts do indeed have the classic basic Battery drain tips.
But what about deleting the items from the Windows\StartUp folder?
Flash a fully loaded battery.
How about borowing my new battery and see if it makes a difference since my wizard is on repair.
Some users even have reported that 8.2 actually was better on the battery then 8.3.
Some believe that it might have something to do with the memory leak problem most Wizard roms have issues with. Keeping more memory reffreshed does require more power. So try to set the weather plug in to only update mannualy set the homescreen to not time out. Or try setting up the included smartskey to overclock instead of Battery status althought i don't think that battery status causes isseus.
Or do a Combo. Drain the battery recharge it perform a hard reset or clear storage. You could also try a lower pagepool rom version, nowadays you can change the pagepool without reflashing. Lower is slower but again it uses less memory. You could also use wizard registry wizard to change the font cache to lower setting and other cache settings.
My advice is to charge as less as possible as my USB connector got ****ed.
I tried the 25.11 on T-mobile network but quit using it as it either froze the ROM or could just not connect.
Or yes you could get another phone
Also make sure you change the settings of the network registry to not automaticly scanning for the network.
elmetal said:
Ive seen many people with this problem. all I can suggest to you is, lower rom numbers on WM6 use up the battery faster. I dont know why that is but that is the trend.
Im not suggesting you go out there and get 2.69 radio rom. the higher you go the more unstable the rom is. all Im saying is, it might be the radio rom mixed with WM6. try a reflash back to wm5 and see if battery is back to 3 days.
One other thing you can try is drain the battery completely, recharge it fully, drain it a second time and recharge it fully again. sometimes when you flash the battery memory gets messed up, it's happened to me once.
Click to expand...
Click to collapse
I have a MDA and I am running WM6 and using the 2.69.11 radio and I have no problems. I found that changing the task manager settings so that the program actually closes when you click x helps increase free ram and also, don't use any overclocker software such as battery status(it kills your battery and it doesnt make that much of a difference anyways...). Another thing you want to do is disable the today timeout under today settings. that tends to use more ram and thus, kills the battery faster.
See i knew i wasn't crazy about the today timeout
Thanks for the confirm.
I had the same problem with I upgraded to 8.1. Battery drain was pretty bad.. Usually getting home from work, I'd still be in the 90's with moderate texting, but with 8.1 i'd be in like the 50's. I just went back to 7.9.
The problem isn't the ROM... it's the audio manager from HTC, that sucker eats battery like I've never seen... been having this issue too, until I stoped using the audio manager and started using windows media player!
dferreira said:
The problem isn't the ROM... it's the audio manager from HTC, that sucker eats battery like I've never seen... been having this issue too, until I stoped using the audio manager and started using windows media player!
Click to expand...
Click to collapse
Same here i (as in i didn't actually notice it) but i stopped using the audio manager in favour of WMP as it gave better reactions to using the Stereo Bluetooth headset. As in Audio manager sometimes did not pick up the next and previous commands or would stop playing.
As i said i never really paid attention and i can only speculate that the battery drained faster when i did use Audiomanager.
Just goes to show that closing apps completely is always the best practice.
BTW, dferreira.
Ai's it Funny how one month after your WM5SE release people actually reacted after my post
What is your reason to use WM5 base?
WM5 is the native OS for Wizards... so, I find it to be more quick than WM6... Never gave me problems, like WM6 did. WM6 is just a face lift on WM5 so... I'm trying to make it as good as WM6 but quicker
Noonski....
You are my sunshine, my only sunshine
You make me happy when skies are gray
You'll never know dear how much I love you
Please don't take my sunshine away
Battery drain solved by flashing to NBD 8.0!!(¿)
Thanks for all the effort mobile friends!
mobile-eenheid said:
Noonski....
You are my sunshine, my only sunshine
You make me happy when skies are gray
You'll never know dear how much I love you
Please don't take my sunshine away
Battery drain solved by flashing to NBD 8.0!!(¿)
Thanks for all the effort mobile friends!
Click to expand...
Click to collapse
What build were you having a problem to begin with?
BTW you should see Alban's Touch running on 312MHZ with 12 MB Pagepool.
It Fliesszzzzzzzzzzzzzzzzzzzz.
There is currently a topic on radio versus battery life but as the conclusion is so great I want everyone to know as it may have got lost in the other thread and I feel users here are missing out by not knowing about it.
Basically several users have flashed the 2.12 radio and found much better battery life. On the 2.15 radio I used to get less than 10 hours. On radio 2.12 I have got 18 hours at least.
To flash a radio to your phone, turn off your phone completely. While holding down the volume down button, turn the phone back on. Keep volume down button pressed until you see the red, green blue screen. Connect your usb cable to phone and PC and the text on the screen will change from serial to USB. Execute the custom RUU file and follow the steps to flash 2.12 radio.
Link to radio and custom ruu:
http://www.megaupload.com/?d=IFCLJFV9
Original discussion thread here to read up on it first:
http://forum.xda-developers.com/showthread.php?t=924059
2.12 give me better battery but slower 3G data while 2.15 3G is faster but little more battery drain. It depend on what you need more.
I choose 2.15 for faster 3G
Question:
Should already know I guess but...
Can we just flash the radio and keep the rest of the set-up or do we have to re do the windows installation / un-locking / activation thing?
Toggs said:
Should already know I guess but...
Can we just flash the radio and keep the rest of the set-up or do we have to re do the windows installation / un-locking / activation thing?
Click to expand...
Click to collapse
Just flash radio through bootloader (hold vol down while reseting) and it'll keep everything as is
The radio won't affect your Windows installation at all. Flash at will Just downgraded from 2.14 to 2.12. Now let's see if I will get some more time from it. With 2.14 it was soemthing like 14-15 hrs.
I Will test it when i go home! Thanks mate!
i also found 2.12 better for battery life. although 2.14 seemed ot have slightly better data/voice quality.
The battery life wins out though
I will test it out. THX Mate.
TheOnly1 said:
The radio won't affect your Windows installation at all. Flash at will Just downgraded from 2.14 to 2.12. Now let's see if I will get some more time from it. With 2.14 it was soemthing like 14-15 hrs.
Click to expand...
Click to collapse
Well depends on the phone you have, I had to reinstall my WP7 DFT rom after downgrading to 2.12 due to constant reboot on the DFT screen. I think one should be aware of it too.
Thank U for Ur extremely useful tip,I have quoted to several Chinses forum
Apologize for no aquire beforehand~~~
Yes ... 2.12 Also gives me a better battery life =)
Sent from my HD7 T9292 using Board Express
xda2_haseeb said:
Yes ... 2.12 Also gives me a better battery life =)
Sent from my HD7 T9292 using Board Express
Click to expand...
Click to collapse
I can confirm that too. Much better
So, how do you check which radio you have from within windows Phone 7?
confirm...however data connection sucks....hmmmmm
Is it just the 3G connections that slow down or would there be a noticeable reduction in speeds over Edge?
Strange... my data connection is the same as always. no slow down at all.
The quality of the data connection depends mainly on the network. If you have good enough coverage you won't notice a difference at all.
Do you get call problems,ie does the phone crash after calling with this radio ?
no changes in signal strength but the calibration for the battery meter is horribly unstable atm... if I do a hard reset after a few hours the battery meter goes higher lol
Can someone please re upload this somewhere else?
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
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.
Hey Guys,
It's my first time around the block with an HD2 so bear with me. I'm haveing MAJOR drainage issues with my battery on my WP7 HD2.
I have the latest pdaimatejam 8107 loaded with the default 5.71 radio.
After a couple of weeks I decided to buy a new battery thinking that the old one was busted (I got the HD2 off Craigslist and under Android it complains about the battery not having the proper charge) After using the new battery I get about the same results.
I installed the HTC Battery Status tool and my mah drain is a crazy -100 to -200mah current! Is this normal? I read threads about people trying to get down from -40mah. I have no background tasks running on the phone (at least none that I'm aware of)
I haven't tried flashing the old 5.51 radio yet because I already loaded my 32gb card with hundreds of apps and music and videos. Is there a way to flash the old radio without having to lose everything? The camera trick does not seem to work, and changing the registry values just has it report back to 11 (not 6 for some reason) upon reboot.
Any help would be great. I think after a couple days though I'll try flashing the old radio.
Thanks in advanced!
you cant flash without loose everything....
for save apps data and setting read Tutorial v1.4 from Pdamatejam page
Kindly search forums.. this has already been addressed a lot
For Best performance and good battery life use 2.15.50.xx hard radio + 5.50 soft radio version
For best battery life use 2.12.xx.xx hard radio + 5.50 soft radio..
I did search the forums and I am aware of the different combinations of the radios and the software.
I am more concerned about whether the -200mah drain is a normal occurrence. I guess I could just report back when I have flashed the older radio, but I really don't want to do that considering the amount of stuff I already have loaded on my partition.
I apologize if it seems redundant to post something like this. I haven't seen anyone post about having a huge drain like 200mah. It just seems odd to me and I don't understand how it can get that high.
To give more information, I made sure to turn off the background tasks in WP7 that I don't need. I make sure I exit the program (by pressing back and making sure it doesn't show up as a card) and I even put the phone on airplane mode. After all of this, my drain was in the hundreds.
EDIT:
Great... I checked it just now and the drain is 400mah
mind you, nothing is even running. I just turned it on for the day and it was the first thing I checked.