SystemUI Process crashing. - Nexus 5 Q&A, Help & Troubleshooting

So I've been running the same setup since I updated to 4.4.4 about a month ago. Stock 4.4.4 rom with Xposed framework, rooted, custom kernel, custom DPI.
This morning I wake up and my phone will boot past the boot screen and just keep giving me the "Unfortunately, the process com.android.systemui has stopped.
Does anyone have stock 4.4.4 systemui file in case mine got corrupted somehow? Or should I flash the system.img? What does the system.img change if I flash it. Will if affect my apps/data/etc?

System.img replaces everything in /system. Your data and apps are in /data
Might be worth reading the sticky threads. This is pretty basic info that you should already know if you're messing with root.
Most likely the problem will be with /data anyway
Sent from my Nexus 5 using Tapatalk

I read somewhere that Xposed might be causing it. Is there a way to disable it as I can't get to it fast enough before the systemui crashes.

Isn't there an xposed removal flashable zip in the xposed thread? I think there is.
It won't be xposed itself but it could be a module or the settings of moduke causing it, which are stored in /data.
That said, removal of xposed would be the best course to take for elimination purposes.
Sent from my Nexus 5 using Tapatalk

impruv said:
I read somewhere that Xposed might be causing it. Is there a way to disable it as I can't get to it fast enough before the systemui crashes.
Click to expand...
Click to collapse
I had this problem after flashing a new nightly version of my ROM.
http://forum.xda-developers.com/xposed/framework-xposed-rom-modding-modifying-t1574401/post51306764
I went into safe mode, documented in the thread above. Uninstalled the xposed installer. Reinstalled the xposed installer apk. Updated Xblast tools to the latest version. Problem seems to have gone away. Will have to see what happens after I flash the next nightly, however. This might have something to do with the ROM overwriting /system

I came across this thread after Googling the issue I was having. I am also rooted, running 4.4.4 (CarbonROM on the Nexus 7 and stock on Moto X), and am running Xposed on both my Nexus 7, and on my Moto X. Suddenly last night I rebooted (first the N7, and then this morning the X), and lo and behold, System UI crashed on both.
I then restored my most recent nandroids on both (within a week), and all good again. Then updated all my apps that needed updating. Rebooted again because the Moto X froze, and again, System UI crash. That got me thinking that an app that was updated may be the culprit. So I updated each of my apps that had updates available one-by-one, and rebooted after each one. All good, until I came to Google+. When Google + updated, and then I rebooted, BOOM. System UI crash. Not sure if this is a conflict with Xposed or a coincidence, but Google + is definitely causing the issue for me. Hope this helps.
EDIT: I will try uninstalling Xposed then updating Google+, and report back.
UPDATE: After once again restoring my latest Nandroid, I uninstalled Xposed, rebooted, and updated all of my apps, including Google+. Rebooted, and all was good. I then went to re-install Xposed, and noticed that there were a few modules, XBlast, Gravity Box, and App Opps, that had updates available. I downloaded and installed the updates, then re-installed Xposed and rebooted. All is fine again.

sn2hotty said:
I came across this thread after Googling the issue I was having. I am also rooted, running 4.4.4 (CarbonROM on the Nexus 7 and stock on Moto X), and am running Xposed on both my Nexus 7, and on my Moto X. Suddenly last night I rebooted (first the N7, and then this morning the X), and lo and behold, System UI crashed on both.
I then restored my most recent nandroids on both (within a week), and all good again. Then updated all my apps that needed updating. Rebooted again because the Moto X froze, and again, System UI crash. That got me thinking that an app that was updated may be the culprit. So I updated each of my apps that had updates available one-by-one, and rebooted after each one. All good, until I came to Google+. When Google + updated, and then I rebooted, BOOM. System UI crash. Not sure if this is a conflict with Xposed or a coincidence, but Google + is definitely causing the issue for me. Hope this helps.
EDIT: I will try uninstalling Xposed then updating Google+, and report back.
UPDATE: After once again restoring my latest Nandroid, I uninstalled Xposed, rebooted, and updated all of my apps, including Google+. Rebooted, and all was good. I then went to re-install Xposed, and noticed that there were a few modules, XBlast, Gravity Box, and App Opps, that had updates available. I downloaded and installed the updates, then re-installed Xposed and rebooted. All is fine again.
Click to expand...
Click to collapse
Yea it was XBlast that caused the issue. I fixed it by disabling Xposed with the key taps, updating all the modules and then rebooting.

