[Xposed General] Programming4life:
This has been fixed xda post​

Note: This is a temporary solution until someone fixes this in Xposed. Also I use my module "SnapColors" as a example throughout this post but this fix should for work any module. I've tested it with other modules and it works. If the module did not previously work on 5.0 then ignore this post and continue on with life.

TL;DR Version:

I found a temporary solution of getting modules to work on 5.1 for modules that worked on 5.0 but don't work on 5.1.

Non-TL;DR Version: Backstory and how I found his temporary solution

So a couple days ago I decided to start working on bring my module(s) to Xposed running on 5.1. In doing so what I noticed with a lot of the modules they seem to crash the app without throwing any kind of error whatsoever. Take for example one of my modules "SnapColors", if SnapColors was enabled in Xposed Installer SnapChat would always crash without throwing any error it wouldn't even say anything along the lines of "process has stopped unexpectedly" it would just close the app. So because of this behavior it led me to believe something was wrong with Xposed and not with my module(s). So I went thought what could be broken in Xposed thats causing this because 5.0 is just one up to 5.1 so the changes couldn't be that big. I went though the things that could cause this and came across "dalvik-cache" I remember reading somewhere Xposed makes some changes to the cache file (.dex) thats created during the creation of dalvik-cache files. So then I thought what if in 5.1 a small change was made to the process of making the dalvik cache files and thats what is causing the problem. So I decided to delete the dalvik cache file for SnapChat which is what my module was hooking into, then I tried opening SnapChat again but it crashed so I tried opening it again and what do you know it opened without any problems with my module fully working without any problems. The fix was kind of a guess too.

The fix/Solution

Note: If you reboot your device you have to do the fix again. Also you are deleting the dalvik cache so you won't benefit from it any more for the app(s) you delete it for. Unless you reboot then everything gets reverted.

What you have to do is delete the dalvik cache file for the app the module is for.

Example: SnapColors a module for SnapChat, so we have to delete the dalvik cache file for SnapChat.

What you need:

1) A file manager with root access, or terminal knowledge.

2) Package name example for SnapChat its "com.snapchat.android". How to get the package name look below theres a how to.

Steps for deleting the cache file:

Make sure the app is not running in the background close it if it is.

Method 1) Via terminal command:

cd /data/dalvik-cache/arm/ && rm data@app@"package name here without the quotes"*

Example command for SnapChat would be don't forget the "*" at the end:

cd /data/dalvik-cache/arm/ && rm data@app@com.snapchat.android*

Method 2) Via file manager: Navigate to /data/dalvik-cache/arm/ look for a file

starting with

the name data@app@"package name here without the quotes".apk delete this file and thats it.

Now try and open the app if it doesn't work close the app then try opening it again. make sure that apps not running in the background before trying again.

Getting package name

Via terminal command:

ls /data/data/ | grep "the app name here without quotes"

Via app: Install https://play.google.com/store/apps/details?id=com.electricsheep.asi

Open it-> Apps tab-> Tap the app-> look for "Package name:" should be the first thing.