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)

[EXPERIMENTAL] [UNOFFICIAL] Xposed for arm64 devices | 5.1 and 5.0 versions available

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!

[5.1.1] [2015-08-29] [Xposed Support] CyanogenMod 12.1

CyanogenMod 12.1​These 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 ?

[ANNOUNCEMENT] CM Bootloop Issues and XPosed with Early November CM Releases...

Hello Everyone,
The AOSP pushed a patch that effectively breaks xposed. The CM team doesn't support xposed (in fact they don't even take bug reports from users who have it installed). That being said, they don't actively work against it either.
There is a comment found here, though it is for the d2, it applies to the other devices as well
http://forum.xda-developers.com/showpost.php?p=69631802&postcount=1162
The patch that AOSP pushed is going to require the xposed dev(s) to do something to work around it (or users can compile their own builds with a workaround).The CM team won't be reverting this new AOSP security measure, for obvious reasons
With that being said, the official XPosed Dev, Rovo89, is currently working on an XPosed modification/solution to this. You can see the work Rovo89 is performing here:
https://github.com/rovo89/XposedBridge/issues/129#issuecomment-260498284
When they figure out a solution, you will find it posted here:
http://forum.xda-developers.com/showthread.php?t=3034811
In the meantime, and unfortunately, if you want to keep using XPosed, you will have to keep using the last CM release that XPosed was working on (the pre-security updated release). And when XPosed has been modified to work on the pre-security releases of CM, then you will be able to update your CM ROM and all will be at peace (hopefully LOL!).
Good Luck...
Peace and Love!
Peace and Love!
~Ibuprophen

Thank you very much for the announcement, I'm really grateful!
It was difficult and difficult to always answer the uninformed about this subject, are causing a certain irritation to developers those users who repeat the same questions (as in the case of VoLTE)
Thank you for keeping us informed!

Some progress from CM team?
https://review.cyanogenmod.org/#/c/170575

Shivver said:
Some progress from CM team?
https://review.cyanogenmod.org/#/c/170575
Click to expand...
Click to collapse
CM's patch is aimed to fix issues on some devices having proprietary blobs that have file descriptor leaks which result in errors during boot.
(e.g. shield tablet in particular)
While this patch allows to white list xposed specific stuff at device configuration level, it was not aimed to serve this purpose at all.

This might help you http://forum.xda-developers.com/showpost.php?p=69699345&postcount=4504

here is the official fix => http://forum.xda-developers.com/showpost.php?p=69702111&postcount=4526

Latest LineageOS 15.1 release incompatible with Magisk

This post is just to warn users of both LineageOS and Magisk to be very careful when updating to LineageOS 15.1 latest release (May 28) as they may end up stuck booting in bootloader mode. My suggestion is to perform a Nandroid backup prior to updating LineageOS 15.1 to May 28 release. I discovered this on a OnePlus 5 ('cheeseburger') and the issue is systematic with both Magisk 16.0 and 16.4. All I could do is wipe everything and revert to the previous release of LineageOS 15.1 (dated May 21) and this one works fine with Magisk 16.0 and also with 16.4. According to a recent (now deleted) post on LineageOS Reddit thread, the same problem happens on OnePlus 5T ('dumpling').

Gynoid said:
This post is just to warn users of both LineageOS and Magisk to be very careful when updating to LineageOS 15.1 latest release (May 28) as they may end up stuck booting in bootloader mode. My suggestion is to perform a Nandroid backup prior to updating LineageOS 15.1 to May 28 release. I discovered this on a OnePlus 5 ('cheeseburger') and the issue is systematic with both Magisk 16.0 and 16.4. All I could do is wipe everything and revert to the previous release of LineageOS 15.1 (dated May 21) and this one works fine with Magisk 16.0 and also with 16.4. According to a recent (now deleted) post on LineageOS Reddit thread, the same problem happens on OnePlus 5T ('dumpling').
Click to expand...
Click to collapse
As a workaround if you flash a different kernel (i.e. Franco) prior to flash magisk everything working fine

the 0605 build also has the same issue. Is anyone has a solution for this trouble?

I met the same issue, and I have to downgrade to 0521 with sideload.

Unfortunately the devs at Lineage don't seem to give a sh... about Magisk - I tried to raise the problem at their Reddit page, but my post and all subsequent users replies (people having the same issues) were deleted - and, true, LineageOS release 0605 still has that same issue. So the only solution If found is to root my Oneplus5 with LineageOS SU instead, but I still had a problem with the current release of Tasker which does not detect root when LineageOS SU is used. Luckily enough, the latest Tasker beta works fine with it.
So I'll live without Magisk for the moment.
Until I get rid of Lineage

Ah - coming into OP5 from a OP3 - has this been fixed in 6/11 release? I read that flashing franco's kernel BEFORE Magisk solves the problem. True?

digger16309 said:
Ah - coming into OP5 from a OP3 - has this been fixed in 6/11 release? I read that flashing franco's kernel BEFORE Magisk solves the problem. True?
Click to expand...
Click to collapse
Unfortunately, the issue is still present in the 6/11 release, at least on my OP5 and most probably on OP5T as well. Regarding other kernels, I don't know and I will not start testing kernels - takes too much time.

