Database Develop

Don't use xposed with lollipop

Hi
As written in title don't use Xposed with lollipop
This is not important but recommended by me
1.I highly, highly recommends you to not use Xposed framework for Lollipop for now, as it overrides our own ART runtime files.
2.Wait for @rovo89 to come up with a better solution, or ROM developers/builders integrate Xposed support for their ROM themselves.
3.I think @rovo89 will update the Xposed Installer later to support ROMs prebuilt with Xposed in-mind.
4.And if you're using a closed-source ROM such as Touchwiz, I'll stay as far as I can with Xposed,as the ART runtime files are closed-source there.
Read this carefully only for lollipop roms!

sameer23 said:
Hi
As written in title don't use Xposed with lollipop
This is not important but recommended by me
1.I highly, highly recommends you to not use Xposed framework for Lollipop for now, as it overrides our own ART runtime files.
2.Wait for @rovo89 to come up with a better solution, or ROM developers/builders integrate Xposed support for their ROM themselves.
3.I think @rovo89 will update the Xposed Installer later to support ROMs prebuilt with Xposed in-mind.
4.And if you're using a closed-source ROM such as Touchwiz, I'll stay as far as I can with Xposed,as the ART runtime files are closed-source there.
Read this carefully only for lollipop roms!
Click to expand...
Click to collapse
Wut? :/

I installed the beta of xposed for Lp, and not all of modules already supported but I highly recommend on xposed.. Check in thread for it.. If your rom is supported, if yes, go and enjoy..

This is must be a joke.. It has to override ART files with xposed implemented codes to work. There's no other way.

sameer23 said:
Hi
As written in title don't use Xposed with lollipop
This is not important but recommended by me
1.I highly, highly recommends you to not use Xposed framework for Lollipop for now, as it overrides our own ART runtime files.
2.Wait for @rovo89 to come up with a better solution, or ROM developers/builders integrate Xposed support for their ROM themselves.
3.I think @rovo89 will update the Xposed Installer later to support ROMs prebuilt with Xposed in-mind.
4.And if you're using a closed-source ROM such as Touchwiz, I'll stay as far as I can with Xposed,as the ART runtime files are closed-source there.
Read this carefully only for lollipop roms!
Click to expand...
Click to collapse
1) Using with Dalvik is not so different, only behavior of Dalvik is changed without change the files.
2) Flash a zip or integrate the same files into a ROM is exactly the same thing.
3) What? This already works, if a developers integrate Xposed in his rom, the users can install only the Installer later.
4) We hope that Samsung didn't change those files.

sameer23 said:
Hi
As written in title don't use Xposed with lollipop
This is not important but recommended by me
1.I highly, highly recommends you to not use Xposed framework for Lollipop for now, as it overrides our own ART runtime files.
2.Wait for @rovo89 to come up with a better solution, or ROM developers/builders integrate Xposed support for their ROM themselves.
3.I think @rovo89 will update the Xposed Installer later to support ROMs prebuilt with Xposed in-mind.
4.And if you're using a closed-source ROM such as Touchwiz, I'll stay as far as I can with Xposed,as the ART runtime files are closed-source there.
Read this carefully only for lollipop roms!
Click to expand...
Click to collapse
1 to 4... Really? For whom did you intend this post? If someone doesn't know the trivia or hadn't read the OP/FAQ and still installed apk he/she/it knows nothing of -> it's their own fault. They bootlooped their samsung device even after Rovo written the red warning? They deserved it.
Everyone! I highly recommend that you don't listen to him (or me, since i too am biased) and think for yourself. If you know how to post logs and have at least basic understanding of android/java - or, at least, understand that any modification made in root may destroy your device/personal data/ whatever (Well, it's an exaggeration, but it's better to be prepared. ) - then help Rovo debug xposed for your device. If you do not - then pls, stop using xposed and posting here.

We waited for it very long time and now you said "sorry, implementation is not good"? Do not use it or create better implementation. When rovo89 had decided for that implementation, he had reasons for it (he wrote them somewhere)

[UNOFFICIAL] Systemless Xposed for Android 5.1/6.0 - v86.1 / 20160928 / SDK22/SDK23

