stock LP7 ICS here. Every time I receive a SMS the screen wakes. Not normally a problem, but recently have found the lockscreen is staying on whilst in my pocket. Must be the fabric of my suit, so its killing my battery.
A friend of mine who is also on LP7 swears his S2 doesn't wake when receiving an SMS. Am i missing a setting somewhere? I'm sure this wasn't a problem on GB.
I am running stock Messaging app.
My S2 wakes when I receive an SMS. It's done that since GB and continues to do that in ICS
Screen time-out?
It could also be your screen time-out being set too high. Try setting the timeout to a lower value and see how that goes
Yup..it will awake around 15 secs
Sent from my GT-I9100 using Tapatalk 2
The screen wakes on Samsung ROMs, although I've noticed it doesn't on the AOKP ROMs I've been using. Perhaps your friend is using one of them?
As for the issue with the screen staying on, check screen timeout (although I'm sure this is separate for screen and lock screen). Or else try a different pocket
Yes your right re screen time out, it is separate for screen and lock screen. But the time-out isn't the problem. Either I have electrically charged legs or the screen sensitivity has increased in ICS. The phone is waking when SMS arrives, then the screen is staying on because it senses a touch through the fabric against my leg. Small movements (ie walking) keep the screen on without unlocking the phone. Obviously easily sorted by keeping phone in a jacket or glass facing outwards rather than against leg.
Just wondered if there was a way to disable the screen on function. After doing a bit of research it looks like GO SMS has the option to disable screen waking.
flashflash said:
After doing a bit of research it looks like GO SMS has the option to disable screen waking.
Click to expand...
Click to collapse
Go SMS can indeed do that- I use it and the screen does stays off if the option is selected
Sent from my GT-I9100 using xda premium
Related
I am a new android owner. When I make a phone call the proximity sensor turns the screen off... great, no accidental screen pressing. However, when I finish the phone call or take the phone away from my ear... I get the lock screen. Why? Why doesn't the screen just go back on to whatever screen was on before the phone call... like the dial pad.
I find this annoying. To hang up a phone call, I have to unlock the screen first.
What phone are you using? Software version etc and are you rooted? This doesn't happen to me so it's not a general android issue.
Sent from my Galaxy Nexus
I have the Moto Droid X. Running CyanogenMod 7.1. Also using exDialer as a dialer replacement.
Does it happen with the stock dialer? If not that's your answer
Sent from my Galaxy Nexus
RTContent said:
Does it happen with the stock dialer? If not that's your answer
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Yep it happened with the stock dialer on ICS and it is happening with JB as well. I am really surprised it doesn't bother more people. What is most annoying is that, I initiated a new call and put my phone to my ear to only that the call did not even establish (e.g., due to network iss ue) and when I want to place the call again, it is already locked. It is definitely due to the proximity sensor, as the same thing doesn't happen if i never put the phone to my ear and just keep watching the screen to confirm that the call did get established (and started ringing).
njmsmith said:
I am a new android owner. When I make a phone call the proximity sensor turns the screen off... great, no accidental screen pressing. However, when I finish the phone call or take the phone away from my ear... I get the lock screen. Why? Why doesn't the screen just go back on to whatever screen was on before the phone call... like the dial pad.
I find this annoying. To hang up a phone call, I have to unlock the screen first.
Click to expand...
Click to collapse
If you are rooted, disable your Proximity Sensor in a call. To do so, add following line to /system/build.prop file:
Code:
gsm.proximity.enable=false
.
Plus, make sure to make screen timeout period long. You can use Widgetsoid app (or, other toggle apps) to make it infinite.
SachinShekhar said:
If you are rooted, disable your Proximity Sensor in a call. To do so, add following line to /system/build.prop file:
Code:
gsm.proximity.enable=false
.
Plus, make sure to make screen timeout period long. You can use Widgetsoid app (or, other toggle apps) to make it infinite.
Click to expand...
Click to collapse
I have display timeout set to 2 minutes, so that can't be the problem, as the whole experience when the call is not connected only takes 10 or 15 seconds to complete. However I have security setting to lock the screen in 5 seconds after the display goes to sleep. Perhaps that is somehow related, so I just increased it to 30 seconds, I will see if the problem goes away.
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
I'm currently using the latest version of clean rom. Lately I have noticed that sometimes when I grab my phone without waking it up, there is kind of a light that comes on towards the top of the screen and it displays missed calls and missed texts the light stays on for a few seconds then fades away by itself. What makes this wierd is I have not been able to force this to happen and sometimes it does it and sometimes it doesnt. This happens prior to me waking up the phone when the screen is black. I think it might have something to do with a motion sensor. Any ideas on what feature this is.
Sent from my SCH-I605 using xda app-developers app
kbauman said:
I'm currently using the latest version of clean rom. Lately I have noticed that sometimes when I grab my phone without waking it up, there is kind of a light that comes on towards the top of the screen and it displays missed calls and missed texts the light stays on for a few seconds then fades away by itself. What makes this wierd is I have not been able to force this to happen and sometimes it does it and sometimes it doesnt. This happens prior to me waking up the phone when the screen is black. I think it might have something to do with a motion sensor. Any ideas on what feature this is.
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
It's called QuickGlance and can be found under Settings --> Motion. The way to activate it is to reach for your phone while it lies flat, covering the sensors in the top-right corner, you can pull your hand back and it'll show up. Interesting thing, if you use an app that forces auto-rotation, such as rotation locker or what have you, you can get the QuickGlance screen to show up in landscape.
I got my Mate 20 last week and I have a nagging issue that I am trying to find a solution for. When I am in the car i have my Mate 20 in a cradle. When I make or receive a call the call screen appears, then about a minute later it will turn off (go black). When I touch the screen it will come back on. I have my screen timeout set to a minute so I understand why this may happen. However, the screen time out I don't think should do this when using the phone call app. Is there a way to keep the screen on during a call? I have looked at the settings and found nothing. I am coming from a Blackberry Priv running andriod and there was a setting the allowed to keep screen on during calls.
On my last 4 Android phones (Samsung) I had the same behavior...which I actually liked as it saves battery. There is no setting AFAIK to disable that on M20P, I mean besides extending the screen timeout.
You could use MacroDroid to set a couple of rules: one to increase screen timeout while a call is active and another to change it back when a call ends.
There are also some apps that are supposed to let you keep the screen on while a specified app is running (like Keep Screen) so don't know if that would work.
denaliman said:
I got my Mate 20 last week and I have a nagging issue that I am trying to find a solution for. When I am in the car i have my Mate 20 in a cradle. When I make or receive a call the call screen appears, then about a minute later it will turn off (go black). When I touch the screen it will come back on. I have my screen timeout set to a minute so I understand why this may happen. However, the screen time out I don't think should do this when using the phone call app. Is there a way to keep the screen on during a call? I have looked at the settings and found nothing. I am coming from a Blackberry Priv running andriod and there was a setting the allowed to keep screen on during calls.
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=com.openappinfo.keepscreenon
Sent from my [device_name] using XDA-Developers Legacy app
Been using my Pixel 6 for my daily driver since I received it after launch. Recently, I have had quite a bit of trouble with the phone screen waking in my pocket and calling random people or 911 (emergency services) or just filling the PIN unlock screen with random numbers. I believe the screen is interacting with the fabric of my clothing. I make sure to power off the screen before I put it in my pocket, and facing the screen outward instead of inward seems to make a bit of a difference. I have scoured the settings and can not find anything. The only other option I see is a full wallet type case that closes over the phone so there is no way anything can interact with the screen. This started happening with alarming frequency in April.
Am I missing something? Any suggestions on how to prevent this? Turning off wake from notifications?
Thanks in advance!
draexo said:
Been using my Pixel 6 for my daily driver since I received it after launch. Recently, I have had quite a bit of trouble with the phone screen waking in my pocket and calling random people or 911 (emergency services) or just filling the PIN unlock screen with random numbers. I believe the screen is interacting with the fabric of my clothing. I make sure to power off the screen before I put it in my pocket, and facing the screen outward instead of inward seems to make a bit of a difference. I have scoured the settings and can not find anything. The only other option I see is a full wallet type case that closes over the phone so there is no way anything can interact with the screen. This started happening with alarming frequency in April.
Am I missing something? Any suggestions on how to prevent this? Turning off wake from notifications?
Thanks in advance!
Click to expand...
Click to collapse
Sorry for not being able to add anything other than I too am experiencing this issue, exactly as described.
I think it could be the double tap to wake I wear jeans and don't have that problem but 8 am using a pixel 6 pro though
Same issue here.
Please use the feedback form in device settings -> about the phone to send the bug report to Google as well.
Thanks!
this never happened to me.
are you using screensaver? AOD? any kind of app which controls the screen on/off?