Crashes (red LED, black screen, reboot) with running Xposed

[jelbo]

Guys. Did you try older versions of xposed for those who have problems? http://4pda.ru/forum/index.php?s=&showtopic=425052&view=findpost&p=41161349

Just v78 for me. Same thing.

So far, running great here, v79 and the reduced amount of apps I mentioned earlier.

 

[alex009988]

Just v78 for me. Same thing.

So far, running great here, v79 and the reduced amount of apps I mentioned earlier.

What about even earliest versions such as v74 and around(it should also support android 5.0.x), for instance?

 

[alex009988]

Now, I had flashed xposed v79 sdk21 arm via twrp and after I tried to install xposedinstaller 3.0 alpha 4 apk but it's not installing. What to do? Thanks in advance.
EDIT 1 I uninstalled framework, installed Xposed installer, flashed framework again but now no modules are not installing.
EDIT 2 WELL, the exact problem is framework, I tried both 78 and 79 with the same result, when it flashed, no modules or xposedinstaller itself can't be installed. And with framework each loading goes with app optimizations.

 

[jelbo]

Now, I had flashed xposed v79 sdk21 arm via twrp and after I tried to install xposedinstaller 3.0 alpha 4 apk but it's not installing. What to do? Thanks in advance.

You'll need the arm64 version.

EDIT 1 I uninstalled framework, installed Xposed installer, flashed framework again but now no modules are not installing.
EDIT 2 WELL, the exact problem is framework, I tried both 78 and 79 with the same result, when it flashed, no modules or xposedinstaller itself can't be installed. And with framework each loading goes with app optimizations.

I had this once as well. APK's refused to install with some unknown error in the package installer, right after installing Xposed. Something went wrong during the initial boot I guess. I fixed this by installing Xposed again (flashing the .zip) and clearing Cache/Dalvik.

The optimizing apps bit should only happen once, after clearing Cache/Dalvik from TWRP.

The 3.0 alpha 4 APK can be installed beforehand, it's just a GUI for the modules, really.

 

[alex009988]

Thank you very much jelbo for your help, .clearing dalvik cash really help me. After the first boot a catch a first black screen reboot, but now it seems it works more or less stable. After xposed installed, album app stops to work indeed. Could you recommend alternative for this app?

 

[jelbo]

Thank you very much jelbo for your help, .clearing dalvik cash really help me. After the first boot a catch a first black screen reboot, but now it seems it works more or less stable. After xposed installed, album app stops to work indeed. Could you recommend alternative for this app?

Yes, you always need to wipe Cache/Dalvik after flashing or uninstalling Xposed.

So you had the crash as well? Did this happen right after the optimizing apps stage? How many user apps do you have installed?

As for the Sony Album alternative, I have never even started that app, but I've been using QuickPic since my first Android days. It's great. It's also more or less dead since it was taken over by Cheetah Mobile, but you can install a 'neutered' version that won't be updated by Google Play. Still works fine.

About the test I'm running: I'm at 57 user apps whilst running Xposed v79 and still haven't had a single crash.

 

[alex009988]

The crash happened after 5 seconds as system booted when I was in menu and try to look at downloads.
I have 71 apps. I experience only one crash for the time being. So, look at what will happen further(tomorrow ).

 

[alex009988]

Now I'm testing xposed v79 because with v78 I had 7 bootloops in two days.

 

[killdozer56]

Now I'm testing xposed v79 because with v78 I had 7 bootloops in two days.

I await your return with experience Xposed v79 to try myself. Thanks

 

[jelbo]

I await your return with experience Xposed v79 to try myself. Thanks

I've been running Xposed v79 fine for several days now and I'm at 76 user apps now, from which 23 are Xposed modules!

It doesn't hurt to flash Xposed and test it. If you get crashes/reboots or bootloops, flash the Xposed Uninstaller, clear Cache/Dalvik (always do that after flashing anything Xposed) and be back where you were again.

As for my test, I expect one of these things:

1. I'll experience an isolated random crash/reboot, unrelated to Xposed (moving on...)
2. I'll experience an isolated random crash/reboot, related to some root-related tweak I did (moving on...)
3. I'll suddenly hit the crashes/reboots again, which will keep happening <- Waiting for this. This could mean that 1) I've installed or tweaked something that's responsible for the crashes, 2) I've hit some limit in the amount of apps that can be installed in our specific scenario (Z4T+Xposed), which would then be an Xposed bug or 3) another explanation.
4. Everything will keep running fine, with me eventually being at the same level of apps I had when I had the issue. Which means that uhm.. I'll have to think. Probably the order I did things was the only working way. Which is clean ROM > SuperSU > Xposed > lots of apps, instead of clean ROM > SuperSU > lots of apps > Xposed. Maybe Xposed doesn't like having to suddenly 'dex2oat' a heap of apps, but doing them incrementally is OK.

