N DP5: Sensors issues still there - Nexus 6P Q&A, Help & Troubleshooting

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.

Related

Android 6.0 AOSP ROM crash/reboot with Chrome Location

Hi all, first post so can't report this in the Dev forum.
I have flashed Marshmallow onto my Nexus 4 according to the instructions in the "official" ROM thread.
All seems to be fine, I had duplicate apps for the clock/calendar etc which didn't bother me much, and I was getting network connectivity issues which have largely gone away. I'm happy to have upgraded as it means I don't need to get a new Nexus phone just yet :good:
However, there is a pretty serious crash trigger, that I can easily reproduce on my handset anyway. Allowing any website to access my location in Chrome will trigger a reboot, every time. Just wondering if any other users have experienced this, whether the ROM developer is aware of it, or whether there is anything I should do to fix the problem or assist in finding a fix?
I found a fix in the very thread I linked above, guess I should have read all 50 pages of it
Here is the fix for anyone coming here from Google in the future.

Gyro dont in 7 beta

I downloaded app to see why my gyro is weird and there i can se that gyro or orientation does not work and it did before joining beta.
Is this a known issue?
Can i solve it somehow?
I got ota yesterday so a pretty new build i guess
I am not rotted i havet it all original
I've had a similar if not the exact same issue as of obtaining this device. I enrolled in the beta around the third Dev preview (immediately after I purchased the phone, it's still fairly new as of writing this), at the end of the fourth preview I started having the same issue, gyroscope just spontaneously stopped working. At first I thought it was a hardware issue after doing some research (apparently some Nexus 6P users gyroscopes are just getting stuck or something along the lines of that?? And they'll report it working again after a few good smacks to the thigh.) I would have assumed this to be the issue but I found that rebooting the device actually fixed it temporarily, but after a few hours it stops working again. I'm now using the fifth and final dev preview and it's still an issue. The fact that rebooting fixes the issue (temporarily) and not smacking the phone around in my scenario leads me to believe this is a dev preview bug.
Yeah it looks like it. Never har trouble before but after updating ro beta it started.
Anyone know if this is a known bug?
its a known bug just restart your phone if gyro isnt working.

Pokemon Go breaking accelerometer/gyroscope on Nexus 6P?

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.

OP2 Screen rotation periodically stops working

Hi folks
I received my OP2 in July 2016, and this issue has been a mild periodic annoyance. As I approach the end of my warranty, I want to be 100% confident that this issue is software rather than hardware... (so rather than a fix, my highest priority is confirming that I do not have a hardware defect)
The issue is that the screen rotation will stop working for most, but not all apps (OnePlus Camera is the sole exception, it seems). It will rotate normally for a couple weeks and then I'll notice in some app, usually YouTube or Facebook first, that the screen orientation won't rotate anymore. Once I notice it in any app, no other app rotates either except the stock camera. I have been experiencing this symptom on-and-off for most of the time I've had the device, spanning multiple OOS releases (currently 3.5.8 and still happening).
A reboot fixes the condition, then it works fine for a week or two and comes back. OnePlus support suggested a factory reset, which I've done pursuing this issue before, and it didn't help (it immediately helped, obviously, but the issue did return on the same schedule as before).
I had my OP2 rooted, but still using the stock ROM otherwise, for several months (to be able to use Adblock). I reverted to 100% stock configuration pursuing this issue, it happened the same before/during/after the time it was rooted.
I have checked out the accelerometer with the app "Test Your Android" and watched the graph in the "gravity sensor" test. When the phone is in its non-rotating state and I rotate the phone, the graph lines cross but the app stays in portrait. This makes me think the phone knows it has rotated. I reboot the phone, redo the same test, and the graph looks similar except the app now rotates as well (ironic, really).
Is there a background service for "screen orientation" similar to how Play Services provides GPS information to other apps? If so, am I right in suspecting that the service responsible for answering the question, "what way is the device oriented currently?" is either not answering, or answering incorrectly?
I would prefer not to go to a third party ROM just to test this as I'm very happy with the current config of my device, other than this issue popping up from time to time. Any input is appreciated.
Thanks!
OOS has a tonne of services running under android system continuously. Screen orientation feedback might be one of them. I haven't used OOS in months. It doesn't seem like a hardware issue since a reboot solves it. If it is too frustrating then try testing it on a custom rom. You can switch back to stock once you are sure it was a problem in OOS or not.
utkarsh102 said:
OOS has a tonne of services running under android system continuously. Screen orientation feedback might be one of them. I haven't used OOS in months. It doesn't seem like a hardware issue since a reboot solves it. If it is too frustrating then try testing it on a custom rom. You can switch back to stock once you are sure it was a problem in OOS or not.
Click to expand...
Click to collapse
The more I think about it, the more stupid it seems to have a device that is rather well-supported by custom ROM devs and to not try some out.
I'll shop around for a ROM and give it a shot. I'm thinking and hoping this is strictly a software issue.
k1shy said:
The more I think about it, the more stupid it seems to have a device that is rather well-supported by custom ROM devs and to not try some out.
I'll shop around for a ROM and give it a shot. I'm thinking and hoping this is strictly a software issue.
Click to expand...
Click to collapse
In case you want suggestions, try these:
Bliss
Halogen
Validus
Lineage 13
Well, I have the same issue on my OP2 intermittently and it does not matter which rom I am using. In addition to OOS, I have had this issue on Marshmallow Cyanogenmod / Nougat Lineage based roms. Sooner or later it always returns. It seems to happen after longer uptime periods. E.g. with OOS3 I had an uptime stretch of 40+ days (without a reboot), so during this time I experienced the autorotation issue multiple times. It seems to get fixed by itself, but then comes back again. A reboot fixes it usually for longer period of time. As I am now on a custom rom, which is updated quite often, at least once of twice a week, the uptime stretches are not that long and I do not experience this issue often. I have noticed that the step counting sensors also stop working intermittently.
On rooted lineage based rom you can manually restart the sensors with following terminal commands:
su
stop sensors
start sensors
Don't know if this works on OOS. I made a tasker task shortcut for this on my homescreen.
Interesting...I have had the problem on-and-off I'd say, sometimes it follows this ~2 week pattern, sometimes it'll go longer than a month with no issues that I've noticed. Of course, it's also fairly rare that I watch videos on my phone and this is the main time that I realize it won't rotate.
Of course, with the current trend being to make all videos square with unnecessary obnoxious text in the letterbox black space, I suppose I'll never need to rotate my phone again </sarcasm>.
Prior to utkarsh102's suggestions I had already flashed AOSPExtended so I'm going to try rolling with this for a short time, if any issues surface (unrelated to my rotation issue) I'll try another ROM. Given that I'm trying to diagnose this issue before my warranty runs out (yeah, shoulda done it sooner, I know) I'll need to have a usable solution that can run stable for weeks uninterrupted to catch this again, if it's going to happen again.
FYI OnePlus support was entirely unhelpful about this issue. They completely disregarded the fact that it is intermittent and was not currently happening when I reported it to them. They were not able to suggest any diagnostic effort I could take to narrow down the issue further. Viewing the accelerometer readings was my own idea, not theirs. That suggestion absolutely should have come from them.
I do know I'm/we're not isolated in having this issue as there are other forum posts on various sites complaining of it.
I'll keep this thread updated with my findings, in the meantime anyone who has experienced this issue please chime in. It would be helpful to present to OnePlus, though I get the impression they won't care as they seem to have classified the 2 as a legacy product at this point. It's not like we're trying to get parts for a dot-matrix printer here.
Edit, October 2017, to provide an update without bumping the thread:
I've been using AOSPExtended on a constant basis since my last update to this thread and while I have experienced a variety of other issues, this particular one with the screen rotation has not affected me. My uptime has never been super long, but long enough at times that I should have seen this issue if it were going to happen following the same pattern as before.

Oneplus 6T software issues

Hello guys,
I bought my 6T a few days ago and have been noticing some annoying software issues:
1. When I unlock my phone it doesn't take me to the application I was using before I locked the screen; it takes me to the home screen.
2. The recent applications keep getting cleared even though I've turned the battery optimisation off.
3. In the lock screen when there's a notification, the ambient display shows the notification but touching on it doesn't turn the screen on. You have to hit the power button or unlock the phone in order to check notifications.
There a couple of other minor issues like apps crashing and then restarting that don't happen too often.
Just wanted to check if others are facing these issues as well and if someone has any solutions.
Those sounds like bugs in the OS, I say this since I'm experiencing the same issues on my OP6 running Open Beta 6 (based off OS 9.0.4 for the 6T).
Have you submitted a bug report on OnePlus feedback page? This way it will get the right people in front and get the issues resolved.
Note2Lover said:
Hello guys,
I bought my 6T a few days ago and have been noticing some annoying software issues:
1. When I unlock my phone it doesn't take me to the application I was using before I locked the screen; it takes me to the home screen.
2. The recent applications keep getting cleared even though I've turned the battery optimisation off.
3. In the lock screen when there's a notification, the ambient display shows the notification but touching on it doesn't turn the screen on. You have to hit the power button or unlock the phone in order to check notifications.
There a couple of other minor issues like apps crashing and then restarting that don't happen too often.
Just wanted to check if others are facing these issues as well and if someone has any solutions.
Click to expand...
Click to collapse
The device and oxygen Pie is pretty new so you gotta give it some time for software update.
Also do you have the tmo variant or the unlocked version?
Because the tmo variant has not gotten any software updates yet.
y2k1ltd said:
Those sounds like bugs in the OS, I say this since I'm experiencing the same issues on my OP6 running Open Beta 6 (based off OS 9.0.4 for the 6T).
Have you submitted a bug report on OnePlus feedback page? This way it will get the right people in front and get the issues resolved.
Click to expand...
Click to collapse
That's a fair point. I haven't done it yet, but I will. Thanks for suggesting it.
harpin14789 said:
The device and oxygen Pie is pretty new so you gotta give it some time for software update.
Also do you have the tmo variant or the unlocked version?
Because the tmo variant has not gotten any software updates yet.
Click to expand...
Click to collapse
I have the unlocked version. You're right it's still pretty new and OnePlus might have jumped the gun a little bit in releasing this in an attempt to be there first OEM to push Pie. Let's hope they fix this in a future update.
I think I finally figured out why the recent apps get cleared. OnePlus has set the background app limit to 16 which is retarded. I remember it was the same on the OnePlus 3 as well. And of course you can't just modify the build.prop file to increase this limit.
It's things like this why we need root. I'm probably gonna have to do it soon if I don't find a way around this.

Categories

Resources