Ok maybe you guys can help. I'm having the strangest problem.
I'm running cyanogenmod nightly 151 and last night I was using the torch widget on bright for a little while and the battery died. Charged it back up and when I unplugged it in the morning it rebooted to white htc logo screen. Booted up normally and as soon as screen times out it reboots again. It did this a number of times so I Did a complete wipe and installed an older nightly, same issue. Full wipe and installed a stable rom, same thing. Then I noticed when I leave it on the charger I don't have the rebooting problem, only on battery power, so I replaced the battery. Same issue. Then I noticed that if I constantly use the phone it doesn't reboot. Only when the screen times out. Set the time out to 30 mins and left it idle. 30 mins later it rebooted. Turned off the "screen off animation" thinking that was the problem, no luck. Flashed back to stock official tmobile rom, same issue! Tmobile is sending me out a new phone and battery but just for curiosity sake and so it doesn't happen again, any ideas on what it could be? Definately gonna avoid that torch widget in the future! Thumbs up to tmobile customer service for their no haggle "overnight me a phone for 5 bux" customer service!
To sum it up, when phone is on charger no problems. When phone is running on battery, anytime the screen goes out, either by hitting power button or by it timing out, it instantly reboots to htc logo.
chrisconley1 said:
To sum it up, when phone is on charger no problems. When phone is running on battery, anytime the screen goes out, either by hitting power button or by it timing out, it instantly reboots to htc logo.
Click to expand...
Click to collapse
Flash a fresh version..or a stable one.
Sent from my HTC Desire Z using XDA Premium App
Yea I flashed 5 different ones, first I flashed back to the previous release that included a different kernel, then the stable rc1, then the stable before that, then I flashed the stock rom with root. There's nothing on my phone now except stock software and root. As soon as I hit the button to turn the screen off it reboots. The real question is what exactly happens when the screen goes off that the phone isn't liking? Its speedy and everythng works great for as long as the screen remains on. Its gotta be a hardware issue if I've tried so many different roms right? Or is there some core piece of software that nightly 151 changed that none of the other roms I'm flashing are changing?
Update: if I have music or navigation on and I turn the screen off the phone doesn't reboot until the song ends or route ends! Lol wth is up with this? It only reboots on idle? Maybe processor drops too low?
Update. Phone stopped rebooting every time the "screen goes off / all processes stopped" and now only does it very randomly, almost hardly ever. Its like its repairing itself lol. Htc cyborg! New phone should be here tomorrow. I was really hoping to figure this out though. Oh well
Related
Greetings to all members.
A couple of days ago i received a new G2.
As soon as i rooted it i installed http://forum.xda-developers.com/showthread.php?t=1605016
Everything completed and the phone would operate normally. I let it fully charge during the night. Next morning i installed some apps from the market (skype fb and a weather widget), then i let it charge again for 20 minutes or so. When i got back to see if it charge, the screen was dimmed like in power saving mode, it wouldn't go back no matter what and the phone hanged there.
I got the battery out and upon rebooting the screen was still dimmed.
I got back to 2.3.3 stock which i had backed up to SD from clockwork, but the problem continued.
I contacted the seller and said they would ship a new one as soon as i sent them the shipping back notice. The thing is i don't want to wait half a month or even more to get the new phone.
I've attached a video of the problem.
I played with the brightness levels on 4.2, you will notice that if i put it on 100% the screen goes completely black.
Also when i put it in standby with the power button and push it again the screen starts flickering for some seconds before it gets stabilized again.
Thanks in advance for your time.
Johnny91i said:
Greetings to all members.
A couple of days ago i received a new G2.
As soon as i rooted it i installed http://forum.xda-developers.com/showthread.php?t=1605016
Everything completed and the phone would operate normally. I let it fully charge during the night. Next morning i installed some apps from the market (skype fb and a weather widget), then i let it charge again for 20 minutes or so. When i got back to see if it charge, the screen was dimmed like in power saving mode, it wouldn't go back no matter what and the phone hanged there.
I got the battery out and upon rebooting the screen was still dimmed.
I got back to 2.3.3 stock which i had backed up to SD from clockwork, but the problem continued.
I contacted the seller and said they would ship a new one as soon as i sent them the shipping back notice. The thing is i don't want to wait half a month or even more to get the new phone.
I've attached a video of the problem.
I played with the brightness levels on 4.2, you will notice that if i put it on 100% the screen goes completely black.
Also when i put it in standby with the power button and push it again the screen starts flickering for some seconds before it gets stabilized again.
Thanks in advance for your time.
Click to expand...
Click to collapse
Are you using automatic backlight?
Johnny91i said:
Greetings to all members.
A couple of days ago i received a new G2.
As soon as i rooted it i installed http://forum.xda-developers.com/showthread.php?t=1605016
Everything completed and the phone would operate normally. I let it fully charge during the night. Next morning i installed some apps from the market (skype fb and a weather widget), then i let it charge again for 20 minutes or so. When i got back to see if it charge, the screen was dimmed like in power saving mode, it wouldn't go back no matter what and the phone hanged there.
I got the battery out and upon rebooting the screen was still dimmed.
I got back to 2.3.3 stock which i had backed up to SD from clockwork, but the problem continued.
I contacted the seller and said they would ship a new one as soon as i sent them the shipping back notice. The thing is i don't want to wait half a month or even more to get the new phone.
I've attached a video of the problem.
I played with the brightness levels on 4.2, you will notice that if i put it on 100% the screen goes completely black.
Also when i put it in standby with the power button and push it again the screen starts flickering for some seconds before it gets stabilized again.
Thanks in advance for your time.
Click to expand...
Click to collapse
Sounds to me like it is really a hardware issue... while it's understandable that you don't want to wait for a new phone to arrive, it is better than ending up with a dead backlight...
It really was a hardware issue, took another one back after a month and it works great.
Thanks for your help guys
Hello, everyone, this is my first post here, and after doing much research on my problem, I haven't had much insight into solving my problem permanently. tl;dr version is at the last paragraph.
First off, I installed AOKP on my phone for the first time a couple months ago and I had no problems for two months for reboots or anything like that, and I believe my phone was overclocked to 1520 mhz on the SmartReflex voltage settings. I did not undervolt whatsoever. In this phase, whenever I would turn it on, I would get to the boot animation, then the animation would hang, and the screen would rise to the highest brightness, flicker, and reboot, or shut down.
Then, in my troubleshooting, being the idiot I was, I accidentally unplugged it while I was flashing back to stock using ODIN. I got the "Android triangle computer" A.K.A. the "Soft Brick" signal. If I booted it normally, into my recovery, ODIN mode, whatever, I would get the same signal.
So, I left my phone alone for a couple weeks, accepting failure. Two weeks ago, I rebooted again into Odin mode, and I saw that Odin on my PC still recognized it, so I connected it and reflashed the stock ICS rom. I re-rooted and installed AOKP, all was fine for two/three days.
After that, the reboots started to happen again, and after a week of constant rebooting, and restoring latest backups,I set the CPU back to normal with no overclocking. I also undervolted but left "Set On Boot" unchecked for everything, This seemed to work fine for normal use, but I still had the phone on "InteractiveX" as the governor. So, when I would go to sleep, I would wake up and the phone would not be on. I would have to battery pull, reboot, etc. I thought this had something to do with one of the cores being turned off when the screen is, so I changed the governor to "Interactive" and the phone would charge now the same.
Now, the problem is, yesterday, I was fiddling with some benchmarks and I OC'd to 1520 for fun, and the phone screen froze, rose to the highest brightness, and shut down. I didn't have it "set to boot" so I thought everything should be fine, so I rebooted and the same thing happened at the boot animation which happened to me when I OC'd. I restored a Nandroid Backup I had before I set it to 1520, and still, no dice.
I reflashed my recovery then, because sometimes it would just freeze at the Google logo and not boot into recovery at all. Then, I restored my Nandroid again, and it booted into Android. After a few minutes, it crashed with the same "High Brightness, Screen Flicker". I restored again, and this time, I rushed into the "Performance Tab" and set my undervolt settings. The phone worked smoothly until I turned the screen off, and then I got the "Screen of Death". Basically, the screen stayed black, but the notification light was still on, and there was no response. So I pulled my battery and tried to reboot, but at the boot animation, the Nexus logo goes into "High Brightness, Screen Flicker". So, I took the battery out, and the phone is just sitting here now for fifteen or so minutes while I typed this out.
My question is, has anyone been having these same issues with their GNex. Because at this moment, I'm thinking I caused a hardware defect for running on 1520 for so long previously and I fried some inner components. Any help?
Edit: I put the battery back in and still the same thing. Going to charge overnight and let it sit, but if anyone has any help, please come forward.
Bump
First off, don't bump threads which aren't even a day old.
Secondly, if your device behaves like that when you UV/OC, have you thought about not pushing it so far?? Why don't you stick to stock for a while to check for hardware failure or if it's just you?
Edit: if it comes back, install stock through fastboot. Leave Odin. Don't OC.
Sent from my Nexus
Sorry
bk201doesntexist said:
First off, don't bump threads which aren't even a day old.
Secondly, if your device behaves like that when you UV/OC, have you thought about not pushing it so far?? Why don't you stick to stock for a while to check for hardware failure or if it's just you?
Edit: if it comes back, install stock through fastboot. Leave Odin. Don't OC.
Sent from my Nexus
Click to expand...
Click to collapse
First post here, didn't know much about rules. Thanks for the response. My Nexus did come back, just about 5 minutes ago. I'm going to stay on AOKP for a day and if I don't encounter any problems, I'll stay on it. If I do, I'll revert back to stock.
So yeah, **** this
bk201doesntexist said:
First off, don't bump threads which aren't even a day old.
Secondly, if your device behaves like that when you UV/OC, have you thought about not pushing it so far?? Why don't you stick to stock for a while to check for hardware failure or if it's just you?
Edit: if it comes back, install stock through fastboot. Leave Odin. Don't OC.
Sent from my Nexus
Click to expand...
Click to collapse
It was working fine until I got 3 or 4 Sleeps of Death a day until today. It just stopped working, and I restored my backup multiple times, but it would just hang at boot or bootloop. So I'm like **** this, so I flashed the stock image for 4.2.2 through Fastboot, and it still didn't boot, even after complete data wipe through the stock recovery. So, I thought it must be 4.2.2 that is doing this, so I installed the 4.1.1 and still the same result.
I'm so done with this thing, it's a hardware issue, total crap of a phone. If it is actually meant to be tinkered with and to be a "developer's phone" this crap wouldn't happen.
Hello guys,
I tried to search for a similar issues but I couldn't find anything similar so please bear with me.
My KF sometimes shuts down overnight. In the morning then I have troubles to switching it on again (clicking the power button, holding it for longer periods of time...). It usually helps for the tablet being connected to the charger, but it takes a few tries to turn it on. After I managed to turn it on again, for example yesterday, it had 80% of battery left.
I am using CM nighties and this is happening already for some time.
I am also using juice defender, I am not sure if that is relevant.
Do you have any suggestion, what could be the cause of this? Maybe a suggested alternative rom? Or some logs I can check? I think the powering on troubles bother me more than the shutting off overnight since I always think it won't come back on anymore.
Also, not sure if relevant. If I try to turn it on and it doesn't, sometimes the button flashes orange. After a few tries it turns green and powers on. Not sure if I am now not only confusing times, when it was simply out of juice.
P.S. On a different note, just curious, does anyone know how if there is a rom with working mic already?
Thanks in advance.
jkb
Yes, I sometimes have the same issue with the power button - in fact it happened to me this morning where I went from about 60% charge to 16% with a sudden power drop.
Not sure why this happens. I thought it was a bad battery so I changed it but am still getting the problem every now and then.
Sent from my Nexus 7 using xda premium
the only thing that i can think of is that during the middle of the night a soft-reboot happens and it cant boot back up into the system. this would cause it to sit there and continually try to boot up. this would use a lot of cpu and a lot of power. as for why that drains battery while being plugged in, well i cant help you on that.
Thanks for the input. I've wiped dalvik, cache and the system and installed hashcodes AOSP Jelly Bean (http://forum.xda-developers.com/showthread.php?t=2041694) and at least it survived this night without shutting down so maybe this helped. If I come across the same issue, I will update this thread with new info.
Thanks again,
jkb
Check this out:
amazon.com/gp/help/customer/forums/kindleqna/ref=cm_cd_pg_pg139?ie=UTF8&cdForum=Fx1GLDPZMNR1X53&cdPage=139&cdThread=Tx2JSJNEOWHGOIT
Sounds like a hardware issue, and Amazon has been replacing those of customers who buy new from them.
Mine has this issue too. I KNOW it has battery power, and is still on, but the screen won't turn on. Only solution is to plug in power, then hold down the power button until it shuts down hard. Then turn back on.
I'm returning mine because of it.
Thanks for the info. I am still hoping this is a software issue.Regrettably I am outside o the US and thus replacing it is nearly impossible. I will see, if the issue returns with the new rom and will update the thread if it happens again, just for your information.
jokob.sk said:
Thanks for the info. I am still hoping this is a software issue.Regrettably I am outside o the US and thus replacing it is nearly impossible. I will see, if the issue returns with the new rom and will update the thread if it happens again, just for your information.
Click to expand...
Click to collapse
Try going to the WiFi settings and selecting 'never' for keeping WiFi on during sleep. This seemed to work for me.... So far it hasn't happened again.
Sent from my Nexus 7 using xda premium
I think this is the bug I am experiencing:
Shutdown bug stalls out the shutdown. Looks like the device is off, but it's still powered draining battery. Currently requires long power button press to fully shutdown after the screen is black (about 15-20 seconds).
from the 3.4 kernel thread (http://forum.xda-developers.com/showthread.php?t=2264563). I am not sure if cm 10.1 nighties contain this kernel, but the description is pretty much spot on.I couldn't test the fix (holding the button for 15-20 seconds), since I already changed roms, but if someone experiences the issue again, he can post if this works and which rom and kernel they are using.
This happens to my Kindle Fire device as well. It just randomly shuts off and it won't come back on until I do a hard shutdown then turn it back on. I currently have AOSP Jelly Bean 4.2.2_r1 on it.
pwrdbykimchi said:
This happens to my Kindle Fire device as well. It just randomly shuts off and it won't come back on until I do a hard shutdown then turn it back on. I currently have AOSP Jelly Bean 4.2.2_r1 on it.
Click to expand...
Click to collapse
Yes, it happened again to me with the same ROM, but it happens less often. I will try the updated kernel once it is finished.
On May 27, 2013, Hashcode listed the known issues of the current kernel on his website:
Sound / MIC debugging
Deep sleep issues with “omapdss_dpi” device
SmartReflex shutdown loop fix.
Charging driver / OTG improvrments
Click to expand...
Click to collapse
Looks like they've been identified and are being resolved. :good:
I've been using my S2 as a music player for a while. and its been running Liquidsmooth 2.10. and its worked just fine for ages.
my s4 was damaged, so i was using my s2 as a backup. it worked fine for a week or more, then suddenly one day, it just just killed it self. nothing was changed as far as rom/kernel or anything. i was just typing a text and all of a sudden the screen flickered, and the camera flash went off a couple times, the screen turned back on and the off again. then it just turned off.
i have not been able to get it back on since. it will show the SII logo for a few seconds then turns off. then proceeds to vibrate once every 2 seconds endlessly. thats all i can get out of it. it wont go into download mode or recovery or anything because as soon as i put the battery in, it tries to boot itself.
anybody have any ideas what is goin on here?
autonami said:
I've been using my S2 as a music player for a while. and its been running Liquidsmooth 2.10. and its worked just fine for ages.
my s4 was damaged, so i was using my s2 as a backup. it worked fine for a week or more, then suddenly one day, it just just killed it self. nothing was changed as far as rom/kernel or anything. i was just typing a text and all of a sudden the screen flickered, and the camera flash went off a couple times, the screen turned back on and the off again. then it just turned off.
i have not been able to get it back on since. it will show the SII logo for a few seconds then turns off. then proceeds to vibrate once every 2 seconds endlessly. thats all i can get out of it. it wont go into download mode or recovery or anything because as soon as i put the battery in, it tries to boot itself.
anybody have any ideas what is goin on here?
Click to expand...
Click to collapse
Sounds like the power button may be stuck which is a known issue with this phone. Here is a thread on the issue:
http://forum.xda-developers.com/showthread.php?t=1931310
autonami said:
I've been using my S2 as a music player for a while. and its been running Liquidsmooth 2.10. and its worked just fine for ages.
my s4 was damaged, so i was using my s2 as a backup. it worked fine for a week or more, then suddenly one day, it just just killed it self. nothing was changed as far as rom/kernel or anything. i was just typing a text and all of a sudden the screen flickered, and the camera flash went off a couple times, the screen turned back on and the off again. then it just turned off.
i have not been able to get it back on since. it will show the SII logo for a few seconds then turns off. then proceeds to vibrate once every 2 seconds endlessly. thats all i can get out of it. it wont go into download mode or recovery or anything because as soon as i put the battery in, it tries to boot itself.
anybody have any ideas what is goin on here?
Click to expand...
Click to collapse
I've come to find out if the phone crashes this will happen, it's normal behavior believe it or not. If you will be patient and wait for about 7 to 10 minutes, the phone will finally reboot. The next reboot will be normal time again. This might be the device's way of protection, IDK.
cwyman said:
Sounds like the power button may be stuck which is a known issue with this phone. Here is a thread on the issue:
http://forum.xda-developers.com/showthread.php?t=1931310
Click to expand...
Click to collapse
thanks, this did the trick. but i think it may have been more so the volume up button. there is a metal piece that surrounds the volume button on the board, somehow it was coming off, pushed it back on and mashed the buttons a bunch, came right on.
autonami said:
...it will show the SII logo for a few seconds then turns off. then proceeds to vibrate once every 2 seconds endlessly...
Click to expand...
Click to collapse
This is almost certainly caused by a bad/stuck power (on/off) switch. It's a very common problem on all the US-carrier Galaxy S2 models. (Sprint, Boost, Virgin, Telus, T-Mobile, AT&T, etc. I don't think Verizon sold the SII)
You can check the switch by gently touching the physical switch (plastic cover/"button" removed) with a toothpick/pen/etc. As a "snap-action" switch, it shouldn't activate until you hear/feel it "snap" closed. If it's activating with a light/slight/tiny touch, the switch is bad. On my Sprint GS2, even the slightest brush against the power button caused it to wake the phone. Sometimes it would stick "on", and then the phone would reboot. I bought a new switch, soldered it in, and have no problems since.
If you don't have insurance coverage and are out of warranty, you can replace the switch yourself. Several eBay sellers offer replacement power switches for the SGH-T989 Galaxy S2. (about ten bucks)
Or, if you don't have mad soldering skills, several offer mail-in repair service as well, and most seem to have great feedback.
Two days ago, my T-Mobile Samsung Galaxy S3 dropped out of my coat pocket as i was running for the bus. I picked it up and saw the screen was cracked along the top left and bottom left hand side. Everything was working for the past two days and i figured i'll just wait till Christmas to get a new phone. This morning i took my phone off the charger and turned it on. The Samsung logo flashed, and then the boot animation for Slimrom (the custom rom i'm currently running on) flashed for about a second but then the screen went black. I did a battery pull but the weird thing is whenever i put my battery back in, even without touching the power button, it boots up by itself but then the screen goes black again. I can access TWRP and download mode but they both go black after a few seconds as well. I was able to successfully turn on my phone and have it fully function for about 15 minutes after putting it back on the charger, but it quickly blacked out again. It also keeps randomly booting up by itself which is weird. Im guessing this is a problem with the screen itself, but could it be a software issue because the device keeps booting up by itself? If it is the screen, will i have to buy a new one or is it not worth it? I've also tried using a different battery and i have the same issue so it can't be that. Any help is appreciated!
Sounds like an issue with the power button, it probably got stuck somehow either when you dropped it, or after you dropped it. Do a simple search for power button and you will find ways to fix it!
Holy crap i didn't even think of that! It makes total sense since every time i even tap my power button, even for just a second, it turns on. I've read around that clearing the cache or a factory reset could work. Is this true?
Unlikely, unless it's a software issue but it's always a possibility. Slam the phone against something to try to get the power button back into place, or open it up and try to see if you can fix it yourself, or replace it
The problem seems to be gone. I haven't had any issues for two days now. All i did was press the power button really hard multiple times. Thanks for you help man!