Related
All - Am at the verge of giving up on android today. Went out on a little trip today and was depending completely on google maps for navigation. Had the following issues:
1) GPS locking took too long despite having the phone exposed to clear skies
2) Data connection getting disrupted abruptly - I need to reboot the phone / or switch in and out of the airplane mode to get the connection going again
3) Experiencing data corruption / missing files on the data card! I lost almost all of the 30+ pics I took today. There are some random files showing up in LOST.DIR - I'm going to try recovering data from it if possible?
Any thoughts, hints and leads would be very useful - going back to winmo 6.5 is like jumping from the frying pan into the fire .
I'm running the darkstone froyo build on the 3.14 stock ROM - did not install HSPL.
I'll be pulling an all nighter to search thru the forums today - in the interim, any help would be much appreciated.
thanks.
this may be obvious but: try other builds, radios, etc.
1. Several fixes available. Run QuickGPS in WinMo about once every week before you boot into Android, lock time should improve drastically. Search for gps.conf and libgps on this forum, they can be tweaked too if QuickGPS doesn't to the trick.
2. Check if you can convert your build, which is probably PPP, to RMNET. RMNET is slower, but more stable, it shouldn't have any data drops. There are fixes for PPP too, but none of them are 100% reliable already. Change to an RMNET build if yours cannot be converted (easily).
3. No idea, never heard of this before. Might be a corruption on your sd card too, try reformatting it.
I've had the phone for about a week now, and it's been really crash-prone and unstable for the first couple of days. I previously had an HD7 for 4 weeks, so I immediately set up my DVP like I had the HD7 set up.
It was so buggy, I hard reset at least a couple of times in those few days. My most recent hard reset was on Sunday, and lo and behold, I didn't experience any crashes for 4 days!
That started me thinking. The difference between the previous hard reset and the current hard reset was that I hadn't loaded many apps or any mp3s yet - so I loaded the same amount of MP3s as I had before (about 8gb) and immediately any new programs started crashing! In fact, I think just about anything that wrote to the disk exhibited errors, from newly downloaded and installed apps to existing apps which does disk I/O. The marketplace crashed all the time while downloading or installing apps.
My best guess as to the cause of the issue is that the SD card is corrupting data. As long as you are using the internal storage, everything runs fine - but once data is written to the SD card, things are getting corrupted. I'm not sure about this, it's just a guess.
At the OS level, the internal storage is combined with the SD card into a single logical disk - AKA JBOD in RAID terms. I'm not sure about the OS-level algorithm it uses to determine whether or not to save to internal vs SD card, but my guess is that it writes to the internal first, then when that is exceeded, it writes to the SD card. Even after removing some MP3s, I still had crashes, so I'm guessing that it doesn't overwrite the same sectors that previously held data until all the "fresh" sectors have been used (ie it was still writing to the SD card).
If this is the case, then the culprits could be either A) Dell's crappy SD card drivers corrupting the data or B) a crappy quality SD card corrupting the data. Given their recent QC issues i'm inclined to think it's B - but I hope it's A because that would imply a software fix as opposed to having to replace hardware.
Either way, I'll write a program to test my hypothesis: It'll create a test files of a specific size and then read them back and check that the test data is correct.
Thoughts? Has anybody else noticed similar behavior after filling up their storage?
I suspected the SD card as well, which is why I included the remaining storage space in the options in the poll at http://forum.xda-developers.com/showthread.php?t=891295
That being said, some others have said that doing a system reset on their phone did not fix the crashing problems. There are 2 major unknown variables here of course - when the phone is using the SD card vs. internal memory, and whether everyone is experiencing the same type of crashing.
pjfan75 said:
I suspected the SD card as well, which is why I included the remaining storage space in the options in the poll at http://forum.xda-developers.com/showthread.php?t=891295
Click to expand...
Click to collapse
Yeah, I wouldn't be surprised if there were multiple causes for the all the crashes people are experiencing - most likely the SD card may be responsible for some of those, while other issues are causing more crashes.
Impossible to tell at the moment, though. But perhaps the reason why people associated wifi with crashing was that they were using the wifi to load more data than they were over 3G?
I've thought about the apps too. AP mobile is one that is involved on my list. Shazam, yelp, where, are others. I an make my hd7 crash with each of them. However, that does not eliminate sd card. Optimal read/write access speed will probably impact crash, lag, and performance.
Based on this thread it sounds like it's probably more of a driver issue.
alodar1 said:
I've thought about the apps too. AP mobile is one that is involved on my list. Shazam, yelp, where, are others. I an make my hd7 crash with each of them. However, that does not eliminate sd card. Optimal read/write access speed will probably impact crash, lag, and performance.
Click to expand...
Click to collapse
I've used those apps on the HD7 and I don't think they ever crashed it - not nearly as often as the DVP crashes.
zaijian said:
But perhaps the reason why people associated wifi with crashing was that they were using the wifi to load more data than they were over 3G?
Click to expand...
Click to collapse
That and also at a much higher rate than 3G typically.
zaijian said:
Based on this thread it sounds like it's probably more of a driver issue.
Click to expand...
Click to collapse
I don't know if I would agree with that. I would hope that drivers would be the same on all devices. To have 1 fail and 20 not fail....is it driver? I would be curious to know what the failure rates would be. Sure we see alot of complaints here on this forum....but there is not a whole lot of traffic about failure of the DVP. All in All, I'm happy with the DVP. I also have a HD7...and I'm happy with that. I have them both sitting here...and when I make a decision to use a phone of my choice...I've chosen the DVP.
With all things being equal, if I get into a fight, the DVP can be used as a weapon.
I've used up quite a bit of storage but the only time I seem to get a crash is when I enable WiFi, otherwise my DVP seems to run stable.
efjay said:
I've used up quite a bit of storage but the only time I seem to get a crash is when I enable WiFi, otherwise my DVP seems to run stable.
Click to expand...
Click to collapse
I have the same results, I went crash free for 2 days without WiFi I wanted to test it and turned it back on and it crashed within a few min.
I have a replacement coming from Dell but I doubt they will have it fixed. I'm hoping it would be something that can be fixed by an update.
Mine crashes too!!
I too am experiencing many of the issues that have been posted on this forum (crashing w/wo wifi, while in MP, or when an app needs data from the internet). Twice I have reached in my pocket, hit the power button to bring up the lock screen and nothing happens - just a blank screen. Hence had to pull the battery and reboot.
A couple of other things I have noticed that I am not sure I have seen on the forums. Does anyone else have a DVP where the top left edge and the bottom right edge are not flush with the bottom of the phone? It is slight, but I noticed it on day one. Also, I have a heck of a time with the accelerometer sticking. Sometimes it refuses to go back into portrait mode. No mater how I turn and twist it (360 deg).
Anyone else experience this?
I used to use the power button to get to the unlock screen, but after fumbling with it a few times in the dark, I switched to flipping out the keyboard, which does the same thing. And while it did often take multiple presses of the power button to wake the DVP, I have never had to pull the battery.
I've had the DVP since November 8th, and had it crash on my severely enough for a battery pull maybe 3-4 times tops. This is both on the "engineering" phone and the "retail" phone. The only difference I have with you guys - and this is pretty significant - is that I hacked my SD card pretty much within the first couple of days of getting it. I've upgraded to a SanDisk class 2 16GB.
Now, I haven't particularly filled it up; in fact, I have tons of space free. But, I'd like to set some facts straight:
1) The DVP has no internal storage. Just a few megs (~16MB or so) just so the OS can run if you pull the SD card. Nothing new here; we've seen this during the first days of the SD card hack thread.
2) If you fill up your storage, and applications request for IsolatedStorage, the request will most likely fail if you have (close to) zero storage free. If applications don't check for that, it will probably crash. I don't know if this is necessarily happening, since I don't have a crashing device to observe this behaviour, but that's one hunch. Some of you have said that the HD7 did not crash when you filled up the storage, which might throw my theory out the window.
3) The SD card used in the DVP is also a SanDisk - I tend to trust them with storage reliability. If it is indeed a driver issue, then Microsoft might have some share in the blame as well - MS writes drivers for the OEMs for WP7.
What we need to do is scientifically reproduce the issue. Instead of general data corruption, another thing to check is to see what happens as storage gets filled up.
kltye said:
What we need to do is scientifically reproduce the issue. Instead of general data corruption, another thing to check is to see what happens as storage gets filled up.
Click to expand...
Click to collapse
I attempted to do just that - I wrote a storage test app and ran it on my DVP, and it encountered no issues.
The app wrote test data, filling up 95% of available free space (around 13.3GB), then read it back in and verified the data. I'm now fairly confident that it's not the SD card or the storage drivers that are responsible for the crashing.
I did however, encounter issues trying to download the Rise of Glory game. I had turned wifi off, but it's large enough that it requires wifi or sync in order to download and install. Once I turned wifi on and retried the download, the phone crashed on me.
Let's see if we can verify the wifi + marketplace issue:
1) make sure phone wifi is off
2) connect DVP to computer, run Zune
3) via zune sync, verify that you can install a large game or app on your phone. It has to be one which you haven't downloaded before, as I don't think you can force zune to reinstall an app it knows you already downloaded.
4) disconnect the phone
5) verify the game runs correctly
6) uninstall the game on the phone
7) turn phone wifi on
8) go into marketplace on the phone
9) reinstall the same game and see if you have any issues with marketplace while downloading (freezing/hanging/etc)
10) if everything's still ok, verify that the game runs correctly
@Zaijian
I tried reproducing your flow on my DVP and it didn't crash. But, what is strange is mine freezes (only twice so far) @ random right after playing and trying to get to some other app or switching between app. This tends me to side on the memory as being the culprit or some other component being the culprit. Most likely could be memory related and how WP7 manages to kill an app. Is there a memtest kind of thing we could run on this DVP?
I wrote a wifi transfer testing app and ran it overnight - it transferred 4GB over my wifi (from my desktop to the phone) correctly and without incident.
So, i've confirmed that:
A) there's nothing wrong with writing a single large file to the file system
B) there's nothing wrong with transferring data over wifi
My next tests will be:
1) simultaneously writing multiple large files to the file system
2) simultaneoulsy writing files to the file system and transferring data over wifi
3) some sort of memory test to see if memory is getting corrupted
WiFi seems to be the issue
Not much question that mine locks up when WiFi is turned on. I have been experimenting with this issue for the past few days and while having WiFi on causes random lock-ups, not having it on makes it run without any issues.
Fortunately, most of the areas I use my phone have good 3G coverage so WiFi acting up is not a deal breaker but I certainly hope they are able to fix this with the impending update.
One consideration is could there be an app we all have that uses WiFi that is causing trouble? Has anyone had issues with this from a fresh device? I seem to recall having it lock up early on before I put many apps on it.
jetjockgordo said:
Not much question that mine locks up when WiFi is turned on. I have been experimenting with this issue for the past few days and while having WiFi on causes random lock-ups, not having it on makes it run without any issues.
Fortunately, most of the areas I use my phone have good 3G coverage so WiFi acting up is not a deal breaker but I certainly hope they are able to fix this with the impending update.
One consideration is could there be an app we all have that uses WiFi that is causing trouble? Has anyone had issues with this from a fresh device? I seem to recall having it lock up early on before I put many apps on it.
Click to expand...
Click to collapse
My problems seem to occur when I'm going through the marketplace and downloading via wifi.
I verified with my test app that wifi can transfer a large amount of data without errors. This leads me to believe that the wifi itself is not the cause of the issues, but that wifi in combination with other factors may be the cause.
zaijian said:
My problems seem to occur when I'm going through the marketplace and downloading via wifi.
I verified with my test app that wifi can transfer a large amount of data without errors. This leads me to believe that the wifi itself is not the cause of the issues, but that wifi in combination with other factors may be the cause.
Click to expand...
Click to collapse
I thought so too but I left the WiFi on and rebooting without accessing Marketplace has been causing lockups as well. In fact, I just noticed it was locked up after a reboot 10 minutes ago and, sure enough, I left WiFi on. I didn't so much as unlock the screen after the reboot although I have also had it lock up while accessing Marketplace.
jetjockgordo said:
I thought so too but I left the WiFi on and rebooting without accessing Marketplace has been causing lockups as well. In fact, I just noticed it was locked up after a reboot 10 minutes ago and, sure enough, I left WiFi on. I didn't so much as unlock the screen after the reboot although I have also had it lock up while accessing Marketplace.
Click to expand...
Click to collapse
I'll test using wifi simultaneously with local disk I/O and see if that causes errors.
Alright, so I have posted on this before, and thought I had it solved... WRONG! So the problem is anytime I go to use data without wifi, it'll reset the phone for some reason. Already tried every radio, and that didn't do it. I've tried 3 different SD cards, even without cards. So if I never setup a data connection the phone works great. As soon as I setup that connection it just starts rebooting. VERY annoying! Especially when trying to show it off lol.
Can anyone chime in on this? Is this normal?
very odd, actually, i would have said nope never heard of it up until 3 min ago when i downloaded a program from the marketplace, left my screen on and didnt touch it and zap, of it went, up to then ive never had an issue at all, i hope it doesnt persist. I think its unlikely an SD issue, but it could be, if you can always reproduce the issue then its likely a system bug, if its random then its more likely to be memory/SD issues.
Hi guys i had the same issue on my TMOUS device and i still have it... but its only when i use my 16gb san disk memory card
So that is SD card issues for yourself then,
intrestingly ive worked out that if i fill up my card a couple of hundred MB more i dont have the issue, take the files off again and it has problems, So ive run it through some tests and there is nothing wrong with it, i can only assume that for one reason or another the OS does not like a particular portion of the card...even though i cant find any issues with it, all i can assume is that there is some performance issue in that sector, not enough to create errors on the PC but below what WP is needing.
Wow that's strange... And yes, I can replicate the same situation consistently. It's always Data for some reason. I just can't tell if it's upload or down
Ok one thing I do notice... It will reboot MUCH easier with specific radios. Others will last much longer before they reboot.
try dumping a few 100MB of music on, if its anything like mine it may be enough to get it working,
To be honest there is so many different stories on here with various issues, including one from myself i dont think there can be a single answer, if a different radio works better than thats one step, try filling more of your SD that another step, keep building it up until you get somewhere, dont think there is much more i can suggest im afraid, sorry!
Hi guys. I've been running the Android Stock Desire build from Cotulla for a few months now. Every once in a while I'd get a freeze, but then a battery in, and out would fix the problem (usually within the first try. sometimes I need to do this a few times, but no more than 5 times)
However, since last Friday my phone has been crashing like crazy! Constant crashes at random stages, and even reboots. Removing the battery also didnt guarantee a fix. I think I may have tried it about a hundred times, and Android just crashed at a random point in time during every boot. Eventually it booted, but since then it has crashed again! I figured that perhaps I should try a newer build.
I've decided to try out this build: [08.MAR.2011][CWM]TyphooN CyanogenMod 7 RC2 v2.5.4[2.3.3][A2SD/RAM][rafpigna OC 1.8]. Since I already have radio 2.15.50.14, these are the steps I've taken:
- Flash Task29 (ShaDrac version).
- Flash MAGLDR 1.13
- Flash ClockworkMod Recovery v1.3 135M System
- Flash CM7
Now, even during the various stages before flashing the CM7 rom, I would get freezes during the MAGLDR 1.13 bootscreen, or recovery won't load and I'll get stuck on the GOGOGO screen. Also, copying the zip file over in the MAGLDR mass storage mode won't work, and causes a freeze when I start the copy. Reset, or Battery removal seems to get me to the next step again.
Eventually I've flashed CM7, but now it freezes at the setup stage.
I'm starting to think maybe its not the various Android builds that I'm trying, but perhaps the problem lies somewhere else on the phone? Any ideas? Is my radio perhaps not the best one for the phone (even though its the latest)?
Any help will be much appreciated.
Regards,
XA83
Shameless bump (hope I'm not breaking any rules!)
I realize this post should have probably been under the CM7 thread as well, but I don't have access to that yet due to my low post count...
Could be:
*Wrong CWM Size, check in the rom thread for information
*leftover data, task 29 and reinstall everything
*Corrupted data on SD card, try booting without sd card to see if this is the case.
Thanks for the reply.
I've removed both the SD card and the SIM card. Phone seems to work flawlessly. Boots CM7 without a hitch. Next step I've added the SD card back, and formatted the card from the CM7 settings page. Still perfect.
I've tried it about 5 times now and every time the SIM card is not present, the phone works like a dream. Every time I put the SIM card in, CM7 crashes within the first few seconds of showing the home screen.
Finally, some progress!! Thanks again for the assistance. However, what dis this mean? Could this be related to the actual SIM card I'm using, or does it have to do with the part where it initiates the network connection and possibly the 3g connection?
*Also, just for information, I believe that I do have the correct CMW size. The build indicates "Flash ClockworkMod Recovery v1.3 135M System" which is the one I've flashed.
maybe reflash back to winmo then do evrything all overagain to android
I doubt it's an issue with the phone and its initiating with the sim card. Just replace the sim card
the SAGA continues
Hi Guys,
So since my last posts I have actually managed to get the phone running Typhoon's CM7 and its been working great... for a while.
I'm currently on version 3.0.4 and I still get:
1) Freezes,
2) Reboots,
3) SOD,
4) This happened today: phone cuts mid-phone call and makes a loud buzzing noise until I pull the battery.
I'm thinking more towards hardware problem at the moment, but please let me know what you think, and what I can do to debug the sitaution. Is there perhaps a hardware monitoring app that I can install that logs the whole system every 1 minute that I'll be able to pick something up.
I was also thinking maybe the phone overheats. As explained in my original post, whenever a crash or reboot occurs, it would sometimes not restart the first time round after pulling the battery out and putting it back in. Sometimes I get crashes even during the MAGLDR stage with "fatal hit" and strange things like that. Or even when I boot into CWM sometimes.
Now, to test this overheating, I've experimented with placing my phone in the fridge for 5 minutes after a crash. Thusfar I've done this 3 times, and every time I get a clean boot when I put the cold battery back in and then the phone functions perfectly for a while.
So, overheating, or do I perhaps need another radio? I'm out of ideas.
Any help will be much appreciated. The problem now is that I'm so used to android that I wont be able to go back to winmo or even blackberry
Regards,
XA83
it happens to my phone, and did on my previous HD2.
I've tried every build, task 29, every radio...new sd card....everything.
matt
Are there any apps we can run to test battery temp, cpu temp, cpu voltage or anything like that? I'm pretty effecient at debugging PC hardware issues, but when it comes to my phone I feel like I'm back in the stoneage!
Please help
I have tried over and over and over and over on this kind of issue.
most if the time was some unfinished coppied file which can;t runs properly on roms.
Try to asks ROM developer.
- SD partition : how many partititons?
- SD partitions : what kind of partitions, is it using etc 2/3/4, does it comes with swap etc?
- Installation method : does it needs to clear phone ROM with cwr ? what is the size?
HD2 usually I will go for 400M size
- config.txt settings for SD/NAND.
A proper guide could helps you on in the installations
If you guys are having overheating problems resulting in freezes, you might want to use SETCPU and set a lower maximum frequency. Something like 800-900 mhz might keep your cpu's from getting too hot. Or maybe setting it to a different governor could help too, idk for sure.
Sent from my HTC HD2 using XDA App
Freezes
huggs said:
If you guys are having overheating problems resulting in freezes, you might want to use SETCPU and set a lower maximum frequency. Something like 800-900 mhz might keep your cpu's from getting too hot. Or maybe setting it to a different governor could help too, idk for sure.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Possible solution, Thanks mate,
I changed the CPU speed to 1036 Mhz from stock 998 Mhz speeds and haven't had a Freeze yet,
before that The touch screen would freeze occasionaly when there was a lot of activity like in games such as fruit ninja ....
a Lower CPU speed such as 806 Mhz also seemed to do the trick ...
I don't understand why the Freezes would occur at stock speeds ...
I'll have to give it a few days though ...
Touchscreen Freezes
huggs said:
If you guys are having overheating problems resulting in freezes, you might want to use SETCPU and set a lower maximum frequency. Something like 800-900 mhz might keep your cpu's from getting too hot. Or maybe setting it to a different governor could help too, idk for sure.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Update:
Tried that with Interactive Governer, it still freezes on odd occasions, and the battery temp shows 33-36 Degrees Celcius on load when running games ...
i'm beginning to think the freeze is temperature related, as it never freezes while it's cool ...
I'm going to try running it with Smartass governer and see if it makes any difference ...
regards.
Yeah, there's been alot of HD2 owners who've had high-temp related freezes, one guy even went as far as to dissassemble his phone, re-bond the cpu to his mainboard, and add a home-made heat sync to prevent further overheating (successfully)
I just figured changing the cpu freq or governor might reduce cpu load, or increase efficiency, resulting in less overheating. But I feel pretty confident in saying that you guys' freezes are very likely coming from heat. It was even a problem in stock WinMo roms
Sent from my HTC HD2 using XDA App
Yawp, I can barely charge my phone with the silicone case on anymore and that's in ac (the AC in my house is usually set at 74F) I have noticed I get freezes at 36C however I can go to the beach and get it up to 44C and it runs flawlessly
Touchscreen Freezes
Dylan Wilson said:
Yawp, I can barely charge my phone with the silicone case on anymore and that's in ac (the AC in my house is usually set at 74F) I have noticed I get freezes at 36C however I can go to the beach and get it up to 44C and it runs flawlessly
Click to expand...
Click to collapse
Thats wierd, I'd have thought that such a High Temp as 44 Degrees C would cause more freezes ....
regards.
i'm getting freezes from cyanogenmod android too. i recently restored my ROM to the original 2.13 and believed to have all previous settings related to android deleted.
freezing
i realy didnt undrestand what the exactly means of freeze, my phone freeze after change rom ,i can't use "TyphooN CyanogenMod " becuz my phone freeze at the android logo and it didnt any animation to boot !!!
i have hspl8 , radio 2.15.50 ,Recovery_130M_system_4M_cache[v3.0.2.4],mgldr 13.
i install windows then install android but it steel frezz, i can install just HyperDroid-GBX rom !!
it this problem fix with cpu temp ??
i get it in Refrigerator still feee !!
Temperature
Hi guys. It's definitely the overheating causing all the freezes. I've now succesfully "fixed" my phone 11/11 times by placing it in the freezer and then it works flawlessly for at least a day.
I'll try setCPU to try and lower the CPU frequency from stock and prevent heat issues.
However, ideally I'd like to return the phone to the manufacturer as a defective one! Only problem - how do you convince the 'genius' tech guy that the phone overheats. Last thing I want is to send the phone in, and only get it back after a few months with some response that they found nothing wrong.
Hence, I'm still looking for some sort of app to prove in a way that the overheating is causing crashes... At least in that case they may be more likely to issue a replacement immediately. Any ideas yet?
Regards,
XA83
Just a follow up:
My phone has been sent back to HTC. After a long wait, tech support said they replaced the hardware components - I'm assuming the phone mainboard.
I've reflashed CM7 since, and it hasn't crashed a single time!
Verdict: Random freezes was caused by hardware problems on the phone, and the crashes was most likely due to overheating of the components.
Regards,
XA83
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.