Hi! I just wanted to ask if it's possible to downgrade say from build Version 17.1810.2007.165 to Version 17.1810.2005.153 and if so how to go about it without losing all the settings? The reason i ask is because i noticed every time there is a new update the screen mirroring randomly gets messed up in that it becomes low res and fuzzy sometimes. Its quite annoying that they still make this problem since they fixed it in a prior build and it comes back again. Quite annoying. Many thanks
Related
I updated to the latest software this week and since then I'm noticing my phone seems more buggy not enough to piss me off, but enough to bug me a bit.
The main thing that's been weird is how often I'm seeing the force close message for several apps, some of which I don't really use.
Side note: I also experienced a issue where I opened my camera app and saw green lines running vertically down the screen
Just wondering if anyone experience unusual buggy behavior since the update?
The update broke my camera all together. I cannot even open the camera app. It trys to open and then closes back out again. Google talk FCing but not many others. Is there any way to revert back?
hated the update. Now running stock sensation le rom from europe and my sensation is better than ever, will stay with this rom for a while.
Hello XDA-Community!
Im having some trouble with my new Nexus 5. The screen randomly starts to "shake" sometimes when im using it. I dont know if i can explain it well ^^', if you search "Nexus 5 screen shaking" on YouTube you find similar results. But my Problem is not so hard like the Problem of them. Actually my Nexus 5 shakes sometimes when I turn it into Landscape mode or use an emulator (DraStic). It also happened once while i was trying out Minecraft on the Nexus. Mostly it works perfectly but if it happens, it annoys me. I dont know if that happened on previous versions^^, cuz when I received my Nexus, i just "restored" all Apps with that function that u get when you first turn on you'r device after typing in your Google Account. Then i just updated and updated. First to Android 4.4.2 i think, then to 4.4.3, then to 4.4.4 and then finally to Android 5.0 Lollipop. After every Update my Apps were "optimized" for the new Version, guess that's good. I tried to clear the Cache but nothing Special happened. I just hope that thats a Software Problem and not a Hardware Problem, due that Lollipop has some bugs now.
Could you help me fixing it^^, hope you can ;D!
Regards,
Felix
After watching a few YouTube videos on the Galaxy S8 I got a notification that my Note 4 had a software update. The conspiracy theorist in me genuinely tried to stop me updating in case this was the update that will bring me a whole load of annoyances in order to force me to update my phone, but I went ahead anyway and low and behold I've had major issues with my phone ever since.
Main issues are random crashes, slow response times (like a minute or so) and random reboots. Seems to happen mostly when I wake the phone up and the longer the phone has been in sleep, the worse the issues are.
I have done three factory resets, (even they were buggy and at times unresponsive, such as it not rebooting when it was supposed to) but the issue still persists. I have removed the SD Card (advice from another website) but it didn't help.
Current version of the update shows as being N910FXXS1DQC8 / N910FBTU1DPL1 / N910FXXS1DQA1
Am I right in thinking the only way to roll back the update is to root It and install a previous update? Would rather not do that and hope someone has some advice please.....
Ever since updating to ColourOS11, android auto has been freezing on me when the screen is off however activating the screen will unfreeze it.
Is anyone else experiencing this or if anyone knows a fix besides 30m screen timeout.
The issue's been mentioned on a couple of other threads, from what I've read it seems to be a Android 11 issue in general, not just limited to Oppo / ColorOS. Haven't seen a way to fix this so far, seems like one has to wait for an update to fix it and until then keep the screen on...
Craphead said:
The issue's been mentioned on a couple of other threads, from what I've read it seems to be a Android 11 issue in general, not just limited to Oppo / ColorOS. Haven't seen a way to fix this so far, seems like one has to wait for an update to fix it and until then keep the screen on...
Click to expand...
Click to collapse
Yea I had a look through some other threads. Turning off AOD and Fingerprint while screen off seems to somewhat work abiet still glitchly. Been in contact with Oppo who seems to only want me to send the phone into the service centre but I am waiting for Christmas break to be over and send it then otherwise hopefully a update by then but doubts.
I just had the issue, but by leaving it plugged in and letting the connection time out, it reset and connected. Took about a minute.
I finally got the ColorOS 11 update and now Android Auto is having this issue. Really rather annoying as I've only just got a new car and had Android Auto so was enjoying it!
Basically same issue where the car screen just locks up until you unlock the phone screen (i still get audio prompts for directions in google maps etc so Android Auto is still running). Seems to be a standoff between the OEM's and Google. Looking at other forums some OnePlus phones have the same issue (BBK group thing perhaps!)
Google answer...
[FAQ] Can't connect to Android Auto on Android 11 - Android Auto Community
support.google.com
I solved this issue going into developer options and activating the "keep screen on while charging" mode. The display will remain on, but with a very low brightness level.
Hello Guys,
i have a friend with a rog phone 5 with a weird sound bug.
Sometimes every sound that is played becomes a white noise and the phone practically just hisses at you.
I also had that bug one time on my old Samsung with LineageOS, so i think thats a software bug.
The Thing is...is already reinstalled him the Software about 5times. Also fully deletd android with TWRP and reinstalled it with bootloader.
Currently its running the latest version provided by asus on their website.
Does anybody have a idea on that bug. I mean....what could i be that wont be fixed when i reinstall the software.
Doesnt seem like a hardware problem to me.
Also the Problem disappears for a specific period of time after he restarts the phone.
Thanks!
Try to disable AudioWizard (com.asus.audiowizard) temporarily and see if that makes any difference. Also try to downgrade the ROM to a different version. Could still well be a hardware issue..