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.
as the title says i was reading when the menu started showing and hiding again and again i tought was some book issues but when i got to the homescreen it began to run apps i had on it, i have no idea of the cause of this problem
I've had this same problem. I believe it's just the software and not a deficient screen. If you look over on the nookdevs website, there's a page about recalibrating the screen. I've tried it a couple of times and it's definitely improved it. Every now and then something wacky happens, but I guess that's to be expected when you let B&N develop for Android.
I had this happen myself once, and it was pretty annoying... If I didn't have adb available I don't think I could have fixed it until I did. I wasn't able to tap the screen myself, it was taping all over the place.
I did manage after a few minutes to get multitouch paint installed and it was drawing weird dots, lines, angles, etc...
I now have the recalibrate command in gscript but not sure I could run it while it's acting up. Luckily it's only happened once, and it happened while plugged in but never seen it happen again.
Happens a lot on my NC, and I think every time its because my kids touch it with dirty fingers (sweets, chocolate etc), smearing small amounts of dirt on the screen.
The screen goes nuts within few seconds, thinks its being clicked etc...
Wiping/cleaning the screen helps to resore normal behavior, btw - while the screen is moist it does not work for me at all...
Ordered screen protectors, lets see if it makes a differencel
My screen randomly goes nuts as well. It seems like a sudden, rather than a gradual thing. The screen sometimes gets pretty dirty, but cleaning it didn't seem to make much difference. Odd thing is, what DID make a difference was taking it out of the aftermarket case. I have no idea why this would work, but it does. One thing this case does is that it pushes the power and volume buttons in, as it uses four elastic straps at the corners. Maybe holding these buttons a certain way recalibrates the screen, and if you're touching it at the time, it freaks out?
I've noticed my screen only bugs out when I have it plugged into the charger.
As long as its unplugged, its fine. As soon as i pop in the cord, the screen goes haywire.
Only the wall charger though, not when its plugged into the USB on the computer.
My screen was doing that until I got a screen protector.
Sent from my LogicPD Zoom2 using XDA App
Also, if you lock and unlock the NC it should stop acting funny.
I noticed that too. Mine hasn't gone REALLY nuts since I took it out of it's case, but sometimes when playing angry birds, it freaks out to the point where I can't play. Hitting the power button, and then hitting it again, and unlocking makes it normal. Wouldn't that indicate it's software instead of hardware? Maybe there's more than one problem?
RChadwick said:
I noticed that too. Mine hasn't gone REALLY nuts since I took it out of it's case, but sometimes when playing angry birds, it freaks out to the point where I can't play. Hitting the power button, and then hitting it again, and unlocking makes it normal. Wouldn't that indicate it's software instead of hardware? Maybe there's more than one problem?
Click to expand...
Click to collapse
Mine does the same thing every now and again. And like you, locking the screen and waking it back up fixes it every time. It's definitely software related.
Do your cases have a latch? With a magnet? Because I'm starting to think that may have something to do with it.
My case has a latch, but the magnet is not against the nook when I'm using it..
HotShotAzn said:
Do your cases have a latch? With a magnet? Because I'm starting to think that may have something to do with it.
Click to expand...
Click to collapse
Heh, I've considered that.. Also considered the mystery sensor to the left of the Nook button too.. Nook is afraid of the dark.
Seriously though, with the CPU guvna' set to ondemand and wifi turned OFF before I power it off I haven't seen it reboot yet. It rebooted once yesterday and I know it had wifi left on as I had just been using it and didn't turn it off before it went to sleep.
So totally making up numbers here....
Default CPU governor + wifi on = 30% chance it's gonna reboot when it goes to sleep..
ondemand governor + wifi on = 20% chance it's gonna reboot
ondemand govenor + wifi off = <10% chance it's gonna reboot (not gonna even say 0 here.. heh)
RChadwick said:
My case has a latch, but the magnet is not against the nook when I'm using it..
Click to expand...
Click to collapse
I tested this theory. When the Nook is in the case, I get crazy screen taps when i try to type something. Out of the case, its perfectly fine.
When I just rest the Nook on the open case (not inside the straps/holders), it will also get crazy screen taps.
One thing to note is I also did not have any problems before updating to 1.0.1. Not saying the update is the cause of the problem but its one of the variables.
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
I've found that after a period of time once the screen has turned off (5 to 10 mins) I need to double tap the screen, then double tap again to actually get it to wake up.
I'm on the .77 FW and while I've heard some of the earlier firmwares could be more responsive I found the screen was TOO responsive and prefer to stick on the latest firmware.
So now that we're all rooted etc, there must be some fix that can be done. Is it a case that the tap2wake process goes to "sleep" after a period of time and the first 2 taps wakes it?
If you move your phone first, then it will work by double tapping.
I think that quadruple tap works because one of those first two taps moves the phone.
Not from my experimentation. It doesn't seem to matter if i've moved it first or tapped it directly when it's sitting on the table. Then only factor that seems to matter is time since screen off.
Thanks for the input though.
It's kinda flaky in my experience. The new firmware did indeed add the "must move phone first" feature to the tap-to-wake, but sometimes two taps don't seem to register even after moving and I have to use the button. Might be something to do with the screen sensitivity being reduced combined with a screen protector perhaps?
I also found the firmware update messed with the proximity sensor and my screen now fails to come on when I want to end a call and move the phone away from my ear. Means I have to use the button to turn on the screen to hang up. Very annoying.
pipspeak said:
It's kinda flaky in my experience. The new firmware did indeed add the "must move phone first" feature to the tap-to-wake, but sometimes two taps don't seem to register even after moving and I have to use the button. Might be something to do with the screen sensitivity being reduced combined with a screen protector perhaps?
I also found the firmware update messed with the proximity sensor and my screen now fails to come on when I want to end a call and move the phone away from my ear. Means I have to use the button to turn on the screen to hang up. Very annoying.
Click to expand...
Click to collapse
I'm on A.5.77, which is the latest, right?
I have this issue about 5% of the time, 95% of the time even if I have the phone lying still on the table double tap works. Must be something (also) else than the firmware!
pipspeak said:
It's kinda flaky in my experience. The new firmware did indeed add the "must move phone first" feature to the tap-to-wake
Click to expand...
Click to collapse
double tap works first time every time even if the phone has been sitting still and idle for 10 hours.
I know theres a few people who have this problem but its something other than just the new firmware.
I'm curious who has a screen protector and who is using a launcher other than stock (or indeed is rooted). I suspect my screen protector and Nova Launcher are not helping matters, but in my case it was definitely brought on by the new firmware. Before that update I had never experienced any double-tap failure at all... it was 100% reliable.
pipspeak said:
I'm curious who has a screen protector and who is using a launcher other than stock (or indeed is rooted). I suspect my screen protector and Nova Launcher are not helping matters, but in my case it was definitely brought on by the new firmware. Before that update I had never experienced any double-tap failure at all... it was 100% reliable.
Click to expand...
Click to collapse
You could be onto something with Nova Launcher. I switched back to the stock launcher and I think things have improved...
had a tempered glass protector on from day one, phone has always been stock, no other launcher. T2W worked brilliantly until the latest firmware update. frustrating when the phone is the car mount, i have to hit the power button to get the screen on instead of just tap-tap.
quarrymanpaul said:
You could be onto something with Nova Launcher. I switched back to the stock launcher and I think things have improved...
Click to expand...
Click to collapse
Full day's use now and replacing Nova launcher with Apex has definitely improved things.
Might help others in the same situation who are scratching their heads wondering why everyone else seems to have perfect tap2wake.
Tried Apex for a day as well. No different than Nova for me.
hey, just figured out something, by accident.
yup, double tap to wake is still mucked up from the latest update (unless the phone is picked up first) but TRIPLE TAP to wake works consistently for me after the phone has been flat/unmoved for some time.
tap-tap-tap
AM Radio said:
hey, just figured out something, by accident.
yup, double tap to wake is still mucked up from the latest update (unless the phone is picked up first) but TRIPLE TAP to wake works consistently for me after the phone has been flat/unmoved for some time.
tap-tap-tap
Click to expand...
Click to collapse
Not working here.
I have a Nillkin tempered glass on mine though.
quack3d said:
I have a Nillkin tempered glass on mine though.
Click to expand...
Click to collapse
me too. weird. fingers crossed the next update takes care of this, properly.
AM Radio said:
...TRIPLE TAP to wake works consistently for me after the phone has been flat/unmoved for some time.
tap-tap-tap
Click to expand...
Click to collapse
Works for me too. [emoji4]
Did Lollipop fix this problem?
quack3d said:
Did Lollipop fix this problem?
Click to expand...
Click to collapse
Not really. In fact it got worse.
quarrymanpaul said:
I've found that after a period of time once the screen has turned off (5 to 10 mins) I need to double tap the screen, then double tap again to actually get it to wake up.
I'm on the .77 FW and while I've heard some of the earlier firmwares could be more responsive I found the screen was TOO responsive and prefer to stick on the latest firmware.
So now that we're all rooted etc, there must be some fix that can be done. Is it a case that the tap2wake process goes to "sleep" after a period of time and the first 2 taps wakes it?
Click to expand...
Click to collapse
Well, I can tell you why this is happening. this happened to me, because I just had too many xposed modules.. once I got rid of them, everything went back to normal
Been a long time since I've posted here but found this thread as had the same issue when the phone is flat on a table.
Anyway, think I've found a solid solution or work around, depends how you look at it. If you use just an extended finger, all other fingers closed or away from the phone, it's very inconsistent but mostly unresponsive.
Solution: grip the top and bottom of the phone lightly with your thumb and middle or 4th finger at the same time as tapping the screen with your index finger. Works every time for me.
So Sony's reduced the sensitivity to the point where it needs additional capacitance so it knows you are holding the phone and it won't unlock in your pocket. Makes sense.
pretty frastrating here too.. but really can't find out the main reason of the problem here as immediately when I got the phone I rooted it, flashed .77, replaced stock launcher with nova, installed expsed and 2-3 modules :crying:
will try the three-taps and olding-phone+index-finger-tapping workarounds, thanks for the hints
Does anyone else have this issue? It's really driving me crazy to the point where I feel like ditching the Nexus 6. It's not even every call, but it is enough to annoy me. Pull the phone away from my head and the screen wont wake up. All I can do is long hold power to force a reset. It's really annoying. I've tried the proximity fix for 5.1 but it still happens. I can't set "power to end call" because also sometimes the phone doesn't wake the screen when there is an incoming call so I have to press power to wake the screen to see who it is.
Does anyone have any idea how to get around this other than the two solutions above? This has happened on both my devices (Original and RMA) and I just can't take it any more.
I sounds like a faulty proximity sensor. And I've observed intermittent behavior like this on previous phones (but not my N6). You can test this with a number of apps. I've used "Sensor Box for Android", but there are several more. Prox sensor is located near the top LH corner. With the app open and on prox sensor, passing your hand over it should register on the app.
You are so active on this forum that I won't even ask about a screen protector....
The proximity sensor seems to work fine under all tests that I have done. I actually use Tasker to utilise the proximity sensor to set ringer volume based on whether it is activated or not (eg in my pocket, proximity sensor CLOSE, set ringer high).
Its not every call either and multiple Nexus 6 devices have had this issue for me too. Proximity sensor works in every test
That's weird. I've had no issues at all. I assume you have the issue on the stock ROM too.....
I suppose I'll have to test though I don't really want to run stock.
What about disabling Tasker and trying it out.
Happens with or without tasker. It's pretty much always done it since 5.1
There are known issues with the prox being flaky on this device. I just need to find a way to overcome this.
Remember, we need to separate problem solving from the idea of how we want our phone to look and perform. Once you've identified the root cause, you can then decide what steps you want to take to solve it.
*Sigh* Yes I know. But it's so intermittent I won't know if it solves it for a looooong time. It would be quicker to return to stock, sell it and buy something else
I've literally never ran stock on the nexus 6.
Like Camera indicated, I'd try removing the screen protector if you have one and see if it's better.
It's not a protector issue.
Let's assume I've done all the obvious things except flash stock
Edit. I'm going to try and use power button ends call. Just to see of its an active call that causes it.
Hopefully it will happen when I can take a log cat but inise the phone very rarely.
Try this app in the Playstore.
https://play.google.com/store/apps/details?id=com.vorlan.screenoncall.free
I had a similar issue where the screen would time out while I was on a call and wouldn't wake when I moved the phone away from my face. I had to hit power button to wake phone and enter pin just to end a call. I make/recieve over 100 calls per day and it was getting old til I found this app. Works perfectly every time.
Thanks but that's not the same issue. Mine will not wake at all. I have to force a reboot to get display
You might give the app a try just to see. It keeps the screen on during a call but the proximity sensor still shuts the screen off unless you are on speaker phone. It may not work, but worth a try to keep your N6!
I've seen the same thing with my N6, display goes black (randomly, not even related to a call) and the only thing I can do is reboot. Haven't wasted any time looking for a solution, 'cause I don't think there is an easy one and there is no way to know if something you try is even going to work! I just reboot and move on.
Just posting to let you know you are not crazy and there is someone else out there with the same problem!!!
I'm not sure what you mean. I've been recommended this app before but I don't like the idea of mybscreen being on.
What do you mean it keeps the screen on but proximity still shuts it off? .
Thanks for confirming
Basically it doesn't let the screen timeout. Proximity sensor still functions like normal.
I would try it and see.
If it helps good, if not no harm. It definitely fixed my issue, even if my issue wasn't exactly what you're experiencing.
Well power button end call didn't help. I don't think it is a proximity sensor issue. Let's hope it happens when I can get a logcat. Unlikely. Maybe a job for tasker.
I had this issue too. I eventually thought it was tied to UV, but then I installed all stock and didnt change anything and it still happened. Maybe a bug in lollipop.