• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

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

Status
Not open for further replies.
Search This thread

bedtime_with_the_bear

Senior Member
Mar 31, 2011
219
208
Sydney, Australia
So the app can check for updates and so but won't notify you? is this normal behaviour?

I think rovo already answered thus earlier in the thread, but yes, it's normal. Individual modules could implement this functionality for themselves, in theory, but I'd question whether that would be desirable at the module level.

Sent from my Nexus 4 using Tapatalk
 

deviantstudio

Member
Jun 14, 2010
29
78
Hi again!
I trying to implement FPS meter mod with help of Xposed framework. In theory i want to hook onDraw method (or similar) of some "root" window element. Does any of devs has such expirience? Unfortunatelly im not much familiar with android sources and framework concepts. So will be appreciated to any advices in start point. Probably need to look at WindowManager class and find out how it attach views. And still not sure about open gl native code. Does such games using WindowManager at all?
 
  • Like
Reactions: mw86

egingell

Senior Member
Apr 10, 2012
4,754
2,059
44
blog.sophielabuf.com
I think rovo already answered thus earlier in the thread, but yes, it's normal. Individual modules could implement this functionality for themselves, in theory, but I'd question whether that would be desirable at the module level.

Sent from my Nexus 4 using Tapatalk

Personally, I would just use the Download Manager to download my own updates.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
 

zacutesz

Senior Member
Aug 10, 2013
257
22
City of Flowers
why everytime i'm trying to open icon Themer or Unicon, a notification always shown. even i try check and uncheck the module and reinstall the framework





sorry for my bad english
 

Attachments

  • Screenshot_2013-12-24-09-37-54.png
    Screenshot_2013-12-24-09-37-54.png
    137.5 KB · Views: 890
  • Screenshot_2013-12-24-14-21-33.png
    Screenshot_2013-12-24-14-21-33.png
    131.8 KB · Views: 871

bosox01

Member
Dec 25, 2011
29
1
Lampung
iam getting an error while iam installing on my xperia z android 4.3
rooted , deodexed
i tried the install couple of times but same results
the log file :

Dec 23, 2013 1:39:41 AM UTC
Loading Xposed v42 (for Zygote)...
Errors during Xposed initialization
java.lang.NoSuchMethodError: android.app.ActivityThread#getTopLevelResources(java.lang.String,int,android.content.res.Configuration,android.content.res.CompatibilityInfo)#exact
at de.robv.android.xposed.XposedHelpers.findMethodExact(XposedHelpers.java:208)
at de.robv.android.xposed.XposedHelpers.findMethodExact(XposedHelpers.java:155)
at de.robv.android.xposed.XposedHelpers.findAndHookMethod(XposedHelpers.java:167)
at de.robv.android.xposed.XposedBridge.initXbridgeZygote(XposedBridge.java:277)
at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:111)
at dalvik.system.NativeStart.main(Native Method)

same problame :( :(
 

1Chef

Senior Member
Oct 10, 2012
768
247
I currently can't search so sorry if this has been previously asked but xposed is making the immersive mode popup appear on my device fairly regularly on unlock, is there any fix?

Sent from my Nexus 4 using Tapatalk
 

astrosp4c3

Senior Member
May 28, 2012
464
148
Moon
In lastest cm11 nightly (23-24, 21 work perfect) for i9000 xposed cause bootloop..

Any idea ?

EDIT:

Nevermind it , i tried disabling all modules and it install perfectly. Maybe is a module causing it

Inviato dal mio GT-I9000 utilizzando Tapatalk
 
Last edited:

bjtu2011

New member
Dec 24, 2013
1
0
I have the same error with you,please help me~~~

I tested the xposed installer on both my Galaxy Nexus and Nexus 7, running Android 4.2.1 and the installations works fine without any issues.

Next I'm trying to build an xposed module. So I first went through the tutorial step by step until I reached the chapter "Trying it out". There it fails with the following error:



The only difference from the tutorial is that I'm using IntelliJ IDEA instead of Eclipse. But the project builds fine. I'm referring to the XposedBridgeApi.jar from your git project.

Then I looked into the source of the error (XposedBridge.java:95) and discovered there's an check for the API level <= 16. However I have API level 17, is it possible this might be the problem here?

Have you solved the java.lang.IllegalAccessError in Xposed module project?Now i have the same problem with you,could you help me? Thank you!
 

Teotsi

Member
Aug 12, 2013
14
5
OK, so i have a rooted phone and everything.
When i downloaded the latest.apk, and opened it, I went to the Framework section, as instructed. Hit install/update, gave root permissions, and..."[-]exec: No such file or directory". Whatever button i press it says the same damn thing. Somebody help?
 

defim

Senior Member
Feb 18, 2012
2,744
1,487
Awesome work!!

One question: In my case, Xposed doesn't notify me about updates
..
So the app can check for updates and so but won't notify you? is this normal behaviour? In this case, could an option be added to notify the user that there's new updates for the modules they've installed (activated or not)? In the case a lot of people doesn't need this, it could be disabled by default. In my case, I love spending hours testing modules and sometimes I am waiting for a fix of one of them while it has been already checked by Xposed :S

++

I don't like it too, to check Xposed installer daily for updates
 

shekinahsmoke

Senior Member
Mar 21, 2011
2,422
949
Brooklyn, NY
so I have Mokee OS 4.4.2 rom on sprint gs3. I was able to isolate why my IMEI and info gets lost on boot up. I am on Xposed 2.4.1. Xposed is messing w/ something and it affects Phone information and gives me no service.
 
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.