[BUG?] Random Boot-stuck on Android 5.X - Xposed General

I recently updated my module's xposed code, and now sometimes get stuck at boot when I updated the Xposed module before, although I didn't touch the Main class.
I released it yesterday, and now several users report the same issue. I and the users were able to fix the bootstuck by wiping dalvik cache, for some it worked instantly, but I had to wipe it several time to get it to boot again.
Now I am not sure if my module is the cause, because I don't see any errors, it sometimes just works, and although it first seemed so, the app isn't always the last Xposed module which gets loaded, thus not definitely the reason for the bootstuck.
UPDATE: Found the issue. It seems that referencing other package classes which are not part listed in xposed_init cause this bootloop. @rovo89, is this fixable?

"Note that this is still an alpha version and for Lollipop on ARMv7+ devices only.
Please install it only if you're willing to take the risk of boot loops. Just because it's working fine and stable for me doesn't mean it will work for everyone the same way."
Rovo mentioned this was to be expected.
Sorry I'm not much of help. :/ My guess is that results vary from devices.

MisterCoolBeans said:
"Note that this is still an alpha version and for Lollipop on ARMv7+ devices only.
Please install it only if you're willing to take the risk of boot loops. Just because it's working fine and stable for me doesn't mean it will work for everyone the same way."
Rovo mentioned this was to be expected.
Sorry I'm not much of help. :/ My guess is that results vary from devices.
Click to expand...
Click to collapse
Well, of course I know. But if @rovo89 and @romracer as well as @C3C076 aren't knowing about, they cannot fix.

I tried using just xposed frakework installed, without any modules and still got this bug. Weird.

delete

Related

[Q] Xposed and cataclysm, System-UI FC

So I know cataclysm is long since dead. But it does seem to still work with the latest factory image. Surprisingly enough. But something about flashing the latest xposed as well causes a System-UI force close loop. I know it's a long shot, and I've google'd it to see if anyone else may have asked or found an answer...but is there a way to get them all to play nice with each other? Aside from flashing an old version of xposed?
jmoore4294 said:
So I know cataclysm is long since dead. But it does seem to still work with the latest factory image. Surprisingly enough. But something about flashing the latest xposed as well causes a System-UI force close loop. I know it's a long shot, and I've google'd it to see if anyone else may have asked or found an answer...but is there a way to get them all to play nice with each other? Aside from flashing an old version of xposed?
Click to expand...
Click to collapse
Cata and Xposed are Both changing the framework. You Have to count on issues or under the hood problems. Because the stock Android also had changed the framework.

Xposed Modules On Stock Firmware Discussion

