So ever since I rooted and xposed kit kat, my nexus 7 has had this odd rotation bug. Mind you I only have gravitybox installed. If I leave my tablet in any orientation for about 10 minutes after a reboot, it will get stuck until I reboot again. This only started recently, and I haven't done much to remedy it because I don't want to deal with restoring all my stuff. Is there anything that might fix it short of this?
Same problem
I have been having the same issue since around the kitkat update. Exact same issue actually, can't figure out how to fix it. I've already factory reset and tried to install a different rom and nothing =(. Need to contact asus for warranty i think
Here also often the problem that screen rotation stops working. Which is very annoying for instance when using Flo before sleeptime while loading battery. In that scenario reverse portrait is needed.
When googling a few months ago before KitKat I found in Google Discussion Groups topics with a ridiculous amount of people with same problem starting from Jelly Bean 4.3 (I think). There it appears it is a often occuring Android bug on all Nexus devices. Even factory reset or reflashing firmware not helping. Apparently not fixed in KitKat.
But not fully informed and 100% shure further about this anymore now. Have to reinvestigate. But it is most cerainly not a hardware bug. Otherwise rotation would never work.
Most of the time in my case rotation stops only working for a little while since KK. However since about a week it rotation won't start working again for a long time like while using JB.
Tried lots of things which seemed to work and than later not. Such as shutdown and power on. Soft reset/hard reboot by long pressing power. Etc.
Probably I will now use same temperary solution as in JB. And hoop fix will come finally from Google. That means using a 3rd party rotation app from Play Store during moments Android rotation has stopped working. Not all those apps working though when Android's rotation itself stopped.
Verstuurd vanaf mijn Nexus 7 (2013) met Tapatalk
I installed hd widgets and use the tilt lock control button.
Related
I am experiencing what seems to be a reproducible phone crash while casting Google Play Music to my TV. If the phone goes to sleep while casting and I wake it, hitting volume down or up buttons while on the lock screen crashes the phone. I couldn't replicate the crash while casting YouTube, only Google Play Music. Also, no crashing when adjusting song volume from lock screen while not casting. When the phone crashes it goes straight to the boot animation, no splash screen shown, and gets stuck there. I have to force shutdown to get it to turn off.
Phone is s-off, rooted, running latest stock.
Anyone with a Chromecast willing to replicate this crash? Any ideas what's going on?
Thanks.
xenakis said:
I am experiencing what seems to be a reproducible phone crash while casting Google Play Music to my TV. If the phone goes to sleep while casting and I wake it, hitting volume down or up buttons while on the lock screen crashes the phone. I couldn't replicate the crash while casting YouTube, only Google Play Music. Also, no crashing when adjusting song volume from lock screen while not casting. When the phone crashes it goes straight to the boot animation, no splash screen shown, and gets stuck there. I have to force shutdown to get it to turn off.
Phone is s-off, rooted, running latest stock.
Anyone with a Chromecast willing to replicate this crash? Any ideas what's going on?
Thanks.
Click to expand...
Click to collapse
Yep. I've had it happen to me as well. I've never really tried to see what the issue may be though.
Its happening to me too. Are you using xposed mod to wake with volume button? I am and I'm thinking that might be the cause. I'll try it a little later and report back.
Edit. That's not the cause. I turned off that mod and it still happens.
No xposed mod or anything else. All I'm doing is trying to adjust the volume of the song that is playing, which one should be able to do while casting, and the whole phone crashes. Is this an HTC problem or Google problem? midnight assassin, what ROM are you running?
midnight assassin said:
Its happening to me too. Are you using xposed mod to wake with volume button? I am and I'm thinking that might be the cause. I'll try it a little later and report back.
Edit. That's not the cause. I turned off that mod and it still happens.
Click to expand...
Click to collapse
I am experienced the same issue last night while using Netflix. I tried adjusting the volume while using my chromecast and then my phone reboots into the HTC one screen. I have to hold the power button until it hard reboots.
Sent from my One using Tapatalk
I get this same issue on Verizon HTC One, although it seems the phone doesn't need to be actually asleep, and it will reboot itself - does not need a hard reset from me.
Non Rooted HTC One
I am also having the same issues when trying to change the volume of Play while the screen is off. I have a non rooted Verizon HTC One.
exact same issue with me when using volume rocker after phone goes to sleep while casting Play Music. I am using ATT phone rooted, s-off, running latest ARHD 31.6 rom. this seems to be an issue with chromecast as it only happens when casting.
Thanks for reporting. I'm trying to figure out if the problem is on Google's end or HTC's. My Nexus 7 doesn't have this problem while casting.
I emailed HTC support about it, with a link to this thread. I'll post back if I get a reply.
I've noticed the same issue. I'm running InsertCoin 6.0-5. It took two reboots before I figured out why my phone kept crashing. I've been using my Chromecast for a while, and I only recently went back to a Sense rom. I was running CM 10.2 until recently, and I can't recall having this issue on that rom, but I can't say for certain. I'm sort of glad to see that I'm not the only one having a problem.
Edit: Oh, and I just noticed this is the Verizon forum (came across this thread via Google). I have an AT&T HTC One.
It's still good to know that the problem is not carrier specific.
I did heard back from HTC and they just punted saying that it's a third party app, not their problem, and suggested uninstalling and reinstalling the app, which doesn't fix anything.
Anyone know how to report this to Google?
Sent from my HTC6500LVW using xda app-developers app
xenakis said:
It's still good to know that the problem is not carrier specific.
I did heard back from HTC and they just punted saying that it's a third party app, not their problem, and suggested uninstalling and reinstalling the app, which doesn't fix anything.
Click to expand...
Click to collapse
Typical manufacturer BS. If your OS crashes because of a third party app, then there's something wrong with your OS. A properly designed OS should be incapable of crashing because of a third party app. Never mind the third party in question in this case is Google... If it only crashes under HTC's spin of Android, then HTC broke something and needs to fix it.
I'm tempted to wait until the "sense-ified" release of KitKat comes out to see if that fixes the issue, since I'm waiting on HTC to fix the stupid purple hue low-light camera issue as well.
I have this very same problem, except i dont have to force shutdown. It just reboots sense (takes about 10 seconds) and then all is fine.
I'm rocking a stock (android 4.3) international simlock free unit.
Not rooted, no s-off, no nothing. Fresh out of the box.
Im still having this same problem on my HTC one X running ViperX 4.07. Has anyone found a solution yet?
I've recently experienced a similar issue when casting from the GP Music app to my Sonos speakers. When trying to adjust the volume from within the GP Music app, it causes the phone to reboot. I have an HTC One still running 4.3 (my carrier in the UK dragging their feet a bit!). I was wondering (hoping) whether this is still an issue with 4.4?
Nexus 7 keyboard and on-screen buttons not working
Hey guy, since quite a while, my nexus 7 has been randomly giving me this problem, which only got worse with time. Every now and then the keyboard would refuse to show up when I tap on a textbox. When this happens, my back button would also stop working. Also, YouTube videos would go all black (no video) while the audio continues to play and/or the on-screen controls would refuse to hide after a while.
I googled a bit and found out that greenify and xposed are causing this problem but in my case even getting rid of them didn't solve the problem. I even uninstalled every new àpp, reverted every new changes but no luck.
I'm really getting sick of this problem and this is the last time I'm seeking for any help before I go ahead and format my device. I'm a bit techie (the reason why I don't wanna go the format way) but this one's really gotten to my nerves.
I'm on KitKat 4.4.4 using Pacman Rom (KK RC-3 dev) with the kernel ElementalX v3.4.0.
I've frozen literally every app I could blame for this issue.
Please help me out guys!!!
No one??? Not even a guess??? Come on guys, pleeaaasssseeeee!!!!!
Hey guys!
So just as the subject reads, the phone from time to time can't connect to my camera and I just get a black screen. Switching between the front and back when this happens triggers the error message and tells me to send a diagnostic report to Google. One of the things I tried was to force close the camera process and still nothing. Only fix is to reboot the phone, but eventually in a day or two the camera will crash again.
Just to rule out any kind of corruption, I wiped the phone to factory settings via recovery and the phone still behaves like this. One of the apps I noticed does not play well with the phone is snapchat (current beta). The app is super laggy and wondering if this could cause the camera overall to eventually crash. Any ideas or thoughts are welcome!
Overall I'm kind if disappointed with the performance of the phone over several days. Upon reboot its quick and over a day or two the phone gets pretty sluggish, even locking up at times for a few seconds without being able to do anything. Sometimes exiting an app and going to the main screen takes a solid 5 to 10 seconds.
Yeah the camera app is very, very bugging. Really hoping there'll be an update that fixes the problems with that and 3rd party cameras.
Sent from my Nexus 5X using Tapatalk
I though I was the only one, the camera takes forever to open and bogs the whole system down, I just the l got the security updates and no camera bugs were addressed
Sent from my Nexus 5X using Tapatalk
Actually that's exactly the way my Nexus 4 behaved, which was the main reason I had to replace it now. Hope 5X won't do that, or I'd be pretty pissed off. I thought it was a hardware issue, but now according to what you write I suspect this might relate to some application installed.
I'll add myself to the list. Sometimes It doesn't even make picture, just get stuck and does nothing for a while, then for whatever reason it start shooting a sequence of pointless picture. Many times it take 2 pics in a row, like a not asked, not wanted crappy pointless multishot
Camera was completely fine for me until I got an OTA update 2 days ago and now its completely dog ****. Freezes for a while when I open the app, and crashes if I turn the phone to landscape.
I just rooted my phone and camera stopped working. Reset to default did nothing.
I'm on B29K. Do I need to downgrade?
twiifm said:
I just rooted my phone and camera stopped working. Reset to default did nothing.
I'm on B29K. Do I need to downgrade?
Click to expand...
Click to collapse
How exactly did you root? And if you flashed a modified boot.img, which one fid you flash? Also, what does "reset to default" mean? Does this mean that you flashed the factory image for MMB29K?
Sent from my Nexus 5X using Tapatalk
I have used android O developer preview and downgraded to android 7.1.2 nut now motion sensor is not working.
How to fix the problem
My Nexus 5x was on the DP2 for almost 2 weeks (very satisfied with it), but after updating some apps on Saturday evening i was in a bootloop. Remedied, after updating again my 50+ apps (including Google apps) again bootloop. So i opted out of beta, and am back on 7.12. All radio fine, but sensors not working. I did a factory reset and everything is working fine.
factory reset fixes
Hi this exact situation happened to me only a day earlier. So happy to find this forum post. The factory reset fixed the issue for me too.
Dang, I was hoping there to be another solution then FSR.
Check to see if your Voicemail apps have anything to do with it. I had this problem and fixed it by disabling my voicemail app from shutting the screen when motion sensor is applicable.
Hi, I have nexus 2013 with Android 6.0.1, since this update and issue came all along and I don't know why!
My WiFi, is intermittent, it disconnects and reconnects all the time
All my other sensors are not working anymore, like auto rotation and gyro
screen sometimes is not being responsive, unless I turn it off couple of times
is it a software issue or my unit is dud? it used to work perfectly for couple of years though.
Yup same here!
Ditto on the rotation working intermittently. Works for a minute after restarting then stops working until I reboot. My wifi is solid though.
I am having the exact same issues as OP, doesn't matter which rom/stock.
Ahmed Sarhan said:
Hi, I have nexus 2013 with Android 6.0.1, since this update and issue came all along and I don't know why!
My WiFi, is intermittent, it disconnects and reconnects all the time
All my other sensors are not working anymore, like auto rotation and gyro
screen sometimes is not being responsive, unless I turn it off couple of times
is it a software issue or my unit is dud? it used to work perfectly for couple of years though.
Click to expand...
Click to collapse
I'm in the same situation but I'm not using stock rom. I'm using a custom RR Nougat Rom for almost 2 years, everything was working nice until this happened. WIFI either stops entirely stops working or works intermittently, and auto rotate doesn't work. I downloaded a sensors app from play store to see if they were actually working or not, to my surprise it says no sensors detected. I panicked and did a hard reset, and then it stucks at bootloop (can't get past the four dots, may be the ROM can't find sensors). Flashed countless custom ROMS, stock rom (6.1, 5.0), but still no dice. But then when I was about to give up, I thought I would give the stock rom 4.3 a final try and magically, my nexus successfully boots up with all the sensors working perfectly. Then I re flashed the custom rom back to my device in which all the sensors are working fine (ORIENTATION, GYRO...).
So may be go back to STOCK ROM 4.3 and then see if the problem persists. I see a lot of 6.0 people are facing these issues.
Good luck!