On screen volume controls won't go away until after 2 seconds minimum - Google Pixel XL Questions & Answers

I've had my phone since launch and this only just started happening. I'm stock.
When I use the hardware volume rocker, the volume control GUI comes up at the top of the screen like always. Before, I could tap anywhere else on the screen to make those controls go away. Now, that no longer works, and I have to wait ~2 seconds for it to go away, which is annoying if I need to use or tap that area of the screen. What is worse, if I even try to tap anywhere else to make it go away, it resets that 2 second timer so that I HAVE to sit and wait for it to disappear EVERY time I use the volume rocker.
Did this change with the last monthly security update? Anyone else seeing this?

Can you be more specific about what you mean when you say "hardware volume rocker"?

Check to see if you have "switch access" enabled in accessibility in settings. This causes weird things to happen sometimes.
Sent from my Pixel XL using Tapatalk

VergilPrime said:
Can you be more specific about what you mean when you say "hardware volume rocker"?
Click to expand...
Click to collapse
The volume button on the side of the phone.
ahent said:
Check to see if you have "switch access" enabled in accessibility in settings. This causes weird things to happen sometimes.
Click to expand...
Click to collapse
No, but thanks for the idea to check.

I'm getting that too, for often much longer than 2 seconds. Sure is weird. Switch Access is off.

I'm using Nova launcher and the slider pop-up goes away as soon as I touch the screen. (December security update, stock and not rooted.)
T
Sent from my Pixel XL using Tapatalk

Crazy late post but I had the same thing happen to me. It went away when I changed my system wide font size.

Having similar issue here, but slightly different.
When i use the rocker and menu appears it will not go away UNTIL I touch somewhere on the screen.
And if I touch the menu to adjust the slider I will still need to touch elsewhere on the screen to make the volume menu go away.
Very annoying.
I'm VZW Pixel XL on 7.1.1 (unlocked bootloader and rooted)
I'm going to be updating to a newer Android version soon, but it's quite annoying until then.

Asus zenfone max pro m1, Android 8.1
I may be to late to answer this tread but I had same problem recently. It got solved. It happened because I downloaded an auto-clicker app to do some stuff. It needed the "display over other app" permission. When I uninstalled it, everything was fine. I think it was due to that permission unusual stuff were happening.

Related

[Q] Problems with 5.1.1

My watch was working perfectly before the 5.1.1 update, but ever since the update, it is slow to wake, unable to swipe away cards from the watch face without opening them, the touch sensitivity is TERRIBLE....have to swipe over and over to get it to register, and for notifications I am unable to select "ALL"...can only select "priority" and "none".
Is anyone else having these problems?
5.1.1 problems are being discussed here if you're not aware:
http://forum.xda-developers.com/zenwatch/general/android-5-1-1-ota-files-online-t3109484
No problem in starting a new thread, though.
nhpilot43 said:
Is anyone else having these problems?
Click to expand...
Click to collapse
I noticed that the touch screen seems derpy to me too. Something is definitely weird with the toggle shade thingy. I'm having the same problem with selecting "all". You can get it, but you have to find the exact spot below and to the left and tap frantically like a dozen times. I reccomend using the test app in developer settings and open the touch test. It will display a small grid and it will trace all your touches. Don't worry if it says fail. Just notice whether or not its tracking your finger. To get it to pass you have to turn the lines green by swiping in a certain direction. Mine tracks perfectly so, for me at least, the hardware is fine. Definitely a software issue.
-Andy
Sent from my Apple Newton.
Yesterday I installed the Android M preview on my phone, and so I had to do a reset on my watch. Now all of the touchscreen wonkiness has gone away, and it's working fine!
Before I was unable to get the app list to appear by swiping from the right, but only by tapping once. Also, I couldn't swipe in the center of the screen in the mode selector shade, but only above or below the row of icons. Now that's all working as well.

Home button continues pressing?

