Database Users

[ROM] New official ROM Global V8.5.4.0.MAGMIED released

Hi all
I just received a new OTA update on official Global ROM. New version is V8.5.4.0.MAGMIED.
Release notes only state one entry.
other
Fixed bugs
OTA is 128 MB.

I've got the update now since around 1 hour and everthing is still working. I believe, but maybe that's because of the reboot, that the finger print sensor is a bit faster now. The update fixes various security issues, but based on the date in the About Phone, the WPA2 issue isn't yet fixed.

I updated my girlfriend's phone. The fingerprint sensor is MUCH faster. Previously it failed a lot of times, too. The one issue she encountered was, that there were a lot of ghost touches, but after restart, they were gone and came back one more time. Will report if this repeats.

8.5.4.0 is really outdated now. It still have Marshmallow base.

It's not outdated, on the contrary. It's a very stable and good system now.
Which features of the newer Androids do you miss?

For me is the same software. Same bugs, i don't know what is change. Maybe the new interface when open a system app

Snow24 said:
For me is the same software. Same bugs, i don't know what is change. Maybe the new interface when open a system app
Click to expand...
Click to collapse
I guess/hope they probably didn't introduce new bugs... so why are you complaining? It's nice that they updated the security patch level...

OJK said:
I guess/hope they probably didn't introduce new bugs... so why are you complaining? It's nice that they updated the security patch level...
Click to expand...
Click to collapse
I love Xiaomi philosophy, but the Mi 5s was updated 3 times in one year. I dislike this situation, because I already have Android MM and i can't istall or use some apps. It's not a huge problem, but now there is Android Oreo and I have Marshmallow, with Miui 8, because Miui 9 isn't ready. There are some bugs, and a lot of things that Miui don't fix and i don't understand why. I'm very sad for that, and the only thing that I appreciate is the new security patch, but Miui is too slow with development, for me

Snow24 said:
I love Xiaomi philosophy, but the Mi 5s was updated 3 times in one year. I dislike this situation, because I already have Android MM and i can't istall or use some apps. It's not a huge problem, but now there is Android Oreo and I have Marshmallow, with Miui 8, because Miui 9 isn't ready. There are some bugs, and a lot of things that Miui don't fix and i don't understand why. I'm very sad for that, and the only thing that I appreciate is the new security patch, but Miui is too slow with development, for me
Click to expand...
Click to collapse
But that's a little bit how all the companies do, no? My experiences with HTC, Motorola and now Xiaomi are all similar - in the end, the custom roms were always the best, strangely also in terms of stability, but mostly in terms of safety (security patches). It is kind of a ****ty situation but it's well in line with our economic system, I'd say...

OJK said:
But that's a little bit how all the companies do, no? My experiences with HTC, Motorola and now Xiaomi are all similar - in the end, the custom roms were always the best, strangely also in terms of stability, but mostly in terms of safety (security patches). It is kind of a ****ty situation but it's well in line with our economic system, I'd say...
Click to expand...
Click to collapse
Yes, it's real. My experience is with a Nexus 5, so I was in a perfect situation and now i can't appreciate no one smartphone without pure Android

does anyone else have more problems after the update?
I really regret updating!
Now I have problems with Bluetooth - keep disconnecting or having interference. My multimedia system in car gone crazy. stops playing music, lost wheel buttons commands.
Even with apps that rely on Wifi I have problems I didn't have before.
GPS isn't connecting automatically after I turn it off, until I reboot the device

No problems here, but I clean flashed it via Fastboot. Try to wipe cache/dalvik or factory reset. I need my opinion clean flashing is not a big problem because setting everything up again is quite fast thanks to the build in backup.
Edit: I clean flashed the 8.5.3.0 then updated immediately via OTA. Got that mixed up.

