Related
If you're like me, a subpar or incomplete Android 2.2 on HD2 experience was NOT an option. I've been through pretty much every combination, followed everyone's advice and always ended up unhappy for one of several reasons :
1. The ROM I installed was missing features, like the camera or other features that crashed.
2. The dreaded "Sleep of Death"
Not to say anything against any of the ROM chefs, because these guys are hard-working geniuses and they do this for free... for us...
But having said that, I had to keep trying. I'm obsessive compulsive when it comes to my gadgets and once I had a taste of Android on the HD2, I knew I wouldn't be happy until I found that elusive combination that made it work the way I wanted it to.
If you're having trouble making Android work on your HD2, listen up... Because now mine works like a charm and here's how it happened...
1. You absolutely HAVE to get rid of the stock Windows Mobile 6.5 that comes on your HD2. I never found a way around that. Until I flashed a custom ROM, it never worked 100%. To do this you need to flash HSPL to your HD2. This allows the installation of custom ROMs.
2. You have to strip Windows Mobile down to next to nothing. If you plan on using Android 2.2 as your daily operating system, you don't need it anyway. I tried lots of versions, but face it - you won't need WinMo anymore once you get Android working 100%. For this, use Chuckydroid, hands down. It is stripped down to next to nothing - no Sense 2.5, nothing fancy in Windows Mobile. BARE. BONES. Chuckydroid can also be set up to autoboot into Android!
3. After installing Chuckydroid, I also flashed Radio 2.15 just to have the latest radio. I've heard people talk against it, but again - I'm working 100%, so I'm happy.
4. For my Android ROM, I chose Mdj revolution 1.5, and updated to the S1 Linux kernel. It was one of few builds that had all features working as they should. The S1 kernel patches a lot of issues that might arise with the MDJ build.
5. Lastly, I noticed I didn't have 3G signal after all this and discovered that at some point my APN information (which tells the phone how to connect to data services) had been wiped out. I am a TMoUSA customer, so I found the information for the USA servers and added it manually to the phone. (System/Wireless & Networks/Mobile Networks/Access Point Names)
I know this isn't every piece of information you need, but if you read each point and investigate on your own, you'll find there's a wealth of information out there to guide you through each step, but to clarify :
1. Flash HSPL (I used HSPL 3, but follow the directions when you find it)
2. Install Chuckydroid (No other custom ROM worked and I tried them all)
3. Flash Radio 2.15
4. MDJ Revolution 1.5 w/ S1 kernel (Most stable and complete I could find)
5. Manually configure APN
Again I'll close with the fact that I have a fully-working Android 2.2 HD2 device. All features, all functions, no errors, no robot voice, no SOD, no gremlins... It just works. Good luck! If you have any additions to this plan, let me know! I'd like to know that I was using the newest 100% WORKING(!!!) Android built with all the best features.
I'd also like to add that, given my luck, now that it's taken me over a week to get Android 2.2 working flawlessly on my HD2, in the next day or so we'll see one of four things :
1. A flashable Android 2.2 ROM that completely replaces WinMo as the Operating system
2. A flashable Android 2.3 (3.0) Gingerbread ROM
3. A flashable Windows Phone 7 ROM
4. The return of Christ
Zaron3d said:
4. The return of Christ
Click to expand...
Click to collapse
That's it That's all...
funny
before 1,2,3,4 you can also try:
0. replace kernel with s2 also made by mdeejay. they say it's very good
thinking better i don't belive this thread belong to this section
noris08 said:
funny
before 1,2,3,4 you can also try:
0. replace kernel with s2 also made by mdeejay. they say it's very good
thinking better i don't belive this thread belong to this section
Click to expand...
Click to collapse
Well I tried a lot of these "quick shortcuts" to make things work and nothing did. Believe me, I've been down every road to make this happen...
and yeah I guess I put this in the wrong section now that I look at it. Sorry!
Yep, this thread have to be moved into the Android General Discussions section.
Just let me know if you have a constantly data transfer on on your "working-like-charm" Leo and I'll immediately flash ChuckyROM (which version?), 'cause I've tried EVERYTHING, my battery lasts 3,5/4 hours running Android and I have to recharge it twice everyday...
vysus said:
Yep, this thread have to be moved into the Android General Discussions section.
Just let me know if you have a constantly data transfer on on your "working-like-charm" Leo and I'll immediately flash ChuckyROM (which version?), 'cause I've tried EVERYTHING, my battery lasts 3,5/4 hours running Android and I have to recharge it twice everyday...
Click to expand...
Click to collapse
try this combo:
- wm - energy nov 8 21684 cht 1.8.5
- radio - 2.15
- android - mdeejay revolution 1.5
- kernel - mdeejay s2
i have only 6% battery drop over 9 hours of standby, all data transfers closed and gsm only, not 3g
all things i tested works flawless
i think you missed the most important thing...
--> hard format your SD card before trying
Camillo
Format or not the SD makes non differences, I have huge battery drain in every situation.
I've had several issues running mdeejay builds, so I prefer FroyoStone 3.2 by Darkstone. I've never tried Chucky ROMs before, so I'd like to flash the brand new one
@camillo
no i didn't forget format card. i just don't do that, formatted first time and never again since then
@vysus
do whatever you want. i just suggested a combo that works very well for me
noris08 said:
@vysus
do whatever you want. i just suggested a combo that works very well for me
Click to expand...
Click to collapse
You're welcome
Unfortunately, NRG ROMs and PPP builds are not suitables for italian providers: using the first ones I had battery drain, trying the seconds I have had continuos data drops, missed calls & SMS, HUGE and nearly incredible battery drain.
I still would like to know which version of Chucky fits better with android, it's the last chance, after that I prefer to let go...
i think an correctly configured setcpu is the most important fact for battery life.
my combo:
winmob:http://forum.xda-developers.com/showthread.php?t=793814
radio: 2.12.50
Droid: hyperdroid 1.7 (nexusHD2 since yesterday cuz of new harastin kernel)
sdcard: transcent class6 sdhc
battery drain without setcpu (overnight, 8h): 40%
with : 3%
TBH I have found no difference between a fully featured winmo rom (laurentius V4 or Energy nov 8th) versus Ozdroid which was stripped down.
I have found that of course the kernel makes the most difference - currently on S2 and it seems rather peachy.
As for battery drain I have found that it is fine even without setcpu on this kernel - however - once in a while, especially at the end of the day, the battery drains super fast - I believe there is an errant process or data transfer that messes it up (perhaps whatsapp?).
I stillhowever have PPP disconnects regardless.
I haven't had one since I disabled the stock widget though.
i only have ppp disconnects if i kill all my tasks. if not, it works fine
I start off my android adventure few weeks back and now I found my treasure and have stop searching.
Here is my combination,
WM ROM: vbn clarity
Android rom: mdj froyo revolution 1.5
Kernel: mdj s2
I have tried some other build and the battery life can only last me half a day but with this combination after more than 12 hours of usage, I still have 40%. (Usage: check email every 30 mins, check xda app every 30mins, moderate web surfing, a few calls)
So for those still struggling to find the combination, you might want to try my combination. Enjoy
Sent from my HTC HD2 using XDA App
A different spin on Android Issues
I too was having issues with SOD, random freezing/rebooting, robot voice etc and basically gave up on having a usable version of Android working on my device.
But then I had a slight lapse in judgement and came up with another hair-brained idea... I decided to attempt to get T-Mobile to let me just switch to a different phone like the Galaxy S / G2 / or MyTouch 4G.
So I task 29'ed the phone, flashed back to the OEM rom, then removed HSPL while not at work... Over the next 2 hours I began to notice that I was having issues even on the default OEM rom.
I got curious, removed the SD card, re-installed HSPL, re-downloaded the T-Mobile Official Rom from their website, and task 29'ed the phone again, reinstalled the OEM rom, and removed HSPL again just to make sure that I hadn't just got a corrupt download or something.
Within 20 mins of loading the T-Mobile rom back on the phone, my phone randomly rebooted itself. Later while I was in the middle of a phone call the phone just made a weird buzzing sound and froze. The buzzing sound would not go away until I removed the battery and restarted. I was also having many of the issues I was seeing in all of the Android builds that I had tried like the screen taking forever to come back on after being locked, the screen being non-responsive etc...
I had attributed all of these problems to the Android roms I was using and Android not being 100% and stil too buggy for the HD2 when it actually was a problem with the device itself.
I went to T-Mobile last night and they are sending me a new phone (probably a refurb) by the beginning of next week. I'm hoping that the new device will clear up all of the issues.
Just thought I would share my experiences, maybe some of you that are having issues with the Android builds could actually just have a bad device like I did...
Zaron3d said:
After installing Chuckydroid, I also flashed Radio 2.15 just to have the latest radio. I've heard people talk against it, but again - I'm working 100%, so I'm happy.
Click to expand...
Click to collapse
Followed your suggest, flashed latest Chucky GTX, did anything else, switched to Android, unplugghed my phone at 2.30 PM, some calls and SMS, few calls received, battery is 42%, over 10% per hour that turns to 12 and over using the device, now I'm hopeless
vysus said:
Followed your suggest, flashed latest Chucky GTX, did anything else, switched to Android, unplugghed my phone at 2.30 PM, some calls and SMS, few calls received, battery is 42%, over 10% per hour that turns to 12 and over using the device, now I'm hopeless
Click to expand...
Click to collapse
Uhhh... what? It depends on what you have running I guess. Mine seems to be running fine. Off the charger for about 3 hours and only down to 90%.
Since I've just had my HD2's screen replaced, I'm still on the stock ROM from when I got the phone back from HTC. I just popped my SD card back in and off I went. The stock ROM works perfectly with Android for me. The radio is the one they installed (see sig).
I'm not sure that WM ROM has that much effect tbh. With the ppp wrapper patched and running the S2 kernal from MDJ, I managed a 320 mile trip with Google Navigate running the entire time. I never had a single data drop or problem with the phone. I was connected to my car stereo via bluetooth too.
ive been playing around with android a lot recently, but i seem to be getting the same or similar errors with every build. i think the problem comes down to an unformatted memory card. i want to start with a fresh phone and memroy card.
my question is which WM build is best for android? i would be using android as my main os but windows mobile would serve as a'backup' os incase android dies on me. i already have a build of android i want to use so just need some advice on which WM build to use. once i have done that i can format the memory card and re-install android.
not sure if it matters, but i would be using a boot loader to get into android. i have radio 2.15.
matthewharmon102 said:
ive been playing around with android a lot recently, but i seem to be getting the same or similar errors with every build. i think the problem comes down to an unformatted memory card. i want to start with a fresh phone and memroy card.
my question is which WM build is best for android? i would be using android as my main os but windows mobile would serve as a'backup' os incase android dies on me. i already have a build of android i want to use so just need some advice on which WM build to use. once i have done that i can format the memory card and re-install android.
not sure if it matters, but i would be using a boot loader to get into android. i have radio 2.15.
Click to expand...
Click to collapse
I'll try to answer the question by sharing my own experience:
I have T-Mobile US HD2 model and tried several builds under "stock" ROM and Radio 2.08 and most of them worked with really bad battery life. Anyhow, I finally decided to move on with installing Hard SPL 2.08 so I can flash custom ROMs into my device. After that following happened:
1. I tried ChuckyDroid ROM lite - barely occupied any space after boot in WinMo - but did not affect Android and how it worked AT ALL! I had shubcraft 2.0 at the moment;
2. Finally after all the chasing I wanted to have fully functional WinMo Rom and fully functional Android build and here is my setup:
Energy 2.5 GTX WinMo ROM based on 3.14 latest TMOUS Update (with the start button on the top);
Android HyperDroid 1.7 with mychprima's kernel (240 lcd density);
Radio is 2.15.50.xx
Re-formatted 16GB stock SD Card I got with my HD2
Results:
Super-smooth Android operation at all times;
Without SetCPU installed (since kernel is already OCd and UVd) my battery life has been AWESOME! I get constant 3-6mA battery stand-by and that alone gives me really good battery life. I am getting one day and few hours after 1.5hr re-charging - that I did not beat with anything I tried on my hd2 before this setup. I have reseted phone last time several weeks ago and not a single force close message so far (to knock on wood hihi) ... No reason to lie - but if you have some time it may be good combo to try our. BTW I do not offer any guarantees on what you do with your phone lol - that's my "fine print" lol
eenbox said:
I'll try to answer the question by sharing my own experience:
I have T-Mobile US HD2 model and tried several builds under "stock" ROM and Radio 2.08 and most of them worked with really bad battery life. Anyhow, I finally decided to move on with installing Hard SPL 2.08 so I can flash custom ROMs into my device. After that following happened:
1. I tried ChuckyDroid ROM lite - barely occupied any space after boot in WinMo - but did not affect Android and how it worked AT ALL! I had shubcraft 2.0 at the moment;
2. Finally after all the chasing I wanted to have fully functional WinMo Rom and fully functional Android build and here is my setup:
Energy 2.5 GTX WinMo ROM based on 3.14 latest TMOUS Update (with the start button on the top);
Android HyperDroid 1.7 with mychprima's kernel (240 lcd density);
Radio is 2.15.50.xx
Re-formatted 16GB stock SD Card I got with my HD2
Results:
Super-smooth Android operation at all times;
Without SetCPU installed (since kernel is already OCd and UVd) my battery life has been AWESOME! I get constant 3-6mA battery stand-by and that alone gives me really good battery life. I am getting one day and few hours after 1.5hr re-charging - that I did not beat with anything I tried on my hd2 before this setup. I have reseted phone last time several weeks ago and not a single force close message so far (to knock on wood hihi) ... No reason to lie - but if you have some time it may be good combo to try our. BTW I do not offer any guarantees on what you do with your phone lol - that's my "fine print" lol
Click to expand...
Click to collapse
thanks for that, Energy ROMs seem to come up a lot, and as development for my current WM build (CleanEx DSE 6.1) seems to have stopped, il give that a go. im currently getting a lot of force close messages revolving around the sync features. also my HTC calender doesnt work and contact images do not display (I assume because it cant sync them from facebook). im currently using MDJ FroYo Sense Revolution v.1.7 as my android build, but il try your setup. battery life has become a bit of an issue for me, but i am a 'heavy' user.
is it better to format the memory card through WM or through the PC? and should i be setting any options or just leave them at default values?
matthewharmon102 said:
thanks for that, Energy ROMs seem to come up a lot, and as development for my current WM build (CleanEx DSE 6.1) seems to have stopped, il give that a go. im currently getting a lot of force close messages revolving around the sync features. also my HTC calender doesnt work and contact images do not display (I assume because it cant sync them from facebook). im currently using MDJ FroYo Sense Revolution v.1.7 as my android build, but il try your setup. battery life has become a bit of an issue for me, but i am a 'heavy' user.
is it better to format the memory card through WM or through the PC? and should i be setting any options or just leave them at default values?
Click to expand...
Click to collapse
What I did was reformatting under multimedia card reader - I do not think it matters but that's what I did.
I did find some registry tweaks that manages sd card power a while ago and tried them under stock rom and radio - it did not work but I never bothered to go back since my battery is not really getting drained - lasts enough for me.
I only installed BSB Tweaks and disabled EVERYTHING and left only power-saving ON. I have no clue whether this helps at all or not but just did it as a preventive measure ... also, make sure auto-lock is DISABLED under Windows. That was one of the old issues to get un-wake-able screens ... however, so far I have not really had any problems.
Keep in mind: if you want to install many apps that you would like to test - do not do it in massive installations one after another. Some apps are known to screw up battery life and stand-by mAs. Therefore, install couple at the time - after reboot if you get low mA - then app is not draining the battery.
So far I have experienced Extended power widget to drain the battery a lot and also any type of news browsers like e-buzz, pulse, etc - they seem to constantly pull data and remain active. However, they may work for you if you have data disabled for the most part (which is probably not the case) - forgot to mention mine is on 3/3.5G at all times.
- Background Data is checked (ON);
- Auto Sync is unchecked (OFF);
- Brightness disabled under very strong light (110 lumens of my flashlight hihihi) and set on 35-40% I think - somewhere around there.
- I have three home-screens and do not feel I need more
- Weather widget, current widget and google search widget - I do not have any clocks for simple reason - when the phone is locked I can easily see the time by clicking the hardware buttons - so what's the point of the background one ...
If I remember any other tips and tricks I'll let you know.
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.
I know theres alot of topics about battery drain, and some methods have worked for some, but I am still stuck in the loop.
I'm using Back to the Future (XBmod-Yuki/7740) - and have tried The Camera Trick, 2.12 Radio, and Registry tweak (battery indicator) and all have failed, i get around 8-10 hours battey on minimal use, (Facebook app for 30min and 8/9 text msgs) [note: 3g and Data on]
and I was wondering is anyone noticing any difference on other wp7 roms? or is that rom specific?
Thanks in advance
Apparently i've got the same issue as you, I got 3 hours off it with intensive use today ( 2.12 radio, no battery fix, but it was draned down to zero )
I'm also using the back to the future rom ( But it's registered as 7720 )
My device is eastern europeian.
I'm back on winmo
i will try wp7 again (HD2O) (7740) but with different SD cards, hopefully i get a lil better life
ill let you knw how that goes
bash18 said:
I'm back on winmo
i will try wp7 again (HD2O) (7740) but with different SD cards, hopefully i get a lil better life
ill let you knw how that goes
Click to expand...
Click to collapse
And i'm gonna get an android SD these days to compare.
with lightly use, my HD2 WP7(Back to the future 7740) ate battery so quick. I'm trying to flash pdaimatejam's v2. Hope to get some changes.
Okay to CONFIRM
Booted pdaimatejam's v2 on lexmar 8gb (class 4 )
Radio: 2.12
and so far used 10hours
and still 54% battery remaining
3g and data is ON!
Location OFF
Live Tiles disables (have to manually update hotmail etc, no push)
Tooks round 40pics, used FB app (Biggest drain)
and few small video clips (2.mins each)
also 70-100 txts snt and recieved
im happy now
yeah i was struggling with battery life for a while too.
the camera trick seems to have helped a lot. i get almost 2 days with normal use with location, 3g and data all turned off. i am going to do the registry trick, then turn location, 3g and data back on to see if anything changes.
EDIT: the registry editor that works with mango does not allow me access to these registry files. oh well.
Android SD was still not the best I've tried. while the ROM had more battery life then yuki's back to the future, it still left me 30 minutes before I was ready to let it go.
Today on WP7 i got 3.5 hours with: the camera trick,(Switch to video and leave it running, right?) also no 3g no Wi-Fi and no Location/Bluetooth. Brightness all the way down ( snowy weather ) . Where can I find the instructions/guide to installing pdaimatejam's or is it included in the download?
Do we have to use camera trick every time we reboot HD2? How about the reset command from MDLDR menu? Do we need use it every time we replace battery?
larryexchange said:
Do we have to use camera trick every time we reboot HD2? How about the reset command from MDLDR menu? Do we need use it every time we replace battery?
Click to expand...
Click to collapse
reboot should be fine, bt i tried the HD20 rom over last few days (radio 2.15) and battery drain whilst standby is AMAZING! with 3g on over night it drained like 5-7% battery, but when using browser, whats app etc battery drains too much :S
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.