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

Status
Not open for further replies.
Search This thread

rovo89

Senior Recognized Developer
Jan 4, 2012
2,585
81,434
You are trying to replace a drawable wih an integer? That can't work, neither for framework-res nor for SystemUI.

You can either use "new XResources.DrawableLoader { ... }" or the XModuleResources/modRes.fwd approach (as mentioned in the Github wiki page). If you bundle the new image with your module, the second option is probably better/easier.
 
  • Like
Reactions: ddmitcyber

Tungstwenty

Senior Member
Nov 1, 2011
1,830
4,512
please example code setReplacement for change icon in framework-res.apk or settings.apk
If you want to change resources in the framework instead of a specific package, you need to do it in initZygote instead of handleInitPackageResources.

Here's an example that I'm using, to replace a dimension resource in the framework. You can do the same to fwd a drawable to a resource bundled in your module.
Code:
	public void initZygote(StartupParam startupParam) throws Throwable {
		prefs = new XSharedPreferences(MY_PACKAGE_NAME);
		modulePath = startupParam.modulePath;
		if (prefs.getBoolean("status_bar_180dpi", false)) {
			XModuleResources modRes = XModuleResources.createInstance(modulePath, null);
			XResources.setSystemWideReplacement("android", "dimen", "status_bar_height", modRes.fwd(R.dimen.status_bar_height));
			XResources.setSystemWideReplacement("android", "dimen", "status_bar_icon_size", modRes.fwd(R.dimen.status_bar_icon_size));
		}
	}
 

paulobrien

Senior Member
Nov 6, 2003
5,276
7,321
Norwich
www.MoDaCo.com
A follow up to the issue I was having with /mnt/asec installation.

I've actually worked around it by getting the module itself to check the app's sourceDir (via pm.getApplicationInfo) and if it's /mnt/asec, then to pop up an alert to the user followed by initiating an installation of the module's own APK which i'm bundling in the module itself. :)

Not ideal arguably, but it works pretty smoothly from a user perspective. :)

P
 

rovo89

Senior Recognized Developer
Jan 4, 2012
2,585
81,434
Ok, so it's basically the same APK that you are delivering inside itself? Probably with a different package name as it has to be unique? Or is the app basically the installer for your module, maybe with some additional options?
 

paulobrien

Senior Member
Nov 6, 2003
5,276
7,321
Norwich
www.MoDaCo.com
Ok, so it's basically the same APK that you are delivering inside itself? Probably with a different package name as it has to be unique? Or is the app basically the installer for your module, maybe with some additional options?

It's delivering exactly the same APK which installs over the top of itself... But a regular install like that goes to /data/app rather than /mnt/asec so problem solved! :)

P

Sent from my HTC One using Tapatalk 2
 

ddmitcyber

Member
Feb 3, 2013
6
1
this is work on multi apk?