Leni_YO said:
No problems here, but I clean flashed it via Fastboot. Try to wipe cache/dalvik or factory reset. I need my opinion clean flashing is not a big problem because setting everything up again is quite fast thanks to the build in backup.
Edit: I clean flashed the 8.5.3.0 then updated immediately via OTA. Got that mixed up.
Click to expand...
Click to collapse
Thank you.
Does wiping cache delete the device content?
The build in backup cannot handle all my content

wiping cache is totally safe here is a short manual (DONT delete user data or anything else):
1. Switch off your phone.
2. Power on your phone while pressing Volume up button + power button
3. A menu appears on the screen. choose Mi Recovery option.
4. choose your language.(select via volume +/- buttons,and choose via Power button)
5. Now choose Wipe and Reset option.
6. Now choose Clear Wipe cache data option.
7. All Set, done. Reboot your Phone.
Click to expand...
Click to collapse

Leni_YO said:
wiping cache is totally safe here is a short manual (DONT delete user data or anything else):
Click to expand...
Click to collapse
Thank you very much.
I tried to do it now
I get the following options:
Reboot
Wipe Data
Connect with MiAssist
When I choose Wipe Data, The only option on the next menu is Wipe All Data
which doesn't sound so good....
It shows me that it's version 3.0 of Mi-Recovery

flipperx said:
Thank you very much.
I tried to do it now
I get the following options:
Reboot
Wipe Data
Connect with MiAssist
When I choose Wipe Data, The only option on the next menu is Wipe All Data
which doesn't sound so good....
It shows me that it's version 3.0 of Mi-Recovery
Click to expand...
Click to collapse
Hmm okay. Maybe someone else can help you. I come from motorola and at the moment with my mi5s im using twrp recovery. You can also clear the cache from inside miui. In my experience clearing the cache never fixed such big system problems. Factory reset is always the way to go imo even if it's quite annoying.

Leni_YO said:
Hmm okay. Maybe someone else can help you. I come from motorola and at the moment with my mi5s im using twrp recovery. You can also clear the cache from inside miui. In my experience clearing the cache never fixed such big system problems. Factory reset is always the way to go imo even if it's quite annoying.
Click to expand...
Click to collapse
Thank you,
If I won't be able to live with it I'll do a factory reset

Nexus 6P Latest 'O' update Killed messaging & Texting - help

Hey' y'all Color be crazy but....
About 3 days ago I checked for updates OTA, and got a new sequrity patch.
but the last 3 days since...
Phone calls Go right to my voicemail box they dont even ring on my phone....
And my [defualt]texting app constantly shows a little cloud crossed out saying no service
Anywheres I had 4gLTE Is now 3g ONLY and i can only do things on the internet thats it, but its slow as a dog.
Airplane mode on-off doesn't work I dialed that *#*# .. (insertnumbers) #*#* for testing and
switching how my phone recieves signal didn't work,
Factory reset from inside my settings + Hard reset from recovery made 0 difference.
Ill recieve all my texts but cant reply to them by rebooting my phone they all come in at once when my phone turns on but them my message app stops working again
-----------
Called my provider (TOTAL WIRELESS,) They said everything fine on thier end nothing they can do. So I called Huawai, and Verizon... got no where.
So im thinking... Its the update patch, or i need a new sim card.. So where / how Do I get the Nexus 6p's STOCK ROM So I can reinstall and how do i do that?
Should i try that? wait for another patch? or request a new sim.... Because as of right now my phones a brick and i use it for work.

Fluttershy_plays said:
Hey' y'all Color be crazy but....
About 3 days ago I checked for updates OTA, and got a new sequrity patch.
my phones a brick and i use it for work.
Click to expand...
Click to collapse
Your not alone my friend I had the same issue with Aprils update. Just randomly during the day I would stop receiving texts and phone calls. I just assumed I was in some kind of bad zone even though had never happened before. Wasn't until my favorite stock build SuperXe got updated to Mays that I switched and haven't had the problem since. Right now I'm on Lineage 15's June build and wow it has come a long way pretty solid no issues. You will have to do some research on unlocking your bootloader and flashing stock images. You can find them if you search "Google API Nexus 6p." Check out Hiesenbergs tutorials on XDA on returning to stock on the flashing procedure. Its the same for flashing stock images of any month you choose. I got simple fastboot 1.4.3 from XDA as well instead of installing Google's fastboot .