I want to start this post off with a couple of very clear points:
@rovo89 is the creator of the Xposed framework
This is a derivative work posted with his permission
This also means the following statements are true:
I have only worked to bring the Xposed framework to Android 5.1
I have only worked to bring systemless support to Xposed on Android 5.1 and 6.0
I have not rewritten the framework from scratch
With that said, I present to you my first unofficial release of Xposed for Android 5.1/6.0. It is my hope that ultimately my changes can be reviewed and an official release posted. But first, the bugs must be squashed! I've written a few Xposed modules that work fine but by posting this unofficial release, I hope to expand my audience of module writers and testers.
How To Test
You must be on Android 5.1/6.0. It will NOT work on Android 5.0 (too many changes to ART).
You should have a working recovery.
If you left the Xposed app installed from Android 5.0, you should disable all modules before installing this framework. Busted modules may keep you from booting after installation otherwise.
I will need Xposed logs (and possibly logcats) to debug any issues. Remember, if your device won't boot after installation, its likely you can reboot to recovery and still grab the Xposed log (assuming Zygote started). It will be in /data/data/de.robv.android.xposed.installer/log as error.log or error.log.old.
Known Issues
Devices with very little free space on /system may have trouble installing. Systemless installations are recommended if your device is supported. Non-systemless installs should be a last resort.
Downloads
First, I'm going to shamelessly point you to the original Xposed for Lollipop thread. Why? Because I want you to read it. This release hardly differs from that one. And maybe, just maybe, it'll save some unnecessary private messages.
Did you read the original Xposed for Lollipop/Marshmallow thread?
xposed-v??-sdk2?-*.zip - Must be flashed with a custom recovery to install the framework.
xposed-uninstaller-*.zip - Can be flashed with a custom recovery to uninstall the framework.
XposedInstaller_3.0-alpha*.apk - Must be installed to manage installed modules.
Use the correct platform and SDK version for your device. Google your device or look in build.prop if you're not sure.
Can't find some of the downloads? Surprise! They're in the original Xposed for Lollipop thread. They're unchanged, so there's no need to post them here too.
Module Developers
It would be incredibly useful to me for people to test the framework in the smallest "units" possible at first. By "unit" I mean things such as "resource replacement", "method replacement", "before method hooks", "after method hooks", etc. It doesn't do me a lot of good to know that some huge, complicated module causes system_server to crash without understanding at what level that's happening. This is actually what held me back from releasing. I have some test modules to use, but I don't have infinite time to write test modules, test the framework, etc.
For discussions, please use this thread or another matching one in this subforum. For historical discussion, please search this thread.
Downloads available here:
Download Here
.

