OP2 Screen rotation periodically stops working - OnePlus 2 Q&A, Help & Troubleshooting

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.

Related

SM-N900W8 & CM11 M12 bugs and issues :(

I have a Canadian Note 3 (SM-N900W8), it's KNOX 0x0 rooted and I have CM11 M12 installed. I have been using only the M builds since I got this phone, I didn't even set up Touchwiz when I got it, I rooted and installed Cyanogenmod out of the box.
Now, with the new CM12 builds coming out, what happened to CM11, are they going to fix the remaining issues? Or did they just bail on legacy KitKat users because I'm having TONS of problems and I don't want lollipop, it runs like absolute crap for the nightlies right now and CM11 M12 isn't much better. Bluetooth takes a couple of attempts to connect, when it does my phone runs super slow to the point it force restarts. For instance, if I'm driving around, listening to music on the car stereo, pull over some where, find a new album on Google Music, start playing that, it's all good, do this a few times, every time I use my phone it gets slower and slower until it force restarts and then bluetooth has trouble connecting again. I've tried this on a few other vehicles of different brands and aftermarket stereos and it's the same result.
Audio is all funky when bluetooth is on too, it sounds like robots for the system sounds and if bluetooth drops while it's connected the music starts playing from the phone and sounds all roboty. I always do clean flashes too and the latest Paranoid Android GAPPS every time I reflash, the ROM is fine out of the box, works flawless for the first few days but after awhile, it becomes so bad I have to backup, wipe, reflash, and start over for another few weeks.
Another issue is somewhere between M8 and M12 one of the builds corrupted my SD card, I tossed in a second new card, it was corrupted again, FutureShop won't give me another one and said my phone is breaking them so I'm SD-less right now.
There are also quite a few apps that force close, but always at random, it's never when doing the same thing over and over, for instance, I can be scrolling through G+ and it tells me settings has stopped working, wasn't even using settings, didn't even have it open, haven't clicked it since booting my phone, just randomly stops working for no reason, this also happens all the time with the Camera, it says it just stops working when I haven't even used it and then if I try to use it, it says the camera is disconnected and won't work until I reboot.
I turn my phone off every night while it's charging and turn it back on every morning so every morning it gets a fresh restart, and I have to restart my phone probably 5ish times a day, if I'm using bluetooth more then normal then there's quite a few more unintentional reboots in there as well.
The last issue, which is a known issue is NFC not working, is there a fix for this yet? I kinda miss this feature and with how flawed CM11 is getting I don't know where to turn since they always seemed to be the most stable out of everything I've tried.
Any before anyone says Temasek's CM builds, I tried it, the final for CM11, it was worse then M12, it's exactly the same as M12, but every issue happens more frequently. Also, the pull down menu (when pulling down from the top right to show toggles), the bottoms of the last row was cut off so it didn't look very appealing either, it also used WAY more battery life, I usually get a full day out of one charge, so around 18 to 20ish hours on one charge, with temaseks cm11 I had to charge my phone half way through the day, sometimes my phone would just die on me without me knowing, the battery usage was always Android System.
A new problem that just happened lastnight was Google Keyboard was deleted and only the voice search would work, but "voice search can't be reached" so I couldn't search for another keyboard app from the playstore. I also used the stock GAPPS so AOSP keyboard is replaced with Google Keyboard, I had to reflash again this morning because I couldn't figure out the keyboard thing, there wasn't even a keyboard under languages in settings so I had no options to pick which keyboard to use. When I reflashes this morning I used the Modular GAPPS to it keeps the AOSP Keyboard just in case this happens again but I'm getting really tired of only having a reliable phone for a few weeks.
So, are there any fixes for these issues?
Bluetooth taking multiple attempts to connect
Bluetooth forcing random reboots
Bluetooth making audio from device all funky and sounds like a robot
Corrupting SD cards
Random system apps stopping without me even using or opening them
Google Keyboard vanishing
Are there any stable ROMs I could try for the HLTE? Maybe one that has working NFC? I'm almost thinking of going back to stock *throws up in mouth* but I don't know what else to do with how many bugs there are and Lollipop is only getting worse with the issues.
I'm also trying to avoid Lollipop because everything is white, Note 3 is an AMOLED display, each pixel illuminates on it's own so white screens use WAY more battery life then black ones which was a feature of Temasek's CM11 that I liked, had the option in settings to make everything black like the good old days.
So guys? Really out on my luck here, not sure what the next step is, any fixes for these problems? Any other ROM's I could try? Would flashing a new recovery and reflashing CM11 M12 fix some of these issues? I'm using Xiaoli CWM v6.0.4.7(20140125). Would the fact that KNOX isn't tripped have something to do with this? I really don't understand why there aren't more posts for these issues which leads me to believe I'm one of the only ones experiencing them.
Any help or suggestions would be greatly appreciated
EDIT:
I forgot to mention that when recording audio or video, it's as if the mic gain is set on full so even the slightest sound is pure distortion, normal talking volume and it clips, I found an app that lets me choose between the mics and when I pic the external mic, it's all muffles as if something is covering it but my phone wasn't in a case while I was testing so I'm not sure what the deal is there but I can't record any decent audio with this and when I record in 4K using Cinema FV-5, all the videos turn out looking like Anaglyph 3D but all pink and green, it's really weird and I don't understand why, but 1080p at 60fps works fine.
I am on CM12 and luckily have had no issues at all. I came from KK 4.4.4 and still have the NB7 BL and modem. I tried one of the guys slim ROMs alpha builds but had issues (probably operator error) but I've tried Bluetooth, GPS, WiFi , LTE etc and everything is good. Not sure what to tell you. I do however always wipe internally and d/l all my apps again through WiFi. A bit cumbersome I know but it won't give me any residual data.
Sent from my SM-N900W8 using XDA Free mobile app

Nexus 6p 7.1.1 scroll lag

I'm running stock android 7.1.1 on a Nexus 6p and there's a dramatic lag in scrolling response. When the screen is scrolling quickly and I put down my finger to stop the scroll there is a huge lag before the scrolling stops. About half a second or more. It seems to occur in all apps (and even system settings menus). I've had this problem since buying the phone a couple weeks ago. It's driving me nuts. I never have this problem with my iPad, MacBook or even my ancient nexus 4. The odd thing is that if instead of just putting down my finger I drag my finger slightly (in any direction) then the lag almost disappears, but obviously that's a very awkward thing to do, especially when none of my other devices require it. Does anybody else have this problem (and hopefully a solution)?
I've talked to Google customer support. They told me to clear the cache of every app (yes that does take quite a while) and to clear the partition cache. This did not resolve the problem and now they want me to do a factory reset, which apparently is the last step before hardware warrantee measures. I'd love to know if this is a common problem.
Al--g said:
I'm running stock android 7.1.1 on a Nexus 6p and there's a dramatic lag in scrolling response. When the screen is scrolling quickly and I put down my finger to stop the scroll there is a huge lag before the scrolling stops. About half a second or more. It seems to occur in all apps (and even system settings menus). I've had this problem since buying the phone a couple weeks ago. It's driving me nuts. I never have this problem with my iPad, MacBook or even my ancient nexus 4. The odd thing is that if instead of just putting down my finger I drag my finger slightly (in any direction) then the lag almost disappears, but obviously that's a very awkward thing to do, especially when none of my other devices require it. Does anybody else have this problem (and hopefully a solution)?
I've talked to Google customer support. They told me to clear the cache of every app (yes that does take quite a while) and to clear the partition cache. This did not resolve the problem and now they want me to do a factory reset, which apparently is the last step before hardware warrantee measures. I'd love to know if this is a common problem.
Click to expand...
Click to collapse
Hi, I made some tests in your issue doesn't occur on my 6P with stock 7.1.1.
Sent from my interstellar 6P
same here
Al--g said:
I'm running stock android 7.1.1 on a Nexus 6p and there's a dramatic lag in scrolling response. When the screen is scrolling quickly and I put down my finger to stop the scroll there is a huge lag before the scrolling stops. About half a second or more. It seems to occur in all apps (and even system settings menus). I've had this problem since buying the phone a couple weeks ago. It's driving me nuts. I never have this problem with my iPad, MacBook or even my ancient nexus 4. The odd thing is that if instead of just putting down my finger I drag my finger slightly (in any direction) then the lag almost disappears, but obviously that's a very awkward thing to do, especially when none of my other devices require it. Does anybody else have this problem (and hopefully a solution)?
I've talked to Google customer support. They told me to clear the cache of every app (yes that does take quite a while) and to clear the partition cache. This did not resolve the problem and now they want me to do a factory reset, which apparently is the last step before hardware warrantee measures. I'd love to know if this is a common problem.
Click to expand...
Click to collapse
You aren't the only person who has experienced this issue but I haven't had it happen. I don't know if anyone found a solution but if you do a search in this section you should find a thread very similar to yours with a lot of responses. I think some people experienced the issue after updating to 7.1.1
jhs39 said:
You aren't the only person who has experienced this issue but I haven't had it happen. I don't know if anyone found a solution but if you do a search in this section you should find a thread very similar to yours with a lot of responses. I think some people experienced the issue after updating to 7.1.1
Click to expand...
Click to collapse
Thanks, I'll have a look. (Tried searching before but didn't find anything.)
For me the problem predates 7.1.1
I found the source of my scroll lag issue. I sometimes enable the magnification gesture in the accessibility settings (because I often use a particular transit app that has insanely small icons). I realized that when I have this setting turned on the scrolling gets laggy. Turning off the magnification gesture seems to solve the problem completely. Not sure if there's any workaround other than disabling the gesture setting.