Exodusche said:
Your not alone my friend I had the same issue with Aprils update. Just randomly during the day I would stop receiving texts and phone calls. I just assumed I was in some kind of bad zone even though had never happened before. Wasn't until my favorite stock build SuperXe got updated to Mays that I switched and haven't had the problem since. Right now I'm on Lineage 15's June build and wow it has come a long way pretty solid no issues. You will have to do some research on unlocking your bootloader and flashing stock images. You can find them if you search "Google API Nexus 6p." Check out Hiesenbergs tutorials on XDA on returning to stock on the flashing procedure. Its the same for flashing stock images of any month you choose. I got simple fastboot 1.4.3 from XDA as well instead of installing Google's fastboot .
Click to expand...
Click to collapse
Could you help me find that? not sure 100% on navigation of this website but ill try.

Exodusche said:
Your not alone my friend I had the same issue with Aprils update. Just randomly during the day I would stop receiving texts and phone calls. I just assumed I was in some kind of bad zone even though had never happened before. Wasn't until my favorite stock build SuperXe got updated to Mays that I switched and haven't had the problem since. Right now I'm on Lineage 15's June build and wow it has come a long way pretty solid no issues. You will have to do some research on unlocking your bootloader and flashing stock images. You can find them if you search "Google API Nexus 6p." Check out Hiesenbergs tutorials on XDA on returning to stock on the flashing procedure. Its the same for flashing stock images of any month you choose. I got simple fastboot 1.4.3 from XDA as well instead of installing Google's fastboot .
Click to expand...
Click to collapse
Found his guide but..
I got to step 6 in his guide, rooting. and now my phone wont boot past google logo
--EDIT--
Fixed by going back to stock and starting over.

Fluttershy_plays said:
Found his guide but..
I got to step 6 in his guide, rooting. and now my phone wont boot past google logo
Click to expand...
Click to collapse
Ok first you want to boot up and finish initial setup before rooting. Second you want to root with Magisk 16.0 zip. You don't have to root unless your planning on modifying system files or using a special app. You can fix or unroot by reflashing just the boot.img from the firmwarwe or Rom you are currently running .

Exodusche said:
Ok first you want to boot up and finish initial setup before rooting. Second you want to root with Magisk 16.0 zip. You don't have to root unless your planning on modifying system files or using a special app. You can fix or unroot by reflashing just the boot.img from the firmwarwe or Rom you are currently running .
Click to expand...
Click to collapse
well i got up and running (8.0 no updates yet) and my 4g lte / Texting capabilities ARE BACK!!!!.
Also, Can i still root, APP side? or does it have to be through flash?
thanks for pointing me in the right direction!
Is there a way to report this issue to google so they can fix it?

Fluttershy_plays said:
well i got up and running (8.0 no updates yet) and my 4g lte / Texting capabilities ARE BACK!!!!.
Also, Can i still root, APP side? or does it have to be through flash?
thanks for pointing me in the right direction!
Is there a way to report this issue to google so they can fix it?
Click to expand...
Click to collapse
I'm sure there's a way to root with app but just as easy to flash TWRP and install Magisk. Which has nice easy feature of hiding root and passing safety net. That way you get a certified playstore and still use android pay to name a few. If your interested let me know I can explain the process after flashing Magisk.

Incoming call issues On HavoC and Aex

hey,
is there any one experiencing incoming call issue , from other end if someone calls rings from their side but on phone there is no ring is coming and that calls goes to voicemail

I get that sometimes but only when my phone has been locked for a long time. Feels like calls don't come in because of some doze setting.