I've had this issue before on my LG Power (Straight Talk branded LG Leon), running on Lollipop 5.0. No matter what I look for I can't find anyone who's experienced similar issues.
It just happened last night on my 5-day old Nexus. I could not open any of my folders to access apps. As soon as a touched a folder, it briefly showed the animation to open it, and it immediately closed. Whenever I selected a widget or the app drawer, they would immediately close as well. When I attempted to swipe down the notification/quick settings shade, they immediately closed themselves. Turning off the screen resulted in the screen immediately turning back on, albeit locked. I was even having trouble turning the device off because the 'Power Off' menu would disappear right after it popped up. Eventually I was able to time it right and was able to power off. Since I restarted I have not have any issues.
Any idea what gives? I'm unrooted, locked bootloader, everything 100% stock, running MM 6.0.1.
the only explanations i can come up with are:
-accidental touching the area in some way (unlikely)
-getting some substance stuck on the screen in that area (unlikely)
-a faulty touch panel (unlikely and very specific defect)
-a hickup in the software (again unlikely)
then again, if the OS (for whatever reason) thinks the home button is pressed, on default it should not only pull you back to the homescreen, but continue and send you right through to google. the conclusion of which would be, that this UI area is triggered repeatedly rather than continuously.
keep an eye out for what could have triggered it in case it occurs again.
check your settings what build exactly you are running (settings -> about phone -> build number).
ans lastly, if it happens again, you should still be able to hold your power button to hard-reboot it (no further interaction with the UI required).
RockinAmigo14 said:
I've had this issue before on my LG Power (Straight Talk branded LG Leon), running on Lollipop 5.0. No matter what I look for I can't find anyone who's experienced similar issues.
It just happened last night on my 5-day old Nexus. I could not open any of my folders to access apps. As soon as a touched a folder, it briefly showed the animation to open it, and it immediately closed. Whenever I selected a widget or the app drawer, they would immediately close as well. When I attempted to swipe down the notification/quick settings shade, they immediately closed themselves. Turning off the screen resulted in the screen immediately turning back on, albeit locked. I was even having trouble turning the device off because the 'Power Off' menu would disappear right after it popped up. Eventually I was able to time it right and was able to power off. Since I restarted I have not have any issues.
Any idea what gives? I'm unrooted, locked bootloader, everything 100% stock, running MM 6.0.1.
Click to expand...
Click to collapse
Try to clean your screen also with a towel
That is extremely weird. It really sounds like a faulty digitizer, but you'd be the first... Maybe it's a rogue app, but unlikely.
Were you doing something before this starts to happen?
I haven't noticed any consistent apps or behaviors when this would occur. This most recent time, I was low on battery (10%) and I had just flipped on my data.
fyi. you could also just press and hold the power button, for 10 secs, for a reboot ( might come in handy when the screen isn't working properly).
dpj52190 said:
fyi. you could also just press and hold the power button, for 10 secs, for a reboot ( might come in handy when the screen isn't working properly).
Click to expand...
Click to collapse
appreciate the tip! I'll keep this in mind if it happens again.
Finally was able to capture a video. The issue occurred after I was playing around with Open Camera and it crashed. Holding down the power button didn't work when this glitch is happening.
https://youtu.be/4n5vzXlUPqM
RockinAmigo14 said:
Finally was able to capture a video. The issue occurred after I was playing around with Open Camera and it crashed. Holding down the power button didn't work when this glitch is happening.
https://youtu.be/4n5vzXlUPqM
Click to expand...
Click to collapse
What's the icon on the lock screen, top right in the status bar? That behavior is unusual if it's not a screen defect. Are you using any apps that monitor battery, a task killer, or maybe a security monitor app?
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
What's the icon on the lock screen, top right in the status bar? That behavior is unusual if it's not a screen defect. Are you using any apps that monitor battery, a task killer, or maybe a security monitor app?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
The icon is a picture for my user profile on the phone.
I don't use anything like that. I had Clean Master installed briefly but it's been uninstalled for a couple of days now.
so it seems like this issue pops up whenever the camera crashes. happens occasionally when using the camera shortcut (double power tap) or in an app that uses the camera.
It's got to be software IMO. It didn't happen when you went to Google Now and your Recent Apps. I'd try uninstalling the Open Camera app first. Do you have Face Unlock active by chance? After that I'd FDR...
exninja said:
It's got to be software IMO. It didn't happen when you went to Google Now and your Recent Apps. I'd try uninstalling the Open Camera app first. Do you have Face Unlock active by chance? After that I'd FDR...
Click to expand...
Click to collapse
right, that's what's confusing me. i did a factory reset last week, set up the phone as a new device. haven't installed a new camera app, just the stock google camera. the issue occurred again last night when using an app called Shopkick, which accesses the camera but crashed.

How to Disable Screen Wake for Ring app

Hey all, my ring doorbell app wakes the screen anytime I get an alert. I want to keep the notifications on but don't want the screen to wake. It wakes even in my pocket which I want to of course avoid. It may just be a bug in the app but I should be able to limit that from happening. Or so I hope anyway.
I have tried the following.
1. Switched all notifications pertaining to the app and individual cameras to "sound only"
2. In the app I have disabled "alerts open full screen video"
3. I have disabled heads up notifications globally through ADB.
4. Disabled ambient display.
5. Disabled notifications on lock screen.
I'm at a loss on what to do next. Any ideas are appreciated at this point.
TIA
ifly4vamerica said:
Hey all, my ring doorbell app wakes the screen anytime I get an alert. I want to keep the notifications on but don't want the screen to wake. It wakes even in my pocket which I want to of course avoid. It may just be a bug in the app but I should be able to limit that from happening. Or so I hope anyway.
I have tried the following.
1. Switched all notifications pertaining to the app and individual cameras to "sound only"
2. In the app I have disabled "alerts open full screen video"
3. I have disabled heads up notifications globally through ADB.
4. Disabled ambient display.
5. Disabled notifications on lock screen.
I'm at a loss on what to do next. Any ideas are appreciated at this point.
TIA
Click to expand...
Click to collapse
I've struggled with the same thing for months. It never used to do it, but after an update earlier this year it became the new normal for me.
I'm glad I'm not the only one. Hopefully somebody chimes in with some sort of work around.
I'm having the same problem with a Sony XZ1 phone (Android 8.0.0). I spoke with Ring at length and it's 'apparently' a problem with my phone, not their App.
I think that's a load of rubbish and something they need to address and fix. I installed the App on another Android phone running an earlier version of software, the App installs with different options and doesn't wake up the screen. So it's obviously dependent on the OS version but as other Apps don't have the same problem I can only conclude that it's an issue with the Ring App.
Has anyone tried uninstalling the app and then install an older version from APK mirror? Not even sure its on there but it's worth a go
hatdrc said:
Has anyone tried uninstalling the app and then install an older version from APK mirror? Not even sure its on there but it's worth a go
Click to expand...
Click to collapse
That's a great idea. There are plenty of versions to try on APK mirror, one or two per month from 2018. Not a good sign for a reliable and stable app.
I'll give it a go later unless anyone gets there first and can suggest a 'good' version to try
Were you able to find an older version that doesn't have the screen wake behavior?
edit: Pixel 2 - going back to 2.0.66.8 still has the screen wake behavior regardless of notification setting.
edit 2: 2.0.57.2 does the same thing...
Looks like the latest ring version finally let's you fix this. Select your devices, go to notification settings, then select sound only. The default is sound plus pop up. I no longer have the issue after making the change.
Can anyone confirm if turning off the 'plus pop' in the ring app settings works? I have a new pixel 3 on Android pie and the app is still turning on the screen at every alert event with settings set to just sound or just silent.
I'm having the same issue with the ring app. It wakes the screen. Really sucks when phone is in my pocket. I have tried every option and or combo of options. I have a pixel 3a on Android 10. Android 10 does have a option to wake screen for notifications found under display advanced, lock screen. But it is turned off
Still a problem on Android 10, No combinations of settings has been able to stop this for me. Of course Ring denies this even though I have sent a logcat to them.

Back/Home Gestures Or Buttons Stop Working

I've noticed since going to the official Android 10 update and then the October update, if the phone sits idle for a while the the back or home functions stop working (both with gestures and the pill). I can open other apps from the notification pull down and navigate forward. I also cannot pull up the keyboard. I tried to submit a log file to Google but Google requires me to type a description of what happened and I can't do that. The only option is to restart the phone from the power menu. Once that happens it's back to normal functioning. This has happened at least 5 times. Has anybody else experienced this?
Sent from my Pixel 2 XL using Tapatalk
Yes! This has been driving me crazy since updating to 10! I finally got fed up and came here looking for answers.
For me it doesn't seem to have anything to do with the phone being idle. It seems to happen after playing video (or potentially other full-screen things, like a game for example). Not sure if it's related to going full screen or maybe going landscape.
When it happens, it seems to only be the home gesture. Back works fine (and sometimes I can keep doing the back gesture to get out of it)
Restarting is usually the quickest way to fix it, but if I don't want to restart, I've found that if I go to settings and switch to 3-button nav, the home button will work again. With 2-button nav, home still doesn't work but multitasking does. Very odd.
I'm suffering from the same problem. I had to switch back to the pill but I've gotten so used to gestures that the pill is tedious.
demarcmj said:
Yes! This has been driving me crazy since updating to 10! I finally got fed up and came here looking for answers.
For me it doesn't seem to have anything to do with the phone being idle. It seems to happen after playing video (or potentially other full-screen things, like a game for example). Not sure if it's related to going full screen or maybe going landscape.
When it happens, it seems to only be the home gesture. Back works fine (and sometimes I can keep doing the back gesture to get out of it)
Restarting is usually the quickest way to fix it, but if I don't want to restart, I've found that if I go to settings and switch to 3-button nav, the home button will work again. With 2-button nav, home still doesn't work but multitasking does. Very odd.
Click to expand...
Click to collapse
I'm having the exact same problem as you. It seems to always happen when I'm playing something full screen in landscape mode. I've just been restarting my phone each time. Thanks for the info about switching back to the three button. There are times when I'm in the middle of something and restarting is just inconvenient.
I did a factory reset 2 days ago and it hasn't happened since. I did not use any backup except for phone calls and text messages.
Sent from my Pixel 2 XL using Tapatalk
Yeah it's random with me at times the back button becomes useless. Thanks Google for this bug. I can't reset my phone every f time!

Weird, inconsistent touch screen behaviour after screen replacement

So I've recently replaced my screen and I'm getting some strange behaviour with the touch interactivity. I have turned on tap visibility in the developer options and will try and descibe what is happening...
It seems to really dislike some apps, for example on the home screen it is the worst - It sees my fingertip contact when i tap, but its as if i'm holding my fingers down. This is the kind of behaviour in the lock screen too.
The weird thing is though, that I can get to the settings menu through holding the power key > "Side key settings" - and everything works perfectly. In other apps it its also pretty usable - though maybe slightly more laggy sometimes and can hang for a few moments.
I am wondering whether this sounds like a software or a hardware issue to anyone with more expertise? (relatively new to this repair/modding stuff). I have tried downgrading it to a younger version of android with odin but that didn't work. I am also wondering whether rooting might open some possibilities?
Thanks
ptanim said:
So I've recently replaced my screen and I'm getting some strange behaviour with the touch interactivity. I have turned on tap visibility in the developer options and will try and descibe what is happening...
It seems to really dislike some apps, for example on the home screen it is the worst - It sees my fingertip contact when i tap, but its as if i'm holding my fingers down. This is the kind of behaviour in the lock screen too.
The weird thing is though, that I can get to the settings menu through holding the power key > "Side key settings" - and everything works perfectly. In other apps it its also pretty usable - though maybe slightly more laggy sometimes and can hang for a few moments.
I am wondering whether this sounds like a software or a hardware issue to anyone with more expertise? (relatively new to this repair/modding stuff). I have tried downgrading it to a younger version of android with odin but that didn't work. I am also wondering whether rooting might open some possibilities?
Thanks
Click to expand...
Click to collapse
looks like you have replaced your screen with a non functioning/ not original screen
can you check if FP is working
JuanTamqd21 said:
looks like you have replaced your screen with a non functioning/ not original screen
can you check if FP is working
Click to expand...
Click to collapse
Sorry, what's FP?
ptanim said:
Sorry, what's FP?
Click to expand...
Click to collapse
fingerprint

Categories

Resources