/edit: got my first random crash/reboot. Screen froze and it happened. I disabled a few Xposed modules I added recently and manually rebooted. If that won't help, I'll uninstall a few apps.

 

[DHGE]

Too restrictive in XPrivacy?

I experienced the crash too!

Somehow my GSS-Reader app vanished. I do not know why...

Easy reinstall from appstore.
Then XPrivacy asked what to do about rights.

Among other things I disabled IPC -> crash

Allowing it things were smooth as before.

So @jelbo: if you use restrictive settings in your xposed modules it could be an option too experiment with the switches. Takes much time. Greping logs seems to be easier.

 

[jelbo]

I experienced the crash too!

Somehow my GSS-Reader app vanished. I do not know why...

Easy reinstall from appstore.
Then XPrivacy asked what to do about rights.

Among other things I disabled IPC -> crash

Allowing it things were smooth as before.

So @jelbo: if you use restrictive settings in your xposed modules it could be an option too experiment with the switches. Takes much time. Greping logs seems to be easier.

Thanks for reporting. Your case seems to be specifically related to XPrivacy-restrictions, or maybe restrictions in general. I haven't used XPrivacy yet on my Z4 Tablet at all, so the source of my random reboots must have been another one. It could still have been restriction-related, as I have used (and still use) AFWall+ to restrict internet access for various user and system apps. I might have used AppOpsXposed as well in the period of time with my Xposed crashes, I forgot. Because of your finding, my suspicion towards that Xposed module is now pretty high @ all other's who have/have had crashes with Xposed, did you have AppOpsXposed enabled by any chance?

As for AFWall+, I don't suspect restrictions from it to be the root cause, because without Xposed installed, AFWall+ ran fine, and combined with Xposed enabled I've only had one crash so far in my ongoing test. As a reaction I disabled some Xposed modules and got rid of some apps, so I'm still on the path of suspecting the cause being either one of those uninstalled/disabled apps/modules being the culprit, or the amount of apps passing a certain threshold that makes the Xposed go crashy.

Hope I still make sense. :silly:

 

[alex009988]

Hi. Another user suggest to deoxed whole system totally in such a way as to there would be no odex file. http://4pda.ru/forum/index.php?s=&showtopic=706675&view=findpost&p=46389415
Suppose we do it with jualdroit lollipop batch deodexer. It's easy, one click needed. But how to push all stuff into the system back and delete all odex files. It's a question of hundreds of files which should be moved manually. It's very, very painstaking job. And there's a big risk to crash the system.
So, I'd like you to share your opinion about it.

 

[jelbo]

The random reboots are back and I'm pretty clueless. I posted a summary on the issue I posted on rovo89's GitHub, but so far I haven't had a response. I did get some interesting logs though. I'll crosspost here:

I got a look at the tombstone_00 that was written, and it says pid: 3667, tid: 3688, name: Signal Catcher >>> com.google.android.gms <<<

This looks an awful lot like @dl12345's Xperia issue that got fixed a long time ago.

Since this report, I've started freshly and ran the device for some time without Xposed. While having quite a bit of apps installed, I flashed Xposed again and it started to randomly crash (again). I managed to just catch one using continuous logcat logging using CatLog.

The (imo) relevant logcat bits:

01-28 20:19:10.371 I/Process ( 1734): Sending signal. PID: 32331 SIG: 3
01-28 20:19:10.378 I/art (32331): Thread[9,tid=32344,WaitingInMainSignalCatcherLoop,Thread*=0x7f74637800,peer=0x12c00080,"Signal Catcher"]: reacting to signal 3
[COLOR="Red"]01-28 20:19:10.484 F/libc (32331): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x4 in tid 32344 (Signal Catcher)[/COLOR]
01-28 20:19:10.571 I/Process ( 1734): Sending signal. PID: 1734 SIG: 3
01-28 20:19:10.573 I/art ( 1734): Thread[9,tid=1748,WaitingInMainSignalCatcherLoop,Thread*=0x7f74637800,peer=0x12c02080,"Signal Catcher"]: reacting to signal 3
[...]
[COLOR="red"]01-28 20:19:10.656 I/DEBUG ( 652): pid: 32331, tid: 32344, name: Signal Catcher >>> org.kustom.wallpaper.service <<<[/COLOR]
01-28 20:19:10.656 I/DEBUG ( 652): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x4
01-28 20:19:10.726 I/DEBUG ( 652): x0 0000000000000028 x1 0000000000000004 x2 6c74636f695f5f0e x3 0000000000000070
01-28 20:19:10.727 I/DEBUG ( 652): x4 0000007f81ed4a00 x5 0000007f81ed4998 x6 0000000000000000 x7 0000000000001002
01-28 20:19:10.727 I/DEBUG ( 652): x8 0000007f81ed4760 x9 0000000000001002 x10 00000000000000b0 x11 0000007f6c930c07
01-28 20:19:10.727 I/DEBUG ( 652): x12 0000000000000020 x13 29d54f8f157c1948 x14 29d54f8f157c1948 x15 0000007f81ed41dc
01-28 20:19:10.727 I/DEBUG ( 652): x16 0000007f82e2bfd8 x17 0000007f82a7fac8 x18 0000000000000028 x19 0000007f81ed4760
01-28 20:19:10.727 I/DEBUG ( 652): x20 0000007f746c9048 x21 0000007f81ed4990 x22 0000007f6c80e0c0 x23 0000000070b89838
01-28 20:19:10.727 I/DEBUG ( 652): x24 0000007f82da1be0 x25 0000007f81ed4990 x26 0000007f82d8edf8 x27 0000007f82da61e8
01-28 20:19:10.727 I/DEBUG ( 652): x28 0000007f82d7a000 x29 0000007f81ed46f0 x30 0000007f82ce211c
01-28 20:19:10.727 I/DEBUG ( 652): sp 0000007f81ed46f0 pc 0000007f82ce1fdc pstate 0000000060000000
01-28 20:19:10.727 I/DEBUG ( 652): backtrace:
01-28 20:19:10.727 I/DEBUG ( 652): #00 pc 000000000032afdc /system/lib64/libart.so (art::DumpNativeStack(std::__1::basic_ostream<char, std::__1::char_traits<char> >&, int, char const*, art::mirror::ArtMethod*)+300)
[...]
01-28 20:19:10.770 F/libc ( 1734): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x1c in tid 1748 (Signal Catcher)
[COLOR="red"]01-28 20:19:14.196 I/nativedumper( 5679): Process pid 32331(org.kustom.wallpaper.service org.kustom.wallpaper.service) died by signal - Catcher.[/COLOR]
01-28 20:19:14.221 D/nativedumper( 5679): Tombstone path:/data/tombstones/tombstone_06 UUID:eabbd4ab-23aa-4ddc-a979-353753a50ed9 PID:32331
01-28 20:19:14.295 I/DEBUG ( 652): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x1c
01-28 20:19:14.353 I/DEBUG ( 652): backtrace:
01-28 20:19:14.353 I/DEBUG ( 652): #00 pc 000000000032afdc /system/lib64/libart.so (art::DumpNativeStack(std::__1::basic_ostream<char, std::__1::char_traits<char> >&, int, char const*, art::mirror::ArtMethod*)+300)
01-28 20:19:14.353 I/DEBUG ( 652): #01 pc 00000000002fe040 /system/lib64/libart.so (art::Thread::DumpStack(std::__1::basic_ostream<char, std::__1::char_traits<char> >&) const+260)
01-28 20:19:14.353 I/DEBUG ( 652): #02 pc 0000000000309104 /system/lib64/libart.so (art::ThreadList::DumpForSigQuit(std::__1::basic_ostream<char, std::__1::char_traits<char> >&)+172)
01-28 20:19:14.353 I/DEBUG ( 652): #03 pc 00000000002ea258 /system/lib64/libart.so (art::Runtime::DumpForSigQuit(std::__1::basic_ostream<char, std::__1::char_traits<char> >&)+96)
01-28 20:19:14.353 I/DEBUG ( 652): #04 pc 00000000002f2adc /system/lib64/libart.so (art::SignalCatcher::HandleSigQuit()+1104)
01-28 20:19:14.353 I/DEBUG ( 652): #05 pc 00000000002f36f0 /system/lib64/libart.so (art::SignalCatcher::Run(void*)+456)
01-28 20:19:14.353 I/DEBUG ( 652): #06 pc 000000000001ba00 /system/lib64/libc.so (__pthread_start(void*)+52)
01-28 20:19:14.353 I/DEBUG ( 652): #07 pc 0000000000017cf0 /system/lib64/libc.so (__start_thread+16)
01-28 20:19:14.446 I/DEBUG ( 652): Tombstone written to: /data/tombstones/vendor/minitombstone_06

KLWP is a live wallpaper app.

The (imo) relevant line from tombstone_06 (the KLWP-related crash):

pid: 32331, tid: 32344, name: Signal Catcher >>> org.kustom.wallpaper.service <<<

The one from minitombstone_06:

pid: 1734, tid: 1748, name: Signal Catcher >>> system_server <<<

I hope these are indeed Xposed-related. At least the one I reported about earlier is.

Here's the new files: https://drive.google.com/folderview?id=0B3--EMNkM4LadHJnTDJYRE4yOXc&usp=sharing

rovo89, is this in the right place btw? I followed your XDA link, but afterwards saw other different places on your GitHub, including 'Xposed'.

I'm at a loss... would it be KLWP, Greenify, App Settings? Xposed itself? Amount of apps? :crying:

 

[alex009988]

The random reboots came back for me too. Moreover, it reboots even without xposed installed when you lunch xmod for clash of clans. Seems we should pay attention to aosp rom, I'm ready to cook and try it but I need help in building.

 

[jelbo]

Xposed v80 has been released. I think it doesn't fix the problems, because when I flashed it, wiped Cache/Dalvik and all of my 352 apps were Optimized, I got the crash+reboot. After the 2nd boot it crashed+rebooted again moments after the lockscreen appeared. 3rd and subsequent boots went fine though.

CatLogging continuously again to find the culprit of the random reboots, which might have been fixed on v80 by the way, but I've no reason to believe so reading the changelog. Sadly, rovo89 has not reacted to my report on GitHub yet. Looks like it's in the wrong category as well

 

[alex009988]

Hello jelbo. I think the problem caused not only by xposed. For example, now xmod 2.1.1 is broken for clash of clans, and if you start it on a health system you'll get a black screen.
However, if you start it on our device WITHOUT XPOSED INSTALLED, you'll catch a reboot with blinkind red led. What I noticed as well is if I start to pull at lockscreed when it appeared right away, I catch a reboot.
It seems reboots happens when the system is busy and it hanged and something wanna start as well, so kinda kernel panic happens.
To my mind, original stock firmware is not fully compatible with root bells and whistle. So we should try two ways to solve the problem
1) Try to deodex the system as these guys did for z5 http://forum.xda-developers.com/xperia-z5/development/patch-deodex-patch-firmware-200-t3301572
2) Cook a aosp rom. Cause it's more clear, root apps "understand" such systems, e.g. cyanogenmod , better made out of original android better.

 

[alex009988]

So, after the work over mounth. I got the real boot loop, dalvik cash haven't helped. But factory reset via tarp fixed the problem. Not it's useable again but of course not perfect.

 

[jelbo]

Hello jelbo. I think the problem caused not only by xposed. For example, now xmod 2.1.1 is broken for clash of clans, and if you start it on a health system you'll get a black screen.
However, if you start it on our device WITHOUT XPOSED INSTALLED, you'll catch a reboot with blinkind red led. What I noticed as well is if I start to pull at lockscreed when it appeared right away, I catch a reboot.
It seems reboots happens when the system is busy and it hanged and something wanna start as well, so kinda kernel panic happens.
To my mind, original stock firmware is not fully compatible with root bells and whistle. So we should try two ways to solve the problem
1) Try to deodex the system as these guys did for z5 http://forum.xda-developers.com/xperia-z5/development/patch-deodex-patch-firmware-200-t3301572
2) Cook a aosp rom. Cause it's more clear, root apps "understand" such systems, e.g. cyanogenmod , better made out of original android better.

This makes sense. After optimizing the CPU is pretty busy. Also, the random reboots seem to happen whenever a lot of stuff is going on and I stress the tablet.

I agree deodexing is a good idea, but I have no idea how to approach this yet. It wouldn't surprise me if deodexing alone fixes this issue.

So, after the work over mounth. I got the real boot loop, dalvik cash haven't helped. But factory reset via tarp fixed the problem. Not it's useable again but of course not perfect.

In about 50% of my (re)boots, I get a hang or bootloop. I just reset and try again and then it boots fine. Maybe youjumped the gun too quickly, or did you have consitent consecutive bootloops?

 

[mcfisch]

How are chances to get around this issue by replacing the odexed apps known as being corrupted with some from another device as some guys did for other Sony devices? Did anyone try this already?