Code: su /data/flimit/flimit $(pgrep zygote)

Code: su sh /system/etc/init.d/01_flimit

Current development version and downloadable files you can always find in @mionica post http://forum.xda-developers.com/show...&postcount=123

@mionica managed to analyze boot process on both ROMs with and without Xposed and came to conclusion that leaks are caused by Xposed process leaking open file handles, see here http://forum.xda-developers.com/show...&postcount=417



There is a current version of the workaround fix (see above), that seems to be the last possible, before Xposed will be released with patch addressing that issue. Good news is that thanks to @mionica precise analysis, @rovo89 - developer of Xposed is already aware of the problem nad it´s cause.

Quote: by @mionica

Anybody who is still having any kind of issues , for whatever reason, please do the following: get into TWRP;

install, in this order, without rebooting : xposed-uninstall-v1.1.zip If you don't have an sd card , you'll need to reboot once after the uninstall .zip, boot the system normally, then get back in the recovery and install the other 3. This only applies to people who don't use an SD card xzdr-busybox-enable-v1.0.zip xposed-sdk21-arm- date .zip xposed-leakplug-v1.2.zip

: copy the logs to the PC , over USB: uninstall_xposed.log install_busybox.log install_leakplug.log each of the 3 zip's will tell you where it saved the log (it's usually the external sdcard)

, over USB: each of the 3 zip's will tell you where it saved the log (it's usually the external sdcard) reboot to system

Thanks in advance for not asking any questions about whether you have to do any of these steps; yes, you have to.

If you follow other instructions than provided by @mionica please get then support from someone else than him.

This thread is about workaround found for bootloops of Xposed in XPERIA family Lollipop. Because of development progress, I have decided to remove historical development, you can see it here:For flashables see EDIT 5 and bellow...I can present somefor users with locked bootloaders who are getting bootloops with Xposed and Lollipop.As you may already know, we have find out, that some undetected error is causing system to bootloop, if too many applications are installed.Exact numbers are varying between different ROMs and devices, generally the maximum number of apps is about 320-330.Debloating (uninstalling unnecessary apps) helps, but remains limiting and for many frustrating. After a research, we have found out,that there is probably a bug, that is causing many files being left open when booting Lollipop with Xposed.Users on unlocked bootloader may modify certain kernel parameters to raise number of open files. This can not be done on Locked Bootloader.After some research and hours of experiments, I found a way, how to change the filelimit for Zygote and subsequent processes. Therefore every child of zygote (hence every app etc.) will inherit raised open files limit from 1024 to 4096.This change, not only XPERIAs, however I only tested it on Z3 D6603 fw 690. But the modificationis done on Linux system level, therefore it should teoretically work just everywhere... It should work also on Locked bootloaders as well.The principle is easy, however implementation was a tricky, because of lack of native linux utils support on Android and fact that we can noteasily modify booting behaviour. But gladly enough we have XZDualRecovery (gret thanks @ [NUT] )....XZDualRecovery enables to call init scripts on startup. I have created a startup script that waits for zygote process to come up, and callsexternal program that changes open file limits for that process. This external program is compiled by me from source provided by http://lzone.de/cheat-sheet/ulimit : Functional XZDualRecovery or other form of init.d support.downloaded ZIP file, it contains:-binary executable for changing open file limits- shell script called by init- source code of binary executablein XZDualRecovery by editing XZDR.prop and change dr.initd.active=trueDont forget to have enabled byeselinux (dr.keep.byeselinux=true)copy(or push adb)remount /system rw (mount -o remount,rw /system)create directorycopyand make executable (create directorywith andcopyandtest run installation:output should be:If not, check permissions etc.Check script by running:it should now give output (if you succesfully ran /data/flimit/flimit....):rebootThats all. Now you can install and update lot more applications. Now I have about 455 packages reported by pm list packages and no bootloop.But as soon as I disable the init.d support, it bootloops. So re-enable by edititng XZDR.prop and it again boots.Please let me know, if you had to modify the script or instructions to work on your device, so I can perhaps make better or more universal version. Thank you guys.While this workaround makes it possible to run Xposed on untouched vanilla Stock ROM, you may still consider debloating it, as debloating will make run your device more smoothly and saves battery. Guys who made debloating scripts made significant efforts in identifying which apps can be safely removed without harming any significant functionality.The ZIP is NOT flashable, follow instructions ^^^^ --- buddy @ McBane87 is developing flashable version.Buddy @ nurps found a bug causing Opera browser to quit upon starting. @ mionica proposed lowering softlimits for open files to 2048 from 4096 in first version of script. Version 1.1 is released.Buddy @ McBane87 created customizedversion of this workaround, so you can flash it from recovery if you struggle with bootloops, dont like to wait fro 300apps to optimize after Dalvik wipe and mess with adb/terminal..Buddy @ mionica published another flashable zip. It is complete installer for the workaround, so far most sofisticated workaround from system point of view. The uninstaller completely removes Xposed if you are too tired of it and forgot to make backupFiles are bellow, for instructions etc. check it out on http://forum.xda-developers.com/show...&postcount=123 and for latest development at http://forum.xda-developers.com/show...&postcount=285 v1: Initial releasev1.1: Changed limits to 2048 from 4096 as high limits caused Opera Webbrowsers to crashv2.0 Reference script - for production please flash @ mionica version of flashable, my script is published for educational purposes. added mionicas mod to detect only changed limits and subsequently remove only those that are child of zygote***************************************I would like to thank mainly to @ [NUT] and to guys who made significant effort with debloating, made other discoveries or were an inspirationfor me, including but not limited to @ serajr AndroPlus (for his work on file limits in kernel) @ redincali and of course to @ rovo89 for his Xposed framework. My apologies if I forgot someone, PM me, its 2 o'clock in morningor in this post http://forum.xda-developers.com/show...&postcount=354 While I have developed initial version (see history), other guys (mainly @ mionica and @ McBane87 ) greatly enhanced and redeveloped whole thing.[B] Recommended installation steps:The basic idea behind is that Xposed bootloops because of it exhausted resources available due to probably internal bug. The workaround basically provides higher limits for open files during boot and restores previous limits after device has booted. The latest flashable installer is very advanced and automates the installation, including necessary checks for proper XZDR configuration, busybox etc.When you experience bootloops after installing Xposed, or you had Xposed working and it started to bootloop after you have installed new app or upgraded a system app, simply reboot to recovery and flash the zip. No need to wipe anything.When installing new, I recommend flashing this zip first, then install Xposed usual way (flash, wipe, reboot, install Xposed apk, install modules).Be aware that while the workaround works for about 80% of cases, there are people who have lots of applications or heavily modified system, experiencing random reboots. Cause is under investiogation, but most probably is in Xposed itself.