Changelog
20160928
suhide compatibility. See this post for details.
20160709
Updated to v86. See @rovo89's post here for details.
Experimental - Systemless bug fixes for devices that can't mount /data in recovery.
Experimental - Systemless builds for Android 5.1 (SDK22).
NOTE - You must use the installer in post #1 or the Material Design Xposed installer if you use systemless Xposed. The default installer will not detect /xposed/xposed.prop.
20160620
Updated to v85. See @rovo89's post here for details.
Experimental - Systemless bug fixes for devices that can't mount /data in recovery.
June 20th - Experimental - Systemless builds for Android 5.1 (SDK22). No changes to SDK23.
NOTE - You must use the installer in post #1 or the Material Design Xposed installer if you use systemless Xposed. The default installer will not detect /xposed/xposed.prop.
20160617
Updated to v85. See @rovo89's post here for details.
Experimental - Systemless support for SDK23 (Android 6.0). This should work similar to @topjohnwu's though there are some significant differences. The uninstaller has not been updated yet.
NOTE - You must use the installer in post #1 or the Material Design Xposed installer if you use systemless Xposed. The default installer will not detect /xposed/xposed.prop.
20150911 - Never Forget.
Updated to v74. See @rovo89's post here for details.
If the official release works for you, there is no need to install this version, unless you want to test LZMA2 compression.
Experimental - Use LZMA2 compression for our backups. If you get errors while trying to install Xposed, this may help.
Experimental - Uninstaller supports LZMA2 compressed backups. Its also backward compatible with official and my previous unofficial releases.
20150816
Disable resource hooking in Sygic
Disable fast access to TypedArray subclasses
Ensure system content providers are compiled before they are needed
See @rovo89's post here for details.
20150808
Merge @rovo89's changes from upstream to support LG encrypted odex files. See his post here for details.
I do not have an LG phone to test. Please report back any problems. Be sure to clear dalvik cache after installing!
20150804
Merge @rovo89's changes from upstream to support LG encrypted apps. See his post here for details.
I do not have an LG phone to test. Please report back any problems. Be sure to clear dalvik cache after installing!
20150727
Include @rovo89's changes from upstream. See his post here for details.
20150716
Include @rovo89's changes from upstream. There are no changes to the framework. If previous versions installed fine, then there is no need to update to this version unless you just really want to.
20150702
Updated installer and bundled busybox. Should resolve issues with mounting /system during install in some cases and incorrectly detecting recovery's value for ro.build.version.sdk instead of the system's.
20150701
Updated installer and uninstaller again. Installer is now less complex but still works on devices with low /system space. If you had no problems installing previous releases, then there's no need to update to this version. Uninstaller is backward compatible. See this commit for details.
20150630
Updated installer and uninstaller. Installer is now a bit more intelligent in creating your backups. Uninstaller is backward compatible. If you had no problems installing 20150629, then there's no need to update to this version. See this commit for details.
20150629
Update to v65 from @rovo89
Note: If the Xposed installer app (not zip) indicates the framework is not installed, then make sure you are using alpha4 of the installer app. This is a bug in alpha3 of the installer app.
20150514
Updated to include @C3C076's commits here. Buy the man a beer!
For details, see commits #1 and #2.
FAQ
Unofficial FAQ maintained by the community is available here
Miscellaneous
Working and non-working modules can be found here. This is not an official list. Your mileage may vary.
If you get "low space warnings" after installation, make sure you wiped Dalvik cache in recovery. If they persist, your ROM may have modified build.prop. See this post for one way on how to fix it. This seems most common with Chroma ROMs.
If your ROM gzip's (compresses) the .odex files in /system, then Xposed will not work and you will bootloop. This is due to patchoat handling the gzipped odex files, but not correctly patching them for Xposed. This causes Xposed to trigger continuous re-dexopt'ing of the compressed odex file.

Awesome! Been waiting for this since you announced on Github! Thanks so much for bringing it public!
Edit: apologies, got a little ahead of myself when I saw the first post in discussion deleted, missed the end of this post in my excitement.

This is incredible! Thank you
Sent from my Nexus 5 using Tapatalk

Wrong footer and signature verification failed. How do I fix this?
I'm on CM12.1 Unofficial, XT 1033
EDIT: Flashed another recovery (TWRP) and it worked.

Thank you soooooo much, for your hard work!!

Bootloop after installing gravitybox [LP]......My wrong , i forgot to make a NANdroid. I'll check it out again with a Nandroid backup.

Works good on my Nexus 5, but not all the modules. For example RootCloak working but after installing GravityBox I'm getting bootloop...
Just thought I share it, to save some tome to others.
BTW... All worked fine for me on 5.0.1

dmatik said:
Works good on my Nexus 5, but not all the modules. For example RootCloak working but after installing GravityBox I'm getting bootloop...
Just thought I share it, to save some tome to others.
BTW... All worked fine for me on 5.0.1
Click to expand...
Click to collapse
Same here with gravity box and it seems with CpuTemp in status bar

Nice job would test it asap

Great work! MinMinGuard is working like a charm with this!

blackzigong said:
Great work! MinMinGuard is working like a charm with this!
Click to expand...
Click to collapse
Is busybox working?

So this may seem like a stupid question but where do we download the xposed-installer-alpha from? Original xposed thread alpha-2??
EDIT: All good, original thread it is

Bootloop on my Nexus 5

Can this thread be locked & use this one forum.xda-developers.com/xposed/discussion-xposed-android-5-1-t3072982 instead?

Has anybody tried Amplify if it's working ???
Powered by ET!

Thanks for your effort

advanced power menu is working fine
nexus 5 stock thanks