Related

[Q] How often automatic crash reboot on Android? (Lollipop)

A bit of history, I was running KK Cloudy 1.2 for a while with xposed and I'd get a 1 or 2 auto reboots from apps/system crashing. I figured this was probably because KK was old and runnign xposed modules.
Recently I clean flash upgraded to 'D850 20f Stock ROM Debloated' Lollipop ROM by cmulk.
I'm still getting one or two auto reboots a day from system crashing. Is this normal?
Even on other ROMs as a more general question how often does your guys system auto reboot from a crash? How often do you reboot manually?
Just so everyone knows how clean of flash I did...
I went through the process of restoring the factory image using LG Flash Tool and TOT file. Then I immediately stump rooted, flashified TWRP, updated TWRP to latest twrp-2.8.5.1_d850-bumped.zip, wipe in TWRP, installed D850_20F_2.0.1.c1.13-00050_Modem.zip and then Debloated_Stock_20f.zip. Then let PS reinstall apps and configured everything manually. Didn't even do a TB restore.
So is this normal behavior for android? Or just the LG G3? Or just me? Thanks!!!
Too early for me to tell. Installed yesterday morning, clean install. So far in the 24 hours, no rebooting. Only thing thus far is my LED is not signaling as designed.
The clean ROM install is 5K faster with Antutu than KK, and 17K faster than a dirty install of the same 5.01 ROM This was repeated x3 to make sure it was the clean install which made the difference for me... yup.
JeffDC said:
Too early for me to tell. Installed yesterday morning, clean instal. So far in the 24 hours, no rebooting. Only thing thus far is my LED is not signaling as designed.
The clean ROM install is 5K faster with Antutu than KK, and 17K faster than a dirty install of the same 5.01 ROM This was repeated x3 to make sure it was the clean install which made the difference for me... yup.
Click to expand...
Click to collapse
Thanks for the reply. Let me know how it goes. I heard about the led issue some folks are trying to get some logs to debug it.
I went through the process again and this time I installed a lot less apps. I'm going to see if that helps.
I didn't have any random reboots until I installed Trickster.. which was stupid of me since there's no BusyBox on the 20f release by AutoPrime
As soon as I uninstalled it after 1 reboot it hasn't happened again.
So if you've got Trickster or any other Kernel Tweak apps installed.. try uninstalling
Two days, no reboots.
I've been running autoprime's stock 20f with Xposed for a week and a half with not a single random reboot. I'm actually amazed by the performance and stability. Wiped system, cache, and data, flashed ROM, and reinstalled all apps with TB (without app data). Froze all AT&T and some LG apps with TB, and removed CarrierIQ.
Activated Xposed Modules:
AcDisplay
All Notifications Expanded
Amplify
G3 TweaksBox (1.4 beta 2)
GravityBox [LP]
Intelli3G
NotifyClean
Pandora Patcher
Play Store Changelog
Screen Filter
YouTube AdAway
EDIT: Forgot to mention that I wiped system and cache also.
cameronkelley28 said:
I've been running autoprime's stock 20f with Xposed for a week and a half with not a single random reboot. I'm actually amazed by the performance and stability. Wiped data, flashed ROM, and reinstalled all apps with TB (without app data). Froze all AT&T and some LG apps with TB, and removed CarrierIQ.
Activated Xposed Modules:
AcDisplay
All Notifications Expanded
Amplify
G3 TweaksBox (1.4 beta 2)
GravityBox [LP]
Intelli3G
NotifyClean
Pandora Patcher
Play Store Changelog
Screen Filter
YouTube AdAway
Click to expand...
Click to collapse
Similar to you, but also wiped system. Titanium installed apps and data. Only two days old at this point. Is stable so far. Very unlike my past trials with LP ROMs. Glad I waited.
JeffDC said:
Similar to you, but also wiped system. Titanium installed apps and data. Only two days old at this point. Is stable so far. Very unlike my past trials with LP ROMs. Glad I waited.
Click to expand...
Click to collapse
Forgot to include that I wiped system and cache also. So glad I waited as well. It is mind blowing how stable it is, especially with an alpha version of Xposed and so many alpha/beta modules. Just installed the beta versions of Greenify and AppSettings also, so we'll see if that introduces any instability.
After restoring apps with their data, were there any apps that you had to clear data for due to issues? Or have they all been solid?
I had all sorts of random reboots with this phone. It started while I was still running stock kitkat . Things got much better after I reformatted my ext SD card to what ever these devices prefer. I think it's fat 32?
Sent from my LG-D850 using Tapatalk
Thanks for the all replies guys.
So far I'm still averaging about a reboot or two a day since I uninstalled a bunch of apps. I don't have any apps that run regularly besides some gapps and soundcloud. I also uninstalled greenify to see if that helped. I don't have any kernel mods and not running xposed either. Probably the most non-stock thing I'm running is the XCam app. But the phone hasn't crashed while using that app.
It's interesting to hear that some of you haven't had any reboots. Makes me wonder if I have faulty hardware. I guess the only way to find out is to go back to complete stock, take the lollipop OTA update and see if it still crashes. I assume if it did I could get another warranty replacement. I also might as mention this G3 is actually a warranty replacement due to my original phone having a LCD defect.
Also I did wipe system and cache before installing lollipop modem and zip update but thanks for the ideas. Maybe I should try autoprime's stock 20f load but I can't see how that'd be any better/different than cmulks debloated 20f?
Any of you guys know a way to use logcat to capture logs just before the crash? I see there is an app to write logcat out to external SD but the crashes are intermittent so it seems I'd probably fill up my SD card before getting a good trace.
slojam said:
I had all sorts of random reboots with this phone. It started while I was still running stock kitkat . Things got much better after I reformatted my ext SD card to what ever these devices prefer. I think it's fat 32?
Sent from my LG-D850 using Tapatalk
Click to expand...
Click to collapse
Thanks slojam I will give this a try tonight.
running cloudy 2.2 without any crashes. Thanks cloudyfa
illusivenick said:
Thanks for the all replies guys.
So far I'm still averaging about a reboot or two a day since I uninstalled a bunch of apps. I don't have any apps that run regularly besides some gapps and soundcloud. I also uninstalled greenify to see if that helped. I don't have any kernel mods and not running xposed either. Probably the most non-stock thing I'm running is the XCam app. But the phone hasn't crashed while using that app.
It's interesting to hear that some of you haven't had any reboots. Makes me wonder if I have faulty hardware. I guess the only way to find out is to go back to complete stock, take the lollipop OTA update and see if it still crashes. I assume if it did I could get another warranty replacement. I also might as mention this G3 is actually a warranty replacement due to my original phone having a LCD defect.
Also I did wipe system and cache before installing lollipop modem and zip update but thanks for the ideas. Maybe I should try autoprime's stock 20f load but I can't see how that'd be any better/different than cmulks debloated 20f?
Any of you guys know a way to use logcat to capture logs just before the crash? I see there is an app to write logcat out to external SD but the crashes are intermittent so it seems I'd probably fill up my SD card before getting a good trace.
Thanks slojam I will give this a try tonight.
Click to expand...
Click to collapse
This is from skeevydude @ http://forum.xda-developers.com/att-lg-g3/development/rom-20f-stock-rom-debloated-t3059610/page13
I'm sure someone will come along who can provide more detail. It does not take long for a log to fill. I did my first few today and an 800K file was about 28 pages long. That is a lot to look through unless you know what to search for.
********************
skeevydude
Anyways, as far as the logs go, the easiest way is by using adb logcat on a PC. Look for guides on how to set all that up....then again, your rooted on LP so that should be done already
The first command to run is "adb logcat *:W >> C:\bootwarn.txt". Enable ADB, power off your phone, plug your phone in to your computer, and let it boot up to the home screen and let it sit there for a minute or two. End the command by using "control+c".
Next, run the command "adb logcat *:W >> C:\notificationwarn.txt" while intentionally doing things that should make your notification light blink -- email yourself, have someone text you a few times, call you, etc. End the command the same way. We need to catch the warnings and errors that are being thrown, so hopefully doing that will help find it.
To help you out on the commands "*:W" tells logcat to only display warnings and up and ">>" tells it to append to a file located where you tell it to be....">" all alone will overwrite a file if it's there.
Anyways, on both those commands, do them twice only changing out the ":W" for ":E" so it'll filter out errors and up.
******************
What worked for me in the first part of his instructions, was to have the command ready/typed into the command prompt on the PC but don't hit the return yet. Then, with the phone off, plug into the computer, wait for the computer to register the phone/acknowledge it, just turn on the phone, and once it starts up press the return key on the PC keyboard to launch the commend. The log will catch things as the phone starts to boot. I tried with the specific directions, but for some reason the PC could not find the device, other than how I detailed here. Just for that first command where the phone is off.
Good luck

