Related
Hi all. Since updating to 2.3.5 my screen randomly lights up. The phone will be just sitting on the table, next to bed etc and the screen will light up for a few seconds and the turn off.
Not been on a stock ROM in a while, but I do remember hearing about this problem when the update rolled out. Just can’t remember if the problem was solved. Had a quick search and no joy. I'll keep looking. I have a theory though...
I had this problem once, and it was down to an app and the WiFi sleep policy. The WiFi sleep policy was set to ’15 minutes’ so the app was occasionally forcing a wake-lock to stop the WiFi from shutting off. This would also cause the screen to come on briefly. Could it be something like that? Sorry I can’t remember what the app was. Try leaving WiFi off and see if that stops it. If not successful try leaving auto-sync off. It will at least rule out or confirm something trying to force a wake-lock to sync something.
Edit: Does this do it only when on charge? Try opening up Car Dock Mode, and turning off 'Auto Launch'.
wnp_79 said:
Not been on a stock ROM in a while, but I do remember hearing about this problem when the update rolled out. Just can’t remember if the problem was solved. Had a quick search and no joy. I'll keep looking. I have a theory though...
I had this problem once, and it was down to an app and the WiFi sleep policy. The WiFi sleep policy was set to ’15 minutes’ so the app was occasionally forcing a wake-lock to stop the WiFi from shutting off. This would also cause the screen to come on briefly. Could it be something like that? Sorry I can’t remember what the app was. Try leaving WiFi off and see if that stops it. If not successful try leaving auto-sync off. It will at least rule out or confirm something trying to force a wake-lock to sync something.
Edit: Does this do it only when on charge? Try opening up Car Dock Mode, and turning off 'Auto Launch'.
Click to expand...
Click to collapse
thanx for the answer friend.i ll try it.
efialtis1971 said:
Hi all. Since updating to 2.3.5 my screen randomly lights up. The phone will be just sitting on the table, next to bed etc and the screen will light up for a few seconds and the turn off.
Click to expand...
Click to collapse
I noticed this too, but only on a Sense 3.5 ROM...Endymion (because, frankly, i didn't care much about any other Sense ROM to stay on it long enough to notice anything) ...but for me, the screen only lit up like a camera flash, just for a fraction of a second! not for a couple of seonds as you have experienced. Been on ICS betas, and RCs and currently on Reaper, but this issue never repeated itself. So far, this has happened to me only on a Sense 3.5 ROM...and my setup, sync frequency, installed apps hardly ever varies from ROM to ROM...I'm pretty consistent about how i like to use my phone.
And frankly, even when this was happening, i didn't bother much because it wasn't affecting performance or battery life... Sense is quirky, to say the least, but i've learnt to tolerate it like you would a sexy girlfriend. If it's sexy enough, it can get away with anything!!
I had this issue on the stock 2.3.3 ROM.
-------------------------------
Sent from my HTC Desire S
I can confirm that issue, like enigmaamit described it. I'm on endy 3.4. Weird...
Sent from my HTC Desire S using XDA App
I had the same issue but just one time few minutes after i pluged my phone .
Same here with MIUI... Just for a 1/10 of a second...
...via Tapatalk
I get this on ICS (virtuos quattro) when screen is off and charging, like half a second on and off again...
i've had this issue with pretty much every ROM, actually had it since i've had the phone. The phone lights up for a quick second. Enough for you to realise when your eyes are closed. i don't pay much attention to it anymore. But i don't think mine lasts seconds like yours. Mine was just a blank screen flashing
dan-fish said:
i've had this issue with pretty much every ROM, actually had it since i've had the phone. The phone lights up for a quick second. Enough for you to realise when your eyes are closed. i don't pay much attention to it anymore. But i don't think mine lasts seconds like yours. Mine was just a blank screen flashing
Click to expand...
Click to collapse
Hmm I think I'm only one but I gess not. It flash for like 0,1-0.2 sec. Just a little bit and I have seen it only in night when room is dark but I'd you don't motivated hardline to see. Flash is low light with blank screen
Sent from my HTC Desire S using xda premium
Can anyone help? While I'm talking, my screen is on. Sometimes if I moved the phone around my face, it turns off, but then it comes back on. Obviously it's draining my battery and I keep pressing mute etc with my face. Thanks in advance!!
See this thread
http://forum.xda-developers.com/showthread.php?t=951858
Sent from my nipple running windows 95 NT.
I saw this, but requires CM7, I'm running stock, rooted....
Hmmmmmm. I'm spent dude. Good luck.
Sent from my nipple running windows 95 NT.
bytemare said:
Can anyone help? While I'm talking, my screen is on. Sometimes if I moved the phone around my face, it turns off, but then it comes back on. Obviously it's draining my battery and I keep pressing mute etc with my face. Thanks in advance!!
Click to expand...
Click to collapse
Have you always had the issue, or did it just now appear? My first Inspire had a broken sensor, so the phone was replaced within 1 day of ownership.
Sent from my Inspire 4G using xda premium
It seems like it happened about 6 months ago. But, I installed leeDroid, then I installed that app to adjust the sensitivity, and it works! I can actually use my phone like a phone again!
Hi. I have been running pacman v22.0.1 for quite some time now and I could quite easily make and receive calls with no problems, the rom was fast and battery life was great. But quite recently, I received a call and answered it spoke but when it came to ending it, I couldn't get the screen to turn on and all that happened was the button backlights were flashing like mad! So I left it for a while and came back to the phone which had dropped from 84% battery to 41% and it was running very slow. Later when I tried making a call, I couldn't hear anything and I couldn't end the call which led to a charge of £5 which isn't too much money I'm not too fussed with that. But I switched to another rom then wiped everything and flashed pacman again but still had the same problem. Is there anybody who is facing the same problem or has a solution? I have tried on 4 different 4.2 roms now and have experienced the same problem with all.
Just uploaded a very, very long log cat if you are a dev or have knowledge of logs, please read!
Problem solved, it was my screen protector which was covering my proximity sensor and jelly beans behaviour with the proximity sensor caused it to stay off. When buying a screen protector always make sure it has a hole or gap of some sort for the proximity sensor. The bug in the log cat was something else which was fixed by a build.prop tweak.
My radio is 3831.19.00.110
ifti786 said:
I couldn't get the screen to turn on and all that happened was the button backlights were flashing like mad! So I left it for a while and came back to the phone which had dropped from 84% battery to 41% and it was running very slow. Later when I tried making a call, I couldn't hear anything and I couldn't end the call which led to a charge of £5 which isn't too much money I'm not too fussed with that.
Click to expand...
Click to collapse
Were you rapidly pressing the power button? Occasionally, I find my phone lags when turning the screen on, I press the power button once and the buttons light up, then I don't press it again and wait for the screen to turn on. If it is pressed a second time, it means "turn the screen off again", so you never see it turn on.
paulie-uk said:
Were you rapidly pressing the power button? Occasionally, I find my phone lags when turning the screen on, I press the power button once and the buttons light up, then I don't press it again and wait for the screen to turn on. If it is pressed a second time, it means "turn the screen off again", so you never see it turn on.
Click to expand...
Click to collapse
That could just be it: the reason for my problem is my impatience! Still need to check though...
No, that didn't fix it. I think it might have something to do with my proximity sensor because on vipersaga, it used to turn the screen on when I moved my phone from my ear but now it doesn't so I have to press the power button.
Also have the same problem on jelly bean fire
Sent from my HTC Desire S
Please help because I really want Jelly Bean 4.2 but at the current moment, it looks like my desire s is incapable of running it!
I flashed the ROM this morning and everything is well except of GPS (or is it just invisible?) and no weather on the cLock widget (btw any ideas here anybody?). I had issues of the screen keeping black with backlightes hardware buttons (and some others) with v21. But I never tried to use the phone for calling somebody with that, cause it was merely a stage facing the best ROM for me.
Did you do full wipe and Dalvik cache wipe? I found it is very useful to do so, cause it eliminates uncertainties the kind of "where does this come from?".
sanilii said:
I flashed the ROM this morning and everything is well except of GPS (or is it just invisible?) and no weather on the cLock widget (btw any ideas here anybody?). I had issues of the screen keeping black with backlightes hardware buttons (and some others) with v21. But I never tried to use the phone for calling somebody with that, cause it was merely a stage facing the best ROM for me.
Did you do full wipe and Dalvik cache wipe? I found it is very useful to do so, cause it eliminates uncertainties the kind of "where does this come from?".
Click to expand...
Click to collapse
Wipe all partitions except sd card AMD done this on pacman v22.0.1, JellyFireBean, JellyTime, flinny cm10.1 and AOKP redefined. I have just flashed a new radio and will check if that fixed it
Flashing a new radio did not fix the problem please somebody help!
ifti786 said:
Flashing a new radio did not fix the problem please somebody help!
Click to expand...
Click to collapse
I've got the same problem. My screen won't turn on after I move the phone away from my head after a call, altho I can turn it on with the powerbutton somehow. Happens on all JB ROMs for me aswell.
I tried Proximity Sensor Finder app from play store and it says 9cm when theres nothing infront of the sensor, then goes to 0cm when there is something, but doesn't go back to 9cm when the sensor is free again. It only goes back to 0cm when I restart the app.
I don't know whats the problem, but I think its software related.
Is the s2w turned on? If so, it could be the problem. BTW, the problem with black screen but capacitive button lights turned on, also have I. I see it, when I turn off the screen and try to turn it on after 5-10 seconds. But waiting a little helps.
Running Pacman 22.0.1
NVardan said:
Is the s2w turned on? If so, it could be the problem. BTW, the problem with black screen but capacitive button lights turned on, also have I. I see it, when I turn off the screen and try to turn it on after 5-10 seconds. But waiting a little helps.
Running Pacman 22.0.1
Click to expand...
Click to collapse
S2w is off, tried waiting too and that didn't help. I took a log cat of what happened and can upload it if wanted. My friend is taking a look at it for me to see whether there's a bug. It could have something to do with the build.prop.
ifti786 said:
S2w is off, tried waiting too and that didn't help. I took a log cat of what happened and can upload it if wanted. My friend is taking a look at it for me to see whether there's a bug. It could have something to do with the build.prop.
Click to expand...
Click to collapse
Maybe you should upload the logcat in the PACman thread.
Ok will do that now
Sent from my HTC Desire S
NVardan said:
Maybe you should upload the logcat in the PACman thread.
Click to expand...
Click to collapse
The log cat is waaaaaaay too long, I've sent you a message, anybody else who wants the log cat, ill pm you.
ifti786 said:
The log cat is waaaaaaay too long, I've sent you a message, anybody else who wants the log cat, ill pm you.
Click to expand...
Click to collapse
Unfortunately I am NOT a developer so I can't help you.
You must copy-paste your logcat in a .txt file and upload it in the PACman thread.
Sent from my Desire S using Tapatalk 2
I'm having the same problem with JellyFireBean v2. I ended up leaving a few voicemails without knowing, and it cost me 10$ from abroad...
I installed an app that gives information about all the sensors (sensor kinetics). When I start the test it shows a distance of 9cm, then I put my hand over the phone and it shows 0 cm, but then I remove my hand and it stays at 0, exactly like when I make a call.
sarcome said:
I'm having the same problem with JellyFireBean v2. I ended up leaving a few voicemails without knowing, and it cost me 10$ from abroad...
I installed an app that gives information about all the sensors (sensor kinetics). When I start the test it shows a distance of 9cm, then I put my hand over the phone and it shows 0 cm, but then I remove my hand and it stays at 0, exactly like when I make a call.
Click to expand...
Click to collapse
Right, I've just had a look through the logcat and i've found a bug. I'm going to try some build.prop tweaks and see what the results are. I will let you know but please bear in mind that it might take some time as I am having some very important exams coming up so I'm going to be revising in most of my free time.
sarcome said:
I'm having the same problem with JellyFireBean v2. I ended up leaving a few voicemails without knowing, and it cost me 10$ from abroad...
I installed an app that gives information about all the sensors (sensor kinetics). When I start the test it shows a distance of 9cm, then I put my hand over the phone and it shows 0 cm, but then I remove my hand and it stays at 0, exactly like when I make a call.
Click to expand...
Click to collapse
Do you have a screen protector on your phone by any chance?
Hey people
Got my smart watch about 4 days ago and it was all good until tonight and now for some reason i can't see the clock anymore unless i press the power button :S i could have sworn it had a low light mode and the clock was visable ok but since tonight i can't see the time unless there's a light pointing straight at the watch. I hooked it upto the service centre thing and updated it through that but hasn't helped.
am I going mad here and just seeing things? :S
EDIT: i also noticed when i turn it off i get some weird colours appearing in the clockface some pinks/purples. i don't understand it was ok a couple of hours ago and it's been on my wrist the whole time :S
Did you try to reset the watch? Also our you have any custom clocks installed, remove them. As after reset, Sony smartwatch app will reinstall them on the watch, once the watch and the phone are connected.
On your watch, go to settings and tap reset watch.
Sent from my HTC One SV using Tapatalk
tried that chap loads of times and nothing tried re-installing firmware and nothing swell. no custom watchfaces installed either just the stock ones
Roxas598 said:
Hey people
Got my smart watch about 4 days ago and it was all good until tonight and now for some reason i can't see the clock anymore unless i press the power button :S i could have sworn it had a low light mode and the clock was visable ok but since tonight i can't see the time unless there's a light pointing straight at the watch. I hooked it upto the service centre thing and updated it through that but hasn't helped.
am I going mad here and just seeing things? :S
EDIT: i also noticed when i turn it off i get some weird colours appearing in the clockface some pinks/purples. i don't understand it was ok a couple of hours ago and it's been on my wrist the whole time :S
Click to expand...
Click to collapse
Just to make it clear, you are not talking about the low power mode right? No backlight, but can be still seen by people in ambient light??? Maybe you should take a picture of the watch so we can clearly see what is going on.
At night my sw2 turns of the screen completely. But when I MOVE the watch it turns on the clock on the display. I think it has an accelerometer that turns off the screen when no movement is detected.
Sent from my GT-N5100 using Tapatalk
severoprisan said:
At night my sw2 turns of the screen completely. But when I MOVE the watch it turns on the clock on the display. I think it has an accelerometer that turns off the screen when no movement is detected.
Sent from my GT-N5100 using Tapatalk
Click to expand...
Click to collapse
The same for me. I think that isn't a bug, but accelerometer
Inviato dal mio LG-D802 utilizzando Tapatalk
It is normal.
It is a feature to save battery when it isn't worn.
I am more curious as to the "watch (display) turns on from moving it". Does the SW2 have an accelerometer? My watch display doesn't kick on when I move it. Or was this a feature of the earlier SmartWatches?
Nomad1600 said:
I am more curious as to the "watch (display) turns on from moving it". Does the SW2 have an accelerometer? My watch display doesn't kick on when I move it. Or was this a feature of the earlier SmartWatches?
Click to expand...
Click to collapse
I believe SW2 does have an accelerometer. Put your watch on a table, leave it untouched for while, screen completely turns off. Not even the low power watch mode is displayed. But once you move it, low power watch comes back on (without the backlight). I observed it many times when it was charging and when left at the bed side table.
But it is not utilized for backlight function. That is a missing feature people are asking for. But I don't really need it. Just like a regular watch, I press a button to turn the light on when I can't see it in the dark.
Sent from my HTC One SV using Tapatalk
thearif said:
I believe SW2 does have an accelerometer. Put your watch on a table, leave it untouched for while, screen completely turns off. Not even the low power watch mode is displayed. But once you move it, low power watch comes back on (without the backlight). I observed it many times when it was charging and when left at the bed side table.
But it is not utilized for backlight function. That is a missing feature people are asking for. But I don't really need it. Just like a regular watch, I press a button to turn the light on when I can't see it in the dark.
Sent from my HTC One SV using Tapatalk
Click to expand...
Click to collapse
Wow... I didn't even notice the screen going completely black after sitting for a while. I am still on watch honeymoon, and either the watch is on my wrist or turned off and on the dresser. But sure enough, it does go into a deeper "sleep" mode and wakes up when I pick it up. Nice!
I do see that having it wake to the backlit mode would be nice but it would seem to kill the battery since when worn it would be in more constant movement. Unless they tuned the accelerometer to only wake when a more significant motion happens.
Nomad1600 said:
Wow... I didn't even notice the screen going completely black after sitting for a while. I am still on watch honeymoon, and either the watch is on my wrist or turned off and on the dresser. But sure enough, it does go into a deeper "sleep" mode and wakes up when I pick it up. Nice!
I do see that having it wake to the backlit mode would be nice but it would seem to kill the battery since when worn it would be in more constant movement. Unless they tuned the accelerometer to only wake when a more significant motion happens.
Click to expand...
Click to collapse
Yeah the previous iteration of smartwatch from Sony did not have always on watchface and it was a necessity. And to see the time you had to turn on the display. One way was to double tap on the watch screen to wake it up. Another way was to light up the screen by lifting your arm and turning the watch towards you. But the second way never really worked reliably.
But I don't think SW2 needs that. As we already have always on watch with great readability even in places where there little light.
Sent from my HTC One SV using Tapatalk
thearif said:
Just to make it clear, you are not talking about the low power mode right? No backlight, but can be still seen by people in ambient light??? Maybe you should take a picture of the watch so we can clearly see what is going on.
Click to expand...
Click to collapse
Sorry for the delay! yeah seems my watch didn't have the low power mode and now it does it's just near impossible to see unless i have some light directly on the screen
Roxas598 said:
Sorry for the delay! basically sitting here in the dark i can't see the time on the display at all but i could when i first got it now I need to actually press the button to see the time :S dunno if it's just me thinking i could or not is the problem lol
Click to expand...
Click to collapse
So there is nothing on the screen not even the low power mode on the watch. I don't know what to tell you boss as you have already done a reset. Maybe one thing to check is to use SUS to reflash the firmware using your pc, if you haven't done it already.
Sent from my HTC One SV using Tapatalk
thearif said:
So there is nothing on the screen not even the low power mode on the watch. I don't know what to tell you boss as you have already done a reset. Maybe one thing to check is to use SUS to reflash the firmware using your pc, if you haven't done it already.
Sent from my HTC One SV using Tapatalk
Click to expand...
Click to collapse
sorry chap i updated my post there is something on the screen but it's impossible to see without some sort of light source on it makes it kinda annoying to use could have sworn it wasn't when i first got it but figured i'd ask anyway!
Roxas598 said:
sorry chap i updated my post there is something on the screen but it's impossible to see without some sort of light source on it makes it kinda annoying to use could have sworn it wasn't when i first got it but figured i'd ask anyway!
Click to expand...
Click to collapse
No problem. I never considered the low power hard to see. But I guess most of the time I am in well lit places
Sent from my HTC One SV using Tapatalk
Didn't see this posted here yet, but forgive me if I missed it.
Trying to find out if anyone has seen or heard of any acknowledgement from Google regarding this. My new Pixel 3 (Verizon; non XL) since day 1 has had an annoying issue with the screen flashing when ambient screen engages. I have my settings with alwayson set to off, and new notifications set to on. If the screen is asleep and I get a text or any notification, the ambient screen wakes and will initially make the entire screen flash white very quickly.
I do not get a flash of the screen in any other scenario when the phones on, it only seems to be when the screens totally asleep and the ambient screen wakes. I can unlock the phone or hit the power button to fully wake the phone to my home screen with no flashing. Its not every single time, but its very often. I do notice sometimes when it doesn't flash the whole screen, the time or text on the ambient display will be at full brightness when it first wakes for a split second and then will go to the dim text Im used to seeing.
Replaced the phone through Verizon. Got another brand new one with the same exact problem. This one even flashes on reboot occasionally just before the white "Google" screen pops up. Google had me send them a bug report this time and are supposed to be having their dev team look at it.
WHY.
Mine did it once
Sent from my Pixel 3 using Tapatalk
I've also now noticed mine will flash in Instagram when I "like" something lol. Just the picture flashes within the app itself in that case, not the whole screen. Such a weird thing, that may have something to do with the app on the new pixel? I don't even know anymore.
I just saw the white flash. It was only for a few ms but it looked like a full brightness white flash on the whole screen. I had just set my phone down and I think the AOD was coming on.
Weird.
Yeah I have a feeling this is happening on way more devices than we're reading about. I hope it's addressed. Sometimes my notification audio cuts out real quick too. Hoping it's just all memory related.
I have this weird kind of screen flickering on my device as soon as I use the fingerprint area to turn the phone on. It is very faint and fast but its like static lines for half a second when the screen comes on??
Archangel said:
I have this weird kind of screen flickering on my device as soon as I use the fingerprint area to turn the phone on. It is very faint and fast but its like static lines for half a second when the screen comes on??
Click to expand...
Click to collapse
Strange, I haven't had any issues like that using the fingerprint reader or just hitting the power button. Mine are all directly related to ambient screen waking.
My Pixel 3 is doing the same thing when I unlock it. Flashes like taking a selfie... I have even looked for the selfie to no avail.
It does not do this regularly, very random.
edster00 said:
My Pixel 3 is doing the same thing when I unlock it. Flashes like taking a selfie... I have even looked for the selfie to no avail.
It does not do this regularly, very random.
Click to expand...
Click to collapse
Same here. Sometimes when I tap the screen to wake it up, it flashes. Just did it a minute ago before I wrote this.
Sent from my Pixel 3 using Tapatalk
I just charged the Pixel face down; during the charge I picked it up to check the progress and I got the screen flash ~2X out of 10.
edster00 said:
I just charged the Pixel face down; during the charge I picked it up to check the progress and I got the screen flash ~2X out of 10.
Click to expand...
Click to collapse
Report it to Google. I feel like it's something they're aware of (I hope) but support certainly isn't saying so if they are.
I saw a post on Android Police about bug trackers and read in some of the comments that people were having problem with screen flashing. Some of them said it was related to the always on display. Mine was flashing like white static lines. But it was only for half a second when you turn on the screen and it didnt happen every time, it was random. I turned off the AOD and it never happened again. Kinda sucks cause I like AOD. But that tells me it is a software problems and not hardware.
I turned off AOD too, for 1 day; the next day I turned AOD back on. I have not had a screen flash since (a few days now).
edster00 said:
I turned off AOD too, for 1 day; the next day I turned AOD back on. I have not had a screen flash since (a few days now).
Click to expand...
Click to collapse
Try rebooting. I bet it's still happening you just may not be noticing. I've had my AOD off for a while and as soon as I turn the new notifications option it comes back. Not every time but still often.
I'm having the same issue, doesn't happen all the time but I can reproduce it usually by unlocking the device, locking it then when ambient display comes on, unlock it and the screen flashes/flickers. I've only managed to do it with ambient screen set to always on.
I've RMA'd this morning so I'll report back when the new phone comes.
I hope you RMA's for other reasons too because it is likely that you will get a phone with the same flickering problem. I think it is a software issue esp since it goes away after we turn off AOD.
steslatt said:
I'm having the same issue, doesn't happen all the time but I can reproduce it usually by unlocking the device, locking it then when ambient display comes on, unlock it and the screen flashes/flickers. I've only managed to do it with ambient screen set to always on.
I've RMA'd this morning so I'll report back when the new phone comes.
Click to expand...
Click to collapse
Archangel said:
I hope you RMA's for other reasons too because it is likely that you will get a phone with the same flickering problem. I think it is a software issue esp since it goes away after we turn off AOD.
Click to expand...
Click to collapse
I just find it strange that people are having the flicker in different scenarios, like mine is only when ambient is set to always on but other people are having the issue when it's set to double tap etc. Anyway I guess I'll see when the new phone comes.
Sent from my Pixel 3 using Tapatalk
Yeah let us know please once you get the new phone. It seems like it is hit or miss with people so you might get lucky and avoid it.
steslatt said:
I just find it strange that people are having the flicker in different scenarios, like mine is only when ambient is set to always on but other people are having the issue when it's set to double tap etc. Anyway I guess I'll see when the new phone comes.
Sent from my Pixel 3 using Tapatalk
Click to expand...
Click to collapse
Quick update. My new phone arrived this morning and I've managed to get the screen to flash once so far where as my old one would do it 8 times out of 10. I feel like this is a poor display hardware problem rather than software.
I believe or rather am hoping that because it only happens when you turn on AOD that it is a software issue and not a hardware one. The only way something will be done is enough people complain on a bug tracker.
steslatt said:
Quick update. My new phone arrived this morning and I've managed to get the screen to flash once so far where as my old one would do it 8 times out of 10. I feel like this is a poor display hardware problem rather than software.
Click to expand...
Click to collapse