Rn10 pro keeps randomly restarting after custom rom installation - General Questions and Answers

I flashed my Redmi note 10 pro (global) a month ago and installed pixel experience then switched to Xiaomi.eu and both were working fine
, I then switched to MSMextended first blood and had a billion bugs(not receiving or sending sms, apps crashing, restarting after calls, etc..)
, after many failed Installations and buggy versions I managed to fix all of the bugs and installed derpfest v12 and everything is working properly except the random restarts and especially after missed calls the phone randomly reboots
I tried everything but this bug kept appearing in every custom rom I had so far and I can't see why
Any help is greatly appreciated bec I can't use my phone like this

Related

[Q] serendipity 6.4, "no service" when receving a call

I installed serendipity 6.4 w/ hardcore speedmod about 3days ago and everything works very well,but when I get a incoming call the phone rings once and I drop signal "no service" a second or two goes by signal comes back everythings fine no missed call shown, like I never got a call...But I can make outgoing calls...plz help
Same exact problem for me, I even tried restarting fresh and doing the whole flashing process over again and still have the same issue.... I'm about to switch roms if this keeps up but I really liked Serendipity
Same problem here, same ROM, same version.
What have you guys tried?
I've flashed back to stock using ODIN and then flashed back to Serendipity again. Problem appeared to be resolved at first, but then 2 days later the symptoms started to repeat.
That made me suspect the problem was with particular apps or widgets I'd stuck on my home screen, so I tried removing my newer apps & widgets such as Facebook and NYT to no avail.
Anyone else with ideas?
I do rather like Serendipity, but will probably end up flashing back to Cognition or something to get around this. Guess I'll wait for Mikey's 2.3 to stabilize!
Update:
Flashed back to a clean Serendipity 6.4 and did not use Titanium Backup to restore my apps. It's working fine right now. In the next few days I'll restore individual apps as I need them, and see if the problem recurs.
Best theory so far is that the problem is either
a) Caused entirely by a particular app or widget
b) Caused by some sort of strange incompatibility between Serendipity 6.4 and a particular app or widget

Help!! PUBG Mobile automatically closes

Hello, i bought mi mix 2s 4 days ago and i installed pubg mobile game on it and it was working normally,, but 2 days ago i unlocked bootloader and and i updated the mobile from MIUI 10 to MIUI 11 by ota then pubg started from yesterday after the update to automatically closes after i join a match sometimes after 2 minutes or 10 minutes or 15 minutes not a constant number of minutes i mean.
Then i tried to install Pixel 3 rom found on this forum and the same problem is done then i installed linagous rom and the problem still happening i already tried many kernels and the problem still exists then tried to clear data and cache and still happeining and tried to delete it and re-install it and still the same, so from where this problem is coming and what i have to do to solve it? any ideas?
Note: Pubg Mobile Closes automatically not force close and not giving me any message, it just closes..
Thank you in Advance
Did you look into your battery saving options?
Also check the check the app options for pupg. But it should not close it while you use it so it's strange..

LineageOS questions

Been in the ROM/kernel scene for waaaaaaay too long and have constantly been told that I should use LineageOS (and its predecessor), esp on the Pixel devices that are no longer supported officially. However, LineageOS consistently fails me on every device, despite my being able to get everything BUT LineageOS to work. I've got to be missing something. Going to go through my experiences below...maybe someone can advice how the heck they get LineageOS to work for them on pixel devices?
Round 1: Nexus 6 (CM)
- Installed great
- No initial issues
- Randomly, phone would report "no sim" and stop working
- Reboots sometimes fixed the SIM issue, but sometimes didn't
- Calls lost because the SIM vanished, phone dropped data during a long drive, thus losing GPS access
- Random "service stopped" errors, usually regarding bluetooth
- Never resolved, even over a dozen different versions of CM (this was before Lineage, but same base)
Round 2: Pixel 2 (LOS 16?)
- Installed great, but had to be careful which gapps to use, as most were larger than the system partition
- No SIM errors right away, but a few reboots cleared it up
- Project Fi issues nonstop, with the phone unregistering several times a day
- SIM errors came back, saying my SIM is missing or damaged
- Overheating problems with the CPU. Appears to be the known bug with the CPU, but only appears in LineageOS
- Random "service stopped" errors, usually about the launcher
- Never resolved over different versions of LineageOS (last version tried was I think 16)
Round 3: Pixel 3 (LOS 17.1)
- ROM installs fine, but the notes say you need the Super Gapps to use Project Fi...but that Gapps doesn't fit in system. This seems like an oversight. Installed with smaller Gapps for testing, knowing there may be some Project Fi issues later. Each "try" below is a fresh reformat.
- First try, it popped up an error that there was a SIM, but it was damaged and unreadable. Could not continue. Told me to order a new SIM (the SIM's fine...). Lots and lots of errors about services crashing.
- Second try, it popped up an error that there was no SIM at all. It offered to just use wifi, which I accepted for testing. After downloading updates, it said the wifi doesn't work. Reboots, retries, just wouldn't work...even though it obviously had up to that point.
- Third try, it said my SIM was damaged again. This time it offered to activate eSIM online. Not sure why it hadn't said that previously, but ok. I tell it to activate...and it says the wifi is down. But...it isn't. Wifi working great, but can't activate the phone.
Overall, super frustrating and I can't imagine others are getting these errors, or LOS would have died out looong ago. How are others getting around these?!?
Lagarde said:
Been in the ROM/kernel scene for waaaaaaay too long and have constantly been told that I should use LineageOS (and its predecessor), esp on the Pixel devices that are no longer supported officially. However, LineageOS consistently fails me on every device, despite my being able to get everything BUT LineageOS to work. I've got to be missing something. Going to go through my experiences below...maybe someone can advice how the heck they get LineageOS to work for them on pixel devices?
Round 1: Nexus 6 (CM)
- Installed great
- No initial issues
- Randomly, phone would report "no sim" and stop working
- Reboots sometimes fixed the SIM issue, but sometimes didn't
- Calls lost because the SIM vanished, phone dropped data during a long drive, thus losing GPS access
- Random "service stopped" errors, usually regarding bluetooth
- Never resolved, even over a dozen different versions of CM (this was before Lineage, but same base)
Round 2: Pixel 2 (LOS 16?)
- Installed great, but had to be careful which gapps to use, as most were larger than the system partition
- No SIM errors right away, but a few reboots cleared it up
- Project Fi issues nonstop, with the phone unregistering several times a day
- SIM errors came back, saying my SIM is missing or damaged
- Overheating problems with the CPU. Appears to be the known bug with the CPU, but only appears in LineageOS
- Random "service stopped" errors, usually about the launcher
- Never resolved over different versions of LineageOS (last version tried was I think 16)
Round 3: Pixel 3 (LOS 17.1)
- ROM installs fine, but the notes say you need the Super Gapps to use Project Fi...but that Gapps doesn't fit in system. This seems like an oversight. Installed with smaller Gapps for testing, knowing there may be some Project Fi issues later. Each "try" below is a fresh reformat.
- First try, it popped up an error that there was a SIM, but it was damaged and unreadable. Could not continue. Told me to order a new SIM (the SIM's fine...). Lots and lots of errors about services crashing.
- Second try, it popped up an error that there was no SIM at all. It offered to just use wifi, which I accepted for testing. After downloading updates, it said the wifi doesn't work. Reboots, retries, just wouldn't work...even though it obviously had up to that point.
- Third try, it said my SIM was damaged again. This time it offered to activate eSIM online. Not sure why it hadn't said that previously, but ok. I tell it to activate...and it says the wifi is down. But...it isn't. Wifi working great, but can't activate the phone.
Overall, super frustrating and I can't imagine others are getting these errors, or LOS would have died out looong ago. How are others getting around these?!?
Click to expand...
Click to collapse
I just did a brand new install of a Lineage OS 18.1 nightly on my Pixel 3. I used NikGapps core since it has support for Android 11. I don't use Project Fi so I can't attest to that. So far everything has been running perfectly, with the exception of a few missing features or bugs I cannot figure out (small quality of life issues- nothing major). I too had issues in the past with CyanogenMod and I killed my old Motorola that way (probably user error though). I know you said your SIM is fine, but being that it has happened on 3 different devices... is it actually the same exact SIM? Might be worth the $10 fee or whatever to replace it. I haven't had a single error about any services crashing or stopping, perhaps I'm just lucky? One of the roms or gapps packages I was reading the notes on said you could install it in 1 or 2 different partitions, essentially making the size a non-issue. Stupidly, I can't remember which item I read that on, but it is apparently out there if you're willing to look.
I set up all my apps and stuff over WiFi and got the phone how I want it before plugging in my SIM card. I'm on T-Mobile. When I plugged in the SIM I didn't have to do any configuration at all it just works, even has WiFi calling. I don't have any apps on autoupdate and was careful about what "System" apps I toggled or installed from the play store. I'm afraid I can't help you much other than to tell you the nightly from 05-18-2021 doesn't give me the issues it seems to give you. Sorry bud!
nasch007 said:
I just did a brand new install of a Lineage OS 18.1 nightly on my Pixel 3. I used NikGapps core since it has support for Android 11. I don't use Project Fi so I can't attest to that. So far everything has been running perfectly, with the exception of a few missing features or bugs I cannot figure out (small quality of life issues- nothing major). I too had issues in the past with CyanogenMod and I killed my old Motorola that way (probably user error though). I know you said your SIM is fine, but being that it has happened on 3 different devices... is it actually the same exact SIM? Might be worth the $10 fee or whatever to replace it. I haven't had a single error about any services crashing or stopping, perhaps I'm just lucky? One of the roms or gapps packages I was reading the notes on said you could install it in 1 or 2 different partitions, essentially making the size a non-issue. Stupidly, I can't remember which item I read that on, but it is apparently out there if you're willing to look.
I set up all my apps and stuff over WiFi and got the phone how I want it before plugging in my SIM card. I'm on T-Mobile. When I plugged in the SIM I didn't have to do any configuration at all it just works, even has WiFi calling. I don't have any apps on autoupdate and was careful about what "System" apps I toggled or installed from the play store. I'm afraid I can't help you much other than to tell you the nightly from 05-18-2021 doesn't give me the issues it seems to give you. Sorry bud!
Click to expand...
Click to collapse
Appreciate you looking at that. I haven't tried 18.1 yet, as I'm a bit gunshy after how bad 17.1 went for me. I'm strongly suspecting most of my issues go back to Project Fi...but it's not the SIM. I've actually bought 2 extra SIMs over the years trying to resolve this very issue. They all do the same thing on LOS.
Hadn't seen the splitting of gapps. That's news to me. Will look into that, as Project Fi requires the largest of the gapps...which is too big to fit into the system partition.
Lagarde said:
Overall, super frustrating and I can't imagine others are getting these errors, or LOS would have died out looong ago. How are others getting around these?!?
Click to expand...
Click to collapse
I'm running LOS 18.1 on my P3 blueline, running it for ages. I use OpenGapps Pico, and haven't had any issues to speak of. It took me a bit to figure out how to flash ROMs etc. on my P3 when I first bought it about 12 months ago, but once I got the hang of it, haven't had any issues.
LOS 18.1 seems very fast and responsive. Rooting with Magisk 23, running LSPosed through Riru, and even have Google Pay working like a charm. Android Auto working perfectly (patched with AIO and Scren2Auto so I can run virtually any apps on my car display if I want to).
Updates are fairly smooth; the only catch is I have to be careful to reflash the Magisk-patched boot.img before rebooting into the system, otherwise I lose root, and by extension, GPay stops working. I just update the ROM using ADB instead of the on-device updater, flash in TWRP recovery, then flash the patched boot.img in Fastboot ... reboot ... and Bob's your uncle.
I also have an old Nexus 7 (2013), and run LOS 18.1 on that 8-year-old tablet very nicely. It can be a tad sluggish on occasion, but for the most part it runs perfectly. The N7 is mostly my games/play machine. I use WiFi hotspot from the P3 when out and about to give the N7 internet access when needed - no problems.
All that to say ... Don't be afraid to try LOS 18.1. It's a fantastic ROM. Can't wait until LOS 19 builds start cropping up.
shaunoleary said:
I'm running LOS 18.1 on my P3 blueline, running it for ages. I use OpenGapps Pico, and haven't had any issues to speak of. It took me a bit to figure out how to flash ROMs etc. on my P3 when I first bought it about 12 months ago, but once I got the hang of it, haven't had any issues.
LOS 18.1 seems very fast and responsive. Rooting with Magisk 23, running LSPosed through Riru, and even have Google Pay working like a charm. Android Auto working perfectly (patched with AIO and Scren2Auto so I can run virtually any apps on my car display if I want to).
Updates are fairly smooth; the only catch is I have to be careful to reflash the Magisk-patched boot.img before rebooting into the system, otherwise I lose root, and by extension, GPay stops working. I just update the ROM using ADB instead of the on-device updater, flash in TWRP recovery, then flash the patched boot.img in Fastboot ... reboot ... and Bob's your uncle.
I also have an old Nexus 7 (2013), and run LOS 18.1 on that 8-year-old tablet very nicely. It can be a tad sluggish on occasion, but for the most part it runs perfectly. The N7 is mostly my games/play machine. I use WiFi hotspot from the P3 when out and about to give the N7 internet access when needed - no problems.
All that to say ... Don't be afraid to try LOS 18.1. It's a fantastic ROM. Can't wait until LOS 19 builds start cropping up.
Click to expand...
Click to collapse
Good info. Have 18.1 also and have it set up to allow OTA updates and keep magisk and my gapps. Have only done 1 update that way but works perfectly, keeps magisk modules also.
Curious, which twrp are u using? Didn't think there was one available?
cheers
AsItLies said:
Good info. Have 18.1 also and have it set up to allow OTA updates and keep magisk and my gapps. Have only done 1 update that way but works perfectly, keeps magisk modules also.
Curious, which twrp are u using? Didn't think there was one available?
cheers
Click to expand...
Click to collapse
Not using TWRP, I'm just using LOS recovery. Sadly, it doesn't allow for doing backups, but it does the job otherwise.
Just an update BTW - currently running into issues with Google Pay/SafetyNet, but it's due to Google playing silly buggers with GPay again, not the fault of LOS.

Question Bluetooth integration fails

Hi, I have been installed custom rom lineage 19.1 on my redmi note 11 pro 5g (veux).
The Bluetooth is working headset/earphones connecting and working normally for audio streaimg like YouTube or any other apps as soon I try to call or receive using any app or phone app, messenger etc, the app becomes unresponsive, even it says phone app unresponsive close or wait window at that point I have no options device freezes and needs to reboot forcefully in order to work.
Any idea?
Baker
Silent14725 said:
Hi, I have been installed custom rom lineage 19.1 on my redmi note 11 pro 5g (veux).
The Bluetooth is working headset/earphones connecting and working normally for audio streaimg like YouTube or any other apps as soon I try to call or receive using any app or phone app, messenger etc, the app becomes unresponsive, even it says phone app unresponsive close or wait window at that point I have no options device freezes and needs to reboot forcefully in order to work.
Any idea?
Baker
Click to expand...
Click to collapse
Pointing out the freeze device means in the background the phone is working the particular app unresponsive error doesn't go away it freezes there
Any non miui rom will have alot of issues. There won't be any help or support until we atleast get a partial functional recovery or official rom releases
You'd have better luck asking the guys who made the ROM instead of creating a thread here. If bluetooth audio worked fine in stock, and it's busted in a custom rom then it's the custom ROM's issue.

Question poco x3 pro dying

My poco x3 pro started to have some problems 2 months ago first Mic stopped working completely after the 13.03 global update , now all of a sudden when i connect my bluetooth headset it connects normally but there is no voice heard and when i play videos no matter what platform video start to stutter even though the app work normally and i can scroll comments or other videos on yt while the video is playing ,games crash if connect my headset ... so im pretty convinced its going to die soon
currently updated to 13.0.4 official global .. did a complete fastboot installation twice and no changes
question is should i install a custom rom , does that have any chance to saving the phone ...which rom u guys recommend simple google search shows crdroid or lineageos and here most popular rom seems to be arrow
king901 said:
My poco x3 pro started to have some problems 2 months ago first Mic stopped working completely after the 13.03 global update , now all of a sudden when i connect my bluetooth headset it connects normally but there is no voice heard and when i play videos no matter what platform video start to stutter even though the app work normally and i can scroll comments or other videos on yt while the video is playing ,games crash if connect my headset ... so im pretty convinced its going to die soon
currently updated to 13.0.4 official global .. did a complete fastboot installation twice and no changes
question is should i install a custom rom , does that have any chance to saving the phone ...which rom u guys recommend simple google search shows crdroid or lineageos and here most popular rom seems to be arrow
Click to expand...
Click to collapse
Sounds like a hardware problem, changing roms won't do anything.
king901 said:
My poco x3 pro started to have some problems 2 months ago first Mic stopped working completely after the 13.03 global update , now all of a sudden when i connect my bluetooth headset it connects normally but there is no voice heard and when i play videos no matter what platform video start to stutter even though the app work normally and i can scroll comments or other videos on yt while the video is playing ,games crash if connect my headset ... so im pretty convinced its going to die soon
currently updated to 13.0.4 official global .. did a complete fastboot installation twice and no changes
question is should i install a custom rom , does that have any chance to saving the phone ...which rom u guys recommend simple google search shows crdroid or lineageos and here most popular rom seems to be arrow
Click to expand...
Click to collapse
The bluetooth one happened to me too. My phone's touch now no longer works even though my phone never fell, got wet, or got pressed hard.
I already tried changing roms, reflashing old and latest MIUI through fastboot and none of them fixed the issue.
jalter1213 said:
The bluetooth one happened to me too. My phone's touch now no longer works even though my phone never fell, got wet, or got pressed hard.
I already tried changing roms, reflashing old and latest MIUI through fastboot and none of them fixed the issue.
Click to expand...
Click to collapse
been working on it since yesterday nothing helped , guess i will have to wait for it to die on me
ty for replying hope your next phone isnt as bad
king901 said:
been working on it since yesterday nothing helped , guess i will have to wait for it to die on me
ty for replying hope your next phone isnt as bad
Click to expand...
Click to collapse
Try installing an Android 13 custom rom. I recommend Exolution X for now since Pixel Experience android 13 is kinda buggy
I have the same problem. And every ROM, whether official or custom, has the same problem.
Install custom ROM. Worth to try. AOSP from foxtrot on tg is perfect a12 for me and everything working perfect.

Categories

Resources