Hi all,
I have never had this problem before, and it's making me kind of nervous.
My battery was low today(~47%), I had it plugged into my computer. It showed that it was charging, but I was using the phone at the time(and the battery was slowly going down, which was weird to me). I went to plug it into the wall, but before that, I turned it off.
I noticed that there was a hibernate option in the menu which I tapped by accident. I woke the phone back up, turned it off, and charged it. I went to turn it on, and it got through both "HTC" screens, and did the "Bamf thunderbolt screen", but it stayed stuck there for like 5 minutes.
I pulled the battery, waited a few seconds, turned the phone back on. Still stuck.
If it helps, SetCPU was updated today, and I hadn't rebooted the phone in a few days.
UPDATE: I restored an old backup, and the phone booted. Could it be a Problem with SetCPU? Anyone else having an issue with the new update?
Thanks for the help!
Could have been a bad flash of the ROM or something? Did you do anything new to it recently?
The only thing that I did was update SetCPU...I haven't flashed anything since I flashed the ROM.
I put the phone in Hibernate by accident, woke it up, and shut it immediately off afterwords. I turned "Stay Awake" off in the development menu to charge it (phone was a little hot; I had been using it). I charged it, turned it back on, and was stuck at the boot screen...don't know why.
I restored, removed SetCPU, and rebooted it twice yesterday (once to flash a battery framework mod, and another just to test it), and it booted right up.
I don't think it was a setcpu problem more than a conflict frequency problem. The bamf toolkit, if you've used it, will clock a certain frequency, and the setcpu will also clock a certain frequency. I think the two apps might have some conflict if you enable them both.
Did ever mess with the voltage settings on setcpu.
Sent from my ADR6400L using XDA App
Wipe wipe wipe and flash again
Sent from my bamf Thunderbolt using XDA App
tryceo said:
I don't think it was a setcpu problem more than a conflict frequency problem. The bamf toolkit, if you've used it, will clock a certain frequency, and the setcpu will also clock a certain frequency. I think the two apps might have some conflict if you enable them both.
Did ever mess with the voltage settings on setcpu.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Don't even know how to mess with the voltage...I've never really messed with setCPU beyond setting battery/charging/screen off profiles.
I uninstalled it and frankly am getting better battery life without it.
Related
Hey, since rooting my Eris, the phone is running hot. It also is not charging past 30%. I have tried wiping and reloading Ivanv07 rom as well as trying the Sense-able 0.7. The phone was on the charger overnight, and now only has 13% charge. I tried setCPU to throttle it down, but it was not able to change the settings despite having root access. Has anyone else experienced something similar/found a fix?
probably a bad battery. try getting a new one.
or do you mean that is started happening immediately after rooting? if so, never heard that before so dunno....
go to add widgets, htc widgets, get more widgets
Use that batter widget and tell me the battery temp, then see if it rises or lowers with useage.
It started happening right after rooting. The battery has gotten up to 50C, and that was just while charging with all Apps closed using ATM.
The only time my battery gets over 50 C is if i am running wireless tether and usb charging. And it will not charge over about 40 %.
Go get a task killer and make sure the tether program isnt running.
It was getting up to 50C without any tasks running, the ATM I mentioned before was for Advanced Task Manager. I ended all apps and services, and it still ran hot. Did not even install wireless tether yet. I tried to reflash PB root image, but hboot tells me now that "Battery voltage is too low" to proceed.
Mine did that once yesterday on the wall charger but I was on 5.5. It acted as if it discharged the battery. It was a fluke and hasn't happened since. I have noticed that the phone when I turned it on will not charge till it is fully booted into the os.
Ok, I found that the battery does seem to charge if plugged in with the phone off, and without the heat issue. One odd thing is that when charging, the battery symbol has its little animation, but when this issue I've been having seems to be going on, it is like the animation for that symbol is frozen. Everything else on the phone seems to be working fine.
tbertoli said:
Ok, I found that the battery does seem to charge if plugged in with the phone off, and without the heat issue. One odd thing is that when charging, the battery symbol has its little animation, but when this issue I've been having seems to be going on, it is like the animation for that symbol is frozen. Everything else on the phone seems to be working fine.
Click to expand...
Click to collapse
reboot into recovery and go to wipe and wipe battery stats
see if that helps
Mine did that (not rooted latest 2.1) and I have to go in and stop the Bluetooth Share app in App Manager. Does that for each reboot. It's weird.
Ok, I think I resolved the issue. I redid the entire root, recovery flash, image load process and actually got the battery to fully charge, though it still charges pretty hot.
The 1st time, the only thing out of the ordinary was that I accidentally went into the root image's recovery console, which froze the phone. I had removed the battery, reflashed the custom recovery, and everything looked good from there, except the battery issue, the heat, and neither wireless mac or bluetooth mac would show.
After redoing the entire process, the macs are showing up for me, which seems to point to clearing up the issue. Will post more if there is still a problem.
@timmywa I did notice that too, and it kept starting the service again after I would end it.
Not 2.1 root but some battery quirks
Well I had a strange issue today, well two actually.
First has happened with my g/f eris with 1.5, and my second leak 2.1 where the battery suddenly drops to less than 30%
Far as I know, I just have to charge like normal again to clear that up since g/f's eris is fine now.
SECOND Issue is I am now stuck in headset mode its a headphone icon with the mouth-piece, when no headphones or headset are in the phone.
I put headphones in and it switches to headphone icon. unplug them and its back to the headset icon, and no sounds.
Anyone else have this? would this be hardware or the new leaks issue?
your help is appreciated, and I will keep you posted if it changes, and how.
After my battery got really low, Power Saver mode turned in. I have it set to go on at 15% . Normally the settings return to normal once plugged back into a charger or the battery level goes back up. This last time I let the battery get down to 5% (I know..) . You know how when it gets that low, it will dim the screen really fast and disable tactile feedback? Well the thing is, it nwver reset itself. I even changed the power settinf and reboot the phone. I had to go into the screen and touch settings to reset them manually.
Anyone know why the settings did not return to normal?
I had the same thing happen. I don't know why it didn't reset. I had to change everything back manually too... I forgot my extra battery on Christmas...
Sent from my HTC Rezound
If anyone else gets this, please post here. If it happens again, I'd be interested to know if there is a fix...thanks.
I also just noticed background data got disabled. Market would not load . I had to manually turn that back on.
happened to me as well. the haptic feedback was disabled when my phone shut itself down. when i charged it back up, it didnt reset the settings to normal.
Same here... happened this morning... could it be due to the unlock?
Sent from my ADR6425LVW using Tapatalk
Yep, that sucks. Same thing happens here. Unlocked bootloader, though I doubt that is the reason.
Sent from my ADR6425LVW using Tapatalk
I have the same issue.
Unlocked bootloader with amon recovery and CleanRom 1.2
When economy mode kicks in due to low battery level, certain settings are not restored upon charge, namely the background data, though I found it was set to CDMA only with LTE disabled as well.
When I tried a Sense3.5 rom on my incredible it did the same thing, so I think this is an issue with Sense, not just the Rezound.
I think we need to start opening tickets with Verizon/HTC for them to address their issue.
fully stock over here, same issue!
I too am experiencing this issue, currently using cleanrom 2.2 sp1
Also have this issue. Stock everything.
yup, stock, same issue.
disabled 'power saver mode' so it never happens again.
Had it happen again. Batt was at 8% when I plugged in. Stock ROM ,no unlock performed. Anyone with a different version of Sense get this issue?
I've had this phone since the end of October, and recently (within the last 2 weeks), I have noticed that it will just turn off randomly and the power button becomes unresponsive. I have to do a battery pull to get it to power back on. This happens 2-3 times per day.
I have only rooted it; no cfw or anything. Does anyone have this problem or a solution?
Thanks
This happens to me some times as well. I found my cause was when I used miui locker. I'm rooted running latest ICScrewed ROM
Sent from my SGH-I777 using xda premium
Random Shutdown
southpawaf said:
I've had this phone since the end of October, and recently (within the last 2 weeks), I have noticed that it will just turn off randomly and the power button becomes unresponsive. I have to do a battery pull to get it to power back on. This happens 2-3 times per day.
I have only rooted it; no cfw or anything. Does anyone have this problem or a solution?
Thanks
Click to expand...
Click to collapse
Be sure to check the battery level.
I have seen this issue when the battery is defective and
will not hold at least a 15% charge at normal shutdown.
The battery level bar may not be accurate, so you might want to
test it with a new battery.
Good Luck!
Well, once I pull the battery and reboot, the phone works fine again on the same charge. It will work for 2 days on the same charge; it just turns off several times. I guess it would be easier to buy another battery than go through the hassle of dealing with a Samsung RMA or AT&T.
I use JuiceDefender if that would make any difference.
My girlfriend and I had the same issue and it turned out to be widget locker, so if you use that it may be the cause.
Sent from my SGH-I777 using XDA App
It's a Sleep of Death.
Are you undervolting?
If on the stock kernel, are you using SetCPU?
Long-press of power (more than 10-15 seconds) should reset you without a battery pull.
What she said ^^^^^
Sent from my SGH-I777 using Tapatalk
Had the same issue, I a fit of frustration I removed a bunch of apps all at once, and the problem went away. I suggest removing apps that you have recently downloaded till you find what's causing the issues.
Symptoms describe what entropy suggested. (sleep of death).
Tried a factory reset yet? You could go app by app as well till you find the culprit.
Sent from my SGH-I777 using Tapatalk
I got frustrated and removed a bunch of apps all at once like hd779 did, as well as disabled juicedefender. I have not messed with the cpu or voltage. I did all this last night and it hasn't died yet, so maybe something worked.
Thanks for the tips.
Did you install the recent update, my issue did not start until I installed it, but like I said I uninstalled a bunch of apps all at once so I could not indentify which app it was, my hypothesis is there is an app or apps out there that do not play nice with the latest update.
I did not have the update installed. As a matter of fact, the thing won't update. I've tried about 5 times and it keeps rebooting and telling me that the update was interrupted and it just gives up.
I'm going to turn on juicedefender later today to see if that was the culprit.
Entropy512 said:
It's a Sleep of Death.
Are you undervolting?
If on the stock kernel, are you using SetCPU?
Long-press of power (more than 10-15 seconds) should reset you without a battery pull.
Click to expand...
Click to collapse
I have a similar issue and the solution you provided worked every time. Is there any way to get rid of this? I am using CM7.1.
When I take my phone to use, screen wouldn't switch on pressing power button. Only way to resolve would be to long press power button and it restarts. I never had to do a battery pull. Doesn't happen frequently. May be 4-5 times over 2-3 months time period.
I just recently installed setcpu and tried changing min and max frequencies. But I have encountered this issue even before installing this app.
I used to use Load Monitor to fix the Sleep of Death issue. But ever since rooting, changing to Entropy's kernel, loads of battery optimizations, Llama configurations (not sure what did it), the Sleep of Death problem has gone away and I can do without the Load Monitor app.
dineshbabumm said:
I have a similar issue and the solution you provided worked every time. Is there any way to get rid of this? I am using CM7.1.
When I take my phone to use, screen wouldn't switch on pressing power button. Only way to resolve would be to long press power button and it restarts. I never had to do a battery pull. Doesn't happen frequently. May be 4-5 times over 2-3 months time period.
I just recently installed setcpu and tried changing min and max frequencies. But I have encountered this issue even before installing this app.
Click to expand...
Click to collapse
Grab the contents of /proc/last_kmsg after you've rebooted with a long press of power. (Hopefully the CM7.1 kernel supports ramconsole. I've been so busy patching up to update3 that I haven't had a chance to coordinate with those guys.)
I'm in dire need of some help. My phone is a stock unit that has had no modifications to it at all. It started shutting off randomly a week or two ago, usually when I would use GPS, bluetooth, or the internet but it does happen when everything is turned off (GPS, bluetooth, and wifi) When I turn the phone back on, the battery would be totally drained displaying to a critical level. This would cause the phone to shut back off. I can repeatedly turn the phone back on, and usually one of the times the battery will be displayed with more charge and allow me to use it, but if I did anything other than make a call the phone would shut back off. This problem does not occur if the phone is plugged in and charging (never shuts off randomly and the battery does not drain). I have already tried factory resetting the phone multiple times and that hasn't seemed to help. Any input would be greatly appreciated!
netiseret said:
I'm in dire need of some help. My phone is a stock unit that has had no modifications to it at all. It started shutting off randomly a week or two ago, usually when I would use GPS, bluetooth, or the internet but it does happen when everything is turned off (GPS, bluetooth, and wifi) When I turn the phone back on, the battery would be totally drained displaying to a critical level. This would cause the phone to shut back off. I can repeatedly turn the phone back on, and usually one of the times the battery will be displayed with more charge and allow me to use it, but if I did anything other than make a call the phone would shut back off. This problem does not occur if the phone is plugged in and charging (never shuts off randomly and the battery does not drain). I have already tried factory resetting the phone multiple times and that hasn't seemed to help. Any input would be greatly appreciated!
Click to expand...
Click to collapse
Have you tried a new battery? Sounds like your battery is on its last leg. It could also be battery contacts on your phone, make sure they are clean and actually touching the battery when you insert it.
Sent from my SGH-T959 using xda premium
have u ever flashed a rom ?if not then u should change ur battery ....
iTz KeeFy said:
Have you tried a new battery? Sounds like your battery is on its last leg. It could also be battery contacts on your phone, make sure they are clean and actually touching the battery when you insert it.
Sent from my SGH-T959 using xda premium
Click to expand...
Click to collapse
I second this, I had the same issue a couple years ago with my g1, a new battery made it run like new again.
netiseret said:
I'm in dire need of some help. My phone is a stock unit that has had no modifications to it at all. It started shutting off randomly a week or two ago, usually when I would use GPS, bluetooth, or the internet but it does happen when everything is turned off (GPS, bluetooth, and wifi) When I turn the phone back on, the battery would be totally drained displaying to a critical level. This would cause the phone to shut back off. I can repeatedly turn the phone back on, and usually one of the times the battery will be displayed with more charge and allow me to use it, but if I did anything other than make a call the phone would shut back off. This problem does not occur if the phone is plugged in and charging (never shuts off randomly and the battery does not drain). I have already tried factory resetting the phone multiple times and that hasn't seemed to help. Any input would be greatly appreciated!
Click to expand...
Click to collapse
what ROM are you using? are you overclocked? I had similar problem with some roms overclocked, my phone would shut down, restart, battery drain was horrible!! during calls would be the most annoying it would turn off and was walking have a conversation with the plastic by my ear .after some research and testing the problem was my overclocking was unstable at 1.2 + running on 1ghz after a while the problem went away
Your phone will restart or shutdowns randomly..if
1.You overclocked GPU or CPU to high performance.
2.You flashed any unwanted zip files for performance or somewhat.
3.You make the phone very heat[Main Reason].
Instructions:
1.Avoid playing high end games for long time(Like me).
2.Avoid playing high end or medium games above 20mins. while charging.
3.Don't allow your phone to heat.(Due to temperature).
4.Try Re-flashing your current Rom(if you installed custom rom).
5.Try flashing your phone.
6.Check your phone completely for viruses with a better antivirus.
7.If the problem is after installing some apps..Try uninstalling that.
Thats all i Know!
happened to me before more than once I agree that you should get a new battery but if you have to wait in the meantime, what I did was:
1. pull the battery out let the phone cool down
2. I put it back in and turned it on
3. If it turns on okay drain the battery till it shuts off by playing music
3. repeat 1 and 2 and if it turns on okay again repeat step 3
4. if not then let it stay off and charge it to maximum and it should be useable
I did this because I assumed that the phone for some reason wasn't reading the battery levels properly so I made sure that the battery was fully drained then charged it to max to fix that. It worked for me but its just to make the phone useable as I still needed a new battery. It drained very quickly and I had to be charging even 3-4 times a day on heavy use but if I only made phone calls and texts it got me through one day.
Hey guys,
Last night I plugged in my LGOG right before I went to sleep. About seven hours later I woke up, woke it up to check the time, then fell back to sleep. When I woke up again a few hours later, my phone was completely dead. No lights go on when charging, nor does it go into the charging mode that happens when the phone is off but charging. The power button does nothing at all. Connecting it to a computer does nothing. I have tried two different wall chargers and a USB plug, and have tried different outlets. The phone is rooted and unlocked. I haven't put any new apps or anything on the phone recently, however I have had a slight overheating issue lately. I don't think that that's what caused the issue though, as when I woke up for the first time and woke it up, the phone was not noticeably hot, and seemed to work fine. Any ideas or suggestions?
Edit: As suddenly as it stopped working, it has started working again, about two hours later. The notification sound buzzed, my phone turned on, and usual on start things happened. However I'm still extremely worried about it. Now that it's on, I assume there's more I can do to figure out the issue- suggestions?
These phones are terribly buggy when charging/when they die, IMO. Worst Android device I've ever had in that respect.
Probably just a fluke, tbh.
Unfortunately it happened again- sent a message, put my phone away, when I tried to turn it on again nothing happened and it stopped working for five minutes.
Apologies for not mentioning this before, but I am using carbonrom, not stock. I've used it for several months with no issues, and have used the latest build for a week or two now without this issue.
miller150 said:
Unfortunately it happened again- sent a message, put my phone away, when I tried to turn it on again nothing happened and it stopped working for five minutes.
Apologies for not mentioning this before, but I am using carbonrom, not stock. I've used it for several months with no issues, and have used the latest build for a week or two now without this issue.
Click to expand...
Click to collapse
Reboot into recovery and wipe cache+dalvik
Maybe the rom needs a little cleaning
Sent from my CM10.2 OGE973
Tried wiping cache and dalvik, but didn't seem to solve the issue. Then my phone started having an issue it's had once before- it turns on for a few seconds, then the screen goes grey for about a minute, then returns to being on. After returning to being on, it acts like it's just started up- ie, there's superuser grant notifications, cpu set notifications, and all sorts of other stuff I usually see on boot. It essentially rendered my phone unusable, so I restored an earlier backup. This seems to have resolved it for now, I may have to wait before updating carbon again.
miller150 said:
Tried wiping cache and dalvik, but didn't seem to solve the issue. Then my phone started having an issue it's had once before- it turns on for a few seconds, then the screen goes grey for about a minute, then returns to being on. After returning to being on, it acts like it's just started up- ie, there's superuser grant notifications, cpu set notifications, and all sorts of other stuff I usually see on boot. It essentially rendered my phone unusable, so I restored an earlier backup. This seems to have resolved it for now, I may have to wait before updating carbon again.
Click to expand...
Click to collapse
Either you have a bad phone (possible, LG seems to have some QC issues based on some of the crazy reports Ive heard fm other people on this forum [Mine's fine]), or it's all the startup **** that you have going.
Do you usually let it discharge to below 5%?
that's a stupid idea with any device, and seems to be especially damaging to our LGOG.
OMGMatrix said:
Either you have a bad phone (possible, LG seems to have some QC issues based on some of the crazy reports Ive heard fm other people on this forum [Mine's fine]), or it's all the startup **** that you have going.
Do you usually let it discharge to below 5%?
that's a stupid idea with any device, and seems to be especially damaging to our LGOG.
Click to expand...
Click to collapse
Have mine 2months been careful not to let the battery shut down on its own but thirds past Monday my car charger weren't bad and the phone shut down. Would not except a charge after that. Went to att and they sent me to a service center. They could not charge it either. They replaced it, now making sure my external battery backup its always charged. Do not want to do that again.
Sent from my LG-E970 using xda app-developers app
That sounds like that could actually be the issue. On the previous iteration of carbon I almost never allowed it to go below about 10%. However the new update seemed to be harsher on battery life and it slipped into the 1% range several times...
same thing happened to me running root box with no tweaks or anything. I woke up and the phone was off, been that way for two days now. it wasn't on the charger so its definitely possible that it died. I actually found this thread because I could've sworn there was a report of someone who had to do a battery pull. I'm thinking that's my only option now.