I am on OxygenOS 3.5.6. Few days ago my proximity sensor stopped working. The screen does not switch off automatically when I bring it near my ear during a call. Also it does not adjust the screen brightness in dim and bright light. I have to keep the automatic brightness adjustment off because if I turn it on, it just turns the brightness to lowest even in bright light in surroundings. I tried to check the values of the proximity and light sensors in some sensors diagnostics app, but the entry of proximity and light sensor does not show up at all as if these sensors are not even present in my device. I am sure I was able to see the values of these sensors when they were working fine. I have tried apps like AndroSensor, CPU-Z, Sensors test. What could be the reason. Thanks in advance
Have you dropped the phone recently and caused any damage? It's unlikely, as the oneplus 2 is fairly robust. I mean I'm currently using it with a cracked screen after it fell down a scaffold. And I think only reason screen cracked was a unlucky placed stone dead in the corner.
It might be a software issue? As the diagnostic apps say there isn't anything there. This is just a hunch. I'd suggest backing up your OS in TWRP or what ever you use. And doing a cache wipe.
If that fails maybe try flashing a random rom. And gaps. See if that fixes your problem at all? With out seeing the phone and playing with it there not a great deal I can do.
But try the above.
Archtects said:
Have you dropped the phone recently and caused any damage? It's unlikely, as the oneplus 2 is fairly robust. I mean I'm currently using it with a cracked screen after it fell down a scaffold. And I think only reason screen cracked was a unlucky placed stone dead in the corner.
It might be a software issue? As the diagnostic apps say there isn't anything there. This is just a hunch. I'd suggest backing up your OS in TWRP or what ever you use. And doing a cache wipe.
If that fails maybe try flashing a random rom. And gaps. See if that fixes your problem at all? With out seeing the phone and playing with it there not a great deal I can do.
But try the above.
Click to expand...
Click to collapse
Actually I already did that. I had a nandroid backup of older version of OxygenOS where those sensors were working. I took nandroid backup of current OS and restored the older one. Still couldnt make those sensors work. I havent dropped my phone recently, the sensors stopped working just out of the blue.
Dreckk said:
Actually I already did that. I had a nandroid backup of older version of OxygenOS where those sensors were working. I took nandroid backup of current OS and restored the older one. Still couldnt make those sensors work. I havent dropped my phone recently, the sensors stopped working just out of the blue.
Click to expand...
Click to collapse
Ah I see very odd.
Well I did some searching for you .
There's an xda thread that discusses it found here: http://forum.xda-developers.com/one...overy-teamwin-recovery-project-3-0-0-t3310713 post #2. It comes down to flashing the persist image found in the recovery zip. Which I've only ever done once or twice so sorry I didn't immediately jump to it. In fastboot mode do:
Code:
Fastboot flash persist persist.Img
Its found in the recovery.zip I belive . I hope it helps.
Archtects said:
Ah I see very odd.
Well I did some searching for you .
There's an xda thread that discusses it found here: http://forum.xda-developers.com/one...overy-teamwin-recovery-project-3-0-0-t3310713 post #2. It comes down to flashing the persist image found in the recovery zip. Which I've only ever done once or twice so sorry I didn't immediately jump to it. In fastboot mode do:
Code:
Fastboot flash persist persist.Img
Its found in the recovery.zip I belive . I hope it helps.
Click to expand...
Click to collapse
Thanks for taking time to search that thread however the link you posted is broken. I guess you are referring to this post https://forum.xda-developers.com/showpost.php?p=65367381&postcount=54
The above thread is for H2OS and the persist.Img mentioned in this thread is to roll back to lollipop. I am currently on MM OOS so I guess I cannot use those files.
The TWRP recovery for OP2 are available as .img files only and not as .zip as you can see here https://dl.twrp.me/oneplus2/. So just to make sure if that persist.img is available on recovery.zip, I downloaded the zip file of other device and checked but persist.img was not there. I also checked in the full rom zip of MM OOS and persist.img was not there too. So not sure from where to get that img now.
Also is there a way to make backup of my current persist.img in the device? Because I dont want to break my phone any further while experimenting with these flashings.
Hi, few months back i flashed h2os and flashed few custom roms. but later on i found that i had broke all my sensors even camera app doesnt work. No help from service center. pleaseeee help me
Hi, where i can find a Proximity and light sensors for the OP2?
I have one with custom Firmware. Bud the Sensor whont working anymore.
I have just clean it. But no effect
Related
During an update, (PASSIMG.zip) in hboot I selected yes (to install) then about a second later, my screen
turned black and now, the only thing I can do is to boot in the installed stock rom (FRG33).
My english is not perfect, i'm sorry for that.
1. I Removed my battery after a while. (about 10 minutes)
2. Inserted the battery back in his place
3. Power down + vol down and I'm stock, I can navigate in
the menu but I can't see anything...
Anyone know how I can get my screen back ? OLED vs SLCD ?
Note: I can boot in my rom, the rom is unrooted, my phone is unlocked.
(And yes, I tried to flash recovery and another rom without success. And I can't
find a way to flash hboot again (bad signature)
I'm using the last version of hboot and radio.
If anyone have an idea of how I can fix this, this will be really appreciated.
Thanks.
I'm starting to think than my /dev/mtd/mtd0 is screwed up.
Anyone know where I can get/or generate a image of a normal mtd0 ?
At the moment I'm running debian sid dand SuperOneClick seem to freeze
after trying to chmod rageagainstthecage or psneu..
Note: Yes my screen work when the boot is completed. (but not in hboot/recovery)
bad spl ?
fblodroid
Ok, sorry for the noise, I was able to perform an update via 766a101ae02c.signed-passion-ota-60505.766a101a.zip (renamed to update.zip) and I powered off my phone.
Removed the battery to be sure there is no power at all.
and using some screenshot found on the web.
I was able to perform the update (blindly, this word exist ?) and the phone rebooted
and asked me if I want to update again (google update) I selected yes, the phone rebooted
and, VOILA, I can see again the crappy X logo with an open lock at the bottom.
Thanks again (ok for nothing, but if than can help some people...)
Yes, shame on my english again.
fblodroid
My guess is that you have an SLCD Nexus One, and the passimg installed the .33 HBOOT which doesn't work for them.
I had the same problem when flashing the MIUI-AU rom, screen went black,removed battery and replaced but the phone was dead,I was already thinking which phone to buy then when I connected the N1 to my laptop miraculously the X logo appeared and the rom launched ok
At the moment my phone is working again but I'm still having a camera issue.
About a 1 1/2 month ago I experienced this problem, no flash, no camera, just
a black screen when I try to run anything than use the camera.
Then a day, I was walking on the street and I checked to see if the flashlight was
working and obscured magic occured, the flash was working again but not the camera,
I wiped my phone again, repartitionned my SD card and installed a new rom and the
camera was back to normal.
Now, about a month later, (the problem started yesterday) i'm having the same issue.
I'm persuaded than this problem is related to a firmware problem, something related to
my /dev/mtd/mtd0 (hboot, perpaps ?) I don't know exactly where the camera firmware
is writed in the phone memory (nand)
I wiped and flashed again and again a lot of rom last night and today and the problem
still exist.
No camera/flash at all.
I'm thinking about returning the phone for warranty issue but like I said before, the
phone is unlocked... perpaps I will try to black the screen again and send the phone for
warranty... this way they cannot see (without fastboot) if the phone is locked or not.
If anyone have an idea of what I can do... a rom to recommend ?
Today I tryed to revert hboot without success...
EDIT: At the moment I'm running a rooted rom based on FRG83G.
fblodroid...
Related to my camera/flash problem:
Hum, I think I found the problem, this is hardware related, something seem to be
badly connected in the phone, I tryed too apply some force on the right border of the
phone with the flashlight ON (I previously looked on the web to see where the "contacts/plugs"
are located on the pcb (teardown pictures) and after applying some pressure, the light came ON
and now I can open and stop the "flashlight" mode.
teardown on the way ? I'm thinking about it... but i'll try to flash another rom again to see
if my camera is back.. (like in the past)
EDIT: No camera for the moment and the flashlight app light on the LED only if I select
the option "High Brightnes", ON/OFF are working with this option selected.
fblodroid
FIXED
After a complete teardown of my phone, and a lots of cigarettes..
I found two cables not correctly connected to her pin.
I made a picture, hum, an ugly picture of which cables.
http://img121.imageshack.us/i/icedqlubgg4zzbv2huge.jpg/ (in the red circles, the two pink dots)
And yep, now my camera/flash are working perfectly.
NOTE: the phone is not easily to dismantle, this is at your risk and peril. (time: about ~25 min)
Thanks again and please, ignore my english. I'm thinking about starting a thread
related to this problem. Should I ?
fblodroid
Hi, I have a HTC Desire GSM PVT4 (HTC__203), with the exact same issue as what is described in the original post. When I boot in hboot or recovery the screen is completely black. When I boot in the normal rom the screen works fine. I reflashed a number of RUU's successfully, but the problem remains.
The misc partition is not part of the RUU images, and I did re-flash the misc partition in an attempt to downgrade. Any idea where I can get an image for the misc partition for my device, or where I can generate one?
Thanks,
Hans
fblodroid said:
After a complete teardown of my phone, and a lots of cigarettes..
I found two cables not correctly connected to her pin.
I made a picture, hum, an ugly picture of which cables.
/link/
And yep, now my camera/flash are working perfectly.
NOTE: the phone is not easily to dismantle, this is at your risk and peril. (time: about ~25 min)
Thanks again and please, ignore my english. I'm thinking about starting a thread
related to this problem. Should I ?
fblodroid
Click to expand...
Click to collapse
Hey. I have the same issue you had with the camera, black screen and forced to close when running it. My flashlight works perfectly thoug.
I tried wiping and reflashing diferent ROMs, stock and Cyanogen with no luck. I also followed your lead and disassembled the phone to check all the connectors but the problem persists.
Any idea for me to try? Thanks for your posts anyway.
soylapinta said:
Hey. I have the same issue you had with the camera, black screen and forced to close when running it. My flashlight works perfectly thoug.
I tried wiping and reflashing diferent ROMs, stock and Cyanogen with no luck. I also followed your lead and disassembled the phone to check all the connectors but the problem persists.
Any idea for me to try? Thanks for your posts anyway.
Click to expand...
Click to collapse
Did you managed to fix it ? Be sure to check all the plugs, at best unplug everythings
and disassemble the phone entirely.
Mine is still working perfectly after two years.
fb
Hi, i'm cross-posting this for visibility.
So, i'm completely lost. I was playing around with ROMs and mods (the RAM build.prop, for example), and now all my phone's sensors seem to be stuck.
I have reflashed back to completely stock ROM, taken official sprint update. Tried modded ROM, done factory resets, cleared/wiped everything, and still the issue persists.
It would appear my Gyroscope, Accelerometer, Proximity Sensor, and Compass are all not responding at all.
Right now i'm on rooted stock AOJ6.
Does anyone have any ideas? Maybe a corrupted sensor properties file or something similar like that? I'm completely at a loss.
Any help is appreciated.
Guys, it fixed itself. I booted into safe mode, restarted and all the sensors are working again.
I doubt it had anything to do with safe mode, as the sensors weren't working in safe mode.
I have no idea what could have done it. I wish I had a real answer for you.
Hello,
I've been without sensors nor camera for a while now (almost a year), got broken because an OTA update. Tried downgrading, didn't work.
Yesterday I managed to root and install TWRP, did some research and heard about ''persist'' partition. I've been searching for similar cases but no luck. Also tried deleting sns.reg
Can someone provide me the persist.img stock file? So I can finally fix my sensors.
Broken sensors:
Gyroscope
Ambient light
Accelerometer
Proximity
Fingerprint
Camera Flash isn't working either.
Foxxo990 said:
Hello,
I've been without sensors nor camera for a while now (almost a year), got broken because an OTA update. Tried downgrading, didn't work.
Yesterday I managed to root and install TWRP, did some research and heard about ''persist'' partition. I've been searching for similar cases but no luck. Also tried deleting sns.reg
Can someone provide me the persist.img stock file? So I can finally fix my sensors.
Broken sensors:
Gyroscope
Ambient light
Accelerometer
Proximity
Fingerprint
Camera Flash isn't working either.
Click to expand...
Click to collapse
Solved, download the firmware version you have here and look for persist.img. The firmware comes with it but the install script doesn't use it. Just flash it:
Code:
fastboot devices
fastboot erase persist
fastboot flash persist persist.img
fastboot reboot
Hello friend,i have similar problems,apart from fingerprint sensor,all my sensors and cameras,camera light are not working,will i loose imei numbers if i flash the persist img ? i dont know how to flash persist img,can you help me please?
Edit: hi i actually fixed my problem by flashing persist.img, all sensors and cameras are working now
Thank you so much
I would like to thank you for this solution, finally, after 2 days trying I have my ZS570KL alive and working faster, I had to try rooting, then it was bricked for some hours, finally I got it rooted, but after deleting that persist/sensors/and.reg it was the same... until i found this thread, everything works good!!! thank you very much
3sgebeams said:
I would like to thank you for this solution, finally, after 2 days trying I have my ZS570KL alive and working faster, I had to try rooting, then it was bricked for some hours, finally I got it rooted, but after deleting that persist/sensors/and.reg it was the same... until i found this thread, everything works good!!! thank you very much
Click to expand...
Click to collapse
Did you also have broken sensors issue and it is fixed now? I want to try it on my ZS570KL too, but is there a persist.img for this phone?
DIXES said:
Did you also have broken sensors issue and it is fixed now? I want to try it on my ZS570KL too, but is there a persist.img for this phone?
Click to expand...
Click to collapse
Depending on your OS version yes, contact me on Telegram @GuerrillaRadi0 (the last character is zero) maybe I can help you, after I fixed the problem I configured fingerprint security and the problem came back, so I tried to flash persist.img again and it didn't work, so I got the raw rom of the Oreo version I have; WW-15.0210.1810.73, which comes with its own ADB, and flashed from there, the same raw rom has the persist.img. After that all sensors worked again, so I configured fingerprint security again just to be sure, and again I lost all the sensors, but after deactivate fingerprint again everything worked fine, I guess I have some hardware issue related to fingerprint sensor, I guess it was because a technician opened the phone to replace screen and battery 2 months ago. I always used fingerprint so I need to go back to pattern.
Good luck
After some days without any issue the problem came back, I flashed persist.img twice and it worked, but about 3 days ago I can't solve this flashing persist.img, I tried wiping everything, downgrading to Nougat, then flashing Oreo, with TWRP and via flashtool, no solution, any other idea?? all sensors are not working.
Thanks in advance
Hi all,
I'm new to the device so I'm maybe doing something wrong but I don't think so. I got the device with a terribly cracked, I flashed Pixel Experience (Android 10) as it's what I've had on my Nexus 5x, everything was working fine so I proceeded to replace the screen. I replaced it with one from Aliexpress which seems legit.
The phone then wouldn't boot, or seemed not to boot. I saw the splash screen then a black screen. The system did boot as I could see the capacative keys light up and sounds working, I just couldn't see any image on the screen. After a while trying to flash other ROMs and other TWRP versions (at this point TWRP showed up as a black screen too) I found that the following solution solved my problem.
https://forum.xda-developers.com/mi-a1/how-to/solved-mi-a1-bootloop-t3973131
This is fine, I can use the stock ROM and update it to the latest version but cannot use any AOSP based ROMS and still cannot use any other recovery apart from the one used to solve the "bootloop".
Does anyone have any idea how I can solve this? I thought the screen was maybe a weird version that needed some additional drivers but the strange thing is that it works for the stock ROM.
Regards,
Simon
Hi:
simonkerr said:
Hi all,
I'm new to the device so I'm maybe doing something wrong but I don't think so. I got the device with a terribly cracked, I flashed Pixel Experience (Android 10) as it's what I've had on my Nexus 5x, everything was working fine so I proceeded to replace the screen. I replaced it with one from Aliexpress which seems legit.
The phone then wouldn't boot, or seemed not to boot. I saw the splash screen then a black screen. The system did boot as I could see the capacative keys light up and sounds working, I just couldn't see any image on the screen. After a while trying to flash other ROMs and other TWRP versions (at this point TWRP showed up as a black screen too) I found that the following solution solved my problem.
https://forum.xda-developers.com/mi-a1/how-to/solved-mi-a1-bootloop-t3973131
This is fine, I can use the stock ROM and update it to the latest version but cannot use any AOSP based ROMS and still cannot use any other recovery apart from the one used to solve the "bootloop".
Does anyone have any idea how I can solve this? I thought the screen was maybe a weird version that needed some additional drivers but the strange thing is that it works for the stock ROM.
Regards,
Simon
Click to expand...
Click to collapse
I'm in the same situation. I think these screens are not 100% compatible so it seems a hardware issue.
Maybe using vendor partition but i'm so stucked as you.
My phone can't hotboot any official recovery although i can boot flashed recovery only if i boot slot a not slot b.
Stock roms boot always using slot a but tried Lineage (thats uses slot b) and got always black screen.
I'll keep reading and trying to solve it.
Regards.
simonkerr said:
Hi all,
I'm new to the device so I'm maybe doing something wrong but I don't think so. I got the device with a terribly cracked, I flashed Pixel Experience (Android 10) as it's what I've had on my Nexus 5x, everything was working fine so I proceeded to replace the screen. I replaced it with one from Aliexpress which seems legit.
The phone then wouldn't boot, or seemed not to boot. I saw the splash screen then a black screen. The system did boot as I could see the capacative keys light up and sounds working, I just couldn't see any image on the screen. After a while trying to flash other ROMs and other TWRP versions (at this point TWRP showed up as a black screen too) I found that the following solution solved my problem.
https://forum.xda-developers.com/mi-a1/how-to/solved-mi-a1-bootloop-t3973131
This is fine, I can use the stock ROM and update it to the latest version but cannot use any AOSP based ROMS and still cannot use any other recovery apart from the one used to solve the "bootloop".
Does anyone have any idea how I can solve this? I thought the screen was maybe a weird version that needed some additional drivers but the strange thing is that it works for the stock ROM.
Regards,
Simon
Click to expand...
Click to collapse
Have you made any progress?
gsausalito said:
Have you made any progress?
Click to expand...
Click to collapse
Thanks for your interest but I've made no progress and actually given up on it. I'm sure the issue could be resolved by buying a new, more compatible screen but I'm not going to put any more money into the phone.
As far as the software solution goes, I've tried almost every combination of ROM + Kernel i can think of but the only thing that works is the stock ROM.
I'm going to close this thread as I don't think it's much use to anyone.
Regards
Sorry for posting here, but i am in the same and i noticed that flashing canting 4.9 kernel gives display for like 8 seconds after screen turns off. May it be a kernel config issue? if anyone in this forum could answer this i could try and change it. Also flashing stock kernel on custom rom solves the problem but makes other thing fail
Hello, I've got the same issue. Is there any solution ? Or, at least, any clue to work on it ?
EDIT: I finally done it!
with this kernel (OC) : https://forum.xda-developers.com/t/...rkernel-v3-1-nonoc-and-oc-12-11-2020.4186317/
And this rom : https://forum.xda-developers.com/t/rom-11-0-official-crdroid-7-1-tissot-13-11-2020.4195351/
I installed this kernel, cause you was saying it is probably a kernel issue, so I tried to look for most recent kernel.
And then, it worked, so I think you was right.
I can't be sure it will work with all ROM, but I think.
Hello Mi A1 friends.
So yesterday I decided to change my crack LCD screen and to my surprise the phone boots into Xiaomi Logo and then after that its just a black screen. Message and other notifcation sounds still come in which means that the phone mange to boot into home screen, just with nothing to display. At the time of changing screen, I am on stock kernel and Pixel Experience 10.
Gonna flash back to stock pie(9) rom and see how it goes from there.
Deezio said:
Hello, I've got the same issue. Is there any solution ? Or, at least, any clue to work on it ?
EDIT: I finally done it!
with this kernel (OC) : https://forum.xda-developers.com/t/...rkernel-v3-1-nonoc-and-oc-12-11-2020.4186317/
And this rom : https://forum.xda-developers.com/t/rom-11-0-official-crdroid-7-1-tissot-13-11-2020.4195351/
I installed this kernel, cause you was saying it is probably a kernel issue, so I tried to look for most recent kernel.
And then, it worked, so I think you was right.
I can't be sure it will work with all ROM, but I think.
Click to expand...
Click to collapse
Sry for reply to an old post, but how did you do it? How did you flash kernel when you can't enter twrp because of screen issues? I have exact the same problem, where stock rom works but everything else cause blank screen. Also can't boot to twrp - probably the same reason.
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..