I have a sprint Samsung Galaxy S3, rooted...Int he past week or 2, whenever I am in an application (Chrome, Yahoo, GTalk, etc) The screen will sometimes randomly shut off. It just goes black, i can still touch and use whatever app I was in (I can hear the sounds of clicks, etc) and the buttons stay lit on the bottom. When I press the lock button it makes the lock noise. When I then unlock it, i get to the lock screen with no problems. If I unlock into whatever app I am running, the screen will almost immediately shut off again, or sometimes after a few seconds, or sometimes it waits until i touch the screen. BUT, if I unlock into a system app (messages, phone, homescreen, etc) the problem doesnt happen.
I have tried adjusting all the display settings for screen timeout, rebooting, battery out, killing services, etc and nothing seems to work.
Any ideas?
scottyd944 said:
I have a sprint Samsung Galaxy S3, rooted...Int he past week or 2, whenever I am in an application (Chrome, Yahoo, GTalk, etc) The screen will sometimes randomly shut off. It just goes black, i can still touch and use whatever app I was in (I can hear the sounds of clicks, etc) and the buttons stay lit on the bottom. When I press the lock button it makes the lock noise. When I then unlock it, i get to the lock screen with no problems. If I unlock into whatever app I am running, the screen will almost immediately shut off again, or sometimes after a few seconds, or sometimes it waits until i touch the screen. BUT, if I unlock into a system app (messages, phone, homescreen, etc) the problem doesnt happen.
I have tried adjusting all the display settings for screen timeout, rebooting, battery out, killing services, etc and nothing seems to work.
Any ideas?
Click to expand...
Click to collapse
are you on stock ROM? if not it may be a problem with your ROM
try a reset and flash ROM again or flash another ROM
Related
ok, some info, i'm coming from the captivate (SGS1), on that phone if you were in a full screen app, or the camera was active, the screen wouldn't turn off regardless of the time out setting.
on this phone i have the timeout on 30 seconds with the stay on mode enabled for when i'm looking at the screen, this works really well except the above doesn't work, when the camera is on or the app is full screen it still times out. this becomes REALLY annoying when doing things like google hangouts as it hangs up the call when the screen turns off.
am i missing a setting? how can i keep the screen on when the app is full screen (games, movies, etc)?
thanks
Hi all,
I'm not too sure if anyone else has ever experienced this but it is starting to annoy me.
When my screen dims after 1 minute and goes to the lock screen I'm able to press the 'home' button and the unlock screen appears but I'm not able to do anything.
Its almost as if my devices jams and I have to press buttons to get it to come back.
I've reinstalled my device and this doesn't happen.
This happens during a call when the screen dims when its near my ear and I take my phone away from my ear the screen doesn't come on and it jams
Please - your help will be greatly appreciated
just swipe unlock it ? or use smart stay
Aimara said:
just swipe unlock it ? or use smart stay
Click to expand...
Click to collapse
I wish that was the issue.
My smartstay is on.
When the device's screen turns off the 2 issues happen:-
1. You press the home button to turn the screen on and the phone goes into the pattern lock screen - when i try do my pattern it doesn't pick anything up almost as if the screen has frozen and I have to wait 1 minute for the screen to go off and do the same process and hope it works.
2. I'm in a call and the screen is supposed to light up after removing it from my hear however it stays black. I have to lay the phone down, wait 1 minute and press the home button and hopefully the screen comes up and hopefully it isn't jammed
try this see if it works https://play.google.com/store/apps/details?id=com.mobint.locker
Hey Aimara,
It didn't work.. It almost seems like the phone jams i.e. there is no RAM left or something
Check your running apps, and could be too many apps running on background using up ram, try to freeze some unwanted apps
I have no issues unlocking my stock Sprint GS3 as you describe. Like some other have mentioned, maybe free up some internal RAM by moving some apps or data to SD storage?
I think it might be caused by CPU tuner and the governors? I noticed when my battery was low it would get stuck on the unlock screen.
Hopefully with my changes it works
Sent from my GT-I9300 using xda app-developers app
I've been experiencing for some time now some random freezes when trying to face-unlock the phone. When pushing the power button to wake the phone, it displays the unlock screen but the box in the screen where your face (or whatever the front camera catches) blacks out, while the rest of the screen is normal (I can see the clock, the notification bar and the emergency call), also the leds for back and menu light up. And the phone justs stays like that, all the leds lighted up and the screen on. The home button doesn't work and the power button only works if I hold it down (it powers down / restarts the phone).
This has happened to my phone from some time ago, its purely random and it always happens when I try to unlock the phone. I haven't had any issues while using the phone nor strange bootloops or sudden reboots. I'm currently on stock XXEMB5 with Speedmod Kernel k2-13 and some apps removed, mainly yahoo widgets and some Samsung apps (I think I just removed all the hubs: game hub, social hub, etc...).
I red the bad eMMs symptoms, but it doesn't seem to be the same. If I had to guess, I would say its something with the camera, but right now I don't know for sure... Anyone has any idea where could be the problem?
Favourite culprit would be a non-standard kernel, wipe the phone and return to fully stock to test.
Your collection of mods and custom changes to rom are probably unique, if it doesn't freeze when stock then add changes one at a time until it happens again.
[Q] Phone get stuck with screen locked. Rebooting starts an endless "startloop"
Hi, I have this Galaxy S3 i9300, with Wanam ROM and Boeffla-Kernel 2.12.
Sometimes, when I lock the screen, it just freezes in there. I'm unable to wake it up, and the LED keeps flashing the last notification.
Most of the time, I get notice of it when I receive a notification (it rings) and the phone cannot wake up. Calling and trying to trigger another notification does not wield any results.
The weird part is this: When I restart it, the OS starts as it should, but it "skips" the lockscreen (when I restart my phone, first thing I'm presented is the pattern lockscreen, all Android default), and it goes directly to the home screen. The touch screen is unresponsive (but it does vibrate when I press any of the two bottom buttons), but phone is still alive (few animations plays smoothly).
Then it restarts. The startup LED (fading blue to bright blue) doesn't turn off (normally it would turn off even before the lockscreen is presented).
Disabling the lockscreen wouldn't solve the problem, nor does starting on "safe mode". Same issue.
Booting into CWM and wiping data/cache folders solves it, but resets my phone. Restoring a backup (data folder only) also works.
Funny fact is that even with a fresh backup (which works), it might just hang up like before (although I didn't modify/install anything).
Logging files should give me some info, but I don't know how to retrieve them, let alone on this condition.
The only step I did so far to try to solve it was to disable a notification program (Logical, it seems to hang up when I receive a notification, and as a wipe to the data folder solves it, I presume it's an rogue app. But never, ever I had a problem with this app, but who knows if on an update, it's crashing my phone)
Does anyone have any information regarding to this? I've never seen something like that.
How do I recover my logfiles during an emergency?
-----------
Had another lock-up. No notifications received and the notification app was disabled. How do I get the log file?
I have a Xiaomi Redmi Note 9S which has the following behaviour: it works normally until the moment it goes under the sun, then (apparently only) the backlight of the screen is turned off and never turns on again until I restart the smartphone, where it works normally until the very moment it "detects" a bright light like under the sun, then the screen goes black. When this happens, sometimes you can still see the shape of what was on screen, but most times it only goes totally black.
When the screen is black, the telephone keeps working normally (music keeps being played, receives calls, vibration responses keep working, etc...(confirmed it using scrcpy and all is working normally)), only that the backlight is turned off and it keeps totally black. During the night, i.e. with artificial light, the telephone works normally (I was able to replicate the error using a strong flashlight above the telephone, the screen also went black the very moment I turned it on).
What I tried to resolve: restarted many times, disabled every auto brightness (also one that I think is a Xiaomi MIUI only, sunlight detector, something like this) settings that are in the configuration menu, restarted using vol up + power button. Factory reseted the smartphone. Disabled pocket mode before and after factory reset.
Any idea how to proceed? What is killing me is that it seem to be a software issue, like, why the screen don't turn on back after a while, but every time you restart it, or why the phone works all night long (i.e. there no strong light on it)?
How to capture the telephone log (logcat perhaps?) and be sure of what is the exact event that is disabling screen? Maybe I can manipulate it to prevent from happening, or to make screen goes back to normal after a while, as I work as a software developer.