I've seen this reported many times, but have never seen a solid fix for it. I've had my S5 for over a year, been on Marshmallow since it could be installed with Smartswitch, and have had no problems. I first noticed things were off when youtube would no longer rotate, so I started my device. For the first time since I've updated, android told me I was on Custom firmware (On S5 startup Screen) I was rooted previously in Lollipop, but have not seen this before a few days ago, and haven't anymore. Sometimes with restarting the device or clearing the cache rotation will comeback and the sensor app I have downloaded will show they work, but a lot of times after either it wont. I have not tried resetting the phone yet, for lack of time of backing up files, but any input would be great here. I can give any information that is needed.
@OP:
I have had the exact same issue for about a month now. I was running stock Marshmallow 6.0.1 when this started happening. A few days prior I updated from Lollipop and rooted my device, so I thought that might be the issue. In my attempts to solve it, I unrooted the phone, rolled back to stock Lollipop, and even installed CM13, all the while factory-resetting and clearing the cache. Nothing worked so far, and my sensors still "freeze" after a while, until the next time I restart the phone. Meaning it's likely a hardware issue, albeit a very weird one. At least I got CM13 now, which is just so much better than TouchWiz
faurionutz said:
It's hardware problem my friend, I fixed mine by reheating gyro ic
Click to expand...
Click to collapse
That... seems like a good idea, actually. Care to link a guide on how to do that? And did it solve the issue permanently?
faurionutz said:
it's hard to dissasembly this model.by your on, search on youtube for instruction
Trimis de pe al meu SM-G920F folosind Tapatalk
Click to expand...
Click to collapse
Disassembly aside, how do you do the actual reheating/reflow? With a soldering iron? Or did you just stick the whole motherboard into an oven?
I've found guides for taking the S5 apart, but not for reflowing its parts.
Related
My Nexus 10's camera is not working - t goes into the app and all I see is a gray screen. For a while I had an exchange server configured that disabled my camera, so I'm wondering if this could be a residual setting due to that. I performed a factory reset, but to no avail.
Is there a way to perform a harder reset, so that all system files and setting are wiped out?
(I once heard that the build.prop is not overwritten on a factory reset).
Thanks.
Have you tried a different version of Gapps? I had something similar, where the camera would take a minute to startup completely.
Do other camera apps work? Try a free one from the Play Store.
sttovo said:
Have you tried a different version of Gapps? I had something similar, where the camera would take a minute to startup completely.
Do other camera apps work? Try a free one from the Play Store.
Click to expand...
Click to collapse
Nope, I don't think it's a delay. It just doesn't work, even with a 3rd party app I used to use on my phone.
Very strange indeed. Maybe you could reflash the stock ROM. I think the factory reset might not clear the system data for apps. Just a guess though. Beyond that I'm at a loss. Sorry.
sttovo said:
Very strange indeed. Maybe you could reflash the stock ROM. I think the factory reset might not clear the system data for apps. Just a guess though. Beyond that I'm at a loss. Sorry.
Click to expand...
Click to collapse
Correct. If the problem is in the /system partition, a factory reset will never touch it.
camera hang
I got a refurbished N10 a few days ago, I did a stock 4.4. flash and the camera initially was black, then after a few goes it would work for a few seconds then become non-responsive, had to a hard reboot once.
Is this a dud unit I got or a problem others have? Remember - stock 4.4 no special kernel etc. I did have a special kernel but I flashed back to stock in trying to fix the problem but nada.
nigelhealy said:
I got a refurbished N10 a few days ago, I did a stock 4.4. flash and the camera initially was black, then after a few goes it would work for a few seconds then become non-responsive, had to a hard reboot once.
Is this a dud unit I got or a problem others have? Remember - stock 4.4 no special kernel etc. I did have a special kernel but I flashed back to stock in trying to fix the problem but nada.
Click to expand...
Click to collapse
Similar issue. Completely stock N10 on 4.4. Camera works fine after boot but a day or two later it is exhibiting this issue of only showing a completely black screen on the default camera app. Same thing with any other app that uses the camera: blackness. And again a reboot rectifies it for a while. Anyone know what is going on with the camera on 4.4?
I happened to have the same issue (but my camera crashed and notified me), and when I searched for it I got this massive thread on Google's product forum. Guess any Nexus device has a chance of having cam boot issues: https://productforums.google.com/forum/m/#!topic/nexus/z47YrU5rxrc
Verstuurd vanaf mijn Nexus 10 met Tapatalk
I know this has been discussed before but I am also having issues with my Nexus 7 2012 Wi-Fi microphone and they do not appear to be connected to an (obvious) hardware issue. I had this issue some months ago when I had upgraded it to Lollipop OTA (5.0.2 to 5.1.1 turned to be completely slow and buggy messes for me, but I digress). The mic suddenly stopped working and no app could hear me when I spoke so I handed it in for a warranty repair (lucky me, it was on the last day before my warranty expired after 2 years!). I got the tablet back after a fortnight and the mic was working absolutely fine. Seeing as how my warranty had now expired, I decided to unlock my tablet (via Nexus Root Toolkit) and install good old smooth-running 4.4.4 on it. I had no issues for a lot of time, but recently I decided to flash 5.1.1 on it, just to see if it's usable on it. Of course, it was a lot slower than KitKat but before I got around to flashing it back, I realized my mic had stopped working again! Restoring my backup of 4.4.4 had no effect on the microphone so I took drastic measures and reflashed everything with Root Toolkit. The microphone actually started working after flashing 4.4.4 (I think the bootloader was involved as well) and then I restored my backup of the same Android version and the microphone kept on working. After a day or two it stopped again! I thought I had messed it up by using Xposed Framework (I had updated some modules on it) and I went over the same procedure again, seeing as how factory resets and backups had no effect whatsoever. After reflashing and restoring my backup I decided not to do anything with the tablet. The mic was working but... it stopped again, for no good reason a day later. The only thing that seems to (temporarily) fix it is reflashing KitKat in the Toolkit. I even tried disassembling the tablet and unhooking the mic module and putting it back in but to no avail.
I think it's a software related issue, seeing as how a simple reflash fixes the microphone but then it stops working again. Attempting to mess with it on the hardware side does nothing. Anyone else experienced the same problem? Anyone found a permanent fix for it? It kind of my makes my tablet unusable on day-to-day basis, since I use Skype and whatnot on it.
Thanks in advance!
I enrolled to beta programa like 3 weeks ago and everything was just fine, but yesterday after some apps updated the phone started freezing a lot, all the apps started crashing especially WhatsApp and Instagram, when I unlock the phone it takes like 5 seconds, also a lot of times when I go to the home screen after writing something, the keyboard stays on screen and it doesnt hides, I dont know what is happening, if someone could help me I would thank it a lot.
Juandos23 said:
I enrolled to beta programa like 3 weeks ago and everything was just fine, but yesterday after some apps updated the phone started freezing a lot, all the apps started crashing especially WhatsApp and Instagram, when I unlock the phone it takes like 5 seconds, also a lot of times when I go to the home screen after writing something, the keyboard stays on screen and it doesnt hides, I dont know what is happening, if someone could help me I would thank it a lot.
Click to expand...
Click to collapse
Don't mean to scare you, but that is exactly what was happening to me right before going into an unrecoverable bootloop. Nothing I tried revived the device, although there have been some that have been able to. I ended up RMA'ing my device as nothing I did brought it back to life. You might be in a different situation but just giving you a heads up.
*Bump*
Stock 7.1.1 and rooted here. I've been on the official 7.1.1 release for our 6P's since early December, and for the past week or so, I've been experiencing freezing as well. I'd be in the middle of typing in Hangouts, streaming music in the car via bluetooth and Spotify, or just waking the phone up from sleep. For the past few days, I've been getting 3-4 freezes per day.
On rare occasions, I've left the phone alone to settle, and it returns to normal, but more times than not, a hard reset is the only 'fix'; until the next freeze.
I reluctantly wiped the phone, unrooted, flashed stock 7.1.1 and re-rooted all via NRT last night. The phone froze again this morning coming off the charger...
Granted, it decided to restore 528mb's worth of WhatsApp history as soon as I unplugged it (why it didn't restore on charger overnight is beyond me though). Will update if it freezes again.
The phone runs butter smooth with zero issues other than these freezing occurrences though. MO, the 6P is the best all-rounded phone currently available, even if it's a year old already.
Appreciate any help or suggestions!!
That's odd try ex kernel and over clock or try HEBF manager on play store
Quick update. Couldn't bear the multiple freezes per day, so I called Google to ask for help. Apparently I've done everything I can on my end (including a factory reset and updating to the latest firmware), so they sent out a replacement 6P to me free of charge. They'll also be covering the courier/shipping costs for my old 6P too. Fantastic customer service. Kudos to them!! I called them Tuesday morning (20th Dec) Australian time, and received my replacement 6P Friday afternoon (23rd Dec). Very quick indeed
Half a day after setting up my replacement 6P, including updating to 7.1.1, I started getting the same symptoms as my old 6P. Freezing, unresponsiveness, etc. Persisted for another day and had enough. I've since done a full wipe and downgraded back to the final 6.0.1 release, and it's been stable as a rock for 3 days now. No freezes, lagginess, nothing.
So I deduce it might actually be a software issue with 7.1.1, and not a hardware problem. It appears a growing number of Pixel and Pixel XL users are also experiencing random freezes on their new phones running 7.1.1 too...
Looks like I'll stick with 6.0.1 until Google makes a formal announcement and something is done about 7.1.1. I've missed Xposed and GravityBox too, so 6.0.1 is all good. Most importantly, it's stable
Had you ever tried booting into safe mode to see if maybe an app was causing the issue? Maybe a compatibility issue between an installed app(s) and 7.1.1
redduc900 said:
Had you ever tried booting into safe mode to see if maybe an app was causing the issue? Maybe a compatibility issue between an installed app(s) and 7.1.1
Click to expand...
Click to collapse
Thanks for the pro tip. I did consider doing that with the replacement 6P, but the only apps that I had installed were the stock Google ones that came with 7.1.1, WhatsApp, Facebook, Twitter, Instagram and SwiftKey. I just assumed if such popular apps were the cause, a lot more people would have pinpointed them as the problem?
I did however read a few users claiming SwiftKey to be the culprit prior to RMA'ing my old device, but even after uninstalling that from my old phone, I was still getting the freezing issues.
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.
Hello everyone,
I've got a big problem with Compass: It continues spinning around at 360 degrees, It never stops.
Already tried to clear app cache, erase app data, uninstall app update and nothing worked.
I've even waited for MIUI 12 official update but nothing changed (I'm on locked bootloader, official global MI rom..never unlocked, never formatted).
Please help, I don't want to format the whole phone for this problem
thanks in advance
M.N.C. said:
Hello everyone,
I've got a big problem with Compass: It continues spinning around at 360 degrees, It never stops.
Already tried to clear app cache, erase app data, uninstall app update and nothing worked.
I've even waited for MIUI 12 official update but nothing changed (I'm on locked bootloader, official global MI rom..never unlocked, never formatted).
Please help, I don't want to format the whole phone for this problem
thanks in advance
Click to expand...
Click to collapse
I've investigated a bit more in depth about this problem and I found out that:
-some alternative Compass apps downloaded from the Google play store (based on magnetic sensor of the smartphone) actually does work correctly
-the problem seems related to the /persist partition, and I don't know how to fix without flashing a new fastboot rom
If you've not unlocked bootloader and everything is official, then two reasons behind your problem. Faulty sensor because of some mechanical or water damage. Or you're sitting close to strong magnetic field.
Did your phone fall or had water damage? Does the compass still spin when you go outside? And also try calibrating it.
rms112 said:
If you've not unlocked bootloader and everything is official, then two reasons behind your problem. Faulty sensor because of some mechanical or water damage. Or you're sitting close to strong magnetic field.
Did your phone fall or had water damage? Does the compass still spin when you go outside? And also try calibrating it.
Click to expand...
Click to collapse
Thank you for your answer! I've factory reset my phone and problem still here: it seems that persist partition got damaged even on totally official and never unlocked phone, Always updated only when notification came (never forced OTA)!!! It happened when MIUI 11 switched from android 9 to 10, it's incredible. CIT Calibration of gyroscope fails. I'm totally disappointed and I found other people on mi forum Who had my same issue but of course none of them could solve the problem flawlessly without losing widevine L1
M.N.C. said:
Thank you for your answer! I've factory reset my phone and problem still here: it seems that persist partition got damaged even on totally official and never unlocked phone, Always updated only when notification came (never forced OTA)!!! It happened when MIUI 11 switched from android 9 to 10, it's incredible. CIT Calibration of gyroscope fails. I'm totally disappointed and I found other people on mi forum Who had my same issue but of course none of them could solve the problem flawlessly without losing widevine L1
Click to expand...
Click to collapse
Me too has the same problem in my Redmi K20pro. I cant use the compass app, which i needed at work site and now i use a normal compass