[Xposed General] faslane:
UPDATE from [MENTION=4419114]rovo89[/MENTION] (2-19-2015 am)

http://xdaforums.com/showthread.php?t=3034811

He's [MENTION=4419114]rovo89[/MENTION] working on a TON of stuff and is aware of the issues some are having. Give him a break, he's busy with "life" and other things until this following Monday (per his post today) so let the man have a life. We're all anxious but this stuff takes time so let him do do. It WILL come. If you NEEEEEED Xposed form Lollipop ad it's not working (or is working and you just don't think it's working, that's on you. Please be patient) and restore a nandroid until and update is released. Do NOT ask when updates are coming and when "xyz device/rom" will be compatible. Do you honestly think he's unaware that EVERYONE (basically) want's his tool? Let him breathe and it'll come when it comes. Flooding the posts with these types of questions doesn't tell him work faster and only creates drama and bantering. Please knock it off. ONLY he knows as he fixes and perfects his tool for the masses.

In the meantime if the instructions below don't work for you simply restore your nandroid which I' POSITIVE you made right? And flash it back and wait until an update is pushed that fixes your issue.

Again, here are the steps MANY have taken and succeeded at including myself.

MAKE a NANDROID before ANYTHING>

If you don't know how (you shouldn't be here whatsoever to begin with) and then calm down, READ TWICE so you understand and especially read the ORIGINAL POST located and the beginning of this thread and make sure you understand what works (even the stuff that has known issues that STILL works...... If you have a question about it, READ the forums, MANY (and probably 99.9% of people) have it actually working and don' realize it because the see the red text and assume it's not installed. THIS is a message of a KNOWN bug....read it again...and then probably again....

Here are the instructions and some information that may or may not apply to you. Most of it probably DOES.

Faslane

Again peeps, you PROBABLY have it working and don't realize it.

This will NOT work on TW Lollipop roms as stated in post 1 from the DEV.

This might vary a bit from your device but should solve/answer MANY people's issues of it "not working"

Download both the arm.zip file

1) Install the APK

2) Install SELinuxModeChanger from play store unless your rom is already set to permissive.

3) Start SELinuxModeChanger and switch to permissive.

4) Flash the framework through recovery (CWM, TWRP etc)

5) Start the xposed GUI. It will show that the framework is not installed in RED.

Select the soft reboot option in the xposed GUI, accept SU access if it asks (you might not see this if SuperSU it set to grant by default) and wait for the reboot to finish.

6) Start the xposed GUI.

It might STILL show it's manual activation error in red but could very well be working. Mine shows this and works fine.

Download a module you KNOW works....NOT GravityBox, NOT greenify (they're both broken) I use xgels which enhances google launcher and it works perfectly. Try this just for fun and to test if Xposed is working.

I'd say 99.99% of peeps stating it's "not working" aren't doing the soft reboot inside Xposed at the framework tab because they see the red text regarding the activation and just assume it's not working. It Probably is working. Mine does the same exact thing

you WILL need to do a soft reboot in Xposed after installing a module and ticking activation each time (mileage wil vary)

Once you've tried ALL of these steps, THEN post what's not working for you.

Fas

Quote from [MENTION=4419114]rovo89[/MENTION] :

Current status (Feb 19):

The most important issue seems to be the incompatibility with Samsung stock ROMs, especially because it's leading to boot loops. I have been working hard on fixing this in the days since the release, however it's not just a single spot that needs fixing. Thanks to GermainZ for testing and providing good log files! So far, I have detected the following issues:

- Enhanced .oat file format: Samsung has added a "TypeLookupTable", probably for performance reasons. The table itself will be ignored by Xposed, but it also means that the file format is slightly different. I have finally understood what they have done and added some logic to skip the referenes to this table.

- Different size of the String class: They have added a clear() method, which is unusual as strings are usually immutable. As this class is one of few that have special support in native code, I had to add one entry to the virtual table of the class.

- Additional fields in DexCache class: Offsets to some fields are different due to this and need to be handled in native code (as this another central class with native parts directly implemented in ART).

- Verifier rejects ViewDebug class: Doesn't seem to be overly critical to me, yet to be tested whether it's working fine with original libraries.

- Implementation missing for some native methods: Some methods in the reflection classes have been implemented in native code instead of Java. This means I will have to implement them as well.

The changes done by Samsung are bigger than I expected, especially given that ART is very complex and mostly undocumented. Anyway, I still think that once these issues have been overcome, it's better to replace the libaries than trying to manipulate data structures and behavior from "outside" (app_process). Think about it: If they have done such big changes, it's very likely that offsets in these data structures are different from AOSP and would need special handling as well.

It would of course be helpful to have an uninstaller ZIP in case you run into a bootloop. I didn't have time for that yet, but maybe someone can build an initial version that basically reverses the steps of the installer ZIP. For the ART libraries, that should be rather easy. You might want to stay away from moving app_process32 back in case you have SuperSU installed. It will need a special procedure to ensure you don't break either part or even your ROM.

There are other issues for sure, for example it seems that some methods cannot be hooked. That's something that needs more investigation, but I would like to fix the more critical issue like the ones for Samsung first.

That said, I won't be able to work on Xposed for the next days, definitely not before Monday. Keep in mind that this isn't my fulltime job and that an alpha phase might take some time. It would be illusionary to assume that we reach a stable state after a few days, with all the changes that have been done.[/QUOTE]