So, I just exchanged my s6edge for a new unit today because the old one had an issue with tone unevenness and extreme yellowing in certain areas on the screen. Anyway, on my new one when I just click the power button to check the time or notification's, not unlocking the phone or anything like that, the display just sits powered on on the locksreen. doesn't time out or turn off. I have to do it manually. Idk why this is happening all of a sudden as it never happened on the old one or any other phone I've owned for that matter.
Any ideas?
I have exactly same problem. But it is software issue and lock screen timeout depends on normal display timeout. I dont know why it is done like this. Ussualy is lock screen timeout about 8 seconds and it is not depend on normal display timeout.
Related
Ok, so after doing all my searching and what not, it seems that for whatever reason the time it takes for the lock screen to time out is tied to the regular screen timeout.
What I mean by this, is when you first hit the sleep/wake button and its on the lock screen, but you don't unlock it, the time it takes for that screen to go to sleep is the same as if you had unlocked it and not used it.
For me at least, this is a major battery life issue. I like to leave the screen timeout at minimum at 5 minutes, because I use my phone's LCD as a flashlight quite often (LGP500 doesn't have a camera flash), and read websites fairly often. Also, I tend to keep my phone in my pocket (who doesn't?), so when walking or moving it's very likely one of the hardware buttons (sleep/wake, home etc.) will be accidentally pressed inside my pocket at least once every short while, basically keeping the screen on permanently.
I'd like to know if anyone has any ideas on how to change this.
Just as a side note, I realize it's possible for rogue apps to keep the screen from timing out, but I've made sure that its not the case here - when the timeout is changed to 15 seconds, the screen turns off at the correct interval.
Anyone have any ideas?
I got my AT&T Galaxy S3 on Saturday and have seen this issue a couple of times now. The issue is that sometimes the screen will not lock after the time I have set (30 seconds). Also, the touch key lights stay on forever until I lock the phone. When I unlock it the touch key lights stay on and the screen doesn't lock. The only way I've found to fix it is a reboot. I first noticed this when I received a text. I use goSMS and have it set to turn the screen on for 10 seconds when a text is received.
Has anyone else noticed this issue or know how to resolve it?
I'm also having the wifi disconnect/reconnect issue and the issue with the cell standby using a lot of battery.
The phone is rooted with the stock ROM.
geiswiz said:
I got my AT&T Galaxy S3 on Saturday and have seen this issue a couple of times now. The issue is that sometimes the screen will not lock after the time I have set (30 seconds). Also, the touch key lights stay on forever until I lock the phone. When I unlock it the touch key lights stay on and the screen doesn't lock. The only way I've found to fix it is a reboot. I first noticed this when I received a text. I use goSMS and have it set to turn the screen on for 10 seconds when a text is received.
Has anyone else noticed this issue or know how to resolve it?
I'm also having the wifi disconnect/reconnect issue and the issue with the cell standby using a lot of battery.
The phone is rooted with the stock ROM.
Click to expand...
Click to collapse
Yep, I am having the same issue.
http://forum.xda-developers.com/showthread.php?t=1761027
kirbo20 said:
Yep, I am having the same issue.
http://forum.xda-developers.com/showthread.php?t=1761027
Click to expand...
Click to collapse
Hmm, I did turn off the wifi power save mode using *#0011* because of wifi disconnect issues. I went in and turned it back on and rebooted the phone. I'll see if I still get the screen lock issue.
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
Hi everyone !
I'm new here (and not a native english speaker, so apologies in advance for any grammar mistakes)
Before making this thread, I looked for info here, but I'm not sure for what to search.
I'll try to explain my problem here.
I bought a Galaxy SIII from my provider 3 weeks ago and everything looked fine, till last week.
Some times to time, with no apparent reason or cause, while my phone is on sleep mode, on my desk, or in my pocket, playing music, I have the following problem: when I push the on/off button to wake up my phone, my screen is turning on, taking me to the lock screen.
But, my screen brightness is very low, like set to the minimum.
And when I draw my unlocking pattern, screen goes black.
Bottom buttons are lit and my phone seems to be OK, I can feel haptic feedbacks.
But the screen is black.
If I push the on/off button again, screen stays black and bottom buttons are not lit anymore, as a usual Sleep Mode.
If I push on/off again (depending on how much I wait between 2 on/off):
- My phone awakes from Sleep and takes me again to the unlock screen, brightness still very low. And after the unlocking pattern traced, black screen again
- If I didn't wait enought after putting it into sleep mode, in this case, I don't have to redraw the unlocking pattern. I'm back to my home screen...
for 1/4 of a second, stilll with brightness at the minimum. And screen goes black.
And after a serie on onoffonoff, boom, my screen is back to full and normal brightness and everything is OK.
At the beginning, my phone did that once in a while. I thought at the time ti was after pushing the on/off button while using a CPU/RAM hungry app, my phone struggling to recover....
But now, it's totally random.
Depending on .... I don't know what, I have to do the onoffonoff thing 2, 5, 10, 50 times in a row so my phone can recover from is half comatose.
Yesterday, I could not use my phone for half an hour ...
and if someone calls me, I hear the ringtone, but screen stays black.
I can answer the call (but not knowing who's calling) by sliding on the part of the screen where the slider normally is.
Funny thing is about removing the battery. It doesn't solve my problem.
When I do so, my phone boots, I see the "Samsung Galaxy SIII" boot screen, on low brightness (whih is not normal ...)
After that, I normally have another boot screen with my provider's logo and tone. But screen goes black again (but I still here the tone)
Then I realized it started to happen when my phone proposed me a Samsung update.
I tried to reset my phone to factory settings but it didn't work, the update was still here.
For a while I thought my problem was solved, because my phone behaved normally for 3 or 4 hours, without problem.
But it came back.
I found on the internet several "almost-same-problems" without proposed solutions.
Like checking if the proximity sensor was blocked by a protective transparent plastic sheet, or a case.
I tried to to remove mine.
Didn't work.
Some people said it was linked to their phone trying to acquire a wifi network.
My wifi on or off, withiin or without the range of a wifi router didn't work ...
I tried to note things down about what I did, when, how, app launched before the problem appears.
I checked battery info (temp, voltage, etc).
No pattern emerged.
So.
Hs anyone of you enountered the same problem ?
Do you have ideas, solutions I can use ?
Or maybe a voodoo prayer ?
I could sent it back to my provider which will bounce it back to Samsung. But it will take ages (3 to 4 weeks ...) :'(
Thanks in advance !
do a factory reset, go completely stock
if that doesn't help, send it in
Glebun said:
do a factory reset, go completely stock
if that doesn't help, send it in
Click to expand...
Click to collapse
That's what I did.
I tried by going into the Parameters menu, and reseting.
I tried by booting my phone with Vol+ / Home / Power buttons to access a console mode and do a wipe data/reset.
The problem is that my phone got an update like one week ago from a 4.?.? to 4.1.2.
And even with a reset, my phone reboot with the 4.1.2 version, which seems to cause this problem.
Or maybe not, but I can't be sure.
As I said, after a factory reset I did yesterday, everything went well for 3 or 4 hours and the problem reappeared.
send it to the service
So say for some odd reason you have your screen time out on 5 minutes, phones on silent you get a text. It wakes your phone up for 5 minutes. I have a rough idea of separating the screen time out selection into two. A screen time out set for when the end user unlocks his or her phone and a wake lock induced screen time out. Now I know there's anti wake lock apps but the idea is as I stated a set screen time out for a user induced wake lock and app induced wake lock. This idea popped into my head randomly as I don't leave smart stay on so I max screen time out to watch video's and sometimes luck my phone on silent for getting to change the screen time out back. Anyone have any insights about this.