Database Info

Battery Widget -> Show what is using it up

I had a battery widget on my screen, which I swear was on the phone before I downloaded any apps. Maybe I am going nuts. It did not show %, but it showed bars.
The nice thing was when I clicked on it it would open up a page showing what apps were using the battery.
I pulled it off the screen, and now cannot find it to put back.
Anyone see anything like that?

It was on the phone when you got it? I just got it yesterday and never saw anything like that....hmmm...

Are you sure you're thinking of a widget rather than going to Settings, About Phone, then Battery Use?

Well, since posting a few min ago, I found that. But I did have an icon on my desktop that I could call that very thing with. But darned if I know how I got it there.
I've been messing with this thing so much, I'm going brain dead.I was having problems a bit ago remembering which app I used to check on available memory. But finally remembered it was Advanced Task Killer.

Long press on the desktop like you were going to add a widget or wallpaper. Choose Shortcut instead, then scroll down to Settings, click it, then choose Battery Use.
That'll put a nice little battery/magnifying glass icon on your desktop, click it and it does what it says, just like you'd went into Settings/About Phone/Battery Use.
And notice some of the other quick and handy shortcuts you can make, besides the wealth of those found in the Settings part.

Well, I am pretty sure that is how I got it there. It has disappeared from the list, so I can no longer install it.
So I guess the real question is what determines what is in that list.
Hmmm....I wonder if that is a Samsung widget, which won't work with Launcher Pro.
....
Nope, I don't see it no matter which launcher I select. I wonder what else is missing.

ewingr said:
Well, I am pretty sure that is how I got it there. It has disappeared from the list, so I can no longer install it.
So I guess the real question is what determines what is in that list.
Hmmm....I wonder if that is a Samsung widget, which won't work with Launcher Pro.
....
Nope, I don't see it no matter which launcher I select. I wonder what else is missing.
Click to expand...
Click to collapse
i have it working with launcher pro

I'm a dork today. I found it. And if I had slowed down and read Croak's reply and paid attention he had the answer.
What I was skipping was selecting Settings after going into the shortcuts. I was thinking that was the settings ICON to open general settings.

Htc Touch Pro (Raphael 500) Running Android , How to overclock?

Alright so Yesterday I installed the android os on my touch pro (raph 500)
i orginally have windows mobile 6.5 which is preety fast
but android is really slow!
i turned off all the settings which i would think it used alot of memory but still no help, so i started seeing videos on overclcking?
can someone explain to me on how to do this,
with links to the download
i really need to speed this up ,it would be amazing if it worked.
also if you give me a response that helps me , ill donate 10.00+ to you .

I do not require funds as I enjoy helping out!
From THIS thread and THIS post:
Overclocking
acpuclock.oc_freq_khz=XXXXXX ( suggested 600000-640000 )
but it is very unstable if you try to get higher than 650000-700000
Click to expand...
Click to collapse
Basically, you add that to the startup.txt file somewhere between the parentheses with an added space between the next command. Keeping in mind, with added OC, you may and may not notice a difference in stability. I honestly never use OC and I am using FroYo from THIS thread. Additionally you can try out Gingerbread Alpha from THIS thread. Please leave feedback in their respective threads, thanks!
n-Joie! (Enjoy)

thanks but this is my startup text :
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2182
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=210 msmvkeyb_toggle=off physkeyboard=raph board-htcraphael-navi.wake=0 gsensor_axis=2,-1,3 acpuclock.force_turbo=1"
boot
Click to expand...
Click to collapse
so which am i supposed to edit, sorry im a noob lol
& u said that was the one you used,
is it fast?

Actually, I can't use that one because I have an at&t Fuze. If you have a RAPH500, you might want to use the following:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2182
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=210 msmvkeyb_toggle=off physkeyboard=raph board-htcraphael-navi.wake=0 gsensor_axis=2,-1,3 pm.sleep_mode=1 acpuclock.oc_freq_khz=XXXXXX"
boot
Click to expand...
Click to collapse
Where XXXXXX is equal to a value between 600000-640000
Additional note: make sure you type something like 600000 or any value up to 640000

lol thanks im trying to see if theres a difference in speed.
but you used froyo?
is that running fast?

