Hello. I used to have cm13+radon kernel. For some time after, I flashed a newer version of cm13, then when speaking on the phone, I experience call drops. I call someone, it accepts the call, but after some seconds (sometimes it's 2 secs and sometimes it's 30 secs) the call drops. But
Then I flashed an older version of cm13 + flashed radon again. But same thing! Then I flashed the rom again (no custom kernel this time) and no problem with calls. Fast forward, yesterday I flashed RR 5.8.0 + agni kernel+cam libs. Same thing happened again. I tried some cm14 firmware, but nothing changed. (actually I bricked the phone.)
Anyway now I am on RR 5.7.4 (nougat roms are buggy without kernels) and no custom kernel. What might be the problem? I can't flash custom kernels.
First thing i would suggest is installing the complete stock MIUI ROM through fastboot, and running that a few days to see if you still get the same issues.
If you don't, then you know it is something that is being done when you install the CM roms. Could be a firmware that you need to flash, could be something with CM or the rom's themselves, or the custom kernels.
You have to do process of elimination here.
goofball2k said:
First thing i would suggest is installing the complete stock MIUI ROM through fastboot, and running that a few days to see if you still get the same issues.
If you don't, then you know it is something that is being done when you install the CM roms. Could be a firmware that you need to flash, could be something with CM or the rom's themselves, or the custom kernels.
You have to do process of elimination here.
Click to expand...
Click to collapse
Without flashing kernel, there wont be a problem i guess because, right now I dont have the issue. (rr 5.7.4 no custom kernel). It shouldnt be kernel end, because i havent heard anyone beside me experiences this.
Hello Axon 7 XDA Users,
as you know, more and more users have a stupid reboot bug. Unfortunately no DEV found the time to take a look into the logs I and other users posted on the forums.
THE BUG
Soft reboots and boot loops at least once a day
- while charging
- while watching videos or surfing
- even then turned off (Ghost booting)
SOFTWARE AND DEVICES
Reports on nearly all custom roms based on LOS
All A2017 / 2017 U / 2017 G models
WORKING SOLUTIONS
A
I seem to have fixed the problem and want to ask you to try my method:
The problem is probably caused by Magisk, all versions from 13.5 till 14.5x beta
After switching to LineageOS integrated root method I am reboot-free since 3 days of intense usage.
Tutorial to uninstall magisk:
- Download magisk-uninstaller and LOS root addon on LOS ROMs (Downloads are attached)
- Reboot into recovery
- Install magisk uninstaller zip file
- Reboot into recovery (maybe not necessary)
- Install LOS root addon
- Wipe dalvik and cache.
- Profit :good: and report back
B
Only use magisk v14 or try 15.2
THX @notese
C
Try disabling Magisk hide
THY @digiNZM
I don't use magisk and I still have reboots. Reboots occur about once or twice a week.
Pastinakel said:
I don't use magisk and I still have reboots. Reboots occur about once or twice a week.
Click to expand...
Click to collapse
Thank you for your feedback.
Maybe you should post what setup you have and which apps you are using with root / xposed access or mods.
I had the reboot issue with the latest lineage os and magisk on b25 universal bootstack.
Currently using Dark ROM with magisk on b32 bootstack for the past week or so and no reboots.
A2017U
SilentEYE said:
Thank you for your feedback.
Maybe you should post what setup you have and which apps you are using with root / xposed access or mods.
Click to expand...
Click to collapse
My setup is pretty plain vanilla, no mods. I have the lineage root installed, but it's disabled most of the time.
If I remove Magisk and go with Lineage root, will I lose Safetynet? I need Android Pay to work.
I had the problem with random soft reboots for quite a few months. There would be no similarities between when the reboots happened, for example it would occur whilst watching YouTube videos, browsing Google Maps or even just leaving the phone in sleep mode. Someone on XDA suggested switching from Magisk v14.5 Beta to stable Magisk v14.0, and since then I haven't had a problem.
Advising people to ditch Magisk altogether might not be the best advice, as for me just switching back to the stable version worked. Remember there have been beta versions of Magisk v14.0 for months and it was definately affecting v14.3 as well as v14.5.
That's weird.
I'm using magisk myelf for a long time and never had reboot issues. :/
Only when using incompatible modules or bad settings.
Maybe that's where the real issue is.
P. S.
I'm using latest stable magisk on latest stable RR for a while no and I get zero reboots.
P650SE said:
I had the problem with random soft reboots for quite a few months. There would be no similarities between when the reboots happened, for example it would occur whilst watching YouTube videos, browsing Google Maps or even just leaving the phone in sleep mode. Someone on XDA suggested switching from Magisk v14.5 Beta to stable Magisk v14.0, and since then I haven't had a problem.
Advising people to ditch Magisk altogether might not be the best advice, as for me just switching back to the stable version worked. Remember there have been beta versions of Magisk v14.0 for months and it was definately affecting v14.3 as well as v14.5.
Click to expand...
Click to collapse
You probably read my advise. My fav rom is AOSP Ex and it was driving me nuts the whole random reboot thing. Your description of the symptoms are exactly like the ones I was having. At the beginning I though it was an issue with substratum but it kept happening even without having substratum installed.
I tried switching roms (Dark Rom, Lineage, and RR) and all had random reboots. The final epiphany I had was that I was using magisk beta 14.5 on all of them. I didn't install any custom kernel or any other thing beside magisk 14.5 and one module (viper). I tried reading at the logs but couldn't trace them back.
I figured to try AOSPex without root as the only common thing between the roms was magisk. After this, the reboots and crashes stopped (I tested this for a week). I started reading in the magisk forums and found people with the same symptoms as ours. I didn't see any major complain with the stable magisk 14.0.
My current setup is ASOP ex with llama kernel and magisk 14.0. I have had this for about two weeks and no random reboots so far. The only problem I have encountered was that I lost root access once and I had to reboot on my own account to regain root (maybe a module incompatibility, I have installed two additional modules since then). Other than that, all is good.
Final tip: I only turn on the magiskhide setting when I need it for a specific app. I have it off by default. I don't want an extra process running all the time if I don't need it or use it regularly (can only be a good thing for battery).
Hope this helps
I got the reboots even with magik v14.
Added @notese his solution to OP
I've only got Magisk for a month or so, but reboots began way before that. So I don't Magisk is the culprit.
hboa said:
I've only got Magisk for a month or so, but reboots began way before that. So I don't Magisk is the culprit.
Click to expand...
Click to collapse
What root method did you use before?
Which rom?
Which root apps?
If you provide us some more, maybe we can hit the sweet spot of the bug.
To all :
Write at the end of your comment your settings
Device
ROM
Kernel
Modem
Root method
Root apps
Had Reboots with Magisk v14.x in different ROMs (Vertex, AICP, AOSP) and with different Kernels. Since i disabled Magisk-Hide it stopped (past 3 weeks). Maybe a weird coincidence. Just thougt i share this. Maybe someone can try too?
Current: AICP (unofficial), LLAMA non-EAS Kernel, Magisk latest (v14.5), MicroG.
digiNZM said:
Had Reboots with Magisk v14.x in different ROMs (Vertex, AICP, AOSP) and with different Kernels. Since i disabled Magisk-Hide it stopped (past 3 weeks). Maybe a weird coincidence. Just thougt i share this. Maybe someone can try too?
Current: AICP (unofficial), LLAMA non-EAS Kernel, Magisk latest (v14.5), MicroG.
Click to expand...
Click to collapse
I always had magisk hide disabled and had the reboot problems.
I will add your solution to topic
I personally had some reboot and bootloop problems while on AICP and LlamaSweet and I thought it was the rom. However I then went to Dark Rom with LlamaSweet and the reboots happened again. I posted about this and someone mentioned 14.5 might be the problem. I installed 14.0 and for the past week? I haven't had a problem. So for me it seems so far to be 14.5 as well. Also as of right now I have BeastMode kernel running. Has anyone tried 14.6 yet?
I will post screenshot of my superuser and modules pages.
I have the latest beta version of Magisk and I have reboots once or twice a day, but not necessarily all days. I have the stock camera and "Enable AK4490 HIFI DAC" magisk modules.
I had reboots on the latest DarkRom, Magisk many times a day for at least a month and a half. Since hurricane Maria cell service was almost impossible to find. I noticed everytime my phone lost coverage it would reboot.
Changed sim to another carrier with great coverage just a few weeks ago and reboots have since gone away. Hmmm
eaponte23 said:
I had reboots on the latest DarkRom, Magisk many times a day for at least a month and a half. Since hurricane Maria cell service was almost impossible to find. I noticed everytime my phone lost coverage it would reboot.
Changed sim to another carrier with great coverage just a few weeks ago and reboots have since gone away. Hmmm
Click to expand...
Click to collapse
Did it hang in the soft reboot loop?
SilentEYE said:
Did it hang in the soft reboot loop?
Click to expand...
Click to collapse
Nope, it would just reboot everytime I drove thru certain areas. For instance, as soon as I passed my towns high school, boom restart.
If I had 3G then all of a sudden it dropped to zero bars, boom restart.
The only way I would not get the reboots was installing DrakenFXs B32 with Magisk. Or turning on airplane mode when I knew I would go thru an area with no service.
Convinced me LOS based rom had problems with handling towers and low signal. I tried them all same reboots.
@eaponte23
your problem seems to be different and is a combination of modems and your provider. I know that there has been similar problems with CM /LOS based ROMs on other devices, depending on the Service provider. These lead to total signal loss or reboots.
The Magisk problem is cauing constant reboots.
i dont know why but both little and big clusters just locking speed below 1100mhz,whatever i do, it never changes on pie rom,installed every rom,installed radon 6.3 modified[it change for sometime but reverts back randomly then locking in same speed]
is this android pie bug or kernel issues?
P.S: miui,nougat roms are normally working ,no issues with them,i dont like oreo roms ,so i dont use them
Do you try with kernel adiutor?
go to vendor/etc/thermal-engine.conf <-- delete this file or backup incase u want it back or u can just edit the value of device limit
So, I install lineage os every one's and a while to test it and see if it is ok for me, I always revert to stock but that's not the point, one problem that I have is that the phone gets VERY HOT. One day I installed lineage and when I finished the setup process, the phone was so hot I couldn't hold it comfortably, while when I finish the setup on the stock rom the phone is just warm. Is there any way to make the phone run cooler? Is the phone getting hot because the software is too much for the processor? . I haven't installed lineage os for about two months now so I may try it again at some point. Is anyone else having the same problem?
No that's not normal, it's not supposed to heat up much.
Maybe you you didnt flash it properly, it's recommended to install it like this.
forum.xda-developers.com/lg-g5/development/rom-unofficial-lineageos-17-1-g5-t4039807/post81972297#post81972297
Also check before flashing if your camera works on the stock lg rom,
If it doesnt you have to downgrade to stock marshmellow, and then upgrade back to oreo to fix it.
dylank said:
No that's not normal, it's not supposed to heat up much.
Maybe you you didnt flash it properly, it's recommended to install it like this.
forum.xda-developers.com/lg-g5/development/rom-unofficial-lineageos-17-1-g5-t4039807/post81972297#post81972297
Also check before flashing if your camera works on the stock lg rom,
If it doesnt you have to downgrade to stock marshmellow, and then upgrade back to oreo to fix it.
Click to expand...
Click to collapse
Thanks for answering,
This is how I install it. The camera on stock oreo is working normally so I don't need to install stock Marshmallow. So, I firstly unlock the bootloader and then install lineage os 15.1 with no gapps. After that I upgrade to lineage os 16.1 again with no gapps. Now I uninstall lineage 16.1 and I am doing a clean install of official lineage os 17.1 WITH gapps. The reason I do this is because if I install lineage 17.1 instantly the cameras and sensors don't work. Unfortunately I don't remember the temperatures that I got but I remember that one day I woke up with 20 C and after 15 minutes of some web browsing and social media it went up to 40 C (there's a slight chance that I'm wrong since I don't remember the exact temperatures as I said)
Strange i didn't have those problems when flashing properly,
Do you also use nano/pico opengapps?
You could also give crDroid Android 5.12, a try maybe that will work well, but it's android 9 instead of 10.
I think you need to flash it in the same way as lineage.
dylank said:
Strange i didn't have those problems when flashing properly,
Do you also use nano/pico opengapps?
You could also give crDroid Android 5.12, a try maybe that will work well, but it's android 9 instead of 10.
I think you need to flash it in the same way as lineage.
Click to expand...
Click to collapse
I originally used nano opengapps but I started using stock because I use most of the gapps anyway but I will try crdroid 5.12 at some point to see what happens.
Hi everyone. this is my very first post. I'm an Owner of a Redmi 6a (Cactus) Running Lineage OS 17.1 Unofficial (20200727) and I'm having some issues with the from so. first, I would like to know which Custom ROM Its better for this model now in 2022. more stable and updated. and also. if I can change the custom ROM to another without problems, just wiping some things ( I have TWRP and Bootloader unlocked already), or I have to get back to MIUI again.
I'm seeking something with the highest android version available for this model without problems like slow charging. camera stops or issues with daily usage, I would like to get my phone a little more powerful again.
Any suggestions, and comments, are well received by me.
Thanks to everybody
welcome to the dark side
so at the beginning i just tested some of the available costom roms, each for a few days (like go shopping) to get to know the functions and to see if they are stable (stable enough - because you can't find all bugs in short time). i am now using LineageOs but this is a personal preference. maybe i should go "shopping" again to see how the other costom roms have evolved over the past two years. as long as i did this testing i flashed all the roms "dirty", this means as you said, just wiping/formatting in twrp and flash new rom but as soon as i left testing and decided to use a rom for a longer period of time i did a "clean" flash. this means flash stock rom again (be careful to don't lock your bootloader again, its preselected in miflash unlock tool), then boot system, enable adb debugging, flash twrp, flash costom rom. i would say from experience that if you do a dirty or even clean flash, lets say you do it 10 times in a row, you will not always get the same result. maybe sometimes in LineageOs (at some devices) the radio is missing, sometimes it's not. sometimes you have a bug with a camera, sometimes you don't. flashing clean should reduce the error rate. this in the first place and the different region versions make it hard to help someone who has a device specific - rom specific - one in a hundred times bug - they need some help with.