Have you find any workaround? i tried to dissable magisk and xposed then also its exist so it not doze issue right ?

alwynjoshy said:
Have you find any workaround? i tried to dissable magisk and xposed then also its exist so it not doze issue right ?
Click to expand...
Click to collapse
Unfortunately I haven't found any solution. It still happens to me sometimes when my phone is locked for a while.

Now i. Am using non treble AeX rom, its okay still now no issues

Try change "preferred network type" to Global. Doing that solved the issue for me.

Some dirty flash updates can cause those issues. I have 2 backups, and one of them is creating this issue. Selecting Global as @christoophat proposed didn't fixed the issue in the failing backup. It actually was always configured as Global. Encryption has nothing to do. Clean flash worked fine. You all having this issue can test it by doing a TWRP backup of your data partition, wipe dalvik/cache/data and reboot. You don't need to go through all the google setup just skip all and test your incoming call.

Oki said:
Some dirty flash updates can cause those issues. I have 2 backups, and one of them is creating this issue. Selecting Global as @christoophat proposed didn't fixed the issue in the failing backup. It actually was always configured as Global. Encryption has nothing to do. Clean flash worked fine. You all having this issue can test it by doing a TWRP backup of your data partition, wipe dalvik/cache/data and reboot. You don't need to go through all the google setup just skip all and test your incoming call.
Click to expand...
Click to collapse
Since I never dirty flash, never even do backups, not sure why you think that here.
And no, my phone (until the latest clean install of LOS 07/23 build I did last night) has never been set as Global default before on this phone, but either LTE/GSM or just LTE
I just tell you what worked on my phone, up to you to try or not. :highfive:

christoophat said:
Since I never dirty flash, never even do backups, not sure why you think that here.
And no, my phone (until the latest clean install of LOS 07/23 build I did last night) has never been set as Global default before on this phone, but either LTE/GSMA or just LTE
I just tell you what worked on my phone, up to you to try or not. :highfive:
Click to expand...
Click to collapse
Sorry @christoophat, I wasn't answering you since you hav already found your fix. As you, I was adding info to bring some light to the issue, thinking on the other members still having the issue. I was asking them to try other things so we all could figure out all the possible causes of this behavior. I am in T-Mobile USA and I don't have the issue. I had to recover an old backup to reproduce the issue.

I am also on TMo USA too.

September 2019 Security update for Mi A2 is now available

69.5MB in size so no major changes are to be expected...

Downloaded it just now...no major changes...no bugs encountered...

Weird noise while switching camera modes seems to have gone

Patched boot of last update ?

parkpark9999 said:
Patched boot of last update ?
Click to expand...
Click to collapse
Stock and patched (Magisk 19.3) images of /boot partition:
Note: I recommend to
- copy stock image to /downloads,
- patch it with Magisk (thus a copy of stock image will be saved in /data for further "Uninstallation of Magisk")
- copy patched image to PC (or take the one attached)
- boot patched image via fastboot
- make "Direct installation" in Magisk
This method will enable you to "Uninstall Magisk" by <Restore partitions> command when preparing to download next OTA

Darshan28 said:
Weird noise while switching camera modes seems to have gone
Click to expand...
Click to collapse
Yes i can confirm that.
Is seems THat WI-Fi Is more stable now also.

ki69 said:
Yes i can confirm that.
Is seems THat WI-Fi Is more stable now also.
Click to expand...
Click to collapse
No, the sound is still there but a lot quieter (tested with a sound meter )

WARNING: Caused my phone to get stuck in a bootloop during update.
I'm not rooted and haven't unlocked bootloader. Trying to find a solution.
Edit: after a bunch of tries and some time charging, it finally booted and displayed a "Couldn't update" error. I'm back to august patch with a working phone. I guess I'll wait for more people to report on this update.
A question: In case my phone gets stuck in a bootloop for good when updating, should leaving the "OEM Unlocking" option enabled be enough to save it and allow me to flash a fresh iso?
I mean, only leave the option enabled, but not actually unlocking the bootloader (I don't want to reset the phone unless necessary).

Wifi has indeed improved a lot! I have now connection to the WiFi with the September update where it did not even find the network with the August update. Big improvement here! It now shows the same behaviour as an Galaxy S7, which is really good with WiFi. Major thing... Thanks Xiaomi!
Edit: it looks like this was only accidentally. On other places WiFi is still far more worse than on other devices. Where other devices find multiple WiFi networks with decent speeds, the Mi A2 find no network at all. If it finds finally one, then the speeds are dramatic. I ditch the phone and I'll go for the S10.

JassyNL said:
Wifi has indeed improved a lot! I have now connection to the WiFi with the September update where it did not even find the network with the August update. Big improvement here! It now shows the same behaviour as an Galaxy S7, which is really good with WiFi. Major thing... Thanks Xiaomi!
Click to expand...
Click to collapse
I'm not sure but seems the range became reduced. Need to test again.

WiFi speeds seem to have increased, camera noise is gone for me. So far no complaints

danannnn said:
WARNING: Caused my phone to get stuck in a bootloop during update.
I'm not rooted and haven't unlocked bootloader. Trying to find a solution....
Click to expand...
Click to collapse
Used to happen with many previous OTA updates to many people. Why should this update be fully safe? That's why experienced stock MiA2 users recommend to keep bootloader and critical unlocked.
danannnn said:
Edit: after a bunch of tries and some time charging, it finally booted and displayed a "Couldn't update" error. I'm back to august patch with a working phone.
Click to expand...
Click to collapse
Good that this method worked for you.... usually works but needs great patience and dedication.
danannnn said:
A question: In case my phone gets stuck in a bootloop for good when updating, should leaving the "OEM Unlocking" option enabled be enough to save it and allow me to flash a fresh iso?
I mean, only leave the option enabled, but not actually unlocking the bootloader (I don't want to reset the phone unless necessary).
Click to expand...
Click to collapse
Yes, enough, but please consider following:
- now with working phone you can save most of your user data to PC (and to Google), then unlock and then restore data;
- when you will be forced to unlock phone in bootloop, you won't be able to save/restore user data
- after unlocking you will have ability to make TWRP backup of your /data partition

Audio is definitely louder.

Aerobatic said:
Stock and patched (Magisk 19.3) images of /boot partition:
Note: I recommend to
- copy stock image to /downloads,
- patch it with Magisk (thus a copy of stock image will be saved in /data for further "Uninstallation of Magisk")
- copy patched image to PC (or take the one attached)
- boot patched image via fastboot
- make "Direct installation" in Magisk
This method will enable you to "Uninstall Magisk" by <Restore partitions> command when preparing to download next OTA
Click to expand...
Click to collapse
Sorry for the question, i'm on 10.0.13.0, can i boot the 10.0.14.0 patched and update, because i uninstalled magisk and all of the modules and the update fails, says it couldn't update.

Anyone thinks that the screen takes quite a while to light up after the fingerprint is recognised?

tatitar said:
Sorry for the question, i'm on 10.0.13.0, can i boot the 10.0.14.0 patched and update, because i uninstalled magisk and all of the modules and the update fails, says it couldn't update.
Click to expand...
Click to collapse
To answer your question, no, you can't update by doing that.
It is highly probable that your system partition have been remounted rw (read/write). For Android to successfully update, it is important for any of the root apps to never remount system as rw.
To check if this is the cause, check Matlog (an app for logcat) after the error when performing the update. Filter "update engine" and check a message in regards to system mounting.
If this is correct, then, to be successful in updating to the September security level, you will need to flash the August's system partition from a fastboot package, and then try the update once again
---------- Post added at 04:28 AM ---------- Previous post was at 04:23 AM ----------
LeChevalierR said:
Anyone thinks that the screen takes quite a while to light up after the fingerprint is recognised?
Click to expand...
Click to collapse
I see that this have a chance to occur when a person updates to a newer patch level. This is based on the messages i have seen in this forum board though it is unknown if it really the cause.
I read that deleting your fingerprints and add them back as new "fixes" this issue. I recommend you to try it out first

Aerobatic said:
...
Click to expand...
Click to collapse
Thanks for the all the explanations.
I guess I'll just keep "OEM Unlocking" enabled for now if its enough to save me from disaster. I don't mind losing my phone data, I consider it transient anyway. I'm just too lazy to set it all up again unless I really need to.
After making sure OEM Unlocking was enabled, that I got fastboot all set up and working, etc., I went ahead and attempted to update again, this time with no issues.

New bug encountered? I was watching a video from YouTube I opened through a WhatsApp link and all of a sudden my back button was there but home and recent apps buttons disappeared and they didn't come back until I reset my phone!

My screen makes some weird noises when it register touch, like squeking or static noise behind the screen, it is hard to explain. It start to hear when touchscreen register touch and it last about 2-3 seconds, then it stop, and when i touch it again the sound is back and so on. It's very annoying

I can do confirm that the camera sound is gone, although I can still hear it if I concentrate enough. It might be what is used to sound before so I can't really tell.
WiFi is definitely improved and it now searches for available networks faster
Overall system speed is improved specially with those awkward keyboard lags in the previous update.
Also LTE Signal got better I can tell
.
.
But I do have a little doubt about the battery life cause my phone had about 14% of charge last night which I forgot to plug in the charger and it was dead in the morning which has never happened before. It usually had at least 5% when that happened before. Still am not sure if that's the real deal so I'm gonna just wait some more to see battery performance.
But the update itself seems stable and bugless enough so it's definitely recommended to install it especially if you're dealing with camera sound...
P.S. : No camera2API nor ARCore

Issue with screen positioning

Just got my OP8 Pro last week and everything was fine until a few days ago. I noticed my screen size is off. It's almost as if it's shrunk. Everything from the top of the screen has dropped about 1mm, so that the camera hole is wrong and the notification bar is below where it should be. I've looked at the dpi, scaling, etc but can't for the life of me find what's changed. Any help would be greatly appreciated.

Did you touch any configurations before that ?
Go to Display > Advanced > Front Camera Display Area and try the option 'hide the front camera' and then go back to 'show the front camera'
see if it fixes the bug.

MoodlePro said:
Did you touch any configurations before that ?
Go to Display > Advanced > Front Camera Display Area and try the option 'hide the front camera' and then go back to 'show the front camera'
see if it fixes the bug.
Click to expand...
Click to collapse
I only set up my phone. I had previously tried switching the front camera display area when I first noticed it was wrong, but it didn't help. Regardless of what settings I use there's always a 1mm or so black area above the status bar.

BRANDENDEUCE said:
I only set up my phone. I had previously tried switching the front camera display area when I first noticed it was wrong, but it didn't help. Regardless of what settings I use there's always a 1mm or so black area above the status bar.
Click to expand...
Click to collapse
It looks like a launcher related problem.
Are you using a custom one of just stock? You could try clearing cache for the launcher in settings - apps and then reboot your phone.
Tell us how it goes.
You might also check your DPI settings (
https://www.reddit.com/r/OnePlus8Pro/comments/jh1x9e
)

Also, if you can take a picture or a screenshot (if it shows) i would highly appreciat it.

MoodlePro said:
Also, if you can take a picture or a screenshot (if it shows) i would highly appreciat it.
Click to expand...
Click to collapse
Using nova or oneplus launcher, it's both the same. I'll see if I can find an extra camera because screenshot doesn't show it

MoodlePro said:
Also, if you can take a picture or a screenshot (if it shows) i would highly appreciat it.
Click to expand...
Click to collapse
Hope this helps.

BRANDENDEUCE said:
Hope this helps.
Click to expand...
Click to collapse
If you're able to do so, clear the cache for both launchers
Update me as always.

MoodlePro said:
If you're able to do so, clear the cache for both launchers
Update me as always.
Click to expand...
Click to collapse
Same as before. I had tried wiping the cache in twrp and it didn't help. I'm trying to get the full zip for the current rom to dirty flash. I'm assuming that will fix the problem, but I can't find anyone who's got it yet.

BRANDENDEUCE said:
Same as before. I had tried wiping the cache in twrp and it didn't help. I'm trying to get the full zip for the current rom to dirty flash. I'm assuming that will fix the problem, but I can't find anyone who's got it yet.
Click to expand...
Click to collapse
it looks like you are not using stock oos or at least some modifications or UI Apps. Some of these apps/mods should be your problem. You are the first on on here reporting this issue so its very likely some of the apps you are using.
I would reset my phone and test every app alone if the issue comes back. Or maybe just deactivate all of them, restart and look what happens.
Stock roms:
[OnePlus 8 Pro][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com
Just in case:
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com

xtcislove said:
it looks like you are not using stock oos or at least some modifications or UI Apps. Some of these apps/mods should be your problem. You are the first on on here reporting this issue so its very likely some of the apps you are using.
I would reset my phone and test every app alone if the issue comes back. Or maybe just deactivate all of them, restart and look what happens.
Stock roms:
[OnePlus 8 Pro][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com
Just in case:
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Click to expand...
Click to collapse
I'm using Oxygen OS 11.0.10.10.IN11AA that I updated right after initial setup. Bootloader unlocked and rooted, swift installer for theming. I've in uninstalled the swift mods and it stays the same. I have some magisk modules, but they were active initially before the issue arose. I did look at the thread for the OOS version, but the newest available is for the last version. As soon as I get my hands on the full zip I'll start from scratch and find out what is causing the issue.

BRANDENDEUCE said:
Just got my OP8 Pro last week and everything was fine until a few days ago. I noticed my screen size is off. It's almost as if it's shrunk. Everything from the top of the screen has dropped about 1mm, so that the camera hole is wrong and the notification bar is below where it should be. I've looked at the dpi, scaling, etc but can't for the life of me find what's changed. Any help would be greatly appreciated.
Click to expand...
Click to collapse
I think after all you've tried I would just MSM back then start over.
Hopefully it's just a very weird glitch although my guess is pointing towards hardware and an alignment issue with the screen..was the device new? Or 2nd hand?
If it's the latter then I'd be having a word, obviously after the MSM wipe, you'll be required to unlock the bootloader again and re-root
It's definitely odd.
If the wipe fails then there may be a calibration tool that enables you to bump the alignment of the screen up a bit, I'm sure dpi changes should have an effect (may need a reboot between changes)
Also change from QHD to FHD, I run in FHD and everything has always scaled really well.

So, the latest update was finally released and I dirty flashed it after disabling all my magisk modules and swift theming, but the issue was still there. I factory reset from twrp and it fixed the problem. All swift theming and modules (viper, Dolby digital, acca, oos call recording) are reinstalled with zero problems. The only thing that I can think of that caused it is an app I used to show battery levels around the camera hole, because everything else is the same. It had to have changed something that even after uninstalling and dirty flashing it didn't revert.

BRANDENDEUCE said:
So, the latest update was finally released and I dirty flashed it after disabling all my magisk modules and swift theming, but the issue was still there. I factory reset from twrp and it fixed the problem. All swift theming and modules (viper, Dolby digital, acca, oos call recording) are reinstalled with zero problems. The only thing that I can think of that caused it is an app I used to show battery levels around the camera hole, because everything else is the same. It had to have changed something that even after uninstalling and dirty flashing it didn't revert.
Click to expand...
Click to collapse
Nice one..