Anyone having issues using Snapchat

Hello everyone, I did some searching on what I'm going to ask but it seems as though all I've read were due to rooting and pertained to logins.
I have a new Moto XPE running the stock Sept. 1st Patch. I can log into Snapchat just fine, my issue lies after I'm using the app. Messages won't load in Snapchat and stories become stock on loading as well. On some Snapchat stories that are loading, after looking at a few images, the screen goes black and is again stuck on loading. Eventually the app crashes and sometimes the phone will crash as well to the point where other apps like YouTube just won't open up and the phone will either reboot on its own or require one from myself manually. Has anyone with a Moto XPE or Moto X Play experienced any of the issues I've described?
Thank you.
Holy crap, I thought it was just me, or that I was just going crazy.
Weird thing is I only started noticing any problems at all when I flashed from stock to a few of the various Nougat builds (CM14, then AICP, back & forth a couple times, then RR) which all have camera driver issues. I noticed half the time the camera wouldn't load upon starting snapchat, or if it did, it would take ~10 full seconds to change from the blank black screen, and sometimes if I would flip it to the front camera or vice versa, it'd just hang indefinitely.
That's the primary reason I switched back to stock a few days ago - I use snapchat A LOT and nougat just doesn't have enough cool features to justify one of my most-used apps basically being crippled to the point of not working the majority of the time. But once I restored my stock backup (not the September security update, the one before it) the camera started up fine in SC but I started getting EXACTLY all the problems you described.
The general consensus seems to be that SC is a super poorly-coded app on Android to begin with, but this must be a recent thing as it makes it downright unusable. I'm actually in the process of going back to 7.1.1 because that still works better than what the app's been doing lately. I wonder if it's happening on devices other than the MXPE?
jDally987 said:
Holy crap, I thought it was just me, or that I was just going crazy.
Weird thing is I only started noticing any problems at all when I flashed from stock to a few of the various Nougat builds (CM14, then AICP, back & forth a couple times, then RR) which all have camera driver issues. I noticed half the time the camera wouldn't load upon starting snapchat, or if it did, it would take ~10 full seconds to change from the blank black screen, and sometimes if I would flip it to the front camera or vice versa, it'd just hang indefinitely.
That's the primary reason I switched back to stock a few days ago - I use snapchat A LOT and nougat just doesn't have enough cool features to justify one of my most-used apps basically being crippled to the point of not working the majority of the time. But once I restored my stock backup (not the September security update, the one before it) the camera started up fine in SC but I started getting EXACTLY all the problems you described.
The general consensus seems to be that SC is a super poorly-coded app on Android to begin with, but this must be a recent thing as it makes it downright unusable. I'm actually in the process of going back to 7.1.1 because that still works better than what the app's been doing lately. I wonder if it's happening on devices other than the MXPE?
Click to expand...
Click to collapse
It happened on my BlackBerry Priv too. I just switched over from that device a few days ago
I'm on stock 6.0.1 and I don't have any big issues with snapchat, the only one is that sometimes camera is very dark at start and I have to go to messages and back to camera to fix that
iks8 said:
I'm on stock 6.0.1 and I don't have any big issues with snapchat, the only one is that sometimes camera is very dark at start and I have to go to messages and back to camera to fix that
Click to expand...
Click to collapse
Yeah same here, it can get a little laggy sometimes for me but I just log out and back in and it works fine.
This might not be here nor there for this specific issue, but if you use Xposed/Snapprefs/rooted etc etc...One thing I noticed that REALLY causes a lot of lag with snapchat is overlays. Especially the FB Messenger app. If you have those chat heads on your screen with Snapchat open as well, things are basically unusable until you get back to the home screen and force close both apps. Could be happening without Xposed as well. Just a thought.
On a side note about Snapchat in general- it has always run like crap on every phone I've owned.
Snapchat kept screwing up, even tried the beta. Decided to try Casper and so far it's working great

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.

