Develop Bugs

[Q] Android is upgrading on every boot

I just bumped my lollipop rom and install xposed then I noticed that my phone shows out "android is upgrading" on every reboot. Is there any way to fix this as it is a little annoying...:crying:
Sorry for my broken English

+1 !

afaik its just a side effect of using the alpha build of xposed. sure, it can get annoying, but having xposed and this 'issue' is better than, well you know.

kp_q said:
afaik its just a side effect of using the alpha build of xposed. sure, it can get annoying, but having xposed and this 'issue' and better than, well you know.
Click to expand...
Click to collapse
This activity tends to get lengthier after every reboot. I've found that once it "seems" to loop in the "Android is upgrading" screen, to remove the battery, boot into recovery, wipe the Dalvik cache, and reboot. It will go through the lengthy procedure of updating software, but will boot a WHOLE lot faster after that.

There is a fix to that. I have the same problem that started after installing xposed on my s4 lollipop. I was able to get rid of the "androidis upgrading". the one that shows you how many apps are being installed. Now, it goes straight to "starting apps". This is not a complete fix though, since it should boot straight up but at least, it's a lot faster now. Use lucky patcher then use the option "remove all odex". That fixed the issue for me. Though not 100% fixed.

abbey666 said:
There is a fix to that. I have the same problem that started after installing xposed on my s4 lollipop. I was able to get rid of the "androidis upgrading". the one that shows you how many apps are being installed. Now, it goes straight to "starting apps". This is not a complete fix though, since it should boot straight up but at least, it's a lot faster now. Use lucky patcher then use the option "remove all odex". That fixed the issue for me. Though not 100% fixed.
Click to expand...
Click to collapse
I tried this method but it didn't work, and there are still 3 apps that are being "optimized" on every boot. Is there any way to find out which apps these are?

alqoshi4life said:
I tried this method but it didn't work, and there are still 3 apps that are being "optimized" on every boot. Is there any way to find out which apps these are?
Click to expand...
Click to collapse
Try to change the version of Xposed installer and see if that fixes the problem. By the way, the problem is 100% fixed now on my phone. I used lucky patcher to remove all odex files. I also installed another version of Xposed. The latest one did not work well so used an older version.

abbey666 said:
Try to change the version of Xposed installer and see if that fixes the problem. By the way, the problem is 100% fixed now on my phone. I used lucky patcher to remove all odex files. I also installed another version of Xposed. The latest one did not work well so used an older version.
Click to expand...
Click to collapse
Which Xposed version did you use? I'm on v68 right now which is the latest. I had v67 and it did the same thing.

V66. I tried2 later versions but this one worked for me.

I have a Oneplus One but I have the same issue. Every damn boot. Android is starting. optimizing app 1 of 121.
I also have the latest version of xposed.
I know not the forum for the OPO but just thought I'd let you guys know other phones face it too and hopefully find a solution to this.
I had to make a really important call and my phone restarted all on its own. That's bad enough but add to the random restart sitting for 5 minutes to wait for android to finish optimizing

abbey666 said:
V66. I tried2 later versions but this one worked for me.
Click to expand...
Click to collapse
I tried v66 like you recommended and the same thing happened. So it must be something else that solved your problem. I guess I can live with it though.

have the same problem with my g3.. everybody have data backup ? )

BlackGodRaven said:
have the same problem with my g3.. everybody have data backup ? )
Click to expand...
Click to collapse
Try the newest Xposed framework v69. Solved my problem completely after a dalvik cache wipe.

alqoshi4life said:
Try the newest Xposed framework v69. Solved my problem completely after a dalvik cache wipe.
Click to expand...
Click to collapse
l solved it too ) l transfer backup to sd card )

abbey666 said:
There is a fix to that. I have the same problem that started after installing xposed on my s4 lollipop. I was able to get rid of the "androidis upgrading". the one that shows you how many apps are being installed. Now, it goes straight to "starting apps". This is not a complete fix though, since it should boot straight up but at least, it's a lot faster now. Use lucky patcher then use the option "remove all odex". That fixed the issue for me. Though not 100% fixed.
Click to expand...
Click to collapse
Trying this now...my G3 crashes for whatever reason from time to time after my Tasker that disables bluetooth as soon as the USB power is disconnected from the car.
Currently on version 79. Patched it with Lucky Pater and removed all odex; rebooted (got stuck but battery out & booted normally).
I'll report if there are any further issues

Okay it's very odd it seems like there's an issue with my LG G3 disconnecting bluetooth from the stock head unit in '13 WRX. If I try pushing the power button off on the radio then shut off the engine (Tasker shuts down bluetooth) then I don't seem to have this issue with the phone crashing. I've yet to have the phone crash if it's on A/C power and Tasker performs the same function.

Smart lock does not work after root(magisk).

I found the smart lock did not work after root, no matter using beta magisk 14.5 or stable 14. I would like to make sure if this is a problem of my own, or a general case, so that I can decide whether to report this to the developers. Thank you.

