Related
discuss. as far as i can tell its related to the battery driver and only occurs while charging on AC. have not experienced it on USB charging off pc/other. baseband update failed to correct the issue. change of cm7 nightlys does not solve the issue. changing kernals "faux made it sod and overheat like hell" trinity is untested. alternate roms are so far untested "most are based off cm7 anyhow so i dont see trial and error for other roms being worthwhile. some claim keep awake while charging solves the issue since the phone will not sleep during charge. believe cm7 has this removed unfortunately.
Solace50 said:
discuss. as far as i can tell its related to the battery driver and only occurs while charging on AC. have not experienced it on USB charging off pc/other. baseband update failed to correct the issue. change of cm7 nightlys does not solve the issue. changing kernals "faux made it sod and overheat like hell" trinity is untested. alternate roms are so far untested "most are based off cm7 anyhow so i dont see trial and error for other roms being worthwhile. some claim keep awake while charging solves the issue since the phone will not sleep during charge. believe cm7 has this removed unfortunately.
Click to expand...
Click to collapse
I was getting the SOD whenever my phone would go into standby... Never when it was charging
Sent from my LG-P999 using xda premium
I had a lot of reboots when charging on AC too.
Sent from my LG-P999 using XDA Premium App
i had a similar issue as well with the phone would just shut off. making the assumption its related to the 15% shut off bugg since when i turned it on "not a sod" it showed not 100% battery despite it was on the charger. this only happend if it was left on charger for a long time. random reboots in cm7 nightlys was solved a while ago opposed to SOD/random shut offs. that or the baseband update solved it
Solace50 said:
i had a similar issue as well with the phone would just shut off. making the assumption its related to the 15% shut off bugg since when i turned it on "not a sod" it showed not 100% battery despite it was on the charger. this only happend if it was left on charger for a long time. random reboots in cm7 nightlys was solved a while ago opposed to SOD/random shut offs. that or the baseband update solved it
Click to expand...
Click to collapse
The baseband has nothing to do with reboots or SOD's.
Sent from my LG-P999 using xda premium
I have 2 G2x, both afflicted with "get hot near camera with SOD with significant battery drain" issue. Rebooting once a day fixed it for both phones. Our SODs would happen randomly - always with screen off, usually NOT on the charger. I charge on USB, she charges on A/C adapter. My wife doesn't always reboot, so I installed setCpu to limit screen off cpu usage, and also installed watchdog lite. So far watchdog lite has had only one hit - from "Linux Process' using 51% cpu - but no SOD.
The only reason I am on this forum is due to SOD - my wife is on-call, and NEEDS a phone, not a brick. the G2x ROCKS, except when it is a brick - then it SUCKS!
My goal is to either
A) find the SOD problem
B) have the SOD problem GO AWAY.
I am interested in any input or organized testing to fix this problem.
SOD? Sleep of death? Sorry, been away from xda for a bit.
My current issue (with 2 phones, and the replacement unit has this after 3 days.) is sometimes that it refuses to charge until I do a battery pull. Once my first g2x (the second i've owned. 3 total) got so low it wouldn't boot or charge and no battery pull would work for a couple days. Got a new one mailed to me, same problem.
I'm really considering demanding an upgrade, maybe to Sensation. Sorry if off topic, but don't want to go posting duplicate topics.
Sent from my LG-P999 using XDA App
My sensation currently has a power drain that I can't seem to find the cause for. I'm using InsertCoin 3.4.2 with bricked kernel 1.5, using SPB shell 3D launcher, got an Anker battery, running tasker to cut data, wifi, gps, etc whenever the screen is off, setCPU running ondemand with max at 1536mhz and minimum 192mhz, etc, etc.
I fully charged my phone to 100% about two or three hours ago, and it's been pretty much left alone since. It's now down to 68%.
I've got BetterBatteryStats and SystemPanel, both showing nothing untoward, no active tasks, no wakelocks from what I can tell, etc. And according to the standard app for battery monitoring, it shows the various connections have indeed been turning off as intended, and the phone has been asleep nigh on all the time it's supposed to be.
Any ideas what's going on, or how I could look into it deeper?
I've just been playing with the phone pretty much non stop since I started this thread an hour ago, and the battery level is now at 60%. So that means it's actually consuming MORE power when it's not even in use!
StuartTheFish said:
I've just been playing with the phone pretty much non stop since I started this thread an hour ago, and the battery level is now at 60%. So that means it's actually consuming MORE power when it's not even in use!
Click to expand...
Click to collapse
Hi,
There is a lot of talk about battery consumption,and it's causes.
Most people will suggest trying a different kernel,or downclock it to 1.2 GHZ.
I've tried different kernels already, and underclocking the cpu seems to make little difference. As I say, setCPU should be knocking it down to 192mhz whenever the screen is off anyway!
StuartTheFish said:
I've tried different kernels already, and underclocking the cpu seems to make little difference. As I say, setCPU should be knocking it down to 192mhz whenever the screen is off anyway!
Click to expand...
Click to collapse
Hi,
Is your ROM a 2.3.4 base or 2.3.5 ?
2.3.5 mate. It's InsertCoin 3.4.2, with sense 3.5 (which I'm not using in favour of SPB).
StuartTheFish said:
2.3.5 mate. It's InsertCoin 3.4.2, with sense 3.5 (which I'm not using in favour of SPB).
Click to expand...
Click to collapse
Hi,
I was going to suggest bricked 0.9.1 with a 2.3.4 ROM,because my son has had great results on his Sensation.
I do not know IC well enough to help.
Sorry.
No problem, thanks for your input anyway.
StuartTheFish said:
No problem, thanks for your input anyway.
Click to expand...
Click to collapse
1)Try his new test version of bricked(beta4).
http://code.google.com/p/bricked/downloads/list
2)Charge to 100
3)Turn off, wait till green, unplug and plugin(bump charging)
4)Boot to recovery thru bootloader and wipe battery stats and then reboot unplugged
Drain you battery to 1, then charge up and repeat for a few days. And you can lower the clockspeed since you're using ondemand, you won't see a speed difference with 1.2 and higher. Oh and use ultra smooth rosie so the home will be faster...And see which apps are open in B/G.
http://forum.xda-developers.com/showthread.php?t=1302914
With the exception of trying the beta bricked kernel, I've already done all that when I first got my anker battery. It's not a calibration issue, it's that something is actually draining the battery even when it should be asleep.
And that rosie change isn't needed, as I'm not even using sense in the first place. I've got no real issues with how the phone actually performs as everything is already perfectly smooth. The only slight issue I have is since flashing the amaze camera, on rare occasions it can lock up when exiting it, requiring a battery pull to get going again.
StuartTheFish said:
With the exception of trying the beta bricked kernel, I've already done all that when I first got my anker battery. It's not a calibration issue, it's that something is actually draining the battery even when it should be asleep.
And that rosie change isn't needed, as I'm not even using sense in the first place. I've got no real issues with how the phone actually performs as everything is already perfectly smooth. The only slight issue I have is since flashing the amaze camera, on rare occasions it can lock up when exiting it, requiring a battery pull to get going again.
Click to expand...
Click to collapse
Oops missed the part about SPB, I have been having similar issues but with Faux's kernel after using Amaze cam, but I doubt that could cause sleep drain. I think you drain is caused by the phone not entering "Deep Sleep", some rogue app is keeping the phone partially awake and sucking up juice. I'm gonna go on a hunch and say the phone is running around 1.x GHz while screen if off due to the app.
StuartTheFish said:
With the exception of trying the beta bricked kernel, I've already done all that when I first got my anker battery. It's not a calibration issue, it's that something is actually draining the battery even when it should be asleep.
And that rosie change isn't needed, as I'm not even using sense in the first place. I've got no real issues with how the phone actually performs as everything is already perfectly smooth. The only slight issue I have is since flashing the amaze camera, on rare occasions it can lock up when exiting it, requiring a battery pull to get going again.
Click to expand...
Click to collapse
Hopefully mine can help you. I also noticed HUGE battery drain issues in the past using Bricked Kernel, so I then reverted to stock. Battery was GREAT, but the stock kernel blows. So yeah, I went back to bricked and using the 3rd? beta right now. My battery started dropping like crazy again, so I thought it was the kernel. Before, I used bricked and it was fine so again, I couldn't really blame the kernel. What I tried after that is deleteing my OC app (I've used both SetCPU and System Tuner) and since then, battery is great again! You can try this and hopefully it'll help!
Tried that already as I too suspected the OC app a few days ago. Made no improvements to battery life, so I've put it back on today. Not tried a different kernel yet though, as I'd read that the bricked kernel was the best choice with InsertCoin? I used faux123's kernel first of all, but found it ran hot and kept crashing...
Down to 30% now by the way.
Ace42 said:
I think you drain is caused by the phone not entering "Deep Sleep", some rogue app is keeping the phone partially awake and sucking up juice. I'm gonna go on a hunch and say the phone is running around 1.x GHz while screen if off due to the app.
Click to expand...
Click to collapse
That's what I'm suspecting too, but I don't know how to go about finding it. I've looked with SystemPanel and BetterBatteryStats and haven't spotted anything, but that could just be because I'm not 100% on what to look for. And why would setCPU not be overriding it and making it clock down to 192mhz whenever the screen is off anyway? Isn't that it's job?
Then try the stock and see if it's still draining. When I tried stock and everything was great, I just simply assumed that it wasn't an app. It was the kernel!
I'm not convinced it's the kernel though, as if it was then battery life would have been crap ever since I flashed it. It hasn't been, it's only been bad for the past few days. Are there any links to the stock kernel just in case I can't find anything else?
- mine is 24 hrs
- heavy use 16 hrs
. Used some aninations only
. Turn off wifi when not in use
. Used only 20% brightness
. Used juice defender
. Downclock to 1.2 ghz intellideman
And ofc my kernel and rom that im using right now!
Thank me if I helped
I use bricked and i actually got better batter out of it but itsn still not up to par.. However fauxs ran faster but my phone was getting up to 47C... Way too hot.. I don't know why mines running so hot.. Using coredroid 2.6. 1.5 bricked kernel. wiped dalv and cache and battery stats... blah.. any input? i had setcpu and deleted it.
SetCPU is uninstalled again now to see if it was causing anything, and there's still a drain on the battery when it should be sleeping. Does anyone have any tips on how to find what's keeping it awake? It's been fully charged again, been unplugged for just one hour and it's down to 80% battery. Not even been using it apart from me flashing the InsertCoin Bravia addition onto it, making it 3.4.3.
One thing I have noticed though, is that BetterBatteryStats says the RILJ dialler has been running for 5m 33s since it was last charged, 775 times, 8.9%. This is on the partial wakelocks screen, whatever they are. Everything else listed is under 1%, with the only exception being the alarm at 1.6%. What does this mean?
Hey everyone
I have had the one x for 2 days now and have been having a few issues.
I tried searching but couldnt find anything related to my issue.
The last few nights I have left my phone off the charger to see standby battery life. Each night I am losing over 20% in 6/7 hours of sleep time. I have downloaded betterbatterystats now so I should have a good understanding of whats causing it soon. But I am also having an issue where my clock falls behind in time overnight. It falls behind about 10/15 minutes by the time I wake up. Also effects my alarm. As I leave my house it eventually updates and sets the clock back to the correct time.
Anyone have any similar issues? Possibly related issues you think?
Thanks
aimetti said:
Hey everyone
I have had the one x for 2 days now and have been having a few issues.
I tried searching but couldnt find anything related to my issue.
The last few nights I have left my phone off the charger to see standby battery life. Each night I am losing over 20% in 6/7 hours of sleep time. I have downloaded betterbatterystats now so I should have a good understanding of whats causing it soon. But I am also having an issue where my clock falls behind in time overnight. It falls behind about 10/15 minutes by the time I wake up. Also effects my alarm. As I leave my house it eventually updates and sets the clock back to the correct time.
Anyone have any similar issues? Possibly related issues you think?
Thanks
Click to expand...
Click to collapse
Are you using the network time (Settings -> Date & Time -> Automatic date & time)? I noticed that it is was not checked by default when I was first setting mine up.
Also, mind sharing what was causing your drain?
stnguyen09 said:
Are you using the network time (Settings -> Date & Time -> Automatic date & time)? I noticed that it is was not checked by default when I was first setting mine up.
Also, mind sharing what was causing your drain?
Click to expand...
Click to collapse
I actually had use network time already enabled. I took it off and set time manually. Ill find out tomorrow morning if it does it again.
As far as battery goes:
Im somewhat new to the android scene so not 100% sure at this point.
I believe it was google + auto update pictures on wifi/mobile. I changed to while on charger and manual.
There also seems to be a weird process called "TPD" in betterbatterystats maxed out w/ a red bar , not sure what it means tho.
I will try and get a screenshot up in a sec.
im guessing its total power draw? not sure what it means tho
There seems to be some reported issues with network time sync... dunno if AT&T towers are off or it's attributed to the HOX losing cell signal (mine does this frequently). It causes all sorts of issues when trying to use time-based two-factor auth like Google Authenticator or RSA tokens.
I'm going to try and manually set it and see if that helps retain proper time keeping.
agentdr8 said:
There seems to be some reported issues with network time sync... dunno if AT&T towers are off or it's attributed to the HOX losing cell signal (mine does this frequently). It causes all sorts of issues when trying to use time-based two-factor auth like Google Authenticator or RSA tokens.
I'm going to try and manually set it and see if that helps retain proper time keeping.
Click to expand...
Click to collapse
I checked cell standby and it did say 0% signal loss , but thats what I thought was causing it.
So even with clock set manually it still fell behind 6 min overnight. I'm lost
Sent from my HTC One X using XDA
Did you ever find out what tpd was? It seems to be a battery life killer on my One X also...
It happened once on my One X. It's been a bug in Sense since the Windows Mobile days. Dunno when HTC will get around to fixing it.
I am having daily problems with this as well. ClockSync app is only good for readjusting as it seems to synchronize overnight and that is when as you all have mentioned, is when the clock falls short. for me i sleep at midnight and wake up at 8:30 and the clock on my hox is slower by 10-15 minutes. this is on a DAILY. this is super super aggrevating and I don't know what to do. Is it possible to get a new HOX?
chillsen said:
Is it possible to get a new HOX?
Click to expand...
Click to collapse
It's a bug in Sense so you should either exchange for a Galaxy S III or wait for a stable CM9 or CM10 ROM.
I haven't had this issue for a long time. Ever since I started using clean rom. Worth a shot to try as well.
Sent from my HTC One X using xda premium
I had similar clock issues when I got my HOX. Never totally figured it out, but I am on manual time and have ClockSync set to sync every hour. No problems since then.
ClockSync can be set to automatically fix your clock if you have root.
realized the only thign that helped me was upgrading firmware. i was on 1.73, now installed 1.85 RUU and everything is cleannnn and good to go!
I've been noticing less than stellar battery life ever since I got my One X.
Lately I have noticed that sometimes my One X will get slightly hot under use(around the camera area), and then after I'm done using it, it still hot and my battery drains like crazy.
I turn the screen off, kill all apps, wait 5, 10, 30 minutes, even one hour I have waited, and the phone is still warm!
I don't use any apps that run in the background or have services that use a lot of battery. I've checked logcat, betterbatterystats, Cpu Spy and can't find anything wrong. I've tried different roms and the same thing happens.
The fix is simple. I just power it off and on and the problem goes away for a few hours, but then comes back! When I power it off, the area gets ice cold in less than 3 minutes , which tells me something is going on.
I can't figure out a pattern to trigger it but it seems to happen most when my phone switches to WiFi from LTE or vice versa.
Has anyone noticed this? It's been incredibly frustrating.
-----------------------------------------------------
After months and months the problem has been found and resolved. It was due to an LTE bug that would happen in certain areas(such as subway stations) if you lost all signal and then regained. The phone would get warm and battery would drop significantly, as much as 2% per minute. The drain would not stop until a full restart.
After trying many many roms, and after about a month testing it, this one has the problem fixed. I haven't tested other ROMS and quite frankly it works so well that I didn't bother testing for other ROMs.
I have this problem too. I put mine to sleep, after waking up from an hour nap the darn thing is hot! And of course the battery drained like crazy. Although it's too early to come to a conclusion, but so far it hasn't happened ever since I turned off autosync and wifi every time I take a nap..
Run betterbatterystats and carat, they can all identify various issues.
My phone does not deep sleep at all. Wtf?
I'm having the same problem, carat and bbs aren't helping
Sent from my HTC One X using xda premium
See if there are rouge apps running in the background that are keeping the phone from deep sleeping.
Go to Settings -> Wifi -> Advanced -> Best Wi-Fi Performance and make sure it's unchecked. It's been known to prevent deep sleep. I'm not sure it would cause such a huge drop in life or the heat, but every little bit helps.
Glad to know I'm not the only one experiencing this. I'm an advanced user, I've tried everything, carat, BetterBatteryStats, aLogcat, System Panel, Cpu spy, you name it. The phone is actually deep sleeping.
Also, I've noticed that the radio area gets hot more than the cpu area, so it might be a radio issue? I'm running baseband 0.17.32.09.12_10.86.32.08U .
zeuzinn said:
Glad to know I'm not the only one experiencing this. I'm an advanced user, I've tried everything, carat, BetterBatteryStats, aLogcat, System Panel, Cpu spy, you name it. The phone is actually deep sleeping.
Also, I've noticed that the radio area gets hot more than the cpu area, so it might be a radio issue? I'm running baseband 0.17.32.09.12_10.86.32.08U .
Click to expand...
Click to collapse
I'm on 0.17.32.09.12_10.86.32.08L (same as you, except for the L). I noticed that you mentioned that it may be when you're switching between WiFi and LTE, maybe it's continuing to hold on to that LTE connection? Also, where is the radio area in relation to the CPU? I know the CPU is right underneath the camera.
stnguyen09 said:
I'm on 0.17.32.09.12_10.86.32.08L (same as you, except for the L). I noticed that you mentioned that it may be when you're switching between WiFi and LTE, maybe it's continuing to hold on to that LTE connection? Also, where is the radio area in relation to the CPU? I know the CPU is right underneath the camera.
Click to expand...
Click to collapse
What is the difference between the L and the U? I've never flashed any radios so I guess I'm using the stock one from the 1.85 update.
I actually just assumed it's the radio because I was testing a cpu stress app to see if it would get "locked" in a high frequency thus causing the drain, but the area that got hot was to left of the camera area, and usually when the problem happens I can sense the warmth more to the right, around the LED flash.
I just charged my phone to 100% and it got warm, I unplugged it and waited a few minutes and the phone was still hot. I turned the phone off and in a matter of minutes (Like 4) , the phone was ice cold again. The plot thickens...
zeuzinn said:
What is the difference between the L and the U? I've never flashed any radios so I guess I'm using the stock one from the 1.85 update.
I actually just assumed it's the radio because I was testing a cpu stress app to see if it would get "locked" in a high frequency thus causing the drain, but the area that got hot was to left of the camera area, and usually when the problem happens I can sense the warmth more to the right, around the LED flash.
I just charged my phone to 100% and it got warm, I unplugged it and waited a few minutes and the phone was still hot. I turned the phone off and in a matter of minutes (Like 4) , the phone was ice cold again. The plot thickens...
Click to expand...
Click to collapse
I don't know what the difference is. I'm running CleanROM DE so it could be that the L is just the radio from 1.88. I never had this heat issue on 1.73, 82, or 85 though. Just the normal amount that threatens to burn your hand off while playing Angry Birds. Maybe try disabling LTE? (Don't ask me how to do that)
stnguyen09 said:
I don't know what the difference is. I'm running CleanROM DE so it could be that the L is just the radio from 1.88. I never had this heat issue on 1.73, 82, or 85 though. Just the normal amount that threatens to burn your hand off while playing Angry Birds. Maybe try disabling LTE? (Don't ask me how to do that)
Click to expand...
Click to collapse
Disabling LTE (By changing the APN settings) , makes my 4G(Non-LTE) connection unstable, for some reason. I experience a ton of data drops , so even if fixes the heat problem, it would create a new one. My data connection is rock solid when using the LTE APN .
I'm running stock 1.85 and the battery is great
Sent from my HTC One X using Tapatalk 2
I had a similar problem before until I installed CleanROM LE 2.0 (and above) I noticed the problem when I connected to wifi after I had lost signal from my commute every day. BBS didn't really help, and it seemed the problem would compound over time, eventually getting to a point where I was losing 3% battery ever couple of minutes.
After I installed the Lite Edition, the problem hasn't appeared since. Battery life seems to be draining normally and the phone doesn't get hot when not in use. It could be something that was removed from Sense that helped the issue, but I'm honestly not sure.
I do remember that before I switched to the Lite edition I tinkered with some settings, and I noticed that Latitude was set to update my location. I turned it off (it's off by default on the Lite Edition ROM), but I'm not sure if that helped my problem. Maybe try disabling that and see what happens.
WuTofu said:
I had a similar problem before until I installed CleanROM LE 2.0 (and above) I noticed the problem when I connected to wifi after I had lost signal from my commute every day. BBS didn't really help, and it seemed the problem would compound over time, eventually getting to a point where I was losing 3% battery ever couple of minutes.
After I installed the Lite Edition, the problem hasn't appeared since. Battery life seems to be draining normally and the phone doesn't get hot when not in use. It could be something that was removed from Sense that helped the issue, but I'm honestly not sure.
I do remember that before I switched to the Lite edition I tinkered with some settings, and I noticed that Latitude was set to update my location. I turned it off (it's off by default on the Lite Edition ROM), but I'm not sure if that helped my problem. Maybe try disabling that and see what happens.
Click to expand...
Click to collapse
Wow,I have a very similar usage pattern. I will try that and report back
Can anyone chime in on the difference between the L and the U in the radios?
Sent from my HTC One X using XDA
There's a thread with flashable versions of all the known radios floating about...There's nothing with a U in it except the Asian radio, but the rest of the baseband version number doesn't match.
http://forum.xda-developers.com/showthread.php?t=1694012
stnguyen09 said:
There's a thread with flashable versions of all the known radios floating about...There's nothing with a U in it except the Asian radio, but the rest of the baseband version number doesn't match.
http://forum.xda-developers.com/showthread.php?t=1694012
Click to expand...
Click to collapse
He fixed that now so even the Asian version apparently ends with an L. Does that mean I have an unkown baseband? doubtful. I have installed sick sense hox and so far so good. We'll see.
deep sleep and warm back.
I've noticed this, too.
I've woken up in the middle of the night to encounter my screen on and no gain in battery charge with a super warm back.
Last night I plugged it up at 73% and I woke up this morning with 71% and a fry-an-egg-hot back.
Restarting resolves the issue, and this is only the second timein about 1.5 months, but a concerning issue nonetheless.
Blame calendar sync
I had the exact same problem, and I narrowed it down to auto-sync.
In particular, my phone was constantly sync'ing my work calendar (my work place uses Google calendar/mail). I have a lot of recurring (weekly) events on that calendar, and one of those events was modified shortly before the sync started acting crazy.
How I fixed it:
1. Go into Settings > Apps > All
For "Calendar" and "Calendar Storage" apps, press the "Clear Data" button.
2. Removed my work Google account and re-added it.
Obviously, if it's not the sync that's causing the battery drain or you don't have any calendars synced, then this is not going to fix anything. Just thought I'd share my particular case with everyone.
Today I had my AT&T One X at around 40% charge when I went to sleep. After getting up the phone had shut itself down and when I try to turn it on using the power switch nothing happens. I charged it then it starts charging from 0%. I am on stock 4.04 rom and have rooted the phone. This is the third time in a month that this has happened. I am attaching the battery curve that I got after today's incident. Please Help! Thank you very much for any help in advance.
bosskaunhai said:
Today I had my AT&T One X at around 40% charge when I went to sleep. After getting up the phone had shut itself down and when I try to turn it on using the power switch nothing happens. I charged it then it starts charging from 0%. I am on stock 4.04 rom and have rooted the phone. This is the third time in a month that this has happened. I am attaching the battery curve that I got after today's incident. Please Help! Thank you very much for any help in advance.
Click to expand...
Click to collapse
Sounds like bad wakelocks, install Better Battery Stats to find out what is draining your battery.
Crappyvate said:
Sounds like bad wakelocks, install Better Battery Stats to find out what is draining your battery.
Click to expand...
Click to collapse
I have installed betterbatterystats and will update with results next time it happens..
I too am having this problem. Though it started happening after my phone drained and wouldn't restart after charging (boot loop). After I fixed that, it's been dropping dead.
I'm on a stock rom with ElementalX 3.0 kernel. Was v2.0 when it initially started.
Any luck finding information? I still get about the same use out of it (sometimes). I'm thinking that maybe the battery's level is getting reported incorrectly?
This is a known bug, whatever the hell is causing it. Just about everyone has had this happen at least once.
Its Reh said:
I too am having this problem. Though it started happening after my phone drained and wouldn't restart after charging (boot loop). After I fixed that, it's been dropping dead.
I'm on a stock rom with ElementalX 3.0 kernel. Was v2.0 when it initially started.
Any luck finding information? I still get about the same use out of it (sometimes). I'm thinking that maybe the battery's level is getting reported incorrectly?
Click to expand...
Click to collapse
How often are you having this problem. I have had this happen about 3 times in the last three weeks or so. Since my post last week, I haven't had it happen to me yet. I now have the betterbatterystats app installed and will update with results the next time I have battery drain.
bosskaunhai said:
How often are you having this problem. I have had this happen about 3 times in the last three weeks or so. Since my post last week, I haven't had it happen to me yet. I now have the betterbatterystats app installed and will update with results the next time I have battery drain.
Click to expand...
Click to collapse
It happens quite often. Happened today, then three days before that. I really don't have much on this phone either. After the initial bootloop I did a factory reset and didn't really add much.
This happened to me once on stock rom and kernel. I think it has something to do with the network trying repeatedly to connect and draining the battery. But the phone is asleep and not updating the battery percentage. When the phone finally awakes, it instantly updates the batteryfrom whatever it was before to 0. It seems to happen to people in the early morning.
There is a pretty sizable thread on this already.
http://forum.xda-developers.com/showthread.php?t=1881439
I have contacted AT&T and HTC. Neither knows whats up. Went to CM 10 though and haven't seen the issue. Although, the last 2 weeks with CR Dev I didn't see the issue either. It used to happen every night.
Butters619 said:
There is a pretty sizable thread on this already.
http://forum.xda-developers.com/showthread.php?t=1881439
I have contacted AT&T and HTC. Neither knows whats up. Went to CM 10 though and haven't seen the issue. Although, the last 2 weeks with CR Dev I didn't see the issue either. It used to happen every night.
Click to expand...
Click to collapse
Thought I remembered seeing a thread but couldn't find it via search.
I wonder if it's a sense based issue if you haven't seen it with CM 10. Though I didn't have any issues while using the stock kernel. -edit just read flar2's post about using stock and seeing the issue
Most likely something is draining while the phone is asleep and the battery doesn't update. You can see in my history details that when the phone wakes it jumps. Especially the ending death jump lol
I know if I have fast boot enabled and then it off, it'll drain around 10%. It only loses around 3 or 4 if the phone is shut down. I've never left it on overnight, but then again I am an avid task-killer
Sent from my One X using Tapatalk 2