How weird is it that I had one of the EVO 3Ds with the shut-off-instead-of-reboot problem (STOCK and temp rooted), but just this morning as I was messing around with Overclocking and Undervolting, it started to reboot just fine, and has been all day. Not a single shut down when I've told it to reboot.. (fast boot is turned off)
I wish I knew exactly what made it start working.
Related
So first a little background. I woke up in the middle of the night with an EXTREMELY hot phone. Somehow it had gotten under my pillow while it was charging (I have no idea how this happened but it did). The phone had a battery symbol with a temp sign, obviously way overheated. Well I quickly pulled the phone from the charger and the battery out of the phone to cool it down. After a few minutes when it had cooled down, I tried to boot it back up. At first everything looked good, TW bootscreen came up, but then nothing else happened. The phone would act like it had fully booted (captive buttons would light up then screen would time out and go black) but the boot screen animation would still be going if I pressed the power button to light the screen back up.
At that point I thought it was all over. I put in my spare battery and got the same results. So I went into recovery and wiped to see if the phone could read from the memory. I didnt have any problems with the wipe or reflashing (running next-gen TW). The phone booted up just fine. I haven't seemed to have any problems since.
So I guess my question is do you think I am in the clear? I ran quadrant to stress the phone to see if anything happened and I am still seeing the same scores. I thought I might have problems with data but it seems to be running ok now.
Is there more stress tests I should run to make sure everything is ok? I have always been cautious with my electronics so I havent run into overheating them before so I am not sure what to look for in this area.
Thanks guys/gals you all are awesome, love the community Usually I don't post/create new threads because search is my friend and I dont like to crowd threads with my stupid answers lol. Thanks again all!
PSS sorry for the long post and confusing explination let me know if I need to re-explain anything. and sorry if this is the wrong section just let me know and/or move to correct location.
My phone got stuck in the boot animation with Trigger v3.2 once. It had nothing to do with overheating.
I remember just doing a reboot and it got stuck in the animation. The screen timed out as if it had booted normally. I rebooted again and it was fine, never had that problem since. It has only happened to me with Trigger v3.2, which is based on KB5 (I think Bionix NextGen is also based on KB5).
So it's probably a software related bug and not related to heat damage or anything.
That's what I am hoping, guess the only way to really know is see if I start having problems over the next few weeks. Thanks for the replay
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.
At random times, my ATT SGSIII will do a hot boot (looks like the phone resets itself quickly. Not full reboot.) I don't know why it's doing this, but it's done it on the stock ROM and on Ultimatum ROM. The only thing I can think that has caused this was rooting it, but I haven't seen anyone else mention anything about it so I'm worried I screwed something up.
I attached a picture of my battery stats graph that shows the skips/jumps each time this happens. It also throws off the "time on battery" by a large margin.
Any ideas?
Thanks
Just to concur that this happened to me today, after I messed around with Bluetooth stuff (turn it on and off).
I'm still stock, unrooted and it happened to me twice in the last day. 1st time I just finished using a flashlight app and the phone froze and then rebooted. 2nd time it had been in my pocket for about 5 minutes. Both times - 2 vibrations, reboot, startup sound and graphics.
Hi.
This night my phone shut down while charging, leading to my alarm not going off and making me miss my bus, but that's another story.
Anyhow, when I woke up the phone was off. I turned it on, and I assume the boot-procces went OK..? I pressed on, saw the kernel bootimage and assume it went on to the ROM bootanimation... When I got to the bathroom I saw my lockscreen, and placed the phone face-down on a shelf.
I heard it "buzz" once, as if it shut down, and now it doesn't boot at all. When spamming the on-key it buzzes five times, but those are all signs of life I can recieve from it.
So, in short terms, how screwed am I?
EDIT: Battery problems. After ticklecharging for an hour from USB I managed to get it to boot. Voltage is 200mV lower than usual, so I should probably just get a new battery.
Which rom are u using?
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.