public void handleInitPackageResources(InitPackageResourcesParam resparam) throws Throwable {
if (!resparam.packageName.equals("com.android.settings"))
return;

XModuleResources modRes = XModuleResources.createInstance(MODULE_PATH, resparam.res);
resparam.res.setReplacement("android", "drawable", "switch_thumb_activated_holo_dark", modRes.fwd(R.drawable.frameworks_res_switch_thumb_activated_holo_dark));
resparam.res.setReplacement("android", "drawable", "switch_thumb_activated_holo_light", modRes.fwd(R.drawable.frameworks_res_switch_thumb_activated_holo_light));

}
@Override
public void handleInitPackageResources(InitPackageResourcesParam resparam) throws Throwable {
if (!resparam.packageName.equals("com.android.systemui"))
return;

XModuleResources modRes = XModuleResources.createInstance(MODULE_PATH, resparam.res);
resparam.res.setReplacement("android", "drawable", "switch_thumb_activated_holo_dark", modRes.fwd(R.drawable.frameworks_res_switch_thumb_activated_holo_dark));

how to do this ?
 

rovo89

Senior Recognized Developer
Jan 4, 2012
2,585
81,434
You will probably get a message that you cannot have the same message twice, which is correct. Just try something like this:
Code:
public void handleInitPackageResources(InitPackageResourcesParam resparam) throws Throwable {
  if (resparam.packageName.equals("com.android.settings")) {
    // replacements that apply only to the settings app
  } else if (resparam.packageName.equals("com.android.systemui")) {
    // replacements that apply only to the System UI
  }
}

I would probably create the XModuleResources inside the if clauses (which means you'd have this line twice), otherwise you will create and throw away an object for all other packages.


Other question: You are replacing a resource from the framework here, but only for two apps. Is this intended? If you want to replace it for all apps (like you asked before), use the way Tungstwenty suggested here (you can skip the two lines with "prefs", they are just there to allow users to toggle the replacement on/off).
 
  • Like
Reactions: ddmitcyber

Marco Lomas

Senior Member
Feb 17, 2012
801
206
Can you please make it conpatible with x86 processor? On my Motorola Razr I dont work :(

Enviado desde mi XT890 usando Tapatalk 2
 

Osyx

Senior Member
Dec 10, 2011
1,026
425
Is there a way to disable xposed thru stock recovery? My friends note 2 got stuck in bootloop after enabling tablet UI module

Skickat från min C6603 via Tapatalk 2
 

rovo89

Senior Recognized Developer
Jan 4, 2012
2,585
81,434
Can you please make it conpatible with x86 processor? On my Motorola Razr I dont work :(

I have no such plans. It would mainly require some different code in the native part of Xposed. Unfortunately, this is some rather dirty coding - it changes native code by patching the assember code by changing several bytes... which cannot be done without much trial and error. I have neither the time nor the x86 device for testing.


Could you please add Gingerbread support

No. This would require rewriting many central parts of Xposed and lots of testing. I have no interest in doing this, also for the two reasons mentioned above: missing time and device. Just with the difference that GB support would be much, much more difficult. It would basically be a different "product".

Is there a way to disable xposed thru stock recovery? My friends note 2 got stuck in bootloop after enabling tablet UI module

Restoring the last backup should always work. If you can somehow create a file /data/xposed/disabled or delete /data/xposed/XposedBridge.jar, Xposed will also not be loaded. Maybe you can also do this via "adb shell" while in the bootloop. Otherwise.. reflashing any ROM or wiping /data completely should work as well.
 

Osyx

Senior Member
Dec 10, 2011
1,026
425
I have no such plans. It would mainly require some different code in the native part of Xposed. Unfortunately, this is some rather dirty coding - it changes native code by patching the assember code by changing several bytes... which cannot be done without much trial and error. I have neither the time nor the x86 device for testing.




No. This would require rewriting many central parts of Xposed and lots of testing. I have no interest in doing this, also for the two reasons mentioned above: missing time and device. Just with the difference that GB support would be much, much more difficult. It would basically be a different "product".



Restoring the last backup should always work. If you can somehow create a file /data/xposed/disabled or delete /data/xposed/XposedBridge.jar, Xposed will also not be loaded. Maybe you can also do this via "adb shell" while in the bootloop. Otherwise.. reflashing any ROM or wiping /data completely should work as well.
Okey thanks :)

Skickat från min C6603 via Tapatalk 2
 

rovo89

Senior Recognized Developer
Jan 4, 2012
2,585
81,434
can i change
ex : linearlayout vertical to linearlayout horizontal without replace a layout ?

Haven't tried it myself, but it should work. Have a look at the "Modifying layouts" part of this page. You hook the layout resource which includes the LinearLayout. Then in handleLayoutInflated, you can change the layout. If the LinearLayout is the root node of the layout you hooked, just cast liparam.view to LinearLayout. Otherwise, you need to use findViewById as shown in the example to get a reference to your LinearLayout. Once you have this reference, you can use myLayout.setOrientation().
 
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.