This has been happening for about 2 months now and has progressively started happening more frequently.
I've narrowed it down to a set of apps that are running when it happens.
Apps in use:
Screen On ( to keep the screen on while driving)
Waze (If you don't know what this app is stop reading now)
Play Music (Streaming through the Pioneer head unit)
It doesn't happen all the time but when it does the screen freezes for about 5 seconds then goes black and music stops the instant the screen freezes. Once the screen is black I try holding down the power button. Sometimes it'll power back on but most times I have to do a battery pull.
I've tried multiple ROM's and it still does it.
I've formatted my internal and external SD.
The last thing I still need to do is ODIN back to stock and then re-root.
Its taken me two weeks to get a logcat when the phone locks up. I'm not sure how much is needed so I'll attach the 2 hour logcat
Get Logcat here.
If someone can help me out and check out the logcat it would be extremely helpful. I can't ODIN back to stock yet because I'm on call all week and need a semi functioning phone till Friday.
I'm on stock unrooted NF4 and getting this sometimes. It happens when I am charging overnight. The next day, phone is off and I have to do a battery pull to turn it on. Luckily on those days I've gotten up before the alarm time. ?
p_synthesis said:
I'm on stock unrooted NF4 and getting this sometimes. It happens when I am charging overnight. The next day, phone is off and I have to do a battery pull to turn it on. Luckily on those days I've gotten up before the alarm time. ?
Click to expand...
Click to collapse
I had similar experience when using my phone as gps device in a long distance drive. Maybe because it got hotter?
Yesterday I was at the hospital with my son (he just had his tonsils removed). We were watching a movie Netflix and my phone locked up and rebooted 4 times within a 30 minute span. I finally had time afterwards to Odin back to stock and updated to NF4 then CFautoroot, TWRP latest and flashed Hyperdrive. I had hoped all was good but when i was cleaning out my car (streaming to the BT stereo) it locked up 10 minutes into my playlist.
Should I take it back to T-Mobile? Is there something else that I can do to troubleshoot?
Are you guys using any cpu apps?
Not that I'm aware of. I am using the compulsive kernel that is bundled with the latest hyperdrive.
Kernel issues, try other kernels.:good:
If you have a custom kernel, don't use setcpu in addition with the specific cpu governor app for that kernel. Also, don't set you minimum at 300 or lower. It's been documented to cause random reboots.
Not using setcpu. Was using the Hyperdrive tweaks to control frequencies.
I tried the latest compulsion kernel and within an hour it restarted twice. Tried the latest leanKernel and still rebooted. I guess I could go to stock, but I hate that music via bluetooth skips constantly on stock kernel.
The reboots are happening now at complete random, sometimes I'm using the phone other times I have the phone sitting on my desk and I'll look down and its at the Galaxy splash screen with the seandroid is not enforcing at the top.
I'm kinda lost at what it might be...I don't think its the ROM, and I'd really like to stick with hyperdrive just because for what I want in a ROM its all there.
wonderbread24 said:
Not using setcpu. Was using the Hyperdrive tweaks to control frequencies.
I tried the latest compulsion kernel and within an hour it restarted twice. Tried the latest leanKernel and still rebooted. I guess I could go to stock, but I hate that music via bluetooth skips constantly on stock kernel.
The reboots are happening now at complete random, sometimes I'm using the phone other times I have the phone sitting on my desk and I'll look down and its at the Galaxy splash screen with the seandroid is not enforcing at the top.
I'm kinda lost at what it might be...I don't think its the ROM, and I'd really like to stick with hyperdrive just because for what I want in a ROM its all there.
Click to expand...
Click to collapse
if u want to try something, when u ODIN flash the firmware, after it boots up, I ODIN flash TWRP then use my Stock Odex not rooted roms,then if u want root just flash SU from chainfire and install busybox,from the playstore, keep a copy on the sdcard and install.. and LEAVE the STOCK KERNEL, I use stock kernels and have no issues this way,
make a copy of my rom, remove the files u don't want from system/app and system/priv-app then flash that rom and SU right after that install busybox, and test that way. if u want I also have on the 3rd page a tethering rom, I have all the version, http://forum.xda-developers.com/showthread.php?p=51812491#post51812491
try it out, If u have problems, try not restore any data if u use titanium backup..
Related
Alright so ive used the search and couldnt find anything. I have a rooted s2 running eagles blood v1.1 and last night i flashed over lite'ing theme and now my phone screen will shut off and wont allow me to turn it back on, i have to hold the power button and it restarts. Ive reflashed eagleblood even recovered back to stock with just root and it continues to do it.
Any help would be much appriciated :/
Sent from my SGH-T989 using XDA App
Probably best to post this in the rom developer's thread. Any number of things can cause this behavior.
I would but my post count is low and i am unable to post there, so for now i am seeking help here.
ive tried un-rooting the phone, flashing the stock rom and no root, but have the same issue.
Did you wipe the caches in recovery?
treo...not! said:
Did you wipe the caches in recovery?
Click to expand...
Click to collapse
sure did, every time i reflashed/flashed i wiped everything
still contines, ive wiped everything, unrooted with factory resets, tried stock rom, eagles blood rom, reflashed multiple times.
screen shuts off and will not turn back on, have to hold power button and phone reboots.
IProbablyDidit said:
still contines, ive wiped everything, unrooted with factory resets, tried stock rom, eagles blood rom, reflashed multiple times.
screen shuts off and will not turn back on, have to hold power button and phone reboots.
Click to expand...
Click to collapse
Are you using SetCPU? I had this problem from a screen off profile where I could get calls or have my alarm go off yet not able to wake the screen unless I manually powered it off and on.
Sent from my EagleBlood-infused SGSII or my GTab 10.1 now "In Paris"
bhowanidin said:
Are you using SetCPU? I had this problem from a screen off profile where I could get calls or have my alarm go off yet not able to wake the screen unless I manually powered it off and on.
Sent from my EagleBlood-infused SGSII or my GTab 10.1 now "In Paris"
Click to expand...
Click to collapse
setcpu ? youll have to bare with me a little bit as i dont know probably all i should
odin back to stock with zedomax file! that usually fixes all probs
GRAB THIS STUFF :http://forum.xda-developers.com/showthread.php?t=1323878
Enjoy and also make sure u have the proper samsung drivers
movieaddict said:
odin back to stock with zedomax file! that usually fixes all probs
GRAB THIS STUFF :http://forum.xda-developers.com/showthread.php?t=1323878
Enjoy and also make sure u have the proper samsung drivers
Click to expand...
Click to collapse
i have tried this already, does not work :/
I'm having the same problem on rooted stock rom. It's getting more and more frequent. The phone just refuses to come back on after going to sleep. If I plug in the power/usb cable, it actually makes the connected noise as if it's actually awake but the screen stays off.
I've uninstalled all cpu and memory tweaking apps and am still experiencing the issue.
KaneHusky said:
I'm having the same problem on rooted stock rom. It's getting more and more frequent. The phone just refuses to come back on after going to sleep. If I plug in the power/usb cable, it actually makes the connected noise as if it's actually awake but the screen stays off.
I've uninstalled all cpu and memory tweaking apps and am still experiencing the issue.
Click to expand...
Click to collapse
ive tried everything, flashed over and over, un rooted, different roms etc nothing has worked so i just used zedomax's stock rom to restore the phone ( problem still continues) called tmobile and will have my replacement within a day or so, nothing else i can do i suppose.
though my problem did seem to start right when i flashed lite'ing theme for eaglesblood (not saying that caused it )
IProbablyDidit said:
ive tried everything, flashed over and over, un rooted, different roms etc nothing has worked so i just used zedomax's stock rom to restore the phone ( problem still continues) called tmobile and will have my replacement within a day or so, nothing else i can do i suppose.
though my problem did seem to start right when i flashed lite'ing theme for eaglesblood (not saying that caused it )
Click to expand...
Click to collapse
i had the same problem with the phone when i got it , i think its gotta be something with the phone.if mine continues then im sending it back also
tigerz0202 said:
i had the same problem with the phone when i got it , i think its gotta be something with the phone.if mine continues then im sending it back also
Click to expand...
Click to collapse
im starting to think it is a phone issue myself, going to find out Tuesday when my new one arrives though i am hoping it was an error on my part because this phone has the chance to be fantastic.
I was having random shutdowns with my 1st phone, the thing is I never did have stock long enough (rooted after 45min of gettjng) to see if it was the phone or root/rom(s).
My second phone is working great without any random shutdowns, but I'm still stock(running on second day of testing).
Gonna root and flash tomorrow and hope everything remains the same if not back it goes before my remorse period ends.
I really think it's phone related rather then a rom because I've never had this problem with previous phones.
So I would suggest on exchanging it.
Sent from my SGH-T989 using xda premium
htc2364 said:
I was having random shutdowns with my 1st phone, the thing is I never did have stock long enough (rooted after 45min of gettjng) to see if it was the phone or root/rom(s).
My second phone is working great without any random shutdowns, but I'm still stock(running on second day of testing).
Gonna root and flash tomorrow and hope everything remains the same if not back it goes before my remorse period ends.
I really think it's phone related rather then a rom because I've never had this problem with previous phones.
So I would suggest on exchanging it.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
i do appreciate the feed back, and from everyone who did give it. after lots of research and back and fourth between stock and custom roms i definitely wanted it to be the rom so it was fixable but im about 96% sure its the actual phone its self.
I rooted the phone using odin, then threw lost kernal on the phone. then used odin to flash the stock pulled kernel to eliminate the yellow triangle then used CWM to flash back to lost kernel. then went to zedomax V3. phone has been working very good. did freeze one time when opening a game and then restarted on its own after a few seconds but this is only once so far. I never knew about this problem until last night when i attempted to do a 100% charge with the phone off so I could reset batt stats. well, EVERYTIME I turn the phone off, it stayed off for a few seconds but then it would always turn itself back on... just flashed back to lost kernel (stable version) and it is now sitting powered off charging just like normal. I liked the OC ability but I will sometimes need my phone to stay off, say when I get on a plane...
anyone else have this problem
Same here I am running version V3 of Zedo, stock rooted.....and have the same issue the phone will not stay off. I have tried it both ways with QuickReboot and also manual with the power button and still have the same results. For me it is NBD but I have not been in a situation where I need to have the phone stay off.
I also tried it with quickreboot (not sure if I have the same app, blue circle with a yellow lightning bolt?). also, does your phone do this? when I shut down using the power button long press, choose power off and then hit ok, it shows the sprint logo with the exploding boxes looking screen, capacative buttons stay lit up for a while as its shutting down, quick reboot just SHUTS DOWN! lol, its like the difference of being on a PC and choosing shutdown or just flipping the switch on the back of the PSU. is it better to shut it down the stock method?
(side note- my palm pre power button started acting up so now I do what I can to use the epics power button as little as needed, which is why I have a screen icon to lock my phone and reboot with quick reboot)
yea we have the same quick reboot program....as for shutting it off which way, I think it is better to shut the phone down using the power button and have the phone go thru the shut down process vice just shutting down right there and then like a light switch. I do the same on a pc i try never to just hold the power button to shut down the pc unless it freezes, I just do the regular shut down process.
I flashed zedo v3 too and had problems too. At random moments i couldnt text, browse web,make calls or get calls unless i reboot. I unrooted it and phone went back to normal. Im sure zedomax will put out a better kernal, he knows wats up. Has anyone else had dat problem?
actually the not-staying-off was the only problem I even had on that kernel except the freeze that happened one time. today on lostkernel, right in a row I had 4 texts say they failed to be sent but then when I talked to the people later they all told me that they were actually delivered. I even rebooted the phone after the first 2 and the next 2 still said failed so I highly doubt that it was anything other than a weird problem with the network though... although I dont know exactly how the whole process works. I think I am going to go back to zedomax later though, I dont fly often so if I end up on a plane Ill just flash lostkernel again since I leave both files on the card on a daily basis. and I like the setcpu profiles. could always go with the experimantal build of lost kernel since technically the zedomax is a beta as well...
So, lately my phone has been acting kinda weird.. Basically, it'll shut off on it's own, no matter what my battery level or if I'm on the charger, its pretty random. When I go to turn it on, it shows me the samsung logo and shuts off after about 3 seconds of the galaxy s3 logo. It does the same in download mode and recovery. The phone will stay off and do that for an hour or more, and then itll turn on and be all dandy again for hours or at least another day. I'm going to take off all my pictures on the sdcard and odin back to stock as soon as possible for warranty, but does this sound like a hardware failure or software? I read about the s3 sudden death syndrome, but this one isnt permanent. Any ideas?
I agree with your assessments.
I'd wonder about overheating or a bad battery.
Sent from my SGH-T999 using xda app-developers app
what's your setup as of right now?
Beware if it shuts down when your flashing back to stock in the middle of the process it may never turn back on.
Sent From My Galaxy S3 Boricua 100%
It might be the kernel that came with the ROM you installed. I used to have problem with ktoon kernel.
I'm running Darthstalker XI, the problem happened with both the stock kernel and the faux samsung kernel. The battery is fine, its completely flat with no bumps or humps. I managed to turn it on once yesterday but as I was getting ready to transfer over the files the phone shut off and didn't start again. I'll try to get it running tomorrow.
EDIT: Now that I think about it, the problem happened when I dirty flashed XI over X. Afterwards I did a wipe and clean install of X1 and the problem persisted. Has anyone else on Darthstalker/UDVLJA based roms had this?
EDIT2: Well after being on the charger all day, I noticed that the green samsung battery icon was on the screen, something it only does when it's about to turn on properly. I instantly pulled out the sdcard and put the latest cm10 nightly and gapps on there and I booted to recovery, wiped, and flashed them right up, no issues. I booted just fine, I signed up and I was downloading youtube, latest now updates etc (bare essentials).... and it shut off again. I'm positive now that it's a hardware failure
mejorguille said:
I'm running Darthstalker XI, the problem happened with both the stock kernel and the faux samsung kernel. The battery is fine, its completely flat with no bumps or humps. I managed to turn it on once yesterday but as I was getting ready to transfer over the files the phone shut off and didn't start again. I'll try to get it running tomorrow.
EDIT: Now that I think about it, the problem happened when I dirty flashed XI over X. Afterwards I did a wipe and clean install of X1 and the problem persisted. Has anyone else on Darthstalker/UDVLJA based roms had this?
EDIT2: Well after being on the charger all day, I noticed that the green samsung battery icon was on the screen, something it only does when it's about to turn on properly. I instantly pulled out the sdcard and put the latest cm10 nightly and gapps on there and I booted to recovery, wiped, and flashed them right up, no issues. I booted just fine, I signed up and I was downloading youtube, latest now updates etc (bare essentials).... and it shut off again. I'm positive now that it's a hardware failure
Click to expand...
Click to collapse
If you have an app that controls kernel voltage that is still set up for set on boot and the voltage is too low when it boots or is granted root it'll kill it in this manner. Otherwise your phone is [email protected]#
Sent from my SGH-T999 infected with AnthraX using Tapatalk 2
I'd wager that if any overclocking/undervolting was done, it was disabled at the onset of problems. OP seems smarter than orangutan.
I used the phone for work, not play, no overclocking was done neither was any undervolting. I ran stock kernel settings.
Aerowinder said:
I'd wager that if any overclocking/undervolting was done, it was disabled at the onset of problems. OP seems smarter than orangutan.
Click to expand...
Click to collapse
I remember a time when XDA had helpful answers and users weren't reduced to insults. I've been around a couple years, hacked more phones than I can count and flashed hundreds of roms in my days, back when everything was still done in adb and terminal emulator. It's no wonder a lot of decent user has started moving over to rootzwiki
I got my S3 last July and rooted it and installed a rom the first day. I've had zero issues with it so far outside of the occasional freeze or reboot. I've pretty much only run Task's AOKP rom. I do not think my problem is rom or kernel related whatsoever, but it seems more like some type of hardware issue.
Anyway, two days ago I was running the 4-26 version of Task's rom with the stock kernel. I did a full wipe and clean install. The phone had been running trouble free with no issues for a couple of days. Suddenly with around 75% battery, it just rebooted when I turned the screen on but kept failing and starting again at the Samsung screen or sometimes made it to the underwear kernel screen. I tried to go into recovery and it started into recovery for about a second and went into reboot again. Tried download mode and it went right in and then rebooted after a second or two. It will not stay in any mode for longer than a second or two. I've tried connecting it to the pc and put it into dl mode and it does the same. I have a usb jig and it puts into download but only for a second or two.
I'm sure I'm missing something, but any help would be appreciated.
double RL said:
I got my S3 last July and rooted it and installed a rom the first day. I've had zero issues with it so far outside of the occasional freeze or reboot. I've pretty much only run Task's AOKP rom. I do not think my problem is rom or kernel related whatsoever, but it seems more like some type of hardware issue.
Anyway, two days ago I was running the 4-26 version of Task's rom with the stock kernel. I did a full wipe and clean install. The phone had been running trouble free with no issues for a couple of days. Suddenly with around 75% battery, it just rebooted when I turned the screen on but kept failing and starting again at the Samsung screen or sometimes made it to the underwear kernel screen. I tried to go into recovery and it started into recovery for about a second and went into reboot again. Tried download mode and it went right in and then rebooted after a second or two. It will not stay in any mode for longer than a second or two. I've tried connecting it to the pc and put it into dl mode and it does the same. I have a usb jig and it puts into download but only for a second or two.
I'm sure I'm missing something, but any help would be appreciated.
Click to expand...
Click to collapse
Check the bad power button or bad battery.
tomy1986.nt said:
Check the bad power button or bad battery.
Click to expand...
Click to collapse
Good suggestion on the power button. Would make sense, but it seems to be fine feels exactly like it should. I took it apart and even left the button off. The part of it that's attached to the motherboard is very crisp and pops right back after pushing it in. Doesn't seem to be the problem. I've tried three different batteries with the same results. Guess I'm going to the service center tomorrow. Damn
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.