- Lolistat - Not working
- Youtube Adaway - Not working
- OGXposes (To login with ogyoutube) - Not working
- AcDisplay - Not working
- Advanced power menu - Working

Does greenify work?

{Op3}(Unofficial) Xposed for Nougat SDK25(7.1.1) based ROMs

***For those users who are Unaware***
The PurifyOS Team have slightly modified the Xposed Nougat source of @ABForce and XposedTool of Rovo collector to allow the creation of rapid zips to install Xposed on Nougat
Flash installer.zip via TWRP/Custom Recovery
If any problems/bootloops flash uninstaller.
Only flash on SDK 25
Might work on custom roms
Enjoy Xposed on op3
xXXXXx Unstable xXXXXx
Download: (Use Files in attachments for no confusion)
http://xposed.purifyos.it
(For now don't use magisk module contain in magisk folder!!!)
Source:
https://forum.xda-developers.com/xposed/xposed-android-nougat-sdk-25-arm64-t3639221
Git:
https://github.com/abforce/xposed_art_n

You should also mention cons, that it's unstable and not 100% working.

Is amplify working?

SpartaKurd said:
Is amplify working?
Click to expand...
Click to collapse
According to some users, Amplify starts running but after sometime stops collecting stats.

tnsmani said:
According to some users, Amplify starts running but after sometime stops collecting stats.
Click to expand...
Click to collapse
Thanks mate. I hope a stable version will be released before Android O

Just wanting to link this here. @rovo89 specifically talks about why this method is dangerous - i.e. flashing "Xposed for Nougat" on an already existing ROM.
The best way is to wait for a ROM developer to compile the patch by abforce directly into AOSP, then build on that. This method will be very unstable, most modules won't work, etc.

it was too beautiful to be true, xposed kept me from upgrading to N for a long time, i can wait some time for rovo's stable release
Sent From the Grey Stuff Inside My Skull

This bricked OP3 with Resurrection Rom 5.4.8

Have anyone succeeded with Magisk Hide and systemless xposed? Share your ROM details.

Show what modules you have

I think it's a good idea to share the magisk's modules we have installed.
-mi A1 gcam
-youtube vanced

Google lens enabler
Google sans mod font
HAL3 enabler
iOS11.1 emoji
Unified hosts adblock
YouTube vanced

Android O APT-X libraries: Android Oreo officially supports APT-X bluetooth audio, however not all phones have the needed library files. This module simply places the missing APT-X(HD) and LDAC files in your system if you don't already have it. Enjoy better bluetooth audio!
Busybox for Android NDK: As a byproduct of building my own static busybox compiles in all supported Android architectures for my AIK-mobile package I figured I might as well offer them up separately as well since there weren't any providers making Android x64 builds when I was researching. The installer detects what architecture (ARM/ARM64, x86/x86_64, MIPS/MIPS64) your device uses and installs the correct busybox binary accordingly. It then cleans up any symlinks from a possible previous installation in the same directory and generates new symlinks directly from the output of the installed binary. Detects and supports "systemless" root via SuperSU/Magisk installation as well.
Systemless Xposed: This is a port of rovo89's Xposed framework to work systemless-ly through Magisk.
SDK 27 (Android 8.1)

AirAudio - stream your music!
Android O APT-X libraries
Audio Compatibility Patch
Mi Mix 2 Snapchat Volume Fix
Unified Hosts Adblock
ViPER4Android FX Materialized

Magic Charging Switch (mcs)

kremmit said:
Android O APT-X libraries: Android Oreo officially supports APT-X bluetooth audio, however not all phones have the needed library files. This module simply places the missing APT-X(HD) and LDAC files in your system if you don't already have it. Enjoy better bluetooth audio!
Busybox for Android NDK: As a byproduct of building my own static busybox compiles in all supported Android architectures for my AIK-mobile package I figured I might as well offer them up separately as well since there weren't any providers making Android x64 builds when I was researching. The installer detects what architecture (ARM/ARM64, x86/x86_64, MIPS/MIPS64) your device uses and installs the correct busybox binary accordingly. It then cleans up any symlinks from a possible previous installation in the same directory and generates new symlinks directly from the output of the installed binary. Detects and supports "systemless" root via SuperSU/Magisk installation as well.
Systemless Xposed: This is a port of rovo89's Xposed framework to work systemless-ly through Magisk.
SDK 27 (Android 8.1)
Click to expand...
Click to collapse
Did you installed Xposed on MIUI?

Adriano-A3 said:
Did you installed Xposed on MIUI?
Click to expand...
Click to collapse
No I haven't anymore. But at the time of writing i had and it was working.
Why do you ask?

kremmit said:
No I haven't anymore. But at the time of writing i had and it was working.
Why do you ask?
Click to expand...
Click to collapse
I'm going to install it on MIUI 9.5.8.

Adriano-A3 said:
I'm going to install it on MIUI 9.5.8.
Click to expand...
Click to collapse
I'm on RR rom and it worked ok.

Adriano-A3 said:
I'm going to install it on MIUI 9.5.8.
Click to expand...
Click to collapse
Did it work for you? I'm still on 9.1 because I need Xposed.

kurtextrem said:
Did it work for you? I'm still on 9.1 because I need Xposed.
Click to expand...
Click to collapse
I didn't try. I sold my Mix 2.

Xposed for Oreo and Pie - Edxpoed

EdXposed
A Riru module trying to provide a ART hooking framework (mainly for Android Pie) which delivers consistent APIs with the OG Xposed, leveraging YAHFA hooking framework.
https://github.com/ElderDrivers/EdXposed
Credits
YAHFA: the core java hooking framework
Riru: provides a way to inject codes into zygote process
XposedBridge: the OG xposed framework APIs
dexmaker and dalvikdx: dynamiclly generate YAHFA hooker classes
Whale: used for inline hooking
Known issues
resources hooking is not supported yet
may not be compatible with all ART devices
only a few Xposed modules has been tested for working
file access services are not implemented yet, now simply use magiskpolicy to enable needed SELinux policies
Build requirements
same as Riru-Core's and zip binaries can be downloaded from here
Build
run :Bridge:makeAndCopyRelease in Gradle window to build edxposed.dex
run :Core:zipRelease to build Magisk Riru module flashable zip file
find the flashable under Core/release/
flash the zip in recovery mode or in Magisk Manager
Install
make sure Magisk v17.0 or higher is installed.
download Riru-core v10 or higher and install it in Magisk Manager or recovery.
download EdXposed and install it in Magisk Manager or recovery.
Install companion application(s)
reboot.
have fun
Companion applications
for v0.2.9.5 and before: Xposed Installer
for v0.2.9.6 and v0.2.9.7: Xposed Installer and EdXp Manager(optional)
for v0.2.9.8 and later: EdXposed Installer
Get help
Forum (recommend): Android Forum
GitHub issues (recommend): Issues
For Users using QQ, QQ Group: 855219808
Telegream: Code_of_MeowCat
Discord: Code_of_MeowCat
Contribute
Apparently this framework is far from stable and all kinds of PRs are welcome.

The main EdXposed XDA thread is here:
https://forum.xda-developers.com/xposed/android-9-0-xposed-solutions-t3889513
Nevertheless, this start post is more informative than the original one.

Is it Xposed replacement for oero/pie?
Sent from my Motorola Moto G (5S) Plus using XDA Labs

QkiZMR said:
Is it Xposed replacement for oero/pie?
Click to expand...
Click to collapse
Is the only Pie compatible version, and also looks like to work on Oreo.
I have a Google Pixel and I can confirm it's working on Pie, a lot of modules works, so far so good.

I started testing it today, on Oreo and I would say that is working stable for now. Some time ago after installing Xposed on my phone, I noticed that Xposed causing that system and application are running little slower than without Xposed. But capabilities that Xposed is giving to me are more important, so I can live with it. Now after installing EdXposed I didn't noticed any impact on system performance.
Sent from Moto G (5S) Plus via Tapatalk

Worked at first and I was able to install fake gapps because I wanted microg, but it stopped working after that. I do have microg working now, but I can't add any more xposed modules as it shows inactive. I read somewhere that it works after a soft reboot, will try that next.