It's running fine with sync and a few other apps running in the background. I would be mindful of livewallpaper and HQ video at the moment as this project is currently still under development, at best. At least that is what I have noticed as far as performance is considered. I have also run a stripped Gingerbread alpha build (the one I linked you to earlier) and it is running faster/smoother than FroYo. To be expected without all the bells and whistles...
NOTE: Speed is relative to performance at the moment. Hence why I say it's still under development...

intresting ill test that out in about 15 mins
but does yours take a long time to come out of sleep mode?

Hmmm, that might be the notorious sleep of death SOD. I usually do something that most don't like but I sort of turn off the screen time out by first making the screen time out greater than 10 or 30 minutes. After that it should make things easier as far as disabling the auto back light/screen timeout feature. Keep in mind this is only a work around, I believe there is mention of actually fixing this issue. You'll need to download a free app called batterybooster (use the link if you want to read up on it a little). Once installed, run it and look for the far right icon and tap it. Set the timeout to Never and you'll notice a decent performance enhancement in the screen off and screen on.
NOTE: You will need to manually turn it off from here-on. You can try to play around with the setting but I find it somewhat problematic. Meaning that if you enable the timeout, it might and it might not work.

alright well i tried the gingerbread and that didnt work it lagged .
i tried froyo , it was amazing then i found out wifi didnt work
so now im back to the regular android one i had before ill be trying to see if theres a difference now that i "overclocked" it .
but thanks for all the help.
ill post back if i need something!

Odd, wifi(wap not wep) works for me... Must be a random occurrence? Have you attempted to update any files and are you using OC? Probably best to stick to a stock-like startup till you get a good feel of most of the basic functions, which may or may not include wifi, gps, 3d and camera; these should be on the "to be worked on" list of things for the devs to complete.

R^7Z said:
Odd, wifi(wap not wep) works for me... Must be a random occurrence? Have you attempted to update any files and are you using OC? Probably best to stick to a stock-like startup till you get a good feel of most of the basic functions, which may or may not include wifi, gps, 3d and camera; these should be on the "to be worked on" list of things for the devs to complete.
Click to expand...
Click to collapse
it works for you?
wth!
and i havenet updated any files on the deive.
no im not using overclock on this onr,
but on another android version which is on my sd card i am
& is there a way i can lock my screen so it doesn't touch any buttons in my pocket &kepp it from going into SOD .

ndnmaster096 said:
it works for you?
wth!
and i havenet updated any files on the deive.
no im not using overclock on this onr,
but on another android version which is on my sd card i am
& is there a way i can lock my screen so it doesn't touch any buttons in my pocket &kepp it from going into SOD .
Click to expand...
Click to collapse
NVM I got the wifi to work now .

Glad to hear about the wifi success story I don't know if I could walk you through that as it seems that wifi can be temperamental ( or just mental )
The only way I could get out of the SOD issue was to try for that work around (setting it to never timeout with the app mentioned) and to set a pattern unlock

R^7Z said:
Glad to hear about the wifi success story I don't know if I could walk you through that as it seems that wifi can be temperamental ( or just mental )
The only way I could get out of the SOD issue was to try for that work around (setting it to never timeout with the app mentioned) and to set a pattern unlock
Click to expand...
Click to collapse
well i set it to never timeout and i have a lock pattern
but since it never times out it wont lock .

also now im starting to notice froyo is rebooting for some weird reason automatically .

Calm down, that is kind of "usual behavior" . There are quire a few things going on and the OS is attempting to "handle it". Sometimes it can't and just quits instead of freezing up ( which would be the lesser of two evils ). To get it to lock, you will have to turn it off manually (power button). Unfortunately, I think if the keyboad slides out, it self unlocks (kind of a self defeating purpose, more or less). If you turn the screen off and wait like 10 seconds then turn the screen on (power key), you should see the lock. I can't say for sure but it does work for me. I don't really have much time for troubleshooting today, as I am at work currently but do look over the threads I linked you to earlier if at all possible.

okay so i turned it off using the power button and it booted to windows mobile (odd)
then i tried running haret.exe & got this message:
"The file HARET cannot be opened. Either it is not signed with a trusted certificate, or one of its components cannot be found. IF the problem persists, try reinstalling or restoring the file."
im not sure what to do.
i tryed reformatting the card and installing fresh files, which didnt work so now im left questioned?