Gynoid said:
Unfortunately the devs at Lineage don't seem to give a sh... about Magisk
Click to expand...
Click to collapse
Don't they explicitly say they don't support it though? Pretty sure I've seen that they aren't interested in supporting it and custom kernels..?
If they don't support it and you are all "I break my phone cos I used the Magisk" it's going to grate somewhat.
It would be like going into a vegetarian restaurant, slipping some gammon into a vegetable lasagna and then complaining cos it tastes horrible. Only in this case you haven't paid any money and they've given you something for free you can take or leave.

OK so just because it's free it should not be criticized? Is that your point? It should never make any progress? Well that's how "free" projects die. Hopefully their developers will be little more ambitious than that..

gurningchimp said:
Don't they explicitly say they don't support it though? Pretty sure I've seen that they aren't interested in supporting it and custom kernels..?
If they don't support it and you are all "I break my phone cos I used the Magisk" it's going to grate somewhat.
It would be like going into a vegetarian restaurant, slipping some gammon into a vegetable lasagna and then complaining cos it tastes horrible. Only in this case you haven't paid any money and they've given you something for free you can take or leave.
Click to expand...
Click to collapse
It would be more like a vegetarian restaurant not catering ever to specific dietary requirements, allergies etc.
Except the restaurant is free so nearly everyone okay with it in theory, but it might mean that they lose patronage as too many of their visitors have food sensitivities that mean they end up going elsewhere.

batwingnz said:
It would be more like a vegetarian restaurant not catering ever to specific dietary requirements, allergies etc.
Except the restaurant is free so nearly everyone okay with it in theory, but it might mean that they lose patronage as too many of their visitors have food sensitivities that mean they end up going elsewhere.
Click to expand...
Click to collapse
I mean, I did wonder if the thrust of this complaint was related to irritable bowel syndrome :cyclops:

gurningchimp said:
I mean, I did wonder if the thrust of this complaint was related to irritable bowel syndrome :cyclops:
Click to expand...
Click to collapse
Rooting it wouldn't help with that

gurningchimp said:
Don't they explicitly say they don't support it though? Pretty sure I've seen that they aren't interested in supporting it and custom kernels..?
If they don't support it and you are all "I break my phone cos I used the Magisk" it's going to grate somewhat.
Click to expand...
Click to collapse
OK, they don't support it but hasn't work on SU ended? Does SU still work to root 15.1? v2.82?
Using the food analogy...
A custom ROM without root is like a half-baked cake to many. Edible perhaps, but not complete.
Magisk has or is becoming the standard to root, isn't it?

digger16309 said:
OK, they don't support it but hasn't work on SU ended? Does SU still work to root 15.1? v2.82?
Using the food analogy...
A custom ROM without root is like a half-baked cake to many. Edible perhaps, but not complete.
Magisk has or is becoming the standard to root, isn't it?
Click to expand...
Click to collapse
You're thinking of SuperSU, lineage, for whatever reason, reinvented the wheel and rolled their own implementation.

OP5 Lineage 15.1 after 2018-05-21 results still in bootloader
the problem seems to persist - the last updates will always result in the device being stuck in the bootloader after flashing. I reversed the update by flashing the cheeseburger 2018-05-21-nightly over the latest (thank god for the working TWRP!) and it boots up normally. I checked up to 2018-06-11
How do we know if this is indeed a problem with Magisk (have v 16.0 installed)? Does somebody need more informations regarding the OP5 (cheeseburger) installs? Can I help in some way to resolve this problem (testing? log files?)
any hope for a resolve? The device works fine but I would like to be able to update regulary at least for security reasons (patched bugs)

I installed LOS15.1 and I see it now. Was this also the case in previous versions, 13 and 14? I remember having to turn on root manually in LOS, then Cyanogenmod and flashing SU. But I think the developer of the custom 14.1 ROM I was using took it out of his ROM so I forgot all about it. Breaking Magisk is lame. I can manage without it, but I prefer the systemless Xposed option it provides.

Did anyone try this with the LOS 20180618 build?

IMHO I don't see anything in the June 18 build changelog that would make me think it's gonna work any better than the previous builds. And on the Magisk side, there hasn't been any new release or beta for a while. So ...

Did anybody find a solution? Would upgrading Magisk 16.0 to 16.4 beta be worth a shot? How about deinstalling Magisk (via the deinstall-zip? or the deinstall option in the manager?) - would this enable the LOS update (as of today 2018-06-18-nightly)? And if yes, would it be safe to reinstall Magisk afterwards or is this door permamently closed?
I would give it a try myself but do not have a backup phone in case of bricking it and I need it for work... a report about a successful strategy would help a lot!

I flashed LineageOS 15.1-20180618-NIGHTLY-cheeseburger and Gapps Nano yesterday. After the reboot I installed the latest Magisk Manager.apk and flashed the latest sdk 27. I am now running LineageOS 15.1 with Magisk v16.0.
I didn't know about any problems there were before because this was the first time I flashed Lineage (had xXx - NoLimits). But I can't see any issues by now. It's working fine. I downloaded Youtube Vanced, Watchdogs Bootanimation and Xposed Framework (only gravitybox atm) which are all working.