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

Status
Not open for further replies.
Search This thread

mirko brand

Member
Feb 24, 2014
42
2
Since this was my first update (I got my phone a month ago) and encounter with this issue I didn't know what it was. Thanks for the info. ;)
 

Bob1732

Member
Mar 11, 2014
6
1
Sorry to bother again, after a few hours reading and trying i am still in need of a bit of assitance.

OnCreate wasnt working the way i intended so i switched to a loadlibrary hook, i intended to load my library after the last unique library is loaded from the application, i need to obviously add in the param result check to make sure lib is loaded successfully but at the moment i can see through catlog the lib is loaded without a problem.

The lib i am using is just the sample/hello-jni from NDK

Defined as:
jstring Java_com_example_hellojni_HelloJni_stringFromJNI( JNIEnv* env,
jobject thiz )

public native String stringFromJNI(); // should just return a simple string

so com.example.hellojni.HelloJni.stringFromJNI(); is what i wanna call, trying the following i always get a class not found exception.

Code:
try {
	Class<?> exampleclass = XposedHelpers.findClass("com.example.hellojni.HelloJni", (ClassLoader)lpparam.classLoader);

	if (exampleclass != null){
		XposedBridge.log("NativeCALL-Result: " + (String)exampleclass.getMethod("stringFromJNI").invoke(null));
	}

} catch (Exception e) {
	e.printStackTrace();
}

any clue ? i know the library is loaded successfully through cat log.
 

nostromo76

Senior Member
Aug 19, 2007
440
96
LG G2 Cloudyfa CloudyStock 1.2

Dear all, I've been having trouble installing Xposed Framework in this ROM.

After installing/updating and rebooting I'm still unable to "activate" the framework.

Do you have any recommendation?

Thnak you very much in advance!

Nostromo.
 

defim

Senior Member
Feb 18, 2012
2,744
1,489
Motorola Defy
Nexus 7 (2013)
Yes, actually the "active" column is more like "installed" and there would have to be an additional column to display the version which was present when the Android stack started. I think that would be too much though. Maybe the best idea would be do rename the column, but it would have to be done in all the 30 translations.

