Hi there,
This is a magisk module compatible with any android device (except x86) running at least android oreo up to latest and greatest Android 11!
It was tested on lineage based roms but should work on all AOSP and some stock roms just fine.
Changelog, Compatibility list and everything else can be found via the download link below at the github page.
Some users already reported compatibility with some stock ROMs so feel free to let me know if it works or not.
If i find the time, i´ll update the compatibility list on github.
Note:
Since Android 10, arm64 devices (everything since 2015 will be arm64) needed updated libs which I didn´t test on oreo and pie so it is possible, android oreo and pie in combination with a more recent device will no longer work.
I didn´t test it so we don´t know until someone is willing to try it out for us!
ARM/armv7 (ooold devices!) will work just fine, the same old libs from oreo still work until android 11.
But now have a great listening experience!
Download here
Credits:
- topjohnwu for magisk
- Qualcomm for aptx
[email protected] for directing me to the right github repo for updated blobs (arm64/android10)
Some Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Very good contribution, is there a possibility that you can make a version compatible with arm64? What happens is that the existing modules are not compatible with Android 10. And the only reason I downgraded Android 9 on my Redmi Note 8 Pro is exactly to be able to use the module that enables aptX support.
sinrequilorios said:
Very good contribution, is there a possibility that you can make a version compatible with arm64? What happens is that the existing modules are not compatible with Android 10. And the only reason I downgraded Android 9 on my Redmi Note 8 Pro is exactly to be able to use the module that enables aptX support.
Click to expand...
Click to collapse
Thanks
I was always using "APTX for android oreo and pie" which still works fine on my htc one m9 running android 10 (arm64).
The module has more complexity in it and maybe even unnecessary stuff.
I'll have a look into the libs my oneplus 3t uses (arm64).
In the meantime you can do a backup of your rom, download the module, extract the system/lib/ files to the exact same directory on your device using twrp file manager (system can't be mounted rw anymore in android).
Maybe it works idk.
Btw are you on stock?
multiwirth said:
Thanks
I was always using "APTX for android oreo and pie" which still works fine on my htc one m9 running android 10 (arm64).
The module has more complexity in it and maybe even unnecessary stuff.
I'll have a look into the libs my oneplus 3t uses (arm64).
In the meantime you can do a backup of your rom, download the module, extract the system/lib/ files to the exact same directory on your device using twrp file manager (system can't be mounted rw anymore in android).
Maybe it works idk.
Btw are you on stock?
Click to expand...
Click to collapse
Yes, I am currently on MIUI 11, Android 9. I use the module "Bluetooth stack audio bitrate changer for SBC + aptX & aptX-HD enabler" and it works without problems in Android 9 under MIUI 11. But I had upgraded to Android 10 and it stopped working (it totally broke the audio via Bluetooth), so I made a downgrade and it is working again.
sinrequilorios said:
I use the module "Bluetooth stack audio bitrate changer for SBC + aptX & aptX-HD enabler" and it works without problems in Android 9 under MIUI 11. But I had upgraded to Android 10 and it stopped working
Click to expand...
Click to collapse
Try the module i mentioned, it will install all the libs for arm64 and should work.
I've checked the libs on my oneplus 3t which has aptx hd out of the box and it looks identical to what this module comes with.
You can find it via magisk manager, search for aptx.
Have a nice day
multiwirth said:
Try the module i mentioned, it will install all the libs for arm64 and should work.
I've checked the libs on my oneplus 3t which has aptx hd out of the box and it looks identical to what this module comes with.
You can find it via magisk manager, search for aptx.
Have a nice day
Click to expand...
Click to collapse
Thanks again for your prompt response, that module I also took the time to test it (when both were in the repo), but it didn't work either, have you recently tried it with any device that is on Android 10? In a 4pda forum nobody manages to make the module work on Android 10. And in the repo of the indicated module they mention that it is incompatible with Android 10. Any additional help I will be eternally grateful, greetings!
sinrequilorios said:
Thanks again for your prompt response, that module I also took the time to test it (when both were in the repo), but it didn't work either, have you recently tried it with any device that is on Android 10? In a 4pda forum nobody manages to make the module work on Android 10. And in the repo of the indicated module they mention that it is incompatible with Android 10. Any additional help I will be eternally grateful, greetings!
Click to expand...
Click to collapse
Hmm yes i've Lineage 17.1 on my HTC One M9 and this module installed and it works fine as far as i remember.
I think i haven't actually tested it yet i may do it later when I'm at home.
I could also try extracting the libs from my daily driver.
It's also possible miui doesn't load the libs even if they're present.
I will talk back later when I'm at home.
multiwirth said:
Hmm yes i've Lineage 17.1 on my HTC One M9 and this module installed and it works fine as far as i remember.
I think i haven't actually tested it yet i may do it later when I'm at home.
I could also try extracting the libs from my daily driver.
It's also possible miui doesn't load the libs even if they're present.
I will talk back later when I'm at home.
Click to expand...
Click to collapse
Thanks for your support, I will be attentive in such case! As for MIUI, in Android 9 / MIUI 11 it works, I don't know if it will be Android 10's problem .
sinrequilorios said:
Thanks for your support, I will be attentive in such case! As for MIUI, in Android 9 / MIUI 11 it works, I don't know if it will be Android 10's problem .
Click to expand...
Click to collapse
The module does work on my HTC M9, at least it loads the libs and enables aptx-HD.
But Bluetooth keeps crashing so i'm not sure if it's an device specific issue or an issue with Android 10.
It also seems like it loads the libs from /system/lib64/ but same results with crashes.
Logcat doesn't help don't understand the issue.
So i can only offer you to test it on your device.
I've hacked together a magisk zip which will add aptx libs to /system/lib/ /system/lib64/ and vendor/lib64/
Just to make sure that your rom will load the libs at all.
If it works for you, maybe i will make a clean release for it aswell.
Don't have any other arm64 device left for testing and on my oneplus 3t aptx is already included and working fine.
multiwirth said:
The module does work on my HTC M9, at least it loads the libs and enables aptx-HD.
But Bluetooth keeps crashing so i'm not sure if it's an device specific issue or an issue with Android 10.
It also seems like it loads the libs from /system/lib64/ but same results with crashes.
Logcat doesn't help don't understand the issue.
So i can only offer you to test it on your device.
I've hacked together a magisk zip which will add aptx libs to /system/lib/ /system/lib64/ and vendor/lib64/
Just to make sure that your rom will load the libs at all.
If it works for you, maybe i will make a clean release for it aswell.
Don't have any other arm64 device left for testing and on my oneplus 3t aptx is already included and working fine.
Click to expand...
Click to collapse
Thank you for your effort. I went back to Android 10 again to test. But I could not make it work, I tried the experimental module that you included here. And it does detect the device as an aptX, but when playing audio it gives an error and the bluetooth fails. I also tried the module that you indicated downloaded from Magisk, but with that module it only detects the device as AAC (as if it were not installed).
Is there a way to manually add the libraries and it works? It does not matter that it is not for a magisk module (that is, it does not matter that it is a little more laborious). Thanks in advance again.
sinrequilorios said:
Is there a way to manually add the libraries and it works? It does not matter that it is not for a magisk module (that is, it does not matter that it is a little more laborious). Thanks in advance again.
Click to expand...
Click to collapse
The issue with android 10 is, you can't mount /system as rw in android anymore due to system-as-root.
But aptx libs are stored in /vendor usually (on arm64).
So i've put together a module with libs from my oneplus3t but jo idea if it will work.
If you have a backup of your rom, extract the contents of the zip and put all the files from /system/vendor/rfsa/adsp/* in /vendor/lib/rfsa/adsp/ to your phone (create folder if it does not exist)
If it does not work, try to to the same thing with the files in /vendor/etc/acdbdata.
Copy file by file, then reboot and try.
For this step begin with the files labeled with bluetooth or bt since there might be existing files you'll have to override and may break other stuff.
And please don't forget to do a backup before you directly write to your partitions!
Good luck
multiwirth said:
The issue with android 10 is, you can't mount /system as rw in android anymore due to system-as-root.
But aptx libs are stored in /vendor usually (on arm64).
So i've put together a module with libs from my oneplus3t but jo idea if it will work.
If you have a backup of your rom, extract the contents of the zip and put all the files from /system/vendor/rfsa/adsp/* in /vendor/lib/rfsa/adsp/ to your phone (create folder if it does not exist)
If it does not work, try to to the same thing with the files in /vendor/etc/acdbdata.
Copy file by file, then reboot and try.
For this step begin with the files labeled with bluetooth or bt since there might be existing files you'll have to override and may break other stuff.
And please don't forget to do a backup before you directly write to your partitions!
Good luck
Click to expand...
Click to collapse
Thanks again for your effort to help me. I checked both directories under "root / vendor", and neither "rfsa / adsp" existed within "lib", nor did "acdbdata" exist within "etc".
I had to create both directories (so no files were replaced), but when I rebooted the device everything I copied through MiXplorer disappeared... as if he had never copied it. I had to add the files via TWRP to keep them that way on reboot. But likewise no change happened, the codec was kept AAC. Then I tried the Magisk module in the repository again, but it stayed in AAC the same way. Finally I tried the experimental module again that you added here. And like the previous time, it was displayed as aptX, but the Bluetooth stopped working.
If it's any use, I'll indicate the similar folders that my device includes:
root/system/vendor/etc
root/system/vendor/lib
root/system/vendor/lib64
root/system/etc
root/system/lib
root/system/lib64
root/vendor/etc
root/vendor/lib
root/vendor/lib64
And also attached the module that I used in Android 9, in case it is of any use. Thank you very much, greetings!
sinrequilorios said:
Thank you for your effort. I went back to Android 10 again to test. But I could not make it work, I tried the experimental module that you included here. And it does detect the device as an aptX, but when playing audio it gives an error and the bluetooth fails. I also tried the module that you indicated downloaded from Magisk, but with that module it only detects the device as AAC (as if it were not installed).
Is there a way to manually add the libraries and it works? It does not matter that it is not for a magisk module (that is, it does not matter that it is a little more laborious). Thanks in advance again.
Click to expand...
Click to collapse
Bad news
I've tested various things on my htc m9 including using the weird libs from my oneplus 3t from what i believe was for aptx but none of them seem to work.
Also the last module you shared comes with various aptx libs in various directories.
The stuff on my oneplus looks like some proprietory stuff and a friend of mine doesn't have any of those files at all (but working aptx in android 10, oneplus6)
So what i guess, it seems like android 10 needs more low level patches to get aptx to work (at least now?) until someone comes up with "generic libs" like we was using previously.
Those generic libs do load on my htc m9 but forces bluetooth to crash (same result on yours)
Seems like they're too old and incompatible and i can't find a source for updated libs.
Maybe i can find a way to talk to the lineageos dev for oneplus3 to find out what he did or what i missed.
Seems like armv7 roms/devices handle this much easier, those old libs do still work perfectly.
Maybe we can get arm64 to use arm 32bit libs but i really don't know how.
Sorry about that, would've been great to fix this but it is a bigger issue as it seems :/
multiwirth said:
Bad news
I've tested various things on my htc m9 including using the weird libs from my oneplus 3t from what i believe was for aptx but none of them seem to work.
Also the last module you shared comes with various aptx libs in various directories.
The stuff on my oneplus looks like some proprietory stuff and a friend of mine doesn't have any of those files at all (but working aptx in android 10, oneplus6)
So what i guess, it seems like android 10 needs more low level patches to get aptx to work (at least now?) until someone comes up with "generic libs" like we was using previously.
Those generic libs do load on my htc m9 but forces bluetooth to crash (same result on yours)
Seems like they're too old and incompatible and i can't find a source for updated libs.
Maybe i can find a way to talk to the lineageos dev for oneplus3 to find out what he did or what i missed.
Seems like armv7 roms/devices handle this much easier, those old libs do still work perfectly.
Maybe we can get arm64 to use arm 32bit libs but i really don't know how.
Sorry about that, would've been great to fix this but it is a bigger issue as it seems :/
Click to expand...
Click to collapse
Don't worry, you did what you could and I really appreciate it. In the same way I will be attentive to the subject, to see if you or someone else finds the solution. It would be great! Greetings and thanks for your contributions!
Guys, I can confirm that there is definitely some problem with the aptx libraries on 10, I was using the same libraries hacked to my build in 14.1, 15.1, now in 17.1 it seems first that aptx is working, but bluetooth then crash. Its not problem of library paths in 10 or something like that, since these libraries based on its filename were from android sdk21, there are pretty old and was working fine on many old android versions, but for 10, we need some updated binaries. I'll try to find some (that's how I got here).
torukk said:
Guys, I can confirm that there is definitely some problem with the aptx libraries on 10, I was using the same libraries hacked to my build in 14.1, 15.1, now in 17.1 it seems first that aptx is working, but bluetooth then crash. Its not problem of library paths in 10 or something like that, since these libraries based on its filename were from android sdk21, there are pretty old and was working fine on many old android versions, but for 10, we need some updated binaries. I'll try to find some (that's how I got here).
Click to expand...
Click to collapse
Yeah those libs also get loaded on my htc m9 (arm64) but BT crashes, the arm (32 bit) libraries are still working fine on such old devices running android 10.
If i remember right, the most used libs in various aptx ports were extracted from a stock OOS from a oneplus3 device but more recent firmwares on other oneplus devices no longer have the aptx encoders as libs and so it is in LineageOS 17.1 for my oneplus 3t which is aptx(hd) enabled out of the box but doesn't have the libs.
Probably integrated to the bluetooth driver itself.
Anyways if you find anything, i would appreciate it if you can share it with us
hey, I've downloaded blobs from google 'blueline' device, these blobs are for 10, and I can confirm that they works in 17.1, there are only 64b libs, in my system both placed to vendor/lib64, from TWRP:
suzuran:/system_root/system/vendor/lib64 # md5sum libaptX*
59d896f337f570eaf54a480261f50ccc libaptXHD_encoder.so
18e6569d5bf4e3b1124e9f95e1b1df4a libaptX_encoder.so
link:
https://github.com/Aqua-devices/vendor_google/tree/x/blueline
Deleted duplicate-post
torukk said:
hey, I've downloaded blobs from google 'blueline' device, these blobs are for 10, and I can confirm that they works in 17.1, there are only 64b libs, in my system both placed to vendor/lib64, from TWRP:
suzuran:/system_root/system/vendor/lib64 # md5sum libaptX*
59d896f337f570eaf54a480261f50ccc libaptXHD_encoder.so
18e6569d5bf4e3b1124e9f95e1b1df4a libaptX_encoder.so
link:
https://github.com/Aqua-devices/vendor_google/tree/x/blueline
Click to expand...
Click to collapse
Thanks for sharing, will have a loom on it this evening and maybe update the module to make it also compatible with arm64 after some testing
Hi, how i can download libs fron GIT?
ÇThanks.
torukk said:
hey, I've downloaded blobs from google 'blueline' device, these blobs are for 10, and I can confirm that they works in 17.1, there are only 64b libs, in my system both placed to vendor/lib64, from TWRP:
suzuran:/system_root/system/vendor/lib64 # md5sum libaptX*
59d896f337f570eaf54a480261f50ccc libaptXHD_encoder.so
18e6569d5bf4e3b1124e9f95e1b1df4a libaptX_encoder.so
link:
https://github.com/Aqua-devices/vendor_google/tree/x/blueline
Click to expand...
Click to collapse
Related
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!
This module patches OPLongshot's code so that it produces PNG screenshots, as it should, instead of JPEG screenshots (ew!). It patches only the VDEX/ODEX files, which have no signature on them — only the APK is signed, which we do not modify, so OPLongshot still retains system signature privileges. The original APK is included to avoid version mismatches (although I don't think there will be much issue even if it isn't includd).
Note that the OPLongshot was taken from the OnePlus 5T's system image. YMMV for other devices on OxygenOS (or even HydrogenOS?).
The current version uses the version of OPLongshot from OnePlus 5T OxygenOS 5.1.0/5.1.1 (same), with version 1.1.0.180328153957.6a699c8.
Remember to clear Dalvik/ART cache after installing this.
GitHub repository (also details of how the patch is done).
Download zip (temporary until the Magisk repo bot refreshes)
any plan for OP5?
h20ray said:
any plan for OP5?
Click to expand...
Click to collapse
Could you upload the APK and odex/vdex files?
Are you going to port it to OnePlus 3/3T devices?
Does it works with the OP5 ?
angelsel said:
Could you upload the APK and odex/vdex files?
Click to expand...
Click to collapse
I've attached the latest the OPLongshot folder (taken from the latest OB14 for the OP5 and zipped). Looking forward to the modifications for this version as well for the OP5, whenever you get the time. Thank you!
shadowstep said:
I've attached the latest the OPLongshot folder (taken from the latest OB14 for the OP5 and zipped). Looking forward to the modifications for this version as well for the OP5, whenever you get the time. Thank you!
Click to expand...
Click to collapse
Do you plan to compile from OB15?
V5 doesn't work on the last OB 14(5T)
Nemo Aeternam said:
V5 doesn't work on the last OB 14(5T)
Click to expand...
Click to collapse
Same here
We will no longer update this great module
We? Hope for an update! jpg must die..
Sent with much love & Android. OnePlus 5T
Would be great to see an update, no longer works on Pie for OP6.
This was meant for the OnePlus 5T stable builds only (as the title states); I don't use the beta builds, nor do I own a OnePlus 6. That the modified vdex even worked on the beta builds and non-5T builds was not intentional.
Someone else can follow the method I have detailed to create modules for the OnePlus 6 and the 5T open betas.
The current version works on OxygenOS 5.1.5 for OnePlus 5T (the APK did not change from 5.1.4 to 5.1.5).
angelsel said:
This was meant for the OnePlus 5T stable builds only (as the title states); I don't use the beta builds, nor do I own a OnePlus 6. That the modified vdex even worked on the beta builds and non-5T builds was not intentional.
Someone else can follow the method I have detailed to create modules for the OnePlus 6 and the 5T open betas.
The current version works on OxygenOS 5.1.5 for OnePlus 5T (the APK did not change from 5.1.4 to 5.1.5).
Click to expand...
Click to collapse
About vdex2dex, did you use it with the entire AOSP tree or do you have a standalone version with dependencies?
If you do have a standalone version (which I couldn't find) can you provide it?
tanish2k09 said:
About vdex2dex, did you use it with the entire AOSP tree or do you have a standalone version with dependencies?
If you do have a standalone version (which I couldn't find) can you provide it?
Click to expand...
Click to collapse
I used it with the entire AOSP tree. Sorry.
Can i just use it in Oneplus 3??
Sent from my OnePlus3 using XDA Labs
Is there any timeframe on when Pie support for this module will be implemented? It worked fine for me in the previous beta version, and now I can only take screenshots with the module disabled since I updated my OP5T today.
zland said:
Is there any timeframe on when Pie support for this module will be implemented? It worked fine for me in the previous beta version, and now I can only take screenshots with the module disabled since I updated my OP5T today.
Click to expand...
Click to collapse
Yes, we need this mod. Sadly I can't do it myself.. but maybe I can help you out with the needed files, OP?
OP Longshot seem to still be at ver. 1.1.0...
but there is a new folder inside the path of OP Longshot called "lib". Inside that folder is a folder called arm64, and inside arm64 are two files calling "libencryptjni.so" and "op_encrypt.so" maybe these are the reasons the old magisk module won't work? i don't know for sure, but i know that these folders and files aren't present in the magisk module.
I would buy you a beer OP, for updating this mod. :good:
moeq123 said:
Yes, we need this mod. Sadly I can't do it myself.. but maybe I can help you out with the needed files, OP?
OP Longshot seem to still be at ver. 1.1.0...
but there is a new folder inside the path of OP Longshot called "lib". Inside that folder is a folder called arm64, and inside arm64 are two files calling "libencryptjni.so" and "op_encrypt.so" maybe these are the reasons the old magisk module won't work? i don't know for sure, but i know that these folders and files aren't present in the magisk module.
I would buy you a beer OP, for updating this mod. :good:
Click to expand...
Click to collapse
I followed the instructions as mentioned in the GitHub readme, and I ended up successfully getting a modified version.
Sadly though, it doesn't seem to work on android P
I have updated the module, based on OOS OB20 (OP5T) but should also work for OB22 (OP5). Cheers.
I think it's a good idea to share the magisk's modules we have installed.
-mi A1 gcam
-youtube vanced
Google lens enabler
Google sans mod font
HAL3 enabler
iOS11.1 emoji
Unified hosts adblock
YouTube vanced
Android O APT-X libraries: Android Oreo officially supports APT-X bluetooth audio, however not all phones have the needed library files. This module simply places the missing APT-X(HD) and LDAC files in your system if you don't already have it. Enjoy better bluetooth audio!
Busybox for Android NDK: As a byproduct of building my own static busybox compiles in all supported Android architectures for my AIK-mobile package I figured I might as well offer them up separately as well since there weren't any providers making Android x64 builds when I was researching. The installer detects what architecture (ARM/ARM64, x86/x86_64, MIPS/MIPS64) your device uses and installs the correct busybox binary accordingly. It then cleans up any symlinks from a possible previous installation in the same directory and generates new symlinks directly from the output of the installed binary. Detects and supports "systemless" root via SuperSU/Magisk installation as well.
Systemless Xposed: This is a port of rovo89's Xposed framework to work systemless-ly through Magisk.
SDK 27 (Android 8.1)
AirAudio - stream your music!
Android O APT-X libraries
Audio Compatibility Patch
Mi Mix 2 Snapchat Volume Fix
Unified Hosts Adblock
ViPER4Android FX Materialized
Magic Charging Switch (mcs)
kremmit said:
Android O APT-X libraries: Android Oreo officially supports APT-X bluetooth audio, however not all phones have the needed library files. This module simply places the missing APT-X(HD) and LDAC files in your system if you don't already have it. Enjoy better bluetooth audio!
Busybox for Android NDK: As a byproduct of building my own static busybox compiles in all supported Android architectures for my AIK-mobile package I figured I might as well offer them up separately as well since there weren't any providers making Android x64 builds when I was researching. The installer detects what architecture (ARM/ARM64, x86/x86_64, MIPS/MIPS64) your device uses and installs the correct busybox binary accordingly. It then cleans up any symlinks from a possible previous installation in the same directory and generates new symlinks directly from the output of the installed binary. Detects and supports "systemless" root via SuperSU/Magisk installation as well.
Systemless Xposed: This is a port of rovo89's Xposed framework to work systemless-ly through Magisk.
SDK 27 (Android 8.1)
Click to expand...
Click to collapse
Did you installed Xposed on MIUI?
Adriano-A3 said:
Did you installed Xposed on MIUI?
Click to expand...
Click to collapse
No I haven't anymore. But at the time of writing i had and it was working.
Why do you ask?
kremmit said:
No I haven't anymore. But at the time of writing i had and it was working.
Why do you ask?
Click to expand...
Click to collapse
I'm going to install it on MIUI 9.5.8.
Adriano-A3 said:
I'm going to install it on MIUI 9.5.8.
Click to expand...
Click to collapse
I'm on RR rom and it worked ok.
Adriano-A3 said:
I'm going to install it on MIUI 9.5.8.
Click to expand...
Click to collapse
Did it work for you? I'm still on 9.1 because I need Xposed.
kurtextrem said:
Did it work for you? I'm still on 9.1 because I need Xposed.
Click to expand...
Click to collapse
I didn't try. I sold my Mix 2.
The new LOS 17.1 for the P2 is amazing. However, the old aptX-HD Mod, which worked on LOS 16 doesn't seem to work on this rom. Is there any special Mod for Android 10, that enables it?
Warning! I did not test this myself as I did not yet upgrade to LOS17!
Based on devices that support aptx I think you have to place the blobs in /system/product/lib64 (instead of /system/vendor/lib64 in LOS 16).
I'm not sure if the blob itself changed.
Source: proprietary-files.txt of other devices
I'm not allowed to post links but search for proprietary-files.txt in LOS 17 repositories of devices that support aptx.
thanks,
so far i tried to copy the old mod files (aptx-enabler.zip) to the /system/product/lib64 folder. That did not work. I will try to search the LOS 17 repositories. But i am afraid that is a little beyond my capabilities. However, if i find something i will post here.
so i spent a lot of time to get this to work. copying the old aptx binaries to the /system/product/lib64 folder did in fact enable aptx hd for my headphones. however, the bluetooth app crashes when trying to play anything. i am not able to find any binaries for android 10 (LOS 17).. i searched on github without any success. if someone could provide a source for a binary for android 10, i guess it would work.
So far i will downgrade to LOS 16
Excuse me for my question but really what is aptx hd I didn't heard about it before
Some repositories use the aptx binary from crosshatch. You should be able to find them online. Maybe they work for our phone?
@HACKIMTOSH It is a Bluetooth audio codec by Qualcomm. Both the phone and the headset need to support it.
rayvw said:
Some repositories use the aptx binary from crosshatch. You should be able to find them online. Maybe they work for our phone?
@HACKIMTOSH It is a Bluetooth audio codec by Qualcomm. Both the phone and the headset need to support it.
Click to expand...
Click to collapse
Aha now i see , thank u
P2 friend said:
so i spent a lot of time to get this to work. copying the old aptx binaries to the /system/product/lib64 folder did in fact enable aptx hd for my headphones. however, the bluetooth app crashes when trying to play anything. i am not able to find any binaries for android 10 (LOS 17).. i searched on github without any success. if someone could provide a source for a binary for android 10, i guess it would work.
So far i will downgrade to LOS 16
Click to expand...
Click to collapse
Did you find a way to make it work? I'm searching for a rom / phone that actually has aptx hd functionality over Android 10. I'm curious if you ever found a way of making it work.
Thanks.
P2 friend said:
so i spent a lot of time to get this to work. copying the old aptx binaries to the /system/product/lib64 folder did in fact enable aptx hd for my headphones. however, the bluetooth app crashes when trying to play anything. i am not able to find any binaries for android 10 (LOS 17).. i searched on github without any success. if someone could provide a source for a binary for android 10, i guess it would work.
So far i will downgrade to LOS 16
Click to expand...
Click to collapse
I have duplicated this on my P2. AptX did not work at all and AptXHD linked to the Fiio but then wouldn't play - bluetooth kept crashing. Could this be an SELinux issue? I just copied the files across to the mounted system partition but I don't know how to set SELinux context from TWRP.
I bought tws Bluetooth with aptx support
I'm on havoc 2.9 android 9 , can you plz give me guide how to enable aptx suppirt in my p2 with the download link
HACKIMTOSH said:
I bought tws Bluetooth with aptx support
I'm on havoc 2.9 android 9 , can you plz give me guide how to enable aptx suppirt in my p2 with the download link
Click to expand...
Click to collapse
On Android 9 use this: https://forum.xda-developers.com/apps/magisk/port-aptx-aptxhd-oreo-8-0-update-jan-t3731151
rayvw said:
On Android 9 use this: https://forum.xda-developers.com/apps/magisk/port-aptx-aptxhd-oreo-8-0-update-jan-t3731151
Click to expand...
Click to collapse
Is it working on pie because he said its for oreo did u tested it on pie ? Does Bluetooth crashed?
Yes, I used the flashable zip on LOS 16 without any problems. I am on LOS 17.1 currently , but haven't found a working method for Android 10 yet.
rayvw said:
Yes, I used the flashable zip on LOS 16 without any problems. I am on LOS 17.1 currently , but haven't found a working method for Android 10 yet.
Click to expand...
Click to collapse
Thanks for the help , ok I'll go with flashable zip
I managed to enable AptX on LOS 17.1 using the binaries locaties here: https://github.com/Flex1911/aptx-libs-android10
The GitHub repo is actually a Magisk module, but I installed the binaries using ADB.
Just remount de system so that you can copy the two binaries to /system/product/lib64. Then change the permissions to 644 and restart the phone. AptX is now enabled.
Please be careful when remounting your system partition!
any recommended guide to follow? or if possible detail steps!
rayvw said:
I managed to enable AptX on LOS 17.1 using the binaries locaties here: https://github.com/Flex1911/aptx-libs-android10
The GitHub repo is actually a Magisk module, but I installed the binaries using ADB.
Just remount de system so that you can copy the two binaries to /system/product/lib64. Then change the permissions to 644 and restart the phone. AptX is now enabled.
Please be careful when remounting your system partition!
Click to expand...
Click to collapse
Does los 17.1 support LDAC codec?
Disclaimer :
Code:
I am not responsible for any damage to your device!
Use this mod at your own risk!
What's this?
This mod increases the audio bitrate on video recording from a disgraceful 96kbps to a respectable 320kbps. Thus, giving a richer, more pleasing audio quality.
Still confused? Click here for a better explanation
Requirements :
- A rooted phone with magisk installed
- An opened mind (important!)
Contributors :
@Jt380p
@Slim K
* NOTES * (READ) :
- Not all ROMs are compatible with this mod, you might end up in a bootloop. YOU HAVE BEEN WARNED!
Download :
https://drive.google.com/file/d/1wr-p7puOL8nYb1wj1AyVbh9XmMp5kRKI/view?usp=sharing (Flash with magisk manager)
Source :
https://forum.xda-developers.com/Mi-9/themes/magisk-audio-bitrate-increase-t3927810
Audio files provided by @Slim K
Thanks to :
@Slim K
@topjohnwu for Magisk
Created : 7/11/2020
Last updated : 7/11/2020
reserved
Just tried it on stock MIUI with stock camera and Gcam. Works like a charm. Ty :good:
Slim K said:
Just tried it on stock MIUI with stock camera and Gcam. Works like a charm. Ty :good:
Click to expand...
Click to collapse
For me it works on Stock, but not on Urnyx05 GCam. Thanks Dev.
Lineage android 11 will benefit from it, or that is already implemented in them?
So which ROMs are not compatible?
Aki-to said:
So which ROMs are not compatible?
Click to expand...
Click to collapse
This mod uses magisk module template to replace a file in vendor folder. A tip for beginners using such a mod is to inspect it to know what it does. For example in the root of the module zip you will find the folder system, which has the needed folders/files path for replacement. If you open install.sh in text viewer, you would read the line :
Bash:
set_perm $MODPATH/system/vendor/etc/media_profiles_vendor.xml 0 0 0644
That should tell you which file it is and their permissions. Now open the same path on your ROM and look for that file, if it exists, then it should work. Although not every camera app (e.g gcam) uses that file.
Slim K said:
This mod uses magisk module template to replace a file in vendor folder. A tip for beginners using such a mod is to inspect it to know what it does. For example in the root of the module zip you will find the folder system, which has the needed folders/files path for replacement. If you open install.sh in text viewer, you would read the line :
Bash:
set_perm $MODPATH/system/vendor/etc/media_profiles_vendor.xml 0 0 0644
That should tell you which file it is and their permissions. Now open the same path on your ROM and look for that file, if it exists, then it should work. Although not every camera app (e.g gcam) uses that file.
Click to expand...
Click to collapse
Thanks, this was very helpful.
Indeed, it seems like a very easy set of scripts, did not expect that. However, the only thing I could not find is where the default functions are actually called, though I assume these are generic functions that are always called by Magisk, no matter which module is being installed.
This mod is also so extremely tiny, you could pretty much make these changes manually. Just take care of permissions and replace the file, that's it. It's even less complicated than working with /etc/fstab, it seems.
Perhaps I should release a couple of mods myself, if mod devs are getting such a Magisk Module template thing, anyway, which pretty much does all the work, already.
Aki-to said:
Thanks, this was very helpful.
Indeed, it seems like a very easy set of scripts, did not expect that. However, the only thing I could not find is where the default functions are actually called, though I assume these are generic functions that are always called by Magisk, no matter which module is being installed.
Click to expand...
Click to collapse
You assume correctly. The path to the functions can be usually found in /data/adb/magisk/util_functions.sh on your device.
Perhaps I should release a couple of mods myself, if mod devs are getting such a Magisk Module template thing, anyway, which pretty much does all the work, already.
Click to expand...
Click to collapse
Why write code twice when it already exists and works for everyone.
Hello, could someone please confirm if it works on firmware xiaomi eu 12.0.4. stable, thank you very much.
nike1973 said:
Hello, could someone please confirm if it works on firmware xiaomi eu 12.0.4. stable, thank you very much.
Click to expand...
Click to collapse
Yes it works
Thank you. Works on MIUI EU 12.0.6.
Eu 12.0.6, super stabilization (on stock camera) crashes when module is active.
I flashed it to the phone. The stock camera app still records audio at 127kbps. Does not save with 320kbps!.I use Indonesian stable miui 12/android 10. please Help!
Anyone tried on Xiaomi.eu rom?
Running 12.0.8.
Hi!
gkhnkaanyrtc said:
I flashed it to the phone. The stock camera app still records audio at 127kbps. Does not save with 320kbps!.I use Indonesian stable miui 12/android 10. please Help!
View attachment 5272691View attachment 5272693
Click to expand...
Click to collapse
Hi! I have the same problem ... Did you fix it? I use Miui 12.0.1 with Android 11
320kbps should be the default, I wonder why the f**k Xiaomi gives us 96kbps.
Does it work in Pixel Experience rom on Surya?