I'm using beta 14.5 and when I open smart lock it asks for a pin and then shows a blank white screen. No options to add devices. I've been using face unlock so I didn't notice until I checked after seeing this.

Try this.
Oneplus forums
It worked for me.

shadeau said:
I'm using beta 14.5 and when I open smart lock it asks for a pin and then shows a blank white screen. No options to add devices. I've been using face unlock so I didn't notice until I checked after seeing this.
Click to expand...
Click to collapse
Exactly the problem I have, so this should be a problem of magisk. I guess magisk is not compatible with 5t now, some other people report they have problem with their wifi after root (I also found wifi is slower).
I tried supersu as well, but it can cause a battery drain. So there is no perfect root for 5t till now.

Beaster said:
Try this.
Oneplus forums
It worked for me.
Click to expand...
Click to collapse
It will become blank again after reboot... It's perfect if I uninstall magisk or use supersu instead.

simonand said:
It will become blank again after reboot... It's perfect if I uninstall magisk or use supersu instead.
Click to expand...
Click to collapse
I second that, it turns blank again after reboot. or sometime during use. So irritating.

I just found out that Magisk itself doesn't seem to be the problem.
I did a fresh install, installed magisk without any problem. The problem started after installing a module from within Magisk...
After that Smart Lock blanked out and removing the module doesn't change anything.

Bart1981 said:
I just found out that Magisk itself doesn't seem to be the problem.
I did a fresh install, installed magisk without any problem. The problem started after installing a module from within Magisk...
After that Smart Lock blanked out and removing the module doesn't change anything.
Click to expand...
Click to collapse
What module did you install? I seem to get this problem even with out magisk. Maybe twrp is the cause?

tyrone1 said:
What module did you install? I seem to get this problem even with out magisk. Maybe twrp is the cause?
Click to expand...
Click to collapse
I guess I was mistaken... A later attempt I also got a blank screen after a while.
Not shure why. In the beginning it seems all ok also after a couple of reboots, but then after a certain time and a reboot it's there. again.

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...

Question magisk module caused bootloop. how to remove module in safe mode.

a magisk module has caused a bootloop. I can enter safe mode. how do I remove the module whilst in safe mode? thre's no sign of magisk? have I lost root in safe mode?

whatsisnametake2 said:
a magisk module has caused a bootloop. I can enter safe mode. how do I remove the module whilst in safe mode? thre's no sign of magisk? have I lost root in safe mode?
Click to expand...
Click to collapse
If you are in safe mode, then just reboot. Your Magisk mods will be disabled and then you can remove the offending module in the Magisk app.

thanks for the reply, yes I figured that out in the end. ha! came very close to resetting the phone!

After reboot my nacisk modules are still active and installed.
I thought ones phone is rebooted in save mode modules will be disabled.
Am I doing something wrong?

netgar said:
After reboot my nacisk modules are still active and installed.
I thought ones phone is rebooted in save mode modules will be disabled.
Am I doing something wrong?
Click to expand...
Click to collapse
Safe mode disables all Magisk Modules. Rebooting after entering safe mode, all Magisk Modules will remain disabled until you individually re-enable any of them.
You're following the correct directions to get into safe mode? It's tricky and temperamental, and also, at least if you use a third-party launcher, all widgets will need setting up again, but not sure if the same thing happens with Pixel Launcher after entering safe mode, too.
Google's Help Page for Find problem apps by rebooting to safe mode - this can be a lifesaver and keep you from having to do a restore to 100% complete stock or even from having to do a factory reset. This will deactivate all Magisk modules, and they'll remain deactivated even after you boot normally after briefly booting to safe mode. You can reenable the Magisk modules as you wish to try to narrow down the problem if it was caused by a Magisk module. This can even get things working again after a Magisk Module wasn't finished installing and potentially causing a bootloop.
Click to expand...
Click to collapse

roirraW "edor" ehT said:
Safe mode disables all Magisk Modules. Rebooting after entering safe mode, all Magisk Modules will remain disabled until you individually re-enable any of them.
You're following the correct directions to get into safe mode? It's tricky and temperamental, and also, at least if you use a third-party launcher, all widgets will need setting up again, but not sure if the same thing happens with Pixel Launcher after entering safe mode, too.
Click to expand...
Click to collapse
Thank for your response.
Yes, in save mode I can see that everything is disabled even magisk, ones I reboot to system my modules are still installed. Weird...
I don't use any custom launcher.
Do I need to have broken module that actually make my phone blootloop? And than save mode will disable all modules?
Thank you again for help

netgar said:
Thank for your response.
Yes, in save mode I can see that everything is disabled even magisk, ones I reboot to system my modules are still installed. Weird...
I don't use any custom launcher.
Do I need to have broken module that actually make my phone blootloop? And than save mode will disable all modules?
Thank you again for help
Click to expand...
Click to collapse
You're welcome. The modules won't be uninstalled, only disabled - there's a toggle on every module to re-enable it again. No, you don't need to have a broken module that makes your phone bootloop in order for safe mode to disable all Magisk Modules.

