Xposed - Legacy thread. Don't panic, Xposed is still here.

Status
Not open for further replies.
Search This thread

WinSern1

Member
May 31, 2013
30
6
Help!!!!!

After installing Xposed installer(2.1.4) on my s4 i9500, i hit install and then reboot, my phone keeps rebooting and rebooting! :crying:
I've tried to flash xposed disabler through CWM, but the issue still there. I am new to Xposed, please tell me where did i do wrong and how to solve it. Thanks:fingers-crossed:
 

eejee

Senior Member
Mar 16, 2009
929
351
Utrecht
Try to do some logcat.

I've had the same issue on my 9505. A logcat is not possible because the device hangs during reboot when loading the os. Since I hadn't made a nandroid backup yet (brand new device, rooted about 15 minutes before this happened), I had to do a factory reset.

Verstuurd van mijn GT-P5100 met Tapatalk
 

WinSern1

Member
May 31, 2013
30
6
I've had the same issue on my 9505. A logcat is not possible because the device hangs during reboot when loading the os. Since I hadn't made a nandroid backup yet (brand new device, rooted about 15 minutes before this happened), I had to do a factory reset.

Verstuurd van mijn GT-P5100 met Tapatalk
You are lucky! i have all important apps and data inside, cannot reset so easily. I will try to flash stock firmware again.
I've read that flashing stock firmware won't make me lose any data in my phone, am I correct?:confused:
 

eejee

Senior Member
Mar 16, 2009
929
351
Utrecht
I did lose all data on the internal sd card. This never happened on my previous devices.

Verstuurd van mijn GT-P5100 met Tapatalk
 

kamso

Senior Member
Aug 12, 2012
842
167
You are lucky! i have all important apps and data inside, cannot reset so easily. I will try to flash stock firmware again.
I've read that flashing stock firmware won't make me lose any data in my phone, am I correct?:confused:
Yes, flashing without data wipe.

Envoyé depuis mon GT-N7100 avec Tapatalk
 

capslock66

Senior Member
Oct 21, 2010
792
1,221
Brussel
It is not boot loop, It can boot to lockscreen but then reboot and go to lockscreen again. It keeps repeating reboot:crying:
Downloading Android SDK...

To stop boot loop :
As soon as you have the boot animation, enter this command on a windows command prompt :
adb reboot recovery
then on recovery, just flash the Xposed-Disabler-CWM.zip
 

WinSern1

Member
May 31, 2013
30
6
To stop boot loop :
As soon as you have the boot animation, enter this command on a windows command prompt :
adb reboot recovery
then on recovery, just flash the Xposed-Disabler-CWM.zip
It's not boot loop...it reboots when reaching the lockscreen and it keeps repeating.
i've tried to flash Xposed-Disabler-CWM.zip , it said success but the issue still there.
 

rovo89

Senior Recognized Developer
Jan 4, 2012
2,585
81,434
It is not boot loop, It can boot to lockscreen but then reboot and go to lockscreen again. It keeps repeating reboot:crying:
Downloading Android SDK...

Can you use "adb" (contained in the SDK)? Then you can execute "adb logcat -d > logcat.txt". If you have that, you can also execute "adb shell" to get a command line on your phone. Type "id" to make sure you are root (and use "su" on the shell or "adb root" from your PC if you are not root) and then execute "touch /data/xposed/disabled".

Rovo89 can you tell me what is exactly problem in aokp roms that xposed not working correctly, I can't stand situation when after reboot i need to wait 2-3 hours for normal state my phone.

Here is the essential part of my mail to the author of this commit (shows a unicorn for me right now, but should work again soon...):
I had several users reporting that with the latest AOKP nightlies and my Xposed framework, their SystemUI takes some minutes to show up. Even though I'm not using AOKP myself, I spent some hours investigation this issue. What I found was:
- The reason for the delay are ANRs, which cause a restart of the SystemUI
- I believe the root cause was introduced in this commit: https://github.com/AOKP/frameworks_base/commit/8432dd523bf51c10e2aa294a9b5494a64ff1f96e
- AppWindow, which is initialized in the start() function of the SystemUI services, loads information about all installed packages
- There are two expensive things in this:
- getting the launch intent results in two queryIntentActivities() calls for each installed package
- retrieving the labels for all launchable packages requires their resources to be loaded
- I injected the package loading functions into the ROM I'm using and they took 10-15 seconds on my S2 at boot time (high load -> more runtime)
- With many installed packages, a slower device or other initializations going on in parallel, the 20 seconds limit for ANRs is easily reached
- Xposed seems be another factor in this, but I have also seen an ANR trace where Xposed was not installed. Even if it slowed down the whole thing by 3 seconds, it couldn't be called the main factor.
- I asked one of the affected users to try an Xposed module that nukes the sortApps() function, which is just one half of the expensive instructions. He reported back that this mostly solves it.