When you say you turned it off, did you hold the button or just press it once? If you pressed it once, then, that is definitly not "usual" behavior. I recall having that issue once upon a time but for the life of me, I don't recall what I did to recover from it. However, it sounds like you are attempting to run from a shortcut that references the program(haret) that is no longer there. To resolve this, I need you to confirm that you are running from the microSD and not a shortcut. Also, you aren't formatting under windows, right? If you are formatting from windows, that would be a "no-no"
Find something like the HP tool (can be googled) that everyone else talks of or even something like the free version of partition wizard should work.

i held the button and it gave me options
1) airplane mode
2)shutoff
3)vibrate
i did try to make a shortcut but i deleted it and now when i checked i was running it from the actual application.
lastly, i did format from windows but i downloaded hp format tool
and formated my device in quick format.
reinstalled the programs and it still gave me the same error message,
please help, i really miss android =(

Try deleting data.img and letting it recreate the file. To clarify about the screen off issue, when you press the power button once (not hold), what does it do? Also, which kernel package are you using and have you attempted to download a newer kernel package yet?
Also, try THIS kernel package; I got it from THIS site. It looks like that kernel package is specific to our devices.

[Q] Weird Stock Browser Issue

Two things:
Firstly, when I type in the browser the screen moves up on every key press...weird.
Secondly, the top of the screen (in expanded desktop mode, with full screen lab running) gets corrupted - legacy downloading blue lines and tabs - which should disappear. Weird.
Any ideas from the brains trust out there? It's been happening sporadically for a couple of weeks - I'm on CM10.1 Nightlies - been the same with various versions of CM10.1.

dgjl said:
can anybody explain and /or solve the following two things:
Firstly, when I type the screen moves up on every key press...weird and annoying.
Secondly, the top of the screen (in expanded desktop mode, with full screen lab running) gets corrupted - legacy page downloading blue lines and tabs - which should disappear remain in the top part of the screen.
Any ideas from the brains trust out there? It's been happening sporadically for several weeks - I'm on CM10.1 Nightlies - been the same with various versions of CM10.1.
Click to expand...
Click to collapse
Bump - any ideas? Has this really never been seen before (did a clean install yesrerday and it still happpens).

Over 100 views and no ideas? Someone must know something. Surely it's not a unique set of problems .

It's definitey an issue with the 'labs' setting - turn that off and it goes away. Any reason why this should happen? can anyone replicate this?

dgjl said:
It's definitey an issue with the 'labs' setting - turn that off and it goes away. Any reason why this should happen? can anyone replicate this?
Click to expand...
Click to collapse
Hi dgjl-
I'm replying to this post with your same settings and having none of the same problems. No scrolling when I typing, no ghosted tabs or lines above? I do have some wierdness with the cursor positioning though and positioning the cursor with the arrow keys does not work in desktop mode but does in mobile mode (user agent). Also the page seems to have a white hue like its been whitewashed.
Labs, Developer Settings, and Experimental all mean about the same thing. It means its a new feature that hasn't been fully tested so use it at your own risk. I tend to avoid these settings unless you want to be a beta test site for Asus. You may then have to disable other settings that previously worked fine to run your new setting as they may conflict. You may have to "experiment" to find the combination of settings that work together.
If you type "about:debug" into the address line, then go back into settings there is a new menu item "debug" and in there are a slew of new settings to check out. Enabling "enable cpu upload path" speeds things up, and there is also controls for OpenGL and WebGL that you might experiment with. Also try disabling "fast scroller" under the advanced settings as it may conflict with the labs flyouts. I am also running my Multi browser2RAM startup script which is the same as browser2RAM.

elfaure said:
Hi dgjl-
I'm replying to this post with your same settings and having none of the same problems. No scrolling when I typing, no ghosted tabs or lines above? I do have some wierdness with the cursor positioning though and positioning the cursor with the arrow keys does not work in desktop mode but does in mobile mode (user agent). Also the page seems to have a white hue like its been whitewashed.
Labs, Developer Settings, and Experimental all mean about the same thing. It means its a new feature that hasn't been fully tested so use it at your own risk. I tend to avoid these settings unless you want to be a beta test site for Asus. You may then have to disable other settings that previously worked fine to run your new setting as they may conflict. You may have to "experiment" to find the combination of settings that work together.
If you type "about:debug" into the address line, then go back into settings there is a new menu item "debug" and in there are a slew of new settings to check out. Enabling "enable cpu upload path" speeds things up, and there is also controls for OpenGL and WebGL that you might experiment with. Also try disabling "fast scroller" under the advanced settings as it may conflict with the labs flyouts. I am also running my Multi browser2RAM startup script which is the same as browser2RAM.
Click to expand...
Click to collapse
Thanks. I've been through the various debug settings already - what's strange is that when debug is operating (i.e., in the same browsing session as 'about:debug' is launched) the problems don't seem to occur. Is there anyway to make debug permanent - as it is on Cromi, for example?

dgjl said:
Thanks. I've been through the various debug settings already - what's strange is that when debug is operating (i.e., in the same browsing session as 'about:debug' is launched) the problems don't seem to occur. Is there anyway to make debug permanent - as it is on Cromi, for example?
Click to expand...
Click to collapse
This is the first I'm hearing about the "about:debug" settings you change not being "permanent". I don't follow you. When I change a debug menu setting in a browser session, then launch a new tab and url "about:debug" in that session, all the settings I changed in the previous session are applied to all new tabs I create. Same is true if I shut it down and relaunch the browser. The settings persist. Yours don't?
Are you running the old browser2RAM that loads the actual browser app as well as its cache into RAM ["mount | grep tmpfs" to check all mounts from the terminal] so the session data doesn't persist? If so, use my startup script 3 in my signature instead - data persists. Its a more versatile replacement for browser2RAM that works on 4.2 as well. For 4.1 and below you can run it from the terminal as su after boot. For 4.2 you need to run it as su *at boot* using either an init.d method or the Script Manager (Devwom) app.
I'm kinda liking this lab flyout! Makes for quick navigation. But this cursor thing is starting to P me O. I use Chrome instead.
@sbdags do you have any suggestions?

elfaure said:
This is the first I'm hearing about the "about:debug" settings you change not being "permanent". I don't follow you. When I change a debug menu setting in a browser session, then launch a new tab and url "about:debug" in that session, all the settings I changed in the previous session are applied to all new tabs I create. Same is true if I shut it down and relaunch the browser. The settings persist. Yours don't?
Are you running the old browser2RAM that loads the actual browser app as well as its cache into RAM ["mount | grep tmpfs" to check all mounts from the terminal] so the session data doesn't persist? If so, use my startup script 3 in my signature instead - data persists. Its a more versatile replacement for browser2RAM that works on 4.2 as well. For 4.1 and below you can run it from the terminal as su after boot. For 4.2 you need to run it as su *at boot* using either an init.d method or the Script Manager (Devwom) app.
I'm kinda liking this lab flyout! Makes for quick navigation. But this cursor thing is starting to P me O. I use Chrome instead.
@sbdags do you have any suggestions?
Click to expand...
Click to collapse
Actually I'm running your script for b2r… As for 'permanent' I just meant the menu for debug being always available, not the settings. When it's there as an option the typing doesn't move the screen up - though screen corruption still happens as described.
Using Dolphin currently as I'm a full screen addict and Chrome doesn't offer that - or flash.

dgjl said:
Actually I'm running your script for b2r… As for 'permanent' I just meant the menu for debug being always available, not the settings. When it's there as an option the typing doesn't move the screen up - though screen corruption still happens as described.
Using Dolphin currently as I'm a full screen addict and Chrome doesn't offer that - or flash.
Click to expand...
Click to collapse
Ah, gotcha. About:debug>enable cpu load path fixed some of the corruption I was having with my cursor. Its not just for speed. Developer Options>Force GPU rendering fixes random reboots and other things if you haven't tried that. Make sure you have my script version 3 for Dolphin support. That's about all I've got for you @dgjl.

elfaure said:
Ah, gotcha. About:debug>enable cpu load path fixed some of the corruption I was having with my cursor. Its not just for speed. Developer Options>Force GPU rendering fixes random reboots and other things if you haven't tried that. Make sure you have my script version 3 for Dolphin support. That's about all I've got for you @dgjl.
Click to expand...
Click to collapse
Thanks for taking an interest, Elfaure. Looking around the 'web' I don't think I'm the only one with ths issue, but there's no one out there with the solution yet. It's just strange that it started without an obvious cause...

SORTED:
I found this thread http://code.google.com/p/android/issues/detail?id=39811
I had downloaded a notifiation app which ran under Settings>Accessibility. The moment I disabled it the probem went away!
Marvellous!

dgjl said:
Thanks for taking an interest, Elfaure. Looking around the 'web' I don't think I'm the only one with ths issue, but there's no one out there with the solution yet. It's just strange that it started without an obvious cause...
Click to expand...
Click to collapse
You might want to unload my script and see if the problem persists. If it does then ? If not, then maybe some switches could be added to your mount line (nodev, nosuid, gid=...etc.)

elfaure said:
You might want to unload my script and see if the problem persists. If it does then ? If not, then maybe some switches could be added to your mount line (nodev, nosuid, gid=...etc.)
Click to expand...
Click to collapse
The solution is in my previous post - anything running in Settings>Accessibility with conflict with the stock browser/lab and cause this to happen. trouble is now I don't know what to do for a notification widget as they all use 'accessibility' and I don't want the notification bar to be visible. Good old Android - there's always something!

dgjl said:
The solution is in my previous post - anything running in Settings>Accessibility with conflict with the stock browser/lab and cause this to happen. trouble is now I don't know what to do for a notification widget as they all use 'accessibility' and I don't want the notification bar to be visible. Good old Android - there's always something!
Click to expand...
Click to collapse
So its either accessibility notifications and a different browser or labs flyouts with the stock brower - your choice. Good you got the bottom of it. That's always the first step in fixing a problem. Looks like you can't have your cake and eat it too on this firmware.

Anyone else experiencing dropped tap inputs?

On my pixel 2 tap inputs occasionally don't register, I've had it happen in the android system menu, the android back/home buttons, chrome, etc. Is anyone else experiencing this?
My phone's basically on stock default settings, nothing unusual running. Not sure if it's only tap inputs getting dropped or the whole system locking up temporarily. Turning on "Show taps" in Developer options I can see there's no visual effect when a missed tap occurs.

Yes, this is me too exactly. Same thing with the dev option too. Not sure if I should wait for 8.1 or if it's hardware and RMA it. Frustrating because I like this phone.

I noticed this on my phone, clicking around in the settings and on the back and home buttons. I then did a factory reset (because of a separate issue where the location icon was always displaying in the notification area, even when not in use). After that the issue seems to have gone away. So it would seem to be software issue. I suggest trying a factory reset (though beware that this wipes everything on your device).
P.S. nonexistent, I'm impressed that you joined the XDA forums in Dec 2010 and never posted a comment until now. Of course, you might need to change your screen name to "existent," now that you're out in the open.

I have definitely noticed this as well, happy to know it wasn't just me

cb474 said:
I noticed this on my phone, clicking around in the settings and on the back and home buttons. I then did a factory reset (because of a separate issue where the location icon was always displaying in the notification area, even when not in use). After that the issue seems to have gone away. So it would seem to be software issue. I suggest trying a factory reset (though beware that this wipes everything on your device).
P.S. nonexistent, I'm impressed that you joined the XDA forums in Dec 2010 and never posted a comment until now. Of course, you might need to change your screen name to "existent," now that you're out in the open.
Click to expand...
Click to collapse
I tried a reset but the issue still showed up. In fact it happened twice on the first time setup stuff afterwards. I called Google and we went through the motions and reset it from recovery mode but it was still there when I was testing it the next couple hours. Anyway, we're doing the RMA thing. I'll let you guys know how it works out when I get my new phone.

Got my replacement and the problem still exists. It even happens just a couple screens into the initial setup after a factory reset from recovery mode.

I find that it occurs when I'm in a small room with the heat turned up. The sensitivity of the touch screen seems to depend a lot on moisture. If I keep my fingers moist (or wear a touch sensitive glove) it works a heck of a lot better.

ritzack said:
Got my replacement and the problem still exists. It even happens just a couple screens into the initial setup after a factory reset from recovery mode.
Click to expand...
Click to collapse
That's good and bad news I guess, hopefully just needs a software update. I have a replacement coming Monday, but I kind of expect no improvement and that this is just a common thing that a lot of people aren't noticing

I noticed that for a while in Google Play Books, in which I tap the screen frequently to turn pages. I tried a factory reset, which didn't help. I tried running in safe mode and testing on Maps and still had a problem, although less frequently (a higher percentage of taps worked). Then it started to work better. We'll see if that lasts.
I tried flicking as opposed to tapping and flicking always works.
I'd suggest posting on the Pixel product forum or calling support, so that Google becomes more aware of the issue. There are some threads on the subject on reddit and the product forum.

Out of interest are you noticing it any particular parts of the screen?
I've noticed it a few times but it's been on areas of the screen near the edges.
I assumed it was some sort of palm rejection thing going on it the background with it thinking I'm accidently mashing the display.

With me it was the right edge toward the middle, as that's where you tap to turn the page in Play Books.

I get it on the back button frequently, but it happened just now in the middle of the screen when I typed the text input box to start writing this

I think this is the whole OS hanging/freezing briefly actually, not a touchscreen input issue
- Pressing the hardware unlock button can get ignored (both locking/unlocking)
- Scrolling from a quick flick + release can suddenly stop (no additional inputs)
So most likely this is a software issue, hopefully fixed in an upcoming update? It's kinda annoying

Did you change the DPI or font size? I go back to default and it seems that everything is good now.
---
update: no it happens again…

nonexistent said:
On my pixel 2 tap inputs occasionally don't register, I've had it happen in the android system menu, the android back/home buttons, chrome, etc. Is anyone else experiencing this?
My phone's basically on stock default settings, nothing unusual running. Not sure if it's only tap inputs getting dropped or the whole system locking up temporarily. Turning on "Show taps" in Developer options I can see there's no visual effect when a missed tap occurs.
Click to expand...
Click to collapse
can you be more specific? I just got Pixel 2 - black, 128GB (Canadian). I can touch and the UI responds well. But i want to test it out thoroughly..

Haven't changed the DPI or font size
LimitsX said:
can you be more specific? I just got Pixel 2 - black, 128GB (Canadian). I can touch and the UI responds well. But i want to test it out thoroughly..
Click to expand...
Click to collapse
I can trigger the system hang/"missed input" most reliably by visiting m.reddit in chrome (any thread w/ comments) and spamming tap on the [-] next to the username of any comment to collapse/expand the section. Turning on Show Taps from Developer Tools in the system menu I can see taps being ignored sometimes

Haven't changed the DPI or font size
LimitsX said:
can you be more specific? I just got Pixel 2 - black, 128GB (Canadian). I can touch and the UI responds well. But i want to test it out thoroughly..
Click to expand...
Click to collapse
I can trigger the system hang/"missed input" most reliably by visiting any m.reddit thread in chrome and spamming tap on the [-] next to the username of any comment to collapse/expand the section. Turning on Show Taps from Developer Tools in the system menu I can see taps being ignored sometimes

nonexistent said:
Haven't changed the DPI or font size
I can trigger the system hang/"missed input" most reliably by visiting m.reddit in chrome (any thread w/ comments) and spamming tap on the [-] next to the username of any comment to collapse/expand the section. Turning on Show Taps from Developer Tools in the system menu I can see taps being ignored sometimes
Click to expand...
Click to collapse
So, I replicated what you told me, 3x. I didn't miss any taps, and no system hang/missed input..
hmm

Got my replacement and it has been much better so far. Still a few dropped inputs but I think those may be false positives because I am hyperfocused on it. Pretty sure I have always had to double click occasionally on all phones at various times.

nonexistent said:
Turning on Show Taps from Developer Tools in the system menu I can see taps being ignored sometimes
Click to expand...
Click to collapse
Yeah, sometimes I see a tap register visually on the screen, but the intended action doesn't happen.
redandblack1287 said:
Got my replacement and it has been much better so far. Still a few dropped inputs but I think those may be false positives because I am hyperfocused on it. Pretty sure I have always had to double click occasionally on all phones at various times.
Click to expand...
Click to collapse
It's funny. I had the issue. Did a factory reset. Felt like it was better. But now that I'm thinking about it more I notice it a lot. So I can't tell if it's really different. Before I figured I'd made a mistake. Now I think it's the phone. Damn you phone!
Anyway, I notice that the issue tends to happen more or less randomly, at any position on the screen. Also, sometimes the same tap fails to register twice in a row, but once it's starts working all subsequent taps that come in a row work (say I'm clicking through a lot of menu items in some settings). So maybe that lends some credence to the idea that there is a system for registering the taps that is not waking up and once it does it works fine.
Perhaps related, I have my ambient display set to wake on double tap. Before the Nov update it hardly worked. Now it seems to be working reliably.

