Everytime I flip my phone over the screen turns off after a couple of seconds. Really annoying in games and videos-- are there any possible fixes for this?
johnjeandoe said:
Everytime I flip my phone over the screen turns off after a couple of seconds. Really annoying in games and videos-- are there any possible fixes for this?
Click to expand...
Click to collapse
Maybe you have "Flip to Shhh" turned on (settings\system\gestures) which I think also turns off the screen. I had it on for a while and noticed this.
Frankenscript said:
Maybe you have "Flip to Shhh" turned on (settings\system\gestures) which I think also turns off the screen. I had it on for a while and noticed this.
Click to expand...
Click to collapse
Thanks for the response!
I just realized the actual issue, uninstalling digital wellbeing from ADB caused my "flip to shh" gesture to go away, and disabling usage access just causes the same problem of turning the screen off again. My only solution is to keep digital wellbeing untouched.
Related
Hello everybody.
I have a rooted 4.0.4 XXLFB Galaxy S3 and have noticed a problem.
Whenever I'm on a call using my blueooth headset, the screen turns on once every 30 seconds, give or take.
It's a problem because if I have the phone in my pocket, sometimes I mute the call, other times I turn off the headset...
Does anybody know how to solve this?
Thanks in advance.
Posting to add a "me too" to the list. Trying a ton of different things, almost to the point of clean device.
Hit the button and the screen turns off, about 2-5 seconds later, screen turns back on. Does not matter what I do. Seems to do it with speakerphone option too. If neither Bluetooth nor speakerphone are used, and you put the phone to your ear, backlight stays off. Otherwise, it automatically turns back on by itself. Tried with wifi on/off, speaker with bt on/off, different headsets, etc. My Wife's does not have this issue, so I gotta look into what is different. There has gotta be a setting or app installed that is doing this. I've even tried apps such as screebl and others. Some even had a thing to say lock it off till press button, and it still comes back on after 2-5 seconds. I've muted and hung up on many people when the phone was in my pocket because of this issue.
I've not used a BT headset but i'm thinking that maybe because the phone isn't against your head the screen comes on. possibly to give you information about the caller.
I'm not saying you should put the phone to your head even though your using bluetooth either.
thanks, but, don't help, tried that too. Had entire top half of phone covered during most tests. Screen does not turn off unless I press button, then comes back on automatically after 2-5 seconds. I did find one app today that seemed to work, but not sure if it works too well "Smart Screen Off".
Sounds silly but have you tried locking the handset?
That's what I meant by pressing the button. Button on right side that if I am not on a call, turns off screen and locks it.
Ok - narrowed it down a ton. If I leave the in-call status screen up, the screen turns back on after being turned off via power button. If I hit home or have any other screen active, it remains off. So dialer related, but I can deal with an extra button press.
visegrip72 said:
Ok - narrowed it down a ton. If I leave the in-call status screen up, the screen turns back on after being turned off via power button. If I hit home or have any other screen active, it remains off. So dialer related, but I can deal with an extra button press.
Click to expand...
Click to collapse
agree with the above. if you leave call status up while connected via BT headset, screen remains active (comes in and out). if you exit active call status (ie press home) then the screen timeout works. if you are talking on the phone without headset, no problem.
so yes, that's the prob. any solid fix yet?
please and thanks....
visegrip72 said:
Ok - narrowed it down a ton. If I leave the in-call status screen up, the screen turns back on after being turned off via power button. If I hit home or have any other screen active, it remains off. So dialer related, but I can deal with an extra button press.
Click to expand...
Click to collapse
Thanks a lot, visegrip. It was really frustating having to redial every other call because i hang up without noticing.
Any solution to this problem? Hitting a home button and locking the phone is not an option when I keep my phone in a leather holster on my belt. That's a main reason for having bluetooth as hands free.
Problem solved by using Tasker. If anyone need APK patch file to fix a problem, let me know and I'll post it here
Almazick said:
Problem solved by using Tasker. If anyone need APK patch file to fix a problem, let me know and I'll post it here
Click to expand...
Click to collapse
Almazick,
It would be great if you can send me the fix!
ital1981 said:
Almazick,
It would be great if you can send me the fix!
Click to expand...
Click to collapse
Here is the fix for a screen that I created. Let me know if it works or not for you.
http://www.mediafire.com/download.php?1ikj7d4wnjs9hx5
Almazick said:
Problem solved by using Tasker. If anyone need APK patch file to fix a problem, let me know and I'll post it here
Click to expand...
Click to collapse
You know, I use tasker and have been trying to figure this out for a while. I've also been trying Secure settings and Locale Using multiple settings and plug-ins. I have not been able to create anything yet that seems completely reliable.
Not trying to be rude or anything, but I am and always have been a little leary of installing APK files unless I know the source. However, if you would be so kind to post the contexts and tasks so that I may enter them myself manually, it would be greatly appreciated. Thank you in advance.
Inane65 said:
You know, I use tasker and have been trying to figure this out for a while. I've also been trying Secure settings and Locale Using multiple settings and plug-ins. I have not been able to create anything yet that seems completely reliable.
Not trying to be rude or anything, but I am and always have been a little leary of installing APK files unless I know the source. However, if you would be so kind to post the contexts and tasks so that I may enter them myself manually, it would be greatly appreciated. Thank you in advance.
Click to expand...
Click to collapse
Well, It's pretty easy.
Profile -> Phone Offhook
Task:
Wait 20 seconds
App-> Go Home
Display -> System Lock
In case if you'll have any problems just use my apk file which is exactly the same.
Good news! I just took the Jelly Bean update from sprint & this problem is FIXED!
I tried calling and turned off the screen and it stayed off!
I also called and didn't touch the screen and after the timeout, it turned itself off!
Hmmmmm... OK. Thank you. I'll have to try that and see how it works. I was looking, hoping and working on trying to get something that would keep the screen off. Dialing, talking and ending the call. I've got something that seems to work for the most part, (I still get quick flashes, which is fine) but still have some more work to do on it.
Sent from my ADR6425LVW using xda premium
visegrip72 said:
Good news! I just took the Jelly Bean update from sprint & this problem is FIXED!
I tried calling and turned off the screen and it stayed off!
I also called and didn't touch the screen and after the timeout, it turned itself off!
Click to expand...
Click to collapse
It's not fixed. I'm getting crazy about this master bug.
After my phone is running for awhile the screen won't time out, a reboot will fix it but after some time the screen won't timeout again. Also if Quick glance is activated, while the issue is present, the screen will turn on, start to dim and then the lock screen will show and stay until I shut it down. Maybe an app is running in the background and keeping it from shutting down? This is when the phone is not charging so it's not the Stay awake setting. I've also turned various settings on and off as well as changing the screen timeout, which is now set to 15 secs, and the problem still persists.
Anyone with this issue?
I've seen some (Issue 37974) with the GS3 posting about the same issue but never saw a resolution.
Any help or insight would be appreciated.
I've noticed this but it usually was an app that kept it running.
From the Homescreen, try holding down the Home "Verzion" button for a few seconds. Click "Remove All" and then see if it times out. If that doesn't work, try clicking "Task Manager" instead and closing all Active Applications.
If either of these do work, then when you notice it again, be more selective in which apps you close until you find the offending app. I have a few Sound Engineering apps that use the microphone and one of them forces my screen to stay on. I'm assuming to access the mic hardware. It seems to run in the background even when I "close" the app.
I've done the remove all and nada but I'm adsuming it is and app too...
Thanks for the reply...
It must be Stay Awake in developer options that is causing this bug. As stated a reboot fixes the issue temporarily, after the reboot the Stay Awake option gets turned off on its own, If I turn it on again the issue appears again shortly after. So somehow the Stay Awake option must be getting messed up and keeping the screen on even when not charging.
My workaround is turn off Stay Awake and Use Tasker to keep the phone awake while charging. Not what I'd like, I'd prefer the system work correctly, but it works for now.
Thanks
first off are you using a different keyboard other then the Samsung one ?
i had this happen to me using Swift.
just reboot your device and you should be golden.
Dont know why the keyboard would do this to the phone but thats what it was and all i did was reboot and Timeout works fine...
thenuke1 said:
first off are you using a different keyboard other then the Samsung one ?
i had this happen to me using Swift.
just reboot your device and you should be golden.
Dont know why the keyboard would do this to the phone but thats what it was and all i did was reboot and Timeout works fine...
Click to expand...
Click to collapse
Don't think the keyboard is a major issue with this. I've had this issue both when using swift and just the SS keyboard. I am more inclined to think like the other poster said that it has to deal with SmartStay. I haven't tried turning it off then rebooting, going to see if that works now. It sucks because toggling SmartStay is really useful, but i'm concerned with burn-in and especially with a battery that lasts 10hrs+, that could be an issue.
kimdoocheol said:
Don't think the keyboard is a major issue with this. I've had this issue both when using swift and just the SS keyboard. I am more inclined to think like the other poster said that it has to deal with SmartStay. I haven't tried turning it off then rebooting, going to see if that works now. It sucks because toggling SmartStay is really useful, but i'm concerned with burn-in and especially with a battery that lasts 10hrs+, that could be an issue.
Click to expand...
Click to collapse
interesting...
just my 2 cents. When i switched to swift from samsung key i just rebooted and it corrected the issue. Im sure theres a permanent fix but works as a temp one imo
Hello,
the following problem appears when i try to unlock the phone after some hours: i can see my home screen, but the screen stays extremely dim. When i try to start an app (e.g. browser) the screen turns black. I can unlock it again, but the screen stays dim. after some unlocking the screen becomes normal (normal brightness) and also the apps are startable.
i am using autobrightness, the stock firmware, 4.1.1 (i9300xxdlih) power saver is not turned on.
thx, i hope you can help me solving this problem
fanbayer
Fanbayer said:
Hello,
the following problem appears when i try to unlock the phone after some hours: i can see my home screen, but the screen stays extremely dim. When i try to start an app (e.g. browser) the screen turns black. I can unlock it again, but the screen stays dim. after some unlocking the screen becomes normal (normal brightness) and also the apps are startable.
i am using autobrightness, the stock firmware, 4.1.1 (i9300xxdlih) power saver is not turned on.
thx, i hope you can help me solving this problem
fanbayer
Click to expand...
Click to collapse
i updated mobile phone to android versiopn 4.1.2. this morning. Unfortunately the problem still appears.
Maybe its a hardware defect?
Try to disable somehow light sensor and change settings to non auto brightness.
Sent from my GT-I9300 using xda app-developers app
d0hn said:
Try to disable somehow light sensor and change settings to non auto brightness.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
i disabled auto brightness and set the brightness to the highest level. But its still same: very dim and after a while a black screen; after a few times of unlocking, the display works normally
I have just seen the same issue on a friend's S3.
Anyone else? I feel like this is a very big issue that is still lurking in a lot of devices.
I tried it myself and I toggled the power button to turn the screen on and off.
It doesn't take long but sometimes when the screen turns back on, it's super dim and you can faintly see the lockscreen image.
You have to cycle the screen several more times to get it to the 'correct' brightness, and no it is NOT a brightness setting.
It's some hardware issue in the phone.
Sorry for the necrobump, but I only found this thread. I have this problem too since about a week back. It makes my phone useless at times. I first thought it was a software issue. I have an app (called Twilight) for dimming the screen more than normal settings and also toning it, for nightime use, and I thought that was the culprit first, but nope. I have flashed rom, recovery, wiped all caches I can think of. Still happens, just now I was in the middle of installing android revolution hd, and the screen ultradimmed on me so I can't finish the process
Thing is, a few months ago I managed to crack my screen by way of gravity and concrete. I let the samsung brand service centre in Stockholm repair it for me (it is out of warranty) and this issue with the dimming never happened before that. Then again, it didn't happen directly afterwards either... but still. So, I am thinking: either me dropping it caused more damages and this is because of that. Or the service center did a bad install of the new screen. Or, the replacement screen that was installed has a defect in itself. I am leaning a bit towards the third explanation... maybe different batches of screens?
Does anyone have any ideas? If I am to contact the service center and complain about their work I would like to be able to point towards a "known problem"...
8Fishes said:
I have just seen the same issue on a friend's S3.
Anyone else? I feel like this is a very big issue that is still lurking in a lot of devices.
I tried it myself and I toggled the power button to turn the screen on and off.
It doesn't take long but sometimes when the screen turns back on, it's super dim and you can faintly see the lockscreen image.
You have to cycle the screen several more times to get it to the 'correct' brightness, and no it is NOT a brightness setting.
It's some hardware issue in the phone.
Click to expand...
Click to collapse
Take it back, if it didn't happen before then the new screen is most likely.
It isn't a common problem
Yo,
I got a problem because on lock screen (screen off) when i get notification (sms or app notification or something) i have the sound but the screen is not turning on.
Also if i turn on screen then i don't have any notification shown on lock screen.
is this a bug or that's normal? i had some android phones before and they were cool but it's weird here
Paviano said:
Yo,
I got a problem because on lock screen (screen off) when i get notification (sms or app notification or something) i have the sound but the screen is not turning on.
Also if i turn on screen then i don't have any notification shown on lock screen.
is this a bug or that's normal? i had some android phones before and they were cool but it's weird here
Click to expand...
Click to collapse
Same problem in my wifes phone. Can anybody can help to solve this issue?
goldielv said:
Same problem in my wifes phone. Can anybody can help to solve this issue?
Click to expand...
Click to collapse
I get the same issue, but it's only when I lock the screen with the app open. if i'm on my homescreen everything is back to normal.
Anyone else experiencing this? Screen wakes up for no reason and stays on permanently till I turn off. I'm on bad boys from BTW, thanks.
centro714 said:
Anyone else experiencing this? Screen wakes up for no reason and stays on permanently till I turn off. I'm on bad boys from BTW, thanks.
Click to expand...
Click to collapse
Settings/ Display,gestures & buttons
uncheck Ambient Display
schmeggy929 said:
Settings/ Display,gestures & buttons
uncheck Ambient Display
Click to expand...
Click to collapse
This was unchecked. Hasn't been happening this past day, I'll keep an eye on it. Thanks for the tip though.