So, here are my suggestions:
- avoid loading the packages during service startup (or at boot time at all - later, the same code just takes about 4 seconds)
- load the information asynchronously if possible to avoid blocking

If you need more information, please let me know.

So in short: I believe that the root cause is that information about all installed packages is loaded at boot time, which is quite slow. It seems that Xposed has also a share in that (i.e. it seems to slow it down a bit further, pushing it over the 20 seconds limit), but I have also seen a trace where the SystemUI crashed in these functions even though Xposed was not installed.

Obviously I'll try to address the performance in the future. @exidler has done some great and detailed analysis and suggested fixes (but as they touch the very core of Xposed, this has to be handled very carefully). Just to get the dimensions right: Execution times are far less than a millisecond in his test. On the other hand, when there are many hundreds and thousands of calls in a short time, this can add up. And during boot time the CPU load is high anyway, so the actual execution time is higher than the CPU time.

So far, I haven't received any reply. If you can address this somehow else, please do so, I honestly don't have the energy to follow up on this. When you talk to your ROM developer, can you ask him to add some logging (with System.currentTimeMillis and maybe a stack trace) at the beginning and end of AppWindow.setupWindow()? That would make it easier to see how much Xposed contributes in this particular case.

Meanwhile, you can try the workaround module from this post. It nukes one of the long-running functions.
 

WinSern1

Member
May 31, 2013
30
6
Can you use "adb" (contained in the SDK)? Then you can execute "adb logcat -d > logcat.txt". If you have that, you can also execute "adb shell" to get a command line on your phone. Type "id" to make sure you are root (and use "su" on the shell or "adb root" from your PC if you are not root) and then execute "touch /data/xposed/disabled".

How to connect my phone with pc in recovery mode? First, i boot my phone into recovery mode, then plugged in usb cable. My pc is not able to detect my phone. Any idea? Of cause usb debugging is checked.
Note : My phone still rebooting.
 

WinSern1

Member
May 31, 2013
30
6
Can you use "adb" (contained in the SDK)? Then you can execute "adb logcat -d > logcat.txt". If you have that, you can also execute "adb shell" to get a command line on your phone. Type "id" to make sure you are root (and use "su" on the shell or "adb root" from your PC if you are not root) and then execute "touch /data/xposed/disabled".



Here is the essential part of my mail to the author of this commit (shows a unicorn for me right now, but should work again soon...):


So in short: I believe that the root cause is that information about all installed packages is loaded at boot time, which is quite slow. It seems that Xposed has also a share in that (i.e. it seems to slow it down a bit further, pushing it over the 20 seconds limit), but I have also seen a trace where the SystemUI crashed in these functions even though Xposed was not installed.

Obviously I'll try to address the performance in the future. @exidler has done some great and detailed analysis and suggested fixes (but as they touch the very core of Xposed, this has to be handled very carefully). Just to get the dimensions right: Execution times are far less than a millisecond in his test. On the other hand, when there are many hundreds and thousands of calls in a short time, this can add up. And during boot time the CPU load is high anyway, so the actual execution time is higher than the CPU time.

So far, I haven't received any reply. If you can address this somehow else, please do so, I honestly don't have the energy to follow up on this. When you talk to your ROM developer, can you ask him to add some logging (with System.currentTimeMillis and maybe a stack trace) at the beginning and end of AppWindow.setupWindow()? That would make it easier to see how much Xposed contributes in this particular case.

