Develop Bugs

Random Reboots OB28

Since there are multiple reports of random reboots appearing multiple times a day on OB27, I think it would be a good idea to start a poll about it.
Just report in this thread if you're facing those issues and which setup you are using!
Please list all your Mods and System changes down below plus your apps which needs root. So we can figure out if there are any analogies.
I will post an example below.

Random reboots?
- None
Setup:
- TWRP-3.2.0-x bluSparkv8.60-op3_op3t
- ExperienceOS R30
- SuperSU (NO Magisk)
- SuHide
- BluSpark 208
Installed Root-Apps:
- PitchBlack-Substratum
- Adaway
- ForceDoze
- Kernel Auditor
- SDMaid
- SELinux Changer

Random reboots?
- Yes
Setup:
- twrp-3.2.0-0-oneplus3t.img (Should I use a modded version?)
- AUDAX OP3T O v4.0
- Magisk 14.5
Installed Root-Apps:
- Substratum with Ozone theme
- Greenify
- SDMaid
Magisk Module
HEVC+SM GC OP3&OP3T and OP5 by crashoverride1995
I guess the Oreo OOS is not working well with the Magisk. But I don't have much time to verify it.

I may find the real reason behind the random reboot issue. It's a magisk module called "Greenify4Magisk".
Once you've installed this module, your phone itself will randomly soft reboot. But the real problem here is that even you disable or delete this module, you'll still get random reboots. The only way to fix this issue is to clean flash your ROM. Start over and reinstall everything but the module. Flash without cleaning the /data partition (a.k.a. dirty flash) can't solve this issue. It looks like the module "pollutes" your /data partition.
I've tried to dirty flash several ROMs and kernels, disable and uninstall every module. But I still got random reboots. It almost made me crazy. So I decided to have a completely new start. I reinstalled every apps and module except the Greenify4Magisk. I've used my phone for nearly a week now and no reboot at all. It used to reboot 2~3 times an hour.

BootCoveryXhosts said:
I may find the real reason behind the random reboot issue. It's a magisk module called "Greenify4Magisk".
Once you've installed this module, your phone itself will randomly soft reboot. But the real problem here is that even you disable or delete this module, you'll still get random reboots. The only way to fix this issue is to clean flash your ROM. Start over and reinstall everything but the module. Flash without cleaning the /data partition (a.k.a. dirty flash) can't solve this issue. It looks like the module "pollutes" your /data partition.
I've tried to dirty flash several ROMs and kernels, disable and uninstall every module. But I still got random reboots. It almost made me crazy. So I decided to have a completely new start. I reinstalled every apps and module except the Greenify4Magisk. I've used my phone for nearly a week now and no reboot at all. It used to reboot 2~3 times an hour.
Click to expand...
Click to collapse
I would say, I have a different issue then. I have installed only Magisk for rooting purpose, no modules at all. But still will get random reboots after few days.
Seems like there are rumors that even Pixel with Oreo gets this random reboots too
Sent from my ONEPLUS A3003 using Tapatalk

Ok, in the thread
https://forum.xda-developers.com/oneplus-3/how-to/randomly-reboots-beta28-t3714665/page3
this has already been discussed, I think to avoid this thread to be considered a duplicate of that one other, we should keep this one essentially as a Poll Thread.
In this sense, my experience is:
-Reboots: YES
-ROM: Freedom OS CE 3.1 & 3.2
-Root: Magisk 14.0
-Modules: None
-Frequency: 1 week without reboots at all, then about 2-3 each day.
------------------------------
-Reboots: YES
-ROM: Oxygen OS Open Beta 28
-Root: Magisk 14.5
-Modules: None
-Frequency: 1-2/day, but once I had 5 days without reboots.
------------------------------
-Reboots: NO
-ROM: Oxygen OS Open Beta 28
-Root: NONE
-Modules: N/A
-Frequency: At least 2 days without reboots.
-> In the Magisk thread it has been reported on other devices too, and it has been acknowledged to be a Magisk Issue. Anyway, this thread might be useful for tracking of the issue to check if it has been solved when the patch arrives. Notice that reboots have an extremely random nature and only a couple days without reboots doesn't mean the issue is fixed. Some reboots are slightly silent, so you can check for reboots in a terminal and type "uptime" to check if there has been a reboot while you weren't looking.

BootCoveryXhosts said:
Random reboots?
- Yes
Setup:
- twrp-3.2.0-0-oneplus3t.img (Should I use a modded version?)
- AUDAX OP3T O v4.0
- Magisk 14.5
Installed Root-Apps:
- Substratum with Ozone theme
- Greenify
- SDMaid
Magisk Module
HEVC+SM GC OP3&OP3T and OP5 by crashoverride1995
I guess the Oreo OOS is not working well with the Magisk. But I don't have much time to verify it.
Click to expand...
Click to collapse
maybe this moudle
HEVC+SM GC OP3&OP3T and OP5 by crashoverride1995

Is Magisk/Root causing random reboots for anyone?

I'm trying to figure out if my pixel is randomly rebooting due to magisk/root or if I'll need to RMA it. It's done it on both 8.0 and 8.1. It only seems to happen when the device get's below 20% battery. Is anyone else experiencing this or should I start and RMA? Thanks in advance.

Looks like Magisk 14.5 might have something to do with it.
Starting on page 452 there are a few posts from there on about it.
Symptoms are a random reboot with a soft boot loop of the SystemUI. The only way to correct it is to hard reboot the device.
I can usually go a few days worth of up time between the bug reappearing.

I was the exact same way on 8.0. Every couple of days, it would start randomly rebooting and/or apps would start crashing. The only fix was to hold the power button until it rebooted. Rebooting by just pressing the power button and selecting reboot would always hang.
I was hoping 8.1 would fix it, but it's quite a bit worse. It's done it at least 4 times so far today. Same symptoms. Apps will start crashing (sometimes the foreground app, sometimes background ones), or the phone will just soft reboot, or both. Sometimes it's while I'm using it, sometimes I'm not using it at the time. No rhyme or reason, that I can tell..
I had one app that crashed immediately every time I tried to start it until I uninstalled it and restored it from backup (with data). That was weird.
If this keeps up, I may have to roll back to 8.0.

theycallmerayj said:
I'm trying to figure out if my pixel is randomly rebooting due to magisk/root or if I'll need to RMA it. It's done it on both 8.0 and 8.1. It only seems to happen when the device get's below 20% battery. Is anyone else experiencing this or should I start and RMA? Thanks in advance.
Click to expand...
Click to collapse
There is a larger thread on this HERE. There is no definitive smoking gun yet but certain root apps seem to be causing it. One way to rule out Magisk would be to simply uninstall the app temporarily (longpress>>App Info>>Uninstall) then fastboot flash the original boot.img and dtbo.img. Run this way long enough to know for sure whether being rooted is causing the issue. There are tons of people rooted who do NOT have this issue, so it is more than likely one of your root apps/themes is causing it.

Seems removing magisk has fixed it at least for me. The only root specific app I used was unified hosts. Sucks that it's that because I only really use root to block ads.

theycallmerayj said:
Seems removing magisk has fixed it at least for me. The only root specific app I used was unified hosts. Sucks that it's that because I only really use root to block ads.
Click to expand...
Click to collapse
Have you tried Adaway? I use very few root apps, but that is the first one I add every time. I've not had any reboots at all and it is very effective. Because you only use the one root app, you may find the culprit was UH, and not Magisk.

I have used adaway but unified seemed to block more. I'm going to try and switch back to adaway and see if I continue to go without reboots

theycallmerayj said:
I have used adaway but unified seemed to block more. I'm going to try and switch back to adaway and see if I continue to go without reboots
Click to expand...
Click to collapse
You can use different host files you don't have to use the ones that come with AdAway. Try Steven blacks out

I'm having this same issue with Magisk. I experienced it with an older Magisk on 8.0 as well.
I'm thinking about just getting rid of Magisk altogether. However, I used ES File Explorer to edit my build.prop to add the command to disable the nav bar. I'm nervous that uninstalling Magisk will cause the "your system is corrupt" message and a bootloop. However, I also have Flash Kernel installed. I wonder if the custom kernel will allow me to use the phone with the modified build.prop and without Magisk...

Help needed for crash-bootloop, logcat included

While updating/installing apps from the google playstore, the phone will crash and bootloop, and requires a full reinstall to get it working normally. I've attached 2 logcat files for both roms which give the same problem - Mokee5.1, CM13 on a clean installation with pico gapps and manually selecting several apps to install. One other custom rom also gave the same problem so I didn't bother trying any other custom roms. Reverting back to stock MIUIv8 gave no issues.
CM13 used to be mostly problem free until a few months ago I think when the update/install issue started happening. The playstore auto update is normally kept disabled on my phone so I'm unaware about when the problem really started happening.
Edit-
It doesn't seem to be happening anymore from a short test after flashing my CM13 backup but I've moved on to LO14.1
It may have something to do with some other complaints that people are having. It looks like some issue with Cynogenmod since Sept/Oct 2017 which needs some patching.
https://forum.xda-developers.com/general/help/bootloop-updating-apps-telegram-t3700773
Update to/ Installation of newest version breaks system
https://github.com/signalapp/Signal-Android/issues/7171
Several apps causes a phone reboot or boot loop
https://gitlab.com/fdroid/fdroiddata/issues/979

Can confirm the issue with CM13 on my Galaxy S3. Unfortunately, I do not know a solution. Just stick to older app versions.

Magisk modules not updating.

I tried uninstalling some modules to see if they were the cause I updated magisk to the beta channel in an attempt to fix it I also can't install new modules either. As far as I can tell I still have root as I have many things that rely on it. The logs are of the first time it happened I rebooted and it failed again giving me the second log. I reinstalled the 15.3 version of magisk and attempted to install a module it failed giving me the third log and the screenshot is after I upgraded magisk to the beta channel. @topjohnwu any idea what might be causing this I saw a post from a few months back but it didn't have a solution

is no one else having this issue?

razgriz1234 said:
is no one else having this issue?
Click to expand...
Click to collapse
I have the same issue. I have been flashing them from TWRP for now until it gets resolved.

CyberpodS2 said:
I have the same issue. I have been flashing them from TWRP for now until it gets resolved.
Click to expand...
Click to collapse
how do you flash them if they are supposed to be systemless? sorry if its a stupid question i still dont completely understand magisk as its the first phone ive had it on

solved with magisk 16.0 version

Regularly occuring errors "App was closed repeatedly" [solved]

Hello.
I am using the crDroid-ROM (version 6.7). The system is rooted with magisk, I am also using the Riru-LPosed module. The system runs absolutely fine for weeks until suddenly apps start getting closed regulary and repeatedly. Rebooting doesn't help, I always have to restore a backup to get rid of the errors.
I have absolutely no idea what causes this behaviour. I attached two logs from a short time after such errors occured. I'd be really grateful for any help or hint what I could do or how to interpret the logs.
Thank you in advance!
Edit: I thoroughly looked into the logs and found the cause. I have the 3C All-in-One Toolbox installed and recently joined the beta program. The latest beta version made the problems.
Different apps in different combinations got closed repeatedly, the log showed "system died … earlier logs will point to the root cause".
Earlier logs said "Fatal signal 11 (SIGSEGV) … (liblib3c.so) …".
I uninstalled the 3C All-in-One Toolbox beta and installed the regular version, the problems are gone. Just in case someone runs into similar problems.