Hey guys,
Was wondering if anyone has experienced their Tab 3 8'' not waking up from sleep at random times.
This happens to be about once every day or two where i have to hold the power button to reset the tab because it won't wake.
I'm on the latest stock firmware.
Sent from my GT-I9100 using XDA-Developers mobile app
I had this happen before, but not as often as you experienced this. I am not sure what happens, but holding the power button to reset always fixes it, even though it is a pain to always have to do that. Also, I am running the latest CM13 rom, but I have experienced it on other roms as well.
Rawb0Ss said:
I had this happen before, but not as often as you experienced this. I am not sure what happens, but holding the power button to reset always fixes it, even though it is a pain to always have to do that. Also, I am running the latest CM13 rom, but I have experienced it on other roms as well.
Click to expand...
Click to collapse
Thanks for the reply. It's interesting it happens on CM13 too. I played around with different governors and schedulers but it doesn't change anything unfortunately.
I thought it might have something to do with leandroid toggling WiFi off for me at certain times as well, but I disabled that and it still goes into a sleep of death.
Sent from my GT-I9100 using XDA-Developers mobile app
44hats said:
Thanks for the reply. It's interesting it happens on CM13 too. I played around with different governors and schedulers but it doesn't change anything unfortunately.
I thought it might have something to do with leandroid toggling WiFi off for me at certain times as well, but I disabled that and it still goes into a sleep of death.
Click to expand...
Click to collapse
This problem is common maybe,it's because of your kernel is buggy or something
Related
Has anybody had an issue where when they press the power button, the screen will turn off for a moment, then come right back on? And if so, does anyone know a solution? I've looked around on the forums a bit, and its a problem on other phones where the screen has to be at at least 40% brightness, but it happens to me no matter how high or low the brightness setting is. Running ACS 1.0.2, but it has happened on other ROMS before, so i doubt it is a ROM issue.
I have had this happen too, but only in CM 7. And just figured it was because that rom is in the alpha stage right now. I have not had it happen in any other rom so far. When it was happening it was only some of the time. Was never able to figure out what the differences were when it would and wouldn't happen. Seemed like it was just random.
Sent from my SPH-D700 using XDA App
I've since found this happens very often when the brightness is up all the way, and the lower the brightness, the less it happens. Could this be a software problem?
I had this happen a few months ago. I wasn't sure what was causing it. At first it was turning on the lock sound, and the sound would play after the screen shuts off. Then the sound would kick the screen back on. I believe I changed ROM later and it never happened again. If you are on a custom ROM, maybe try reflashing?
I have had the exact same thing happen on 2 different Roms. Just wipe and flash and it fixes the problem.
BloodThirstyEmu said:
I have had the exact same thing happen on 2 different Roms. Just wipe and flash and it fixes the problem.
Click to expand...
Click to collapse
Unfortunately that only lessened it, not fixed it. It still happens enough that I leave the brightness down. Tried multiple times. :/
This still happens on a fresh stock install of EC05. Could this be a hardware issue that I should get checked out?
I'm running the stock ICS FF18, rooted. All seemed reasonably well for the first couple weeks, now the damn thing wants to randomly reboot.
I tried wiping, reinstalling the stock ICS, but the problem returned. Reboots happen maybe upwards of a dozen times a day. I've tried isolating the problem but unable to find a common variable...sometimes it happens when I'm in the middle of something, like web surfing or texting. Sometimes it happens when I press the power button, sometimes it happens when it's just sitting there not being touched, sometimes it happens when plugged it, sometimes when not plugged in.
I can't think I have a bad install twice and I'm not finding much on the forums here about others with a similar problem with the stock ICS. So I'm thinking either an app is being a b1tch and causing problems or perhaps something related to the battery? If there was one common theme, it does always happen later in the day or at night after the battery is down below 50%.
Does anyone have thoughts, ideas, suggestions on the likelihood of a bad battery or perhaps someone experienced something similar?
waltcoleman said:
I'm running the stock ICS FF18, rooted. All seemed reasonably well for the first couple weeks, now the damn thing wants to randomly reboot.
I tried wiping, reinstalling the stock ICS, but the problem returned. Reboots happen maybe upwards of a dozen times a day. I've tried isolating the problem but unable to find a common variable...sometimes it happens when I'm in the middle of something, like web surfing or texting. Sometimes it happens when I press the power button, sometimes it happens when it's just sitting there not being touched, sometimes it happens when plugged it, sometimes when not plugged in.
I can't think I have a bad install twice and I'm not finding much on the forums here about others with a similar problem with the stock ICS. So I'm thinking either an app is being a b1tch and causing problems or perhaps something related to the battery? If there was one common theme, it does always happen later in the day or at night after the battery is down below 50%.
Does anyone have thoughts, ideas, suggestions on the likelihood of a bad battery or perhaps someone experienced something similar?
Click to expand...
Click to collapse
Any special wi-fi config? (That's the culprit in my case.)
garwynn said:
Any special wi-fi config? (That's the culprit in my case.)
Click to expand...
Click to collapse
No...never installed the hotspot hack, did have foxfi installed, but did not reinstall after reloading ff18.
im also having the same problem as well, and the problem has became worse and worse,what started off as once or twice a day,is now at least occurring every 10 min.I think im about to downgrade right now to stock gingerbread and see what happens
My phone has always had some amount of random "poweroffs" (not really reboots, I pick up the phone expecting it to be on and it boots from scratch instead). However its much more frequent on ICS (FF18/FH13).
rocket321 said:
My phone has always had some amount of random "poweroffs" (not really reboots, I pick up the phone expecting it to be on and it boots from scratch instead). However its much more frequent on ICS (FF18/FH13).
Click to expand...
Click to collapse
U can always unroot back to el29(gingerbread)i was having the same problems and now i can enjoy my phone
Sent from my SPH-D710 using xda premium
I had that issue on AOKP M6, then realized my power button was actually broken. It would reboot the phone because it was actually stuck down internally. Had to get a new phone.
Sent from my SPH-D710 using xda app-developers app
R0CKSTAR3N3RGY said:
I had that issue on AOKP M6, then realized my power button was actually broken. It would reboot the phone because it was actually stuck down internally. Had to get a new phone.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
The power button seems to be a common cause of random reboots and that's what I'm leaning towards now as no other software fix has resolved the problem. Supposedly Sprint ordered me a replacement to swap out phones. I'd definitely recommend trying a different Kernel if on FF18 and if that doesn't fix it, try rolling back to EL29.
So yeah all the 4.2 Roms are making me very angry because I'll turn my screen off and it doesn't want to turn back on. Is anyone else having this issue? Does anyone know how to fix it?
dakota.breeden said:
So yeah all the 4.2 Roms are making me very angry because I'll turn my screen off and it doesn't want to turn back on. Is anyone else having this issue? Does anyone know how to fix it?
Click to expand...
Click to collapse
its called sod, sleep of death. its a common problem with 4.2.1 kernel source. just about everyone has experienced them, some a lot more than others, root and not rooted, custom rom/kernel and stock. google needs to fix it in its source. there are some anecdotal fixes, some claim work, others say dont work.
I'm running a 4.2 ROM (Beta at that) and am amazed at how much better my device is working. Everything is smoother and I haven't had a single issue. I honestly don't see how everyone is having so many problems with it.
063_XOBX said:
I'm running a 4.2 ROM (Beta at that) and am amazed at how much better my device is working. Everything is smoother and I haven't had a single issue. I honestly don't see how everyone is having so many problems with it.
Click to expand...
Click to collapse
im loving 4.2.1, cant say that i have any real issues with it. but, i do get sod occasionally, about once every ten days or so. if you around the forums, just about everyone has experienced them. some get them several times an hour, some several times a day, some several times a week, some just have had sod once or twice total. every device is different, they will have differing experiences.
dakota.breeden said:
So yeah all the 4.2 Roms are making me very angry because I'll turn my screen off and it doesn't want to turn back on. Is anyone else having this issue? Does anyone know how to fix it?
Click to expand...
Click to collapse
just go back to 4.1.2 if you are having issues.. 4.2.1 is a hit or miss IMO, some ppl get issues while for others it works great
Just a thought, how many of you had bt on when sod occurs?
Sent from my i9250
bk201doesntexist said:
Just a thought, how many of you had bt on when sod occurs?
Sent from my i9250
Click to expand...
Click to collapse
Interesting idea. I never use it and have never had any issues.
i never use bluetooth, but have had sod.
Same here.
063_XOBX said:
Interesting idea. I never use it and have never had any issues.
Click to expand...
Click to collapse
I've had issues with BT on 4.2.1 (OTA), turned it off after a) sending first file OK b) second file fail, and it stuck on " turning off".
Read below.
simms22 said:
i never use bluetooth, but have had sod.
Click to expand...
Click to collapse
dakota.breeden said:
Same here.
Click to expand...
Click to collapse
I've experienced a "black screen" on 4.2.1 (OTA), due to what i think was a crash from XDA app, probably from using it with an ad blocker, at least from what i could see. I could adb shell to the device, remount system, no problem. I've removed the ad blocker from the system, while still on 4.2.1 (OTA), and have not experienced the "black screen of death" again.
I have not experienced a "sleep of death" yet on this device. Note: definition of sod from my galaxy s days: device is in a state (after going into deep sleep) in which the only way to get it back is pulling the battery out. System is unresponsive.
I've flashed JOP40D through stock images, and haven't seen black screen/sod scenarios, recreating the same system, more or less.
As i rarely use BT, i haven't tested it again, but we shall see.
Op, what apps do you have installed? Do you use SR/AVS? If not, please raise voltages by 50mv at each step, or at least the lowest and highest step, for mpu, core and iva.
While the device is in this state, no communication is possible? Can you logcat? dmesg? Can you receive calls?
Sent from my i9250
I have not had that issue or any SOD and I am running CM10.1 with LeanKernel, my wife runs the same setup and she also has not had any issues.
I've seen SoD's on Jellybro CM10.1 with ZenSERIES kernel v14.1, but only when using the ZenX governor. If I change to Pegasusq, the SoD's stop. I guess ADA is still working out some of the kinks in ZenX. Ooo, and it looks like v15 was released a few days ago. Something new to flash.
Ok so I've been using a few different versions of the CM10 ROM and I've noticed a new problem. On occasion, when I go to wake the device, it will not wake. The keys light up, but thats it, the screen doesn't come on. The only way to get it working again is to hold down the power button and wait till it restarts. It's happened twice so far, not too frequently but annoying none-the-less.
Is there something I can do to fix this?
screwregi said:
Ok so I've been using a few different versions of the CM10 ROM and I've noticed a new problem. On occasion, when I go to wake the device, it will not wake. The keys light up, but thats it, the screen doesn't come on. The only way to get it working again is to hold down the power button and wait till it restarts. It's happened twice so far, not too frequently but annoying none-the-less.
Is there something I can do to fix this?
Click to expand...
Click to collapse
I thought you said you noticed a new problem...
Sent from my LG-P930 using xda premium
lordcheeto03 said:
I thought you said you noticed a new problem...
Sent from my LG-P930 using xda premium
Click to expand...
Click to collapse
I meant new to me! Though I looked around like crazy, cant find anything on this problem so I figured it was unique to my device.
screwregi said:
I meant new to me! Though I looked around like crazy, cant find anything on this problem so I figured it was unique to my device.
Click to expand...
Click to collapse
Nah, I'm mostly just giving you a hard time The CM10 nightly thread has gotten to be a beast to look through; seriously though... that problem is pretty old, and like you said; the only way to get around it is to hold power or do a battery pull. Just wait until you have an alarm go off in the morning and you can't turn it off!
Try the 2013 nightly, it does not appear to have this issue
Nz
notzippy said:
Try the 2013 nightly, it does not appear to have this issue
Nz
Click to expand...
Click to collapse
Maybe not, but it probably has other issues instead!
I can confirm that these issues still exist in the NIGHTLY (1/20) version. Just had it happen. Doesn't appear to be quite as frequent, but definitely still happening. I think it MAY have something to do with notifications, not sure though. Seems to often happen when I get a notification, I'll go turn it on and it wont wake from sleep.
screwregi said:
I can confirm that these issues still exist in the NIGHTLY (1/20) version. Just had it happen. Doesn't appear to be quite as frequent, but definitely still happening. I think it MAY have something to do with notifications, not sure though. Seems to often happen when I get a notification, I'll go turn it on and it wont wake from sleep.
Click to expand...
Click to collapse
Just saying; but there's already a thread for discussing CM10...
Haven't really found much about this issue but sometimes this gesture doesn't work, even after just barely putting the device to sleep. All the other gestures(flashlight, camera,music) work perfectly but the wake feature is hit or miss kinda thing.
Can amplify or something similar cause this issue?
Yes, same thing happened to me sometimes. Usually happens when I holding the phone on my hand or just pull it out of pocket, probably it's because the Pocket Mode turned on.
You can "force"-enable that feature into the kernel using for example Kernel Adiutor. It fixed the problem for me.
I also experience this issue when I take out the phone from my pocket. In this case, I need to do the double tap around three times to get it working. But in every other cases it is working without any issues.
Maybe we should report it on OP Bug report.
néonaloj said:
You can "force"-enable that feature into the kernel using for example Kernel Adiutor. It fixed the problem for me.
Click to expand...
Click to collapse
How do you happen to do that? I'm a complete noob when it comes to messing with the kernel