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

[huytrang90]

@huytrang90, @xzaxox, @heatseeker_x04, @Publiuss, @culson_35 and others who saw the "segmentation fault":
Could you please try the attached versions? static1 will very likely work, but please also test the other one. Just install the app and press "install/update", no need to test any modules. I might add more versions to try later.

Since I am already on 2.3, when I installed and try out either of your static1 or 2, they all work.

Do you want me to go back to 2.2 to try?

 

[sixth.pr1m3]

Since I am already on 2.3, when I installed and try out either of your static1 or 2, they all work.

Do you want me to go back to 2.2 to try?

I tried, static2 not working. static1 works

 

[rovo89]

Are all modules compatible with Xposed 2.3 AND miui(I know it's a beta, I wanna know if them theorically work with miui)?
I must install only Xposed framework?

Not all modules. There are some which are for example made especially for Touchwiz (Samsung) or Sense (HTC) or for vendor-/ROM-specific features. But the generic modules (e.g. App Settings) should usually work.

The only module that doesn't seem to work for me is unicon

Again, please report it to the module author, it might be a check that looks for /data/xposed or so. I can't say much about modules, especially if I don't have their source code.

 

[rovo89]

Since I am already on 2.3, when I installed and try out either of your static1 or 2, they all work.

Do you want me to go back to 2.2 to try?

Ah, sorry. I wanted to ping @mflova instead.

I tried, static2 not working. static1 works

Thanks... Could you (or anyone with the same issues) send me the following files from your ROM? It would help if you could reproduce it myself.
/system/bin/linker
/system/lib/libc.so
/system/lib/libcutils.so
/system/lib/libm.so

 

[tamirda]

This is Xposed version 2.3.Most notably, this brings Xposed to users who weren't able to use it before:

• added x86 support (thanks to @Tungstwenty for the help!)
• should work with SELinux / SEAndroid / Knox
• should be compatible with both JIT and non-JIT ROMs (almost all ROMs for ARM processors are JIT-enabled)
• experimental, but full MIUI support (before you ask: yes, this is my own code, not a contribution from a fork)

But there are also some new features/fixes:

• context menu in the modules list (for app info, support link, uninstall etc.)
• hopefully fixed incompatibilities with a few ICS ROMs
• workaround for a Paranoid lockscreen bug (appeared only under certain circumstances)
• better error output if app_process is not compatible (that "Xposed is not (yet) compatible with Android SDK version ..." message)
• several UI and navigation fixes

Some words about internal changes:

• /data/xposed not longer exists, those files are now stored in the standard folder /data/data/de.robv.android.xposed.installer
• This means you need to enable your modules again for this update
• The flashable zip to uninstall Xposed in case of bootloops has changed and should work for ARM and x86 now - if a few of you could test it (especially with TWRP), that would be great. It is written to the SD card automatically (Xposed-Disabler-Recovery.zip). After it's flashed, the framework section should display that app_process is not installed.
• The "cleanup" button is no longer needed. The "uninstall" button restores the original app_process binary. Uninstalling the Xposed Installer from Settings => Apps removes everything else.

And finally, for developers:
There is one new method findMethodsByExactParameters() that you can use if you don't know the method name but the parameter types (and optionally the return type). If you want to use it, use the new API from the first post and bump your minimum Xposed version to 36.


Download is available via the builtin updater (wait until it appears or hit the refresh button) or at http://dl.xposed.info/latest.apk.

I knew you can solve this SElinux problem
Thank you very much my friend and keep the hard work!

 

[defiant07]

@rovo89,

I encountered the seg fault errors too. See signature for rom details; also note I am using SuperSu.

static1 works ; static2 does NOT work (I get the same seg fault errors) .

Attached the requested files in a zip. Hope they help; lmk if I can provide further information.

 

[xzaxox]

Also here static1 working but static2 not and using supersu.

 

[CoolApps]

2.3 is Broken, do not update yet until further notice.
I got seg fault errors on my Sony Tablet S which broke the WiFi radio partially.
Restoring to 2.2 fixed it.
On my Nexus 4 it broke mobile data but then after after 2 reboots after the framework installation Gapps forced close and then mobile data started to work again, strange bug but 2.3 is working fine on my Nexus 4 now.

Here is the video of my Sony Tablet S which is having issues with the latest version: https://www.youtube.com/watch?v=H2O-Z9XBotc
Really though I don't see why this would touch and temporarily brake the radio.

Sent from my Nexus 4 using XDA Premium 4 mobile app

 

[rovo89]

@rovo89,

I encountered the seg fault errors too. See signature for rom details; also note I am using SuperSu.

static1 works ; static2 does NOT work (I get the same seg fault errors) .

Attached the requested files in a zip. Hope they help; lmk if I can provide further information.

Thanks. The files didn't work properly on my phone, but ok... I guess I have to revert back to the statically linked BusyBox, at least on ARM processors. The x86 version is much bigger and at the moment it is unclear whether there are x86 ROMs with an incompatible linker as well.

2.3 is Broken, do not update!
I got seg fault errors on my Sony Tablet S which broke the WiFi radio partially.
Restoring to 2.2 fixed it.
On my Nexus 4 it broke mobile data but then after after 2 reboots after the framework installation Gapps forced close and then mobile data started to work again, strange bug but 2.3 is working fine on my Nexus 4 now.

Too be honest, that sounds very weird. Yes, the segfaults are known (see most of the posts above), but I can't imagine either how this could have any effect at all, except that modules might no longer work because the framework is only half installed. Anyway, I'm looking for a solution at this moment.
Same for mobile data, especially as it seems that these were only temporary effects. Did you do a full reboot after installing?

From my point of view, nothing speaks against trying version 2.3 unless more people report similar issues.

 

[CoolApps]

Thanks. The files didn't work properly on my phone, but ok... I guess I have to revert back to the statically linked BusyBox, at least on ARM processors. The x86 version is much bigger and at the moment it is unclear whether there are x86 ROMs with an incompatible linker as well.



Too be honest, that sounds very weird. Yes, the segfaults are known (see most of the posts above), but I can't imagine either how this could have any effect at all, except that modules might no longer work because the framework is only half installed. Anyway, I'm looking for a solution at this moment.
Same for mobile data, especially as it seems that these were only temporary effects. Did you do a full reboot after installing?

From my point of view, nothing speaks against trying version 2.3 unless more people report similar issues.

It took two reboots after installing the framework to get Gapps to crash and fix the mobile data.
I am not sure if Gapps was having a conflict with the OS and framework but that should not happen that's for sure.

Sent from my Nexus 4 using XDA Premium 4 mobile app

 

[mbze430]

I have 2.3 running on my SGS3 on PA3+.... it's "running" but I am getting weird problems here and there most notiably with Android Tuner which uses the Xposed framework.

I also have 2.3 installed on my Galaxy Note 8.0 running CM10.2... and that is completely breaking it. It's always stuck on boot logo(when I enable any modules). Going to reinstall 2.2

 

[rovo89]

It took two reboots after installing the framework to get Gapps to crash and fix the mobile data.
I am not sure if Gapps was having a conflict with the OS and framework but that should not happen that's for sure.

Is that reproducable? If you go back to 2.2, reboot and install 2.3 again, do the same issues appear again (on your Nexus)? Maybe you just had bad luck and the phone rebooted in an unfortunate moment. Version 2.3 has been downloaded 18,000 times in the first ~24 hours and this is the first report about such issues, that's why I think it's far to early for a "don't install" warning.

 

[rovo89]

I have 2.3 running on my SGS3 on PA3+.... it's "running" but I am getting weird problems here and there most notiably with Android Tuner which uses the Xposed framework.

I also have 2.3 installed on my Galaxy Note 8.0 running CM10.2... and that is completely breaking it. It's always stuck on boot logo. Going to reinstall 2.2

Do those PA issues also occur if you have no modules installed? And could you please describe exactly what problems you notice?

Regarding CM10.2: That's what I run to. Before going back to 2.2, could you please grab a logcat (adb logcat -d > logcat.txt) to give me a chance to analyze and fix the errors?

 

[CoolApps]

Is that reproducable? If you go back to 2.2, reboot and install 2.3 again, do the same issues appear again (on your Nexus)? Maybe you just had bad luck and the phone rebooted in an unfortunate moment. Version 2.3 has been downloaded 18,000 times in the first ~24 hours and this is the first report about such issues, that's why I think it's far to early for a "don't install" warning.

I will try but still it did break WiFi in a way on the STS.

Sent from my Nexus 4 using XDA Premium 4 mobile app

 

[rovo89]

Xposed 2.3.1

I have just uploaded a minor update (version 2.3.1) to the repository:
- Fixed "Segmentation fault" error during installation on some ROMs
- A few translation updates
If version 2.3 is working fine for you, there is no need to update.

 

[bdorr1105]

I have just uploaded a minor update (version 2.3.1) to the repository:
- Fixed "Segmentation fault" error during installation on some ROMs
- A few translation updates
If version 2.3 is working fine for you, there is no need to update.

is the same version over in the TMO note 3 section or should I use the beta in the TMO section

 

[CoolApps]

I have just uploaded a minor update (version 2.3.1) to the repository:
- Fixed "Segmentation fault" error during installation on some ROMs
- A few translation updates
If version 2.3 is working fine for you, there is no need to update.

The Seg Fault error is now gone, has for the mobile data bug now after installing the latest version after installing the framework and one reboot Gapps force closes then fixes the mobile data (it force closes a few seconds now, I am currently looking at it).
Anyway while using the reboot button I noticed many crashes and then a reboot which means that it is doing something before rebooting, what is it doing before rebooting really?
EDIT: According to the logcat Google Cloud Messaging failed to start it's init service, most likely to do with Greenify, maybe it is causing the bars to grey out or something, it does say that there was not internet connection since then so this is just confusing.

Sent from my Nexus 4 using XDA Premium 4 mobile app

 

[eduardo_b]

Well, 2.3 installed without issue and all modules seem to be functioning without problem, so the BusyBox issue is apparently dependent on specific models. I have two GS3s, and they are fine. Haven't updated GS1 or two tablets (Nexus 7, STab2 7) yet.

 

[rovo89]

is the same version over in the TMO note 3 section or should I use the beta in the TMO section

This thread (and http://repo.xposed.info/module/de.robv.android.xposed.installer) is the one and only true source. You might find copies somewhere else, but copies become outdated. There was a 2.3 beta1 version, but you shouldn't be using it any longer.

The Seg Fault error is now gone, has for the mobile data bug now after installing the latest version after installing the framework and one reboot Gapps force closes then fixes the mobile data.
Anyway while using the reboot button I noticed many crashes and then a reboot which means that it is doing something before rebooting, what is it doing before rebooting really?

Soft reboot restarts the Java stack and one process that is responsible for rendering. Several other services stay up, which is why this is the fastest method.
Reboot sends the "reboot" OS level command, which usually resets the phone immediately and without giving applications and services the chance to end properly. That's why I mentioned you might have just hit a bad moment.
The reboot command in your power menu seems to give the system a few seconds to prepare for shutdown, so this is the safest way to restart.

As you mentioned that the Gapps force close is reproducable, could you please get me a logcat shortly afterwards? Would be interesting to see why it crashes and if the logcat mentions anything about mobile data.
Speaking about that, is the data connection really completely lost? Or is the icon just not blue any longer? As far as I know, Google Services test the connection to some Google servers and that is how the system decides whether the icon should be blue or not. That would at least be a connection to the crash.
EDIT: Just saw your EDIT I forget to mention it from time to time, but you should try if the bug also occurs if you have no modules activated. If it's a module issue, I can search very hard for the cause and won't find it.

 

[boggdy]

Can you attach the content of /data/data/de.robv.android.xposed.installer/log/debug.log please? That will show whether Xposed starts up correctly.

I tried and tried to find that file/folder. Is it any specific location I have to look for it? Should it be on the Root partition, Internal memory or SD Card? I checked on all three locations, but it was not there. I can send you some screenshots, if it makes it easier.