/* Intro */
3 months after the first functional Xposed for Lollipop by @rovo89 was introduced,
now here comes *somewhat* functional Xposed for Samsung Lollipop firmware.
Embrace yourself.
/* Technical background */
Why were Samsung users left out of the Xposed party?
Because Samsung has massively customized ART runtime included in their firmwares compared to AOSP.
And plus, because the system partition has so little space left, they have additionally implemented xz decompression on top of ART.
Those 2 main reasons has differentiated Samsung's ART from the rest of the ROM's ART.
More technical information on post 2.
/* Disclaimer */
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this project
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
/* Prerequisite */
Due to my skills limitation, only deodex'ed ROMs are supported for now.
For more explanations, checkout post 2.
/* Supported firmwares */
Every ARMv7(32-bit) Samsung Lollipop Android 5.0 deodex'ed firmware should work.
But please note that I have tested this only on Galaxy S4, Note 3 and S5.
For 64-bit, please check http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960 by @wanam
For 32-bit on Android 5.1, I cannot develop on it as I don't have any 32-bit devices capable of running Android 5.1.
/* Before you download ... */
Donate to @rovo89
Donate to @wanam
Show your thanks to @_riddle
Without these people, this would not have been possible at all.
/* Details about binaries */
CyanogenMod's ART runtime changes merged - Performance improvements
Compiled using Linaro GCC 4.8
Method in-lining optimizations made in Android 5.1 merged
Few Android M ART runtime changes which were early-adopted by Samsung merged
-O3 and other compiler optimizations added
Release separated to "exynos" and "snapdragon" versions for more compiler optimizations
Optimize everything enabled
/* Download */
Attached below on XDA
/* How to install */
1. No matter what you do, back-up first.
2. Install XposedInstaller app from http://forum.xda-developers.com/showthread.php?t=3034811
3. Flash the attached Xposed framework zip on the custom recovery.
/* How to uninstall for V1 ~ V7 */
1. Flash the attached Xposed uninstaller zip on the custom recovery.
/* v75+ sticky note */
With v75 and up, this port do not longer touches core-libart.jar, thanks to @wanam.
This would potentially increase compatibility and fix other weirdness such as malfunctioning email app.
However, this introduces some variables.
First, there are more versions that you should choose.
Exynos and Snapdragon is quite self-explanatory, but there are now new "requestConcurrentGC" version for maximizing compatibility.
Don't know what to choose? Don't worry, it won't break your device if you install a wrong one.
If you install a wrong one, the installer will simply tell you that you should go with the other version.
As far as my testing goes, only the Korean Note 3 firmwares should install "requestConcurrentGC" version.
Uninstaller part have changed too.
You need to use uninstaller provided directly by @rovo89.
Do not use my uninstaller for v75 and up.
/* Technical information and Q&A */
Q: What took you so long?
A: @rovo89 has explained himself. http://forum.xda-developers.com/showpost.php?p=58949255&postcount=3
Q: Okay, you don't seem like a better developer than @rovo89. How did you do it?
A: Of course not. This is the main reason why deodex'ed ROM is a prerequisite.
Samsung has implemented all sorts of funny stuffs on their version of ART. See the link above.
To workaround this, converting a ROM to deodex'ed format somewhat brings back the oat formats to *AOSP-like* dex format(Huge thanks to @_riddle).
After deodexing is done, we can use source-built ART binaries with minimal modifications.
But due to my coding skills, I had to modify core-libart.jar to make it work again.
The core-libart.jar differs from every single device out there and it'll be a real headache to match with 1 ART binary version. That's why I've included the core-libart.jar on the installation zip file.
The included core-libart.jar has 2 different versions to correspond on the type of ROM user is using.
1 : Firmwares with appStartup
2 : Firmwares without appStartup
After deodexing, installing new ART stuffs, we can start the boot-up sequence.
Unfortunately again, /system/bin/installd passes some arguments that AOSP version of dex2oat do not understand. To bypass this, I've patched oat tools to ignore unimplemented arguments.
Now we can see the good old "Android is upgrading" pop-up and go have a cup of coffee while it dexopts all those hundreds of bloatwares.
Q: Fantastic, but now I get a continuous logcat burps - http://pastebin.com/MxeAE76n
A: To avoid that, that's why I've put 2 different versions of core-libart.jar. But unfortunately on those cases, my installer has failed to recognize which version your ROM uses.
During the installation, the installer will output a message on which core-libart.jar is installed on your system.
After you see that logcat stuffs, please change to the opposite version of core-libart.jar the installer told you.
So for example, if the installer says core-libart1.jar is installed, extract the zip and replace /system/framework/core-libart.jar with core-libart2.jar within the zip.
Q: How do I deodex my ROM?
A: @joeldroid and @svadev have an awesome tool for you to deodex your ROM.
Go check http://forum.xda-developers.com/and.../script-app-joeldroid-lollipop-batch-t2980857 and http://forum.xda-developers.com/galaxy-s5/general/tool-deodex-tool-android-l-t2972025
Both worked flawlessly for me.
Q: Gimme tha sources!
A: https://github.com/arter97/android_art/tree/samsung-lollipop
Q: AAA and BBB modules are incompatible!
A: Most likely because they don't support Touchwiz Lollipop *yet*.
Q: You mother father gentleman, you bricked my phone!
A: Unfortunately, I had tested those only on 3 devices which, ironically, has the same processor. Maybe Exynos family is not support, I don't know.
I told you to back-up beforehand. Post log and we can probably work together and add your device/ROM supported.
/* Changelog */
v75
Xposed v75 merged
(Fixes boot issue with latest Android 5.0 firmwares)
Method changed to use @wanam's XposedBridge
/* v75+ sticky note */
With v75 and up, this port do not longer touches core-libart.jar, thanks to @wanam.
This would potentially increase compatibility and fix other weirdness such as malfunctioning email app.
However, this introduces some variables.
First, there are more versions that you should choose.
Exynos and Snapdragon is quite self-explanatory, but there are now new "requestConcurrentGC" version for maximizing compatibility.
Don't know what to choose? Don't worry, it won't break your device if you install a wrong one.
If you install a wrong one, the installer will simply tell you that you should go with the other version.
As far as my testing goes, only the Korean Note 3 firmwares should install "requestConcurrentGC" version.
Uninstaller part have changed too.
You need to use uninstaller provided directly by @rovo89.
Do not use my uninstaller for v75 and up.
V6
Xposed v71 merged
Possible performance degradation issue fixed
Releases renamed to "exynos" and "snapdragon", now the "exynos" version is properly optimized for Exynos processor
Uninstaller added
Optimize everything enabled
V5
Xposed v65 merged - Now compatible with alpha4
Do not attempt to use uninstaller provided by rovo89, it will brick your device for now - TODO
V4
ART runtime & Xposed binary changes by rovo89 merged - Fixes logging and some other misc issues
CyanogenMod's ART runtime changes merged - Performance improvements
Compiled using Linaro GCC 4.8
Method in-lining optimizations made in Android 5.1 merged
Few Android M ART runtime changes which were early-adopted by Samsung merged
Few core-libart.jar smali durps fixed
-O3 and other compiler optimizations added
Release separated to "generic" and "krait" versions for more compiler optimizations
Generic - Devices with Exynos or other non-Krait Snapdragon SoCs; If you don't know which to choose, go with Generic.
Krait - Devices with Quadcore Krait Snapdragon SoCs.
V3
Another version of core-libart.jar added for GT-i9505 compatibility
(Firmwares without isMdfEnforced)
This update is unnecessary for devices which already runs Xposed with no issues.
V2
Source code modification attempted to hopefully fix boot issues with devices like Galaxy Alpha.
https://github.com/arter97/android_art/commit/eed217701cc2d3a57f940c5bd69b393c768777a9
This update is unnecessary for devices which already runs Xposed with no issues.
/* Known issues */
- Galaxy Alpha users apparently get a bootloop with this.
A kind user provided a logcat, will look into it ASAP.
Solved with V2.
- GT-I9505 users apparently get a continuous Google Apps FCs with this.
Solved with V3.
Thank you!!!!! How do we go about reverting it just in case anything were to happen? Does this have the same issue as darkera13's guide where you can't install apps?
Sweet! Any chance of supporting the S6 in the future?!
Damn no support for s6 edge
---------- Post added at 05:55 PM ---------- Previous post was at 05:54 PM ----------
Looks great though. No decomiling involved
SuperSmashedBro said:
Thank you!!!!! How do we go about reverting it just in case anything were to happen? Does this have the same issue as darkera13's guide where you can't install apps?
Click to expand...
Click to collapse
Exactly same .
Goood good
works fine on my galaxy s5 dous BOC2
xposed moudle and install apk normally works fine
darkera13 said:
Exactly same .
Click to expand...
Click to collapse
Which one is the original method yours or arter's?
I'm confused?
AMAZING!!!!!
arter you're genius!
noobiedev83 said:
Which one is the original method yours or arter's?
I'm confused
Click to expand...
Click to collapse
Me. I show a demo video 1 week ago. I public it first, even dont say but he base on my work is the true.
Xposed dont work with Samsung Lollipop Roms long time ago, the long time enough for all of you think this mission is impossible until i public my guide and he public after that about few hours.
darkera13 said:
Me. I show a demo video 1 week ago. I public it first, even dont say but he base on my work is the true.
Xposed dont work with Samsung Lollipop Roms long time ago, the long time enough for all of you think this mission is impossible until i public my guide and he public after that about few hours.
Click to expand...
Click to collapse
It should at least give you credit for that because I do remember seen your post a week ago
darkera13 said:
Me. I show a demo video 1 week ago. I public it first, even dont say but he base on my work is the true.
Xposed dont work with Samsung Lollipop Roms long time ago, the long time enough for all of you think this mission is impossible until i public my guide and he public after that about few hours.
Click to expand...
Click to collapse
Um, no offense but your method quite differs from mine.
I left out String.clear() and modified core-libart.jar to be compatible universally.
Your guide did not help me in anyways.
And I was also working on this weeks ago. Just didn't share it with the world which were *not-working* then.
arter97 said:
Um, no offense but your method quite differs from mine. And I was also working on this weeks ago. Just didn't share it with the world which were *not-working* then.
I left out String.clear() and modified core-libart.jar to be compatible universally.
Click to expand...
Click to collapse
You know what you do. Dont lie yourself.
To be honest, i tried both methods and @arter97 's methods worked for me without any hassle.
Kudos to you for making this work.
noobiedev83 said:
It should at least give you credit for that because I do remember seen your post a week ago
Click to expand...
Click to collapse
Here http://forum.xda-developers.com/showpost.php?p=60747729&postcount=2645
and here http://forum.xda-developers.com/showpost.php?p=60748574&postcount=29
darkera13 said:
You know what you do. Dont lie yourself.
Click to expand...
Click to collapse
Stealing is the least thing to do on my mind, as I have gone through the same thing over and over.
Ask my Twitter's followers.
I can personally guarantee you that I have not stolen anything from you.
Ask me how I did it more specifically, I'll happily explain it to you.
Working on Note 4 PopRocks Rom N910T
arter97 said:
Please note that I have tested this only on Galaxy S4, Note 3 and S5.
Click to expand...
Click to collapse
You think this will work on Albe95 S6 Rom port (GT-I9505)? :fingers-crossed:
Related
CM12.{0,1} (Lollipop) official/unofficial builds for the Droid 4
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.0/5.1 (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at any of us for messing up your device, we will laugh at you.
* Collectively, and at the same time.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review.
These are WIP builds of porting CM12.{0,1} to the Droid 4 (and also other devices using the same device/motorola/omap4-common-infrastructure). They probably won't work, so don't expect too much. Use on your own risk!
Builds:
Last official build:
http://droid.cs.fau.de/cm-12.1/official/
Old manual builds:
http://droid.cs.fau.de/cm-12.0/pre-alpha-test/new_safestrap/
Changes (only device/family specific, CM base is always synced before build and contains more changes):
2015-04-16:
Switched CM build-target, new nightlies will now be 12.1: http://review.cyanogenmod.org/#/c/94693/
2015-02-01:
No more unofficial builds! See: http://review.cyanogenmod.org/#/c/87596/
2015-01-28:
Mobile data fixes
Remaining com.android.phone crashes on VZW finally fixed (thanks @joojoobee666)
2015-01-24:
Fixed sw-keyboard popup when hw-keyboard is used (thanks @joojoobee666)
Fixed reboot to recovery
Fixed sepolicy for whisperd (dock service)
2015-01-22:
Fixed su-permissions
Crashes on Verizon most likely fixed, please report back
2015-01-20:
Fixed flashlight
2015-01-18:
SELinux updates.
This requires manual action for applications to continue being able to access their own files when upgrading from 2014-01-14 or 2014-01-15 (older versions are fine)!
Due to SELinux-bugs in 2014-01-1{4,5}, you have to relabel your data-partition on the first boot when upgrading from 2014-01-14/-15. This only needs to be done once. To do this, enable adb/usb debugging and grant root to adb (both in developer settings) and execute via an adb shell:
Code:
su -c 'for i in /data/*; do echo "${i}"; restorecon -DFrv "${i}"; done; sync; reboot'
2015-01-1{4,5}:
More fixes for {,umts_}spyder
sepolicy updates
GSM fixes
notable CM changes: su integration fixed
2015-01-11:
Updated SELinux policies (mostly for spyder/umts_spyder)
Added kernel stability fixes
Video decoding fixes
2015-01-09:
Enabled SELinux enforcing
Add SELinux-policies for motorola services
Enable ro.telephony.get_imsi_from_sim on VZW devices (thanks @joojoobee666)
2015-01-02:
Sync CM changes
2014-12-23:
Fixed stock camera
2014-12-22:
Sync CM changes
Fix build due to P2P changes (fix pushed into CM)
Enabled security for adb (keys/not root by default)
2014-11-30:
Added APN fixes for CDMA/LTE
Enabled multiuser mode (might not work yet)
Last update for a couple of weeks
2014-11-27:
Fixed graphics glitches
2014-11-26:
Fixed HW video-decoding
Enabled doze mode (no pickup sensor in the devices!)
CM resync as always
2014-11-23:
Probably fixed mobile data on LTE
Fixed WiFi-tethering
2014-11-22:
Requires a recovery supporting SELinux
What's working:
Phone (tested on Verizon and on GSM/UMTS in Europe)
Mobile data (at least on GSM/UMTS in Europe)
WiFi
WiFi-tethering
GPS
Camera
Playback of DRM-protected content (using Widevine from OnePlusOne)
What's not working:
Probably most everything else, including, but not limited to:
Some connectivity issues (should be solved now)
Data encryption
Gapps (CM-12.0):
Dhacker29 provides gapps for Lollipop:
http://d-h.st/YQG
http://d-h.st/jzr
http://droid.cs.fau.de/cm-12.0/gapps/ (Mirror)
Gapps (CM-12.1):
https://github.com/cgapps/vendor_google/releases/
Installation:
You need a new recovery supporting SELinux
An updated Safestrap (3.75) which supports SELinux can be found here: https://github.com/stargo/android_packages_apps_Safestrap/releases/tag/v3.75
Please read the instructions on how to install this version and follow the order of the steps in it.
GSM users:
To use this CM12.{0,1}-ROM on GSM-networks you should install Mentor.37's GSM patch
Source / Repositories:
maserati device-support: https://github.com/CyanogenMod/android_device_motorola_maserati
omap4-common device-support: https://github.com/CyanogenMod/android_device_motorola_omap4-common
omap4-common kernel: https://github.com/CyanogenMod/android_kernel_motorola_omap4-common
local manifest to build cm-12 for the Droid 4: http://droid.cs.fau.de/cm-12.0/pre-alpha-test/new_safestrap/local_manifest.xml
XDA:DevDB Information
CM 12.{0,1} on Motorola Droid4, ROM for the Motorola Droid 4
Contributors
stargo, Hashcode, Dhacker29
Source Code: https://github.com/CyanogenMod
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: No Longer Updated
Created 2014-11-23
Last Updated 2016-02-16
thank you @stargo, I am so pleased to see this thread, I was wondering when this thread is going to appear. Looks like I will continue to cling onto my droid 4 for a while, no virtual keyboard can beat a droid 4 keyboard.
Is data encryption enabled by default like on the nexus 6? I read that it greatly reduces the performance of the device. I meant this: http://www.xda-developers.com/android/disable-data-encryption-nexus-6/
Once again, thank you so much for your efforts in keeping this device alive.
sharptv said:
thank you @stargo, I am so pleased to see this thread, I was wondering when this thread is going to appear. Looks like I will continue to cling onto my droid 4 for a while, no virtual keyboard can beat a droid 4 keyboard.
Click to expand...
Click to collapse
Is data encryption enabled by default like on the nexus 6? I read that it greatly reduces the performance of the device. I meant this: http://www.xda-developers.com/android/disable-data-encryption-nexus-6/
Click to expand...
Click to collapse
No, data encryption is not enabled by default (and still doesn't even work for us).
Cheers,
Michael
Flipping sweet thanks y'all rock i love xda
Cast Screen
Hey stargo. thanks a lot for this! :good:
The 'Cast Screen' under settings pull-down menu is not working. It does not find any of the chromecasts that I have nearby.
Not a big deal, and not a priority at all for me, but just wanted to let you know.
Thanks again!
G'day,
just wanted to confirm the procedure for updating SafeStrap, since some people have CM11 in their stock slot:
in the first step (when you say 'go back to stock'), are you saying simply to boot the stock slot, regardless of ROM (since once SS is unistalled the 'slots' don't exist)?
Or do you mean boot to stock ROM, in stock slot?
I'm guessing it's the former, but I'd like to be sure before taking the plunge =)
thanks for your work! I gave the 2011 version a run over the weekend, it worked pretty well all things considered =)
gabhroo123 said:
Hey stargo. thanks a lot for this! :good:
The 'Cast Screen' under settings pull-down menu is not working. It does not find any of the chromecasts that I have nearby.
Not a big deal, and not a priority at all for me, but just wanted to let you know.
Thanks again!
Click to expand...
Click to collapse
May not ever work, IIRC, chromecasting the screen requires hardware we just don't have. :[
Shobai said:
G'day,
just wanted to confirm the procedure for updating SafeStrap, since some people have CM11 in their stock slot:
in the first step (when you say 'go back to stock'), are you saying simply to boot the stock slot, regardless of ROM (since once SS is unistalled the 'slots' don't exist)?
Or do you mean boot to stock ROM, in stock slot?
I'm guessing it's the former, but I'd like to be sure before taking the plunge =)
thanks for your work! I gave the 2011 version a run over the weekend, it worked pretty well all things considered =)
Click to expand...
Click to collapse
assuming that cm11 is currently installed in your stock slot and you want to update to the new test safestrap by stargo:
uninstall the existing safestrap using the original safestrap, for instance, if the existing safestrap is 3.73, you should install safestrap 3.73 and uninstall the recovery.
DO NOT REBOOT YOUR PHONE IN THE PROCESS
after you have uninstalled the existing recovery, uninstall safestrap(3.73), and then install the new safestrap by stargo, and install the recovery.
your safestrap is now updated, and nothing will be wiped.
YOU MUST NOT REBOOT YOUR PHONE DURING THE PROCESS, you can only reboot after a recovery has been installed.
hope you find this useful
thelolotov said:
May not ever work, IIRC, chromecasting the screen requires hardware we just don't have. :[
Click to expand...
Click to collapse
It need some kernel changes... but it should work...original gnex have the same cpu/gpu and they make it work... @lucize was seeing that but i dont know what happend with that
---------- Post added at 07:38 AM ---------- Previous post was at 07:37 AM ----------
By the way....thanks michael for your great work!...please make a donation link to send you some beer money!
Cheers, sharptv, much obliged =)
gabhroo123 said:
The 'Cast Screen' under settings pull-down menu is not working. It does not find any of the chromecasts that I have nearby.
Not a big deal, and not a priority at all for me, but just wanted to let you know.
Click to expand...
Click to collapse
Yes, our GPU driver does not support WFD. And in contrast to the GNEX, Motorola added much stuff to our version, so it's not easy to sync it back with the upstream kernel. Last time I tried that, I ended up with a non-working display and couldn't figure out why...
Shobai said:
just wanted to confirm the procedure for updating SafeStrap, since some people have CM11 in their stock slot:
in the first step (when you say 'go back to stock'), are you saying simply to boot the stock slot, regardless of ROM (since once SS is unistalled the 'slots' don't exist)?
Click to expand...
Click to collapse
Just boot to whatever you currently have installed in the stock slot. And I have to underline what @sharptv said, never reboot your phone in the process (it might work when you have the stock ROM in the stock slot, but it will surely break in every other case).
Cheers,
Michael
Will cm12 be pre-rooted in future? I can't seem to find anything solid on this, hopefully someone will be able to shed some light on this.
This App Camera work fine: https://play.google.com/store/apps/details?id=com.radcam.camera
---------- Post added at 11:34 AM ---------- Previous post was at 11:31 AM ----------
sharptv said:
Will cm12 be pre-rooted in future? I can't seem to find anything solid on this, hopefully someone will be able to shed some light on this.
Click to expand...
Click to collapse
See this thread: http://www.xda-developers.com/android/supersu-beta-lollipop-root-stock-kernel/
Download and install with recovery
I can confirm that at least on my phone that LTE is working. Great work .
flash these zips in recovery for root i got the from my nexus 7 root toolkit
HOPE IT WORKS FOR YOU :good::cyclops:
TheXG6HD said:
I can confirm that at least on my phone that LTE is working. Great work .
Click to expand...
Click to collapse
Yay! Thanks for confirming
It is a really bad hack, but if it works... http://review.cyanogenmod.org/78845
Cheers,
Michael
stargo said:
Yay! Thanks for confirming
It is a really bad hack, but if it works... http://review.cyanogenmod.org/78845
Cheers,
Michael
Click to expand...
Click to collapse
Data doesn't come up on its own, still needs some prodding (selecting the APN) and will go out randomly. Still not ready for prime time, sadly.... :<
It does come up a lot quicker, however.
thelolotov said:
Data doesn't come up on its own, still needs some prodding (selecting the APN) and will go out randomly. Still not ready for prime time, sadly.... :<
It does come up a lot quicker, however.
Click to expand...
Click to collapse
That's VZW weirdness
But if it comes up, then data is actually passing? Because that is what my patch was intended to fix. Before that the data-indicator would show up, but data would not actually get transmitted...
Can you probably send me the output of "ip route list" and "ip addr list" when LTE data is connected?
Would be interesting to see, what is actually happening now. I can only guess from here...
Regards,
Michael
stargo said:
That's VZW weirdness
But if it comes up, then data is actually passing? Because that is what my patch was intended to fix. Before that the data-indicator would show up, but data would not actually get transmitted...
Can you probably send me the output of "ip route list" and "ip addr list" when LTE data is connected?
Would be interesting to see, what is actually happening now. I can only guess from here...
Regards,
Michael
Click to expand...
Click to collapse
LTE was working on first build, just took 10+ mins to connect then worked good.
Sent from my XT907 using Tapatalk
stargo said:
That's VZW weirdness
But if it comes up, then data is actually passing? Because that is what my patch was intended to fix. Before that the data-indicator would show up, but data would not actually get transmitted...
Can you probably send me the output of "ip route list" and "ip addr list" when LTE data is connected?
Would be interesting to see, what is actually happening now. I can only guess from here...
Regards,
Michael
Click to expand...
Click to collapse
The deal is, the data works at first, then at random intervals it breaks and needs to be manually reset. I'm travelling right now so I can't really risk using CM12 right now, but I'll get you some logs when possible. JJB is having the same issue, I'll ask him to try and get you some details.
To my brothers (you know who you are)
Long, long ago...
A small pet dinosaur was left, abandoned and alone. His keepers, it seemed, had more interest in newer, more capable pets. But he eventually met with other dinosaurs, also abandoned, and a man named hephappy...
STATUS: NOT BOOTING
JENKINS SHUT DOWN
NO DOWNLOADS
The purpose of this thread is two-fold, I think. It is meant to be a venue for androidarmv6 (team) ,as most of their development is done off- site. It is also meant to be a place for hard core dinosaur lovers to test this work, and add to it as development proceeds. As androidarmv6 has brought us, the p500 community, through to working CM- 11, now we will start a new chapter, namely CM- 12. At the time of this posting, there have been several successful builds for the p500. But none are successfully booting, as yet.
I can't stress enough that most of this work is experimental, as the newer source code is being adapted to work on these devices. So unless you are okay with a possibly bricked (unusable) phone, don't flash any of these ROMs. Also, I do not have any responsibility or liability in the case that you should damage your phone by flashing any of this firmware. Also, your warranty will be voided. And I do not represent, and am not affiliated with androidarmv6. That said... YOU HAVE BEEN WARNED.
Website:
http://androidarmv6.github.io/
Source code:
https://github.com/androidarmv6
You can watch development as it progresses, or you can sign in and participate here:
http://review.androidarmv6.org/#/q/status:merged
STATUS: NOT BOOTING
JENKINS SHUT DOWN
NO DOWNLOADS
sent from my towelrooted LG L34C using daishi4u bumped twrp 2.8.3.0 and bumped key-boot-recovery kernel
...as he looked back on the sleeping giants, exhausted from their long journey, the wizard Androidmeda new that he had taught them all that he could, and they had all that they needed. But he also knew that they would never be able to survive crossing the mountains into the new land. Only their child would be able...
Well I guess this is it my brothers. Seems that all has been tried, and CM-12 will not be released for armv6 devices. But many thanks to our devs for trying. It's been a long run. Amazing, just amazing.
ibub said:
To my brothers (you know who you are)
Long, long ago...
A small pet dinosaur was left, abandoned and alone. His keepers, it seemed, had more interest in newer, more capable pets. But he eventually met with other dinosaurs, also abandoned, and a man named hephappy...
The purpose of this thread is two-fold, I think. It is meant to be a venue for androidarmv6 (team) ,as most of their development is done off- site. It is also meant to be a place for hard core dinosaur lovers to test this work, and add to it as development proceeds. As androidarmv6 has brought us, the p500 community, through to working CM- 11, now we will start a new chapter, namely CM- 12. At the time of this posting, there have been several successful builds for the p500. But none are successfully booting, as yet.
I can't stress enough that most of this work is experimental, as the newer source code is being adapted to work on these devices. So unless you are okay with a possibly bricked (unusable) phone, don't flash any of these ROMs. Also, I do not have any responsibility or liability in the case that you should damage your phone by flashing any of this firmware. Also, your warranty will be voided. And I do not represent, and am not affiliated with androidarmv6. That said... YOU HAVE BEEN WARNED.
Source code:
https://github.com/androidarmv6
ROMs:
http://jenkins.androidarmv6.org
sent from my towelrooted LG L34C using tapatalk
Click to expand...
Click to collapse
Congrats! Nice preface wording, bro! :good:
Great! and thanks.
I have not been using cm-11. Omni runs better and seems!! to have fewer bugs. Problem with cm is that when newer comes along, older bugs are left there. I guess we all prefer to play with the latest and greatest so not really complaining. My real problem with cm-11 is the special recoveries needed for it.
I would like to try cm-12 builds, but want to be able to get back to the omnirom. How do I get around the recovery changes (would be nice to have a cwm or twrp that asks on bootup: Want TSL? Switch system and data? But for now, I do not want to lose my alternatives or brick the phone.
How to proceed?
BTW: Link points to end-user builds (cm-11). We'll get there.
Dovidhalevi said:
Great! and thanks.
I have not been using cm-11. Omni runs better and seems!! to have fewer bugs. Problem with cm is that when newer comes along, older bugs are left there. I guess we all prefer to play with the latest and greatest so not really complaining. My real problem with cm-11 is the special recoveries needed for it.
I would like to try cm-12 builds, but want to be able to get back to the omnirom. How do I get around the recovery changes (would be nice to have a cwm or twrp that asks on bootup: Want TSL? Switch system and data? But for now, I do not want to lose my alternatives or brick the phone.
How to proceed?
BTW: Link points to end-user builds (cm-11). We'll get there.
Click to expand...
Click to collapse
Thanks, link updated to View/All.
sent from my towelrooted LG L34C using tapatalk
This is great @ibub !
Thanks for taking the initiative of building CM12 for this device, which never seems to grow old.....
The androidarmv6 team is just awesome! Keep up the gr8 work! It's always appreciated!
Waiting for it to boot for now...
D3oDex3D_AyusH said:
This is great @ibub !
Thanks for taking the initiative of building CM12 for this device, which never seems to grow old.....
The androidarmv6 team is just awesome! Keep up the gr8 work! It's always appreciated!
Waiting for it to boot for now...
Click to expand...
Click to collapse
Just to be clear, this is not my work. Androidarmv6 team (mainly androidmeda for p500) compiles these ROMs. Thanks belong to them (him).
sent from my towelrooted LG L34C using tapatalk
Wut? ART isn't compatible with ARMv6, AFAIK.
Casserole said:
Wut? ART isn't compatible with ARMv6, AFAIK.
Click to expand...
Click to collapse
We shall soon see.
sent from my towelrooted LG L34C using tapatalk
CyanogenMod announces official CM12 Nightlies!
http://phandroid.com/2015/01/05/cyanogenmod-cm12-nightlies/
Do not even expect P500 on the list!
EDIT:
CyanogenMod 12 nightlies now available for 31 devices, based on Android 5.0.1 Lollipop (LRX22C). LG Optimus One is out of the list to be sure
http://blog.gsmarena.com/cyanogenmo...able-31-devices-based-android-5-0-1-lollipop/
While in other hand, our devs are working to port experimentally newer version of CM12 (Android 5.0.2 LRX22G) on armv6 obsolete devices, though! :good:
You can look at development of android_art as it progresses here:
http://review.androidarmv6.org/#/q/status:merged
and here:
http://review.androidarmv6.org/#/c/7676/
Who dares (try this on p500) win!
http://jenkins.androidarmv6.org/view/Developers/job/cm-experimental/1308/
http://jenkins.androidarmv6.org/vie.../archive/cm-12-20150108-EXPERIMENTAL-p500.zip
Sent from my HM 1SW using XDA Free mobile app
xu3sno said:
Who dares (try this on p500) win!
http://jenkins.androidarmv6.org/view/Developers/job/cm-experimental/1308/
http://jenkins.androidarmv6.org/vie.../archive/cm-12-20150108-EXPERIMENTAL-p500.zip
Sent from my HM 1SW using XDA Free mobile app
Click to expand...
Click to collapse
Trimmed>>Flashed>>Stuck at CM bootlogo
CCXAlex said:
Trimmed>>Flashed>>Stuck at CM bootlogo
Click to expand...
Click to collapse
+1K
GERRIT_CHANGES: 7676 7748 7693 7651 7751 7792
Code:
7676: * runtime : make entrypoints ARM; if the target arch is lower than
armv7, set armv6.
* compiler: add a new define: ARM_MODE_WORKAROUND, enable it if
the target cpu is arm11. Use ARM assembler and replace
Thumb{1-2} opcodes with ARM ones. Update some code to
support new opcodes
NOTE: kArm is not implemented, probably it use to work only in
portable mode.
7748: Compatibility work around for bad graphics driver dependency
7693: legacy OMX: squashed commit for legacy OMX support for LP
7651: Revert "Revert "Turn on BLE, GATT, and SMP of Bluetooth stack""
7751: msm7x27-common: Initial cm-12 bringup
7792: jemalloc: Force gcc for atomic functions
GCC built-in functions provide advanced things like prefetch, expected, synchronization...
Bootloog attached.
It seems bootloop's culprit is regarding with dynamic shared libraries (lib*.so) which must be fixed first.
It does not work on any device arvm6.
Link
A reminder: unannounced experimental builds that you may see on Jenkins are made by and for developers alone, and are definitely not suitable to be flashed by users. The cm12 totoro build from today doesn't install or boot, and I expect many future builds will be the same, so don't waste your time with it.
Also, a reminder of some things you shouldn't do (now or ever): don't ask for ETAs, don't spam the dev thread, and don't PM me asking for information that isn't on a public post.
There are many things that need to be fixed for armv6 devices. I've sorted out the major issues specific to Broadcom hardware, but there are more important issues that need solving for ARMv6 devices in general that are being working on by several people (assembly errors, ART compatibility, build system integration, etc.). It's going to take time. Thanks for your understanding.
Click to expand...
Click to collapse
Build cm_p500-userdebug-cm-12.0 (Jan 11, 2015 9:45:30 PM)
Androidmeda built it for testing via Jenkins, if you dare to waste your time!
http://jenkins.androidarmv6.org/view/Developers/job/cm-experimental/1311/
ROM: http://jenkins.androidarmv6.org/vie.../archive/cm-12-20150111-EXPERIMENTAL-p500.zip
xu3sno said:
Build cm_p500-userdebug-cm-12.0 (Jan 11, 2015 9:45:30 PM)
Androidmeda built it for testing via Jenkins, if you dare to waste your time!
http://jenkins.androidarmv6.org/view/Developers/job/cm-experimental/1311/
ROM: http://jenkins.androidarmv6.org/vie.../archive/cm-12-20150111-EXPERIMENTAL-p500.zip
Click to expand...
Click to collapse
If it works on s5360 it will also work on the P500. But this time it does not work perfectly on any device armv6. I will follow up if it worked on my s5360 will report over here.
Thanks for the update by @xu3sno
Any PlayStore said:
If it works on s5360 it will also work on the P500. But this time it does not work perfectly on any device armv6. I will follow up if it worked on my s5360 will report over here.
Thanks for the update by @xu3sno
Click to expand...
Click to collapse
@Any PlayStore
also @CCXAlex (may be you have luck to try it, but I doubt )
Even Any PlayStore has quoted previously, just to satisfy my curiosity, insisted to install cm12-20150111_EXPERIMENTAL-p500.
Trimmed > clean installed > rebooted > boot loop As previous attempt, it seems lib*.so need to be fixed (?)
Don't know it's wasting my time or not
Quote:
A reminder: unannounced experimental builds that you may see on Jenkins are made by and for developers alone, and are definitely not suitable to be flashed by users. The cm12 totoro build from today doesn't install or boot, and I expect many future builds will be the same, so don't waste your time with it.
Click to expand...
Click to collapse
Yes, yes, we know or should know. But, hey, who does not want to be the first to see this play? The only reason I am staying off is because of the CM tricks with switching system and data partitions meaning recoveries are not compatible.
Anyway, diehards within the CM universe, once in that bootloop if ART had indeed done its thing, check remaining system space and contents of those /system/app/... folders. My (un-) educated guess is that this may become the big problem.
xu3sno said:
@Any PlayStore
also @CCXAlex (may be you have luck to try it, but I doubt )
Even Any PlayStore has quoted previously, just to satisfy my curiosity, insisted to install cm12-20150111_EXPERIMENTAL-p500.
Trimmed > clean installed > rebooted > boot loop As previous attempt, it seems lib*.so need to be fixed (?)
Don't know it's wasting my time or not
Click to expand...
Click to collapse
I also attempted to install this. Initially my trimming method seems to have broken update binary, so flash failed. Next installed full ROM (/system =189MB) using @HardLight twrp 2.7.0.0 TLS (successfully flashed). Stuck at boot animation. No log (flashing while driving).
sent from my towelrooted LG L34C using tapatalk
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?
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!
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 ?