....!!!!PLEASE ONLY POST ABOUT XPOSED AND MODULES YOU ARE USING ON AT&T STOCK FIRMWARE NOT THE UNLOCKED U FIRMWARE AS THERE MAY BE DIFFERENCES IN EXPERIENCE AND USABILITY THAT MAY CAUSE PROBLEMS!!!!....
This thread is for anyone to posted what Xposed modules you use and if they are or are not working. It will also be a thread to let others see who are new to xposed or havent used it on their s7 edge yet what is and isn't working as well as identifying what modules should be avoided because they are causing problems with the phone ex. lag, freezing, bootloops, other. please comment what you are using along with your experience and any news related to xposed and or modules. i will (when i have time) edit this post with what i have installed what does and doesnt work as well as posting what others put here. of course there will be a working and not working section that will be updated when things break or become useable. hope this thread helps some people out and saves some time and trouble.
....AGAIN!!!!PLEASE ONLY POST ABOUT XPOSED AND THE MODULES YOU ARE USING ON STOCK AT&T FIRMWARE ONLY AS THERE CAN BE DIFFERENCES BETWEEN WHAT DOES AND DOESNT WORK ON STOCK FIRMWARE AND THE UNLOCKED U FIRMWARE!!!!....
....WORKING MODULES ARE IN POST #2....
....modules that work for me and or others....will be update as i use working modules or people post or pm working modules....i will not be including modules that do not work just to save time and space. At this point in time just assume it doesnt work unless someone can confirm it, dont want to kill your phone!!!!....
1. Greenify
2. Amplify
3. Xtouchwiz (turned some setting off that were on by default!!!! Fake system status i'm guessing is best turned off!!!!)
4. Neopower menu
rob219 said:
****ONLY ANPLIFY AND GREENIFY ARE WOTKING OUT OF THE ONES I HAVE INSTALLED IN THE PICS, ALL THE OTHER MODULES SHOWN ARE NOT WORKING AS OF NOW ON MY DEVICE****
Click to expand...
Click to collapse
Did you have any luck with RootCloak or XTouchWiz?
TehPirate_ said:
Did you have any luck with RootCloak or XTouchWiz?
Click to expand...
Click to collapse
rootcloak im unsure as i have uninstalled it (didnt need it) and xtouchwiz i hacent retried. something (maybe a setting in xtouchwiz) was giving me some sim card pop up that wouodnt go away on boot and wouod make me reboot to recovery to do something to ky sim that just failed and the pop up would be there upon boot. i had to odin to get rid of it. it happened 3 times and each time it happened i had rootcloak and xtouchwiz installed. since removing both i hacent had a problem. so no i didnt and i believe one of them caused the problem. if anyone is using both or one or the other let me know what you do and dont have enabled or disabled in each module.
rob219 said:
rootcloak im unsure as i have uninstalled it (didnt need it) and xtouchwiz i hacent retried. something (maybe a setting in xtouchwiz) was giving me some sim card pop up that wouodnt go away on boot and wouod make me reboot to recovery to do something to ky sim that just failed and the pop up would be there upon boot. i had to odin to get rid of it. it happened 3 times and each time it happened i had rootcloak and xtouchwiz installed. since removing both i hacent had a problem. so no i didnt and i believe one of them caused the problem. if anyone is using both or one or the other let me know what you do and dont have enabled or disabled in each module.
Click to expand...
Click to collapse
I appreciate your feedback. It would be inaccurate for me to reply with mine as I use the unlocked firmware. But in this case, the results were the same more or less.
TehPirate_ said:
I appreciate your feedback. It would be inaccurate for me to reply with mine as I use the unlocked firmware. But in this case, the results were the same more or less.
Click to expand...
Click to collapse
i have since installed xtouchwiz and have no problems i turned a few things off that were on by default. i turned off fake system status and the disable scaling feature that was on. it works. rootcloak i have also reinstalled but i don't think it works. im not sure, i know snapchat has problems logging in if your rooted and i am experiencing this problem with or without rootcloak so i believe it is not working but i could be wrong.
Hi, I am new to xda and Android as a whole. So I have rooted (SM-G935A) and I can't find any way to install xposed because TWRP doesnt support the snapdragon variants. Do you mind telling me how you did it?
RileyIssKing said:
Hi, I am new to xda and Android as a whole. So I have rooted (SM-G935A) and I can't find any way to install xposed because TWRP doesnt support the snapdragon variants. Do you mind telling me how you did it?
Click to expand...
Click to collapse
flashfire

[Rant -- sorry] SystemUI has stopped happens way too often...

Since Magisk 11 released and even now with 12, rebooting feels like a roll of the dice between flashing something or installing a module. I don't have any real development experience, but had tried building a module or two and troubleshooting another in the past few weeks, which resulted in eventually booting to the error SystemUI has stopped... This has happened several times in a day even. Now today, I push the April security update, install Magisk 12, and slowly start piecing my setup together 1 by one to make sure everything works properly. Then suddenly another SystemUI has stopped error... Only way to fix it is to restore from TWRP or factory reset. A timely process. Flashing zips in TWRP in the past hasn't resulted in this for me ever... That's going back to the Donut days on my Samsung Moment, LG Optimus, HTC One M7, and now my Nexus 6. I really want to love Magisk, but its very frustrating to get so far then to have to restore and start again.
Is it something I'm doing wrong? Is there a better way to resolve this when it occurs? Is there a way to avoid this error? Is this even a Magisk issue and the fact it hasn't happened before is a matter of luck? I don't even know what's causing it...
Use MagiskMount to mount magisk.img to /magisk and delete the installed module
duxishere said:
Use MagiskMount to mount magisk.img to /magisk and delete the installed module
Click to expand...
Click to collapse
Yes, I do that. That's not even the problem. It's when I finally boot after installing something or removing a module, SystemUI stops and I can't do anything.
Hm... I did notice this issue a couple of times on my Nexus 6 as well. It did happen a few times when installing modules that weren't quite compatible or otherwise had issues (I was experimenting and it was never quite reproducible), but mainly when trying to do a TWRP backup or restore (completely reproducible, 100% of the times). I figured it was my device acting up and never really connected it with Magisk.
I'm going to do some further testing...
gk1984 said:
Yes, I do that. That's not even the problem. It's when I finally boot after installing something or removing a module, SystemUI stops and I can't do anything.
Click to expand...
Click to collapse
Exactly my problem too. Im using redmi note 3 with lineage os and rr. The problem sam like this. Please tag me if you find the solution.
batmi said:
Exactly my problem too. Im using redmi note 3 with lineage os and rr. The problem sam like this. Please tag me if you find the solution.
Click to expand...
Click to collapse
I concluded it's a module I was using. Actually, the module I tried writing myself. Stopped using, no more issues. Well, at least not yet.

Confused about installing Xposed on Nougat

My apologies, but I'm overwhelmed by installing Xposed on Nougat and I'd like some help from a kind soul.
I'm running Android 7.0 on an LG G5 RS988, and have root and superuser access, with TWRP.
I've installed the Xposed Installer provided by dvdandroid (XposedInstaller_by_dvdandroid_09_09_17.apk)
...then used that to flash install the framework by PurifyOS (26-07-17-xposed-v87-sdk24-Xposed-by-PurifyOS.zip).
Unfortunately on the homescreen of the Installer, I get the message "installed, but not active".
The log includes a lot of information about java.lang.ClassNotFoundException errors for com.android.internal.policy.impl.GlobalActions
I'm unsure of how to proceed, out of ignorance. I don't understand the role of Magisk (or what it is), how Nougat works relative to Xposed, or basically anything that's happened with Xposed since Marshmallow. I've read the threads and unfortunately am still confused.
Could someone please help me out?
@mean_liar you can ask dvdandroid and send him a log with the xposed error i think it can be a sdk issue and he'll might send u a zip with the files he wants u to test
Sent from my FRD-L09 using Tapatalk
I revisited the problem, uninstalled, cleared cache, reinstalled... now it is activated and installed, but the modules don't seem responsive regardless of activation.
I'm going to sit on this a day, take some time, and figure out if I should be trying Magisk or not.
mean_liar said:
I revisited the problem, uninstalled, cleared cache, reinstalled... now it is activated and installed, but the modules don't seem responsive regardless of activation.
I'm going to sit on this a day, take some time, and figure out if I should be trying Magisk or not.
Click to expand...
Click to collapse
Try http://www50.zippyshare.com/v/B04DN0DB/file.html
And select the sdk-23 apk there seems to be a bug if a higher sdk is set
Also clear dalvik-cache it should help you.
Sent from my FRD-L09 using Tapatalk

Magisk v23.0 slows down phone

Hello, I have the following problem, the operating system and the Greenify application worked very well on Magisk v22.1, but after updating to v23.0, there are problems, the operating system itself on the phone is slow and in the Greenify application, I am dissatisfied with this update v23.0 .
Please help what can be done about it.
My HTC U11, Stock ROM.
Greetings.
Noticed this on my Pixel 3 running stock as well. I would have to restart the phone several times to get it running.
GrandAdmiral said:
Noticed this on my Pixel 3 running stock as well. I would have to restart the phone several times to get it running.
Click to expand...
Click to collapse
I understand it turns out there is a problem with this v23.0 update, I wonder who else has a problem with it, besides us.
I'm not seeing any similar issues on v23 (and haven't on the canary releases leading up to it either). That doesn't mean there isn't a possible issue though...
Have you guys checked your modules if there's a possible culprit there?
Didgeridoohan said:
I'm not seeing any similar issues on v23 (and haven't on the canary releases leading up to it either). That doesn't mean there isn't a possible issue though...
Have you guys checked your modules if there's a possible culprit there?
Click to expand...
Click to collapse
I only have these modules and they were on v22.1, they did not cause any problems like this v23.0.
That the modules worked fine in earlier releases doesn't necessarily mean that they work on current/future release...
You need to do some troubleshooting if you're interested in getting to the bottom of this.
Disable modules to figure out if it's one of those. Disable MagiskHide to see if it's connected to that. Etc...
Didgeridoohan said:
That the modules worked fine in earlier releases doesn't necessarily mean that they work on current/future release...
You need to do some troubleshooting if you're interested in getting to the bottom of this.
Disable modules to figure out if it's one of those. Disable MagiskHide to see if it's connected to that. Etc...
Click to expand...
Click to collapse
It may be that the module may not work properly on this v23.0.
Okay, I will follow your suggestion on what to do with it, I'll check it out and let you know.
From the very beginning, MagiskHide is turned off.
MagiskHide off, module turned off, Riru, Riru - Edxposed, phone restart, phone working, fast as it was on v.22.1, probably something is wrong with these modules.
Sounds like EdXposed is causing some issues then... You might want to check the Xposed forums and/or EdXposed Github issues to see if there's some mention of similar problems there.
Didgeridoohan said:
Sounds like EdXposed is causing some issues then... You might want to check the Xposed forums and/or EdXposed Github issues to see if there's some mention of similar problems there.
Click to expand...
Click to collapse
I will check the forums, maybe I will come across something, and if not, I will also write a post there, maybe a new update of these modules will fix something.
Thanks for your interest in the topic.

Categories

Resources