Renaming the row or adding another one, both ways needs a new translation :(
 

Vagelis1608

Senior Member
Sep 16, 2012
2,240
870
Athens
LG G2 Mini
Xiaomi Redmi Note 4
Dear all, I've been having trouble installing Xposed Framework in this ROM.

After installing/updating and rebooting I'm still unable to "activate" the framework.

Do you have any recommendation?

Thnak you very much in advance!

Nostromo.

Go to Xposed Installer -> Settings -> Installation mode and choose recovery. Then go to Xposed Installer -> Framework -> Install/Update and reboot.
 

rovo89

Senior Recognized Developer
Jan 4, 2012
2,585
81,433
Sorry to bother again, after a few hours reading and trying i am still in need of a bit of assitance.

OnCreate wasnt working the way i intended so i switched to a loadlibrary hook, i intended to load my library after the last unique library is loaded from the application, i need to obviously add in the param result check to make sure lib is loaded successfully but at the moment i can see through catlog the lib is loaded without a problem.

The lib i am using is just the sample/hello-jni from NDK

Defined as:
jstring Java_com_example_hellojni_HelloJni_stringFromJNI( JNIEnv* env,
jobject thiz )

public native String stringFromJNI(); // should just return a simple string

so com.example.hellojni.HelloJni.stringFromJNI(); is what i wanna call, trying the following i always get a class not found exception.

Code:
try {
	Class<?> exampleclass = XposedHelpers.findClass("com.example.hellojni.HelloJni", (ClassLoader)lpparam.classLoader);

	if (exampleclass != null){
		XposedBridge.log("NativeCALL-Result: " + (String)exampleclass.getMethod("stringFromJNI").invoke(null));
	}

} catch (Exception e) {
	e.printStackTrace();
}

any clue ? i know the library is loaded successfully through cat log.

First of all, have you verified the your library is working fine in a "normal" app? Before that, I wouldn't try to do such calls in an Xposed module.
I believe a difficulty with this are the class loaders. You are looking for the HelloJni class in the app - is it defined in the app? Or your module? If it's in your module, then you should be able to avoid reflection completely, but you need to make sure that the library is loaded for the right classloader. System.loadLibrary() takes that caller's loader, whereas you look for the class in param.classLoader...
 

Bob1732

Member
Mar 11, 2014
6
1
First of all, have you verified the your library is working fine in a "normal" app? Before that, I wouldn't try to do such calls in an Xposed module.
I believe a difficulty with this are the class loaders. You are looking for the HelloJni class in the app - is it defined in the app? Or your module? If it's in your module, then you should be able to avoid reflection completely, but you need to make sure that the library is loaded for the right classloader. System.loadLibrary() takes that caller's loader, whereas you look for the class in param.classLoader...

Thanks again for your time.

The package i want to hook is called "com.test.test"

the package com.example.hellojni does not exist, i only have this function defined inside the shared library.. maybe this is a limitation or a misunderstanding from me.

The method and class would never exist inside the package, but the way i understood it was i could system.loadlibrary and that defined class would be added to the program.

Perhaps i need to rename my function to REALPACKAGE.CLASS.METHOD instead of com.example.hellojni, going to try this and keep trying.
 
Last edited:

rovo89

Senior Recognized Developer
Jan 4, 2012
2,585
81,433
The method and class would never exist inside the package, but the way i understood it was i could system.loadlibrary and that defined class would be added to the program.

Perhaps i need to rename my function to REALPACKAGE.CLASS.METHOD instead of com.example.hellojni, going to try this and keep trying.

The Java class containing the native methods definitely needs to be loaded by any classloader, and then you must load the native library for the same classloader. During the initialization, the native library should then connect the C++ functions to the Java stub. Not sure if you need to do this manually for real JNI, at least the system libraries explicitely register their methods.

If com.example.hellojni.HelloJni isn't part of com.test.test, then you have to include it in your module or load it from another jar file. Renaming doesn't change anything about this, you can have two classes with the same name and package and yet they won't be the same unless they are also loaded by the same classloader.
 
  • Like
Reactions: paulle

MgudFrn

Senior Member
Oct 18, 2013
70
5
28
Kathmandu
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.

I'm getting Segmentation Fault in this version. I tried installing using all three methods but there is same problem.
Previous version works fine.

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.

Where is that additional app? Please see my attachment for actual error message:

uploadfromtaptalk1395597492356.jpg

Sent from my Karbonn A1* using xda app-developers app
 
Last edited:
  • Like
Reactions: paulle

Bob1732

Member
Mar 11, 2014
6
1
The Java class containing the native methods definitely needs to be loaded by any classloader,

There is the problem then, I assumed the loaded library added the method automatically but when I think about it, it can't add the method when the class doesn't exist makes sense now. All a little over my head at the moment, need to learn a lot more about how java works.

For now I will just use jni_onload to set up the hooks but I look forward to being able to learn a more advanced way.

Really many thanks for your time.
 

hamzahrmalik

Senior Member
May 31, 2013
1,658
2,020
I need help editing dimens.xml in framework-res.apk using Xposed

I am trying to make a very simple module which will simply replace navigation_bar_height property with a user defined value. At the moment, since the module is in early development, it simply sets it to 20 (no configurable option). The default is 48 on my phone so I think I should be seeing a difference, but I'm not. I'm not sure if it is failing to replace the resource, or if it is replacing but then ignoring the new value. Here is the code

Code:
import android.content.res.XResources;
import de.robv.android.xposed.IXposedHookZygoteInit;
import de.robv.android.xposed.XposedBridge;

public class Main implements IXposedHookZygoteInit{

	@Override
	public void initZygote(IXposedHookZygoteInit.StartupParam startupParam) throws Throwable {
		XposedBridge.log("LOADED");
		try {
			XResources.setSystemWideReplacement("android", "dimen", "navigation_bar_height", 20.0);
		
	} catch (Throwable t) { XposedBridge.log(t); }
	}

}

Any help is appreciated
 

rovo89

Senior Recognized Developer
Jan 4, 2012
2,585
81,433
I'm getting Segmentation Fault in this version. I tried installing using all three methods but there is same problem.
Previous version works fine.

Where is that additional app? Please see my attachment for actual error message:

View attachment 2645989

Here it is. I wanted to know how frequently this error occurs - not too often as it seems.
Just as a reminder: This file is only needed when you get "Segmentation fault" errors.
 

Attachments

  • XposedInstallerStaticBusyBox_v1.apk
    279.3 KB · Views: 65,550

rovo89

Senior Recognized Developer
Jan 4, 2012
2,585
81,433
I am trying to make a very simple module which will simply replace navigation_bar_height property with a user defined value. At the moment, since the module is in early development, it simply sets it to 20 (no configurable option). The default is 48 on my phone so I think I should be seeing a difference, but I'm not. I'm not sure if it is failing to replace the resource, or if it is replacing but then ignoring the new value.

At the moment, it's not possible to replace dimension resources with variables/literals. You can only forward it to your module's resources: https://github.com/rovo89/XposedBridge/wiki/Replacing-resources#complex-resources
 
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!
    316
    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.