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

[jelbo]

Hi,
I try to install xposed and the deodexed trick for the sony camera app next weekend if i'm not busy.

Thanks, that would help. I can send you the deodexed file if you want, so you don't need to set up that deodexing tool and Java. On the other hand, maybe that file is the culprit here, haha. Better to test your own file.

 

[killdozer56]

Thanks, that would help. I can send you the deodexed file if you want, so you don't need to set up that deodexing tool and Java. On the other hand, maybe that file is the culprit here, haha. Better to test your own file.

Thanks, but I have already deodexed the file myself so i'm prepared to flash xposed. I backup my files via twrp and Titanium next weekend and i post the results

 

[jelbo]

Time for another theory after reading lots of stuff.

@mionica had a very intersting finding with his Xperia Z3 Dual. Although the problem is primarily a bootloop after installing Xposed, he also mentions random reboots. What has my interest is this:

The rate at which handles are leaked seems to strongly correlate with the number of processes/apps on a system; the experienced lifetime of systems with few applications (such as mine or the OP's) is high, appearing to be stable (though I've seen my first random reboot yesterday ), whereas people who use cartloads of applications could see reboots within hours or less;

This aligns with my experience on the Z4T, which started with random reboots and is now at the level of the device rebooting almost immediately after booting into Android. The only real difference I can think of is that in the meantime I have installed lots of apps. Now that I think of it, the random reboots started to intensify the longer I used the Z4 and the more apps I installed.

Apparently, there is a file limit (open file handles?) in Sony ROMs.

where the file limits are 1024 (soft) / 4096 (hard)

(source)

The issue is further discussed on this GitHub Xposed Issue, from where it was also fixed in the official Xposed Framework back in April 30. In the thread is also mentioned that @AndroPlus had released a kernel (Z3 I think) with

with INR_OPEN_CUR bumped to 4096

(source)

When I do a ulimit -n I also get 1024 (you need busybox I think), so it's not changed to 4096 in AndroPlusKernel v10. I think it shouldn't be any higher than 1024 because the root cause (file handle leak) was fixed in Xposed, but I still do really wonder if upping the limit to 4096 fixes my issue. Can't seem to do it myself, there is no sysctl.conf in /system/etc/.

I also really wonder what happens on Z4 Tablet devices with Xposed running fine, when you install lots of apps. That would make it a general issue on the Z4 Tablet with Xposed (and maybe the AndroPlusKernel), which I believe it is.

 

[killdozer56]

Time for another theory after reading lots of stuff.

@mionica had a very intersting finding with his Xperia Z3 Dual. Although the problem is primarily a bootloop after installing Xposed, he also mentions random reboots. What has my interest is this:



This aligns with my experience on the Z4T, which started with random reboots and is now at the level of the device rebooting almost immediately after booting into Android. The only real difference I can think of is that in the meantime I have installed lots of apps. Now that I think of it, the random reboots started to intensify the longer I used the Z4 and the more apps I installed.

Apparently, there is a file limit (open file handles?) in Sony ROMs.

(source)

The issue is further discussed on this GitHub Xposed Issue, from where it was also fixed in the official Xposed Framework back in April 30. In the thread is also mentioned that @AndroPlus had released a kernel (Z3 I think) with

(source)

When I do a ulimit -n I also get 1024 (you need busybox I think), so it's not changed to 4096 in AndroPlusKernel v10. I think it shouldn't be any higher than 1024 because the root cause (file handle leak) was fixed in Xposed, but I still do really wonder if upping the limit to 4096 fixes my issue. Can't seem to do it myself, there is no sysctl.conf in /system/etc/.

I also really wonder what happens on Z4 Tablet devices with Xposed running fine, when you install lots of apps. That would make it a general issue on the Z4 Tablet with Xposed (and maybe the AndroPlusKernel), which I believe it is.

have you try ulimit -n 4096

 

[mionica]

mionica had a very intersting finding with his Xperia Z3 Dual. Although the problem is primarily a bootloop after installing Xposed, he also mentions random reboots. What has my interest is this:

To put things into context: back in the day, Xposed leaked file handles like there was no tomorrow (it opened the same file, over and over again, and didn't close it). We worked it around back then by setting the number of files that could be opened by the system server to 4096, since Android would kick the bucket the moment the system server became unable to open one more file; this didn't solve the problem, but delayed it a fair bit.

To check if this applies to you, try something like this from an ADB shell:

for p in /proc/*; do if test -d $p/fd; then echo $p: $(ls -l $p/fd/*|wc -l) file handles; fi; done

; if you see very large numbers for at least a process (at least 500), chances are, a file handle leak is the culprit; if not, it's something else.

 

[alex009988]

Unfortunately, reading these so bad news, stop me from rooting at the moment. What I really need from xpose is only adaway, but as I see xpose doesn't work at all even without any modules / framework. Moreover, as it was previously mentioned, the camera doesn't work either what make it totally "cool". AndroPlus could have ruled out the problem, but it seems he is not active developer to our regret. The last version of the kernel was released two month ago. Anybody tell me what the damn tablet do we have(sorry for my emotions, of course it's rhetorical question):crying:

 

[jelbo]

have you try ulimit -n 4096

This works, thanks.

To put things into context: back in the day, Xposed leaked file handles like there was no tomorrow (it opened the same file, over and over again, and didn't close it). We worked it around back then by setting the number of files that could be opened by the system server to 4096, since Android would kick the bucket the moment the system server became unable to open one more file; this didn't solve the problem, but delayed it a fair bit.

To check if this applies to you, try something like this from an ADB shell:

for p in /proc/*; do if test -d $p/fd; then echo $p: $(ls -l $p/fd/*|wc -l) file handles; fi; done

; if you see very large numbers for at least a process (at least 500), chances are, a file handle leak is the culprit; if not, it's something else.

Thanks for the tip. The biggest number I'm seeing without Xposed running is 347 (/proc/1355: 347 file handles), but of course, I should test with Xposed installed. Somehow my ADB driver broke, so that's gotta wait :/ I got the number now using Terminal Emulator.

 

[killdozer56]

Unfortunately, reading these so bad news, stop me from rooting at the moment. What I really need from xpose is only adaway, but as I see xpose doesn't work at all even without any modules / framework.

Hi,
Adaway work without Xposed.

 

[jelbo]

but as I see xpose doesn't work at all even without any modules / framework.

Well, some people have Xposed running just fine. I suspect they have a small amount of apps installed. It's just some people have problems, for which there must be a same cause I think.

I did a little experiment this afternoon by doing a factory wipe in TWRP and flashing Xposed again. Guess what, no crash after booting into Android. Of course, I couldn't resist installing a handful of apps I so dearly need. Like AdAway A handful quickly became about 33 (/edit: more, maybe 50-60) and then I got my first random red LED crash and reboot. This was with NO Xposed modules installed and active. Just now, I uninstalled some apps to see how well it goes now. /edit: I'm now at 43 user apps, 174 normal system apps and 128 frozen system apps.

Also I was thinking about @Mr. Schnabel's similar experience.

Hey!

Had same issue, started about 3 weeks after unlocking, rooting and xposed out of nowhere ... reflashed Stock, rooted again and problem solved!
No more reboots even i set up my system ecxactly like before ...

Don´t know what was really causing the issue but reflashing helped me

Cheers

Yes, like said running same setup as before the re-boots occurred. Root/Xposed/Same modules/ same apps, etc.

System was running w/o problems for about 3 weeks and out of nowhere came those re-boots. Didn´t update any app/module/etc. in this time only thing was the BK50 but i had it for about 10 days before it started acting weird so don´t know what was really causing the problems ....
Sometimes after seconds, sometimes after minutes, sometimes after hours ... out of nowhere black screen/Red light and reboot ...

Could this be that in those 3 weeks you did install (a few) more apps until you hit a limit? And that after you started over you never reached that same amount of installed apps?

@D_STROY, you still have the same random reboot issue as me, right? Can you check (with Titanium Backup or anything else that can do it) how many user apps you have installed?

My guess is that it is Xposed framework that is causing issues, I don't know if you have this too....but the system logs on my device have wall after wall of error code displayed in red and they nearly all mention Xposed, honestly I have never seen such a vast list that repeats over and again of errors, it made me think about uninstalling Xposed but I just can't live without it!!!

If you can share some of your logs, this can help.

Moreover, as it was previously mentioned, the camera doesn't work either what make it totally "cool".

Camera works fine after rooting? The Album app crashes, but you can fix that by deodexing it or by freezing/uninstalling it.

FWIW, in my logcat from the 2nd boot that crashed almost immediately, from a few days ago, I had these crash logs:

[COLOR="Red"]01-12 13:57:08.635 F/libc    ( 3667): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x1c in tid 3688 (Signal Catcher)[/COLOR]
[COLOR="DarkSlateBlue"]01-12 13:57:08.753 I/DEBUG   (  644): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x1c[/COLOR]
[COLOR="red"]01-12 13:57:08.917 F/libc    ( 1340): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x8 in tid 1349 (Signal Catcher)[/COLOR]
[COLOR="DarkSlateBlue"]01-12 13:57:12.170 I/DEBUG   (  644): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x8[/COLOR]

A small summary.

• The cause of the crash/reboot issues is not the ROM (28.0.A.8.260) or the kernel (AndroPlusKernel v10), because people with the issue (D_STROY and Mr. Schnabel) and people without the issue (DHGE and killdozer56) are running the same ROM/kernel. It's unlikely the people with issues are running the exact same German customized ROM as me.
• The issue only happens with Xposed installed. I have tried both v78 and v79 (sdk21-arm64).
• It's not an active Xposed module, because I can reproduce the issue without any Xposed modules activated.
• When I have a lot of apps installed, tablet runs fine.
• When I have a lot of apps installed and then flash Xposed, tablet crashes after completing 'optimizing' apps. Each time. After the reboot, it will crash moments after the lock screen appears. Each time.
• 'Lots of apps' could be one specific app that is't playing nice with Xposed. If so, it's likely not a preïnstalled system-app, because then all Xposed users would have the issue. Unless fellow victims D_STROY and Mr. Schnabel run the same German customized R6A flavour of the ROM.
• When I have a lot of apps installed and uninstall Xposed, tablet runs fine.
• When I completely wipe the tablet, and then flash Xposed, it runs fine. Haven't tested this very long, because I install my apps one by one on a clean device.
• As soon as I have quite a few apps installed, the tablet starts crashing/rebooting. Again, I'm not complete sure on this yet.
• What set me on the wrong path initially is that soft rebooting is broken on the Z4 Tablet. It results in a crash which fully reboots the tablet. Soft reboots are often caused by SystemUI crashes. On the Z4T a SystemUI crash most likely will crash the whole system.

So as of now, I think the cause is either the amount of installed apps or a specific (user) app that doesn't play well with Xposed.

 

[killdozer56]

Well, some people have Xposed running just fine. I suspect they have a small amount of apps installed. It's just some people have problems, for which there must be a same cause I think.

I did a little experiment this afternoon by doing a factory wipe in TWRP and flashing Xposed again. Guess what, no crash after booting into Android. Of course, I couldn't resist installing a handful of apps I so dearly need. Like AdAway A handful quickly became about 33 and then I got my first random red LED crash and reboot. This was with NO Xposed modules installed and active. Just now, I uninstalled some apps to see how well it goes now.

Also I was thinking about @Mr. Schnabel's similar experience.




Could this be that in those 3 weeks you did install (a few) more apps until you hit a limit? And that after you started over you never reached that same amount of installed apps?

@D_STROY, you still have the same random reboot issue as me, right? Can you check (with Titanium Backup or anything else that can do it) how many user apps you have installed?


If you can share some of your logs, this can help.


Camera works fine after rooting? The Album app crashes, but you can fix that by deodexing it or by freezing/uninstalling it.

FWIW, in my logcat from the 2nd boot that crashed almost immediately, from a few days ago, I had these crash logs:

[COLOR="Red"]01-12 13:57:08.635 F/libc    ( 3667): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x1c in tid 3688 (Signal Catcher)[/COLOR]
[COLOR="DarkSlateBlue"]01-12 13:57:08.753 I/DEBUG   (  644): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x1c[/COLOR]
[COLOR="red"]01-12 13:57:08.917 F/libc    ( 1340): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x8 in tid 1349 (Signal Catcher)[/COLOR]
[COLOR="DarkSlateBlue"]01-12 13:57:12.170 I/DEBUG   (  644): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x8[/COLOR]

A small summary.

• The cause of the crash/reboot issues is not the ROM (28.0.A.8.260) or the kernel (AndroPlusKernel v10), because people with the issue (D_STROY and Mr. Schnabel) and people without the issue (DHGE and killdozer56) are running the same ROM/kernel. It's unlikely the people with issues are running the exact same German customized ROM as me.
• The issue only happens with Xposed installed. I have tried both v78 and v79 (sdk21-arm64).
• It's not an active Xposed module, because I can reproduce the issue without any Xposed modules activated.
• When I have a lot of apps installed, tablet runs fine.
• When I have a lot of apps installed and then flash Xposed, tablet crashes after completing 'optimizing' apps. Each time. After the reboot, it will crash moments after the lock screen appears. Each time.
• 'Lots of apps' could be one specific app that is't playing nice with Xposed. If so, it's likely not a preïnstalled system-app, because then all Xposed users would have the issue. Unless fellow victims D_STROY and Mr. Schnabel run the same German customized R6A flavour of the ROM.
• When I have a lot of apps installed and uninstall Xposed, tablet runs fine.
• When I completely wipe the tablet, and then flash Xposed, it runs fine. Haven't tested this very long, because I install my apps one by one on a clean device.
• As soon as I have quite a few apps installed, the tablet starts crashing/rebooting. Again, I'm not complete sure on this yet.
• What set me on the wrong path initially is that soft rebooting is broken on the Z4 Tablet. It results in a crash which fully reboots the tablet. Soft reboots are often caused by SystemUI crashes. On the Z4T a SystemUI crash most likely will crash the whole system.

So as of now, I think the cause is either the amount of installed apps or a specific (user) app that doesn't play well with Xposed.

Thanks jelbo,
can you give a procedure step by step to install Xposed(what to wipe, dalvik, cache, factory reset) of after your experience to identify the problem and what posting log
I have 211 user apps and 304 system apps

 

[alex009988]

Did you try xposed 3.0 alpha 4 http://4pda.ru/forum/index.php?showtopic=425052&st=11440#entry39835298 (in order to download from 4pda you have to sign up there)?

 

[jelbo]

Thanks jelbo,
can you give a procedure step by step to install Xposed(what to wipe, dalvik, cache, factory reset) of after your experience to identify the problem and what posting log
I have 211 user apps and 304 system apps

That's a lot of apps! Good. It's simple really. I just flashed xposed-v79-sdk21-arm64.zip from the official thread. Grab xposed-uninstaller-20150831-arm64.zip as well in case you need it. After flashing Xposed, slide the Wipe Cache/Dalvik button and reboot. It'll take a little while longer, then it will start 'optimizing app x of x'. In my case, when that's complete, it will do the crash at the first interaction or very short thereafter.

If it crashes for you too, you can capture a logcat with adb. I used the 15 seconds ADB Installer v1.4.3. It's best to set that up first. In Android, enable USB debugging from the Developer menu (visibible after hitting the build number in About this Tablet 5 times or so). Install the ADB tool on Windows. It will need an ADB driver. I forgot where I got mine from, but it's listed as a Sony sa0112 driver and I'm pretty sure you can force install the one for the Z3+ uploaded here on XDA. ADB drivers are pretty generic. Instructions are here. Test the connection by opening a cmd.exe and running adb devices. You'll need to approve once on your tablet. If all went well, it will list the device with it's serial

When the tablet is booting, or at least when it's displaying an Android GUI (the optimizing apps stage for example), you can capture a logcat using adb logcat -v time > logcat.txt. File will be saved in where you have the command prompt open. ADB will be busy capturing as soon as the 'waiting for device' disappears. You can stop writing to logcat.txt with Control + C. An Android crash will also stop it. And provide some useful crash details in the logcat.txt

If you don't have any problems I think there might be a specific app on my tablet that's the cause. We can then compare some lists maybe.

Thanks for working on this as well!

 

[jelbo]

Did you try xposed 3.0 alpha 4 http://4pda.ru/forum/index.php?showtopic=425052&st=11440#entry39835298 (in order to download from 4pda you have to sign up there)?

Yes, but that's just the Android APK for downloading modules and stuff. Nowadays, the actual Xposed magic is installed via the .zip file through recovery.

 

[alex009988]

Yes, but that's just the Android APK for downloading modules and stuff. Nowadays, the actual Xposed magic is installed via the .zip file through recovery.

There is also the .zip file. Please, look at the message in a more detailed way. .....20150430.zip

 

[jelbo]

There is also the .zip file. Please, look at the message in a more detailed way. .....20150430.zip

Oh, excuse me. There is indeed. But it's the official Xposed release from April 30 that I mentioned. Those fixes should still be in all later releases up until v79. Also, that .zip is for ARM, not ARM64, I don't think it'll work on the Z4T, which needs 'sdk21, arm64' flavoured Xposed. Thanks for the effort though :good:

 

[killdozer56]

That's a lot of apps! Good. It's simple really. I just flashed xposed-v79-sdk21-arm64.zip from the official thread. Grab xposed-uninstaller-20150831-arm64.zip as well in case you need it. After flashing Xposed, slide the Wipe Cache/Dalvik button and reboot. It'll take a little while longer, then it will start 'optimizing app x of x'. In my case, when that's complete, it will do the crash at the first interaction or very short thereafter.

Thanks
When i installed Xposed 3 weeks before. I have not had any crash From android for several hours. I Could configure my xposed modules (greenify, 3c toolbox pro, Ownorientation) reboot several time no crash (but the optimisation window after each reboot). But when i try to open the sony camera app that's when i started with the problems.
I use adb v 1.0.32 from http://forum.xda-developers.com/htc-one/general/tool-updated-adb-version-1-0-32-fastboot-t2932160 I think this Is the last version of ADB and fastboot

 

[jelbo]

Thanks
When i installed Xposed 3 weeks before. I have not had any crash From android for several hours. I Could configure my xposed modules (greenify, 3c toolbox pro, Ownorientation) reboot several time no crash (but the optimisation window after each reboot). But when i try to open the sony camera app that's when i started with the problems.
I use adb v 1.0.32 from http://forum.xda-developers.com/htc-one/general/tool-updated-adb-version-1-0-32-fastboot-t2932160 I think this Is the last version of ADB and fastboot

All right. The camera/album app FC problem is as far as I know not related to the random rebooting.

What I am really curious about is what happens when you install Xposed v79 on your current setup with lots of apps. If it also crashes after the optimizing apps stage, we're closer to finding the root cause.

The ADB/fastboot version doesn't matter, as long as they can communicatie with the device. You'll only need ADB to collect a log, in the scenario in which the tablet crashes.

 

[killdozer56]

All right. The camera/album app FC problem is as far as I know not related to the random rebooting.

What I am really curious about is what happens when you install Xposed v79 on your current setup with lots of apps. If it also crashes after the optimizing apps stage, we're closer to finding the root cause.

The ADB/fastboot version doesn't matter, as long as they can communicatie with the device. You'll only need ADB to collect a log, in the scenario in which the tablet crashes.

Ok
I retry this weekend

 

[D_STROY]

Well, some people have Xposed running just fine. I suspect they have a small amount of apps installed. It's just some people have problems, for which there must be a same cause I think.

I did a little experiment this afternoon by doing a factory wipe in TWRP and flashing Xposed again. Guess what, no crash after booting into Android. Of course, I couldn't resist installing a handful of apps I so dearly need. Like AdAway A handful quickly became about 33 (/edit: more, maybe 50-60) and then I got my first random red LED crash and reboot. This was with NO Xposed modules installed and active. Just now, I uninstalled some apps to see how well it goes now. /edit: I'm now at 43 user apps, 174 normal system apps and 128 frozen system apps.

Also I was thinking about @Mr. Schnabel's similar experience.




Could this be that in those 3 weeks you did install (a few) more apps until you hit a limit? And that after you started over you never reached that same amount of installed apps?

@D_STROY, you still have the same random reboot issue as me, right? Can you check (with Titanium Backup or anything else that can do it) how many user apps you have installed?


If you can share some of your logs, this can help.


Camera works fine after rooting? The Album app crashes, but you can fix that by deodexing it or by freezing/uninstalling it.

FWIW, in my logcat from the 2nd boot that crashed almost immediately, from a few days ago, I had these crash logs:

[COLOR="Red"]01-12 13:57:08.635 F/libc    ( 3667): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x1c in tid 3688 (Signal Catcher)[/COLOR]
[COLOR="DarkSlateBlue"]01-12 13:57:08.753 I/DEBUG   (  644): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x1c[/COLOR]
[COLOR="red"]01-12 13:57:08.917 F/libc    ( 1340): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x8 in tid 1349 (Signal Catcher)[/COLOR]
[COLOR="DarkSlateBlue"]01-12 13:57:12.170 I/DEBUG   (  644): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x8[/COLOR]

A small summary.

• The cause of the crash/reboot issues is not the ROM (28.0.A.8.260) or the kernel (AndroPlusKernel v10), because people with the issue (D_STROY and Mr. Schnabel) and people without the issue (DHGE and killdozer56) are running the same ROM/kernel. It's unlikely the people with issues are running the exact same German customized ROM as me.
• The issue only happens with Xposed installed. I have tried both v78 and v79 (sdk21-arm64).
• It's not an active Xposed module, because I can reproduce the issue without any Xposed modules activated.
• When I have a lot of apps installed, tablet runs fine.
• When I have a lot of apps installed and then flash Xposed, tablet crashes after completing 'optimizing' apps. Each time. After the reboot, it will crash moments after the lock screen appears. Each time.
• 'Lots of apps' could be one specific app that is't playing nice with Xposed. If so, it's likely not a preïnstalled system-app, because then all Xposed users would have the issue. Unless fellow victims D_STROY and Mr. Schnabel run the same German customized R6A flavour of the ROM.
• When I have a lot of apps installed and uninstall Xposed, tablet runs fine.
• When I completely wipe the tablet, and then flash Xposed, it runs fine. Haven't tested this very long, because I install my apps one by one on a clean device.
• As soon as I have quite a few apps installed, the tablet starts crashing/rebooting. Again, I'm not complete sure on this yet.
• What set me on the wrong path initially is that soft rebooting is broken on the Z4 Tablet. It results in a crash which fully reboots the tablet. Soft reboots are often caused by SystemUI crashes. On the Z4T a SystemUI crash most likely will crash the whole system.

So as of now, I think the cause is either the amount of installed apps or a specific (user) app that doesn't play well with Xposed.

Hi Jelbo,

I currently have 155 user apps installed, of which 43 are Xposed modules but there are a couple of those modules that aren't active at the moment.

Funnily enough, my tablet had been running quite stable and I was going to write a post on here to let you know....and guess what? YES, i had about 3 random crashes and reboots! So the mystery still remains unfortunately....

I read on your post about the ROM you have running, I have the same version (28.0.A.8.260) but mine is Customized UK ROM.

Just wanted to ask, when you get a red light and reboot event, does your tablet boot into Android ok? Because I have to do a hard reset (power + vol up buttons) and then reboot most of the times otherwise it just stays at the Xperia wave screen for ages, sometimes it boots without a reset.
Should hard resets be avoided? I thought I read somewhere that they aren't something that should be done often?

I'll have a look into the logs you asked about and try and post them here too.

 

[alex009988]

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