So my Rezound will occasionally just shut off. It always happens while the screen is off (so not while I'm using it). But I'll go to try and turn it on to no avail. And I am forced to do a battery pull to get it working again.
Recently whenever I try to restart my Rezound it hangs on the HTC Logo for over a minute and never leaves until I press the power button and then press it again.
Any thoughts?
Edit: Also I just noticed, this has never happened before, but the screen is now showing the blue flicker like crazy. I always got the blue flicker here and there very fleetingly but now its every few seconds and the entire screen turns blue.
Shutdowns?
Are you undervolting or underclocking? I've had problems when using a screen off profile with clocks and voltages that are too low. It caused my phone to get into a deep sleep state that would need a battery pull to get it back.
I'm assuming you're running an ICS rom since you mention the blue flicker? Did you update the rom recently? Apparently if you set the animation to 1.5x it reduces it IIRC.
I've had mine shut off on it's own a few times. I'd leave it on at night and when I went to use it in the morning it would boot up instead of just showing the lockscreen, I assumed it was because the battery was dead but it would be at like 80%. Still never figured out why it does that, only happened a few times.
Related
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.
I have a rooted Samsung Vibrant running Slim Bean 3.0 on Semaphore kernel. Sometimes, when the device crashes (usually from overload) it will begin to reboot, starting at the boot animation (skipping the "Vibrant Samsung" screen) and boot to a seemingly normal state, the only problems being:
The cell network is disconnected. If I go into or out of airplane mode it gets stuck while changing. It doesn't matter how good my reception is, it has the "no service" icon and will not call or text.
Sometimes, the battery indicator gets screwed up, it will display 2-5%, even if I know it is much higher. This false reading is duplicated in recovery mode. I can get it back to normal either by waiting, or by charging the phone while it is off. If i perform the latter, the opposite will sometimes happen, with it showing a power level much higher than it should be. Like the former, it will slowly creep back to normal. (This occasionally happens during a normal reboot (though never a power off and on) so it might be a separate issue) Another note about this: Once, when the battery was showing an amount I knew to be falsely high, I was (stupidly) using it, and the phone suddenly crashed in the weirdest way I have seen: It stopped responding to anything (except a later battery pull. I don't remember if the softkey backlights worked) and the screen got colored lines running vertically along it. I speculated that it might have run out of power and the battery voltage dropped low enough to start causing problems.
Sorry about the wall of text. Any help will be greatly appreciated.
Are you using deep idle? It is notoriously unstable and will require battery pull if the phone shuts off from it. Also uv'ing or oc'ing to extreme can cause the soft reboots.
I have a similar battery "fluke" when rebooting while charging. It will jump from 10% to 70%. Idk why this happens but saw it on PA and HB.
Sent from my SGH-T959 using xda premium
samsgun357 said:
Are you using deep idle? It is notoriously unstable and will require battery pull if the phone shuts off from it. Also uv'ing or oc'ing to extreme can cause the soft reboots.
I have a similar battery "fluke" when rebooting while charging. It will jump from 10% to 70%. Idk why this happens but saw it on PA and HB.
Sent from my SGH-T959 using xda premium
Click to expand...
Click to collapse
No, I don't think I have deep idle on, and anyways, I never need to pull the battery, just reboot normally.
Details of my panic situation below.
The phone is still awake and I can feel haptic feedback and hear sounds, but the screen is just blank. Did a number of battery pull but still nothing. Finally after awhile of battery pulling and letting it sit for a few seconds off, I powered on the device and I could see some sort of grey tint on the screen where I was met with a very vague but still visible boot animations. After about 3 seconds, it improves and I pushed slightly on the screen and noticed it helped, so I pushed on it further to help it out and it just turned back to normal everything turned out fine. What could be the problem with it?
what could be the problem? I never dropped it or anything so any suggestions as to why this happened and if it'll happen again?
Been running the GPE ROM flawlessly since I flashed on the 12th... Until today. Don't know if this is ROM related but maybe you guys can help.
Out of nowhere, my phone kept shutting off. Couldn't use it for more than a minute after booting before it would turn off completely. Battery was charged so I was kind of like 'wtf'. Then all of a sudden it wouldn't even get to the swirling colors boot screen. It would shut off halfway though the Samsung Custom logo. ****.
Tried plugging it in and pulling the battery multiple times. I can't even boot to recovery! The blue text shows in the upper left but then it will go off again. It's plugged in now but not showing the battery charging screen.
I can only get it to turn on for about a second. Am I ****ed? Is this thing bricked? Super random because I changed NOTHING this morning and it was fine yesterday.
crovax33 said:
Been running the GPE ROM flawlessly since I flashed on the 12th... Until today. Don't know if this is ROM related but maybe you guys can help.
Out of nowhere, my phone kept shutting off. Couldn't use it for more than a minute after booting before it would turn off completely. Battery was charged so I was kind of like 'wtf'. Then all of a sudden it wouldn't even get to the swirling colors boot screen. It would shut off halfway though the Samsung Custom logo. ****.
Tried plugging it in and pulling the battery multiple times. I can't even boot to recovery! The blue text shows in the upper left but then it will go off again. It's plugged in now but not showing the battery charging screen.
I can only get it to turn on for about a second. Am I ****ed? Is this thing bricked? Super random because I changed NOTHING this morning and it was fine yesterday.
Click to expand...
Click to collapse
It could be a power button failure, it's actually quite common on the S4.
Google "Galaxy s4 power button problems"
Check out this link:
http://forum.xda-developers.com/showthread.php?t=1931310
This problem started happening two weeks ago and it's quite annoying. Running Android 5.11 Archidroid with the latest Archikernel version on my phone.
The problem is that my Galaxy S3 seems to freeze when the screen turns off. If the screen is turned off for maybe half an hour or more, pressing the power button will not wake the device. In an attempt to figure out if it's a broken power button, I set the home and volume buttons in the settings menu as keys that will turn on the screen, but that doesn't work either. The only way to fix the issue is to hold the power button to restart the device and doing that every couple of hours gets really annoying. Trying to turn on the screen literally does nothing, as if the phone is turned off.
When the phone is not charging, the interval between the freezes seems to be much longer. The phone will work perfectly for a couple of hours without the above mentioned problem but when on a charger it quickly screws up.
Now, I don't believe my device turns off during this "process". I've turned on the LED for charging and whenever I'd get the screen freezing problem I'd unplug the charger and the LED wouldn't go away, it'd still light up as if the phone is connected to the charger, which it isn't.
Anyone have any idea on what the problem is? I've never experienced this before and it started happening all of a sudden.
How low is the kernel clockspeed running in sleep mode?. Should be at 200mhz at the very minimum!.
Beamed in by telepathy.
If this does not happen on a stock ROM, it would be a problem with the ROM and the phone.