I've always read the thread about battery life problems on here thinking "Thank **** mine doesn't have that problem" - luckily since I bought mine in December the battery has been quite impressive really.
But a few days ago it suddenly started losing power VERY fast. I'm talking about 10%/hour even on standby, so I undid changes I'd made recently and it made no difference.
Then I read through loads of other threads on here from people who had poor battery life on their phones to look for clues/solutions.
It seems that the responses are (understandably) fairly consistent, eg:
check for stuff running in task manager
remove changes recently made to the phone/uninstall recently added apps
make sure your data/wireless etc isn't doing stuff it shouldn't be
turn off automatic updates
turn down the screen brightness
check activesync
do a hard reset
upgrade your radio rom
etc
All of these of course make sense and are useful suggestions, but it seems there are a good few cases where doing these things don't help, ie you check out the different potential causes and none appear to be responsible. And in the case of sudden poor battery performance you can't point the finger at the rom/screen brighness/auto updates if they are only doing the same as they have been for ages without issue.
So is there a genuine case for the batteries just suddenly 'going weak'?
I've resorted to a hard reset on mine last night after assuming something had got corrupted hence why I could not find the cause of the sudden battery weakness.
But it hasn't helped - it's still dropping approx 10% each hour while on standby, even on a basic install, without even all the apps I normally have.
To me therefore it logically has to mean a failing battery if a hard reset does not help - or can anyone argue why that might not be true? The only exception I can think of realistically is a hardware fault with the phone.
Have ordered a new standard one anyway, and a hicap 'bulge' battery, so I'll post up if the new one cures it. Quite a few battery threads seem to have no conclusion, so ultimately they're not all that helpful in those cases.
How many other people have had issues like this where the battery life has rapidly gone downhill and a new battery has solved the issue?
Also, has anyone done any tests on their 'dodgy' batteries to see if they are indeed going bad or if it's the phone at fault? For instance (really basic I know) if I were to hook up a light bulb to the battery and measure how long it lasts before it goes dim, then compare it to the results from a new battery, would that be worth trying?
If that's the case it's p1ss poor that a state of the art phone can't even go 6-7months before the battery is junk!
I understand and appreciate that li-ion cells only have a certain number of charge cycles (like most rechargeables) but this takes the cake!
My old XDA orbit is years old, still has its original battery, and that has not deteriorated by any noticeable amount, so these shouldn't either.
See: http://forum.xda-developers.com/showthread.php?t=688496
and let me know if the new battery fixes the problem. I think the batteries might be crap and prone to failing early.
Thanks for the link - sounds exactly the same as my issue.
Hopefully the new battery packs will sort it but that's shocking quality control or product design/testing if these are failing so quickly.
change , Toshiba Tg01 , its better , im using 2 of thems , hd2 and Tg01
made by Japan is better than Taiwanese ,
Enchanter said:
change , Toshiba Tg01 , its better , im using 2 of thems , hd2 and Tg01
made by Japan is better than Taiwanese ,
Click to expand...
Click to collapse
Yeah right. But that has not solved the problems with the 6 month old phone.
What i have not read in the post of Cret is that you took the memory card out and see if that improves battery life. a corrupt file on the memory card causes a huge drain.
try because that also happenns suddenly e.g. after been connected to a computer and not disconnecting properly.
That's a damn good point actually - thanks. I had seen that mentioned in other battery threads yet somehow completely forgot to try it.
I will try and see whether it makes any difference - cheers.
If that should turn out to be the cause of the problem how do you resolve it?
To elaborate - I don't imagine you can easily identify which file would be the culprit, without formatting the card and adding the files back one by one and testing for the fault to re-appear. That's totally impractical, almost impossible with the number of files you can fit on a 16gb card, and the time it would take to carry out that process, so what do you do?
Or is it possible that simply copying them off the card, formatting it, and pasting them back would somehow resolve the issue.
Enchanter said:
change , Toshiba Tg01 , its better , im using 2 of thems , hd2 and Tg01
made by Japan is better than Taiwanese ,
Click to expand...
Click to collapse
How pointless.
wilcovh said:
Yeah right. But that has not solved the problems with the 6 month old phone.
What i have not read in the post of Cret is that you took the memory card out and see if that improves battery life. a corrupt file on the memory card causes a huge drain.
try because that also happenns suddenly e.g. after been connected to a computer and not disconnecting properly.
Click to expand...
Click to collapse
Doesn't this usually result in filesys.exe spiking up to 100% (or just high) CPU usage, though? It isn't doing this on mine, although I'll give it a shot without the SD card. I would expect better battery life without an SD card in anyway, but nothing dramatic.
Cret, let me know if your new battery sorts the problem so I know to buy one myself!
the battery do this only a the begining but after 6 monthes of use it becomes better day after day
hoss_n2 said:
the battery do this only a the begining but after 6 monthes of use it becomes better day after day
Click to expand...
Click to collapse
What are you talking about? Again, you enlighten a thread with useless information. You can clearly see the OP has had the phone for 6 months (as have I) and the battery is failing (as is mine).
Plus, your battery must defy the laws of physics if it gets better day after day. Interesting.
Cret said:
If that should turn out to be the cause of the problem how do you resolve it?
almost impossible with the number of files you can fit on a 16gb card
:
Click to expand...
Click to collapse
What you can try is put the memory card in a card reader and run checkdisk on the card. see if that identify's any problems on the file system
beside of that it seems that the HD2 has problems with 16GB cards, at least quite a few of them. read through the posts.
Id suggest to collect more data about the problem.
The program BattClock lets you check the battery drain in mA. A normal drain for the HD2, with no processes keeping the CPU awake, is 4mA in standby, with only the radio being powered to receive calls.
So, since the battery current value isn't update instantly, right after you wake up form stanby battclock should be showing 4mA (max6-7mA or something lik that) fora few seconds. If that's not the case, and if the drain is way higher than that, then it may be the case that the phone for some strange reasons is draining more current than it should, and it's not a real battery fault.
I had a similar issue, solved it by disabling auto backlight. Set it at 30% and all good since then.
Well, I thought there had been a slight improvement over the weekend with this battery issue but this morning on standby the phone dropped 3% in a matter of 5 or 10 minutes on standby.
So I removed the mcirosd card and in nearly 3 hours since then it has dropped another 4%. That's a big improvement and does hint that the card is the fault, but it's too early to be sure about that. I've put the card back in to see if it begins to drop fast again. If so I'll take it out for longer and monitor it again.
wilcovh said:
What you can try is put the memory card in a card reader and run checkdisk on the card. see if that identify's any problems on the file system
beside of that it seems that the HD2 has problems with 16GB cards, at least quite a few of them. read through the posts.
Click to expand...
Click to collapse
Good idea. I wasn't aware that the phones had problems with cards this size. What about with 32gb ones (not that I can afford one!)?
ephestione said:
So, since the battery current value isn't update instantly, right after you wake up form stanby battclock should be showing 4mA (max6-7mA or something lik that)
Click to expand...
Click to collapse
I did use battlog briefly, but just to keep an eye on the current current amount in use and it was fluctuating a lot just with the phone awake but running no apps. Sometimes it after waking it the phone would show a low figure like you quote but other times not.
I haven't checked batlog out fully in terms of what it's capable of, but what would be great would be an app that can log the current use like that does, but at the same time also log a list of which processes/services/applications are running, then that could REALLY give some useful info.
Eg the log shows normal current use, then spikes upwards when a specific process begins to run.
Cret said:
I haven't checked batlog out fully in terms of what it's capable of, but what would be great would be an app that can log the current use like that does, but at the same time also log a list of which processes/services/applications are running, then that could REALLY give some useful info.
Eg the log shows normal current use, then spikes upwards when a specific process begins to run.
Click to expand...
Click to collapse
make a request for this feature in battclock's thread
The author seems to be quite open to useful suggestions (I, among others, suggested the log-to-txt feature )
Would be a good idea - I like BattClock I must admit. Nice to have the taskbar info like it does.
Ok, later on in the day, it's worked out that it's used 35% battery in approx 3.5 hours of standby - pretty horrendous. Equates to about 10.5 hours (very roughly) battery life on standby. I've checked periodically during this 3.5 hour period and the drop has been steady.
With the card removed, it went 3 hours and only lost 4%, meaning approx 77 hours of standby time at that rate.
Quite a difference between the two.
So at this point it very much looks like there is a fault relating to the memory card.
I'll try some testing tonight. Mainly that will mean I'll first do a filesystem test as suggested. Then delete all the media files, cut the remainder of files and paste them elsewhere, format the card then paste them back, and see how it then behaves.
So it seems now that buying new batteries (and almost slagging off the HTC one) was slightly hasty, but they'll still be really useful, so I'm not at all bothered about that.
Try putting the blank card in, with nothing on it. Would be interesting to see how much juice it draws just having a card in there without reading anything from it.
I have the same issue.
My HD2 worked like a charm, only around 12% battery drain in 24 hours (I could carry it around on standby for one week before recharging).
Now - it sucks around 3% per hour. After one day, I'm at around 25% charge
At first I thougth this was related to Co0kie's Home Tab, but even after hard-reseting, it still drained battery as hell.
At the moment I'm running it without memory card (4GB Kingston) to see if this might be the issue...
I've run a CHKDSK on my memory card just in case, but the filesystem's fine. Any update, Cret?
Well, I'm sure mine was caused by the card, or at least a fault that related to it (ie possibly a file rather than the card itself).
Since I removed the card the battery life returned to normal, so I formatted it, and then copied some of the content back onto it again. It has been back in the phone for a little while now and has been behaving quite well. Basically for instance it's at 77% now at 10.30pm after being removed from the charger around 8am. I haven't used the phone much except to check emails a few times, read a few texts, and go online a couple of times/read RSS feeds a little.
So I'm fairly happy with that.
BUT - not having had the chance to use the phone much (ie mess about) since I formatted the card, I just found that the phone thinks there is no card inside it at the moment for some reason!
I removed it and the PC can read the card and its contents no problem but the phone cannot see it. The only reason I can think of for this is that I formatted the card as NTFS instead of Fat since it's meant to give faster performance, but is it possible that the phone itself does not support this format?
Since it's not working at the moment I'll have to try wiping it and changing it back to fat again.
Yes I have tried rebooting it also.
Next thing is th double size replacement battery I bought arrived the other day. The battery fits ok but the replacement cover that came with it does not fit properly at all.
The cover clips in ok on the side of the volume buttons, but no matter what I do it just hangs loose on the opposite side so I can't actually use the bloody thing since the battery will just fall out like this. Really not happy at all about this.
This is the one I bought:
http://cgi.ebay.co.uk/Extended-2400...eBatteries&hash=item5d2925ce91#ht_1862wt_1137
I think I will be trying to return this for a full refund since there appears to be a design flaw. Normally I would attempt to make something like this fit properly myself but if I failed then I'd have a piece of junk that I could neither use nor return so I think better just to return it without messing about.
It's a shame as the cover actually looks like it should fit perfectly, and seems to fit very well, it's just that it fails completely to latch in place on one side, as if the clip bit is not long enough perhaps.
What concerns me slightly at the moment
Just reformatted the card as Fat instead of NTFS and loaded my files back on and it works now.
So I'll update in due course once I've been using it loaded up again.
Related
When I first got the phone, I could go from 7am to 11pm on 100% and end the day at around 50% (and this is running a stable overclock on BatteryStatus of 260mHz). About a month later, the usage has remained the same, but now I cant even make it past the 12 hour mark without getting in a charge!
The main differences now are that I installed Slide2Unlock and a SMS threading application (the name need not be mentioned).
Can anybody explain what's the deal?
ummm i have to say that im experiencing the same problem about a month and a half after owning the wing...havented installed anything or overclocked
Re:
Well, I'm out of touch with the current Flash days, but if i remember my old computer classes...
I would think, the more data you put on the SD card, and in memory, the more power the PDA needs to use to keep the information in memory, right?
Then again, my information is fairly well dated
BBM-Lee said:
Well, I'm out of touch with the current Flash days, but if i remember my old computer classes...
I would think, the more data you put on the SD card, and in memory, the more power the PDA needs to use to keep the information in memory, right?
Then again, my information is fairly well dated
Click to expand...
Click to collapse
Very true... but this wouldn't apply to me since I'm only using 19MB on a 2GB stick and 22.25MB on my phone's storage.
And Lace, I was hoping somebody had the opposite end of my side. I have installed a number of .cab's and have overclocked my processor. I'm just glad to know that this happened not of my own doing.
freakingwilly said:
When I first got the phone, I could go from 7am to 11pm on 100% and end the day at around 50% (and this is running a stable overclock on BatteryStatus of 260mHz). About a month later, the usage has remained the same, but now I cant even make it past the 12 hour mark without getting in a charge!
The main differences now are that I installed Slide2Unlock and a SMS threading application (the name need not be mentioned).
Can anybody explain what's the deal?
Click to expand...
Click to collapse
if you are talking about the tmobile wing, just call tmobile and tell them about the problem and ask them to send you a new battery, see if that resovles this issue, i'm sure your phone AND battery is still under warranty (1 year)
This happen to mine too, i had to send it in.
they changed the motherboard and the battery
I have searched through XDA and read all the threads regarding the 'suspend process' issue. The specific issue is outlined in Issue # 11126 on the Google Code/Android project home...
http://code.google.com/p/android/issues/detail?id=11126
I am trying to get to the bottom of this, as best as possible. For all intents and purposes, this really appears to be a mystery. Ultimately, it appears as though there is (currently) absolutely no specific reason a to why 'suspend' runs wild until the device is rebooted.
My question is (I know we can all only speculate):
Is there any chance that this could be Google account-specific?
The reason I ask is, I've been doing some "testing," just to try and make sense of this for myself. Here is what I've done/come across thus far...
- My fiancee's first MT4G was a black one manufactured in Taiwan. It had the inferior LCD-SH-C2 screen. Her battery was draining VERY quickly - i.e. before noon, without using the phone for much else other than texting.
- I enabled USB Debugging for her, to "rule out" the init process issue.
- Even though she only had Handcent, Facebook and Angry Birds installed, I removed all of them, leaving only Watchdog.
- I factory reset her phone, twice.
- For all of the above, the device was not rooted. I have since rooted her phone via the steps in this thread.
I'm in the process of creating a new Gmail account for her, exporting ONLY her contacts and then using that account for her new MT4G (Plum) that's scheduled to arrive today. I'm actually thinking of NOT using her new Gmail account at first though, so I can use her original Google account on this new, clean device and see if the suspend issue persists.
I might just be wasting my time, but I enjoy doing this and I don't think it's a complete waste to try and find SOME constant here. Am I nuts for thinking it's tied to the Google account? The Google account seems to be a black box of sorts. There is more than just contacts, apps and settings, yet there is no "window" into everything else that comes down - e.g. I can't log in to Gmail and "configure" it to not restore her wallpaper or WiFi settings. So that's why I say it's a black box of sorts, since it's doing more in the background than we have control over.
Nothing is truly random, at least not in the context of Android and the hardware affected. There has to be some reason why users of various devices, either do or do not experience this issue. Whether it's a specific action or the something that differs between one person's action vs. another person's, there has to be SOMETHING that's triggering this on her device, yet never triggers it on mine. I guess I'm just trying to flush everything out and hope that discussing it will help rule out/rule specific variables.
Let me know what you find. This is driving me crazy! I charge my phone at night, so when I head to work it's at 100%. By the time I'm heading home (4-430pm)... the phone is around 15% battery.
Watchdog tells me suspend ranges from 5%-49% at any given time. I've never had suspend drop below 5% except on fresh reboot. I've noticed, though, after a reboot that the suspend process will slowly work its way back up to using lots of CPU cycles (it starts at, say, .2%, then 10 minutes later its 3%... 30 minutes later its 5%... an hour later its 9%). Battery just gets hotter and hotter due to this.
I'll be checking back to see what you find! Thanks!
mwelliott said:
Let me know what you find. This is driving me crazy! I charge my phone at night, so when I head to work it's at 100%. By the time I'm heading home (4-430pm)... the phone is around 15% battery.
Watchdog tells me suspend ranges from 5%-49% at any given time. I've never had suspend drop below 5% except on fresh reboot. I've noticed, though, after a reboot that the suspend process will slowly work its way back up to using lots of CPU cycles (it starts at, say, .2%, then 10 minutes later its 3%... 30 minutes later its 5%... an hour later its 9%). Battery just gets hotter and hotter due to this.
I'll be checking back to see what you find! Thanks!
Click to expand...
Click to collapse
According to XDA and Issue #11126, you're not alone.
What's really bugging me is that neither my first MT4G, nor its 1st replacement or its 2nd replacement, have ever done this. My fiancee's first phone did this. She is now using my 2nd replacement while she waits for hers to arrive (today). So a device that never exhibited this issue, over the course of at least a week of normal-for-me use, started exhibiting this issue for my fiancee maybe a day or so after using the phone.
I thought I had "solved" it when I didn't see it crop up the first day she used my replacement phone. She was quick to let me know I was incorrect.
So I've got serious pressure here - all of my MT4G's haven't exhibited the out of control 'suspend process' issue while I was using the devices, but with her, it does. <queue the jokes>
We own our own business, so we're in the same room all day long while we use our phones. I was the first to tell her, "it's something you're doing." I'm only repeating myself by saying that I blamed it on an app she installed or something she "did" to cause it. After factory resetting, what...2, 3 times...I'm starting to forget; after checking the apps that are installed (and removing all of them); after verifying every setting from USB Debugging, screen brightness, account sync, etc. I seem to at least be able to say, "every single setting, shortcut, widget, app or usage pattern, does not produce the issue on any device I have used with my Google account, whereas it does with my fiancee."
That's the most difficult part to get absolute - the usage pattern. She's doing such basic things though, but I know that even the slightest of difference can produce different results.
I will most certainly report my results, futile or not.
The only common denominator I've noticed so far is that it only affects Sense UI devices.
Chadastrophic said:
The only common denominator I've noticed so far is that it only affects Sense UI devices.
Click to expand...
Click to collapse
That seems to be the constant, to a degree. I'm seeing people state that they're having this issue on anything from the Samsung Galaxy S (i9000) to a Nexus running Cyanogen 6.1. That's people stating it though, so I'm not sure if they're actually experiencing the same issue or not.
I am biting my tongue, but I think I found another common denominator...I am going to post back in a coupla days once I've seen it last for this entire week.
hi,
i'm running cyanogenmod 6.1 on a desire hd and have been experiencing the suspend process problem exactly as described in this thread a nubmer of times now over the last week. so its definately not limited to devices running sense.
the only circumstances this behavior hasnt shown is when running 2g only with all other sorts of communications and sync off
zero_oli said:
hi,
i'm running cyanogenmod 6.1 on a desire hd and have been experiencing the suspend process problem exactly as described in this thread a nubmer of times now over the last week. so its definately not limited to devices running sense.
the only circumstances this behavior hasnt shown is when running 2g only with all other sorts of communications and sync off
Click to expand...
Click to collapse
Yeah, it didn't seem 100% related to devices running Sense, so thanks for posting back to this.
My fiancee was experiencing this across her first two MT4G devices and has yet to experience the issue on her third and final MT4G. I want to see it run the rest of the week though before I share, but the issue did pop-up for her pretty much within 24-48 hours on her first two MT4G's.
Shlongwoodian: I have been following your posts as the "suspend" process has been affecting me since I received my phone the first day available. However, I am reluctant to send for a replacement as all else is great on the unit I have and there seems no gaurantee that a new phone fixes this issue.
I have tried Tmo and HTC and both seem clueless; therefore, I appreciate your research and look forward to any "fix" short of waiting for Gingerbread.
Anyone have any wisdom to pass on? This issue is driving me crazy! I've noticed it most on my black MT4G (w/the good screen) after browsing the web, youtube or using the media player. My wife's red MT4G (w/the inferior screen) has had no issues and her battery is amazing! The first day she got her phone her battery lasted 24 hours without even conditioning it! Granted she doesn't use it like I do mine, but it is still a huge difference. When this issue comes up on mine, I'm dead within 3-4 hours. I have Watchdog set so when it alerts me I just soft reset. That clears it up until it decides to come back at random intervals. It usually doesn't come back until I open the browser, etc. With as much as I use my phone (I am constantly on the road), it becomes a major pain to have to constantly monitor battery life. Any help is greatly appreciated!!!
Man, I am sorry to report that I gots nothin'. Ok, here was my original theory...
I was speculating that "something" inside the Google/Gmail account was the cause. My reasoning being, essentially, your info is stored in a database. When you get an Android device, that online database is synced locally with the phone's database. We each have different databases and there is more than just your apps, Market links, contacts, etc. I never exhibited the /suspend issue on phones that she experienced the /suspend issue on. I figured it was database-specific.
If a table contains a value, or rather, does not contain a specific value (or if columns are missing, etc.), it can cause an application to respond in a negative way. Sometimes, this causes an error to bubble up in an application. Other times, it doesn't. In my experience, I've seen much more subtle issues in databases, that don't cause errors or a crash, but instead just cause "undesirable results."
When my fiancee got her final, good replacement Plum Glacier, we started with a completely new Google account. We thought we nailed it, when a handful of days passed without seeing /suspend get out of control, leading to Android System and/or OS sucking down battery life. I think it was nearly a week into it and one day while she was out, she realized she lost battery life really quickly - i.e. left the house with 90% and by the time she got to the store, shopped for a bit and looked, her phone was down to like 30-40%. She knows how to check for /suspend and it was, of course, back.
It's still not something that can be completely ruled out, since it's not a very air-tight test. There could be something about my Google account (which I've had pretty much since Gmail beta was available) that's keeping me (and others like me) from getting it or that idea could be crap.
For some reason, I have never, ever seen this happen on my Glacier(s) running stock 2.2.1. Phones that I never saw the issue on, she saw the issue on. There is so much speculation around it, but it just seems like "some people" don't experience it and "some people" do. It's all over different devices, different skill levels, etc. No apps, same apps, whatever and it happens to some but not others.
Sorry to get anyone's hopes up. I'll keep looking for differences/similarities though and if I find anything at all I'll - or if anyone else finds anything, no matter how ridiculous it sounds (yes, we've tested the 'rock' and it doesn't appear to suffer from the /suspend issue) - post it here.
Thanks for trying! It was a good theory. So . . . now what? Is there any way to get this ranked higher with Google, HTC, etc. to get more people working on it? It is really driving me nuts! It mainly happens after I use the web browser, then put the phone on standby for some reason. I can't even use the browser any more without needing to reboot it to save battery life. There is another thread, but specifically for the Evo and I think one for the Nexus one, all with the same problem. What if a new thread were started that is not device specific? That way we can get more people to star it and maybe Google or whoever will pay more attention to it! I would hate to think that we are stuck with this problem until when and if we get upgraded to 2.3. I would suggest rooting and flashing a new ROM, but even those with custom ROM's are having the same problem, so that's not going to help. Thoughts???
jpiano said:
It mainly happens after I use the web browser, then put the phone on standby for some reason.
Click to expand...
Click to collapse
It truly is a mystery to this day. I've seen people say, "it happened right after I installed Handcent" or "it happens as soon as I do..." No one has come up with any concrete evidence thus far.
My fiancee has Handcent, I have Handcent. I used Handcent heavily, never had an issue. She stopped using Handcent - still has the issue. We've gotten so granular in our troubleshooting, we're literally tracking every step. LOL i.e. I pressed the trackpad to wake the phone, once; I unlocked the phone, I swiped my thumb once to view my Watchdog Widget on the screen to the left of my homescreen, etc., etc., etc.
So, for now, we just wait? My phone (and all previous phones) have been just fine. My fiancee however...yeah, I'm trying to find a fix pretty quickly.
One common theme that I've seen with this issue is that it only happens after I put the phone to sleep. I have never seen it crop up while actually using the phone. Maybe we're going about it the wrong way in trying to identify an app, etc that's causing the problem... perhaps it is simply the code involved in putting the phone to sleep and that's why there hasn't been any consistency with what one does to make it appear. In your experience, have you ever seen or heard of it showing up while the phone is being used? Perhaps it's just on mine that it works that way, but I thought it was worth mentioning. I know nothing about code or how android works so please forgive the noob comment if this is an obvious one. Merry Christmas!
I've got this problem big time. Returned my first phone because I thought it was the phone. First few days were good but lately its back and as bad as ever. First thoughts were angry birds twitter or wifi but I have no idea. If I can't figure this out I might have to sell this phone.
I will try to post some more thoughts. I think you're onto some good ideas here.
Sent from my HTC Glacier using XDA App
(Re-posting from the developer's Google blog where others are following this issue): Interesting about using the phone without a Google account. Not sure if this is relevant or not, but I've noticed something else with consistency. Granted I wasn't able to document the behavior through system panel at the time, but this has consistently happened. When suspend goes crazy, I can get it to stop simply by charging the phone! Even if I charge the phone for a few seconds, then unplug, it stays dormant without having to reboot. Noob speaking here but perhaps the part of android that actually logs the battery usage is suspending when the phone goes to sleep? When it us charging, this log is reset and clears the process from running. If this is even possible, then could someone write an app that clears this system log? Maybe by mimicking what happens when the phone is charging, we can at least temporarily clear the issue without the need tovl reboot? Again, I know nothing about all this so sorry if this is all irrelevant. Just sharing what I've noticed to be consistent. Thoughts??
Also, I saw on another xda blog (http://forum.xda-developers.com/showthread.php?t=870557&page=2) that someone linked this issue to a corrupt photo on the sd card. After formatting the card and restoring some files, says the issue has not returned!
jpiano said:
Also, I saw on another xda blog (http://forum.xda-developers.com/showthread.php?t=870557&page=2) that someone linked this issue to a corrupt photo on the sd card. After formatting the card and restoring some files, says the issue has not returned!
Click to expand...
Click to collapse
I wonder if you're on to something with the SD card. I've been thinking I haven't seen the suspend issue return on my phone in quite a while. I just realized that the only thing I've really changed is installed a new 16 gb SD card. Since then, no suspend process problems. For those who are having the problem still, I wonder if removing or formatting their cards would show any improvement? Worth a shot if at least to eliminate another possible factor.
Sent from my HTC Glacier using XDA App
That's cool that this thread is flushing out other ideas and possible variables. I like the idea of connecting it to the charger for a couple of seconds, but my fiancee is so used to just rebooting her phone each morning and sometimes again by mid-day, that it's easier for her to do just that.
jpiano said:
Even if I charge the phone for a few seconds, then unplug, it stays dormant without having to reboot.
Also, I saw on another xda blog (http://forum.xda-developers.com/showthread.php?t=870557&page=2) that someone linked this issue to a corrupt photo on the sd card. After formatting the card and restoring some files, says the issue has not returned!
Click to expand...
Click to collapse
I like the microSD Card notion. This is such a weird issue, that it's so easily associated with other items - e.g. applications, usage patterns, etc. This seems feasible though, but the only way to know for sure is to reproduce it. My fiancee experiences the suspend issue daily, if she doesn't reboot regularly. So, I should be able to take her microSD card and use it in my phone and get the suspend issue. I don't want to 'muddy' up by swapping microSD cards, so I'll try reformatting her card and see if that makes any difference. She usually sees the issue within 24-48 hours of a fresh boot, so it shouldn't be long before we see if that fixes it or not. I can check the card for errors, etc. as well.
werk said:
I just realized that the only thing I've really changed is installed a new 16 gb SD card. Since then, no suspend process problems.
Click to expand...
Click to collapse
I'll be upgrading to a 16 GB Class 10 soon, so I can give her my Samsung if need be. I'd really like to see if this is it though. It would explain the "some people get it and some people don't" pattern.
I also noticed that the minute I plug the phone in the problem goes away. Not sure why, just confirming it happens to me too. I also should note that when I returned my phone, they popped my old SD card into my new phone. So if there is an SD card issue with a corupt file/photo that could be something as well. I wonder woody if your girlfriends phone has had the same SD card after how many times did you say you traded it in? BTW, a side note, how did you exchange it so many times? After I took mine back to the store on day 14 they told me I wasn't able to exchange it again.
I do have a 16GB SD card but just haven't had time to install it. Wanted to double check which things I need on the new one from the old one, but it might be a good way to test this issue. Let me know some ideas before I swap the cards and maybe I can help test this.
Also, one more thing, what is the app you're using to log stuff? I'm just using Watchdog Lite right now.
I've got to figure this out or this is a dealbreaker for me. I have waited 3 years to upgrade phones, first time on Android, really wanted iPhone but wanted to stick with month to month from TMob. If this continues I think I will move to Windows Phone 7 or iPhone if I have to, but I really like this phone when the battery is not draining like a leech.
Thanks.
werk,
Just wondering what process you went through when you upgraded SD cards. Did you copy any files over to the new one or just start blank?
Thanks.
royhobbs said:
werk,
Just wondering what process you went through when you upgraded SD cards. Did you copy any files over to the new one or just start blank?
Thanks.
Click to expand...
Click to collapse
Just straight copied the existing files over from the old card to new one (new one in phone connected via USB, old card in SD adapter in my laptops SD card slot). I think some Angry Birds files didn't make it due to long paths, but reinstalled it and no problems since then.
Recently on every build i use the display is taking up about 80% of the overall battery use i use it moderately but it only lasts about 8-9 hours. I looked on my battery usage and over the 9 hours my screen had been on bout about 50 minutes but had used 80% I have it on lowest brightness and have set it to turn off after 15 secs. Anybody else having this issue or know of a way around this. Also use setcpu with screen off settings and current widget is showing around 3-6mah when in standby.
Nobody else experiancing this?
I've had this issue in the past. Check this thread out, its a POSSIBLE reason why the screen is draining the battery. Basically the proximity sensor keeps running constantly when it should only activate during phone calls. In winmo the proximity sensor behaves correctly and turns off once you've hanged up. I'm hoping devs notice this and can hopefully find a fix for it
http://forum.xda-developers.com/showthread.php?t=870149
P.S. try installing system panel lite, just in case a rogue app is draining cpu constantly in the background even when your screen is off
Hmm no I'm pretty sure it's got nothing to do with the proximity sensor, this is a way more serious battery drain.
I suggest trying another build, maybe you're using an outdated one? If not, try reformatting your SD card (full format, not the quick one), changing radio and changing WinMo. You don't have to do them all at once, it may very well work after just one or a couple of these steps.
StephanV said:
Hmm no I'm pretty sure it's got nothing to do with the proximity sensor, this is a way more serious battery drain.
I suggest trying another build, maybe you're using an outdated one? If not, try reformatting your SD card (full format, not the quick one), changing radio and changing WinMo. You don't have to do them all at once, it may very well work after just one or a couple of these steps.
Click to expand...
Click to collapse
Its strange as its doing it will all builds i have formatted my card several times i have tried several new builds also swapped radios, done task 29 and tried several wm roms bit confused by it as some people are saying they get a days use and i dont not even in aeroplane mode :/
Jammie_1989 said:
Its strange as its doing it will all builds i have formatted my card several times i have tried several new builds also swapped radios, done task 29 and tried several wm roms bit confused by it as some people are saying they get a days use and i dont not even in aeroplane mode :/
Click to expand...
Click to collapse
That pretty much leaves out one option: try another SD card. Not all cards are equally optimal for Android. Just borrow one from a friend, and check if it makes a difference.
Hi all,
A few of us on the SD card list thread have tried this and it seems to be stablizing things....the theory as we are working with now is that the problem is due to a power control issue in the Samsung drivers for the phone, not especially in the card itself.
No ill effects have been reported as of yet, and the battery life seems to be on par with before the switch was made. It is a simple fix, and can be reversed easily.
I ran the phone for 2 months without a card, and with these keys toggled, it is actually FASTER than it was. I don't fully believe it, but it has been over a week and rock solid.
First off, you need to dev unlock your phone. See the thread here for simple and complete instructions: http://forum.xda-developers.com/showthread.php?t=938106
Next off, you need to toggle the following 3 registry keys in the Registry Editor provided in the above post:
The keys have to do with MMC (internal memory) power management.The big speed improvements is in games/apps (Fruit Ninja opens and operates leaps and bounds faster than it did when the phone did stock!)
Code:
HKEY_LOCAL_MACHINE>Drivers>SDCARD>ClientDrivers>Class>MMC_Class>DisablePowerManagement (Change to 0)
Code:
HKEY_LOCAL_MACHINE>Drivers>SDCARD>ClientDrivers>Class>MMC_Class>High_Capacity>DisablePowerManagement (Change to 0)
Code:
HKEY_LOCAL_MACHINE>Drivers>SDCARD>ClientDrivers>Class>SDMemory_Class>DisablePowerManagement (Change to 0)
One point of note here, do not be afraid if the phone locks up the first time soft resetting after these changes, mine did and it was fine after a battery pull.
Also, I would be interested to hear any theories about why this one made such a big difference when it seemingly affects only the internal storage. Maybe because the two storage devices are "bridged" by WP7?
Comment below with your experiences please!
If this gets enough test results, we will submit it to Microsoft. Thanks!
As I already mentioned:
Up to now I just did the SD card registry hack. The device is now stable for over 3 days, longer than ever before.
Battery life wasn't noticable affected, lasted for around 40h with moderate usage (thumbs up indeed).
In fact without this registry hack I wasn't able to get down to an empty battery without those reboting/dataloss issues.
But I need some more days, then I will change the MMC registry key also.
No speed improvements mentioned up to now.
I applied the hack to all three keys. So far, it is much less laggy. Not sure if that will return after 4+ weeks as before, but here's a pretty cool side effect:
After the hack, my screen does not stop responding to touch when the phone is placed on my desk or a soft surface, like a couch cushon. It was getting really annoying because I often place mu phone on my desk during the day for easy access, but every time I tried to onlock it, it would not respond unless I picked it up. Sometimes, it's nice to leave it lying down and operate it. Couldn't do that before, but I can now! WooHoo! Thank you for this.
I'll report back if it starts up again in a couple weeks.
Sent from my Focus WP7 using Board Express
Whoa! I just tested this and you are correct! More proof that the Samsung power drivers are full of problems. Who would have thought?
For testing purpose I changed the MMC Keys also and made some Videos (no I won't upload them). There were absoluteley no differences in app loading times (ok, i know the longer loading apps are pretty much all stored on the sd card, ) and also not in overall performance, although this isn't provable easily.
I changed the keys back to normal, but kept the sd card key change to 0.
I address the positive speed effects to sdcard key for now. Perhaps i will make some tests without any reg change in the next few days.
Still stable as hell!
Edit: Damn I forgot to test the not responding problem (even though i didn't notice it that often and badly)
Sebo1985 said:
For testing purpose I changed the MMC Keys also and made some Videos (no I won't upload them). There were absoluteley no differences in app loading times (ok, i know the longer loading apps are pretty much all stored on the sd card, ) and also not in overall performance, although this isn't provable easily.
I changed the keys back to normal, but kept the sd card key change to 0.
I address the positive speed effects to sdcard key for now. Perhaps i will make some tests without any reg change in the next few days.
Still stable as hell!
Edit: Damn I forgot to test the not responding problem (even though i didn't notice it that often and badly)
Click to expand...
Click to collapse
As I mentioned above, I'm hoping it's not just a result of resetting something and it still returns in a few weeks. Although, the thing about the screen touch response not working when laying on something is COMPLETELY GONE! That alone is worth the setting change. It really was annoying for me the way I use the phone. Thank you to eveyone involved in finding this setting.
PS: From my perception, I don't believe my battery is behaving any differently. Although, I would imagine if it were scientifically tested, it surely would be using slightly more juice. But it still had the normal amount left in the evening, and I probably used it slightly more testing it out. Maybe getting the screen to perform better uses less power?
For the sake of completeness: I set the sd card key back to 1, and I do not experience any slow down in overall performance or in app loading times. Still I cannot reproduce any of those not responding issues you mentioned.
For today and tomorrow I will stay with this setting an will wait for a random reboot. Let's see what and when it happens.
tried this with a 16gb class2 sandisk... loaded it up to 9.25 left and the reboot monster came... but it was weird... it would rebllt like every 30 sec with no loss then poof all lost...then rendom self reboot all mem would reappear and start the reboot process all over.... now it didnt do this till it was unplugged.... plugged in it was fine... reformatted... re set up did the tweak... loaded and the same as before... so for me no... but im going to test it with another card on the list... heres to hoping....
but it does fix the sitting on the bed and unresponsive gimmick.....
So would this be worthwhile even for someone without an sdcard? For the screen response issue i mean. It's so annoying haha.
edit: Screw it i went ahead and did it hah. It def fixed the touch screen responsiveness issue!
Which cards?
Can you guys post the specific SD cards you are testing this with. I am curious to see if somebody has tested it with the Sandisk class 2 32gb card. Thanks.
knwldg0010 said:
Can you guys post the specific SD cards you are testing this with. I am curious to see if somebody has tested it with the Sandisk class 2 32gb card. Thanks.
Click to expand...
Click to collapse
Sebo's testing with a SanDisk Class 4 32GB card which ended up being more stable (before it failed and before he tried the registry stuff) than the Class 2s from Sandisk.
Based on what you have read, would it be best to get rid of the class 2 32gb card or wait to see if there is an actual fix? Since this seems to be a power issue based on the fix, does it really matter what class it is then? Thanks.
knwldg0010 said:
Based on what you have read, would it be best to get rid of the class 2 32gb card or wait to see if there is an actual fix? Since this seems to be a power issue based on the fix, does it really matter what class it is then? Thanks.
Click to expand...
Click to collapse
Something to keep in mind is that this registry hack is relatively new. Some people managed to go for weeks without issues on an unmodified WP7 with a card. It's entirely possible that these hacks are just a stopgap, or a reset, and actually *fix* nothing.
Theoretically, the card shouldn't matter. If I hadn't locked my 32GB Class 4 Kingston to my old (bricked) Focus, I would try it with the current one and see if doing the registry tweaks fixes the slow sync issue on it. Someone in the SD Card List thread claims to have done the registry tweaks and it ended up failing badly too with a 16GB Class 2 Sandisk. However, the 16GB Class 2 Sandisk is one of the more reliable ones (without tweaks) through the limited testing this board has done, so it's possible he has a bad card.
In brief, it shouldn't matter (within reason) what brand/class/capacity you use. If this tweak is the real deal, it should work, especially if your only concern is random reboots. However, you still would want to avoid cards with extremely high class ratings at typically their random read/write is slow (which the most common usage of the storage in WP7). In terms of performance, there's no guarantee as to what these tweaks will do as the only consistent change has been that phones that would constantly reboot due to their cards aren't (yet).
However, to answer your initial question, I don't believe anyone has tested a Class 2 Sandisk 32GB card. I wouldn't put too much faith that your card will have the exact same results as Sebo's class 4 because we aren't certain what the cause is. We believe it's power, but we're not 100% sure. If you're already using the card in your phone, you don't really have much to lose. If you're not using it yet, then you only have something to lose if you, like me, don't have a Nokia/Symbian phone that you can use to reformat the card if it fails.
Good post fishface.... That's where most are thinking its a fix.. This is just a theory right now.. That's why there's another post wanting testers... my find was it did fix the sensitivity issue...theres no doubt on my end.. But card wise my 16gb class2 SanDisk worked before I tried this until I hit 15gb used... Then it went goofy... I tried it 5 times.. Same thing. Just about 15gb used was where the instability happened. Soon as the reg hack hit I read thru it.. I love reg edits.. Made my Omnia 2 &hd2 quite decent phones... That's when I saw the mention of others thinking this too.. So I took my 16gb class2 SanDisk that I freshly brought back to life, and decided to test it out... I posted the results before... Plugged in no issue.. Unplugged it went goofy at 12.7 used... I was stable at that point before without the edits... Not saying it doesn't help but it made mine worse... I'm still going to try other cards though .. I do think there is something to this... I might try different scenarios of the edit... What's it going to hurt..i mean were here for the same goal to help find a solution... Well except the lurkers..you all know who you are..lol. But again. Great post fishface...
Thanks for all of the info. I guess fix is the wrong word to use, but i was just trying to get an idea of what others have done. Whenever i would pass the 10gb mark, mine would do a full wipe after a couple of restarts. I still have my 32gb card in my phone, because there really is no point of taking it out and possibly loosing it. Plus i was hoping an official fix would come out so i could just apply the patch. I have been waiting to see when the MS update would come out so i could do a full backup before running test. Thank you for your help.
anyone tried messing with block sizes? Default is 128. I'm wondering if maybe your sd card has trouble with that block size its causing the lagginess. Who knows lol....
Sent from my SGH-i917 using Board Express
Also I'm still using my 32gb Kingston class 4. I have all 3 keys set to 0. And its still going strong other than that one reset I had. MMC block size 128 sd block size 128. If my sd card can't handle that large of a block size I would have instability.
Sent from my SGH-i917 using Board Express
Anyone know if this also fixes the song stuttering issue? That's definitely power related since it only happens in the last couple of seconds of a song if the screen is off. One you turn it back on, the music plays perfectly.
jeffgeno said:
Anyone know if this also fixes the song stuttering issue? That's definitely power related since it only happens in the last couple of seconds of a song if the screen is off. One you turn it back on, the music plays perfectly.
Click to expand...
Click to collapse
I haven't had a chance to test that yet but I'll post if I have any issues
Sent from my SGH-i917 using Board Express
I'm stuck. Made it through the first three downloads and have my phone unlocked.
Followed Registry Editor link and downloaded RegistryEditor 1.1.0.0.xap. My computer will not open up this file because it doesn't know what program to use, so I tried to download it straight to my phone and my phone says it doesn't support xap. What steps am I missing?
How do I get into the registry to change the three tabs?
For about 2 months since I have owned this phone it has given me nothing but crap. I always kept my G1 in my pocket and I always dropped it, even had it in water 3 times! (never had any problems) The G2 however if I kept it in my pocket, dropped it, or open/closed the keyboard repeatedly the phone would shutoff! Very Very disappointed at first. I missed many calls and text messages.
So How come NOW I can drop it, open/close the keyboard repeatedly, and keep it in my pocket without it shutting off?
I did a little investigating of the battery and contact points on this phone, it turns out that there is room for play with my battery. SO every so often the contacts would lose connection with the battery!
TO fix this I put a small piece of folded paper along the top edge of the battery opposite of the contact point to the phone, it made a more secure and snug fit to the contact points.
The battery does get Hot so I do not recommend this as a permanent fix as it is now a small fire hazard.
BUT, to this day I have had ZERO problems.
I am sooooo now with my G2 any questions or other comments please leave them below.
CYANOGENMOD 7 RC1
Class 10 4gb microSd
1500MAH battery
Hard rubberized black graphic case
Talk about going backward! I remember the old nokia 5160s that everyone and their brother had folded up paper in the batteries about 10 years ago! LOL
SySfS
Meh... I don't think anyone else has this problem. If they did then they probably exchanged it.
Sent from my T-Mobile G2 running Cyanogenmod.
I have this problem.
I can't exchange it because I bought the phone on ebay.
If you search through the threads and on google, quite a few people experience this random freeze / shutdown where you have to do a battery pull.
I've tried flashing different roms, using only basic apps etc...
I don't think it's software related anymore, and if it is, it's too hard to diagnose. Many suggestions have been made, micro sd card slot, battery connections, software, weird app, different rom... I haven't tried removing SD card yet and my battery connection seems ok, it's pretty tight in there...
Don't know what the problem is and I wish someone could figure it out as it's frustrating to drop too much $$$ on a phone and have it act this way.
Random Reboots
I have a similar problem with my G2. It randomly reboots when its siting stationary on my desk or in my car.
This problem is made stranger though because it NEVER does this while I'm using it!! If I have it playing Pandora or Youtube - no reboots. But, like clockwork, if turn off the screen and set it on my desk, reboot... never fails... it will reboot 2 or 3 times then seems to be ok for a little while. Very annoying because I can't make or receive calls while its doing this.
Like others I've read plenty of posts on this but no working fix I can find. Some people say they returned their phone 2 or 3 times and still have the same issue. Some people say its related to signal strength but it does this will full bars or no bars.
I've tried custom Roms: CM6.1.1, CM7-RC1, & Virtuous 1.0.1 and the problem remains.
Does anyone know how to fix this? This is the only negative about an otherwise HOT little phone.
At least yours reboots! A lot of others just freeze (like mine)! And then you don't even know it.
I'm trying out another theory... Installed CM6 a few days ago. Had the same problem.
But I just started OC using CPU Tuner and the stock CM6 Kernel., the lowest option I have for clock speed is 700 something for some reason, so I just used that. So far, 36h, hasn't done it. I THINK, it might be related to the phone not getting enough juice for some odd reason - even on stock, so when you OC it and set a higher clock speed for idle, it might help. NOT sure yet but testing. Will post up if it "fixes" the problem for me.
My G2 was randomly shutting off a lot, usually right after I stuck it in my pocket. The solution? I exchanged it. The new one never does that XD
Possible fix for random reboot
I think I may have found a working fix for my random reboots. Credit goes to the OP.
I installed the Pershoot kernel and since then I haven't had a reboot and up until now it has rebooted like clockwork.
I'll see how it goes.
I had this problem while using the Red ChiChi/EVO batteries, but I believe my problem to be with the back cover. I might have dropped it and the cover got slightly tweaked, or perhaps it was the chichi battery, as it wasn't exactly a perfect fit. If a certain spot on it gets touched or pushed in, the battery loses contact with the pins and kills the phone. I have to pull the battery and let it set for a minute b4 putting it back in and powering up.
I used the same method, with a piece of folded paper on top for a while.
Perhaps its a different problem than the OP, but this only happened with my ChiChi batteries. With stock battery, it always seemed to be a good enough fit, and the corners kept it in place.
I ended up buying an extra stock battery for around $20, and now I carry 2 Stock batteries at all times.
Solution finally?!
I think I found the solution for my phone:
set OC profiles so the phone doesn't go below a certain mhz threshold.
On CM6 stock with CPU Tuner, it defaults to 700mhz lowest. Did not notice any increase in battery drain.
Uptime - 70 hours. Finally fixed!
//UPDATE: I did experience a freeze around the 100 hour mark, but so far that's the only one in the last week or so. In any case, it's doing MUCH better than before...
//OK I lied it still does it but so far just once or twice a week. Better than once a day.
So far there are apparently three problems/solutions:
- Micro SD slot loose connection / improper close - Check micro SD card slot
- Idle voltage too low, freezes phone / use OC kernel and set screen off speed higher
- Bad battery connection / manually fix
After many tries and diagnosing I think one issue is that on stock settings, the idle / screen off profile is set too low, which can freeze the phone (although I did have it freeze once while I was actively texting... not sure why). But 99% of the time it happened with the screen off. Hopefully it doesn't happen again, will keep phone on to see, but I don't remember it going more than 48h without freezing lately.
I have tried the following which did NOT fix the issue for me:
Micro SD check
Uninstall programs (skype, launcher pro, various others)
Revert to "stock"
CM6 "stock"
Checked Battery
Used stock battery / China battery
All those solutions still led to the random freeze / battery pull situation, but could potentially work for you.
2 G2's did the same thing. T-Mobile states known problem. After 14-hour shut down pulled mSDHC card and Sim and replaced battery which was drained in the off-state.
Solved problem and bought a Nokia N8.
Customer Service at T-Mobile and HTC is totally unconnected and unresponsive. Their answer wait for the FOTA.
Hope they don't send it to my Symbian ^3 jewel!
Was Shutting down multiple times a day - FIXED!
Hey Guys,
I've purchased my G2 from ebay so was not able to return it. So I've been trying to fix this problem for ever.
I have not found anything that works until now (knock on wood).
I installed the Cyanogenmod (cm_vision_full-32.zip) and updated my older CM version. The phone has not shutdown once in 4 days, which is a first.
Note: my GPS does not work with this version. I'm about to try a clean wipe to see if it will activate. I'm guessing however that the shutdown issue is 100% tied to the GPS so if I'm successful the problem will return. If a wipe does not work I'll try new radios.
I'll update any progress.
-Pappi23
lost800 said:
I have this problem.
I can't exchange it because I bought the phone on ebay.
Click to expand...
Click to collapse
Caveat emptor.
I know. Live in Canada and only way to get the phone.
Me too, although my phone is at uptime: 211 hours right now
CM6 with cpu tuner with the settings posted above... basically make sure it never underclocks below 700 mhz.