https://www.xda-developers.com/andr...ode-that-detects-frantic-back-button-presses/
It should be, it whas introduced on Android 7.1.x
Related
Hello,
With DP5 (it was the same on DP4), after a while (it can be a day or an hour), some of the phone sensors stop working: no auto-rotation and no ambient display. Reboots fix the issue until it happens again.
The improvment between DP4 and 5 is that auto-brightness is not affected by the bug anymore.
I saw some threads on reddit and other sites about the issue and a few android bug reports but quite nothing on XDA except on thread with 1 reply.
Some Android dev had replied on a bug report that this is a known bug and that the fix was ready for the next update (ie DP5) but the bug is still there.
So do you also have the issue? Any ideas where it comes from?
Some people believe it's Pokemon GO-related, what do you think?
Thanks
(I know that most of people play Pokemon GO anyway so this could mean nothing but issue started on DP4 it seems, and Pokemon GO released when quite everybody had switched to DP4.)
BigDRim said:
Hello,
With DP5 (it was the same on DP4), after a while (it can be a day or an hour), some of the phone sensors stop working: no auto-rotation and no ambient display. Reboots fix the issue until it happens again.
The improvment between DP4 and 5 is that auto-brightness is not affected by the bug anymore.
I saw some threads on reddit and other sites about the issue and a few android bug reports but quite nothing on XDA except on thread with 1 reply.
Some Android dev had replied on a bug report that this is a known bug and that the fix was ready for the next update (ie DP5) but the bug is still there.
So do you also have the issue? Any ideas where it comes from?
Some people believe it's Pokemon GO-related, what do you think?
Thanks
(I know that most of people play Pokemon GO anyway so this could mean nothing but issue started on DP4 it seems, and Pokemon GO released when quite everybody had switched to DP4.)
Click to expand...
Click to collapse
Seeing how it's not an official release it is just speculation by the dev that a fix would be pushed by preview 5. For whatever reason that was not achievable. The official release is more likely going to be aimed at fixing as much of the current known issues as possible.
After playing Pokemon Go for a while my Nexus 6P accelerometer/gyroscope stops working. The phone doesn't auto rotate anymore and I can't use the AR option on the app for compass. The only way to fix this is by rebooting the phone. Anyone else having the same problem? I've found people with the same issue (Pokemon Go + Nexus 6P) on this thread on Google forums:
https://productforums.google.com/forum/#!topic/nexus/ytCwNnOJEaM
EDIT
I'm currently using the latest 7.0 Nougat Preview
Yes, but it's a Nougat problem. It's fine on MM and it'll probably be fixed for the release version.
Should be fixed in a future build
https://code.google.com/p/android/issues/detail?id=217918
ammmze said:
Should be fixed in a future build
https://code.google.com/p/android/issues/detail?id=217918
Click to expand...
Click to collapse
That's awesome! Thanks for the answer.
Not quite Pokémon Go related, but with the new August Security patch update from Google, anyone else experience Auto Rotate being slow to respond? As with previous patch updates, I didn't have this problem.
I recently updated to nougat on my s7 edge and noticed "disable absolute volume control" under developer options. As far as I can tell this feature never worked with any of my BT devices. Is this disabled by Verizon or just broken on my phone?
It's not just about your device, it's a widespread problem of Nougat. I'm facing same problem on Xperia Z5C. Try looking for some patches|fixes on github for any Nougat ROM.
nobody else has this issue with my phone? still not working for me...
does anyone have it working and can prove it?
Hello Everyone.
Sorry if this is in the wrong forums. I did a few searches first, and based on this thread with no results: https://www.reddit.com/r/WearOS/comments/bgwpco/checking_for_updates_for_wear_notification
It sounds a bit like a general wear issue... possibly only with older wear devices.
I have a Sony Smartwatch 3. I am often getting the "Checking for updates for Wear" notification.. Which means that my Google Play app, will just crash if I try to use it.
Sometimes it seems to help, to sync wear apps, via the Wear OS app.. but not really anything tangible..
I actually flashed stock Android 7 on my Moto X Style, because I thought the issue was due to running custom image.. but I am still getting this error, as long as I have my Smartwatch connected..
Does anyone know anything about this.. possibly any clever solutions.. Or is it just a big middle finger from google/sony about buying a new smartwatch ?
Thanks in advance.
Not sure why but D2W seems to be not working more recently for me?
Fully up to date stock OS 8Pro
Anyone else getting this or is it some app only i use that's blocking it perhaps?