Meanwhile, you can try the workaround module from this post. It nukes one of the long-running functions.
Now my phone is able to connect with my pc in recovery mode. I've done once as you mentioned above but still rebooting.
My phone is rooted. After (use "su" on the shell), juz type "touch /data/xposed/disabled" or i should insert anything in front of it? etc. adb shell
 
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 638
    Xposed 2.4 beta1/beta2

    This is Xposed version 2.4 beta1. The main new features and fixes in this version are:
    • Support for Android 4.4 (KitKat)
    • Significant performance improvements of the framework
    • Viewer for the debug.log in the installer
    • Check in the installer whether Xposed is actually active and working

    First of all, I would like to thank the 45 people who donated to get me a Nexus 5, from a little "thanks" to huge amounts of money. I was really impressed and hope you like this update.

    In detail:
    Xposed should now fully support KitKat. As mentioned, that wouldn't have been possible at this time without your support.
    Modules should continue to work if they don't rely on AOSP internals that have changed in KitKat. One example: It seems that the battery icon is no longer an (animated) image, but a Java implementation. Obviously, any modules that try to replace the battery image will no longer work. The Xposed framework can't do anything here, the module needs to be rewritten. Therefore, if some of your modules don't work, please get in contact with the module author first. You will probably see an error in the new debug.log viewer in this case.
    Xposed isn't compatible with ART, I can't say yet whether it will be in the future (will require a major rewrite if possible at all). As you would get into a bootloop if you try to combine Xposed+ART, Xposed automatically resets the choice to "Dalvik". If you want to test ART, you must uninstall the framework.

    The performance improvements apply to the very core of Xposed, the method hooks, in all Android versions. In a test app developed by @exidler, the overhead per call used to be ~71 μs (= 0.071 ms) per call to a hooked method (with one empty callback handler) on my Galaxy S2. Now it's ~13 μs (= 0.013 ms). That's a relative improvement of factor ~5.5x. Thanks to @exidler for the research and several suggestions! I have sent a pre-beta to @kamso, who had reported lags with older versions. Now everything works fine for him. Anyway, I wouldn't say that Xposed had bad performance before. Keep in mind that we are talking about significantly less than a millisecond here.

    The debug.log viewer should give a quick impression whether Xposed and modules could be loaded fine. It also includes options to save the log to SD card (so it's easier to transfer it to a PC etc.) and send it via mail.

    The Xposed Installer now checks whether the latest version of the framework is active. If not (e.g. because it's not installed yet, you forgot to reboot or something in Xposed doesn't work), you will see a warning in the welcome screen and at the top of the module list.

    Finally, there were some other minor improvements and fixes and new/updated translations.


    Developers:
    As a reminder, please keep the debug.log clean. It's only helpful if it's not as spammed as logcat. You should only use XposedBridge.log() for error messages and other unexpected situations. If everything runs fine, it shouldn't write anything to the log. If you really need to keep some logging in published builds, please use either logcat or make it an opt-in options (i.e. disabled by default and the user enables it if he runs into problems).

    Apart from that, there was a little API change: https://github.com/rovo89/XposedBridge/commit/3c18f6f6bd4e0ec57898b3b3a79b5584d0396054
    I assume that very few modules use the "extra" field to transfer information between beforeHookedMethod() and afterHookedMethod(). If you do, simply replace it by getExtra().

    Layout inflation hooks now also work if the layout has been included in other layouts. That's actually a pretty tricky use-case for the "extra" parameter mentioned about (and other tricky technologies).

    If for some reason you need to determine the active XposedBridge version in your module, you can use XposedBridge.XPOSED_BRIDGE_VERSION.

    findMethodBestMatch() now also looks for protected and package-private methods in superclasses. That's mainly useful if you use the callMethod() or callStaticMethod() helper.

    UPDATE: (beta2)
    The new beta should fix the "read-only filesystem" errors. If you used to experience them, please try this version. Otherwise, there is no need (and no advantage) to update.

    UPDATE:
    The final version is out, please use it instead (see first post / in-app installer).
    479
    The ART of patience

    Regarding ART possibly becoming the default runtime engine: I think that's good news because it means that we will get a stable version of ART then. I'm reluctant to work further on ART support at the moment for mainly three reasons:

    1. Time. I used to spend every evening and every weekend for Xposed, either to give support here (often answering the same questions again and again), writing code or researching about bugs or new ideas. As you may have noticed, there are now days or even weeks where I don't even log on to XDA, and I'm actually glad about this.

    2. Experimental software is bound to contain bugs, even severe ones. There is a reason why Google didn't make this choice available for the typical user (and keep in mind, we are not typical users). I neither want people to blame Xposed if their phone starts acting up nor do I want to hunt bugs which are caused by a runtime engine that is explicitely labelled as not finished yet.

    3. As long as ART is experimental, it's much easier to make big changes to the code. Once a final version is out and used by the masses, quality engineers we be much more careful not to break things. That means that Xposed for ART on 4.5 (or whatever it will be called) might need to be completely different than for ART on 4.4. More variants means more time for maintenance. And I don't feel like pushing something out now just to drop support again in a later version. There is not enough benefit of using ART at the moment to justify that.

    You know, I had already worked on ART support and spent several dozens of hours reading the code, looking for ways to hijack it, implementing my ideas, doing trial and error and starting again from the beginning. I finally had my Nexus 5 boot with Xposed in early December and quickly tested the App Settings module. I'm happy about that, but I also know that this was just a very experimental version, less ready than ART itself. It is totally hacked together and only tested with the stock ROM. ART is quite complex and has several different modes. It's not worth giving the current development to someone else before I have tested these things on my phone, where I can debug much better than instructing someone else to do it. It also requires rewriting app_process to be a light executable again, which loads either the Dalvik or ART Xposed library, depending on your settings. That would require changes in the installer as well, etc. etc.

    So you see, there is still lots of work to do. At the moment, I'm not actively working on it, but trying to get some other things fixed (e.g. LG ROMs) or improved (installation via recovery, better installation feedback in case root access failed, static Busybox package). And as I said, I do have other things in my life as well. It's not about money, that's what I have my full-time job for. I work on Xposed for fun (and maybe a bit for the reputation ;)), so the best way to ensure that I keep on working on it is not taking away the fun part of it. Don't pressure me like it was my duty to implement something ASAP (!!!), be patient even if it takes a bit longer until I answer and join the volunteers who help answering basic questions here so I don't have to. Thanks!
    317
    General information on Xposed has been moved to this thread: http://xdaforums.com/xposed/xposed-installer-versions-changelog-t2714053
    The FAQ has been moved to this thread: http://xdaforums.com/xposed/-t2735540
    Questions, suggestions, bug reports and so on can be posted in the Xposed General forum (for the installer/framework/development only) and in the Xposed Framework modules forum (for anything module-related).
    222
    Xposed Framework Installer (Flashable Zip)

    Announcement: Xposed Framework v2.5+ comes with an option to flash its own install zip via recovery, making my package obsolete. I'll leave them up for posterity; could be useful should the need arise for downgrading on some devices. Cheers all! 10000 downloads is pretty cool. :)

    Xposed Framework v2.2+ has fixed JB4.3 installation and v2.4+ has added support for KK4.4, but for those that still want it, or cannot install via the APK due to /system write protection like HTC's S-ON, here is an updated zip frontend method for installing the framework; now for Xposed Framework v2.4.1.

    You MUST have the Xposed Installer APK installed FIRST. The zip will detect if you do not and stop.

    Flash this in recovery and my frontend script (the update-binary) will detect the correct architecture and SDK version to use the appropriate Xposed app_process and busybox builds (x86, armv5, v6 and v7 & sdk 15 and 16+ supported), and should detect the uid of the Xposed Installer APK on-the-fly and set up the required files with it.

    It leaves a log behind in /data/local/tmp/xposed-log.txt either way with more details about how it went. :cool:

    It also unpacks Xposed-Disabler-Recovery.zip to /sdcard/ (or /sdcard/0/ if it exists) to be as close to the APK install method as possible. For those wanting another method to reactivate after a ROM update or toggle Xposed disabled/enabled, @amishxda has also created a cool "Xposed toggler" zip here.

    Note: Xposed Framework files and the install.sh used are the work of @rovo89 and @Tungstwenty; I have only created a recovery flashable zip to function as an alternative frontend for the framework installation process. I take no credit for their fantastic work.


    P.S. If you found this handy then please check out my Odds and Ends thread for more flashable goodness. :D

    5351 downloads of v2.1.4 when removed. 1049 downloads of v2.2 when removed.
    193
    Xposed 2.5 final

    This is Xposed version 2.5 (final). The main new features and fixes in this version are:
    • Rewritten framework installation/uninstallation
      • Uses interactive su (via libsuperuser) to provide improved compatibility with different Superuser apps
      • Better feedback when root access fails (doesn't freeze the app anymore)
      • Offers installation via custom recovery (CWM/TWRP), either flashing the file automatically or manually
    • Safemode to disable Xposed with hardware keys to get out of (most) bootloops
    • Compatibility with Sony/LG ROMs (4.3 and 4.4), Meizu ROMs (4.4)
    • Debug setting to disable resource hooking as a temporary workaround for incompatibilities with some theming engines (not all modules can be used in this mode)
    There are also other improvements and fixes, especially many translations updates.
    In case you get a message "Segmentation fault" during installation, you can now download an additional app which provides statically compiled versions of BusyBox (a lot bigger, but should work with every ROM). It's not needed otherwise.

    Quick explanation of the safemode: It was developed by @Tungstwenty and makes it possible to disable Xposed by repeatedly pressing one of the hardware buttons during early startup. The phone will vibrate twice when the first key press has been detected. Then you have five seconds to press the same button four more times. Each key press will be confirmed with a short vibration; the final one with a long vibration. It creates /data/data/de.robv.android.xposed.installer/conf/disabled, which prevents most of Xposed's actions (e.g. no hooks are made and no modules are loaded). There's no 100% guarantee that this will get you out of a bootloop, but in most cases it should.

    As always, you can download it via the in-app updater or from http://dl.xposed.info/latest.apk.