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

Status
Not open for further replies.
Search This thread
By:
Advanced…
rovo89

rovo89

Senior Recognized Developer
Jan 4, 2012
2,585
81,400
mmcneil said:
@ rovo89, I want to add Xposed to my custom build android build; based the response show above, do I include only the Xposed folder or do I need to add all three folders that are found under the "Source code" listing in the OP ? Thanks.

Mike
Click to expand...
Click to collapse

mmcneil said:
Thanks for responding. In answer to your question, I'd like to have it listed in "Settings" as opposed to just showing up as an icon in the app drawer. So for example, if I had a section in Settings called "MyTools", I'd want to have Xposed show up in that section. I don't know that I could do that with just the .apk I hope I explained that properly :eek:

Thanks,

Mike
Click to expand...
Click to collapse

Xposed needs to be installed via the app in order to create the required data structures etc. If you just dropped in the native part of Xposed into your ROM, you would get an additional binary app_process_xposed_sdkXX. With a modification of Android.mk, you could replace /system/bin/app_process directly, but you don't gain anything from that. The user would still have to open the app and press the install/update button. Even if you also compiled XposedBridge.jar and the installer yourself.

You can of course modify your settings app to include a "link" to the installer, you don't need any change in the APK for this. And many launchers allow to hide certain applications if you really want to.

Please also the FAQ on how I don't support such attempts to include Xposed into ROMs.
 
  • Like
Reactions: kitrax59
mefistos

mefistos

Senior Member
Feb 3, 2013
391
151
Sligo
Rovo any info on the secure storage problem on galaxy s5 which causes private mode not working wit xposed? :)

Sent from my SM-G900F using Tapatalk
 
1

1967ls2

Senior Member
Jun 17, 2010
419
13
Installed the xposed all, everything went well buy now my Verizon s5 retail version is super slow & buggy. I've uninstalled the xposed apk but no change. Anyway to quickly revert back?

Edit: never mind. Reinstalled & found the option to uninstall. Seems to be smooth as butter again
 
Last edited:
  • Like
Reactions: xKloaKa
Pkt_Lnt

Pkt_Lnt

Inactive Recognized Contributor
Dec 26, 2011
7,894
5,804
SLO
1967ls2 said:
Installed the xposed all, everything went well buy now my Verizon s5 retail version is super slow & buggy. I've uninstalled the xposed apk but no change. Anyway to quickly revert back?

Edit: never mind. Reinstalled & found the option to uninstall. Seems to be smooth as butter again
Click to expand...
Click to collapse

You are the second to state this on Verizon S5, but no one has posted an Xposed log while active or a logcat. If you would like help, please post those.
 
  • Like
Reactions: bedtime_with_the_bear
1

1967ls2

Senior Member
Jun 17, 2010
419
13
Fyi, resolved the issue and s health is now working with xposed & I installed wanamp and just made a ton of mods.

Had to uninstall xposed, change a build prop line, then clear all data on s health and health services, reboot, then install xposed. There is a write up in the s5 Verizon forums.
 
  • Like
Reactions: Pkt_Lnt
J

JDM1

Member
Feb 7, 2008
14
4
No mobile network connection after xposed install

I've searched this thread and all through XDA trying to find info on this issue and haven't found anything, so I hope it's ok that I'm posting this here. I attempted to install the xposed framework on my rooted verizon galaxy s5. After I installed it and the phone rebooted, the phone had no cell network or mobile data signal. (In the notification bar, the data indicator displays a circle with a line through it and the mobile signal indicator shows no bars.)... Here is what I tired to remedy:
  • Uninstalled xposed framework and rebooted - same problem.
  • Factory reset - same problem. Now, since the phone is not setup, it tries to activate when it first turns on but can't.
  • ODIN back to stock vis instructions in this thread (http://forum.xda-developers.com/showpost.php?p=53447942&postcount=1) .. Same problem and again it tries to activate but cant.

.. Getting pretty nervous here because I can't find any other examples of people having this issue. Any help that anyone can provide will be very much appreciated.
 
magnamentis

magnamentis

Senior Member
Jul 30, 2013
8,682
8,624
Al-Ándalus
magnamentis.com
more info needed but anyway :

JDM1 said:
I've searched this thread and all through XDA trying to find info on this issue and haven't found anything, so I hope it's ok that I'm posting this here. I attempted to install the xposed framework on my rooted verizon galaxy s5. After I installed it and the phone rebooted, the phone had no cell network or mobile data signal. (In the notification bar, the data indicator displays a circle with a line through it and the mobile signal indicator shows no bars.)... Here is what I tired to remedy:
  • Uninstalled xposed framework and rebooted - same problem.
  • Factory reset - same problem. Now, since the phone is not setup, it tries to activate when it first turns on but can't.
  • ODIN back to stock vis instructions in this thread (http://forum.xda-developers.com/showpost.php?p=53447942&postcount=1) .. Same problem and again it tries to activate but cant.

.. Getting pretty nervous here because I can't find any other examples of people having this issue. Any help that anyone can provide will be very much appreciated.
Click to expand...
Click to collapse

a) according to your info it could be that you lost your efs data (IMEI), search google and xda about efs-backup and you'll find plenty of information

b) i hope you make the proper difference between the framework and the modules. you write "after installing xposed" but the framework
.... will never kill your efs partition/information so it's whether a coincidence, or you did not mentione what else you installed and/or
.... you installed modules with the framework and forgot to see these two things as two instead of one. somehow to install the framework
.... without modules makes little to no sense (IMO) and therefore this could well be a point. check your imei if it's gone or still there.

however, i doubt that one of the modules would kill your efs partition/data, this would be well known after short time but
this is just an assumption, there can be new stuff one does not know any minute.

so resuming this a bit, it's not the framework most probably, cannot even imagine how it would do that and therefore this would be
the wrong thread, start looking in samsung, efs, efsbackup, etc. threads and/or the modules thread of all the modules you're running.

Current Devices:
I9100 Black, CM11 4.4.3 ( Formerly PAC, OMNI, PA, Dorimanx, etc. )
I9100 White, CM11 4.4.3 ( Formerly PAC, OMNI, PA, Dorimanx, etc. )
N7000, 4.1.2 TouchWizz All Stock ( very motivating to continue flashing custom roms further haha.... )
N7100, Cyanogenmod 11, Agni Kernel 2.7.7, Xposed Framework ( Formerly AOSNP, PAC, Omni, PA, Devil, Thor, etc. )
Nexus 4, Cataclysm 4.4.2, Franco Kernel r203, Dalvik & Bionic Patched, Xposed Framework ( Formerly PAC, PA, Cataclysm, Faux, etc. )
Nexus 5, Cyanogenmod 11 4.4.3, ElementalX, Xposed, ( Formerly Cataclysm, Franco & FKU Color Control, Dalvik & Bionic, Faux, Bricked, Chaos etc. )
 
  • Like
Reactions: igs.itec
rovo89

rovo89

Senior Recognized Developer
Jan 4, 2012
2,585
81,400
mefistos said:
Rovo any info on the secure storage problem on galaxy s5 which causes private mode not working wit xposed? :)
Click to expand...
Click to collapse

Let's keep it in this thread please: http://forum.xda-developers.com/xposed/xposed-s5-t2725405/post53501607

theknut said:
BREAKING: Next Major Version of Android to Finally Remove Dalvik and Set ART as Default!

Oh my, they even addressed you personally in this news, rovo :D
Click to expand...
Click to collapse

Just commented on that, I'm afraid people expect that by the day the next Android version is released, I will just compile Xposed for ARt and that's it. Oh, and I'm a bit surprised that they totally remove Dalvik, I thought it might be kept as a developer option.
 
  • Like
Reactions: Aleq, manbat, Mikulic1802 and 11 others
Massi-X

Massi-X

Senior Member
Nov 28, 2013
273
361
String array

Hi @rovo89
I'm trying to do a module but I've met a problem:
I have to edit this array of String situated in a class but i don't have idea how to do it...
Is possible to do this?

Code: 
 public static final String[] FieldA = new String[] {
"a","b","c"
};
 
GermainZ

GermainZ

Inactive Recognized Developer / Retired Forum Mod
Aug 3, 2012
6,174
8,800
Massi-X said:
Hi @rovo89
I'm trying to do a module but I've met a problem:
I have to edit this array of String situated in a class but i don't have idea how to do it...
Is possible to do this?

Code: 
 public static final String[] FieldA = new String[] {
"a","b","c"
};
Click to expand...
Click to collapse
You can't (static final), you need to hook the methods that use this array and handle it there instead.
 
  • Like
Reactions: MarkusOSx and S0bes
Status
Not open for further replies.

Similar threads

rovo89
  • Locked
  • Sticky
[OFFICIAL] Xposed for Lollipop/Marshmallow/Nougat/Oreo [v90-beta3, 2018/01/29]
Replies
49
Views
7M
rovo89
rovo89
rovo89
[DISCUSSION] Xposed for Lollipop
Replies
13K
Views
4M
B
breversa
romracer
[UNOFFICIAL] Systemless Xposed for Android 5.1/6.0 - v86.1 / 20160928 / SDK22/SDK23
Replies
7K
Views
3M
D
Deleted member 11604687
T
[2019.5.1][Magisk] Systemless Xposed v89.3/v90.2-beta3 (SDK 21-27)
Replies
8K
Views
3M
C
CookieCream
wanam
  • Locked
[UNOFFICIAL][5.1/6][v87.1][28 Nov]Xposed for Samsung Lollipop/Marshmallow
Replies
6K
Views
2M
wanam
wanam

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 638
    rovo89
    rovo89
    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).
    View
    479
    rovo89
    rovo89
    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!
    View
    315
    rovo89
    rovo89
    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).
    View
    222
    osm0sis
    osm0sis
    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.
    View
    193
    rovo89
    rovo89
    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.
    View

New posts