Hi, I have a rooted S3, just recently I noticed that my phone will automatically set the screen timeout to zero (0) second once a while!! This is very strange, because you know normally the zero second option doesn't even appear.
Currently it is happening once a day or every two day. It is so annoying.
I wonder if someone injected some code in the rooted ROM (I am using the Roger rooted ROM), one of my app is doing that? Anyone is having the same issue??
vincarama said:
Hi, I have a rooted S3, just recently I noticed that my phone will automatically set the screen timeout to zero (0) second once a while!! This is very strange, because you know normally the zero second option doesn't even appear.
Currently it is happening once a day or every two day. It is so annoying.
I wonder if someone injected some code in the rooted ROM (I am using the Roger rooted ROM), one of my app is doing that? Anyone is having the same issue??
Click to expand...
Click to collapse
try a differnt rom?
Wipe, and reflash. Step one, every time.
Pink pony Gs2 i777
Pure Google Gnex i9250
Pink stallion Gs3 i747
Stock tweaked Asus tf201
Related
Anyone else having sleep of death issues recently on JB? Im running the stock JRO03C Build rooted, busyboxed, and deodexed (http://forum.xda-developers.com/showthread.php?t=1737849), and only MOD I have on top of that is a battery percentage mod(http://forum.xda-developers.com/showthread.php?t=1738335). Recently in the past week or so I've had a few sleep of death incidents. This morning was one of them where my alarm didn't go off! My notification light was on, and my phone was plugged into the charger, but couldn't wake it. Anybody else experiencing this issue, or have any suggestions of things to look at/try? All the other threads on this are from ICS, so not sure if they would apply since this in on pretty much stock JB.
I don't know but think people either don't know the meaning of stock or I have to learn the meaning
What you described is not stock Rom.and to your answer no I don't get sod.
True. I'm not on stock, I guess I meant to say that my ROM was created from stock. Good to know that someone else is not experiencing this though. Thanks.
The only issue I have is that the phone freezes after recieving or making a call.
That happened about two times only.
I only have about two weeks with the phone and I upgraded to JB as soon I got the phone. I didn't even run the setup wizar in JB: just unlocked the bootloader and flashed 4.1.
I though it was a bad flash and applied the yakju 4.0.4 factory image and the flashed the OTA to get stock JB 4.1.1. I had the issue only one time with that setting.
Right now, my phone is completely yakju. I don't remember my variation. I just recall it came with 4.0.1 and upgraded itself to 4.0.2 and no more.
Cheers!
andrewhansen86 said:
Anyone else having sleep of death issues recently on JB? Im running the stock JRO03C Build rooted, busyboxed, and deodexed (http://forum.xda-developers.com/showthread.php?t=1737849), and only MOD I have on top of that is a battery percentage mod(http://forum.xda-developers.com/showthread.php?t=1738335). Recently in the past week or so I've had a few sleep of death incidents. This morning was one of them where my alarm didn't go off! My notification light was on, and my phone was plugged into the charger, but couldn't wake it. Anybody else experiencing this issue, or have any suggestions of things to look at/try? All the other threads on this are from ICS, so not sure if they would apply since this in on pretty much stock JB.
Click to expand...
Click to collapse
+1
I was having screen freeze while using the google reader app. Had to pull battery.
Am running the same ROM, with battery percentage mod as well. Stock kernel. Not sure why.
possible sleep of death fix?
andrewhansen86 said:
Anyone else having sleep of death issues recently on JB?.
Click to expand...
Click to collapse
I was running stock 2.3.2 on my Evo Shift and was experiencing this issue. try backing up your sd card onto your desktop and then formatting it. it worked for me. I run an unofficial version of cm9. the only issue i still have is that my htc logo that shows at boot is still gone, and with that gone I cant easily select items in hboot/fastboot on the device. but thats for another forum for another day.
chorner said:
I was running stock 2.3.2 on my Evo Shift and was experiencing this issue. try backing up your sd card onto your desktop and then formatting it. it worked for me. I run an unofficial version of cm9. the only issue i still have is that my htc logo that shows at boot is still gone, and with that gone I cant easily select items in hboot/fastboot on the device. but thats for another forum for another day.
Click to expand...
Click to collapse
1. 2.3.2 isn't JB.
2. The GNex doesn't have an SD.
3. It's also NOT an Evo shift.
4.Nice first post.
063_XOBX said:
1. 2.3.2 isn't JB.
2. The GNex doesn't have an SD.
3. It's also NOT an Evo shift.
4.Nice first post.
Click to expand...
Click to collapse
good point. i also was wrong about the sd card anyways. i flashed cm9 back on it. turned auto brightness off. it had the issue. rebooted. turned it back on. re-enabled autobrightness. no issue.
thanks for the compliment.
I'm on 4.2 and have the issue. A few times a day, I'll pull it out of my pocket and I see the "backlight" turn on but screen is on. (I'm not sure how there is a backlight if is amoled but i do see some kind of something very very faint )
In Developer Options put all animation scales to .5x.
el_charlie said:
The only issue I have is that the phone freezes after recieving or making a call.
That happened about two times only.
I only have about two weeks with the phone and I upgraded to JB as soon I got the phone. I didn't even run the setup wizar in JB: just unlocked the bootloader and flashed 4.1.
I though it was a bad flash and applied the yakju 4.0.4 factory image and the flashed the OTA to get stock JB 4.1.1. I had the issue only one time with that setting.
Right now, my phone is completely yakju. I don't remember my variation. I just recall it came with 4.0.1 and upgraded itself to 4.0.2 and no more.
Cheers!
Click to expand...
Click to collapse
I experienced a similar issue on 4.1, but it would happen almost once day (very annoying). I'm now on a 4.2 rom and I haven't seen the issue in weeks. :laugh:
I have a problem. Yesterday, my phone started rebooting randomly. It's been happening almost every time I use the phone. I rooted and flashed the Calk E4GT 2 4.0.4 ROM about a month or so ago and have had no issues to speak of with it at all. I disabled the facial unlock because I noticed that the reboot would routinely happen with either I was trying to unlock or put the phone in standby or while I was trying to use it in some way.
In the past I had noticed similar behaviors randomly, but never became a persistent issue. Anyone have any ideas as to what the culprit could be?
If I need to reload...how do I go about doing that? Just pick a new ROM and flash from CM to start from scratch? If so, what's a good ROM that is 4.0.4 based to run with....Cyanogenmod?
willjr0k5 said:
I have a problem. Yesterday, my phone started rebooting randomly. It's been happening almost every time I use the phone. I rooted and flashed the Calk E4GT 2 4.0.4 ROM about a month or so ago and have had no issues to speak of with it at all. I disabled the facial unlock because I noticed that the reboot would routinely happen with either I was trying to unlock or put the phone in standby or while I was trying to use it in some way.
In the past I had noticed similar behaviors randomly, but never became a persistent issue. Anyone have any ideas as to what the culprit could be?
If I need to reload...how do I go about doing that? Just pick a new ROM and flash from CM to start from scratch? If so, what's a good ROM that is 4.0.4 based to run with....Cyanogenmod?
Click to expand...
Click to collapse
I'm having the same problem with the stock ff18 rooted...started out of the clear blue, can't place my finger on a consistent pattern. I'm gonna try installing a new kernel and see if that helps. If it works I'll let you know.
I disabled facial recognition security and cleared dalvik and normal cache with clockworkmod. My phone hasn't rebooted basically all day so far.
Something must have been stuck in the cache possibly that was causing issues.
Sent from my SPH-D710 using xda app-developers app
I'm now on CM10.1 official, but tried stock, Cataclysm and a couple of other roms and kernel combinations.
I always end up with BSOD (black screen of death) at some point. The screen just turns off and doesn't comes on again, even if it receives a call (it does ring though).
Last BSOD was on today's CM10.1 already. I had to remove the battery.
It's not a usual thing to happen, but it ends up happening sometime.
Don't know if it's my new Mugen 2000 mAh battery, or some program I restore using TitaniumBackup. Never had a BSOD in 4.1 roms.
joooe said:
I'm now on CM10.1 official, but tried stock, Cataclysm and a couple of other roms and kernel combinations.
I always end up with BSOD (black screen of death) at some point. The screen just turns off and doesn't comes on again, even if it receives a call (it does ring though).
Last BSOD was on today's CM10.1 already. I had to remove the battery.
It's not a usual thing to happen, but it ends up happening sometime.
Don't know if it's my new Mugen 2000 mAh battery, or some program I restore using TitaniumBackup. Never had a BSOD in 4.1 roms.
Click to expand...
Click to collapse
It is a common issue with custom kernels right now. It is due to a bug in the source. We have to wait for Google to fix it. For the meantime use a stock kernel or anything close to stock like 007 kernel
Sent from my Galaxy Nexus using Tapatalk 2
joooe said:
I'm now on CM10.1 official, but tried stock, Cataclysm and a couple of other roms and kernel combinations.
I always end up with BSOD (black screen of death) at some point. The screen just turns off and doesn't comes on again, even if it receives a call (it does ring though).
Last BSOD was on today's CM10.1 already. I had to remove the battery.
It's not a usual thing to happen, but it ends up happening sometime.
Don't know if it's my new Mugen 2000 mAh battery, or some program I restore using TitaniumBackup. Never had a BSOD in 4.1 roms.
Click to expand...
Click to collapse
deeren said:
It is a common issue with custom kernels right now. It is due to a bug in the source. We have to wait for Google to fix it. For the meantime use a stock kernel or anything close to stock like 007 kernel
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
the same issue with stock kernels too(unrooted and rooted).
btw, its not called bsod, its called sod(sleep oif death)
It's probably not kernel related. Did you turn your animations off in developer settings? Try turning them to .5. Helped me and several others. Running mmuzzy with tiny kernel.
klobkelosh said:
It's probably not kernel related. Did you turn your animations off in developer settings? Try turning them to .5. Helped me and several others. Running mmuzzy with tiny kernel.
Click to expand...
Click to collapse
Will try that.
Thanks everyone.
I have the same BSOD/SOD issue... will try the 0.5 animation trick and report back. I would hate to go back to 4.1 roms.
I found new love for my SGN with the 4.2.1 smoothness.
Did it help?
I am experiencing SOD / BSOD on my Nexus 4 + latest CM10.1 nightly from time to time... (stock kernel).
In developer settings there are actually three settings regarding animations - are all to be set to .5?
Best regards,
ww
For me it did, yes.
No more BSOD.
I put them all to x.5
I've been diagnosing this for some time and I feel fairly confident that it is only the animation duration setting that triggers the sod. I have the other two settings set to 0 and duration set to 1 and no sod. But, it will not turn off that pesky crt animation.
who in here looked at logcat/dmesg when that happens?
do you have daydream ON? do you use an adblocker?
i've had one on 4.2.1, WITH AN ADBLOCKER installed. no adblocker, no bsod. full stock (rooted, unrooted, tried them both, doesn't matter), default settings (only enabled usb debugging)
just had another SOD / BSOD: I connected the charger and realized after 15 minutes, that the clock was unchanged (still 15 Min prior) - I tried to open an app and got a timeout. After I switch the screen off and on again I just saw a black screen (a little bit lighter than actually off) - but no homescreen anymore... damned.
I have tried searching for this problem but I must be using the wrong terms... so sorry in advance if I missed a post that addressed this issue.
My sprint S3 does this twitchy/glitching thing on every touchwhiz based jellybean rom (does not do it on TW ICS ROMS) I have tried. It basically makes it nearly impossible to do sliding animations, IE it can actually get stuck and start flashing halfway between screens, or when pulling down the top menu, however you can open new programs just fine if you are already on the right screen for them. Luckily it does not do this all the time, but when it happens it keeps doing for 10 minutes or so and its annoying as hell.
I figured this must be a rare issue even though it effects both my wifes phone and mine, since I have never read anything about it, however I just got a new replacement phone and it does the exact same thing, even on dead stock TW JB ROM.
Oddly enough I discovered last night that if I turn on my screen filter app it stops completely, but it starts right back up when I turn off screen filter..... any ideas how to fix this?
Try grabbing cache clear from the play store and set it to run every 12 hours. It helped my phone a good bit.
Sent from my SPH-L710 using xda premium
No one else ever has this issue?
joelespinoza said:
No one else ever has this issue?
Click to expand...
Click to collapse
I had it dude, but it was just on the CleanBean ROM, it was annoying as hell!
So I changed the ROM, Its weird that its happening on a Stock ROM, any suspicious app?
Hey guys. I moved up from a Verizon Note 2 to a T-Mobile Note 3 two weeks ago (and switched carriers obviously).
Since then, it has happened that the phone gets stuck and then reboots.
Three times it's happened while scrolling in the 9Gag app, once while in the Play Store and once as I was unlocking the phone using a pattern an e-mail came in and the vibration got stuck for a while and then rebooted.
I've also noticed that if I have WiFi on, Skype logs in fine, if I leave the house so I go on 4G and then come back to WiFi, Skype refuses to see a connection unless I turn off WiFi or reboot the phone.
Then yesterday the entire phone was in landscape mode even though I had auto-rotate enabled, and whether I turned it off and back on, it stayed on landscape mode until I rebooted the phone.
My wife also has a T-Mobile Note 3, bought at the same time. For her it's rebooted only once so far while using Google Maps.
I've had S3, Sprint Note 2, Verizon Note 2, and my wife has had S3 and S4. Now we both got these Note 3s and man, this is way too glitchy. On the Note 2 I went over 2 months once without rebooting the phone. This one has rebooted itself 5-6 times in 2 weeks!
We're updated to KitKat 4.4.2 (OTA) and not rooted or modified in any way (yet). So I'm wondering if it's KitKat that is glitchy, since our phones before weren't on KitKat, or the Note 3s in general, or just my specific Note 3.
Would love any info on this. Thanks.
I would do a master reset. Worst case Odin stock rom. Avoid send in for refurbished one
Def don't root yet. Try and get phone stable first.
TWEAKED N3
If i'm going to wipe, I might as well root. I've rooted and modded all my devices to date. Just when I got to the Note 3 it seemed that things had become considerably harder than on the Note 2...so I chickened out.
EDIT: if you don't mind me doing the noob thing and just asking, what's the easiest way to get root? I don't particularly care about a customized rom, but definitely want system access to get rid of all this bloat and install my customized video ringtone program.
Max_Pain said:
If i'm going to wipe, I might as well root. I've rooted and modded all my devices to date. Just when I got to the Note 3 it seemed that things had become considerably harder than on the Note 2...so I chickened out.
Click to expand...
Click to collapse
It not harder it more steps and Odin is best. But if you have hardware issues on stock u need to know before root
TWEAKED N3
Yeah, doing it now. Going to go stock but rooted so I can have some control. Maybe later on i'll flash a custom rom when I have time to go through them and see which one suits my style.
Thanks.
I'd suggest doing a factory reset b4 anything, then if that dose not work, use odin and flash kit kat... then if ur issue persist, maybe contact samsung.
Sent from my SM-N900T using XDA Premium 4 mobile app
---------- Post added at 05:57 PM ---------- Previous post was at 05:56 PM ----------
Also one u have root, go to the play store and check out greenify. I swear by it. C:
Sent from my SM-N900T using XDA Premium 4 mobile app
I'm already rooted on stock deodex. Let's see how it goes.
What's Greenify for?
Max_Pain said:
I'm already rooted on stock deodex. Let's see how it goes.
What's Greenify for?
Click to expand...
Click to collapse
Hibernating battery hogging apps and their associated services when they aren't being used.
Sent from my SM-N900T using Tapatalk
Max_Pain said:
I'm already rooted on stock deodex. Let's see how it goes.
What's Greenify for?
Click to expand...
Click to collapse
I be honest I don't use it and this kk really doesn't drain the battery like job did stock
TWEAKED N3
I haven't noticed any sort of glitches since I've had my N3. Even after putting the jedi ROM on it seems fine. As far as the battery goes, I know there are alot of complaints that kk has killed alot of the life out of it. I haven't noticed a difference in battery life either. It holds a charge all day and some. And greenify is to stop or freeze certain apps that run constantly in the background that could drain the battery. I personally didn't really like the app nor did I need it.
Sent from my SM-N900T using Tapatalk
Well, I went on a stock deodexed rom and got on lean kernel for a while... but it's still doing the stuck-and-reboot thing. It's always related to the touch screen, so i'm either scrolling or clicking to open an app or settings within an app. The phone gets momentarily stuck, then full reboot.
How long do I have to get it exchanged in store? I wonder if i'm within that time frame. It's definitely not normal and getting very annoying.
If i'm outside the time to get exchanged in store, what's my next best option?
I have to say that this experience with the Note III has been nothing short of disappointing and nothing like the two Note IIs I had before (different carriers for each, neither broke or gave any problems).
Here's an update for anyone who finds this and is in the same boat.
I had two issues: 1) the power button became so recessed that it's a hassle to turn on/off the screen, 2) the phone kept turning on and off, by the end almost constantly, without any obvious pattern beyond it getting stuck after me touching the screen (i.e. never just up and turned off while being idle).
Because of the recessed power button, T-Mobile shipped me a replacement phone. Should arrive tomorrow.
I still tried troubleshooting the rebooting issue. I think it came down to one or a couple of the following:
1 - Go Weather EX
2 - Freeza's CRT mod
3 - flashable 1% battery mod
4 - bootanimation.zip support flashable script
5 - something in the Deodexed version of the stock KitKat rom
In prepping to take the phone to T-Mobile, I did the return to stock thing with Odin, putting back stock kitkat odex non-rooted rom. The entire afternoon I got not a single reboot. Since I came back home with the phone, I restored a backup I had made before doing the Odin stuff. Back to rebooting.
So I thought, let's go back to the stock experience like I had earlier, and restore my apps through the play store and manually hunt it down.
Now i'm running the stock odexed kitkat rom, rooted, with lean kernel, with a whole bunch of stock apps frozen, and virtually all my apps and not a problem. I avoided 2-4 since those mess with the framework and I thought it could have something to do with it. I removed Go Weather EX because I experienced a reboot once while setting it up as a live wallpaper.
When the new phone arrives tomorrow I'll try to duplicate my current setup and hopefully won't have any more rebooting issues. I hope this helps anyone experiencing the same thing. I know it's kinda convoluted and not very concise, but then again this experience has been nothing short of annoying and confusing.