Develop Bugs

Multitouch problems on the Note 10.1 (updated 03/05/2014)

[Update March 5th 2014]
Probably all 2014 Note 10.1's sold these past few months are suffering from one or more multitouch issues. From what we now know these appear to be software issues, effecting all current firmware versions for this device.
There are 2 known manifestations of this bug (or more likely: these bugs), described below. In both cases it seems to be a software issue because normally the 2014 Note 10.1 will work fine and the process of re-creating the issues is very clear and repeatable.
It looks like the multitouch driver becomes unstable if either one of the following occurs:
1. (Some models) You place (a part of) your hand on the screen for (at least) 5 seconds without moving it. This would usually happen when you are writing or drawing with the S-Pen.
2. (All models?) You place a finger (or several) on the screen for a longer time (close to 30 seconds) without moving it (them).
After either of these situations a 'defective unit' will show very erratic multitouch behaviour for a while.
It is easiest to see what happens if you use a so-called "Multitouch testing tool" (available Free on the Play Store). Such a tool typically shows all the screen areas where screen touches are detected by the device (in this case: the 2014 Note 10.1). Examples of such tools are: MultiTouch Test, MultiTouch Tester and YAMTT.
Erratic behaviour will usually start with all screen touches suddenly disappearing, meaning the device forgets that you have fingers (or part of your hand) on the screen. If you remove fingers (your hand) from the screen and again touch the screen several times a whole range of behaviour is seen: touches are detected and erroneously forgotten in quick succession. Sometimes so-called ghost-touches appear (meaning, the device will detect touches not anywhere close to where you are actually touching the screen).
This erratic behaviour will usually disappear when you leave the screen alone for a while, although several people (including me) have reported longer running issues (for instance during typing and editing using an on-screen keyboard). A surefire way to get rid of the issues is rebooting your device.
Since this is a "Note" device many people who's 2014 Note 10.1 suffers from these multitouch issues will encounter it while (or after!!) using the S-Pen. Others will notice issues while gaming or during typing/ editing.
The following clip by Kizune shows an example of what can happen while being inside a Multitouch testing app:
More videos you can find below (in post #16) and in the SwiftKey not working well on 2014 Note 10.1 topic, where the roots for starting this topic sprout from.
As of yet Samsung appears to be unaware of these issues, although several have approached them about this, returned their Note tablet, exchanged it or even handed one in for repairs. Hopefully we get this fixed soon.
Note 1: from early reports (in post #83) it looks like the new Note Pro 12.2 doesn't suffer from these issues.
Note 2: It is possible that a build up of static charge (through capacitance) is causing these issues, possibly caused by bad wiring (grounding) of the touch/ S-Pen detection circuitry.
Note 3: A new video has surfaced (in post #89) which shows 'noise' introduced in the touch-detection software while pinching/ zooming (see video below). It is unclear if this is related to the issues mentioned above.

i noticed this using the stock kb. i'm not a particulary fast typist on the screen but i'd get far too many lack of responses when typing on the split kb. standard qwerty was fine, but that have been b/c i'd type slower. i'm able to hit keys quicker on my gn8 without any misregistering of keystokes.
the fact there has been to OTA's in just a week is a sign they let this one out before it was ready. i still love the tablet though.

It happens to me too just like you see in the youtube video.

Just tried YAMTT and I am luckily not showing the issue seen in the video. Perhaps the second OTA solved it?
Sent from my Galaxy Note 10.1 via Tapatalk.

wingdo said:
Just tried YAMTT and I am luckily not showing the issue seen in the video. Perhaps the second OTA solved it.
Click to expand...
Click to collapse
Did you try the "whole hand" thing too? It would be super if Samsung solved things that quickly, but I feel a little aprehensive. We didn't get the recent updates yet in my area so I cannot see for myself.

wingdo said:
Just tried YAMTT and I am luckily not showing the issue seen in the video. Perhaps the second OTA solved it?
Sent from my Galaxy Note 10.1 via Tapatalk.
Click to expand...
Click to collapse
no, I took both OTA's Just before rooting.

wingdo said:
Just tried YAMTT and I am luckily not showing the issue seen in the video. Perhaps the second OTA solved it?
Sent from my Galaxy Note 10.1 via Tapatalk.
Click to expand...
Click to collapse
Same here. I tried a couple touch apps and all were fine. The YAMTT app just seemed buggy at times. but I could not replicate what the video showed on any of the apps and do not have problems in real world applications either.

atg284 said:
Same here. I tried a couple touch apps and all were fine. The YAMTT app just seemed buggy at times. but I could not replicate what the video showed on any of the apps and do not have problems in real world applications either.
Click to expand...
Click to collapse
Did you try the "whole hand" procedure too?
---
I changed the opening post because I feel many will be tempted to just try the youtube clip and not bother reading anything else. Hopefully we won't have too many people voting before properly taking all steps because you cannot change your vote once you voted (an xda forum limitation).

Ettepetje said:
Did you try the "whole hand" procedure too?
---
I changed the opening post because I feel many will be tempted to just try the youtube clip and not bother reading anything else. Hopefully we won't have too many people voting before properly taking all steps because you cannot change your vote once you voted (an xda forum limitation).
Click to expand...
Click to collapse
I did what the person was doing in the video and could not replicate what was happening on his. I also placed my whole had on it and put all ten fingers on it. No bugs. I am on the second update. Build number ending in AMJ4
Edit: the YAMTT app seems buggy because the other touch apps don't go crazy when all ten fingers on on it. But I could not replicate what YAMTT app was doing to the one in the video.

atg284 said:
I did what the person was doing in the video and could not replicate what was happening on his. I also placed my whole had on it and put all ten fingers on it. No bugs. I am on the second update. Build number ending in AMJ4
Click to expand...
Click to collapse
Did you place your whole hand on the screen of the 2014 Note 10.1 for several seconds, without moving it? Did you put your fingers on the screen afterwards? The video is not meant for reproducing the bug, the written procedure is. The video just shows what happens when you write, as the bug has already be introduced before the start of the clip.
Edit: The YAMTT app is not important, puting your hand for several sevonds on the scyeen IS. This creates what goes on afterwards. You can repeat it in any of the Multitouch testing apps, just place your hand (or part of it) on the screen for a while and see in the MT app what happens.

Ettepetje said:
Did you place your whole hand on the screen of the 2014 Note 10.1 for several seconds, without moving it? Did you put your fingers on the screen afterwards? The video is not meant for reproducing the bug, the written procedure is. The video just shows what happens when you write, as the bug has already be introduced before the start of the clip.
Edit: The YAMTT app is not important, puting your hand for several sevonds on the scyeen IS. This creates what goes on afterwards. You can repeat it in any of the Multitouch testing apps, just place your hand (or part of it) on the screen for a while and see in the MT app what happens.
Click to expand...
Click to collapse
Ok, I see. So when I put my whole hand/palm on it for 2-5 seconds then I try to put all ten it starts to "wig out" a bit but it still registers all ten its just sporatic. Also it seems to only have a problem with like 7 or more after because I can put many fingers on it before it wigs out. I still don't see a real world issue on mine even after I do the full hand thing.
Side note once I exit out the app the ten fingers on it are fine again.
What problems are people seeing due to this?

atg284 said:
Ok, I see. So when I put my whole hand/palm on it for 2-5 seconds then I try to put all ten it starts to "wig out" a bit but it still registers all ten its just sporatic. Also it seems to only have a problem with like 7 or more after because I can put many fingers on it before it wigs out. I still don't see a real world issue on mine even after I do the full hand thing.
Side note once I exit out the app the ten fingers on it are fine again.
What problems are people seeing due to this?
Click to expand...
Click to collapse
As far as I am aware the problem doesn't disappear as simple as that. It would be great if there was a way to get rid of it without rebooting.
You could get any type of interface problem afterwards, as even one finger touch can give ghost finger touches. I noticed things being wrong in SwiftKey before finding out what it was.

Ettepetje said:
As far as I am aware the problem doesn't disappear as simple as that. It would be great if there was a way to get rid of it without rebooting.
You could get any type of interface problem afterwards, as even one finger touch can give ghost finger touches. I noticed things being wrong in SwiftKey before finding out what it was.
Click to expand...
Click to collapse
Oh I don't have that at all. no ghost finger touches ever. I have not rebooted over the period of testing either today. Are you fully updated?
I will keep checking this over time though.

Ettepetje said:
The video is not meant for reproducing the bug, the written procedure is. The video just shows what happens when you write, as the bug has already be introduced before the start of the clip.
Click to expand...
Click to collapse
Well, actually the method shown in the video is the "previous version" of the current one. I could produce the bug with that method very often right after booting. But the "whole hand" method is more reliable.
What problems are people seeing due to this?
Click to expand...
Click to collapse
1. When taking notes at the university, I sometimes move the viewport in S Note using the zoom gesture without the zooming motion. And as you can see, putting my hand on the screen as shown in the video triggers the problem for me, so doing that gesture is almost impossible for me. I know there are scrollbars, but they move the viewport too slowly (but of course I use them when I notice the multitouch issues are occurring).
2. Same as above, but when drawing in Sketchbook or ArtFlow. And here it's extremely annoying because there are no scrollbars I could use.
3. A small annoyance compared to the others but: When I play Carmageddon, the multitouch issues get triggered once in a while. And then I can only either control the car, or accelerate or break, but not both simultaneously. Sometimes my touches aren't even registered at all. I often get destroyed due to the multitouch issues.

Kizune said:
Well, actually the method shown in the video is the "previous version" of the current one. I could produce the bug with that method very often right after booting. But the "whole hand" method is more reliable.
Click to expand...
Click to collapse
I changed the description in the opening post. I never had it happen like that yet. Did you know you get the errors just by holding the side of your hand on the screen for a bit? I thought that was how you discovered this. Doing that looks very similar to how you are holding your hand in the videoclip.
Did you find another way to get rid of the issues besides resetting your Note?
Btw: With Carmageddon, if you are high enough level and want to kill pedestrians, not having control means your opponents die crashing into you, ending the race before you finish all pedestrians.

Ettepetje said:
Did you know you get the errors just by holding the side of your hand on the screen for a bit? I thought that was how you discovered this. Doing that looks very similar to how you are holding your hand in the videoclip.
Click to expand...
Click to collapse
Exactly, I noticed it while taking notes. And then I made this my test method to replicate the error.
Anyway, here are some videos. The first shows a real-life situation in S Note with that problem, the second and third show that the problem also occurs in other multitouch test apps (yes, I'm looking at you, atg284 ).
And to make it more "real-world friendly", I used my old "provocation method" because that's how you put your hand on the screen while drawing and writing.
Btw: With Carmageddon, if you are high enough level and want to kill pedestrians, not having control means your opponents die crashing into you, ending the race before you finish all pedestrians.
Click to expand...
Click to collapse
Yup. And I even got that tank-like bonus police car, so they die just by touching my car tank.

I do stand corrected I can reproduce this issue on the new Note, old Note is fine and dandy.
Sent from my Galaxy Note 10.1 via Tapatalk.

wingdo said:
I do stand corrected I can reproduce this issue on the new Note, old Note is fine and dandy.
Click to expand...
Click to collapse
Did it take longer to get the erratic behavior like you said in pm? I'm trying to get the description in the opening post right, since we got 4 people now who claim they don't have it. I think the score should be 100%, and just included the Poll so that people at Samsung would quickly realise how big the impact is.

I can duplicate this.. just didn't figure how to repeat consistently until now..
First noticed when trying to pinch zoom in adobe reader .. you get very jerky redraw back and forth.. this could be app specific , but i haven't seen this on other devices
Sent from my SM-P600 using xda app-developers app

I'm also experiencing this. It's a terrible issue when taking notes in class.
Can we expect a fix?

Satisfaction with Nougat update

Looks like today majority of Europe is getting Nougat update on HTC 10.
How is update working for you, regarding bugs and stability? I'm kinda scared of updating it, since the Nougat update ruined my Oneplus 3.

just do it. its great

I actually got my new HTC 10 yesterday, and Nougat today, in the Netherlands.
So far no issues at all.

Does it have any affect on battery life?

daEXk said:
Does it have any affect on battery life?
Click to expand...
Click to collapse
for me battery life is a little better on N

I think it's a good improvement, but I have had the occasional issue with screen touch sensitivity, for example, on page scrolling - sometimes if I scroll and hold my finger still, the page flickers up and down, and sometimes it scrolls to the start or end hyperfast. Also when using Swype, it sometimes completely misreads the initial finger movements, inserting more characters than I've passed over . These don't happen often enough to be a problem, but they didn't happen before and make me wonder if the screen sensitivity has been tweaked up a bit in some way.

Have been on N for a good 3 weeks already? Generally, the phone is performing admirably, day to day performance is faster, snappier.
However, with all the improvements being made, there are still some bugs that have yet to be quashed, mainly the in built camera app.
Right now, with the camera in Pro mode, whenever I am adjusting more than 1 variable ie; shutter speed & iso, the tap to focus refuse vehemently to work.. Also, live preview for shutter speed never goes past 3-5 seconds. In the past, when I max out the shutter speed (@16 secs) I will most definitely get a blown out image, for now, 5 seconds onwards doesnt seem to make any difference, until you actually take a shot... As a frequent user of the phone's awesome camera to take low lit shots, this is rather disastrous.
My phone is a Taiwan set, so I dunno if these issues are exclusive. Do chime in if you encounter similar problems with the camera app too!
PS: am using another photography app that does manual and RAW (manual camera) works pretty sweet!

dlorde said:
I think it's a good improvement, but I have had the occasional issue with screen touch sensitivity, for example, on page scrolling - sometimes if I scroll and hold my finger still, the page flickers up and down, and sometimes it scrolls to the start or end hyperfast. Also when using Swype, it sometimes completely misreads the initial finger movements, inserting more characters than I've passed over . These don't happen often enough to be a problem, but they didn't happen before and make me wonder if the screen sensitivity has been tweaked up a bit in some way.
Click to expand...
Click to collapse
exactly. that page flickers up and down. Scrolling in Stock rom is not as smooth as it is in LOS rom. This issue alone makes me sad every time I use my phone. HTC why you do this. No idea if it is good in MM rom. After seeing your post.. I would downgrade to 6.0 just to see how it works.

It's good, definitely more efficient but you'll not have xposed and from what I've read the likelihood is Slim that well get it, I think it's because the base has changed so much and continues to change meaning it has to be modified greatly, this is the only thing I miss. Certain devs also haven't updated their apps. For example Kodi wasn't updated, might be now but wasn't a little while ago.
Personally I think the trade off for performance and stability is worth it.. I wouldn't go back. Plus with the pixel launcher and a decent theme the phone really flies.

So far so good
No problems here, updated on Tuesday.

Upgrade to Nougat already? Hows it working for you?

For those who have upgraded already, how did the upgrade process go and how are you liking it so far?
This is a big upgrade and I'm nervous about pulling the trigger until this is vetted out a bit.
Chris

The process went well. I had to play with the display resolution and zoom to get things looking right. I had to re install my theme store theme to get it back. Other than that, it runs great. Only a few apps not compatible with n. But I have like 400 apps. So not bad! Oh yes, I did need a couple of reboots too.

Sweet! Well... having to go five steps back first was a PITA but when finished (and thank God for the Samsung Cloud Backup System - I had just done a backup three days before this project and it saved my arse!) Once I finished the AT&T OTA of QB2, I did a Restore from the Samsung Cloud and the phone looked EXACTLY like it had with Nougat PL4! Desktop, Apps, (most) settings... awesome!

Going good, process went smooth. I'd just say plug up and stay plugged during upgrade

Just did the upgrade. I have to say guys, this was BY FAR the smoothest stock upgrade I've ever experienced from Samsung. They did a nice job on this.

I'm just running into the issue of UI Lag. The update went smooth enough though. I will also say I am having issue with video playback in chrome if I flip to fullscreen then the ability to control the video is gone and i cant minimize it i have to hit the home key to get out of the video.

I just finished installing QB2. Everything works smoothly except one annoying bug. The Activity Zone app launch not in full screen. It's like 70% of the screen. I tried to change the display resolution but the same.
Anyone having the same issue?

snugroho3 said:
I just finished installing QB2. Everything works smoothly except one annoying bug. The Activity Zone app launch not in full screen. It's like 70% of the screen. I tried to change the display resolution but the same.
Anyone having the same issue?
Click to expand...
Click to collapse
No, mine launches full screen!
---------- Post added at 03:46 PM ---------- Previous post was at 03:45 PM ----------
CFoote said:
Just did the upgrade. I have to say guys, this was BY FAR the smoothest stock upgrade I've ever experienced from Samsung. They did a nice job on this.
Click to expand...
Click to collapse
DITTO!

jimd1050 said:
No, mine launches full screen!
---------- Post added at 03:46 PM ---------- Previous post was at 03:45 PM ----------
DITTO!
Click to expand...
Click to collapse
Yes, it launch in full screen but the content of the app is not. Please see attached picture. Do you have the same?
It was full screen in marshmallow

That is quite strange, my Activity Zone is full screen, do you have your Zoom function under "Display" set to small?

Upgrade went smooth , i did it manually and not OTA , all working good with good battery life.
What i did is as follows :
1- Odin the PI2 as a base line
2- Then via recovery from the device I used "update from SD card" and upgraded to PK2
3- Then i did it again via recovery from the device I used "update from SD card" and upgraded to QB2
Download the needed files from the following thread
https://forum.xda-developers.com/s7-active/how-to/s7-active-sm-g891a-ota-updates-firmware-t3540866

I updated to the BQB2 build via OTA about a week after it became available. I'm generally pleased with it, but there are a few things here and there that make me think that perhaps I'm due for a factory reset and start over.
Battery life is slightly down for me, which doesn't match up with reports I'm hearing from others. It's not much lower, but it's noticeable.
UI seems to be slightly more 'laggy'. Reduced the animation scales in the dev options to compensate. Maybe because I was running 'Good Lock' when the update happened?
Seems like wifi connection is not 100% stable. I see the notification bar 'flicker' from time to time, and it keeps re-posting the notification about what network I'm connected to.
Seems to get warmer while charging wirelessly, to the point that it pauses the wireless charging. But, this is in a cradle in my car, with Waze running, and it's warmer than it had been for a few months so not really sure if the update is involved in this or not.
Probably one or two other smaller things that I'm not thinking of at the moment. Obviously they weren't showstoppers, since I can't recall right now.
I like that they included the mobile hotspot toggle again (finally!), but they still don't have a 'mobile data' one. System UI Tuner is still gone, although I've read some people think that's the case with Nougat in general, so not sure.
All that being said, it updated to the BQC2 build today. The wifi thing seems to be resolved, despite this being only a 'security update'. I'll let it shake out for a few days or so and see if I still think it's worthwhile to start all over.

Went smooth for me, took literally less then 2 minutes.
All my apps/settings are working flawlessly and I experienced no issues thus far.

I updated to Nougat since it was released and I can't say I'm happy. Battery looks slightly worse and at least 1 or 2 twice a week my phone slows down getting almost unresponsive. I have to restart it.
That never happened with Marshmallow. I'll try it for one more month and if not I will go back to Marshmallow. Is that still possible?

That is a good question. I know that with small version upgrades the phone keeps the original version stored for a full wipe, but on a big OS upgrade I am not sure. Hopefully someone will know. I want to say yes it can be done.

Im on QD4, loving Noguat at how quick it is. But, i hate how all the menus and settings are all bunched and i have use search to find basic things.

I actually am having some issues with my s7 active I installed the 7.0 update a few months back and never looked back because the 7.0 stock rooms great no issues except recently last week's my phone started rebooting on its own . I though no biggie cause it did every once in a while , but now it has greatly increased . What happen was it froze on Facebook messenger app when I was trying to reply to a message and would not unfreeze so I had too force restart it that is when the problems really begun. The moment I force restarted it and it rebooted and i got into hone screen i keep getting notifications that apps were crashing over and over and the phone decided to restart on its own and keep doing the same thing . So I was like wtf maybe it's a app or something so I decided to do a factory reset and clear cache and rebooted the phone looked like that fixed the problem for a whole 2 minutes then the crashing of apps and random restarts . I was tired so.i was like ok I just turned the phone off and notice that it was kinda warm and decided to go to bed and mess with it tomorrow . So when I woke up I booted the phone up and it was acting normal no crashing or anything no reboots but after 2 hours it randomly started rebooting and sometimes the apps crash bit currently the phone is working but i get random freezes and reboots all day . I have tried searching for a solution but no luck. Some people claim its a app but when I have no apps Installed and it still does it its not a app problem . Some people say it could be the mother board flus faulting out or bad battery can't send it in for repair cause I bought the phone off eBay. Is anyone else having these issues and know of a fix maybe thanks sorry for the long post.

Upgraded to BQB2 a week ago, I am very happy with everything, it's smoother, faster and manages RAM better (well I was Rooted on 6.0.1 so it was laggy) all my apps work perfectly and I've disabled many things with Package Disabler Pro, I've been testing running music, google maps chrome, whatsapp, messenger, face all at the same time, very smooth BUT I must say it does drain battery much faster than before.
Now my phone wont make it through the day, it even drains on standby, I've already flashed 7.0 twice and wiped cache, I'm still, thinking if I will keep this or go back to 6.
Yesterday alone, my battery went from 89% at 1:30am to 52% at 10:30am, only on standby. When I check Battery use my com.android.systemui is the one eating up most of it, I even set my resolution low to HD. If anybody has a solution, any help would surely be appreciated, I don't wanna go back to Marshmellow, but if I must......

Upgraded and everything was fine apparently, then I saw the huge battery drain, tried averything I found and decided to go back to marshmallow.

KGB7 said:
i hate how all the menus and settings are all bunched
Click to expand...
Click to collapse
Can you please provide screen shots?
There are 2 more ups after QD4 (side load), I need to know if I should be prepared to go that far if I proceed with QD4.

Android 8.1 slow fingerprint reader

Anyone else notice or experience a slower fingerprint unlock after applying the 8.1 OTA update? A VERY noticeable difference in unlocking speed after the update.

1up1up said:
Anyone else notice or experience a slower fingerprint unlock after applying the 8.1 OTA update? A VERY noticeable difference in unlocking speed after the update.
Click to expand...
Click to collapse
No issue here mate, still as fast as it was before on 8.0.0. Might wanna try another reboot to see if it fixes your issue. You could then always try a factory reset as well.

I just downloaded and reinstalled the 8.1 factory image. Went through and setup phone from today's backup and added fingerprints. While the phone was finishing downloading apps from backup, the fingerprint unlock was fast and normal as usual. After apps updated and restore finished, I restarted the phone. Immediately, the slow fingerprint unlock returned. I have very few apps and this wasn't an issue until after I applied the 8.1 OTA side load before the initial posting of this thread. Additional testing of the speed by pressing the power button then unlocking with fingerprint reader yields inconsistent unlock speeds. At this point, I do not want to say that maybe it's because of a particular app that is installed on the phone, but rather it's possibly a problem with 8.1.
Any thoughts?

To put it into perspective, the fingerprint unlock under normal speed feels almost "too sensitive" because it's so fast. Now it registers my fingerprint touch right away but is followed by a slight pause/stutter before unlocking the screen.

1up1up said:
To put it into perspective, the fingerprint unlock under normal speed feels almost "too sensitive" because it's so fast. Now it registers my fingerprint touch right away but is followed by a slight pause/stutter before unlocking the screen.
Click to expand...
Click to collapse
I have this exactly

I too am facing similar problems. My phone on 8.1 takes about 1.5s to unlock while it only took <1s on 8.0. A workaround I took was to have always on display activated. And I ain't a fan of the always on display.

Yup. First thing I noticed was this delay between when the fingerprint is actually recognized (vibrate), until I actually get visual on the screen. Around a second or more

I actually had this issue on 8.1 DP2. But since doing a fresh install of the 8.1 official release, my finger print reader is just as fast as 8.0. Maybe try a new fresh install.

SOLIDFND said:
I too am facing similar problems. My phone on 8.1 takes about 1.5s to unlock while it only took <1s on 8.0. A workaround I took was to have always on display activated. And I ain't a fan of the always on display.
Click to expand...
Click to collapse
I too, am not a fan of the "Always On" display but can confirm that this does fix the problem. Thanks for sharing your finding.

sn0warmy said:
I actually had this issue on 8.1 DP2. But since doing a fresh install of the 8.1 official release, my finger print reader is just as fast as 8.0. Maybe try a new fresh install.
Click to expand...
Click to collapse
Sadly, I actually went through a fresh 8.1 install but fingerprint scanner is still slow with ambient display off. Off to reinstalling my apps...

I found hit super hit or miss. When I flashed my rma phone to dp2 it was slow to unlock. When I flashed 8.1 final it was fast again. I had to flash 8.1 final again but this time the phone was slow to unlock. I got my new device flashed 8.1 on and it is thankfully unlocking quickly. I wish you all luck

I submitted it to Google under DP2 and it has been deferred to a future build... maybe re-submit under the final 8.1 as well??
https://issuetracker.google.com/issues/69984153

Today I also noticed a random "static pop" noise coming from the phone while Chrome browser was open. It was quite distinct and loud and happened twice.

SOLIDFND said:
Sadly, I actually went through a fresh 8.1 install but fingerprint scanner is still slow with ambient display off. Off to reinstalling my apps...
Click to expand...
Click to collapse
Same problem, gets fixed with always on display but if the screen is not on in between the seconds of pressing the power button and ambient display kicks in then the problem is still there. Also tried deleting the fingerprints and redoing the fingerprint initiation, but it did not help. The sensor registers the fingerprint by vibrating but screen gets on only after a second or more. sometimes though it is instantaneous. another problem for Google to fix I guess in next month update.

1up1up said:
To put it into perspective, the fingerprint unlock under normal speed feels almost "too sensitive" because it's so fast. Now it registers my fingerprint touch right away but is followed by a slight pause/stutter before unlocking the screen.
Click to expand...
Click to collapse
Same issue here since updated to 8.1
The fingerprint is recognized quickly (you fell the short vibration) but the screen turns on with a delay of about a second.
I have the same issue when I just press the Powerbutton - it also takes about a second until screen turns on.
Guys, I'm so disappointed with my Pixel 2 XL. Never had so many issues with a stock firmware phone.

Been running 8.1 through the beta for awhile now and haven't had any of these issues. Not sure if I'm just lucky or what but it's been humming along just fine. Just installed the 8.1 official over the 8.1 beta and haven't noticed anything as of yet. Will pay attention to see if I notice anything being slower.

I am also seeing the issue after updating to 8.1. It takes about 2 seconds for the screen to appear. AOD does make it faster but I can deal with it and hopefully google fixes it soon

I searched he'd the issue on google- obviously because I HAVE IT TOO. This is infuriating. This is major functionality. after 8.1 the finger print reader is slow AF. It feel like my old galaxy s4 that i just came away from when i would swipe to unlock it. How many times do we unlock these things a day? We just went from the fastest unlocking phone to the slowest. Why is this effed up? I'm pissed.
We have ppl whining about the freaking hamburger emoji having the cheese on the bottom and the wrong foam in the beer mug, meanwhile it takes forever to get into the phone to do anything much less get to the Emojis. How does BASIC functionality go BACKWARDS with an update?
What's even more infuriating is I can't go back to 8.0!!! Google doesn't allow it do they? I am coming to this phone off a Galaxy s4. One of the big benefits of the pixel family is the "fast updates."I saw someone argue that this isn't necessarily a plus sometimes these new Android versions slow a phone down, and it's done. Sometimes, like in this case, bugs are introduced. The very first update I took on this phone largely argues his point.
Another thing I'm noticing is the battery life seems to be dropping much faster. I'm wondering if it's the flash kernel 2.0 I installed though.
I will be filing a complaint on the link someone so kindly posted above (thank you), and I will be going into the chat option through the help menu on my phone to file a complaint there.
EDIT: it also seems like Google assistant isn't working now either. "Ok Google" brings her up. The mic registers my talking, but no results are displayed.
EDIT 2: I also forgot to mention that along with the slow unlock the swipe function on the finger print reader has been altered. Smiling up and down to toggle the notification drawer is very inconsistent and buggy. I have the finger print quick action app installed. I had a single tap set up to lock the screen. I had my finger print reader un/locking the phone and toggling the notification drawer. While the notification drawer has always been a little buggy, it was VERY functional and very acceptable. Something has changed on the reader so it is having a harder time differentiating between the different movements. Now it usually registers a swipe as a tap and the screen locks. I expected this to happen when I first downloaded the app on 8.0, but I was pleasantly surprised when everything worked through the sensor. Now I am very disappointed. The issue is NOT constant. It comes and goes. Idk why it does that. I'll be seeing if I can figure out why. I will NOT be activating the always on screen as a means to circumvent this issue. I don't want burn in. I've been concerned with that issue associated with always on before the pixel showed up.

jbarcus81 said:
I submitted it to Google under DP2 and it has been deferred to a future build... maybe re-submit under the final 8.1 as well??
https://issuetracker.google.com/issues/69984153
Click to expand...
Click to collapse
I want to jump on board and file an issue too. What do I select the issue as?it's not a developer preview. Is it android system issue? Framework?

fearfighters said:
I have this exactly
Click to expand...
Click to collapse
-deleted
---------- Post added at 06:08 PM ---------- Previous post was at 06:02 PM ----------
1up1up said:
To put it into perspective, the fingerprint unlock under normal speed feels almost "too sensitive" because it's so fast. Now it registers my fingerprint touch right away but is followed by a slight pause/stutter before unlocking the screen.
Click to expand...
Click to collapse
Same here

Question A13, another "Am I the only one?" Thread!

Ok all, I'm getting quite frustrated with my P6P. Was on A12 and sideloaded the OTA for 13 Beta 4.1. I didn't want to lose any data but also didn't want to enroll in the beta program which would have pushed the OTA anyway.
Beta was working but definitely noticed a hit to battery life at first and some weird things like running warmer, phone being warm just sitting on the pixel stand fully charged, just generally not feeling right. The good news was, it seemed to have gotten a little better over the next few days of use but still not great so when I saw stable A13 released last week, instead of going back to 12, I committed to using the Android flash tool and fully flashing A13.
After flash, I chose to restore my Google One / Drive backup and omg the battery life was completely abysmal and running hot. We are talking losing 20% per hour of light usage, standby was losing 10%+ per hour and wasn't going into deep sleep at all. I thought at first it was my Galaxy Watch4 and the Samsung health app causing the majority of the issues but when I disabled "activity tracking" on the app, it didn't fully resolve the issues.
Other issues include: taking phone out of my pocket, screen sometimes doesn't wake up (I remember this was an issue with A12 but G eventually acknowledged and fixed but I guess it's back), connected via Bluetooth to my car (no Android auto) the ring tone is no longer playing when I get a call, generally feeling not as smooth, weird system usages showing up in accubattery and the Android battery manager as using good chunks of battery, etc.
At this point I got another idea: reflash A13 but don't restore from backup (which I hate doing because then I have to go through every single setting to find stuff I changed and set it again both in the system and on apps). It seems like that helped a little with stand by battery drain but still seems to be draining at a higher level while in use. The issue of screen not waking up sometimes is still present and now, I just saw this morning that I tap on the Google Play System Updates within the security menu and it does nothing. I was able to get into it yesterday morning and it found an update (still says July 1 though) but I didn't reboot to complete it until this morning. Now I can't get into it anymore at all. I also found some weird folders in my DCIM folder and another one that referenced icloud and iphone transfers but I've never been an iphone user.
I'm so frustrated with this phone lately and it seems like no matter what I do, I cannot get it to work right with multiple little things as well as battery drain.
Am I the only one? And if not, anyone have any ideas on how to fix my issues? Is it time to contact Google for an RMA? I was one of the launch day orders so I don't know if my specific hardware is the issue. I am now locked in to 13 bc of the bootloader thing, I didn't manually flash the BL to both slots, only used official flash tool which you'd think of this was a critical thing, Google would do that with the flash tool but I guess they can't get their left hand to recognize what the right hand is doing.
Just typing this post on Chrome browser for 10 mins, burned through 4% battery.

You're not the only one...
https://www.reddit.com/r/GooglePixel/comments/wddk1s

nomisunrider said:
You're not the only one...
Click to expand...
Click to collapse
Thanks for that reddit article but that's not exactly answering my questions. Yes I know I'm not the only one who's had battery issues and I've gone through all those steps up to and including reflashing cleanly and wiping.
What about the other stuff I'm having issues with? Anybody else experience any of those issues? Is there anyone on 13 stable NOT having some issues with battery or other oddities?
Essentially I'm debating on wiping again and/or reloading the OS again but if others are having the same or similar issues then it may just be Google being Google and releasing a buggy build (yet again).

Side note, I also just got a notification that Google One backup is currently running and to tap for more info but yet, I don't have it plugged it nor is the phone idle. It is on wifi though but I tapped the notification and nothing was happening. It said the last backup was at 3:37am. Also, I am now down another 10% of battery since posting this with barely any usage.

Hi, I've been on Android 13 Stable for the past 7+ days, and haven't had any problems.
The only suggestion I have is a start completely fresh type, but there's no guarantee it'll fix anything. Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own).
^ It's fixed things for many users, including myself, that nothing else including the factory image would fix, but for me, that was six months ago so obviously on Android 12, and it was a different issue than any that you're describing.

jrg67 said:
Is there anyone on 13 stable NOT having some issues with battery or other oddities?
Click to expand...
Click to collapse
I've had no issues with 13 but didn't have any on 12 either. Day one phone too.

roirraW edor ehT said:
Hi, I've been on Android 13 Stable for the past 7+ days, and haven't had any problems.
The only suggestion I have is a start completely fresh type, but there's no guarantee it'll fix anything. Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own).
^ It's fixed things for many users, including myself, that nothing else including the factory image would fix, but for me, that was six months ago so obviously on Android 12, and it was a different issue than any that you're describing.
Click to expand...
Click to collapse
I did what I thought was starting fresh the last time around (Sunday). Used the official flash tool and didn't restore anything from backup. All I did was add my Gmail accounts and then manually downloaded every app I use and then tried to set all the settings again in both system and apps to how I like them. Is there something I'm missing? Is there a difference between the pixel repair tool and the Android flash tool? What about the settings that are flash tool? I have them set to wipe, lock, and force flash everything. Not sure if that exists on pixel repair tool. I've also noticed a fairly large reduction in size of the backup that occured last night with the apps section showing only 44 apps at about 11.7MB in size when my previous backup was 60 apps at about 48.2MB. I'm thinking of just wiping/reflashing again for the 3rd time but restoring from backup this time since it really didn't make much difference.
How about the Google play system up bug thing? Can someone tap on it and see if it comes up checking for an update or if it does nothing like me. And when I say nothing, just the menu option to tap on just lights up but doesn't open anything. How about the issue with the screen not waking up if taken out of your pocket?

For what it's worth, I haven't started from scratch since I accidentally did last December (after originally setting my phone up in late October or in November). I used the Android 13 factory image over top of my existing install without wiping.
I'm under the impression that yes, there is a difference between the Pixel Repair Tool and the Android Flash Tool, but I've never actually used the Pixel Repair Tool. I know the first several months, at least, the Pixel Repair Tool hadn't yet been updated to work with the Pixel 6 Pro. It may have been updated since then, I just don't know for sure.
When I have wiped/factory reset in the past six years (starting with my Pixel 1), I always restore all or almost all data from Google's backup. I do have Swift Backup do automatic nightly backups as well, but I only restore data (through Swift Backup) for the apps that I really need to - definitely not very many.
Your settings for the Android Flash Tool sound fine.
Is the "Google Play System Up(date) bug where clicking on it doesn't do anything? If so, it doesn't do anything for me, either. Mine doesn't even light up, but I have dark mode on, plus using Pitch Black theme from AOSP mods.
I rarely have my phone in my pocket, so it probably just doesn't come up often enough for me to have noticed, so I can't confirm one way or the other.

Well, I found an answer to the Play System Updates "bug". We are not the only ones, road warrior! https://www.google.com/amp/s/9to5google.com/2022/08/20/check-google-play-system-updates-pixel/amp/

jrg67 said:
Well, I found an answer to the Play System Updates "bug". We are not the only ones, road warrior! https://www.google.com/amp/s/9to5google.com/2022/08/20/check-google-play-system-updates-pixel/amp/
Click to expand...
Click to collapse
Cool, thanks for sharing the news! I hadn't bothered checking manually in very many months, possibly since late last year or very early this year.

Now, on to the other stuff like no more ring sound over Bluetooth in my car, the screen not waking sometimes, terrible battery life, etc etc. Boy do I love this time of year when new the OS launches, screws up many phones and makes people trade them in for the next version. P7P here I come!

roirraW edor ehT said:
Cool, thanks for sharing the news! I hadn't bothered checking manually in very many months, possibly since late last year or very early this year.
Click to expand...
Click to collapse
jrg67 said:
Well, I found an answer to the Play System Updates "bug". We are not the only ones, road warrior! https://www.google.com/amp/s/9to5google.com/2022/08/20/check-google-play-system-updates-pixel/amp/
Click to expand...
Click to collapse
Google Play Store v31.9.20-21 is rolling out and will fix that Play System Updates "bug".

jrg67 said:
Now, on to the other stuff like no more ring sound over Bluetooth in my car, the screen not waking sometimes, terrible battery life, etc etc. Boy do I love this time of year when new the OS launches, screws up many phones and makes people trade them in for the next version. P7P here I come!
Click to expand...
Click to collapse
Here's another weird one.. apparently now I can't keep my phone on vibrate while in the car. For a test, I turned my ringer on and then tested it again.. low and behold, it rang through the speakers in my car. This is trash. I know Android enabled in-band Bluetooth audio years ago and I recall this same thing happening way back with my nexus 6p and each pixel I've had but this one. There was a setting in developer settings to turn that off which fixed it and allowed it to work correctly but with this phone, it worked out of the box so I never thought twice about it. I just checked the dev settings and it's nowhere to be found. I have no idea what A13 could have done to screw that up nor do I know if the dev setting even existed on this phone prior to A13. I just don't get it. I guess I could see if there's any updates to my car's multimedia system but I have an Audi and any software updates come from the dealer for a price. How dumb. I guess I'll be scouring the Audi forums for a fix on that.

Meh, the Google Play Store updates are irrelevant to me. So no worries there on my part, haha. But this phone's battery life has been rather questionable. I have, however, noticed that after being on the full A13 build for around a week or so and disabling 5G from the get-go that my battery now lasts MUCH longer. My phone does not seem to generate as much heat either - which is always a plus. But I also seem to have more phone/messaging reliability than I have had in the past with this device.
I am beginning to think that the modem and 5G has had the most to do with this phone's imperfections.
Also - for OP - but I have noticed that my phone often doesn't wake up with a single tap either - but only when the gyroscope stays mostly stationary for a longer period of time. When I pull the phone out of my pocket, it usually comes on with one tap. But if it has been sitting on a table or other mostly flat surface for a while, it takes two taps to wake the display.
Ultimately, I won't be getting the Pixel 7 Pro. I will, however, be getting the Pixel Fold which should launch at around the same time =).

I can't say too much about the google provided and infiltrated system images, since I only booted it on that image ONCE -- just long enough to flip the "allow OEM unlock" switch so I could flip it to AOSP and then GrapheneOS. But I will say that on GrapheneOS, the update from 12->13 has been pretty seamless. One fairly minor glitch with activating wifi hotspot that was fixed with yesterday's SECOND update, but aside from that, not a single one of the bugs mentioned in this thread.

96carboard said:
I can't say too much about the google provided and infiltrated system images, since I only booted it on that image ONCE -- just long enough to flip the "allow OEM unlock" switch so I could flip it to AOSP and then GrapheneOS. But I will say that on GrapheneOS, the update from 12->13 has been pretty seamless. One fairly minor glitch with activating wifi hotspot that was fixed with yesterday's SECOND update, but aside from that, not a single one of the bugs mentioned in this thread.
Click to expand...
Click to collapse
This kills me. Why is it that a third party dev can release a stable build with little to no bugs but if bugs are found, a patch is pushed out right away to fix yet Google cannot seem to get it right. Furthermore, if they do fix bugs, they refuse to push them out-of-band. This isn't 2008 anymore, we shouldn't need custom ROMs to get the best performance out of our phones.

jrg67 said:
This kills me. Why is it that a third party dev can release a stable build with little to no bugs but if bugs are found, a patch is pushed out right away to fix yet Google cannot seem to get it right. Furthermore, if they do fix bugs, they refuse to push them out-of-band. This isn't 2008 anymore, we shouldn't need custom ROMs to get the best performance out of our phones.
Click to expand...
Click to collapse
Well, aside from the bugs issue, as time goes on, more and more you need something besides what it ships with in order to actually have security and privacy. Google has fallen a very long way from the openness and respect that they once promised. The final straw for me was when they started working with governments to include and share covid contact tracing functionality.

Update:
Apparently the 4th complete wipe and OS flash was apparently the trick to fix the majority of my phone's issues. I did restore from my backup this time because the last time that I started from scratch, it made no difference. I figured if it's still going to be buggy, I may as well have all my info and settings correct. It's now been about 24 hours. See below for status of my issues.
1. Massive battery drain - fixed for the most part. Still have to restrict Samsung Health app but for the most part, it seems to be back to normal.
2. Screen not waking up when pulled from pocket or elsewhere that the proximity sensor activated and screen was off. - Fixed so far
3. Play system update button broken - already found this wasn't an A13 bug. I still haven't gotten the fixed update of playstore but before this latest wipe and OS flash, I sideloaded the latest version and it fixed it.
4. Connected to Bluetooth in car no longer plays ringers out loud. - Weird one as I think this is part A13 because Google baked in a new BT stack that's been in development since A11 called gabeldorsche https://www.androidpolice.com/android-gabeldorsche-bluetooth-stack/ and partly my infotainment system in my car. I am not on the current version of the car's infotainment but since my car is a '14 Audi, it doesn't have OTA updates.
5. Heating up during normal use - seems to be fixed
6. Warm while on the pixel stand and fully charged - haven't been able to observe this one bc last night, I put the phone on the stand and by morning it was at 72% and not charging. No clue if that's a new bug or if it was just not sitting on there just right. Didn't really look into it but we'll see what happens tonight.
So that seems to be the majority. Overall the phone doesn't feel "weird" anymore and most things I was having trouble with appear to be resolved. Sort of ridiculous that I had to wipe and reload the OS 4 times though.

jrg67 said:
2. Screen not waking up when pulled from pocket or elsewhere that the proximity sensor activated and screen was off. - Fixed so far
Click to expand...
Click to collapse
I actually had a similar issue with A12 -- when on a phone call, pull the phone away and it took forever to turn the screen back on. Seems to have been corrected with A13.

96carboard said:
I actually had a similar issue with A12 -- when on a phone call, pull the phone away and it took forever to turn the screen back on. Seems to have been corrected with A13.
Click to expand...
Click to collapse
This one still may be around for me but perhaps not as severe as it was during the first 2 times I loaded 13. I just experienced it about an hour ago. Took phone out of my pocket to place on my desk at work and screen was black but the AOD did eventually come on by itself after about 10 long seconds. We'll see what happens.