Android is optimizing apps on reboots

Get stuck while Android is optimizing apps on reboots, this happens both on my xperia z2 tablet, and z3 phone. Both running 5.1.1 with recovery and root. Wiped dalvik and cache, problem is still there.. Anyone who has any ideas?
asjstian said:
Get stuck while Android is optimizing apps on reboots, this happens both on my xperia z2 tablet, and z3 phone. Both running 5.1.1 with recovery and root. Wiped dalvik and cache, problem is still there.. Anyone who has any ideas?
Click to expand...
Click to collapse
I had this issue with lucky patcher enabled in xposed, do you use xposed?
I'm using xposed, but not lucky patcher. Have done a Google on it, could not see anyone pointing to xposed regarding this bug, but will search more later on!
same here.
I had that issue after installing iFont (xposed) and Fontster, while trying to change fonts on my rooted z3(5.1.1).
Both of them did`t work, I'm still trying to find a way to change my z3 font.
I remove them, it didn't happen again.
I didn't think Xposed was working reliably yet with 5.1.1
Font zips:
http://forum.xda-developers.com/showthread.php?t=2448958.
I'm using ChocoCooky with no issues. Some of the fonts are chopped on my home screen for some odd reason. dpi??
heywheelie said:
I didn't think Xposed was working reliably yet with 5.1.1
Click to expand...
Click to collapse
It's working quite well, but not all modules are working. There a post somewhere listing modules that are working well.

Help - Cannot get Xposed installed on the Z5 (perpetual bootloop)

Alright, I know the Z5 is supposed to bootloop a few times (AndroPlus says 2-3 times in his rooting thread) before it'll boot with Xposed installed, but after installing the framework, mine just bootloops indefinitely.
I've tried several times on different firmwares (32.0.A.6.152 and 32.0.A.6.209 Customized_US) and with different Xposed versions (xposed-v79-sdk22-arm64.zip and xposed-v80-sdk22-arm64.zip). Each time, I let it bootloop 5+ times for good measure. Each bootup, it'll load the wallpaper, then load SystemUI, and then freeze shortly after, followed by a reboot. It does this perpetually and will not boot all the way. I have no Xposed modules nor the Installer installed on the phone, so there should be nothing interfering with the bootup in that regard. I have tried with the Xposed Installer installed beforehand as well.
The only other advice I've found online is a couple articles that suggest this old modified Xposed package "xposed-v74-sdk21-arm64-dl12345-UNOFFICIAL-20150929.zip" for Z3, Z4, and Z5 that bootloop when installing Xposed, but I'm hesitant to use a dated version and one that's for an older SDK as well. Plus, the threads on XDA recommend the latest Xposed version as working.
The phone is rooted, obviously, with SuperSU 2.46 and running AndroPlus kernel, which shouldn't be a problem. I do have a bunch of system apps (bloatware) that are uninstalled and some disabled, but I don't see why that would cause an issue. I honestly cannot think of anything else that would be causing this to not work. Really hoping someone here has experienced the same and knows the solution. I'm also curious: how many times have others had to let their device bootloop before successfully booting with Xposed?
neonixxx said:
Alright, I know the Z5 is supposed to bootloop a few times (AndroPlus says 2-3 times in his rooting thread) before it'll boot with Xposed installed, but after installing the framework, mine just bootloops indefinitely.
I've tried several times on different firmwares (32.0.A.6.152 and 32.0.A.6.209 Customized_US) and with different Xposed versions (xposed-v79-sdk22-arm64.zip and xposed-v80-sdk22-arm64.zip). Each time, I let it bootloop 5+ times for good measure. Each bootup, it'll load the wallpaper, then load SystemUI, and then freeze shortly after, followed by a reboot. It does this perpetually and will not boot all the way. I have no Xposed modules nor the Installer installed on the phone, so there should be nothing interfering with the bootup in that regard. I have tried with the Xposed Installer installed beforehand as well.
The only other advice I've found online is a couple articles that suggest this old modified Xposed package "xposed-v74-sdk21-arm64-dl12345-UNOFFICIAL-20150929.zip" for Z3, Z4, and Z5 that bootloop when installing Xposed, but I'm hesitant to use a dated version and one that's for an older SDK as well. Plus, the threads on XDA recommend the latest Xposed version as working.
The phone is rooted, obviously, with SuperSU 2.46 and running AndroPlus kernel, which shouldn't be a problem. I do have a bunch of system apps (bloatware) that are uninstalled and some disabled, but I don't see why that would cause an issue. I honestly cannot think of anything else that would be causing this to not work. Really hoping someone here has experienced the same and knows the solution. I'm also curious: how many times have others had to let their device bootloop before successfully booting with Xposed?
Click to expand...
Click to collapse
i have installed it 3-4 times on my phone , and every time , it only bootlooped once. but then i manually rebooted just to be sure. i dont really know what causes yours to bootloop, did you try wiping cache and dalvik after installation? does your device optimize apps on startup?
arismelachrinos said:
i have installed it 3-4 times on my phone , and every time , it only bootlooped once. but then i manually rebooted just to be sure. i dont really know what causes yours to bootloop, did you try wiping cache and dalvik after installation? does your device optimize apps on startup?
Click to expand...
Click to collapse
Thanks for the response. Yeah, I've tried wiping cache and dalvik after installing, before rebooting. It does go through optimizing every single app on the first boot after clearing cache, and doesn't on the subsequent reboots, which is just as is expected.
And I have also tried manually powering off the phone from the power dialog while it was booting, before it could freeze and bootloop itself. It made the device shut down gracefully, then I let it sit for about 15 minutes and turned it on, but the results were the same as well.

Just a heads up about the new marshmallow install

I installed marshmallow yesterday through Odin, using one of the walkthroughs on XDA. I was going from a custom ROM to marshmallow. The OP in the guide I was following said he didn't completely wipe his phone beforehand. I didn't either and everything installed perfectly fine, when I booted up everything seem to be fine. But then 30 seconds passed and I started to receive incessant notifications letting me know that several apps we're not responding and had to close. In total there are about 20 to 25 apps that were not responding or working or opening. I figured out though that it's a simple fix if you have this issue. Just a simple uninstall and reinstall could fix the issue if it's just happening with one app. If this happens to you though and it's like my case where it's a bunch of apps, you can simply just back everything up with titanium backup and simply restore all the apps you backed up... no uninstalling necessary. No issues since then. I don't know if I'm the only one who had this issue but hopefully this can help someone.
Also kind of off topic, does anyone know if Xposed for marshmallow on our phones is available.
I cannot say if this warrant a new thread, should have posted it in the threat you follow and let the users who will be following that guide about what you went through.
Honestly, everyone I know (especially those rooted) typically wipe their phone and more specifically ODIN the latest update before and not just dirty odin / flash it.
In my many ODIN guide you will see, they usually recommend a wipe after odin there is a reason for that, to avoid what you just went through. Permissions get all jacked up, apps FCs, wont start up, phone locks up, yadi...yada....
WIPE
P.S xpose for marshemellow been available eons ago, just look around xda.
Hey there. Xposed is available. I already installed and tested a bunch of modules. Use this guide.
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
You just need the xposed installer, sdk23 arm64 version and the uninstaller in case things get squirly.
Sent from my SM-N920T using Tapatalk
ariazad said:
Hey there. Xposed is available. I already installed and tested a bunch of modules. Use this guide.
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
You just need the xposed installer, sdk23 arm64 version and the uninstaller in case things get squirly.
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Thank you ariazad!

Xposed Issue/Question

Hello all. I'll try to explain my issue with as much detail and hopefully somebody can help me.
Anyways I picked this phone up on sale on amazon and I have already unlocked the bootloader and am successfully rooted. Now I want to use Xposed. I have been trying to get it to work for 2 days now and I am fed up.
I downloaded the correct Xposed installer(SDK 24 v88.2) and it will somewhat work but then after a reboot It says it's installed but not active and it tells me to check the logs of which are blank. I am rooted the supersu way and have twrp installed.
I've read about some script I can put in the init.d folder or something like that but I cannot seem to get it to work.
I am on emui 5.0 with android 7.0.
Can someone please for the life of me help me get this to work?
I'm simply trying to use a module for my Snapchat called snaptools.
I know it's a lot to ask but can someone please help with a tutorial or a fix/instructions?
Unluckily I'm facing the same issue on my phone without having found a solution yet, both by official or systemless Xposed versions, the result is always the same as yours; Xposed framework looks installed but deactivated after some reboots, and it stays like that until i completely remove it and reinstall it again. Then, after other 2 reboots or something like that, it gets deactivated again and again. I already tried to look for a fix on official systemless Xposed thread as you can see here from an old post of mine https://forum.xda-developers.com/showpost.php?p=74439953&postcount=5740 but even trying other Xposed Installer versions (official, topjohnwu's, dvdandroid's one...) or without using Greenify4Magisk module, the issue persists. I thought I was the only one facing this lol. I'm rooted with Magisk, so the issue must be something else than the SU manager used. Can i ask you if you have Greenify installed on your device? I have to tighten the circle of possible causes of this, because it's getting me mad.
RedSkull23 said:
Unluckily I'm facing the same issue on my phone without having found a solution yet, both by official or systemless Xposed versions, the result is always the same as yours; Xposed framework looks installed but deactivated after some reboots, and it stays like that until i completely remove it and reinstall it again. Then, after other 2 reboots or something like that, it gets deactivated again and again. I already tried to look for a fix on official systemless Xposed thread as you can see here from an old post of mine https://forum.xda-developers.com/showpost.php?p=74439953&postcount=5740 but even trying other Xposed Installer versions (official, topjohnwu's, dvdandroid's one...) or without using Greenify4Magisk module, the issue persists. I thought I was the only one facing this lol. I'm rooted with Magisk, so the issue must be something else than the SU manager used. Can i ask you if you have Greenify installed on your device? I have to tighten the circle of possible causes of this, because it's getting me mad.
Click to expand...
Click to collapse
I do not have greenify installed unfortunately. I literally got this phone 2 days ago and I've never had this issue before.
I just uninstalled the SuperSU version and Installed the magisk version for root and then installed Xposed through the magisk manager and installed the modified Xposed installer apk that can see the systemless install. Xposed has survived a couple reboots and my modules are working but I fear that it will stop working as you stated before randomly. Have you tried it my way?
Flash magisk v14 through TWRP and then install Xposed SDK 24 systemless through the magisk manager. And then installed the modified APK for Xposed installer. It's at least made it further than the normal Xposed install.
Edit: Since I've posted this I have survived 2 more restarts. I feel like I'm playing Russian roulette Everytime I restart it but so far so good.
patrick8996 said:
Flash magisk v14 through TWRP and then install Xposed SDK 24 systemless through the magisk manager. And then installed the modified APK for Xposed installer. It's at least made it further than the normal Xposed install.
Edit: Since I've posted this I have survived 2 more restarts. I feel like I'm playing Russian roulette Everytime I restart it but so far so good.
Click to expand...
Click to collapse
Ok so greenify isn't a cause of this issue... yes i tried it already, read my post above... Both by official by rovo89, and systemless by topjohnwu (with related installer obviously) the issue persists. It works, like the other one, but after some reboots (i reboot my phone once a day, at least) i find it deactivated. Yeah you said well, it's a Russian roulette ahahah i tried every version of Xposed practically...
RedSkull23 said:
Ok so greenify isn't a cause of this issue... yes i tried it already, read my post above... Both by official by rovo89, and systemless by topjohnwu (with related installer obviously) the issue persists. It works, like the other one, but after some reboots (i reboot my phone once a day, at least) i find it deactivated. Yeah you said well, it's a Russian roulette ahahah i tried every version of Xposed practically...
Click to expand...
Click to collapse
Hmm I'm still active but I haven't restarted since I posted. I'm wondering why there isn't a more detailed thread regarding this as it seems a lot of people use this phone.
Maybe you can try fresh with magisk and the modified Xposed installer for straight systemless. I've had a hell of a lot more luck this way than I have through the regular install. It's survived 5 reboots so far. Have you tried just a soft reboot inside the Xposed installer? I mean I know it's not a full restart but it may maintain Xposed and keep it active.
Maybe because only a limited set of people are facing this. And maybe only some devices suffer this. I tried both, fresh installations of normal Xposed / systemless Xposed, both didn't survived after 2 or 3 normal reboots. Yes I always rebooted by Xposed Installer when it was installed, even because i can preserve on/off button the longest i can this way, but sometimes a soft reboot isn't sufficient to apply some modifications, so i rarely used them. I daily rebooted with normal reboots. I'll try when new versions will be available at this point, i tried actual builds for 2 weeks encountering always this error so I'm not motivated on trying them again
Hey @patrick8996 did you tried latest systemless Xposed, V89? It surely works much better than previous one, V88.2, it has already survived 5 reboots while activating various modules compatibility is definitely increased with this update, I hope the issue won't represent in future
RedSkull23 said:
Hey @patrick8996 did you tried latest systemless Xposed, V89? It surely works much better than previous one, V88.2, it has already survived 5 reboots while activating various modules compatibility is definitely increased with this update, I hope the issue won't represent in future
Click to expand...
Click to collapse
I just installed it last night and so far so good.
My lasts posts regarding v88.2 were proved incorrect because once I rebooted one more time it went back to not working. But this new update to v89 seems to be working. Hopefully all goes well.
patrick8996 said:
I just installed it last night and so far so good.
My lasts posts regarding v88.2 were proved incorrect because once I rebooted one more time it went back to not working. But this new update to v89 seems to be working. Hopefully all goes well.
Click to expand...
Click to collapse
Yeah this build survives always reboots, even after recovery boots... I'd declare this issue solved :victory:
RedSkull23 said:
Yeah this build survives always reboots, even after recovery boots... I'd declare this issue solved :victory:
Click to expand...
Click to collapse
I've had a weird issue that my module's randomly stopped working. I had to disable them all in the Xposed app and restart and then enable them and restart again. Not sure if you've had this issue. But it's not that big of an issue because as long as Xposed stays active after a reboot it's a simple fix.
patrick8996 said:
I've had a weird issue that my module's randomly stopped working. I had to disable them all in the Xposed app and restart and then enable them and restart again. Not sure if you've had this issue. But it's not that big of an issue because as long as Xposed stays active after a reboot it's a simple fix.
Click to expand...
Click to collapse
Never faced this. The framework keeps staying active actually
RedSkull23 said:
Never faced this. The framework keeps staying active actually
Click to expand...
Click to collapse
My Xposed stays active it's just my modules randomly stop working inside Xposed. So I have to disable all my modules reboot and then reenable them and reboot again.
I had issues last night with updating magisk. When I updated to v15 it took all my sound away on my device. I had to uninstall it and reflash v14 and everything went back to normal.
patrick8996 said:
My Xposed stays active it's just my modules randomly stop working inside Xposed. So I have to disable all my modules reboot and then reenable them and reboot again.
I had issues last night with updating magisk. When I updated to v15 it took all my sound away on my device. I had to uninstall it and reflash v14 and everything went back to normal.
Click to expand...
Click to collapse
V15.1 should fix everything. V15.0 was messing up thousands of phones
RedSkull23 said:
V15.1 should fix everything. V15.0 was messing up thousands of phones
Click to expand...
Click to collapse
Ya I installed 15.1 and no longer have any issues. I'm happy all has been working for this long
Sent from my BLN-L24 using Tapatalk

Categories

Resources