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

Status
Not open for further replies.
Search This thread

abhishrant

Member
May 9, 2012
14
0
0
param.args[0]

I'd suggest you review the development tutorials (this is explained there; see OP) and take a look at a few example open source projects.

Thanks that param.args solved the problem... :D
I read the tutorials form the OP it said about param.args but didnt explain how or I couldnt find it.. :{

---------- Post added at 06:37 AM ---------- Previous post was at 06:01 AM ----------

Another problem.... How can I get variables declared in the function in afterHookedMethod? Those are not parameters.... :/

In original function

...
Bundle bundle = this.a();
...

I want to get that bundle variable after the original method is done! :D
 

egingell

Senior Member
Apr 10, 2012
4,754
2,059
0
43
blog.sophielabuf.com
Thanks that param.args solved the problem... :D
I read the tutorials form the OP it said about param.args but didnt explain how or I couldnt find it.. :{

---------- Post added at 06:37 AM ---------- Previous post was at 06:01 AM ----------

Another problem.... How can I get variables declared in the function in afterHookedMethod? Those are not parameters.... :/

In original function

...
Bundle bundle = this.a();
...

I want to get that bundle variable after the original method is done! :D

You can only get class members. Local variables are inaccessible.

Edit: With that example, you should be able to call .a() directly using .callMethod() or .callStaticMethod().

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
 
Last edited:
  • Like
Reactions: abhishrant

BlackArtsInc

Senior Member
Apr 26, 2012
773
77
0
Athens
Just wanted to share a problem I had trying to update xposed modules earlier today and maybe help out someone.

I was trying to update Gravity Box and after downloading the module,I just couldn't press the Install button.Assuming one has already activated the Unknown Sources for installing apps not on the Play Store and also has the Verify Apps disabled in Google Search Settings,the solution for getting the install button to work was to disable Screen Tint related apps.

For me it the problem was caused by Screen Tint Adjuster.Turned it off,updated all xposed modules,then turned it on again.

Hope I helped some people having the same problem.

N.

Not sent from my xPERIA M.
 

FKayan

Member
Mar 19, 2014
19
0
0
Can you test this version please? dropbox.com/s/fvt08kqx5bhnxqa/XposedInstaller_2.5-beta2%2BASUS.apk



You open the Xposed Installer app and go to "Logs". There you can share the log or save it to a file.
Please also make sure that you are using the 2.5 beta2 version (see first post for a link).

Sorry for the delay to reply. rovo89, I had not seen the beta version, so I installed it and it worked thanks.

I have another version of the log if you want I post.

thank you :laugh:
 

taranfx

Senior Member
May 23, 2010
330
240
0
Mountain view, CA
geeknizer.com
This is Xposed version 2.5 beta1. 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. 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 everywhere). 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.

I will leave this version up for a few days for bug reports and to give translators a chance to add missing strings. Unless critical bugs are found, I plan to upload a final version to the repository (e.g. for auto-updates) some time next week.

Update: 2.5 beta2 includes some fixes in the root error detection, plus an indication that the installation mode text is actually clickable.

Well when I install, I get "Could not extract app_process". And it doesnt install by any of the three methods.
 
  • Like
Reactions: maleksa

Programming4life

Senior Member
Jul 8, 2013
620
624
0
programming4life.com
You are calling it as static with callStaticMethod, but your goBack() method is not static. So either change goBack() to static or use callMethod and parse the appropriate class instance

Now I changed the code to this(below) It now does nothing at all. (no error is outputted). Do you know how I can get a exsting instance of the class "com.google.android.apps.chrome.Main" which was created by the app. I think i need to get the initial instance of the class that was created when launching the app but how can I get that existing instance? thanks
Code:
Class<?> Tab = XposedHelpers.findClass("com.google.android.apps.chrome.Main", lpparam.classLoader);
XposedHelpers.callMethod(Tab.newInstance(), "goBack");
Can't I do something like this?
Code:
XposedHelpers.callMethod(existing instance of "com.google.android.apps.chrome.Main" made by app launch, "goBack");
 

dk_zero-cool

Senior Member
Nov 6, 2010
3,529
4,996
0
Horsens
Now I changed the code to this(below) It now does nothing at all. (no error is outputted). Do you know how I can get a exsting instance of the class "com.google.android.apps.chrome.Main" which was created by the app. I think i need to get the initial instance of the class that was created when launching the app but how can I get that existing instance? thanks

You can't. This framework works by letting you hack your way into apps and framework parts, kind of like providing full access to a house you normally would not have access to. While inside this house, you can to whatever you like, just as if it was you who lives there. But you cannot change things inside this house if you are currently inside another house. (Well almost, except for IPC, Broadcasts etc).

So, you need to hook the class (Break into the house) and either do your work from inside there, or use those hooks to add a broadcast or IPC feature that will allow you to execute work in one process from within another.
 

Programming4life

Senior Member
Jul 8, 2013
620
624
0
programming4life.com
You can't. This framework works by letting you hack your way into apps and framework parts, kind of like providing full access to a house you normally would not have access to. While inside this house, you can to whatever you like, just as if it was you who lives there. But you cannot change things inside this house if you are currently inside another house. (Well almost, except for IPC, Broadcasts etc).

So, you need to hook the class (Break into the house) and either do your work from inside there, or use those hooks to add a broadcast or IPC feature that will allow you to execute work in one process from within another.

So I'm screwed? noo, so there is no way of calling "goBack"
 

GermainZ

Inactive Recognized Developer / Retired Forum Mode
Aug 3, 2012
6,174
8,788
113
How can I hook to Listeners? Like onClickListener..? :D
Like any other method, although those are usually in anonymous classes so you might have to update your module if the app gets updated, as the identifier might change (e.g. SomeClass$4 becomes SomeClass$5.)
 
  • Like
Reactions: abhishrant

abhishrant

Member
May 9, 2012
14
0
0
Like any other method, although those are usually in anonymous classes so you might have to update your module if the app gets updated, as the identifier might change (e.g. SomeClass$4 becomes SomeClass$5.)

I update it regularly... :D
Can I have an example (with link... as i am not finding these)?

And what class should I use to hook the method?

Thank You,
 

GermainZ

Inactive Recognized Developer / Retired Forum Mode
Aug 3, 2012
6,174
8,788
113
I update it regularly... :D
Can I have an example (with link... as i am not finding these)?

And what class should I use to hook the method?

Thank You,
As I said, just like any other method. Of course you use the class in which the method is. Here's an example from an old version of one of my modules:
Code:
...
findAndHookMethod("com.google.android.finsky.activities.DetailsTextViewBinder$SelfishUrlSpan", null, "onClick", View.class, new XC_MethodHook() {
    @Override
    protected void beforeHookedMethod(MethodHookParam param) throws Throwable {
        // Code goes here
    }
});
...
 
  • Like
Reactions: abhishrant

abhishrant

Member
May 9, 2012
14
0
0
As I said, just like any other method. Of course you use the class in which the method is. Here's an example from an old version of one of my modules:
Code:
...
findAndHookMethod("com.google.android.finsky.activities.DetailsTextViewBinder$SelfishUrlSpan", null, "onClick", View.class, new XC_MethodHook() {
 [user=439709]@override[/user]
    protected void beforeHookedMethod(MethodHookParam param) throws Throwable {
        // Code goes here
    }
});
...


Actual code
Class com.someGame.helpers.countHelper
package com.someGame.helpers;

public class countHelper {
//Some vars
....

private healthHelper hHelper;
healthHelper.OnHealthChangeListener mPurchaseFinishedListener = new helthHelper.OnHealthChangeListener()
{
public void onIncrese(int count)
{
....
//I want to replace this method with Xposed.
}
.....
});
....
}

So this should be the code in Xposed?

....
final Class<?> hookClass = XposedHelpers.findClass("com.someGame.helpers.countHelper", lpparam.classLoader);
findAndHookMethod(hookClass, null, "onIncrese", ???, new new XC_MethodReplacement() {
@override
protected Object replaceHookedMethod(MethodHookParam param) throws Throwable {
//Code here
}
});

Is that correct? and what should go in '???' ?
 

garyd9

Inactive Recognized Developer
Sep 13, 2006
2,644
2,730
0
50
Pittsburgh, PA
The xposed tutorial (https://github.com/rovo89/XposedBridge/wiki/Development-tutorial) suggests cloning from https://github.com/rovo89/XposedMods/tree/master/XposedLibrary and then referencing XposedBridgeAPI.jar from that project. However, it seems that the API.jar in that repo is a bit out of date and lacks some of the newer xposed framework methods.

Any chance of either updating the API used in XposedLibrary, or updating the tutorial to reference the OP of this thread for a more current API?
 
  • Like
Reactions: rovo89
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!
    313
    General information on Xposed has been moved to this thread: http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053
    The FAQ has been moved to this thread: http://forum.xda-developers.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.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone