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...
Related
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.
Hey,
I have some minor and major lag issues (freezes and crashes), sometimes I even have to force restart the phone.
It happens with most of the customs ROMs that I have tried (HavocOS, ShapeshiftOS, Pixel Extended, etc.) but not every ROM (the only ones where it doesn't occur are ArrowOS and xiaomi.eu I think)
Even after flashing multiple times (mi flash + Clean flash), it happens with multiple apps, so I don't think it's apps related (maybe magisk or TWRP), and not ROM too.
Is anyone facing those issues, or is there any solution or thing that I can do to solve this problem.
Also, I'm having issues collecting logs because it is happening randomly and when it happens the log app I use crashes, but it is always the same issue (ANR Input dispatching timed out (...))
I have one set of logs where I got freeze (5-10 seconds) multiples times, I will attach the file.
I can provide anything to help solve this annoying problem.
Thanks in advance
faced that problem too with app Greenify (xiaomi.eu rom + Twrp Alpha +Magisk 23)
Still a pain to have to deal with that, is anyone here ready to help ?
CRNO said:
faced that problem too with app Greenify (xiaomi.eu rom + Twrp Alpha +Magisk 23)
Click to expand...
Click to collapse
Don't use it. That and Hyperion were on my stock Note 10+ that got boot looped twice, back to back, grrrrrr. Removed both on the 3rd load and still running that load over a year latter.
When you're seeing that kind of behavior you're just one reboot away from a boot loop
Havoc os was the only ROM with freeze's after the phone went in sleep mode, apps like YouTube freezing then. But on the other roms I didn't had that and i tested everyone on havoc I have installed the ROM 2 times with different firmwares but always a freezing of apps after deep sleep
r3sp said:
Havoc os was the only ROM with freeze's after the phone went in sleep mode, apps like YouTube freezing then. But on the other roms I didn't had that and i tested everyone on havoc I have installed the ROM 2 times with different firmwares but always a freezing of apps after deep sleep
Click to expand...
Click to collapse
Too bad I have to install others ROMs, I much prefer Havoc. But weird that it also appears with other ROMs
I have been having similar issues. I'm from the US and it happens often when I am using mobile data.
Shmi117 said:
I have been having similar issues. I'm from the US and it happens often when I am using mobile data.
Click to expand...
Click to collapse
+1 same here
All pixel based custom roms crash while I'm on mobile data. I think it's a modem issue.
NonoBow85 said:
Too bad I have to install others ROMs, I much prefer Havoc. But weird that it also appears with other ROMs
Click to expand...
Click to collapse
I have been using havoc latest build for close to 2 weeks. I didnt encounter any freeze though
aravreddy2231 said:
+1 same here
All pixel based custom roms crash while I'm on mobile data. I think it's a modem issue.
Click to expand...
Click to collapse
Same here in BC. I have found it seems to happen with LTE with ArrowOS (I haven't tried any other custom ROMs). I haven't had the problem occur at all on H+.
If you are rooted, check /sys/fs/pstore/console-ramoops, or dump logcat/bugreport if you aren't rooted, and search for "crash". On my device, it says that my modem crashes which causes every CPU core to stop and reboot.
Shmi117 said:
If you are rooted, check /sys/fs/pstore/console-ramoops, or dump logcat/bugreport if you aren't rooted, and search for "crash". On my device, it says that my modem crashes which causes every CPU core to stop and reboot.
Click to expand...
Click to collapse
I will try that later, thanks
I got that if it can helps
After some research, I think the problem is caused by @manuelbianco tree for alioth, that is widely used and correspond to which ROMs I have problem with.
Still doing some research on how to solve this because it removes ROMs that would like to use.
If anyone knows anything, I would like to hear it.
NonoBow85 said:
After some research, I think the problem is caused by @manuelbianco tree for alioth, that is widely used and correspond to which ROMs I have problem with.
Still doing some research on how to solve this because it removes ROMs that would like to use.
If anyone knows anything, I would like to hear it.
Click to expand...
Click to collapse
yes. That tree has some instabilities. Unfortunately most alioth developers are using that tree. You can try hentaios and arrowos. They are not using that tree
kmykoh said:
yes. That tree has some instabilities. Unfortunately most alioth developers are using that tree. You can try hentaios and arrowos. They are not using that tree
Click to expand...
Click to collapse
Yes I know, but I in my opinion there are not the best, hope it will be fixed soon enough.
i think i finally found a solution, if you have magisk installed, i reccomend uninstalling it and giving up root, because i did it and the freezing stopped, maybe trying an older model or just giving up magisk overall will stop the freezing, but i did remove magisk and the freezing stopped, completely. also, remove any custom kernels to prevent more freezes and other shenanigans from happening, cheers.
I am facing the same issue for a long time now. Others with same device(Poco X3) didn't have any problem, it's just me and it sucks!!!
himanshu1081 said:
I am facing the same issue for a long time now. Others with same device(Poco X3) didn't have any problem, it's just me and it sucks!!!
Click to expand...
Click to collapse
This section is for Poco F3.
Does anyone have issues with bluetooth? When I connect to my car it will reboot my phone in around 15-20 mins. I"m on crDorid now but it also happened on Syberia but everything was fine on stock global 12.5.2. I have already flash back to stock Miui and then reinstall crDorid rom, It still having the same issues. I have also turn off location scan for wifi and bluetooth.
Thanks
I have same issue but im in LineageOS, I tested ArrowOS and it was the same.
Swapped to evox and still having the same issue. I might just go back to stock rom.
I'll have to test it too.. I was bored to pair it to be honest but I'll do it to check it.
Not sure if it helps but I'm using another ROM with I think is not allowed on XDA (helluvaOS), and used a bluetooth headphone for 35min today, without problems.
spoonsports said:
Swapped to evox and still having the same issue. I might just go back to stock rom.
Click to expand...
Click to collapse
Spoonspots, I reinstalled Lineage Os and install imersity kernel and now its working fine, i dont know if it was for the clean installation or the kernel.
.
franko_m19 said:
Spoonspots, I reinstalled Lineage Os and install imersity kernel and now its working fine, i dont know if it was for the clean installation or the kernel.
Click to expand...
Click to collapse
Thanks for letting me know. I had to go back to stock because my phone was rebooting every 5 mins at some locations. But after I saw shadowam said that the banned OS was working so I gave that a try and its been good so far. Only 1 random reboot after using android auto the whole day.
i have been using many aosp rom AND in all of them I have experienced random reboots while using LTE but I don't understand what causes it.
Does anyone know what causes this bug?
Are you in NA? This is an NA specific bug which is caused by a kernel panic in the modem subsystem.
This problem is fixed with the IMMENSITY kernel (although it doesn't fix the modem crashing, only the hard reboots), it is also fixed in ProtonAOSP and hOS ROM as they both share the same sources, but the sources for these ROMs are not open.
LineageOS and AOSP based ROMS have this issue and its annoying.
Same here.. hope they address the kernel issue!
It needs attention from devs and maybe code sharing from the ProtonAOSP/hOS devs. I have tried, it just falls on deaf ears.
I used my phone with LTE for a month in August and I didn't have a single reboot. I was in crdroid. Sometimes it fell to 3G or GSM due to bad coverage but that was rare.
nikosrs4 said:
I used my phone with LTE for a month in August and I didn't have a single reboot. I was in crdroid. Sometimes it fell to 3G or GSM due to bad coverage but that was rare.
Click to expand...
Click to collapse
This only effects NA as far as I know. Are you in NA?
Try switching Kernels. Some of the Custom ROMS now come with Optimus Drunk Kernel that causes issues with lags and stutters and random reboots. My phone kept rebooting over and over today until I flashed a different kernel.
Shmi117 said:
This only effects NA as far as I know. Are you in NA?
Click to expand...
Click to collapse
Sorry, what is NA?
North America.
Shmi117 said:
Are you in NA? This is an NA specific bug which is caused by a kernel panic in the modem subsystem.
Click to expand...
Click to collapse
Looking forward to having this issue resolved, I've tried countless ROMS but they all share the same issue.
Temporary fix is to switch to H+ or 3G and the reboots won't happen anymore. or Flash to HentaiOS which has the fix for this issue.
Psst... I use an lte router, tp link mr600, and got pissed off with it when I realised the modem side was android 6, AND uses adb seperatly, so my router kidnapps the adb routing (no, not rooting, routing..) by simply killing all access to adb in the router while using adb in my connected device, creating major headaches ... took a while to figure the router commandeered my local adb!!!
aravreddy2231 said:
Temporary fix is to switch to H+ or 3G and the reboots won't happen anymore. or Flash to HentaiOS which has the fix for this issue.
Click to expand...
Click to collapse
Tried HentaiOS (hentai_alioth-Rika-ota-rq3a.210905.001-Furry.09081409), cleaned install on the latest firmware (V12.5.4.0.RKHMIXM Global).
Reboots are not longer present, but data is not working.
Desperately trying to find a viable solution (AOSP) aside from going back to MIUI.
On the latest Havoc rom at the moment. Still experiencing reboots when changing cell towers. Appreciate if some solutions can be suggested.
Also experiencing it while traveling. Not from NA.
Edit:
I'm using LOS
There are two issues here:
1) Modem crashes that look like this (dev number varies):
[E][mhi_control_error] mhi: esoc0 sfr: ssr:MP:rflte_dm_rx.c:8675:rflte_dm_rxagc_config_update_switchpoints_and_lna_offsets_in_dm: Rx cal data is NULL for rfm dev 10
2) When the modem crashes, it causes the device to start.
We can work around 2 (and various ROMs already have done but lineage not yet). On 1, I'm not yet clear if this is just us or whether it happens on stock too. If it happens on stock, we're likely hosed until a firmware update fixes it. If it doesn't happen on stock, we ought to (eventually) be able to fix it in lineage too.
Never had this problem on Arrow os what is your firmware?
sam3000 said:
There are two issues here:
1) Modem crashes that look like this (dev number varies):
[E][mhi_control_error] mhi: esoc0 sfr: ssr:MP:rflte_dm_rx.c:8675:rflte_dm_rxagc_config_update_switchpoints_and_lna_offsets_in_dm: Rx cal data is NULL for rfm dev 10
2) When the modem crashes, it causes the device to start.
We can work around 2 (and various ROMs already have done but lineage not yet). On 1, I'm not yet clear if this is just us or whether it happens on stock too. If it happens on stock, we're likely hosed until a firmware update fixes it. If it doesn't happen on stock, we ought to (eventually) be able to fix it in lineage too.
Click to expand...
Click to collapse
Thank you for the explanation. The problem is not present on MIUI.
S1mon12 said:
Thank you for the explanation. The problem is not present on MIUI.
Click to expand...
Click to collapse
I was able to do some testing last night and found the same - I see no modem restarts on miui. This gives me some hope that we might be able to find a proper fix. In the meantime, I will upload a workaround to lineage that allows the modem to reset instead of hard rebooting the device. There's the kernel hack that some devices are using to always just reset modem on crash but it should also be able possible to get the subsystem restart (ssr) config to do similar (without kernel changes). Possibly just selinux issue for why it's not doing this already.
Just to update, I have been on ArrowOS for about a week now and have not crashed since.
EDIT: The modem does crash, but it does not cause a kernel panic, so it silently reboots, about a 5-10s downtime, really annoying actually.
works fine during setup then vanishes and the wifi button doesn't do anything afterwards. is it hardware or software related?
weird thing i noticed is that any wifi related setting, will make the settings crash and not respond...
miui global 12.5.8 stable, Android version: 11 RKQ1.200826.002, security update: 2002-01-01
dunno how to explain this, but this is what it looks like when I try to do anything in the settings (google drive video)
I have also looked at this thread where it seems similar to my problem, but could not find a solution.
MIUI 12.5 wifi issues
Hi, today I received the EU update to MIUI 12.5 - 12.5.1.0(RFAEUXM) . However, now my Mi 9 can't connect to wireless networks. I already tried restore the network defaults and then the factory reset without success. Any ideas? The behavior is - I...
forum.xda-developers.com
edit: seems like i have to unlock the bootloader to install a different rom, will update in a week
Sounds like a major issue , after watching the video, 2 things I would try remove sim reboot then try, of still fails the ROM must be corrupt , I would reinstall/flash sounds like you tried a factory reset so thats what I would do
thank you for your response. I did remove the sim and factory reset but no change. Can I reeinstall without having the phone unlocked? or is that only possible with an unlocked phone and the fastboot thing?
edit: found out how to local update rom, going to that and see how it goes.
edit2: installed a new rom but the issue still persist.
21sep said:
thank you for your response. I did remove the sim and factory reset but no change. Can I reeinstall without having the phone unlocked? or is that only possible with an unlocked phone and the fastboot thing?
edit: found out how to local update rom, going to that and see how it goes.
edit2: installed a new rom but the issue still persist.
Click to expand...
Click to collapse
you meant to say you just did a update? you will need unlocked bootloader I do believe but not positive if your going from stock to stock
I installed MIUI 13.0.3 with this method https://c.mi.com/oc/miuidownload/detail?guide=1 but the same problem with the WIFI persist. If it was an software issue it should have fixed it right? so I'm thinking that it might be a hardware issue instead.
21sep said:
I installed MIUI 13.0.3 with this method https://c.mi.com/oc/miuidownload/detail?guide=1 but the same problem with the WIFI persist. If it was an software issue it should have fixed it right? so I'm thinking that it might be a hardware issue instead.
Click to expand...
Click to collapse
Did you mess up with any wifi or persist thingy?
update: I unlocked the phone and installed different rom versions with MiFlash.
I installed everything step by step following this guide for installing via fastboot https://c.mi.com/thread-1857937-1-0.html.
alioth_global_images_V13.0.2.0.SKHMIXM_20220314.0000.00_12.0_global: same problem
alioth_eea_global_images_V12.5.8.0.RKHEUXM_20220210.0000.00_11.0_eea: put WiFi settings on static
worked long enough to fully setup and install some apps than it went full retard. (longest working wifi connection yet)
after a second restart, the wifi is compeltly gone now.
alioth_global_images_V12.5.6.0.RKHMIXM_20220210.0000.00_11.0_global: WiFi didn't work at all
alioth_eea_global_images_V12.5.3.0.RKHEUXM_20210706.0000.00_11.0_eea: WiFi worked for 2 minutes
I don't think i have any more roms to test out so maybe i will try a custom rom xd
try with custom roms