My Tab is running stock HC 3.2, only rooted with CWM v5.x.
Couple days ago I'm experiencing that the device is rebooting randomly while it's in deep sleep.
Does any fix or patch for this, and can I check a log or something to find why does it do that?
Thanks in advance.
Maybe it's the famous "Sleep of Death" issue?
Check this out:
http://forum.xda-developers.com/showthread.php?t=1386785
I experienced this issue in stock HC. However, after flashing CM9 it stopped. Must be some bug in Samsung's firmware...
Try reflashing stock ROM and see if it helps!
Hope I've helped!
Leave flashing as a second option
air001 said:
My Tab is running stock HC 3.2, only rooted with CWM v5.x.
Couple days ago I'm experiencing that the device is rebooting randomly while it's in deep sleep.
Does any fix or patch for this, and can I check a log or something to find why does it do that?
Thanks in advance.
Click to expand...
Click to collapse
Try to Wipe/Clean data in recovery mode first, I used to have the same problem but with stock HC (plus some batteries issue), leave flashing as a second option. Just FYI, it seems that ICS rom doesn't have this bug so far, so you can try it if you want.
Hey so when I update my phone from a nightly from August to a nightly in September I keep on getting random force reboots. I managed to flash to the experimental M1 nightly and i'm stable there, but anything past that and I get force reboots (my phone randomly shuts off).
Any help would be greatly appreciated! Thanks!
Are you sure it is due to CM? I have the same issue with the stock Rom rooted.
Well it only happens on any nightly past the experimental M1.
Have you tried a clean flash? Or have you just been doing dirty flashes over and over?
Yeah, I tried a full wipe then install last night.. didn't get a force reboot for about an hour but then after that it went back to "normal" and happened like every five minutes.
Thank God i made my back before I installed cm10 i had and still have the same issue, so i went back to stock+root if anyone know the fix post it thanks
kevin2005 said:
Thank God i made my back before I installed cm10 i had and still have the same issue, so i went back to stock+root if anyone know the fix post it thanks
Click to expand...
Click to collapse
Same here I had tested e different rom and mostly reliable I found was DarthStaker v7. But looks like samsung did something with the new s3 hardware because before my phone replacement my first s3 was smooth as a butter with any rom but now is a pita toget it shorted out with new rom. Stock+root works way better that any rom.
Sent from my SGH-T999 using xda premium
So I installed Team Eos4 nightly build 94 with kat kernel 80b and it is great so far with only a couple odd things. Has anyone trying this had their device turn off when it it should just be sleeping? Mine will shut off if the screen goes dark for more than just a few minutes. Thanks.
Edit: i messed up. I was on the stock kernel, not kk 80b. I must have flashed the kernel first before the rom. Idiot i am. Anywho, other than that i followed all protocol set up by the developers. Am using rogue recovery. Just flashed Kat kernel 80b now, so I'll see what happens. Thanks for the replies.
What recovery are you using?
Did you wipe the caches, system and do a factory reset in recovery before flashing?
OK, it is still happening. I'm running rogue xm recovery 1.5.0 which claims to be a cwm 5 based recovery.
Same issue. If the pad sleeps for more than minute or so-- haven't done an official time-it will basicly turn itself off. Need to long press the power button to turn back on and it goes through the regular boot process. I don't think this is some sort of deep sleep mode, but not really sure.
Sent from my Transformer TF101 using Tapatalk HD
I would install the GooManager and install TWRP.
Many of the CWM 5 recoveries have issues with Android 4.2 file structure.
After installing GooManager, tap the menu button in the top right and Install OpenRecoveryScript.
That is all you need to do to get TWRP.
frederuco said:
I would install the GooManager and install TWRP.
Many of the CWM 5 recoveries have issues with Android 4.2 file structure.
After installing GooManager, tap the menu button in the top right and Install OpenRecoveryScript.
That is all you need to do to get TWRP.
Click to expand...
Click to collapse
Thank you for your help. I guess afterward it would be necessary to go through the whole process of wiping and flashing again?
Sent from my Transformer TF101 using Tapatalk HD
I would highly recommend it.
Update: interesting experiences yesterday with the rom. Was doing fine with me at work when there was no WiFi access, but once back home it would sometimes do its little sleeping trick. I decided to wipe and re flash the room and then the kernel, but it is still happening. Will try a full factory reset and flash again.
Sent from my Transformer TF101 using Tapatalk HD
I am having a similar problem but only with some versions/updates of this ROM.
I leave my Transformer on pretty much all the time. I noted on an earlier version (I think it was the Nightly 92) that my machine worked great all day. It would be actively used, sleep some, be used some more, sleep, etc...... However, when I went to bed at night (still leaving it on) I would get up in the morning and find the Transformer requiring the long power button hold to restart/cold boot. This happened for several days. I believe when I updated to and used the B136 Build all worked well and I did not see this problem. I updated to B143 yesterday and this problem occurred again this morning when I tried to turn the Transformer on.
I have not seen the issue during the day, even if I let the unit sit for a few hours untouched. a few other points to note:
Battery was always above 75% when the issue occured. Don't think it is a battery issue.
CPU is set to 312/1400 SmartassV2 (has been this way with all versions of the ROM that have or do not have this issue)
Virtually no other issues with the ROM. It is awesome.
Thoughts or similar experiences???
Shesakillatwo said:
I am having a similar problem but only with some versions/updates of this ROM.
I leave my Transformer on pretty much all the time. I noted on an earlier version (I think it was the Nightly 92) that my machine worked great all day. It would be actively used, sleep some, be used some more, sleep, etc...... However, when I went to bed at night (still leaving it on) I would get up in the morning and find the Transformer requiring the long power button hold to restart/cold boot. This happened for several days. I believe when I updated to and used the B136 Build all worked well and I did not see this problem. I updated to B143 yesterday and this problem occurred again this morning when I tried to turn the Transformer on.
I have not seen the issue during the day, even if I let the unit sit for a few hours untouched. a few other points to note:
Battery was always above 75% when the issue occured. Don't think it is a battery issue.
CPU is set to 312/1400 SmartassV2 (has been this way with all versions of the ROM that have or do not have this issue)
Virtually no other issues with the ROM. It is awesome.
Thoughts or similar experiences???
Click to expand...
Click to collapse
Been messing around with things.. This issue only happens when unplugged from charger. I installed wake lock to see if that would do anything. It seems to eliminate the problem but then you have battery drain. This reminds me of an issue that occured to some people after the ICS update.
Sent from my Transformer TF101 using Tapatalk HD
frederuco said:
I would install the GooManager and install TWRP.
Many of the CWM 5 recoveries have issues with Android 4.2 file structure.
After installing GooManager, tap the menu button in the top right and Install OpenRecoveryScript.
That is all you need to do to get TWRP.
Click to expand...
Click to collapse
FWIW, I'm still using Rogue 1.5, and I've flashed countless EOS 4 builds without issue. I'm not sure what build the OP actually installed since the latest is only 93, and it only came out tonight. I've also had no issues with sleep on any builds.
Sent from my Transformer TF101 using xda premium
just lou said:
FWIW, I'm still using Rogue 1.5, and I've flashed countless EOS 4 builds without issue. I'm not sure what build the OP actually installed since the latest is only 93, and it only came out tonight. I've also had no issues with sleep on any builds.
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
That should have read 92. I have just went up to the 93. So far, so good. This ROM is fantastic performance.
Sent from my Transformer TF101 using Tapatalk HD
wekurtz74 said:
That should have read 92. I have just went up to the 93. So far, so good. This ROM is fantastic performance.
Sent from my Transformer TF101 using Tapatalk HD
Click to expand...
Click to collapse
I upgraded from B143 to 93 last night just before going to bed, left the tablet on all night, and again this morning had to do the long power button hold to get the tablet booted. A minor inconvenience when stacked up against the gains the ROM gives me. Guess we'll wait for the next version and see how that goes...............
---------- Post added at 09:31 AM ---------- Previous post was at 09:21 AM ----------
One other thing I noticed in the Dev Threads. If I understood correctly, some builds are appear to be done with "Linaro toolchain", and some not. I do not even know what "Linaro toolchain" is, but if some use this and some do not, could this possibly be a reason I have issues with some builds and not others. Sorry in advance if this is a stupid question???
Now I had the opposite experience. On 93 it made it all night without issue, but today it is doing the shutdown. There is some variable that is in play here that I am missing.
wekurtz74 said:
Now I had the opposite experience. On 93 it made it all night without issue, but today it is doing the shutdown. There is some variable that is in play here that I am missing.
Click to expand...
Click to collapse
As an FYI, I have downloaded and installed B145 and will let you know how it goes. To add to my input here, everytime I upgrade/flash:
1. I do a Cache wipe
2. I do a Dalvik Wipe
3. I flash the ROM
4. Flash the 80B Kernel
5. I flash the GAPPS
6. I again do both a Cache and a Dalvik Wipe
7. I reboot.........
I also have the TWRP Flash script/app installed.
So, I attached my dock last night for the first time since I rooted and moved to the 4.2 ROM to check out the Battery changes for the Dock. They worked well and the ROM continues to be awesome. On going to bed, I left the dock attached and all started up fine this morning. Since having the dock attached is adding another variable, I will disconnect it before going to bed tonight and provide an update tomrrow.
Short update. Left my unit on all night and responded perfectly this morning when I tried to wake it up. B145 with the v3 Battery patch seems to be working Great!!!!!
After Several days I can report that B145 with the v3 Battery patch seems to be working perfectly for me.
Yesterday I installed b148 with the kat kernel 85 and within a matter of minutes got several sudden reboots and at least 1 SOD. On top of that the battery went down 30% (from 100% state) in about 1 hour of use. Since I don't have any bluetooth devices for my tablet I flashed kernet 80b, and I haven't experienced reboots or SODs. And, at least today, battery usage seem to be back to the normal level (~20%/hour).
Sent from my Transformer TF101 using Tapatalk HD
[Edit] Ok, so I just learned Timduru issued a new test kernel, 85b. Will be giving that one a try...
landous said:
Yesterday I installed b148 with the kat kernel 85 and within a matter of minutes got several sudden reboots and at least 1 SOD. On top of that the battery went down 30% (from 100% state) in about 1 hour of use. Since I don't have any bluetooth devices for my tablet I flashed kernet 80b, and I haven't experienced reboots or SODs. And, at least today, battery usage seem to be back to the normal level (~20%/hour).
Sent from my Transformer TF101 using Tapatalk HD
[Edit] Ok, so I just learned Timduru issued a new test kernel, 85b. Will be giving that one a try...
Click to expand...
Click to collapse
try the 92 kernel also and preview 150.
scott
wn1ytw said:
try the 92 kernel also and preview 150.
scott
Click to expand...
Click to collapse
I am heading this way.. will let you know how it goes.. as I have had most of the problems described in this thread over the last few days..
So I just rooted my phone and flashed cyanogen cm10 for my Blaze. It worked flawlessly for the first 2 days but then suddenly would either freeze for a few seconds and shut off or just plain shut off on me. It happens randomly like it doesn't happen during anything specific. I searched Google and the forums but couldn't find a solution. Please can someone help me out?
Sent from my SAMSUNG-SGH-T769 Cm10 using Tapatalk 2
Daze7 said:
So I just rooted my phone and flashed cyanogen cm10 for my Blaze. It worked flawlessly for the first 2 days but then suddenly would either freeze for a few seconds and shut off or just plain shut off on me. It happens randomly like it doesn't happen during anything specific. I searched Google and the forums but couldn't find a solution. Please can someone help me out?
Sent from my SAMSUNG-SGH-T769 Cm10 using Tapatalk 2
Click to expand...
Click to collapse
Are you running the latest nightly or the 'stable' build? The 'stable' build (note the "") isn't that stable and from the sound of it you are experiencing the screen of death (SoD) that I believe is present in the 'stable' build.
If you flashed the 'stable' build, flash the newest nightly instead. Or better yet, head on over here and also flash this (it's better than CM10 IMO - Just be sure to flash the kernel AFTER the rom). :good:
Daze7 said:
So I just rooted my phone and flashed cyanogen cm10 for my Blaze. It worked flawlessly for the first 2 days but then suddenly would either freeze for a few seconds and shut off or just plain shut off on me. It happens randomly like it doesn't happen during anything specific. I searched Google and the forums but couldn't find a solution. Please can someone help me out?
Sent from my SAMSUNG-SGH-T769 Cm10 using Tapatalk 2
Click to expand...
Click to collapse
Which version of CM10? No reboots here on Provision.. Used CM10 latest nightly as a base.. If you have random reboots then I should too.. Also a logcat would be helpful.
Sent from my Provisioned Galaxy S Blaze
Im on the stable version, but ill try the nightly like the first post suggest or the link you provided
Edit: logcat on the way sorry about that
Sent from my SAMSUNG-SGH-T769 using Tapatalk 2
anactoraaron said:
Are you running the latest nightly or the 'stable' build? The 'stable' build (note the "") isn't that stable and from the sound of it you are experiencing the screen of death (SoD) that I believe is present in the 'stable' build.
If you flashed the 'stable' build, flash the newest nightly instead. Or better yet, head on over here and also flash this (it's better than CM10 IMO - Just be sure to flash the kernel AFTER the rom). :good:
Click to expand...
Click to collapse
Hey, I downloaded the rom and kernel that u suggested. When i plugged in my phone to my laptop to transfer the files to my sd card i noticed that my internal sd and ex sdcard now reads as 'Generic Hierarchical'. Prior to this i did notice that my ex and internal memory were not showing the correct amount of space after rooting but i was so happy with the root that it slipped my mind somehow.
What in the world is generic hierarchical? And how can I get it safely to Fat32 to flash the ParanoidAndroid without messing up my phone?
Daze7 said:
Hey, I downloaded the rom and kernel that u suggested. When i plugged in my phone to my laptop to transfer the files to my sd card i noticed that my internal sd and ex sdcard now reads as 'Generic Hierarchical'. Prior to this i did notice that my ex and internal memory were not showing the correct amount of space after rooting but i was so happy with the root that it slipped my mind somehow.
What in the world is generic hierarchical? And how can I get it safely to Fat32 to flash the ParanoidAndroid without messing up my phone?
Click to expand...
Click to collapse
Go to settings/storage. Press menu. Then USB computer connection. There you can choose. Select USB mass storage. When connected to the computer it will prompt you if you want to move files from computer to your phone.
Sent from my Provisioned Galaxy S Blaze
In the end I just went back to stock and did a clean new root, this time with ParanoidAndroid. I loved the cm10 stable i had but the phone shutting off was t0o much. Thanks for all the help though i really appreciate it. :angel:
As the title says my P5113 reboots instead of powering off. Its been doing this since I've rooted and flashed a new rom and every rom there after. any help is much appreciated.
Cataulin said:
As the title says my P5113 reboots instead of powering off. Its been doing this since I've rooted and flashed a new rom and every rom there after. any help is much appreciated.
Click to expand...
Click to collapse
Here's something related to your post. Read here: http://forum.xda-developers.com/showthread.php?t=2429173
Cataulin said:
As the title says my P5113 reboots instead of powering off. Its been doing this since I've rooted and flashed a new rom and every rom there after. any help is much appreciated.
Click to expand...
Click to collapse
I don't believe the previous post reference is applicable since that guy is stock. I had this same issue plus the horrible battery drain when I went to 4.4, and every 4.4 rom I went to didn't change it. I must have tried every 4.4 out there, I like the feature set on 4.4 but not as much as the other. I just yesterday flashed back to slimbean 2.2 which is a 4.3 rom and all my issues disappeared. My tab now powers off and reboots into recovery properly now. And battery, I'm at 16.5 hours with 4 hours of screen time and still at 60%.
wolfclan68 said:
I don't believe the previous post reference is applicable since that guy is stock. I had this same issue plus the horrible battery drain when I went to 4.4, and every 4.4 rom I went to didn't change it. I must have tried every 4.4 out there, I like the feature set on 4.4 but not as much as the other. I just yesterday flashed back to slimbean 2.2 which is a 4.3 rom and all my issues disappeared. My tab now powers off and reboots into recovery properly now. And battery, I'm at 16.5 hours with 4 hours of screen time and still at 60%.
Click to expand...
Click to collapse
Ill try that. thanks will report back if fixed.