Question Is your touchscreen acting like you long pressed frequently?

I have noticed, especially in Chrome, that my phone often confuses a split second touch of the screen, like when I'm trying to scroll, as a long press. On my previous devices, I can put my finger on the screen and slide a little and hold for a fraction of a second before sliding again, never taking my finger off the display, making it easy to skim without bouncing the screen all over the place, but this same action seems to make the phone think I'm long pressing and sometimes it does it when I'm just trying to flick scroll normally too. It has been driving me nuts and I thought it may just be me since I hadn't seen others complain about it but then today I saw two others say they have the same issue so now I'm curious how prevalent it is.
For the record, I'm running the QPR1 beta 3 but it was doing it on stock .031 too.

@EtherealRemnant
Go to Settings then Accessibility. Scroll down to Timing Controls and change Touch and hold delay to medium.

I can reproduce this issue when I use the full flesh of my thumb to scroll.
In normal use I've had it happen twice or so.

bjevers said:
@EtherealRemnant
Go to Settings then Accessibility. Scroll down to Timing Controls and change Touch and hold delay to medium.
Click to expand...
Click to collapse
This is why I stick around XDA, people with knowledge about the devices we use.
This cleared up --so far-- all of the quirky errant touches and context menus I've been getting the past week
Thank you!

I've seen it happen a few times while in Chrome from scrolling, but I experienced the same behavior on my Pixel 4 XL.
I'll be scrolling past stuf in Chrome, and sometimes it'll read it as " Oh, you clicked this! " then proceed to load that page up.

