Related
Hey guys,
Thought I'd post this here and keep you guys updated on further developments.
I live in the Netherlands and bought a 32GB version at Dixons at the 13th of November 2012
I had found the touchscreen a bit unresponsive sometimes in the past.
But couldn't really find out why it was acting up. I finally isolated the issue.
It is exactly the same as this guys vid:
(Thanks for the vid injahnet)
Together with a little backlight bleeding, I decided to send for repair.
(The problem persisted after a factory reset, no other apps were open when testing.)
I went back to Dixons and showed the problem to the Dixons dude.
He acknowledged there was an issue and sent it for repairs or replacement.
Due to the holidays this can take some time. Maybe even next year
I was about to open my tablet for a look inside one of these days, boy am I glad I didn't do that yet
Anyway to get a good view on this issue globally, are there more people that have the same issue?
You could go to: Settings > Developer options > and then under "Input" you can enable Show touches. and try to to the same procedure as in the vid. (Thanks Peterk-1)
Or you could test with MultiTouchTester like Injahnet.
The weird thing is, my dad's N7 16GB does the same.
Update 17-12-2012: Please do not test while plugged in as the device will be grounded and the issue will not occur. (Thanks dad)
Feedback is really appreciated!
Please vote in the poll above!
Cheers,
Daan
I have zero problems with multitouch while using my Nexus 7. Working just fine, but you must disable any apps which interfere with gestures or it'll steal events.
Can't say I've ever used multitouch with the N7 laying on a random object however.
But sure, send it in for repair......... I'll keep using mine.
If anyone thinks they have multi touch problems then loading an app isn't required. Just go into Developer Options and under Input you have two options to display touch and track detail.
peterk-1 said:
If anyone thinks they have multi touch problems then loading an app isn't required. Just go into Developer Options and under Input you have two options to display touch and track detail.
Click to expand...
Click to collapse
Nice one. I'll add that.
khaytsus said:
I have zero problems with multitouch while using my Nexus 7. Working just fine, but you must disable any apps which interfere with gestures or it'll steal events.
Can't say I've ever used multitouch with the N7 laying on a random object however.
But sure, send it in for repair......... I'll keep using mine.
Click to expand...
Click to collapse
I've done a factory reset before I tested No apps are open except MultiTouchTester
It's in for repairs
Well... Over 200 views. And only 4 votes, which includes mine
Community feedback is failing hard.
Anyway, I'll keep you guys posted on the repaired Nexus.
At the moment of writing we know that three people are having this issue.
I know someone else with a nexus I'll check if he has the issue too.
Cheers,
Daan
Yes, i have this problem. And only while device is laying on the table.
Wow, this is bizarre, thanks for pointing it out. I can confirm it happens when it's laying on my pillow, and doesn't when I'm holding it.
Thanks for the vote guys.
By the way, it seems obvious that the Nexus should not be plugged in while testing.
However I cannot test this 'cause mine is at the shop
Would anyone be willing to test?
I'll add that in the original post (+ a mention of your name and a thank you of course))
Cheers,
Daan
Mine was unplugged while testing.
Sent from my Nexus 7 using Tapatalk 2
if the two touch-points got the same X or Y coordinate my nex7 does only detect one of them. i don't think this is an issue.
herrrevo said:
if the two touch-points got the same X or Y coordinate my nex7 does only detect one of them. i don't think this is an issue.
Click to expand...
Click to collapse
However, zooming in Google maps for example will become quite difficult
Anyone try and see if taping the ground pin on the wifi antenna fixes the issue? This seams like a grounding problem.
ionstorm66 said:
Anyone try and see if taping the ground pin on the wifi antenna fixes the issue? This seams like a grounding problem.
Click to expand...
Click to collapse
Exactly! I was also thinking of this.
Do people who have this issue also have the flickering issue!?
ecoviws buttress
Just an FYI, I installed CM 10.1 with Trinty Seven. Now I get 10 touches on pretty much any surface.
I don't have a multitouch issue, but I do have an entire band on my screen which has stopped responding to touch at times. It all started when I let my tab shut down due to low battery. Initially, the Nexus 7 neither charged (when put on charging, obviously), nor did it boot up. After trying for several hours, somehow it started charging. And since then, sometimes certain areas of my touchscreen become unresponsive to touch. Since the band which is unresponsive is towards the upper part of the screen, using notifications becomes completely impossible. It keeps 'snapping back up' when I try to pull it down, cos while I am pulling it down, the notification tray encounters an unresponsive area, so it just goes back up. Called up Google and they will be sending a replacement device. All I am afraid about is that I have an 8gb version, and they would be sending an 8gb as well, so I hope it isn't refurbished or something, as Asus has stopped making the 8gig model.
I'm having an issue where the screen, ( mostly in a webpage or document,) starts moving up and down and zooming in and out without my input.
Sent from my Nexus 7 using xda app-developers app
Just tested this out and yes, my device is doing it too. Interesting. No other issues like screen flicker (except the auto brightness bug in 4.2). My n7 is c9O
DaanJordaan said:
Well... Over 200 views. And only 4 votes, which includes mine
Community feedback is failing hard.
Anyway, I'll keep you guys posted on the repaired Nexus.
At the moment of writing we know that three people are having this issue.
I know someone else with a nexus I'll check if he has the issue too.
Cheers,
Daan
Click to expand...
Click to collapse
community feedback is not failing hard, more like you're just starting a new thread without bothering to search if issue/topic already exist.
this isn't new and there is no fix, that is just how the touchscreen function. the N7 isn't the only device to have this.
dilldoe said:
community feedback is not failing hard, more like you're just starting a new thread without bothering to search if issue/topic already exist.
this isn't new and there is no fix, that is just how the touchscreen function. the N7 isn't the only device to have this.
Click to expand...
Click to collapse
Don't feed the trolls!
Must... not... feed... aaargh....
You are kinda missing the point of this thread.
It is to see how many people have this issue.
There is no thread capturing that in an easy way unless you want to count every post.
Now please tell your brain to start functioning again and leave this thread alone if you have nothing to add.
Asus Google Nexus 7 32GB touch death zone
Hi DaanJordaan,
Found out that my brand new N7 seems to have a similar "no touch zone" issue; an area the size of my little finger on the left lower part of my screen does not seem to react to touch! It interferes with typing the keyboard in portrait mode (no keyboard problems in up-side-down portrait mode).
When I use the Easylabs Multi Touch test I can see the dot changing color when I move over this area, doesn't happen anywhere else on the screen..
Using the developer tools (turning on the two options that allows to show touch/leave a trail of touch) it becomes even more clear that this area does not react to touch! I can "paint" lines around the "no touch zone" (it actually splits into 2 touch areas using one finger around the "death spot"), and the "no touch zone" reveals itself by not showing any trail/history line of touch..
Oh yes, and it does not matter if I lay the N7 on the table, or hold it in my hand, the issue is always there.
Therefore I returned the N7 back to the MediaMarkt, and they will send it in for repairs...
I've got a bad feeling about this | - )
I am curious to hear about experiences with your N7, once you have it back!
I'll report mine here, in three weeks or so (that's the outlook...).
Cheers!
NeverMind
I have only had my tf701 a day but Ive noticed sometimes when docked to the keyboard if you dont touch the mouse for a few seconds sometimes when you move the mouse again it will make a flicker around where the mouse is located, it doesnt always do it, just wondering if anyone has noticed this or is it a fault with my tablet?
I can live with it, but if there is a known fix it would be nice to sort it.
Thank You
After a bit of messing about I think it only does it with live wallpapers? Which isnt a problem as I wont be setteling on a live wallpaper anyway found them far too distracting.
Would still be nice to know this is fixable though.
Thank You
I was wrong its not to do with live wallpapers, just seems to do it on some apps, for example if I go to apex launcher then settings, if I leave the mouse for 10 seconds or more than rouch to move it, it makes the strange flash across the screen.
Could anyone else please test if theirs does this?
Thanks
Asus considers it to be a feature - not a bug - and calls it "smart backlight adjuster".
For most people it goes away upgrading to 4.3 which I guess you haven't done?
berndblb said:
Asus considers it to be a feature - not a bug - and calls it "smart backlight adjuster".
For most people it goes away upgrading to 4.3 which I guess you haven't done?
Click to expand...
Click to collapse
Yeah I am running 4.3?
I have noticed it does it on the drawer too, only when using the dock and leaving the mouse dormant for 8 seconds or more than moving it again it sends horizontal lines across the screen for a split second, is this the bug *ahem* feature you speak of?
Thanks
berndblb said:
Asus considers it to be a feature - not a bug - and calls it "smart backlight adjuster".
For most people it goes away upgrading to 4.3 which I guess you haven't done?
Click to expand...
Click to collapse
Also when you say adjuster, that sounds like it would be something that requires adjusting but it still does this with screen set to full brightness, or least brightness, with auto off, also wit outdoor on or off, it still does the strange flicker.
I can happily live with it, doesnt bother me that much just dont want it to be something that is going to get worse as Im very close to unlocking the device and dont want to blow all warranty if I already have a fault.
Thanks
dougie175 said:
Also when you say adjuster, that sounds like it would be something that requires adjusting but it still does this with screen set to full brightness, or least brightness, with auto off, also wit outdoor on or off, it still does the strange flicker.
I can happily live with it, doesnt bother me that much just dont want it to be something that is going to get worse as Im very close to unlocking the device and dont want to blow all warranty if I already have a fault.
Thanks
Click to expand...
Click to collapse
No what I had in mind was the screen dimming and brightening. What you describe sounds more like the "flashing black lines" the TF700 has (which seems to be due to some nvidia driver issue). I have not noticed those on the TF701 but then, I am so used to them from the 700 I probably wouldn't even notice. Have not read anything about them in the forums though, so I suspect your situation is unique.
Are you in the US? Get a Squaretrade warranty. I find the peace of mind is worth the $75 since they don't care about locked/unlocked...
berndblb said:
No what I had in mind was the screen dimming and brightening. What you describe sounds more like the "flashing black lines" the TF700 has (which seems to be due to some nvidia driver issue). I have not noticed those on the TF701 but then, I am so used to them from the 700 I probably wouldn't even notice. Have not read anything about them in the forums though, so I suspect your situation is unique.
Are you in the US? Get a Squaretrade warranty. I find the peace of mind is worth the $75 since they don't care about locked/unlocked...
Click to expand...
Click to collapse
No I am in the UK Im afraid, hmmmmm its deffo a tf701 not a 700 hehe
Can you please test for me open your drawer, leave the mouse in the centre for 10 seconds then move it and see if it does the black lines?
Also did the issue ever get resolved or get any worse on the 700 or is it just something the user gets used to?
Thank You
dougie175 said:
No I am in the UK Im afraid, hmmmmm its deffo a tf701 not a 700 hehe
Can you please test for me open your drawer, leave the mouse in the centre for 10 seconds then move it and see if it does the black lines?
Also did the issue ever get resolved or get any worse on the 700 or is it just something the user gets used to?
Thank You
Click to expand...
Click to collapse
Don't have the keyboard for the TF701 - yet. So I can't help you with your test.
The black lines on the 700 are benign - I don't even notice them anymore. But I don't think my 701 has them, so there is a possibility that your tablet has a glitch...
berndblb said:
Don't have the keyboard for the TF701 - yet. So I can't help you with your test.
The black lines on the 700 are benign - I don't even notice them anymore. But I don't think my 701 has them, so there is a possibility that your tablet has a glitch...
Click to expand...
Click to collapse
Thanks, I have sent Asus an email to see if they will help me, I bought the tablet second hand though so they probably have no interest even though it is only 3 months old and hasnt been out long enough to be out of warranty.
If they will fix or replace it for me ill take that, if not i can happily live with it
dougie175 said:
No I am in the UK Im afraid, hmmmmm its deffo a tf701 not a 700 hehe
Can you please test for me open your drawer, leave the mouse in the centre for 10 seconds then move it and see if it does the black lines?
Also did the issue ever get resolved or get any worse on the 700 or is it just something the user gets used to?
Thank You
Click to expand...
Click to collapse
Just tried your test and I see no lines. Maybe because I'm not on the stock rom exactly?
dougie175 said:
Thanks, I have sent Asus an email to see if they will help me, I bought the tablet second hand though so they probably have no interest even though it is only 3 months old and hasnt been out long enough to be out of warranty.
If they will fix or replace it for me ill take that, if not i can happily live with it
Click to expand...
Click to collapse
I don't want to be negative here, but waiting for Asus' response is pretty useless. Their support staff has two answers for questions beyond: "Where do I find my pictures?" and they are:
a) Factory reset, and if that does not help:
b) Send it in for repair - which may or may not cost you a bundle...
If you do send it in get written confirmation that your tablet is still under warranty first and take pictures of your tablet documenting its condition, how you packed and shipped it etc.
Thanks for the replies
This is what I get
dougie175 said:
Thanks for the replies
This is what I get
Click to expand...
Click to collapse
That is entirely different from what I thought it was and I have no idea what could be causing it. Do you get that ever when the dock is not connected?
berndblb said:
That is entirely different from what I thought it was and I have no idea what could be causing it. Do you get that ever when the dock is not connected?
Click to expand...
Click to collapse
No it cannot be replicated when the dock is not connected or when just touching the screen with or without the dock connected, it only does it on some areas of the system such as drawer and some apps if the mouse if left dormant for 8 seconds or so then moved.
I have done a factory reset and cold boot as requested by Asus, but the problem still persists as shown here in the new video
http://s9.photobucket.com/user/dougie175/media/Mobile Uploads/MOV_0020.mp4.html
dougie175 said:
No it cannot be replicated when the dock is not connected or when just touching the screen with or without the dock connected, it only does it on some areas of the system such as drawer and some apps if the mouse if left dormant for 8 seconds or so then moved.
I have done a factory reset and cold boot as requested by Asus, but the problem still persists as shown here in the new video
http://s9.photobucket.com/user/dougie175/media/Mobile Uploads/MOV_0020.mp4.html
Click to expand...
Click to collapse
Mine definitely doesn't do that. Try switching the cursor mode to gesture mode for me and see if that makes a difference. (I doubt it will but you never know)
Then go to the system settings, about and click the build number 7 times to enable developer mode. Then go into developer settings and look for force GPU rendering and disable hardware overlays. Check both. Reboot - any difference?
Check the cables
When troubleshooting a screen flicker, I always check the cables first. Several TechRepublic members agree. Ian C B, Bruceb, Crjordan, and Aqmike all suggested checking the video and monitor power cables before doing anything else. Ian C B reminds us to confirm that the cables are screwed in tightly and to replace the cables with new ones to see if the problem persists.
"The color changes are almost always a faulty wire in the cable," Crjordan said. "Try working the cable back and forth near both connectors. If this causes the color change, you could have a broken wire in the cable, or a loose pin in one of the connectors. Make sure the cable is out of the way (from feet, hands, and other objects). You may also try zip-tying it to itself or another stable object until you can replace either the cable or the monitor."
Check the environment
If a cable isn't the culprit, then the user's workspace should be next on your hit list. Monitors are notoriously sensitive to magnetic fields. Speakers, florescent lights, fans, cell phones, radios, and any other electrical device can cause a wide range of monitor problems. (See Figure A.) "Check what's around the [monitors]," Vilefileman said. "Cell phones are known to cause screen flickers, among other things, and plugging a radio or fan into the same receptacle can also cause screen flickers."
Maybe its like some kind of electrostatic interefereence in your environment more to do with the power being supplied to the device. Check cables. Etc. I think its interference or something.
sbdags said:
Mine definitely doesn't do that. Try switching the cursor mode to gesture mode for me and see if that makes a difference. (I doubt it will but you never know)
Then go to the system settings, about and click the build number 7 times to enable developer mode. Then go into developer settings and look for force GPU rendering and disable hardware overlays. Check both. Reboot - any difference?
Click to expand...
Click to collapse
I have noticed one other thing, it will not do the fault on first reboot, until the screen is locked, once unlocked it starts doing this fault
Gesture mode made no difference
Also done the developer options and they made no difference :crying:
sbdags said:
Mine definitely doesn't do that. Try switching the cursor mode to gesture mode for me and see if that makes a difference. (I doubt it will but you never know)
Then go to the system settings, about and click the build number 7 times to enable developer mode. Then go into developer settings and look for force GPU rendering and disable hardware overlays. Check both. Reboot - any difference?
Click to expand...
Click to collapse
I was wrong disabling hardware overlays does seem to resolve the issue?
However each time I reboot the option is un ticked that's why I thought it didn't do it
YayYouFixedIt said:
Check the cables
When troubleshooting a screen flicker, I always check the cables first. Several TechRepublic members agree. Ian C B, Bruceb, Crjordan, and Aqmike all suggested checking the video and monitor power cables before doing anything else. Ian C B reminds us to confirm that the cables are screwed in tightly and to replace the cables with new ones to see if the problem persists.
"The color changes are almost always a faulty wire in the cable," Crjordan said. "Try working the cable back and forth near both connectors. If this causes the color change, you could have a broken wire in the cable, or a loose pin in one of the connectors. Make sure the cable is out of the way (from feet, hands, and other objects). You may also try zip-tying it to itself or another stable object until you can replace either the cable or the monitor."
Check the environment
If a cable isn't the culprit, then the user's workspace should be next on your hit list. Monitors are notoriously sensitive to magnetic fields. Speakers, florescent lights, fans, cell phones, radios, and any other electrical device can cause a wide range of monitor problems. (See Figure A.) "Check what's around the [monitors]," Vilefileman said. "Cell phones are known to cause screen flickers, among other things, and plugging a radio or fan into the same receptacle can also cause screen flickers."
Maybe its like some kind of electrostatic interefereence in your environment more to do with the power being supplied to the device. Check cables. Etc. I think its interference or something.
Click to expand...
Click to collapse
Theres not really any cables I can check, I have checked the connection is pushed in correctly which it is.
I have just tried to replicate the error outside with my phone turned off inside the house so no chance of interference and the error was still present.
Don't think this is quite the issue as it only does it when moving the mouse after leaving it on certain apps for 8 seconds.
Thank you for the help though
Hey everyone,
I recently bought my new Honor Play.
First night I noticed something but didn't have time to investigate it any further.
When my device is laying on the table or bed I can't fully control the screen (top and bottom).
For example:
I want to bring my notification/settings area down and its not reacting (using cut-out, tried full bar ... same result).
Neither is the navigation button (using 1 but tried it with 3 ... same result).
The weird part is that it's happening only if the device is laying directly on something (table/bed/box/etc.).
I assumed that it could be something with gyroscope, but when the phone is horizontal in hands (tested with compass gyroscope 0°) everything is fine.
Ok i guessed it could be a few things, so here is the list of what I already tried:
fingerprint scrolldown notification X
smart & automatic rotation X
unwanted pocket call accept X
different notification bar settings X
different navigation bar settings X
different themes (original x usermade) X
different screen settings (FHD+/ HD+; small/medium/big text and view mode)
-
everything with/without protective case (product ID : 51992528)
I noticed it the first night (sunday) and since then i received two or three updates and it's still the same. Now I'm a bit worried it can be a HW thing.
OR
Could it be from a protective glass ? On second thought I dont think it is when its OK when not laying on smthing...
Thanks everyone for advice!
Have you removed the screen protector to verify that? I would advise you reset the phone after that. Don't forget to backup your data.
Is it one of those glove mode or pocket mode things?
pja1985430 said:
Have you removed the screen protector to verify that?
Click to expand...
Click to collapse
No I did not. I will when I buy a new one.
pja1985430 said:
I would advise you reset the phone after that. Don't forget to backup your data.
Click to expand...
Click to collapse
I'll try.
_a! said:
Is it one of those glove mode or pocket mode things?
Click to expand...
Click to collapse
Tried both. No effect.
Anybody with Honor Play who can try it?
I'm wondering if it's just me.
Sounds like a poor grounding of the display digitalizer. I’m afraid it’s a hardware defect. Mine has no problem detecting fingers when it’s on a table.
ByoBcz said:
Anybody with Honor Play who can try it?
I'm wondering if it's just me.
Click to expand...
Click to collapse
I can't reproduce your problem with my Honor Play. It's in a case, no screen protector though. It acts exactly the same whether it's lying down on a table or I'm holding it.
I have the same thing, bought a 15€ screen protector so I ain't peeling this off..
Gotta take a look from the settings. Will update on it soon.
Me too I am having this weird touch behavior and I don't know whether it's a hardware issue or a software one
This is a pretty big issue that blue up on the OnePlus forum and Reddit. People are experiencing ghost touches in apps. It's very easy to also experience this by opening cpu-z and letting it sit there for a minute or two not doing anything. It seems not everyone is experiencing this though. I have tested and do experience it. Do you?
Yup. Mine does with cpu-z open. what do we do?
BossJ said:
Yup. Mine does with cpu-z open. what do we do?
Click to expand...
Click to collapse
Depends if it's a hardware or software issue. Personally I already submitted a return request with OnePlus.
I just cancelled my order.. hopefully there is a software fix for you guys
This only happens to me on cpu-z and not in any other app. So I guess a future software update is gonna fix it.
Left it for a minute and didn't notice anything. On 9.5.3, bootloader unlocked and patched boot image with root.
I haven't experienced in a few days, it was happening a lot until I disabled pretty much all gestures.
I installed CPU-Z just to check on my International 8GB/256 model and I've got no issue with ghost touches. Not sure what is causing this for you all, but I do hope it is sorted out for you all.
When I turned off NFC the issue went away for me glad I don't use it whatsoever haha
Purest said:
I haven't experienced in a few days, it was happening a lot until I disabled pretty much all gestures.
Click to expand...
Click to collapse
Well that's not a solution disabling a useful feature to not have ghost touch issue.
On screen/off screen gesture are one of my favorite using it, so not a solution to me.
Simple will return the device.
I haven't order yet but i will next couple of days.
There's many reports across oneplus forum.
https://www.androidpolice.com/2019/...ros-are-suffering-phantom-touch-input-issues/
I left CPU-Z running for at least 10 mins.
And all is OK. Maybe it's a rouge program or something to do with the unlock\twrp?
The only way to be sure is to reset to stock and only install CPU-Z
Seems OnePlus using Novatek panels https://github.com/OnePlusOSS/andro...input/touchscreen/oneplus_touchscreen/Novatek
Poco F1 had same problems with Novatec and only way fix it was replacing whole panels, they tried to fix over updates but witout luck
romanB_SK said:
Seems OnePlus using Novatek panels https://github.com/OnePlusOSS/andro...input/touchscreen/oneplus_touchscreen/Novatek
Poco F1 had same problems with Novatec and only way fix it was replacing whole panels, they tried to fix over updates but witout luck
Click to expand...
Click to collapse
Wow that's seems real bummer.
Why would OP use Novatek display controller since had bad reputation and bad track record.
So the question is how do we know if all that units effected having all of the them Novatek display controller?
Or if there's another supplier for those units that don't have that issue.
Man things are getting much worse if it's hardware related and not software that I thought.
Sent from my V1821A using Tapatalk
It's extremely annoying it has happened to me a few times even when I was boasting about the new device to some colleagues at work. I thought it was me at first until then I read IRS an actual thing. I won't return it yet but I might if it's not sorted soon. It's extremely irritating.
Sent from my [device_name] using XDA-Developers Legacy app
Looks like ghost touches are related to NFC. Try with NFC turned off.
C3C076 said:
Looks like ghost touches are related to NFC. Try with NFC turned off.
Click to expand...
Click to collapse
Can confirm. My Ghost touches seize when NFC is disabled.
Sent from my GM1913 using Tapatalk
I've started yesterday experiencing that ghost touchs and also screen not responsive to touch in some panel sections (mostly the upper right zone). The phone didn't gave me that problem since I bought. I noticed when this happening, pulling the notification bar down to the tile settings makes that zone work again. Same thing happened when that random ghost touchs happens.
Didn't had any problems, don't use NFC, tried turning it on, ghost touches started appearing on cpuz, but not on other apps. As i don't use NFC i probably won't return the phone.
I just tried with CPU-Z and a few seconds after starting the app, the screen turns crazy tapping here and there. Can confirm also disabling NFC solves it.
Turning off nfc or not using gestures or not using cpuz app is just temporary solution.
And there's multiple reports that ghost issues happening other app too.
And we never know if thing get worse over time.
I'm afraid it's a more common issue than we thought but many users simple didn't notice it until now.
Oneplus should clearly take attention on that issue seriously and fix it ASAP.
Shouldn't be happening at all with any kind app or scenario of usage.
Sent from my V1821A using Tapatalk
Is anyone else having an issue with the always on display? Not a big deal but occasionally the AOD goes off and the tap to wake function doesn't work. Unlocking/locking the phone fixes it but it reoccurs again randomly through the day.
andrewd71 said:
Is anyone else having an issue with the always on display? Not a big deal but occasionally the AOD goes off and the tap to wake function doesn't work. Unlocking/locking the phone fixes it but it reoccurs again randomly through the day.
Click to expand...
Click to collapse
I was having the same issue when I had the edge notification app installed that makes the screen light up around the camera when you get a notification.
Uninstalled and no issues since
Tap to wake not working for me
Not sure if this is connected but in addition to the always on display/tap to wake issue when I'm in a phone call the screen will stay off even when I move the phone from my ear to hang up, see the keypad etc. Again I have to use the power button to wake the screen. A problem with the proximity sensor perhaps?
andrewd71 said:
Not sure if this is connected but in addition to the always on display/tap to wake issue when I'm in a phone call the screen will stay off even when I move the phone from my ear to hang up, see the keypad etc. Again I have to use the power button to wake the screen. A problem with the proximity sensor perhaps?
Click to expand...
Click to collapse
Do you have any notification or edge lighting apps installed?
Mdizzle1 said:
Do you have any notification or edge lighting apps installed?
Click to expand...
Click to collapse
No, I've not installed any apps like that.
I am having both the issue with always on display and the screen staying off during a call even when it's not up to my face. I don't have any edge display app installed. They happened right out of the box. Glad it's not just me.
czm said:
I am having both the issue with always on display and the screen staying off during a call even when it's not up to my face. I don't have any edge display app installed. They happened right out of the box. Glad it's not just me.
Click to expand...
Click to collapse
This is an odd one - are you using a case? I just had a case through the post this morning and now using the phone with the case the issues have stopped! I'll keep checking through the day but as of now all is good.
andrewd71 said:
This is an odd one - are you using a case? I just had a case through the post this morning and now using the phone with the case the issues have stopped! I'll keep checking through the day but as of now all is good.
Click to expand...
Click to collapse
Not using a case. It's sporadic. Tap to wake works fine for a while and then stops. The issue during calls is constant. Not major issues just niggles.
Not noticed any bugs with ambient display, but it has used 20 percent battery in 21hrs.
Seems a bit high to me, have just turned it off, not worth a 5th of my battery.
czm said:
I am having both the issue with always on display and the screen staying off during a call even when it's not up to my face. I don't have any edge display app installed. They happened right out of the box. Glad it's not just me.
Click to expand...
Click to collapse
Yeah I'm having both issues happen RANDOMLY as well. I'm HOPING Google will put out a fix for these two issues very soon.
Tried working with Google's Tech Support Team via chat earlier on the AOD issue. Tried a few things like clearing the cache of the launcher & restarting in Safe Mode then back to Normal Mode, and it seems to be doing it less but then it just did it again for a short time like an hour ago.
Using a case, no edge stuff, and also using Nova Launcher (though it happened in Pixel Launcher as well).
If anyone finds a fix for this, I would appreciate it too!
RockStar2005 said:
Yeah I'm having both issues happen RANDOMLY as well. I'm HOPING Google will put out a fix for these two issues very soon.
Tried working with Google's Tech Support Team via chat earlier on the AOD issue. Tried a few things like clearing the cache of the launcher & restarting in Safe Mode then back to Normal Mode, and it seems to be doing it less but then it just did it again for a short time like an hour ago.
Using a case, no edge stuff, and also using Nova Launcher (though it happened in Pixel Launcher as well).
If anyone finds a fix for this, I would appreciate it too!
Click to expand...
Click to collapse
Mine is fine for a while them randomly the tap-to-wake won't respond. I had also hoped that the OTA would have addressed, but maybe it is affecting far fewer users than other bugs.
czm said:
Mine is fine for a while them randomly the tap-to-wake won't respond. I had also hoped that the OTA would have addressed, but maybe it is affecting far fewer users than other bugs.
Click to expand...
Click to collapse
Yeah. Seems like more and more people are noticing and like me reporting these various issues to Google. So hopefully the next batch will include fixes for all this stuff.
I have same two problem with AOD, touch to wake up and screen off/on when calling.
DOMIN_ said:
I have same two problem with AOD, touch to wake up and screen off/on when calling.
Click to expand...
Click to collapse
I recommend you guys report these issues to Google so to increase the odds of them coming up with an OTA sooner than later. You can call them or chat with them via this link (as I did). Just scroll down to the bottom and choose your contact preference.
RockStar2005 said:
I recommend you guys report these issues to Google so to increase the odds of them coming up with an OTA sooner than later. You can call them or chat with them via this link (as I did). Just scroll down to the bottom and choose your contact preference.
Click to expand...
Click to collapse
On the pixel support forum they also recommend you report it via settings>about phone>send feedback about device. I think this way it also easily picks up the log files.
I believe the answer to all of your questions lies in a faulty proximity sensor. I was driving myself nuts with all of these issues exactly, and no app was the culprit because I factory reset and still had the issue. I'm going to post a link to a Reddit thread that I found that confirmed my suspicions. on Wednesday of this week I went back to Verizon and traded the phone in and now I have received a phone that works 100% as expected.
Reddit thread.
Good luck all, hope this helps.
czm said:
On the pixel support forum they also recommend you report it via settings>about phone>send feedback about device. I think this way it also easily picks up the log files.
Click to expand...
Click to collapse
Yeah I got an e-mail from the support guy to do that as well after he'd ask that I send a bug report. Just did it regarding AOD not staying on all the time and also.............I noticed that Hold for Me doesn't ALWAYS come up when calling businesses. Two examples include T-Mobile Customer Service & a local major hospital in Chicago. In most cases though, it does. Just an FYI. Not sure if this is something that they will fix, but I think it should come up all the time, or AT LEAST when you're calling an established business of ANY kind.
---------- Post added at 05:30 PM ---------- Previous post was at 05:26 PM ----------
Morpherios said:
I believe the answer to all of your questions lies in a faulty proximity sensor. I was driving myself nuts with all of these issues exactly, and no app was the culprit because I factory reset and still had the issue. I'm going to post a link to a Reddit thread that I found that confirmed my suspicions. on Wednesday of this week I went back to Verizon and traded the phone in and now I have received a phone that works 100% as expected.
Reddit thread.
Good luck all, hope this helps.
Click to expand...
Click to collapse
Very interesting!
I REALLY don't want to send mine back because I've spent so much time setting it up already (and my sister's too lol). I did some changes in the settings so I'll just cross my fingers and hope it works right.
Is there a way to recalibrate the proximity sensor?
RockStar2005 said:
Yeah I got an e-mail from the support guy to do that as well after he'd ask that I send a bug report. Just did it regarding AOD not staying on all the time and also.............I noticed that Hold for Me doesn't ALWAYS come up when calling businesses. Two examples include T-Mobile Customer Service & a local major hospital in Chicago. In most cases though, it does. Just an FYI. Not sure if this is something that they will fix, but I think it should come up all the time, or AT LEAST when you're calling an established business of ANY kind.
---------- Post added at 05:30 PM ---------- Previous post was at 05:26 PM ----------
Very interesting!
I REALLY don't want to send mine back because I've spent so much time setting it up already (and my sister's too lol). I did some changes in the settings so I'll just cross my fingers and hope it works right.
Is there a way to recalibrate the proximity sensor?
Click to expand...
Click to collapse
I don't believe it's a calibration issue. The way mine worked (or didn't as the case may be) was sporadic and seemed to almost be as if the sensor or module was loose? Inside the housing. Quite literally, jostling it around would make it work sometimes. Furthermore, if you download the app in that reddit thread, the proximity sensor tester Link Here, you can sort of gauge yourself if it's actually occurring. With mine, sometimes it would work by swiping my hand over the sensor, the color would change. Other times, the color stayed the same, and as the video showed ,I could put pressure on where the sensor was and change the color. But if it wasn't working, jostling the phone around would sometimes make it work and the color would change.
Additionally in the advanced test in that app, it is supposed to tell you how far away from the sensor an object is. On my (nonworking) phone, that number for distance would be pegged at 0 regardless of how far away my hand was. However if I put pressure on the sensor, it would jump to like 5 cm.
See if your phone is doing these things. If so, I would recommend you get it replaced, as it likely will not work properly otherwise. Verizon deemed this a hardware issue when I swapped phones. Also note that I factory reset twice, and one of those times I imported literally nothing when setting it up. So it wasn't a settings or app issue. I do believe there's a rash of faulty proximity sensors going on here.
Morpherios said:
I don't believe it's a calibration issue. The way mine worked (or didn't as the case may be) was sporadic and seemed to almost be as if the sensor or module was loose? Inside the housing. Quite literally, jostling it around would make it work sometimes. Furthermore, if you download the app in that reddit thread, the proximity sensor tester Link Here, you can sort of gauge yourself if it's actually occurring. With mine, sometimes it would work by swiping my hand over the sensor, the color would change. Other times, the color stayed the same, and as the video showed ,I could put pressure on where the sensor was and change the color. But if it wasn't working, jostling the phone around would sometimes make it work and the color would change.
Additionally in the advanced test in that app, it is supposed to tell you how far away from the sensor an object is. On my (nonworking) phone, that number for distance would be pegged at 0 regardless of how far away my hand was. However if I put pressure on the sensor, it would jump to like 5 cm.
See if your phone is doing these things. If so, I would recommend you get it replaced, as it likely will not work properly otherwise. Verizon deemed this a hardware issue when I swapped phones. Also note that I factory reset twice, and one of those times I imported literally nothing when setting it up. So it wasn't a settings or app issue. I do believe there's a rash of faulty proximity sensors going on here.
Click to expand...
Click to collapse
Hey Morpherios,
Ok.............downloaded that app and tried it out several times. It passed some of the time, but then I'd try it again a few minutes later and it would fail on both tests. Ughh!!
You think even though it passed a few times I still need to replace it?