Related
Hi, today suddenly my phone didn't rotate the screen anymore when I rotated the phone to landscape. I had auto-rotate on. This problem had stayed for a while now and I have already rebooted my phone as well as turned off and on auto-rotate. I know the accelerometer is working because I used apps that use the accelerometer, so my guess is it's done software bug. I think it had happened before to me but briefly and it somehow got fixed. I'm wondering if this has happened to someone else and how you fixed it. Thanks!
Sent from my Nexus 4 using xda app-developers app
If u were referring to it auto rotating in the home screen, the stock launcher doesn't not do it
No not the home screen, any screen (browser, Facebook, mail, etc..)
Sent from my Nexus 4 using xda app-developers app
Try an app called ultimate rotate to force rotation in apps as a test
Sent from my Nexus 4 using xda premium
settings accessibility auto rotate
molesarecoming said:
settings accessibility auto rotate
Click to expand...
Click to collapse
Way to read the OP.
This just happened to me....I have auto-rotate checked in accessability and display...any help would be appreciated.
Happening to me now as well. Not sure whats causing it :-/
Auto Rotate
It is happening to me as well.
I don't know if it pertains to you or no as mine is rooted and it does only on AOKP Rom.
For now what I had is to install Screen Orientation app. It lets you toggle Forced Portrait / Forced Landscape mode from notification bar.
And i have checked auto rotation enable in settings.
Open Instagram, it forces portrait..
help
This is happening to me right now but much worse, I've toggled, rebooted, wiped, reflashed, flashed old backups, different kernels, different roms I was originally running AOKP with faux kernel and my auto-rotate had been working fine then I downloaded temple run and I couldn't tilt from side to side, I would re-calibrate but every sensor app I download says that my; Accelerometer, compass, light sensor, proximity sensor, temp, gyroscope, gravity sensor, linear acceleration, and rotation vector sensor don't even exist, the apps say there not there. I have no idea what more to do to reset them or fix them, they were all working fine before and then they just stopped.
Any ideas or information would be appreciated, the last thing I'm going to try is a full Odin flash back to stock everything (if that is even available yet for the nexus 4)
tech.central said:
This is happening to me right now but much worse, I've toggled, rebooted, wiped, reflashed, flashed old backups, different kernels, different roms I was originally running AOKP with faux kernel and my auto-rotate had been working fine then I downloaded temple run and I couldn't tilt from side to side, I would re-calibrate but every sensor app I download says that my; Accelerometer, compass, light sensor, proximity sensor, temp, gyroscope, gravity sensor, linear acceleration, and rotation vector sensor don't even exist, the apps say there not there. I have no idea what more to do to reset them or fix them, they were all working fine before and then they just stopped.
Any ideas or information would be appreciated, the last thing I'm going to try is a full Odin flash back to stock everything (if that is even available yet for the nexus 4)
Click to expand...
Click to collapse
i read something about losing sensors by using the 4.2.2 radio With a 4.2.1 Rom. anyways it's a documented issue. try going through the 4.2.2 threads. i believe that's where i saw it mentioned.
EDIT: here it is!
http://forum.xda-developers.com/showpost.php?p=37977813&postcount=3
searching the thread:
http://forum.xda-developers.com/search.php?searchid=146897726
smacking it worked
read on another forum that "a decently hard smack" would correct it.
they were right, Its working again.
solved mine
in my case, it was an app called gravity screen. uninstalled it, reboot phone, and the auto rotate is enabled now
hello fellow xda-ers
I recently updated to the latest and stable CM10.1 (after using M2,M3, RC3 and RC5) and noticed that my home button stops working after a while. I'm not sure when it started but I think it was with the RC.
I did a search but it didn't yield anything particularly relevant. Is that a known problem?
I just reinstalled everything after resetting all data and it still happening.
thanks in advance for your input,
n
edit: before someone mentions it, I read this thread:http://forum.xda-developers.com/showthread.php?t=2340170 where the user indicates that re-flashing everything and restoring his apps using TB fixed the problem. That's exactly what I did but the problem persists unfortunately.
edit2: the problem seems to be limited to when the app drawer is opened. Home works fine with apps
same thing is happening to me. i was running cm since i bought the phone in February. Decided to flask Franco and now I'm getting this weird touch screen problems. The bottom row where the home button is located will become unresponsive. I decided to go into developer settings and enable "show touches". My phone is sometimes touches without my physical input.
Not sure if kernel related or if my touchscreen coincidentally has given out. I'm gonna try flashing stock kernel and see if that fixes things
nks2105 said:
edit2: the problem seems to be limited to when the app drawer is opened. Home works fine with apps
Click to expand...
Click to collapse
I have the same problem on
Franco M3 and CM10.1 stable, just I'm not sure if it started when I flashed CM stable or Franco M3. Home button doesn't work with app draw open and also it doesn't swap from one homescreen to the default.
However if I got to settings>Launcher>Homescreen>Default screen and change it to another screen then back again the home button works properly but after a few days it stops again.
edit: its as if it just forgets what screen is supposed to be default
Hey,
it seems that today my Note 3's (N9005) gyroscope has broken. It did some glitches and then stopped working. Auto rotate doesn't work in any app.
All gyroscope testing apps shows that rotating front and back works but rotating to left and right doesn't work.
Running latest Omega, 4.4.2
tested many kernels, disabled xposed. Will clean flash if everything else won't work.
Has anyone had the same problem?
Try installing Samsung Hubs.
Sammy move all sensors related thing to that app in 4.4+...
If you dont have that app, sensors will not work...
Mine also like that till I reinstalled that app. And I thought that my sensors were goner....
Crescendo Xenomorph said:
Try installing Samsung Hubs.
Sammy move all sensors related thing to that app in 4.4+...
If you dont have that app, sensors will not work...
Mine also like that till I reinstalled that app. And I thought that my sensors were goner....
Click to expand...
Click to collapse
Thanks, tried that but still not working. Gyroscope needs to be calibrated, I suppose but seems that there's no way how to do that
Sent from my SM-N9005 using Tapatalk
Crescendo Xenomorph said:
Try installing Samsung Hubs.
Sammy move all sensors related thing to that app in 4.4+...
If you dont have that app, sensors will not work...
Mine also like that till I reinstalled that app. And I thought that my sensors were goner....
Click to expand...
Click to collapse
Just to inform, my sensors started working again. I tried all the recover zips which contained the missing hub files, tried to re-bloat but no help. Then, I just watched a Facebook video and tried to rotate it and suddenly rotation began to work. I checked the sensors and all are back online again. Very odd. I have a odd doubt that could facebook or fb messenger app have caused this, because yesterday evening, when the probelms started, facebook and fb messenger force closed and halted the phone, so I had to pull the battery out. And it began to work again now with a rotation in facebook video. Sounds funny though
EDIT: I remembered that I just updated the new looking fb app. Though I have no reasonable explanation what could be the connection between fb app and auto-rotation sensor.
Just wondering if anybody else has this issue.
For some reason, when I set Auto Rotation to OFF (I.E. quick settings tile says "Portrait"), my Z will still auto rotate as normal in any app that usually does.
EDIT: It has started working now for me, after rebooting a few times, but I didn't really do anything special :\
EDIT2: It is random and recurring. However I "calibrated" accelerometer yesterday (26th November) by spinning the phone around a few times on all three axis, so far so good *fingers crossed*
Only apps like E.g. MX Player which have their own internal rotation lock ever work. Other apps like Chrome and Tapatalk and so on will still just ignore the setting and rotate automatically.
Does anybody else experience this on the stock Lollipop ROM? I have it in stock and also now in kamarush's 5.1.1 AOSP build. Possible hardware issue? I don't see how, though, that doesn't make sense!
Thanks in advance.
Sent from Xperia Z via Tapatalk
Having the same problem on my XZ1, it's a shi*** bug .. very very annoying bug .
Well mine has started working randomly, now, after rebooting a few times.
Very strange, I had this bug for a LONG time on stock ROM (but now I'm on a custom AOSP build).
At least I am not the only one who had the same issue, I thought I was going crazy
Only real thing I did was toggle the Auto Rotate setting under Settings > Accessibility (not Display) a few times, didn't solve it but I have rebooted since. Maybe it's just a broken Setting that needs to be switched off > reboot > switch on > reboot > repeat this process until it starts working?
Started happening again. I played with Auto Rotate toggle a few times, now it's the opposite - no matter the setting it will NOT rotate!
I think this issue is specific to kamarush's AOSP build, though. Stock didn't do this.
Sent from Xperia Z via Tapatalk
I have the opposite problem. Phones set to auto rotate but won't rotate.
jmindset said:
I have the opposite problem. Phones set to auto rotate but won't rotate.
Click to expand...
Click to collapse
Yeah, mine sometimes does either way. Right now though, it's working perfectly.
What I did was "calibrate" my accelerometer. This is simply done by rotating the phone on all three axis several times (x, y, z) I.E. rotate the phone several times in all three directions. This might have solved it for me, or could be a coincidence.
Sent from Xperia Z via Tapatalk
CosmicDan said:
Yeah, mine sometimes does either way. Right now though, it's working perfectly.
What I did was "calibrate" my accelerometer. This is simply done by rotating the phone on all three axis several times (x, y, z) I.E. rotate the phone several times in all three directions. This might have solved it for me, or could be a coincidence.
Sent from Xperia Z via Tapatalk
Click to expand...
Click to collapse
Yeah its not always just randomly. Especially when I'm watching YouTube. Thanks for the tip though. I shall give it a try
Yep was random for me too, but so far so good after I spun my phone around on all axis. Fingers crossed. Never had to do this before, though, so it's pretty weird!
Sent from Xperia Z via Tapatalk
so i recently replace my mtxp screen and everything was working perfectly until one day i was watching a youtube video and tried using my navbar buttons and they were unresponsive..did everything from rebooted..clear cache..reinstall rom...same problem..its like the bottom of the screen is unresponsive and only works when screen is locked...
anyone else with the same problem/solution?
Hi, I have the same situation: the screen was replaced some 9 months ago and worked fine until a few days ago, when the navigation bar stopped responding. I think it happened during watching a video (on facebook or YouTube) as in your case. I've also tried everything you did, but for no avail. The interesting thing is that the screen itself is reaponsive in that area e. g. during the Setup wizard or on the lock screen (e.g. the button to switch on the camera is working fine). I think I had some similar issue with another android device (LG 4X) when I was using a non-stock ROM (CM) and there was some issue with the installation of Google Apps. As I'm using the stock ROM for my Moto X Style, my best guess is that it might be a potential Google Play Services update that is causing this issue.
Maybe this theory could be checked by installing a third party ROM without Google Apps (I'm not sure if that is possible) to see whether the navbar works that way or not.
vodanium said:
Hi, I have the same situation: the screen was replaced some 9 months ago and worked fine until a few days ago, when the navigation bar stopped responding. I think it happened during watching a video (on facebook or YouTube) as in your case. I've also tried everything you did, but for no avail. The interesting thing is that the screen itself is reaponsive in that area e. g. during the Setup wizard or on the lock screen (e.g. the button to switch on the camera is working fine). I think I had some similar issue with another android device (LG 4X) when I was using a non-stock ROM (CM) and there was some issue with the installation of Google Apps. As I'm using the stock ROM for my Moto X Style, my best guess is that it might be a potential Google Play Services update that is causing this issue.
Maybe this theory could be checked by installing a third party ROM without Google Apps (I'm not sure if that is possible) to see whether the navbar works that way or not.
Click to expand...
Click to collapse
Hopefully I will figure it out.. It's definitely a software problem triggered by a update or system app.. My work around for now is using a nav bar app from the playstore
vodanium said:
Hi, I have the same situation: the screen was replaced some 9 months ago and worked fine until a few days ago, when the navigation bar stopped responding. I think it happened during watching a video (on facebook or YouTube) as in your case. I've also tried everything you did, but for no avail. The interesting thing is that the screen itself is reaponsive in that area e. g. during the Setup wizard or on the lock screen (e.g. the button to switch on the camera is working fine). I think I had some similar issue with another android device (LG 4X) when I was using a non-stock ROM (CM) and there was some issue with the installation of Google Apps. As I'm using the stock ROM for my Moto X Style, my best guess is that it might be a potential Google Play Services update that is causing this issue.
Maybe this theory could be checked by installing a third party ROM without Google Apps (I'm not sure if that is possible) to see whether the navbar works that way or not.
Click to expand...
Click to collapse
Hopefully I will figure it out.. It's definitely a software problem triggered by a update or system app.. My work around for now is using a nav bar app from the playstore
Hi, I have switched on the "Show touches" feature in the Developer options to see whether the screen is detecting touches in the bottom area of the screen: it actually doesn't. It is not an issue on the lock screen though but it is for the navigation bar. So, it seems it is the hardware that is acting up, after all...
I have found a thread about this issue with a workaround to increase the height of the navigation bar by xposed: https://forum.xda-developers.com/moto-x-style/help/navigation-buttons-issue-t3497985
I'll try either that or by installing a custom ROM that has that option built in - e.g. AICP 12.1 (Android 7.1) seems to have such setting.
https://forum.xda-developers.com/moto-x-style/help/solved-navbar-responding-t3993049
Same problem here - at least in my case also a hardware issue after replacing a broken screen. Thought (as many did) it was software because TWRP, lockscreen etc works, but if you actually try touching only the downmost parts of the TWRP or lockscreen buttons, it won't react. "Show touches" from developer tools also shows touches being registered only just above the normal navigation buttons.