bjevers said:
@EtherealRemnant
Go to Settings then Accessibility. Scroll down to Timing Controls and change Touch and hold delay to medium.
Click to expand...
Click to collapse
I will try this and report back. Thanks. I didn't even think it could be an accessibility setting.
EDIT: Instantly better, thanks!

Unlike the scrolling issue, I've never had this so perhaps it's something only some devices have.

Nice find! I think the short setting is a little too short while the medium setting is a little too long. I wish they could be adjusted manually like you can with the setting on the Google keyboard.

jaseman said:
Nice find! I think the short setting is a little too short while the medium setting is a little too long. I wish they could be adjusted manually like you can with the setting on the Google keyboard.
Click to expand...
Click to collapse
I'm hoping there will be a patch soon that refines the sensitivity. I agree that medium touch-time is a bit too long when you are intentionally trying to access the context menus, but it's much less aggressively annoying than what I was experiencing with the OS

I no longer own my Pixel but when I did it had the problem. Can't remember where I found this solution but it works.......
Using ADB, I've changed the delay timeout to a non-standard value and it seems to have fixed the problem for me i.e. long click delay is consistent every time:
adb shell settings put secure long_press_timeout 401
p.s. For reference standard values are:
Short - 400
Medium - 1000
Long - 1500

appro77 said:
I no longer own my Pixel but when I did it had the problem. Can't remember where I found this solution but it works.......
Using ADB, I've changed the delay timeout to a non-standard value and it seems to have fixed the problem for me i.e. long click delay is consistent every time:
adb shell settings put secure long_press_timeout 401
p.s. For reference standard values are:
Short - 400
Medium - 1000
Long - 1500
Click to expand...
Click to collapse
I'm not familiar with shell, what would the exact command be, I did try adb shell but entering the above it says secure inaccessible or not found. I would like to try medium setting on 700.
Edit: Nvm I tried again & it worked. I set it to 600 which is better now