Thread Closed

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

OP rovo89

23rd November 2013, 06:33 PM   |  #5611  
theCroh's Avatar
Senior Member
Flag Oulu
Thanks Meter: 36
 
157 posts
Join Date:Joined: Dec 2011
More
Quote:
Originally Posted by vivekmishra

Just trying to ask whether it will support Android 4.4 in future as humbly as possible.

Sent from my Nexus 7 using Tapatalk

@rovo89 is doing his best to find out if and how this can be achieved.

Sent from my Nexus 7 using Tapatalk 4
23rd November 2013, 06:35 PM   |  #5612  
rovo89's Avatar
OP Senior Recognized Developer
Thanks Meter: 14,508
 
2,376 posts
Join Date:Joined: Jan 2012
More
Quote:
Originally Posted by bree1

hello. I tried to reinstall Xposed but again I had the same problems of FC. here is the logcat. thanks for your attention.

https://app.box.com/s/w9kiqmxwgjt0nxyyl655

Thanks, but... there is no FC in the logs. The main logcat would be enough, but it must be taken shortly after the FC, without any reboots in between (because that resets the log). The log is also much shorter than usually, looks like it was reset after booting?

Quote:
Originally Posted by vivekmishra

Just trying to ask whether it will support Android 4.4 in future as humbly as possible.

Yes. Preparing some release notes (and dinner, so give me some time ) at the moment for a beta.

Quote:
Originally Posted by nicola20

Hello , I installed this wonderful application on Samsung s4 4.3 rom stock recovery stok root! I have been falsified successfully , thank you! Now I wonder if I'll do other mods I can use in case of problems with the clean recovery stok ? Thank you.

Sorry, I don't understand what the question is. Are you talking about the flashable zip to disable Xposed in case of errors? As far as I know, it only works in custom recoveries.
The Following 25 Users Say Thank You to rovo89 For This Useful Post: [ View ]
23rd November 2013, 06:56 PM   |  #5613  
Dahnark's Avatar
Member
Thanks Meter: 6
 
58 posts
Join Date:Joined: Jan 2013
Quote:
Originally Posted by rovo89

Thanks, but... there is no FC in the logs. The main logcat would be enough, but it must be taken shortly after the FC, without any reboots in between (because that resets the log). The log is also much shorter than usually, looks like it was reset after booting?


Yes. Preparing some release notes (and dinner, so give me some time ) at the moment for a beta.



Sorry, I don't understand what the question is. Are you talking about the flashable zip to disable Xposed in case of errors? As far as I know, it only works in custom recoveries.

Then today a beta? Great

Enviado desde mi Nexus 5
23rd November 2013, 07:01 PM   |  #5614  
Member
Thanks Meter: 12
 
41 posts
Join Date:Joined: Feb 2013
Quote:
Originally Posted by rovo89

Thanks, but... there is no FC in the logs. The main logcat would be enough, but it must be taken shortly after the FC, without any reboots in between (because that resets the log). The log is also much shorter than usually, looks like it was reset after booting?


Yes. Preparing some release notes (and dinner, so give me some time ) at the moment for a beta.



Sorry, I don't understand what the question is. Are you talking about the flashable zip to disable Xposed in case of errors? As far as I know, it only works in custom recoveries.

Yes that was the question! thanks

Inviato dal mio GT-I9505 con Tapatalk 2
23rd November 2013, 07:03 PM   |  #5615  
Senior Member
Thanks Meter: 48
 
386 posts
Join Date:Joined: Jul 2011
More
Quote:
Originally Posted by rovo89

Could you please post a screenshot? That might make it easier to understand where exactly the error is happening. Did the root confirmation popup appear? Could you try to remove Xposed Installer from the list of allowed apps so it requests root again?


https://drive.google.com/file/d/0BxF...it?usp=sharing
https://drive.google.com/file/d/0BxF...it?usp=sharing
https://drive.google.com/file/d/0BxF...it?usp=sharing

These are the links of the 3 screenshots. There's no popup about SU request by Xposed. Also in Superuser (i have the Clockworkmod one) there are only 4 apps: Link2sd, Greenify, Solid Explorer and Apex Launcher.
The odd thing is that in August I've installed Xposed Framework and used some modules like AppSettings or Xblast without any problem. Now I'm running on the same rom as before, CM9 on Xperia Sola! Have a nice day
Last edited by alexhdkn; 23rd November 2013 at 07:07 PM.
23rd November 2013, 07:52 PM   |  #5616  
nemofbaby2010's Avatar
Senior Member
Flag Detroit, Michigan
Thanks Meter: 162
 
573 posts
Join Date:Joined: Aug 2011
More
Quote:
Originally Posted by alexhdkn

https://drive.google.com/file/d/0BxF...it?usp=sharing
https://drive.google.com/file/d/0BxF...it?usp=sharing
https://drive.google.com/file/d/0BxF...it?usp=sharing

These are the links of the 3 screenshots. There's no popup about SU request by Xposed. Also in Superuser (i have the Clockworkmod one) there are only 4 apps: Link2sd, Greenify, Solid Explorer and Apex Launcher.
The odd thing is that in August I've installed Xposed Framework and used some modules like AppSettings or Xblast without any problem. Now I'm running on the same rom as before, CM9 on Xperia Sola! Have a nice day

Run root checker you may have lost root or run a updated version of superuser.zip. if all just try a reinstall.

Sent from my SPH-L720 using Tapatalk
23rd November 2013, 07:54 PM   |  #5617  
thecrock's Avatar
Junior Member
Flag London
Thanks Meter: 3
 
8 posts
Join Date:Joined: Jul 2008
More
And so it begins.

Sent from my Nexus 4 using Tapatalk 2
The Following 2 Users Say Thank You to thecrock For This Useful Post: [ View ]
23rd November 2013, 07:54 PM   |  #5618  
Senior Member
Thanks Meter: 48
 
386 posts
Join Date:Joined: Jul 2011
More
Quote:
Originally Posted by nemofbaby2010

Run root checker you may have lost root or run a updated version of superuser.zip. if all just try a reinstall.

Sent from my SPH-L720 using Tapatalk

i didn't understand the part with "run a updated version of superuser.zip. if all just try a reinstall." how can i lose root? other apps that require root work fine, like greenify or apex or even solid explorer when i access to /system
23rd November 2013, 08:31 PM   |  #5619  
rovo89's Avatar
OP Senior Recognized Developer
Thanks Meter: 14,508
 
2,376 posts
Join Date:Joined: Jan 2012
More
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/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.

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).
Last edited by rovo89; 1st December 2013 at 07:47 AM.
The Following 642 Users Say Thank You to rovo89 For This Useful Post: [ View ]
23rd November 2013, 08:44 PM   |  #5620  
ahrion's Avatar
Senior Member
Thanks Meter: 245
 
721 posts
Join Date:Joined: Jul 2013
Bravo! @rovo89

Testing now.

Sent from my LG-E980 using Tapatalk

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


Top Threads in Xposed General by ThreadRank