Remove All Ads from XDA

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

2,585 posts
Thanks Meter: 81,779
 
By rovo89, Senior Recognized Developer on 31st March 2012, 03:55 PM
Thread Closed Email Thread
30th November 2013, 08:26 AM |#6111  
Member
Thanks Meter: 108
 
Donate to Me
More
Quote:
Originally Posted by lulu217783

Does this work on cataclysm ROM?

Sent from my Nexus 5 using xda premium

Most likely, give it a go. If it doesn't, uninstall, simple as that.
30th November 2013, 09:07 AM |#6112  
seriosbrad's Avatar
Senior Member
Flag Alberta
Thanks Meter: 230
 
More
Everything works perfect with Gravity Box on the 11/29 Nightly OMNI ROM for Note 2
30th November 2013, 09:31 AM |#6113  
davidwyl's Avatar
Senior Member
Thanks Meter: 33
 
More
Quote:
Originally Posted by egingell

It doesn't choose. Whichever one loads last overrides the previous; however, if an option is not enabled, it gets ignored... or so I believe. There's also no harm in enabling the same option in both.

SGS2 - JB 4.1.2 GB27
SGS4 - JB 4.2.2 MF9

does it has any rules which one load last?
install/enable last will get loaded last??
30th November 2013, 10:13 AM |#6114  
Member
Thanks Meter: 5
 
More
I am having some serious issues with bootloops, this if my 5th on 3 days and I suspect that it might have to do something with xposed. The only problem I have is when I get one I have to format /data and I believe its where xposed is keeping its logs? I am now using ADB on a windows machine and I have not yet formatted /data. How do I pull the logs with ADB? I have tried "adb logcat.txt /C:\ but that doesn't work.. Maybe I have usb debugging deactivated... I can't see the logs if I try adb -s Xposed aswell.
30th November 2013, 10:57 AM |#6115  
defim's Avatar
Senior Member
Thanks Meter: 1,500
 
More
Quote:
Originally Posted by VRob

Why is it that it tells me "can't open file" when I download and then attempt to install?... Nexus 5, running stock but rooted android. Thanks, please forgive my ignorance.

It's a misleading message. I got it also when the api required by the apk it's higher than your system s
30th November 2013, 11:01 AM |#6116  
rovo89's Avatar
OP Senior Recognized Developer
Thanks Meter: 81,779
 
Donate to Me
More
Quote:
Originally Posted by Ranomez

I can install Carbon ROM or AOKP and test if you want, but last time I tried with all my apps the SysteUI startup delay still happened even without Xposed but was way shorter (a few seconds), cause of that I moved to AOSP+ till now, but that didn't get updated so I switched to SlimBean now till we get android 4.4, then I'll go back to pure AOSP/AOSP+ (if it gets updated), cause of your framework I could give up "AOSP custom roms" like AOKP and Carbon for roms as close to pure AOSP as possible. Anyway tell me if you want me to test AOKP or Carbon, but it will take me a whole night to restore all my apps with titanium after I flash?

I don't want to steal your time and it's not urgent. If you have the time though, I would appreciate if you could compare the boot times between Xposed 2.3.1, 2.4 and without Xposed.

Quote:
Originally Posted by halomaster

Someone I know currently has a Galaxy S4 complete stock with 4.3. He has knox on his phone.

Let's say I root his phone with the method that does not trip the knox counter (rooted with knox 0x0). If I install the Xposed framework and the modules, will it trip the knox counter?

I don't know how Knox is implemented and what it looks for, so I can't give an answer to that, sorry.

Quote:
Originally Posted by egingell

It doesn't choose. Whichever one loads last overrides the previous; however, if an option is not enabled, it gets ignored... or so I believe. There's also no harm in enabling the same option in both.

Well, kind of, but I really wouldn't recommend enabled the same option in both modules. As you said, both modules will be executed. They might achieve this feature in different ways or they might hook the same method. In the latter case, the modules are called one after another in a rather random order. Sometimes this will work just fine, but if for example both try to remove a view, the second one won't find it anymore and might not handle this very well.

This is why developers of tweak collections should give you the possibility to disable the tweaks individually and don't even attempt to do anything if you disabled it. It's all up to the modules' good behavior, Xposed couldn't handle this even if it wanted to. And relying on a certain order is not good behavior.

Quote:
Originally Posted by RovG

@rovo89, I am not sure is this error is Materdualfix's or Xposed's. Please check.


Code:
-----------------
30 Nov 2013 05:39:15 UTC
Loading Xposed v41 (for Zygote)...
Loading modules from /data/app/com.dr8.sbicons.sgs-1.apk
  Loading class com.dr8.sbicons.sgs.mod.StatusBarMods
Loading modules from /data/app/com.oasisfeng.greenify-2.apk
  Loading class com.oasisfeng.greenify.pro.FrameworkPatch
Loading modules from /data/app/ma.wanam.youtubeadaway-2.apk
  Loading class ma.wanam.youtubeadaway.module.Xposed