roirraW "edor" ehT said:
You're welcome. The modules won't be uninstalled, only disabled - there's a toggle on every module to re-enable it again. No, you don't need to have a broken module that makes your phone bootloop in order for safe mode to disable all Magisk Modules.
Click to expand...
Click to collapse
So something doesn't work for me.
My modules are still enabled.
Picture is posted right after rebooting from save mode.
Edit
I noticed that my widgets are only disabled

netgar said:
So something doesn't work for me.
My modules are still enabled.
Picture is posted right after rebooting from save mode.
Edit
I noticed that my widgets are only disabled
Click to expand...
Click to collapse
I believe you. I have no idea. The last time I used safe mode was probably 7-8 months ago or more. It definitely didn't behave like that for me.
Is it actually a problem, since you're not boot looping - since you're able to boot normally anyway?

roirraW "edor" ehT said:
I believe you. I have no idea. The last time I used safe mode was probably 7-8 months ago or more. It definitely didn't behave like that for me.
Is it actually a problem, since you're not boot looping - since you're able to boot normally anyway?
Click to expand...
Click to collapse
I am just testing just in case installing bad magisk module.
Couple months ago I needed reinstall all my phone because of it.
I guess I still can't risk.

netgar said:
I am just testing just in case installing bad magisk module.
Couple months ago I needed reinstall all my phone because of it.
I guess I still can't risk.
Click to expand...
Click to collapse
Do you just disable them manually before updating, or you just don't update? I disable all mine manually before updating, although certainly once you enable any again, yes, it's possible for it to start boot looping. Usually by then I'll hear about these certain modules causing bootloops on the latest update, though.

roirraW "edor" ehT said:
Do you just disable them manually before updating, or you just don't update? I disable all mine manually before updating, although certainly once you enable any again, yes, it's possible for it to start boot looping. Usually by then I'll hear about these certain modules causing bootloops on the latest update, though.
Click to expand...
Click to collapse
I always disable all modules before system update. I don't have a problem with that.
I got a blootloop after installing "bad" magisk module. That's why I installed bootloop saver module but it doesn't seems to work for me.

netgar said:
I always disable all modules before system update. I don't have a problem with that.
I got a blootloop after installing "bad" magisk module. That's why I installed bootloop saver module but it doesn't seems to work for me.
Click to expand...
Click to collapse
Yeah, I gave up on Bootloop Saver Module. I see you still have it installed. I suggest uninstalling it - I wonder if it's interfering with the stock Android experience after rebooting from safe mode.

roirraW "edor" ehT said:
Yeah, I gave up on Bootloop Saver Module. I see you still have it installed. I suggest uninstalling it - I wonder if it's interfering with the stock Android experience after rebooting from safe mode.
Click to expand...
Click to collapse
I will test it. Thank you for your suggestion.

If all else fails you can just get rid of them all in adb
Code:
magisk --remove-modules
Source
Frequently Asked Questions
The Magic Mask for Android
topjohnwu.github.io

Question pixelify bootloop error

does anyone else have an issue with installing pixelify? i used to be able to install 2.1 but then i started to have issues with it not working with android auto so i uninstalled it and reinstalled it and now i keep getting bootloop errors
i am on stock OOS/A13 and have the bootloop protector module installed (which is what typically saves me lol) but ive deleted everything associated with pixelify i think within my phone after uninstalling it and getting the same issue, i ran the ADB logcat command while it was bootlooping and got the following attachment but im not really sure where to even begin looking in it, this issue only occurs when trying to install pixelify and i can install other modules

I'm experiencing the same. It looks like it's been reported to the developer. Hopefully, he can sort it out. https://github.com/Kingsman44/Pixelify/issues/144

Veid71 said:
does anyone else have an issue with installing pixelify? i used to be able to install 2.1 but then i started to have issues with it not working with android auto so i uninstalled it and reinstalled it and now i keep getting bootloop errors
i am on stock OOS/A13 and have the bootloop protector module installed (which is what typically saves me lol) but ive deleted everything associated with pixelify i think within my phone after uninstalling it and getting the same issue, i ran the ADB logcat command while it was bootlooping and got the following attachment but im not really sure where to even begin looking in it, this issue only occurs when trying to install pixelify and i can install other modules
Click to expand...
Click to collapse
If you use pixelify to benefit from Google Photos, I recommend that you use this lite module.

yassine2217 said:
If you use pixelify to benefit from Google Photos, I recommend that you use this lite module.
Click to expand...
Click to collapse
Thanks! what does it do?

Veid71 said:
Thanks! what does it do?
Click to expand...
Click to collapse
It provides you with unlimited storage for Google Photos and Drive.