So on Monday I went out and got a shiny new Turbo. I'm loving it so far and hoping for root and or bootloader unlock eventually. This morning though something odd happened. For a period of about ten seconds my capacitive buttons quit working completely - no vibrate when I touched them, no nothing. The phone wasn't frozen or anything. Then they suddenly started working again. About five minutes later it did it again, but it hasn't done it since. Should I be worried? What should I do?
I'm having the exact same issue, seems to be random.
Ok I have the Moto Maxx and noticed that too... then I figured that in my case it happened because I was touching the screen with my palm while tying to reach for the capacitive buttons. The buttons stop working while you are touching the screen. Check if that is what is happening to you.
jfassad said:
Ok I have the Moto Maxx and noticed that too... then I figured that in my case it happened because I was touching the screen with my palm while tying to reach for the capacitive buttons. The buttons stop working while you are touching the screen. Check if that is what is happening to you.
Click to expand...
Click to collapse
I've even had it do that if there is any liquid on the screen...like maybe a few small drops of water after you just washed your hands or something like that.
Does the proximity sensor disable the buttons? Thinking that if the phone thinks it is near your face for a call, it might shut off the screen and buttons to prevent accidental presses.
Ekkoria said:
So on Monday I went out and got a shiny new Turbo. I'm loving it so far and hoping for root and or bootloader unlock eventually. This morning though something odd happened. For a period of about ten seconds my capacitive buttons quit working completely - no vibrate when I touched them, no nothing. The phone wasn't frozen or anything. Then they suddenly started working again. About five minutes later it did it again, but it hasn't done it since. Should I be worried? What should I do?
Click to expand...
Click to collapse
They will automatically dim and turn off when in a well lit area/room. If you are in a dark environment they will always be on.
Just hold the device under a lamp and watch buttons dim slowly off. Turn lamp off or go to a dark room and watch them illuminate back to life after 8-10 seconds.
Pretty standard, however, if they are going on and off constantly in the dark, than most likely a defective unit.
jfassad said:
Ok I have the Moto Maxx and noticed that too... then I figured that in my case it happened because I was touching the screen with my palm while tying to reach for the capacitive buttons. The buttons stop working while you are touching the screen. Check if that is what is happening to you.
Click to expand...
Click to collapse
I'm pretty sure this is what happened to me, after playing around with it I noticed my phone does the same thing. That's a load off my chest, I was a bit worried about it. thanks!
Screen pinning vs Long press for menu
Just a note, I recently discovered that if you have lollipop screen pinning enabled under the security settings and also the "Use long press for menu" setting enabled under display settings, they seem to conflict and cause all kinds of key lag with any of the capacitive keys. Must be because both utilize a long press of the recents/overview key. As long as you only enable one or the other it should be fine. Just thought I'd throw that out there.
I have had this problem too, it simply has to do with the fact that the screen is and capacitive keys are combined. You can use one or other, but not both. If you encounter this, just mess around on the screen for a few seconds and the keys should work again.
Clear cache. That usually fixed the problem for me.
Sent from my XT1254 using Tapatalk
Related
I thought the screen shuts off when you're in the middle of a call (proximity sensor?). On the iPhone, when you're in the middle of the call, it shuts the screen off when its by your face just so you don't hit anything like mute, etc...
Any way to get around this? Thanks
Legaleye3000 said:
I thought the screen shuts off when you're in the middle of a call (proximity sensor?). On the iPhone, when you're in the middle of the call, it shuts the screen off when its by your face just so you don't hit anything like mute, etc...
Any way to get around this? Thanks
Click to expand...
Click to collapse
Mine shuts off the screen when your face is close to it.
Settings -> Call Settings, do you have Keep screen awake checked?
I don't see that option. Settings, then call settings... I see voicemail, call forwarding... That's pretty much it. Running Stock 2.1
Mine has done this a couple times now,i'll be talking to someone and all of a sudden start hearing beeps as if hitting the numbers on the keypad. First time it happened I thought it was the person on the other end but it happened again last night and I looked at the phone after I got off the call and it had #2* or something like that in the dialer so something is definitely weird here.
bluehaze said:
Mine has done this a couple times now,i'll be talking to someone and all of a sudden start hearing beeps as if hitting the numbers on the keypad. First time it happened I thought it was the person on the other end but it happened again last night and I looked at the phone after I got off the call and it had #2* or something like that in the dialer so something is definitely weird here.
Click to expand...
Click to collapse
are you using a screen protector/skin/case ... anything?
mine has never given a problem.
so far.
Maybe you have a really skinny head that's not passing the sensor?
nmesisca said:
are you using a screen protector/skin/case ... anything?
mine has never given a problem.
so far.
Click to expand...
Click to collapse
Nope, I imagine this will happen to everyone at some point though. It doesn't happen very often, it just out of the blue will happen one day. I guess the more you talk on the phone the more likely you will be to eventually experience it Maybe it has something to do with enabling the keypad? As that is what I did last night to punch in an extension.
This problem happened with my gf, when she had a droid. For some reason while she was talking on the phone the screen wouldn't always stay off and she would bump the on screen buttons with her cheek and end up usually trying to add a new caller to the call, thus muting whom she was talking to. She also had a lot of problems with the Capacitive touch screens, it wouldn't register half the time where she touched.
I've never had this happen to me, I doubt it actually will. It must be something related to how we hold our phones, and where it lines up to peoples differently shaped heads.
bofslime said:
This problem happened with my gf, when she had a droid. For some reason while she was talking on the phone the screen wouldn't always stay off and she would bump the on screen buttons with her cheek and end up usually trying to add a new caller to the call, thus muting whom she was talking to. She also had a lot of problems with the Capacitive touch screens, it wouldn't register half the time where she touched.
I've never had this happen to me, I doubt it actually will. It must be something related to how we hold our phones, and where it lines up to peoples differently shaped heads.
Click to expand...
Click to collapse
Never happened to me in 2-3 years with the Iphone. To act like it is happening because we are holding the phone wrong is a bit absurd, I mean it's not exactly a complicated process I will try and figure out what's happening, haven't paid much attention to it yet because I figured it was a fluke but it happened twice now and is happening to other people.
One thing I noticed last night was the phone screen was still blacked out while the beeps happened so it's not a sensor thing the screen is actually blacking out it's just being activated again by something that happens after it's off I assume.
I'm not using a case or anything. It NEVER happened to me with the iPhone, but it happens quite often with the Nexus One. VERY annoying... It should be like the iPhone, where when its by your face, it shuts off the screen AND disable the touch buttons below the screen.
I think its the touch buttons causing the problem... Because my screen does turn off when its by my face.
Legaleye3000 said:
I'm not using a case or anything. It NEVER happened to me with the iPhone, but it happens quite often with the Nexus One. VERY annoying... It should be like the iPhone, where when its by your face, it shuts off the screen AND disable the touch buttons below the screen.
I think its the touch buttons causing the problem... Because my screen does turn off when its by my face.
Click to expand...
Click to collapse
This is the behavior I experience with my nexus one (stock and custom roms). As soon as I place it near my face the proximity sensor turns off the screen.
The capacitive buttons below the screen are disabled when the screen turns off for me as well. I just called in to voice mail and hit every one while the screen was off due to the proximity sensor, not a single response from any button or the screen and no change in call status when I moved the phone away and the screen came back on.
krohnjw said:
This is the behavior I experience with my nexus one (stock and custom roms). As soon as I place it near my face the proximity sensor turns off the screen.
The capacitive buttons below the screen are disabled when the screen turns off for me as well. I just called in to voice mail and hit every one while the screen was off due to the proximity sensor, not a single response from any button or the screen and no change in call status when I moved the phone away and the screen came back on.
Click to expand...
Click to collapse
Yea it's some kind of fluke, It happens so randomly I am thinking it might be something to do with the internet connection like checking mail or maybe the GPS doing something that wakes up the buttons while the proximity sensor keeps the screen off because everything will be fine then all of a sudden it happens while the screen is still blacked out.
Sounds like a factory reset might fix this issue... definitely not normal behavior.
I think this is happening to a bunch of people. I don't think a factory reset would help. I think its a bug...
uansari1 said:
Sounds like a factory reset might fix this issue... definitely not normal behavior.
Click to expand...
Click to collapse
No it's not a normal behaviour you are correct however it's not anything a factory reset is going to fix either. It's some kind of software bug that once enough people experience it will get sorted, just a matter of time before enough people start complaining to bring it to attention of Google or HTC.
bluehaze said:
Never happened to me in 2-3 years with the Iphone. To act like it is happening because we are holding the phone wrong is a bit absurd, I mean it's not exactly a complicated process I will try and figure out what's happening, haven't paid much attention to it yet because I figured it was a fluke but it happened twice now and is happening to other people.
One thing I noticed last night was the phone screen was still blacked out while the beeps happened so it's not a sensor thing the screen is actually blacking out it's just being activated again by something that happens after it's off I assume.
Click to expand...
Click to collapse
Are you accidentally hitting the volume buttons on the side of the phone? It sounds like you might be turning the in call volume down, thus leading to it being muted.
^^ No... My face actually hits the mute button. I then have to click the mute button with my finger once i realize the person can't hear me and then they start hearing me again after I click it.
It happens with other buttons on the screen too.
Legaleye3000 said:
^^ No... My face actually hits the mute button. I then have to click the mute button with my finger once i realize the person can't hear me and then they start hearing me again after I click it.
It happens with other buttons on the screen too.
Click to expand...
Click to collapse
Figured I would ask... I sell cell phones, and I get about 1 person a day in that has muted their in call volum by accidently hitting the volume toggle button without knowing it... all different phones (BB's are the worst!).
Anyways, my proxy sensor works perfect! I even just tested it a bit, and it senses a single finger tip starting about 1" away from the screen anywhere along the top of the screen... worked on both the left and right side and everywhere in between just fine.
I use my phone a lot at work in call (calling in to CS, calling the manager, etc) and have not had a single proxy sensor issue in the week I have had my phone.
bluehaze said:
No it's not a normal behaviour you are correct however it's not anything a factory reset is going to fix either. It's some kind of software bug that once enough people experience it will get sorted, just a matter of time before enough people start complaining to bring it to attention of Google or HTC.
Click to expand...
Click to collapse
May not be normal, but its not a bug that seems to be effecting all phones. Same thing that not everyone is experiencing random touch events, 2g/3g toggling, or dust/dogfooding. To say every phone has this problem because you do is simply short sighted.
bofslime said:
May not be normal, but its not a bug that seems to be effecting all phones. Same thing that not everyone is experiencing random touch events, 2g/3g toggling, or dust/dogfooding. To say every phone has this problem because you do is simply short sighted.
Click to expand...
Click to collapse
LOL shortsighted eh? It's a bug it will happen to more and more people eventually and you will see, i'm sure it will happen to you eventually as well. Only thing shortsighted is your reply.
Good day to you sir.
So you've played with changing button sensitivity, heard about perhaps removing the screen protector, but still don't get it?
I think I might.
Try this, let me know if you guys can confirm, then perhaps we need to send info to HTC?
Unlock your screen
Place your phone on a level surface so its curved back can rock back and forth.
Enter the app drawer, so pressing HOME will actually do something.
As gently as you can, steady the phone with one hand, and touch HOME (It should work)
Now, re-enter the app drawer and press quickly on your phone's HOME key. This will cause it to quickly rock back and forth a bit and shake.
Press the home key all you want, it shouldn't work... especially the more you bang on it.
Wait 10 seconds.
Steady your phone again, press HOME gently. It should work.
The theory? Something is programmed in the phone that if it detects rapid shaking, like maybe in a pocket or being handed back and forth during watching a video... to turn off the buttons to prevent undesired actions. BUT, the curved back of the phone naturally lets this motion occur so it's triggering when it shouldn't.
If you're particularly twitchy, maybe that can cause it from time to time while even in hand too?
SOLUTION:
Run calibration tool a few times until the symptom goes away. Try alternating between pressing more firmly or more softly to make a difference. Take care to center your fingers on the letters.
If you experience bad button behavior while phone is on a flat surface, re-calibrate:
SETTINGS->Language and Keyboard->HTC Sense Input->Advanced->Run Calibration Tool
I couldn't replicate this problem. The home button works as intended while being rocked. I also haven't found to have any button response issues that some encountered.
Long813 said:
I couldn't replicate this problem. The home button works as intended while being rocked. I also haven't found to have any button response issues that some encountered.
Click to expand...
Click to collapse
LOL
compact_bijou said:
LOL
Click to expand...
Click to collapse
Heh, come on man... the phone has BOOM Sound, it was meant to be rocked, no?! :laugh:
Serious note though... yeah always have thought the buttons worked fine too and thought other people were crazy...
I lay it flat though casually press them, they go away and don't come back.
Also couldn't replicate it. Basically the home/back buttons work when they want to, which apparenlty is about 95% of the time. The other 5% is just purified annoyingness.
Allegedly HTC has fixed the button problem in 1.29.XXX.12 which so far has only rolled out to unbranded phones in Europe and Asia. However if you have the international phone you can install the newest Android Revolution ROM which is based on the .12 software. Everyone who has .12 seems to agree that the button sensitivity issue is gone.
Re-ran calibration tool pressing normally and it seems to have fixed it.
No amount of shaking or rapid pressing causes the phone to miss a button press.
This is with US Version of phone w/ screen protector.
If you experience bad button behavior while phone is on a flat surface, re-calibrate:
SETTINGS->Language and Keyboard->HTC Sense Input->Advanced->Run Calibration Tool
I've had this problem with 2 different roms now (PureNexus, Chroma) on a few kernels (stock, ElementalX) so I'm not sure whats causing it but I need a fix. In a call, many times the screen just stops responding. Sometimes I can turn the screen on/off using power button and its fixed. Other times nothing works and I have to do a hard reboot by holding down power key since nothing else works on screen.
This is on latest version of the rom/kernels. Any ideas?
When you say its stops responding, do you mean it goes dark and nothing displays on screen? Or that its on with everything displaying but tapping it does nothing?
Only when in contact with ears?
akholicc said:
When you say its stops responding, do you mean it goes dark and nothing displays on screen? Or that its on with everything displaying but tapping it does nothing?
Click to expand...
Click to collapse
Its on, touch doesn't do anything. The phone is working since volume keys bring up the UI but you can't do anything. Also proximity sensor works, it turns on/off as I bring near ear. I don't have a screen protector.
ECrispy said:
Its on, touch doesn't do anything. The phone is working since volume keys bring up the UI but you can't do anything. Also proximity sensor works, it turns on/off as I bring near ear. I don't have a screen protector.
Click to expand...
Click to collapse
I'm having a similar issue from the last month.. I'm on DP5
when i get a call most times the screen is off.
To answer the call i've to put on the screen, unlock the phone and then go to the heads up notification and choose answer there..
waiting for nougat final hoping it'll fix this.
Tried fiddling around with notifications importance setting.. it helped a little but then there was the annoying heads up showing along with the regular incoming call screen.
Sometimes (very rarely, has happened twice) the screen just remains black and will only work normally after a reboot.
Anybody have any suggestions?
I was having similar issues, also on the Developer Preview and I ended up noticing that the phone app was blocked from showing any notifications despite the fact that I never set it that way. I would hear the call ringing but would never see the screen to answer. Just changed that setting and everything was back to normal. Perhaps something is causing the phone app to fail to show notifications for you as well.
Non rooted, T mobile branded 3 month old note 8. No water damange, no drops etc.
Using chrome one miniute, set the phone down to watch a movie on my tablet, picked up the phone to check messages and boom. Screen is off. The phone works, I can even answer calls because I know where the answer button is on the screen, haptic feedback works, all indicator lights work. The phone screen remains off.
Tried a soft reset (tried hard reset too the best I could being I cant see the screen) and the phone seems to reset based on the vibration and indicator light patters but the screen remains off. It's as if a physical connection between the screen and the brains of the phone has been severed. Literaraly the weirdest thing that has happened to me in a decade of Android phone ownership.
Googled all the black screen issues with these phones and most of them are resolved with just a soft reset... some said that the phone is in it's lowest dimmed state and go to a dark room and i'll see it faintly and then can increase brightness... no luck...
Has anyone experienced this?
I would say it's a warranty job, just tried turning my brightness to zero and you can still see the screen.
I did have a similar problem on an old note that had root and custom rom though but I had somehow set the volume rocker to control brightness and it had lowered itself to minimum in my pocket
KEVIN88GT said:
Non rooted, T mobile branded 3 month old note 8. No water damange, no drops etc.
Using chrome one miniute, set the phone down to watch a movie on my tablet, picked up the phone to check messages and boom. Screen is off. The phone works, I can even answer calls because I know where the answer button is on the screen, haptic feedback works, all indicator lights work. The phone screen remains off.
Tried a soft reset (tried hard reset too the best I could being I cant see the screen) and the phone seems to reset based on the vibration and indicator light patters but the screen remains off. It's as if a physical connection between the screen and the brains of the phone has been severed. Literaraly the weirdest thing that has happened to me in a decade of Android phone ownership.
Googled all the black screen issues with these phones and most of them are resolved with just a soft reset... some said that the phone is in it's lowest dimmed state and go to a dark room and i'll see it faintly and then can increase brightness... no luck...
Has anyone experienced this?
Click to expand...
Click to collapse
Try pressing and holding Volume down and power button for 5 to 7 seconds to force power off, then try to boot to download mode Volume Down + Bixby + Power button and see if the download mode screen shows......if not then probably a bad screen.
Sent from my God Mode 8
Tried it......nothing.....warranty job it is.... Bummed to have some refurnished phone in exchange for a Brand new 900 dollar phone just a few months back?
KEVIN88GT said:
Tried it......nothing.....warranty job it is.... Bummed to have some refurnished phone in exchange for a Brand new 900 dollar phone just a few months back?
Click to expand...
Click to collapse
Yeah that sucks, i can imagine..... i too hate the idea of refurbished units being swapped for warranty....bs, should be brand new unit!
Sent from my God Mode 8
so I had it replaced under warranty through T mobile. Refurb phone will come in today. One quesion. Should I let the Tmobile techs do the data/settings transfer from old phone to new one or just do everything myself from scratch (which will obviously take longer).
This happened to my phone twice for the past month or so. (both in Nougat and Oreo - Non rooted) Black screen but phone seems to be responding -- I can receive calls and notifications etc -- And force reboot doesn't fix it. I've also tried drainging the phone when it first happened to me but doesn't work. HOWEVER, it gets okay so randomly. Like I just left it for couple of hours and it just worked when I hit the power button.
I did tried bringing the device to Samsung but what they did is to just manually upgrade/reset the software in their end which I could have done in my part but I just let them do it. They told me to come back if it happens again which is kinda BS.
I can conveniently say this is a Hardware issue. I will wait for it to happen again on my phone and request for a replacement. Phone is 4 months old when it first happened.
I have the same issue with blank screen but phone is working.
It started couple of weeks after i dropped my phone on the ground. There is black dot on my screen and broken glass but phone was working ok and was still pretty usable. But then it started:
Display works fine but when i switch display of, lock the phone or display switched because of its timer it didn come switch on... But phone works, i can use it with blank (black) screen.
I had to do force restart so the display will turn on with samsung logo and booting screen, and keep on till another switch of.
I was trying every setting (but no hard reset) and then i found a little hack:
When you turn on the "Always On Display" (AOD) function you can let the screen switch off or do it manually, wait for 1-2 sec and always on display will come up to the screen. Then when you press home button or lock button screen will swtich on normally. YOu can type pin and use phone witch screen working. But when you try to unlock from "AOD" with your finger or your eyes it unlock but with screen black.
So i was using it like this. everytime you need to wait second untill AOD comes up, but it was working fine.
Problem nu 2 is that now it stop working, AOD is working but when i want to switch screen on from AOD it shows black screen and phone is working on blind.
So everytime after my screen goes black or to AOD i have to unlock the phone blindly and "Force restart" it and have to keep waiting until boot, and then have to never let phone to screen of.
Its not usuable.
¨
Now what do you think? Is it hardware problem or software problem? Because screen is working but randomly. The black dot of dead pixels on the screen is getting slightly bigger in time (about 1 year) but its like 1.5cm round. Maybe this cause the problem? And why hack with AOD was working for half a year and then stoped working? There wasnt any updates right before, but i tried to install some apps (non display related) so ill try to uninstall them.
Hawe you got any idea if i can repair it on my own even if i loose the waterproofability?
Or can it be replaced for free if i have a warranty? (I dont have insurance)
Thanks for your tips guys.
Reprocrastinator said:
I have the same issue with blank screen but phone is working.
It started couple of weeks after i dropped my phone on the ground. There is black dot on my screen and broken glass but phone was working ok and was still pretty usable. But then it started:
Display works fine but when i switch display of, lock the phone or display switched because of its timer it didn come switch on... But phone works, i can use it with blank (black) screen.
I had to do force restart so the display will turn on with samsung logo and booting screen, and keep on till another switch of.
I was trying every setting (but no hard reset) and then i found a little hack:
When you turn on the "Always On Display" (AOD) function you can let the screen switch off or do it manually, wait for 1-2 sec and always on display will come up to the screen. Then when you press home button or lock button screen will swtich on normally. YOu can type pin and use phone witch screen working. But when you try to unlock from "AOD" with your finger or your eyes it unlock but with screen black.
So i was using it like this. everytime you need to wait second untill AOD comes up, but it was working fine.
Problem nu 2 is that now it stop working, AOD is working but when i want to switch screen on from AOD it shows black screen and phone is working on blind.
So everytime after my screen goes black or to AOD i have to unlock the phone blindly and "Force restart" it and have to keep waiting until boot, and then have to never let phone to screen of.
Its not usuable.
¨
Now what do you think? Is it hardware problem or software problem? Because screen is working but randomly. The black dot of dead pixels on the screen is getting slightly bigger in time (about 1 year) but its like 1.5cm round. Maybe this cause the problem? And why hack with AOD was working for half a year and then stoped working? There wasnt any updates right before, but i tried to install some apps (non display related) so ill try to uninstall them.
Hawe you got any idea if i can repair it on my own even if i loose the waterproofability?
Or can it be replaced for free if i have a warranty? (I dont have insurance)
Thanks for your tips guys.
Click to expand...
Click to collapse
If you're under warranty it will likely be a free repair, unless they find other damage. Like moisture damage.
As far as fixing it yourself, it's just about as cheap to have Samsung do it than it is to buy the parts yourself. It's $229 for Samsung to do it, and you'll maintain the water resistance rating.
same has happened to me
KEVIN88GT said:
Non rooted, T mobile branded 3 month old note 8. No water damange, no drops etc.
Using chrome one miniute, set the phone down to watch a movie on my tablet, picked up the phone to check messages and boom. Screen is off. The phone works, I can even answer calls because I know where the answer button is on the screen, haptic feedback works, all indicator lights work. The phone screen remains off.
Tried a soft reset (tried hard reset too the best I could being I cant see the screen) and the phone seems to reset based on the vibration and indicator light patters but the screen remains off. It's as if a physical connection between the screen and the brains of the phone has been severed. Literaraly the weirdest thing that has happened to me in a decade of Android phone ownership.
Googled all the black screen issues with these phones and most of them are resolved with just a soft reset... some said that the phone is in it's lowest dimmed state and go to a dark room and i'll see it faintly and then can increase brightness... no luck...
Has anyone experienced this?
Click to expand...
Click to collapse
This has just happened to my note 8 too. I was about to update it and had started it. set my phone down and picked it up and phone screen is black but can hear the haptic feedback.
I can only see the lock screen and the notifications. Everytime I try to unlock my phone I only get to see a glimpse of the notescreen and then the screen turns black. Even when I try to go to camera through the lock screen the screen goes black too. When I charge my phone it heats up so I haven't really charged it as well. Has this also happened to anyone? It seems as if the phone's sensitivity still works in all places but when I unlock it the screen just goes black.
I also have problem of freezings and always rebooting. Tried soft and hard resets/factory reset. Still same problem. This phone has hardware issue. Do not buy.
I realize this thread is quite old but I have this exact same issue now. I have managed to discover some other information by playing around with various settings which are noted below. To begin with, I was able to used the AOD hack posted above for a while but it no longer works. The only way I can get my screen to come back is with a soft reset - but as soon as the screen times out or i turn it off, it goes black, with or without AOD enable. All the on screen buttons still work as well as the haptic feedback - I just can't see anything.
Now on to what I have found:
One thing I have found is if I turn off adaptive screen brightness and crank the brightness slider to the right, when it goes black I can faintly see some of the buttons - enough that I can turn the phone off or restart it from the power menu (If I switch the default setting to night that also helps to see the buttons a bit better). Also, if I enable night mode I can also see the brightness slider faintly but when I slide it left, it just makes the screen completely black and when I slide it right, it only returns it to the very faint brightness level.
So at this point I am stuck. To summarize the issue:
1. When the screen either times out or turns off, it is still "alive" but goes black. It will not return to normal brightness.
2. Turning off adaptive brightness and cranking brightness slider to right allows you to see faint buttons after screen times out but won't return to normal brightness.
3. Enabling night mode helps to see the faint buttons, in particular the brightness slider a bit better. However the screen still cannot return to normal brightness.
4. The only way to get the screen back to full brightness (albeit temporarily until the next timeout) is to turn off the phone or reset from the power menu; or soft reset holding volume down + power simultaneously.
Hopefully someone else has figured out a way to recover this. I am on Android 9 with Samsung UI 1.0
Phone is completely stock, never rooted and completely out of warranty.
I just picked up an XZ2 for a steal. So far I really like the phone, but one thing has really been nagging me. The lift to wake functionality works pretty well most of the time, but occasionally, it will just stop working completely. It's like the phone goes to sleep and stops recognizing the sensors or something. It doesn't happen after sitting for a long time, either. It actually happens right after I've been using it. Today, the screen timed out and went black and no matter how much I shook the phone, put it in my pocket and took it out, etc., it never worked again until I hit the power button.
Before someone suggests just hitting the power button or fingerprint sensor: You're missing the point. I shouldn't have to. It's bad enough that Sony took tap-to-wake from us and never gave it back. But I expect this feature to work consistently. Really, you should rarely, if ever, have to hit the power button. A similar feature on the iPhone works without fail almost 100% of the time.
I'm just looking to see if anyone else has experienced this. The phone is fresh out of the box, has the latest build (51.1.A.4.225) and was set up manually, not restored from a cloud backup. Has anyone else seen this?
Oh yes, it is one of three really small, miniscule bugs I've got with my XZ2. In my case, the lift to wake only stops working a few times and after I wake the phone manually, it works the way it should work again. But it only happens in those rare times.
AlvinZahran98 said:
Oh yes, it is one of three really small, miniscule bugs I've got with my XZ2. In my case, the lift to wake only stops working a few times and after I wake the phone manually, it works the way it should work again. But it only happens in those rare times.
Click to expand...
Click to collapse
Thanks. Yeah, it's annoying. The inconsistency drives me crazy. It seems to have something to do with the screen timeout.
I wish they would just give us proper tap to wake back.
Sent from my H8266 using Tapatalk