Related
Was running Resurrection Remix 7.1.2 on my G5 before flashing the pixel experience 8.1 rom, after flashing it though, it began rebooting after ever 10 seconds or so when booted into the actual os, since this was happening, I restored a backup of RR which was made before flashing oreo, and after restoring this backup my device began showing the same symptoms as the ones I saw on pixel experience, except the reboots had an interval of about 20 minutes, unlike on oreo with 10s, and since this was still happening I decided to flash a stock firmware XT1677 (my device however, is XT1675), and somehow after flashing this stock firmware it was displaying THE EXACT SAME symptoms I saw on oreo and then on RR nougat, so put simply: after flashing oreo, every single rom including stock was rebooting every 10 seconds (except RR with 20 minutes), so what I did was flash TWRP on stock rom (bootloader still unlocked) and flashed RR with the hopes of atleast having a longer interval of reboots, and now whatever rom I flash wont even get past the boot animation, anyone ever heard this happening before, or better yet, know how to fix this?
Sorry for the long paragraph.
I got my 2nd note 5 global last week. The first one is perfectly fine on the same firmware. With the new one I had two issues from the get go.
The screen started flickering when turned to full brightness (this issue was gone after the third factory reset) and the device is heating up which still persists.
I already reached out to the shop I bought from. I heard that with this miui version, there are some issues on other Xiaomi devices but that the 5 pro is fine.
Any chance, that by flashing to an older version of miui this issue could be solved?
For anyone interested I include two videos. One of the phone while charging and one while idle. In both situations the phone was factory reset and no mobile data or wifi on.
Videos were mirrored after the upload and I don't have the original files anymore but you get the idea.
https:// photos.app.goo.gl/fOEf0RYnU56QYymk2
If you unlocked bootloader in your new global version Flash MIUI 10 through TWRP. Hopes it will solve the heating issue.
Thanks for the advice flashed Miui 10, Resurrection Remix and Lineage os all with the same issue. Will try to lock the bootloader again and still waiting for an answer from the shop.
try going developer options,
under background process limit, no processes
under background check, tick only necessary apps, untick those that you do not want to run in background like facebook
I've been having this issue where the touchscreen on my OP 5T will be working just fine but the next second just turn unresponsive to any touch, and no amount of rebooting fixes it.
So far, I've tried using the unbricking tool and restored it to OOS 5.1.3, wiped everything off the phone and tried the latest OOS 9.0.1, and even some custom ROMs like Pixel Experience, both the official Oreo version and some unofficial Pie versions.
I even tried installing custom kernels like the blu-spark kernel and the π kernel.
But here's the thing, all of these work right after making the change but the touchscreen stops working a day later. I'm still on the fence if this is a hardware or a software issue, because (do please correct me if I am wrong) a hardware issue would be if it was totally unresponsive and not work fine after installing a new ROM/kernel, which is not the case here, leading me to assume it has to be something in the software related?
gasburger said:
I've been having this issue where the touchscreen on my OP 5T will be working just fine but the next second just turn unresponsive to any touch, and no amount of rebooting fixes it.
So far, I've tried using the unbricking tool and restored it to OOS 5.1.3, wiped everything off the phone and tried the latest OOS 9.0.1, and even some custom ROMs like Pixel Experience, both the official Oreo version and some unofficial Pie versions.
I even tried installing custom kernels like the blu-spark kernel and the π kernel.
But here's the thing, all of these work right after making the change but the touchscreen stops working a day later. I'm still on the fence if this is a hardware or a software issue, because (do please correct me if I am wrong) a hardware issue would be if it was totally unresponsive and not work fine after installing a new ROM/kernel, which is not the case here, leading me to assume it has to be something in the software related?
Click to expand...
Click to collapse
Same problem. Did you solve this problem?
Has anyone found a permanent solution to this? Or at least a reason? My op 5t also stops responding randomly to the touch. This is really bad.
I also have this problem as well. It seems that many users have this issue. OnePlus should take a close look at it
I have been having this issue for more than 6 months. The problem came after one update during android Oreo if not mistaken (Which update i can't remember)
For my phone, the screen will be unresponsive during the below occasions:
1. After rebooting the phone, touchscreen is unresponsive for up to a minute
2. When browsing pictures in gallery
3. When taking picture using portrait mode
4. When google play is updating apps
5. When google photo is backing up photos.
I am also doubting if is a hardware or software issue, because it only happened in some occasion previously for my case. Tried wipe and install stable/open beta a few times, same thing.
After the latest open beta update, it got even worst, other than the above occasions, the screen start to stop working randomly (be it watching a youtube video or using chrome), its getting annoying as i need to restart my phone a few times a day.
I saw alot of people having this issue, but has yet to raise concern of OnePlus.
I've recently had the same problem, I was still running Lineage 15.1 and had not updated my firmware in months because the official builds switched to 16, then suddenly 2 weeks ago the touch screen stops responding while I was actually using it. Reboots didn't help, clearing cache and flashing lineage didn't help. In the end I somehow got it to work again by flashing the last open beta - but even then it didn't work right after flashing it, I had to leave it over night then it mysteriously started responding again in the morning.
I've just had it happen again and I have tried removing the screen protector and completely discharging the battery as some people on the oneplus forum have reported this helps, but it did not work for me. I really can't be bothered going through the whole process of re-flashing open beta then flashing back to lineage and installing all my apps an restoring my data again, but the only other option at this point is to try take it apart to check the screen is still connected to the motherboard properly....
solution
I also faced this problem, then i tried to degrade it to android oreo, and somehow i never faced touch issue, i think this is a bug in android pie,
karyy said:
I also faced this problem, then i tried to degrade it to android oreo, and somehow i never faced touch issue, i think this is a bug in android pie,
Click to expand...
Click to collapse
I'm not sure about that, the first time I had the issue appear I was still running oreo, as I mentioned, I hadn't updated anything in months due to the lineage nightlies switching to Pie.... That said, certainly seems like most people who have reported it mentioned upgrading to Pie
Facing same issue..
I have a similar issue too..
It started several months ago, when the screen used to randomly stop working, a quick hard reboot usually solved the issue.
But about a month ago, the screen stopped responding altogether and any amount of reboot did not work. So too the device to Oneplus service, there they flashed it to 9.0.7, and the screen started working again, and continued working for a few more hours, until it stopped responding again.
Tried flashing several times using the unbricking tool, but all efforts in vain.
Finally after a month or so, I bought a new phone, and today I just wanted to see if anything has changed on OP5T, and to my surprise, the touch screen started working again.
So this time I enabled USB Debugging, permanently enabled OTG, so that even if the screen stops working, I can use an external keyboard/mouse.
But OP5T is no longer my primary device, and hence I have moved on to a different manufacturer, as I saw absolutely no point in buying another Oneplus and god knows what will happen a year down the line...
Has anyone found a solution to this? I am facing the same problem with my oneplus 5T.
chandle-stick said:
Has anyone found a solution to this? I am facing the same problem with my oneplus 5T.
Click to expand...
Click to collapse
I had the problem. Had to send it back to OnePlus. They replaced the cpu under warrenty. Call 0neplus.
i have this problem on LineageOS 16, in stock is good
k-ninja said:
I'm not sure about that, the first time I had the issue appear I was still running oreo, as I mentioned, I hadn't updated anything in months due to the lineage nightlies switching to Pie.... That said, certainly seems like most people who have reported it mentioned upgrading to Pie
Click to expand...
Click to collapse
I was just searching this issue online. I'm currently facing it as well.
Rebooting the phone makes it go away. I face this issue while charging the phone via official dash charger.
I'm running stock Oxygen OS 5.1.7 running Oreo 8.1.0. I faced this issue 6-8 months ago as well. I cleared 7gb free space in my phone then it started working fine then. My device is 64GB variant. I never updated to Android Pie.
This is a major problem in OnePlus 5 and 5t. I've seen many posts on both XDA and official oneplus forums but found no guaranteed solution so far. I was thinking of flashing custom kernel but then saw here that people are still facing this issue in custom ROMs.
I thought I had solved the problem by installing the RenderZenith kernel, which someone on the oneplus forums recommended in the thread there dealing with this issue... but it has resurfaced after a couple of months without issue. Rebooting does not fix the issue for me, I have to flash a stock firmware, and sometimes reboot a few times, before the touchscreen starts working again. I tried installing CarbonROM instead of Lineage to see if that made a difference but it lasted about a day before the problem reoccurred. I am now going to try a Q-based ROM (probably Carbon) to see if that makes any difference, but I am not hopeful. I have even had the issue occur once while I was still running stock 9.0.9 and had not yet got to reflashing a custom ROM, had to do a full wipe and reinstall the stock ROM again to get it working.
I'm about ready to throw this phone in the bin and buy something new - only problem is I don't know what. Certainly not going to waste money on another oneplus after this debacle but there aren't many other options that are good for custom ROMs. Too bad OOS is such insecure trash and Oneplus as a company cant be trusted, otherwise I might at least see how I go running stock for a while.
k-ninja said:
I thought I had solved the problem by installing the RenderZenith kernel, which someone on the oneplus forums recommended in the thread there dealing with this issue... but it has resurfaced after a couple of months without issue. Rebooting does not fix the issue for me, I have to flash a stock firmware, and sometimes reboot a few times, before the touchscreen starts working again. I tried installing CarbonROM instead of Lineage to see if that made a difference but it lasted about a day before the problem reoccurred. I am now going to try a Q-based ROM (probably Carbon) to see if that makes any difference, but I am not hopeful. I have even had the issue occur once while I was still running stock 9.0.9 and had not yet got to reflashing a custom ROM, had to do a full wipe and reinstall the stock ROM again to get it working.
I'm about ready to throw this phone in the bin and buy something new - only problem is I don't know what. Certainly not going to waste money on another oneplus after this debacle but there aren't many other options that are good for custom ROMs. Too bad OOS is such insecure trash and Oneplus as a company cant be trusted, otherwise I might at least see how I go running stock for a while.
Click to expand...
Click to collapse
Have you tried Affinity kernel? Saw a post here. But it is for OnePlus 5
https://forum.xda-developers.com/showpost.php?p=79256461&postcount=95
archz2 said:
Have you tried Affinity kernel? Saw a post here. But it is for OnePlus 5
https://forum.xda-developers.com/showpost.php?p=79256461&postcount=95
Click to expand...
Click to collapse
No I haven't.... but I am losing faith by the minute here.... screen now stops responding even in TWRP or on a fresh install of the stock OS..... I'd say it's hardware related but seems weird that reverting to stock fixes it... sort of....
k-ninja said:
No I haven't.... but I am losing faith by the minute here.... screen now stops responding even in TWRP or on a fresh install of the stock OS..... I'd say it's hardware related but seems weird that reverting to stock fixes it... sort of....
Click to expand...
Click to collapse
Okay. So you're currently running stock ROM version 9.0.9?
Another query, did this problem occur on your phone in stock Oxygen OS v5.1.7 with Oreo 8.1. 0?
Sent from my ONEPLUS A5010 using Tapatalk
---------- Post added at 08:23 PM ---------- Previous post was at 07:57 PM ----------
k-ninja said:
No I haven't.... but I am losing faith by the minute here.... screen now stops responding even in TWRP or on a fresh install of the stock OS..... I'd say it's hardware related but seems weird that reverting to stock fixes it... sort of....
Click to expand...
Click to collapse
Okay. So you're currently running stock ROM version 9.0.9?
Another query, did this problem occur on your phone in stock Oxygen OS v5.1.7 with Oreo 8.1. 0?
Sent from my ONEPLUS A5010 using Tapatalk
archz2 said:
Okay. So you're currently running stock ROM version 9.0.9?
Another query, did this problem occur on your phone in stock Oxygen OS v5.1.7 with Oreo 8.1. 0?
Sent from my ONEPLUS A5010 using Tapatalk
---------- Post added at 08:23 PM ---------- Previous post was at 07:57 PM ----------
Okay. So you're currently running stock ROM version 9.0.9?
Another query, did this problem occur on your phone in stock Oxygen OS v5.1.7 with Oreo 8.1. 0?
Sent from my ONEPLUS A5010 using Tapatalk
Click to expand...
Click to collapse
I'm not running OOS now, but I have had the issue occur while I was. I am just re-flashing OOS to get the touchscreen to work again, but actually I can't even get the setup wizard to work once the phone boots (hangs on the "just a sec" screen), so I am usually flashing another custom ROM once the screen works again. I managed to get to about 6 hours of normal usage last night before the screen stopped responding again - after fighting with the phone all day and most times not getting much past installing magisk modules.
I am starting to think the problem is related to either Magisk, or the riru kernel hooking modules necessary for Xprivacylua (which is mandatory to install IMO) - I had been using the YAHFA module mostly but yesterday I tried Sandhook to see if it made any difference - that was when I managed to get to 6 hours instead of 30 minutes, but it was also when I went back to Magisk 19.3 instead of installing 20.2. Now that I think back, I am wondering if it was upgrading Magisk from 19.x to 20.x that made the issue resurface after a couple of months without it.... Can't remember for certain, but it seems like the most plausible explanation. I tried flashing Magisk uninstaller this time when the screen stopped, but it didn't help - only reflashing back to stock works (sometimes it even takes a few goes). Whatever the problem is, it seems like it is tripping some hardware related switch which only gets reset when installing stock FW.
the other thought I had was that perhaps the hooking framework is getting in the way - like it intercepts the screen touches before they are processed, but it bugs out for some reason and they never get passed on to the OS. I don't know enough about how it works honestly, or any idea how to go about debugging such a weird problem, so no way to look into it.
Anyway, to answer you other question - I never had the problem with OOS 5.1.7, I have never run stock OOS on my phone, but the first time I had the problem was with Lineage 15.1 Oreo 8.1.0. I can't remember if at that time I was running stock xposed or edxposed.
I'm close to my wits end here. IF the problem turns out to be magisk related, it's pretty much new phone time - I doubt even if I logged a bug report it will get looked at any time soon much less resovled, and I simply refuse to run an android phone without xprivacylua.
k-ninja said:
Anyway, to answer you other question - I never had the problem with OOS 5.1.7, I have never run stock OOS on my phone, but the first time I had the problem was with Lineage 15.1 Oreo 8.1.0. I can't remember if at that time I was running stock xposed or edxposed.
Click to expand...
Click to collapse
Edexposed is for Pie ROMS as there's been no development for Pie from official developer for xposed. Chances are you were running xposed only on Oreo 8.1.0.
Today I flashed Franco Kernel on my phone, been running smooth so far. I used to get non-responsiveness while dash charging specifically. Let's see how it goes. Will keep you updated.
Bugger it... I managed to get to 4 days or so after flashing back to LOS 16.1 / Magisk 19.3 / Edxposed YAFHA / Franco kernel, but it has just crapped out on me again.
This time I has tried a slowly-slowly approach, at first running just the stock OS and apps for a few hours, then gradually started installing magisk, riru, edexposed, then finally xprivacylua - Didn't have any problems up to there. Then I installed pico gapps, and used the Play store to do a fresh install of Mobius Final Fantasy instead of restoring from Titanium backup (this game is actually the only real reason I need gapps at all :-/). Mobius is a PITA because its like a 5Gb download, so it takes a long time to reinstall rather than restore from TB. Anyway it seemed like it was working ok for a few days after the fresh install but I just picked up the phone as couldn't unlock it. I have noticed that often the problem does occur while I am playing the game and I have wondered if there is something about it which makes it more likely to trigger, but it can't be the only thing as it happens even during the setup wizard sometimes.... bloody infuriating.
Anyway... not sure what to do now. Really CBF going through the back-to-stock dance again. Meh.
Hello everybody.
I have an issue with the Poco F3 regarding signal and networking.
After the last update to MIUI 12.5 and later MIUI 13, my phone was having issues making and receiving calls and also using mobile data.
Before those updates, I had no issues whatsoever.
I unlocked my bootloader and decided to try a custom rom, thinking it will solve this issue but nothing has changed.
I have "no service" in areas were many other phones (xiaomi and cheap ones at that etc) have at least 4g. Other times, while I do have service, I can't make or receive calls and even if I can, it's dropping after the first minute or so. Trying to use mobile data is a mess too, working rarely and most of the times I get that exclamation mark and cannot access the internet. It's starting to cause issues at work.
Note, that I use the phone with dual sims from different carriers and the issue is the same. I tried using only a single SIM thinking it might have something to do with dual sims but nothing.
I tried everything, from factory reset, to reseting network settings, airplane mode for 30seconds, custom roms, custom apns etc etc.
The sims work as they should on a poco m3 that I also own, but on the F3 the issue remains.
Now, the issue is much work with android 12, both with MIUI and custom rom (using PixelOS at the moment).
Do you think it is a hardware issue? Should I try an android 11 custom rom and see if the issue is fixed? Is there anything else I should try?
It's driving me crazy and since it's causing work related issues I am thinking of just getting a new phone at this point.
Thanks in advance.
crashpoum99 said:
Hello everybody.
I have an issue with the Poco F3 regarding signal and networking.
After the last update to MIUI 12.5 and later MIUI 13, my phone was having issues making and receiving calls and also using mobile data.
Before those updates, I had no issues whatsoever.
I unlocked my bootloader and decided to try a custom rom, thinking it will solve this issue but nothing has changed.
I have "no service" in areas were many other phones (xiaomi and cheap ones at that etc) have at least 4g. Other times, while I do have service, I can't make or receive calls and even if I can, it's dropping after the first minute or so. Trying to use mobile data is a mess too, working rarely and most of the times I get that exclamation mark and cannot access the internet. It's starting to cause issues at work.
Note, that I use the phone with dual sims from different carriers and the issue is the same. I tried using only a single SIM thinking it might have something to do with dual sims but nothing.
I tried everything, from factory reset, to reseting network settings, airplane mode for 30seconds, custom roms, custom apns etc etc.
The sims work as they should on a poco m3 that I also own, but on the F3 the issue remains.
Now, the issue is much work with android 12, both with MIUI and custom rom (using PixelOS at the moment).
Do you think it is a hardware issue? Should I try an android 11 custom rom and see if the issue is fixed? Is there anything else I should try?
It's driving me crazy and since it's causing work related issues I am thinking of just getting a new phone at this point.
Thanks in advance.
Click to expand...
Click to collapse
Rollback miui first to any android 11 version, see if the issue remains.
Then if you want you can flash custom roms and such... Your firmware got updated to android 12 when you upgraded miui , installing custom ROM won't downgrade it that's why you want to rollback miui
Thank you for your reply.
I need some time to do this proccess since I am practically 24/7 on call, but I will surely give it a shot when I get the chance.
Just a question though. Is it something common with this phone? A quick google search shows it happens with android 12 on the oneplus phones, but I got nothing for the poco f3.
Some time ago, with a similar issue, all I had to do was flash a kernel and it got fixed. Do you think there is a chance it is kernel related?
crashpoum99 said:
Thank you for your reply.
I need some time to do this proccess since I am practically 24/7 on call, but I will surely give it a shot when I get the chance.
Just a question though. Is it something common with this phone? A quick google search shows it happens with android 12 on the oneplus phones, but I got nothing for the poco f3.
Some time ago, with a similar issue, all I had to do was flash a kernel and it got fixed. Do you think there is a chance it is kernel related?
Click to expand...
Click to collapse
No idea... I don't think kernel houses firmware components tho , they live in their own separate partition
You can use DSU Sideloader. This allows you to boot into Android 11 and check Cell-connectivity & Wi-Fi, without touching your Main OS.
Basically, you download the Android 11 GSI, extract the "system.img", set up the app (either through Root or ADB), select "system.img" and Install.
That app utilizes Android's DSU feature, but lets you install any GSI you feed it.
Android has a built-in 'DSU Loader' in Developer Options, but it only lets you install the Android 12 and Android 13 Beta GSI, not older ones like Android 11. ^^
Note: GSI's don't work on Xiaomi.eu Custom ROM. May also not work on other Custom ROMs. ^^
cyanGalaxy said:
You can use DSU Sideloader. This allows you to boot into Android 11 and check Cell-connectivity & Wi-Fi, without touching your Main OS.
Basically, you download the Android 11 GSI, extract the "system.img", set up the app (either through Root or ADB), select "system.img" and Install.
That app utilizes Android's DSU feature, but lets you install any GSI you feed it.
Android has a built-in 'DSU Loader' in Developer Options, but it only lets you install the Android 12 and Android 13 Beta GSI, not older ones like Android 11. ^^
Note: GSI's don't work on Xiaomi.eu Custom ROM. May also not work on other Custom ROMs. ^^
Click to expand...
Click to collapse
That's a cool feature and thank you so much for the reply.
However, when trying it, I get stuck on the Poco logo and then straight to recovery. So I guess it doesn't work on the rom I am using.
Rebooting back to system from TWRP works as it should, so there are no further issues.
Tried the two official images from google, and the result is exactly the same.
crashpoum99 said:
That's a cool feature and thank you so much for the reply.
However, when trying it, I get stuck on the Poco logo and then straight to recovery. So I guess it doesn't work on the rom I am using.
Rebooting back to system from TWRP works as it should, so there are no further issues.
Tried the two official images from google, and the result is exactly the same.
Click to expand...
Click to collapse
Hm, I don't know.
You just need an unlocked bootloader (in most cases apparently).
When it didn't work for me, it was solely because of the Custom ROM Xiaomi.eu. Doesn't work at all there.
You're on Stock MIUI, I think, and it should work there normally. For me it does.
cyanGalaxy said:
Hm, I don't know.
You just need an unlocked bootloader (in most cases apparently).
When it didn't work for me, it was solely because of the Custom ROM Xiaomi.eu. Doesn't work at all there.
You're on Stock MIUI, I think, and it should work there normally. For me it does.
Click to expand...
Click to collapse
That's all true I guess.
But as I stated, I am on the PixelOS custom rom at the moment.
Just to see if the issue was MIUI specific, turning out it isn't.
I will return to MIUI 12.5 when I get the chance regardless.
crashpoum99 said:
That's all true I guess.
But as I stated, I am on the PixelOS custom rom at the moment.
Just to see if the issue was MIUI specific, turning out it isn't.
I will return to MIUI 12.5 when I get the chance regardless.
Click to expand...
Click to collapse
Did you ever get the signal problem solved?
narmak said:
Did you ever get the signal problem solved?
Click to expand...
Click to collapse
No, not at all unfortunately. Tried everything, even downgrading and switching around custom roms.
I figure it's a hardware issue and have since swapped my sim to my older Mi 9 Lite and use that device only for calls and data hotspot.
If, however, you have some solution to propose I will gladly give it a shot!
Hi, I also got myself the Poco F3 in June 2022.
Some days ago (~end of September) it started having little to no signal in places that I usually had good signal coverage.
I use 2 SIMs. I tried any combination of SIM as well as single SIMs.
Signal is bad and even if the indicator shows signal with severals bars, calls are not going out nor can I receive calls.
MIUI is
I thought of resetting the phone but after reading this thread I prefer to return the phone as long as it is still stock rather than wasting my time.
There are several posts about this issue on Amazon as well.
Same thing happening to me. This is a good smartphone but sadly, it wasn't just me that is having the same issue.
Same here. Simcard works fine in my Mi 8 and iPhone 7. Went back from LineageOS to MIUI, but MIUI tells me the Simcard "can't be activated" and doesnt get signal at all. With my Mi 8 i have 4G coverage.
I do have the exact same problem.
Tried different roms A11+A12, MIUI+Custom, even opened it up to check if the antenna cable was loose.
Has anybody fixed that problem?
did you manage to fix it? I had the same problem in pixelOs and now I want to install pixel experience but it worries me
gurripato said:
did you manage to fix it? I had the same problem in pixelOs and now I want to install pixel experience but it worries me
Click to expand...
Click to collapse
i was facing the same problem, it was solved when i flashed Xiaomi.eu 13.0.6.0 via fastboot.
its working perfectly since that, at least in xiaomi.eu. I didnt try any other rom.
Xblade234 said:
i was facing the same problem, it was solved when i flashed Xiaomi.eu 13.0.6.0 via fastboot.
its working perfectly since that, at least in xiaomi.eu. I didnt try any other rom.
Click to expand...
Click to collapse
Thanks for the hint. I will try it myself and report then...
I'm on the latest xiaomi.eu weekly beta and I do sometimes have a signal, but it's really unstable.
Xblade234 said:
i was facing the same problem, it was solved when i flashed Xiaomi.eu 13.0.6.0 via fastboot.
its working perfectly since that, at least in xiaomi.eu. I didnt try any other rom.
Click to expand...
Click to collapse
Are you using 5G or LTE data plan?
Xblade234 said:
i was facing the same problem, it was solved when i flashed Xiaomi.eu 13.0.6.0 via fastboot.
its working perfectly since that, at least in xiaomi.eu. I didnt try any other rom.
Click to expand...
Click to collapse
Problem is still there...
Hi. I hope someone can help me with a problem with GPS locking.
I have a Chinese LE2120 that has been imported into the Uk. The phone shipped with the international version of Oxygen OS 11.2.10.10.LE15AA. This is on Android 11 and works perfectly. There are no issues with obtaining good satellite lock when using GNSS even when indoors.
The problems started when I accepted a system upgrade to Android 12. On Android 12 I am unable to get a satellite lock when using GNSS even when outdoors. The phone will sometimes lock onto 1 satellite, but that's about it. Restarting the phone will sometimes allow GNSS to obtain a good lock, but it never lasts long. This issues makes using any navigation/mapping apps impossible.
To date I have tried multiple factory resets and tried all versions of the Android 12 system updates that have been offered right up to C61, but the problem still persists. Downgrading back to Oxygen OS 11.2.10.10.LE15AA fixes the problem so I don't believe it to be hardware related.
OnePlus technical support in the UK are unable to help as my phone is a Chinese import. I have been able to find one other report of this issue on the OnePlus forums, but it was never resolved.
I would be very grateful if anyone who has the LE2120 and has successfully upgraded to Android 12 without GNSS/GPS issues could share their gps.conf file in vendor/etc so that I can compare my version to a known working version to try to determine if it is a config issue. Alternative if anyone has had similar issues and managed to resolve them then I would be keen to know what the fix involves.
For now I am back on Android 11 with no issues, but it would be good to be able to obtain the latest security patches.
Thanks in anticipation, Dave.
Hello
I vave the same problem please how can i back to Android 11
Ôv
Hi.
Sorry to hear that you are having problems after upgrading to OOS12. I never did managed to to GPS/GNSS working reliably on OOS12.
There are a couple of things to try before downgrading to OOS11. First of all you have to know that downgrading to OOS11 will wipe your phone. All data and self installed apps will be gone so please make sure that you have a good backup of anything important!
First thing I would try is to wipe the cache partition of the phone. It may work and it certainly won't do any harm and you won't lose any data. The thing is I'm not sure how relevant the cache partition is on Android 12, but worth a try. Instrustions here ... https://www.hardreset.info/devices/oneplus/oneplus-9-pro/wipe-cache/ Be certain to only wipe the cache partition and NOT the data partition. If this works for you then great and please post back to let me know.
If there are still GPS/GNSS problems then next I would update the phone to OOS13 (Android 13) and see if the problems are resolved. When you are on OOS12 you should automatically get offered the OOS13 update in the System Update menu option. If not then install the Oxygen Updater App from the Play Store and get the OOS13 update from there. https://play.google.com/store/apps/details?id=com.arjanvlek.oxygenupdater Again, with this option you should not lose any data or apps, but please back anything important up first.
If you still have GPS/GNSS problems then to downgrade to OOS11 please follow these instructions ... https://community.oneplus.com/thread/1534473 Please do remember that this process WILL wipe the phone so backup important data first!
Any problems then please post back here and I'll try to help.
Good luck!