OP5 Camera not working, constant crashing/rebooting (I have searched threads etc)

Ever since my update to 9.0.5 my camera hasn't been working, as well as phone has been blacking out, system freezing up, the LED Light turning to a sort of baby blue color until I force reboot it (this bug has been with my phone since my first boot upon a full charge from 0% after unpacking it). I have scoured the forums of here at XDA and official One Plus forums. All other people have similar camera bugs but those are features of the camera bugging out and easily fixed with a cache clearing. My issue is with the system itself, and no amount of clean (Very) flashes results in a fix. If I go into recovery, select all partitions and format those, even repeatedly has this annoying system bug persist. The camera does come back if I revert to 8.1 OTA and custom ROMs, but the security patches are too far behind for me to keep using them. I am posting here to find out if anyone has had this issue and successfully fixed it as it has been over 2 months since I received my OP5 but I cannot use it for any intensive task as it worsens the freezeups and reboots. Further I live in a remote Alaskan village and there isn't even a OP Center close to the state to send it in. No amount of stock flashing fixes it at all and I am about to curse Oneplus for not being able to push out a stable device.:crying: :edit: I forgot to add that the gyroscope no longer functions as well. Not even in the factory testing menu by entering *#808# in the dialer with the stock roms.
arcticphoenix said:
Ever since my update to 9.0.5 my camera hasn't been working, as well as phone has been blacking out, system freezing up, the LED Light turning to a sort of baby blue color until I force reboot it (this bug has been with my phone since my first boot upon a full charge from 0% after unpacking it). I have scoured the forums of here at XDA and official One Plus forums. All other people have similar camera bugs but those are features of the camera bugging out and easily fixed with a cache clearing. My issue is with the system itself, and no amount of clean (Very) flashes results in a fix. If I go into recovery, select all partitions and format those, even repeatedly has this annoying system bug persist. The camera does come back if I revert to 8.1 OTA and custom ROMs, but the security patches are too far behind for me to keep using them. I am posting here to find out if anyone has had this issue and successfully fixed it as it has been over 2 months since I received my OP5 but I cannot use it for any intensive task as it worsens the freezeups and reboots. Further I live in a remote Alaskan village and there isn't even a OP Center close to the state to send it in. No amount of stock flashing fixes it at all and I am about to curse Oneplus for not being able to push out a stable device.:crying: :edit: I forgot to add that the gyroscope no longer functions as well. Not even in the factory testing menu by entering *#808# in the dialer with the stock roms.
Click to expand...
Click to collapse
It's more likely that you have an hardware issue according to your detailed description of the issue. Cause the gyroscope is also needed for proper camera functionality, camera app may crash.
strongst said:
It's more likely that you have an hardware issue according to your detailed description of the issue. Cause the gyroscope is also needed for proper camera functionality, camera app may crash.
Click to expand...
Click to collapse
Yeah it is part hardware and part software. A couple of months ago I used the cracked unbrick tool found here at XDA and I regained most functionality which was lost after upgrading from 9.0.4 - 9.0.5, though I do still get system freeze ups and reboots. But that is from a faulty unit not any of the ROMs.
I apologize for reviving an old post so any mods may close this thread.
arcticphoenix said:
...
I apologize for reviving an old post so any mods may close this thread.
Click to expand...
Click to collapse
THREAD CLOSED on request of OP.

Categories

Resources