Loading modules from /data/app/tungstwenty.xposed.masterkeydualfix-1.apk
  Loading class tungstwenty.xposed.masterkeydualfix.XposedMod
java.lang.IllegalStateException: Cannot broadcast before boot completed
at com.android.server.am.ActivityManagerService.verifyBroadcastLocked(ActivityManagerService.java:13982)
at com.android.server.am.ActivityManagerService.broadcastIntent(ActivityManagerService.java:14000)
at de.robv.android.xposed.XposedBridge.invokeOriginalMethodNative(Native Method)
at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:547)
at com.android.server.am.ActivityManagerService.broadcastIntent(Native Method)
at com.oasisfeng.greenify.pro.i.a(SourceFile:33)
at com.oasisfeng.greenify.pro.a.r.a(SourceFile:58)
at com.oasisfeng.b.a.afterHookedMethod(SourceFile:27)
at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:561)
at com.android.server.am.ActivityManagerService.startProcessLocked(Native Method)
at com.android.server.am.BroadcastQueue.processNextBroadcast(BroadcastQueue.java:777)
at com.android.server.am.BroadcastQueue$1.handleMessage(BroadcastQueue.java:129)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:137)
at com.android.server.am.ActivityManagerService$AThread.run(ActivityManagerService.java:1557)
-----------------

Have a look at the trace, it clearly happens in a module hooked by Greenify. That should be the first contact.

Quote:
Originally Posted by ryebread761

Not sure if you'd know why the drawables aren't appearing correctly though?

No idea. Maybe check if there are other drawables or layouts needed for this, especially for the shadows?

Quote:
Originally Posted by EzZn0

I am having some serious issues with bootloops, this if my 5th on 3 days and I suspect that it might have to do something with xposed. The only problem I have is when I get one I have to format /data and I believe its where xposed is keeping its logs? I am now using ADB on a windows machine and I have not yet formatted /data. How do I pull the logs with ADB? I have tried "adb logcat.txt /C:\ but that doesn't work.. Maybe I have usb debugging deactivated... I can't see the logs if I try adb -s Xposed aswell.

try "adb logcat -d > logcat.txt" while you are in the boot loop.
The Following 4 Users Say Thank You to rovo89 For This Useful Post: [ View ]
30th November 2013, 11:05 AM |#6117  
Quote:
Originally Posted by rovo89

I don't want to steal your time and it's not urgent. If you have the time though, I would appreciate if you could compare the boot times between Xposed 2.3.1, 2.4 and without Xposed.

Ok, will do later today or tomorow night, but that means I will report tomorow if I install AOKP today or on monday if I install it tomorow night.
The Following User Says Thank You to Ranomez For This Useful Post: [ View ] Gift Ranomez Ad-Free
30th November 2013, 12:21 PM |#6118  
rovo89's Avatar
OP Senior Recognized Developer
Thanks Meter: 81,779
 
Donate to Me
More
Xposed 2.4 final
This is Xposed version 2.4. The main new features and fixes in this version are:
  • Support for Android 4.4 (KitKat) in Dalvik mode (ART is not supported, see below)
  • 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/XposedBrid...9b5584d0396054
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.

There is a new findFirstFieldByExactType() helper, which might be useful if you target an app protected with Proguard and know that there is just one field with that specific type. Don't use it because of laziness.
The Following 186 Users Say Thank You to rovo89 For This Useful Post: [ View ]
30th November 2013, 02:01 PM |#6119  
Senior Member
Flag Jakarta
Thanks Meter: 462
 
Donate to Me
More
i just want a quick question...
is possible to make:

resparam.res.setReplacement("com.package", "drawable", "pngs", xxxxx);

where xxxxx point to an image in external sd card?

thanks
30th November 2013, 02:08 PM |#6120  
CoolApps's Avatar
Senior Member
Thanks Meter: 610
 
More
@rovo89 Thanks for this awesome update.
Will it be still safe to update the framework to 2.4 even on Android 4.3?

Sent from my Nexus 4 using Tapatalk
30th November 2013, 02:35 PM |#6121  
rovo89's Avatar
OP Senior Recognized Developer
Thanks Meter: 81,779
 
Donate to Me
More
Quote:
Originally Posted by fajarep

i just want a quick question...
is possible to make:

resparam.res.setReplacement("com.package", "drawable", "pngs", xxxxx);

where xxxxx point to an image in external sd card?

thanks

Not exactly with that syntax, you need to implement a DrawableLoader:
https://github.com/rovo89/XposedBrid...cing-resources

Quote:
Originally Posted by CoolApps

Will it be still safe to update the framework to 2.4 even on Android 4.3?

Yes, Xposed is still compatible down to Android 4.0.3.
The Following 2 Users Say Thank You to rovo89 For This Useful Post: [ View ]
Thread Closed Subscribe to Thread

Tags
don't ask questions about modules here!!!, framework, xposed
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes