CyanogenMod 12.1These are builds of CyanogenMod 12.1 using JustArchi's repos, modified to support the Xposed Framework.
XPOSED IS NOT INCLUDED, FLASH IT!
Link to Xposed
What's the difference here?
This ROM is DEODEXED, that's the difference. Now, the first boot speed will be slower.
Google says:
Dex file compilation takes more time than dexopt, which can be noticeable when all of a user's apps must be compiled during first boot (after factory reset or after receiving an OTA). To reduce the amount of compilation needed, ART supports the option of pre-optimizing libraries and applications in the system partition. Including the pre-optimized dex files takes space in the system image, so these options trade first boot time for system image size. Enabling WITH_DEXPREOPT causes everything in the system image to be pre-optimized. If this makes the system image too large, additional options can be specified to reduce the amount of pre-optimization.
Click to expand...
Click to collapse
And why Xposed now works?
Xposed for Android 5.1 is on Alpha stage. Therefore, it's unstable and has a lot of problems.
The developer of the unofficial port, romracer, explained:
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.
Click to expand...
Click to collapse
So, a deodexed ROM fixes the problem.
DOWNLOADS
20150829
XDA:DevDB Information
CyanogenMod 12.1 for i9300, ROM for the Samsung Galaxy S III I9300
Contributors
brianelv, JustArchi, Moster2, arter97
Source Code: https://github.com/ArchiDroid
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod 12.1
Version Information
Status: Beta
Created 2015-08-30
Last Updated 2015-08-30
Changelog
2015-08-29
- Initial release
Reserved.
Are these builds just reverting the dlmalloc tweaks?
whatsgood said:
Are these builds just reverting the dlmalloc tweaks?
Click to expand...
Click to collapse
No. Archi changed the ROM from deodexed to odexed. It only affects the first boot (that's the "faster first boot" tweak). It's useless, and breaks the compatibility with Xposed.
So, is same rom with the change "Enable dex-preoptimization" reverted? u update cm sources too?
Im afraid to flash a rom that dont comes from oficial developer, will u test all build on your phone before post here? i dont want to brick my phone.
Thanks from compile and share this build.
galen2 said:
So, is same rom with the change "Enable dex-preoptimization" reverted? u update cm sources too?
Im afraid to flash a rom that dont comes from oficial developer, will u test all build on your phone before post here? i dont want to brick my phone.
Thanks from compile and share this build.
Click to expand...
Click to collapse
Yes, it's the same ROM. I like CyanogenMod 12.1 so I'll update it frequently. And yes, I do tests before posting, with and without Xposed.
brianelv said:
No. Archi changed the ROM from deodexed to odexed. It only affects the first boot (that's the "faster first boot" tweak). It's useless, and breaks the compatibility with Xposed.
Click to expand...
Click to collapse
Why do you spread false information? Dex-preoptimization doesn't affect only first boot and I described why.
JustArchi said:
Why do you spread false information? Dex-preoptimization doesn't affect only first boot and I described why.
Click to expand...
Click to collapse
It's the same, odexed or deodexed. I tested it, and there are no improvements. Besides, odexed roms breaks Xposed. So, what's the problem using a deodexed rom?
Archi, you made a LOT of optimizations, you're the best with this. But odexed roms with Xposed are not compatible. With odex I can't see any difference, and I need Xposed, so I disabled it. Other people needs Xposed too (I think) so I shared it.
brianelv said:
It's the same, odexed or deodexed. I tested it, and there are no improvements. Besides, odexed roms breaks Xposed. So, what's the problem using a deodexed rom?
Archi, you made a LOT of optimizations, you're the best with this. But odexed roms with Xposed are not compatible. With odex I can't see any difference, and I need Xposed, so I disabled it. Other people needs Xposed too (I think) so I shared it.
Click to expand...
Click to collapse
There are no improvements?
Keep using your xposed builds then, you're too ignorant to notice the difference.
brianelv said:
No. Archi changed the ROM from deodexed to odexed. It only affects the first boot (that's the "faster first boot" tweak). It's useless, and breaks the compatibility with Xposed.
Click to expand...
Click to collapse
Brother, Calm down. Don't use so mean words like 'useless' which may not look good to the original developer.
Whatever you are doing is based on the months of hard work done by developers like @JustArchi . Have some respect on their opinions or decisions.
As I said before, many Xposed lovers would appreciate your work which is based on ArchiDroid sources with Xposed support. Just make sure to communicate your thoughts in meaningful good words.
Xposed 5.1 officially released! Now supports odexed roms
I'll update the thread later.
Link of Xposed: http://forum.xda-developers.com/showthread.php?t=3034811
any screenshots ?
Related
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)
arm64 is now officially supported: See here
Old OP
Hello Everyone,
I have successfully compiled Xposed for android 5.1.x for arm64 devices.
I have so far tested this on my Nexus 9 running a custom CyanogenMod based Android 5.1 ROM with SELinux disabled (It may work on ROM's with SELinux enabled but testing has to be conducted.).
Install zip is attached to this post. (The SDK 22 one) This will only install Xposed framework for Android 5.1 for arm64 devices. Please see the original Lollipop post to get the other files you need. (Hint: you only need the Xposed APK from that post.)
I compiled this based off of @romracer's source code for Xposed on Android 5.1.x.
So far I have tested the module Lolistat, It seems to be working well.
Please be patient during boot, let your device boot 10 minutes before reporting that it is "bootlooping"
====================
For Android 5.0.x
I have also compiled Xposed for Android 5.0.x for arm64 devices. I have had mixed results from testers so far. The install zip is also attached to this OP (The SDK 21 one). Many HTC M9 users have reported this caused a boot-loop for them. This will only install Xposed framework for Android 5.0.x for arm64 devices. Please see the original Lollipop post to get the other files you need. (Hint: you only need the Xposed APK from that post.)
Remember to always backup all data before using. Use at your own risk.
Please note: There will most likely be arm64 related bugs with both of these. See this post for more information.
Please be patient during boot, let your device boot for 10 minutes before reporting that it is "bootlooping"
just in case...
I got a new m9 in the box, thinking about waiting to activate it since xposed wouldn't work on it yet.
Sim-X said:
I got a new m9 in the box, thinking about waiting to activate it since xposed wouldn't work on it yet.
Click to expand...
Click to collapse
I could also compile Xposed arm64 for android 5.0 if there is enough interest.
Sim-X said:
I got a new m9 in the box, thinking about waiting to activate it since xposed wouldn't work on it yet.
Click to expand...
Click to collapse
Somebody would need to be willing to test, but I could try to compile Xposed for it.
Well, if you're willing to test and support it, you can post unofficial files for testing...
I have a Nexus 9 with Android 5.0 myself and it's running fairly well. I haven't used any complex modules though.
Be aware that 64-bit ROMs need different handling in a couple of places and break some expectations. For example, initZygote() will be executed twice, as there are two app_processXX processes now. Modules might not expect this. I also didn't succeed to enforce a certain startup order of the processes (app_process64 before app_process32) yet, so results might be a bit random. There are probably more differences like this and it's generally more complex than on 32-bit ROMs. That's why I have only posted files for ARM so far. On the other hand, if you're willing to look into issues that come up (e.g. installation problems, crashes, things that are not working) and do some pre-analysis, that's fine and could bring the project forward. If nothing to major comes up, I can then also include official files with the next version. Additional support would be very welcome anyway.
Framework installation zip attached to OP.
good
Only for 5.1?
auggie246 said:
Only for 5.1?
Click to expand...
Click to collapse
I made a version for android 5.0 but I would need somebody to test it before I release it.
5.0 for samsung galaxy s6 ?
koko115 said:
5.0 for samsung galaxy s6 ?
Click to expand...
Click to collapse
Are you kidding? Move along!
subscribed.
Feel free to post any problems you have with this here. (arm64 related problems)
Rastapop 5.1 on n9 with selinux on. I can install xposed fine but rebooting after enabling YouTube adaway and gravitybox causes a never ending boot logo
YouTube adaway works fine
For me
Guitarboarder28 said:
Rastapop 5.1 on n9 with selinux on. I can install xposed fine but rebooting after enabling YouTube adaway and gravitybox causes a never ending boot logo
Click to expand...
Click to collapse
From my understanding, gravitybox is not compatible with Android 5.1 at all.
joshuabg said:
From my understanding, gravitybox is not compatible with Android 5.1 at all.
Click to expand...
Click to collapse
Ohhh didn't even think about that. Would make sense
Thanks for taking this on, joshuabg. I couldn't believe it when I saw this thread. I thought that 5.1 jumped the arm64 shark and we'd never see xposed for N9.
Anyway, I flashed on AICP 4/6 with FireIce K8.3, SELinux disabled and it booted just fine. Tried the following modules, and I see what rovo meant in his post above. It's really hit or miss with the modules just like the [SUPER ALPHA] xposed for 32 bit arm devices. Thanks again for rolling this out to test.
YouTube Adaway - seemed to work, jumped to dozens of random videos and no ads
Minmin Guard - app opened and seemed to operate normally but I think it may have blocked ads across the board without my telling it to do so. I think it also caused an XDA Free force close on opening that wouldn't go away
Swype Tweaks - caused Swype to FC anytime the keyboard should have launched
Yup my bad. Gravitybox says right in the description it'll cause a boot loop on 5.1. Everything is working perfectly. Thanks!
Can anyone update xposed to work with the new security fixes applied to newer android 4.4.4 builds ?
New fix: Install the apk file found here:
Http://forum.xda-developers.com/showpost.php?p=64063168&postcount=62
edit: old fix:
read the attachment txt file and copy two files from an older build for your device to those folders (/system/lib & (/system/bin)
http://forum.xda-developers.com/showpost.php?p=63864337&postcount=35
@rovo89 : can you update it please?
robuser007 said:
Can anyone update xposed for the new security fixes found in newer android 4.4.4 builds ?
Click to expand...
Click to collapse
Black_Focus_X said:
@rovo89 : can you update it please?
Click to expand...
Click to collapse
What devices and ROMs are you using that have these problems, and what is in the error logs and logcat?
Without this information, no one can help you, not even rovo89 himself.
Also, have you searched the forum to see if others have this issue and what's been learned about it?
It's Samsung Galaxy S3 with Cyanogenmod 11 official! I searched the forum but couldn't find an answer. Maybe my english isn't good enough
My device is Motorola RAZR XT910, with a TI OMAP4 ARMv7-A SoC.
Right now, I am on an Unofficial CyanogenMod 11 (Android 4.4.4) ROM which contains the latest security fixes for the Stagefright vulnerability and was built on November 15. When I try to install Xposed framework, using the latest official stable installer from Xposed Repo, I get an the following error: "Xposed is not (yet) compatible with Android SDK version 19 or your processor architecture (armeabi-v7a)".
When I was on the latest Official CyanogenMod 11 ROM for my device, that was built back on September 1st, Xposed would install and work properly on it, withour any troubles / warnings / errors. Now, I just want to use the latest build that has me protected against Stagefright but I can not install Xposed framework on it at all.
@rovo89 Is there / will there be any fix for this issue?
Having the same problem with the latest build of CM11 (2015.11.15).
unknownsoldierx said:
Having the same problem with the latest build of CM11 (2015.11.15).
Click to expand...
Click to collapse
Same on XT910 on 15.11 CM11 build!
from XT910 or XT925 using Tapatalk
me 2
samsung n5120, just update the new cm11 then show the error message
Yes, i got the same error message when I updated my Redmi 1S to the newest CM11.
I tried to search in MIUI forum but the answer only for MIUI OS.
I tried the patch for my Redmi 1S, it gave me bootloop.
Are there any explanation for this?
Thanks
Same issue here...Redmi 1s..CM 11 4.4.4 ...xposed not working...any solution ??
FYI, I believe this commit is causing the problems:
http://review.cyanogenmod.org/#/c/118800/
Replacing /system/bin/app_process and /system/lib/libandroid_runtime.so from previous CM builds will allow the framework to be installed without problems.
Ok, i'll try
But it can't be a right solution
Well, of course it's meant to be a temporary workaround, until (hopefully) rovo89 will have the time to fix this, if possible. If you heavily rely on Xposed it's better than nothing.
With the link to the commit, I just wanted to help to point out where the problem comes from in order to maybe get a permanent solution.
derf elot said:
Well, of course it's meant to be a temporary workaround, until (hopefully) rovo89 will have the time to fix this, if possible. If you heavily rely on Xposed it's better than nothing.
With the link to the commit, I just wanted to help to point out where the problem comes from in order to maybe get a permanent solution.
Click to expand...
Click to collapse
rovo it's not going to fix anything on kk, it's been done, too old. He's working on M and somewhat supporting L, so no luck with older builds.
Thank you. I tried it and. Yes it works. Xposed working
---------- Post added at 16:36 ---------- Previous post was at 16:34 ----------
ldeveraux said:
rovo it's not going to fix anything on kk, it's been done, too old. He's working on M and somewhat supporting L, so no luck with older builds.
Click to expand...
Click to collapse
Can you look into his head or what?
LG Optimus 4X HD Nightly 15112015 Xposed not working.
View attachment 3544451
Sorry about the pic being in spanish but is my girlfriend phone and i was giving her instructions via skype. It says "Xposed is not (yet) compatible with Android SDK version 19 or your processor architecture (armeabi-v7a)".
derf elot said:
FYI, I believe this commit is causing the problems:
http://review.cyanogenmod.org/#/c/118800/
Replacing /system/bin/app_process and /system/lib/libandroid_runtime.so from previous CM builds will allow the framework to be installed without problems.
Click to expand...
Click to collapse
Can someone make an update.zip for recovery ?
Feel free to try the zip I posted here. Make a backup first. Normally re-flashing your ROM should solve any issues, but you never know.
Xposed dead in latest CM11 *Unofficial* rom
Same thing with cm11 latest release with security patches for stage fright. Although the rom is listed as "Unofficial", it comes from THE Official cm11 OMAP 4 developer. Only listed unofficial because CM has not caught up with the developer. Xposed Framework does not work anymore on Android 4.4.4 See attached screenshots.
Ohmster said:
Same thing with cm11 latest release with security patches for stage fright. Although the rom is listed as "Unofficial", it comes from THE Official cm11 OMAP 4 developer. Only listed unofficial because CM has not caught up with the developer. Xposed Framework does not work anymore on Android 4.4.4 See attached screenshots.
Click to expand...
Click to collapse
You just posted what some other guys posted before you...
And if you would read the thread then you would know there is an update.zip for this problem! With this, Xposed is working without problems!
Are there any major differences between these two firmwares respecitvely are there any specific strengths or weaknesses?
oliman99 said:
Are there any major differences between these two firmwares respecitvely are there any specific strengths or weaknesses?
Click to expand...
Click to collapse
I think it is personal preference tbh, however I prefer SlimLP since I have messed around with custom ROMs for a while and currently run SlimLP on my phone as well. Also I like the customization that comes with SlimLP more than the plainness of ordinary CM.
The SlimLP rom developers don't recommend using xposed due to some ART optimizations. If anyone really wants xposed someone did suggest trying wanams modified xposed version.
rjmxtech said:
I think it is personal preference tbh, however I prefer SlimLP since I have messed around with custom ROMs for a while and currently run SlimLP on my phone as well. Also I like the customization that comes with SlimLP more than the plainness of ordinary CM.
Click to expand...
Click to collapse
I have been considering switching from cm 12.1 to slim lp on my fire. When you say additional customization what does that elude to? Theming and visual, or performance customization?
blueberry.sky said:
The SlimLP rom developers don't recommend using xposed due to some ART optimizations. If anyone really wants xposed someone did suggest trying wanams modified xposed version.
Click to expand...
Click to collapse
I've got xposed on the cm 12.1 rom. Haven't tried yet on SlimLP though.
If you do try it on SlimLP go for wanams xposed. And of course let us know if it you get any problems.
blueberry.sky said:
If you do try it on SlimLP go for wanams xposed. And of course let us know if it you get any problems.
Click to expand...
Click to collapse
I successfully flashed v2.1 of SlimLP, and then I tried v75 and v78 of wanams xposed (preceded with the mandatory installation apk). Both versions led to bootloop; I was able to remove the bootloop by using the uninstallation apk.
Since I want/needed xprivacy I switched to CM12.1 but gapps has stopped working. When there's a new version of SlimLP I might try again.
EDIT: I fixed the gapps in CM12.1 (12/04 built) by (1) doing a factory reset and (2) uninstalling the Playpermissionfix module in xposed. In retrospect I probably could skip (1) and do (2) only. Play store is still slightly wonky but it mostly works, and youtube definitely works 100%.
Damn, it's really a pain that SlimLP doesn't support xposed. I want xprivacy as well.
I just had to uninstall SlimLP and go to CM12.1 because of no support for Xposed from the developers. It's upsetting that with their (or ezio's) modifications that they should want to control something so big rather than let us decide for ourselves.
Because any reasoning such as "it's too big of a security risk" is absolutely ridiculous as it's our choice rather to expose ourselves and at the same time, most people installing modules and Xposed Framework at this point should know what we are installing to by now.
misticalx said:
I just had to uninstall SlimLP and go to CM12.1 because of no support for Xposed from the developers. It's upsetting that with their (or ezio's) modifications that they should want to control something so big rather than let us decide for ourselves.
Because any reasoning such as "it's too big of a security risk" is absolutely ridiculous as it's our choice rather to expose ourselves and at the same time, most people installing modules and Xposed Framework at this point should know what we are installing to by now.
Click to expand...
Click to collapse
The decision to decide for yourself is always in your hands. It is their rom to develop it how they want. If you do not like it, don't use it (as you have indiciated), but don't throw blame on a dev for not including support for something.
***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.