Related
Audio Modification Library is a library of known audio mods. It'll search your magisk directory for any supported audio mods and incorporate them into itself. It's been completely redone to act as a standalone module so devs no longer need to worry about using a framework for their audio mods and users no longer are limited to just mods using that framework.
Some history
Originally, Unity Installer and AML were combined into one. That's what's archived on ahrions github.
Nowadays, unity is its own thing and AML was completely redesigned into what it is today. The whole purpose of aml is to combine the audio effect/policy/mixer/etc files from multiple audio mods into one set because only one copy of a file can be active mounted at any given time. With non-magisk installs, the actual copies of those audio files are all modified by various mods (aka they all work with the same copy) and so there's no need for aml
What is the purpose of this?
Audio mods often function in part by modifying some audio files (such as audio_effects, mixer_paths, etc.). The problem here is that each mod has it's own copy of the files and magisk can only mount 1 copy of each, so only 1 mod will completely work. AML functions by combining them all into one set of files to remedy this issue.
So how does it work?
It's now a standalone zip that is flashed once and forgetten about. It's magisk only for obvious reasons and will incorporate all supported audio mods into itself automatically during install, and then during each boot if any changes were detected. So it will adjust for any changes in audio mods such as new ones being installed, some being removed, or an existing one being updated.
Where the Mod is Located:
This is more of the nitty gritty for anyone interested but the aml specific copies of audio files and the mod itself are stored in the aml folder in the magisk directory like a typical module. However, it moves any detected audio files out of the folder of any audio mods so they won't be mounted by magisk and conflict. They're moved to .core/aml for safe keeping so they can be restored back to the mod later if you choose to uninstall aml or if upgrading aml
When do I flash this?
Unlike with older version of aml, order doesn't matter. However, it's best to flash aml FIRST. The reason for this is that an increasing number of audio mods look for aml and behave differently if it doesn't yet exist.
Troubleshooting:
If a mod didn't work before you flashed aml, it probably won't work after. Take up the issue on the mod's thread.
Otherwise, if a mod works before flashing aml and doesn't after: First, try uninstalling all audio mods and then reinstalling them (including aml). If that doesn't work, then I'll need you to make a post with this in it:
Recovery log after flashing AML
List of Audio Mods Installed
AML version last working on (if applicable)
Zip attachment of your aml magisk module (/data/adb/modules/aml) folder (note that there's a debug.log file in here that's shows everything)
Zip attachment of your aml backup folder (/data/adb/aml) folder
Currently Supported Mods:
AM3D
AudioWizard
V4AFX
V4AXhifi
Dolby Atmos (ahrion's ports)
Dolby Atmos Axon 7 Oreo (guitardedhero's port)
Dolby Digital Plus
Bang&Olufsen ICEPower (only tested ainur version)
Arkamys (only tested ainur version)
Dirac (only tested ainur version)
Dirac Hexagon (only tested ainur version)
JamesDSP
MaxX Audio 3
Audio Compatibility Patch (formerly universal deep_buffer remover)
Ainur Sauron
SquareSound
Sony Xperia Z2 Sound System
Ainur Narsil
Ainur DTSX
Ainur DTS Ultra
Dolby Atmos Pie/Q+ (guitardedhero's ports)
Want an audio mod added to AML?
Make a post about it and I'll see if it's eligible. No guarantees that I'll add it but these are things that it must have to even be considered:
Original/unique (so not a repackaging of other audio mods)
Universal(ish) (support a large number of devices - not specific to a handful of devices)
Patches files rather than replaces them (the whole point of aml is to be a collection of patches)
Patches must be static (won't be changing with each mod update)
Audio Mod Can't be Added to AML Directly? You can still add it in!
If it doesn't meet these requirements, you can still make it aml compatible.
You just need your mod to create a file called ".aml.sh" in the root of the mod directory ($MODPATH typically). It'll need to have the patches for your mod in a format that aml can understand:
For patching audio_effect files, AML includes a 'patch_cfgs' function that makes life much easier. So if you have an effect and library to add:
Code:
patch_cfgs <effect_name> <UUID> <library_name> <library_path>
For example:
Code:
patch_cfgs v4a_fx 41d3c987-e6cf-11e3-a88a-11aba5d5c51b v4a_standard_fx /vendor/lib/soundfx/libv4a_fx.so
Note that this patch_cfgs function is for audio effects files only. If you're patching audio policy or mixer_paths files, then you'll need to make the patches the old fashioned way yourself.
So if you're not patch audio effects files, skip on down to the 'Some other variables/options' section
'patch_cfgs' has several flags that can be used (the format followed by an example for each is listed here as well):
-l: patch library
Code:
patch_cfgs -l <library_name> <library_path>
Code:
patch_cfgs -l v4a_fx /vendor/lib/soundfx/libv4a_fx.so
-e: patch effect
Code:
patch_cfgs -e <effect_name> <UUID> <library_name>
Code:
patch_cfgs -e v4a_standard_fx 41d3c987-e6cf-11e3-a88a-11aba5d5c51b v4a_fx
-o: patch output_session_processing (postprocessing). Typically used with both 'l' and 'e' flags as well
Code:
patch_cfgs -ole <osp_section> <effect_name> <UUID> <library_name> <library_path>
Code:
patch_cfgs -ole music atmos 9d4921da-8225-4f29-aefa-aacb40a73593 atmos /vendor/lib/soundfx/libatmos.so
-q: patch pre_processing (preprocessing). Typically used with both 'l' and 'e' flags as well
Code:
patch_cfgs -qle <pp_section> <effect_name> <UUID> <library_name> <library_path>
Code:
patch_cfgs -qle music atmos 9d4921da-8225-4f29-aefa-aacb40a73593 atmos /vendor/lib/soundfx/libatmos.so
-p: patch proxy effect (note that since this is a special kind of effect, it cannot be used with '-e'). When used by itself
Code:
patch_cfgs -p <proxy_effect_name> <proxy_UUID> <sw_library_name> <sw_UUID> <hw_library_name> <hw_UUID>
Code:
patch_cfgs -p dax 9d4921da-8225-4f29-aefa-6e6f69726861 dax_sw 6ab06da4-c516-4611-8166-6168726e6f69 dax_hw a0c30891-8246-4aef-b8ad-696f6e726861
But it's typically used with 'l'
Code:
patch_cfgs -pl <proxy_effect_name> <proxy_UUID> <sw_library_name> <sw_UUID> <sw_library_path> <hw_library_name> <hw_UUID> <hw_library_path>
Code:
patch_cfgs -pl dax 9d4921da-8225-4f29-aefa-6e6f69726861 dax_sw 6ab06da4-c516-4611-8166-6168726e6f69 /vendor/lib/soundfx/libswdax.so dax_hw a0c30891-8246-4aef-b8ad-696f6e726861 /vendor/lib/soundfx/libhwdax.so
-r: replace. Normally, aml will only apply any of the above if it doesn't exist in the audio cfg file. With this flag enabled however, it'll replace any existing effects. It's pretty rare that this would be needed (none of the mods patches built-in to aml have this)
no flag specified: if no flags are specified, patch_cfgs will use -le by default (patch library and effect). This is what's typically used (like in the first example before this list)
For patching other files: just add you script logic like it it was in your mod.
If you're patching mixers for example:
Code:
for i in $(find $MODPATH/system -type f -name "*mixer_paths*.xml"); do
<add_patch_here> for mixer '$i'
done
MODPATH is equivalent to aml's directory since it's running the aml.sh script
Then when AML is installed, it'll detect this .aml.sh file and apply the patches accordingly
Source
Download
Awesome work! Excited to try it out. Will the usual AML mods such as ainur and v4a be updated or can I go ahead and test out with the current v2.9 zips?
nonchalantroller said:
Awesome work! Excited to try it out. Will the usual AML mods such as ainur and v4a be updated or can I go ahead and test out with the current v2.9 zips?
Click to expand...
Click to collapse
Just finished updating everything. Usual aml mods are now unity mods so you don't even need to worry about that anymore. I'll put a list of supported mods to the op in a min
Edit: OP updated, ainur mods will likely be released tomorrow so you'll need to hold off until then to use them
Here's the install log from Magisk where Viper is asking for drivers.
MrBrady said:
Here's the install log from Magisk where Viper is asking for drivers.
Click to expand...
Click to collapse
Can you try this test zip and send the recovery log?
Zackptg5 said:
Can you try this test zip and send the recovery log?
Click to expand...
Click to collapse
Sure! Installation failed. Log attached.
MrBrady said:
Sure! Installation failed. Log attached.
Click to expand...
Click to collapse
Danget, dumb error on my part. I reuploaded the attachment in my last post so try that. Sorry!
Zackptg5 said:
Danget, dumb error on my part. I reuploaded the attachment in my last post so try that. Sorry!
Click to expand...
Click to collapse
Installed the updated file. Still asking to install drivers. Log attached.
MrBrady said:
Installed the updated file. Still asking to install drivers. Log attached.
Click to expand...
Click to collapse
Dang, still same error on recovery log but now I'm starting to hone in on the problem. Thanks!
MrBrady said:
Installed the updated file. Still asking to install drivers. Log attached.
Click to expand...
Click to collapse
Does this aml work for you? (Post recovery log and aml folder please)
Zackptg5 said:
Does this aml work for you? (Post recovery log and aml folder please)
Click to expand...
Click to collapse
Installing this caused V4A to ask for drivers again. Folder and log attached.
MrBrady said:
Installing this caused V4A to ask for drivers again. Folder and log attached.
Click to expand...
Click to collapse
Think I got it. I'll need the same stuff as before
Zackptg5 said:
Think I got it. I'll need the same stuff as before
Click to expand...
Click to collapse
Bingo! That works now. Attached is the directory and log.
MrBrady said:
Bingo! That works now. Attached is the directory and log.
Click to expand...
Click to collapse
Sweet! Thanks for all your help, I really appreciate it :good:
Zackptg5 said:
Sweet! Thanks for all your help, I really appreciate it :good:
Click to expand...
Click to collapse
My pleasure! Thanks for making this mod! I know we all really appreciate it, even if it's not voiced often enough.
AML has been updated to v1.1! Main changes are fixes or xml cfg files (should fix issues with pixel 2's) and some other minor fixes. Thanks to @MrBrady for the troubleshooting help
v1.2 has been dropped. Hopefully this will be the last release for a while.
Changelog: Fixed janky bootmode stuff, Fix uninstall/upgrade when a supported audio mod has just been upgraded in bootmode
So basically any weird things that happened when flashing in magisk manager are now fixed
Zackptg5 said:
v1.2 has been dropped. Hopefully this will be the last release for a while.
Changelog: Fixed janky bootmode stuff, Fix uninstall/upgrade when a supported audio mod has just been upgraded in bootmode
So basically any weird things that happened when flashing in magisk manager are now fixed
Click to expand...
Click to collapse
Thanks! Seems to be working right on Pixel 2 XL now.
Safety net got tripped,RR unofficial 7.1.2, I passed again after uninstalling aml.
Gonna try again but install from twrp...seemed to fix my viper issues, might do the same for aml
---------- Post added at 08:27 AM ---------- Previous post was at 08:18 AM ----------
preference said:
Safety net got tripped,RR unofficial 7.1.2, I passed again after uninstalling aml.
Gonna try again but install from twrp...seemed to fix my viper issues, might do the same for aml
Click to expand...
Click to collapse
Yep, twrp install works with no safety net trip. I've never had this many issues using the direct install in magisk. I doubt that it's a module issue, I'm probably messing up the process.
Dropped v1.3. Fixes issues with output_session_processing patching - mainly applicable to dolby oreo
EdXposed
A Riru module trying to provide a ART hooking framework (mainly for Android Pie) which delivers consistent APIs with the OG Xposed, leveraging YAHFA hooking framework.
https://github.com/ElderDrivers/EdXposed
Credits
YAHFA: the core java hooking framework
Riru: provides a way to inject codes into zygote process
XposedBridge: the OG xposed framework APIs
dexmaker and dalvikdx: dynamiclly generate YAHFA hooker classes
Whale: used for inline hooking
Known issues
resources hooking is not supported yet
may not be compatible with all ART devices
only a few Xposed modules has been tested for working
file access services are not implemented yet, now simply use magiskpolicy to enable needed SELinux policies
Build requirements
same as Riru-Core's and zip binaries can be downloaded from here
Build
run :Bridge:makeAndCopyRelease in Gradle window to build edxposed.dex
run :Core:zipRelease to build Magisk Riru module flashable zip file
find the flashable under Core/release/
flash the zip in recovery mode or in Magisk Manager
Install
make sure Magisk v17.0 or higher is installed.
download Riru-core v10 or higher and install it in Magisk Manager or recovery.
download EdXposed and install it in Magisk Manager or recovery.
Install companion application(s)
reboot.
have fun
Companion applications
for v0.2.9.5 and before: Xposed Installer
for v0.2.9.6 and v0.2.9.7: Xposed Installer and EdXp Manager(optional)
for v0.2.9.8 and later: EdXposed Installer
Get help
Forum (recommend): Android Forum
GitHub issues (recommend): Issues
For Users using QQ, QQ Group: 855219808
Telegream: Code_of_MeowCat
Discord: Code_of_MeowCat
Contribute
Apparently this framework is far from stable and all kinds of PRs are welcome.
The main EdXposed XDA thread is here:
https://forum.xda-developers.com/xposed/android-9-0-xposed-solutions-t3889513
Nevertheless, this start post is more informative than the original one.
Is it Xposed replacement for oero/pie?
Sent from my Motorola Moto G (5S) Plus using XDA Labs
QkiZMR said:
Is it Xposed replacement for oero/pie?
Click to expand...
Click to collapse
Is the only Pie compatible version, and also looks like to work on Oreo.
I have a Google Pixel and I can confirm it's working on Pie, a lot of modules works, so far so good.
I started testing it today, on Oreo and I would say that is working stable for now. Some time ago after installing Xposed on my phone, I noticed that Xposed causing that system and application are running little slower than without Xposed. But capabilities that Xposed is giving to me are more important, so I can live with it. Now after installing EdXposed I didn't noticed any impact on system performance.
Sent from Moto G (5S) Plus via Tapatalk
Worked at first and I was able to install fake gapps because I wanted microg, but it stopped working after that. I do have microg working now, but I can't add any more xposed modules as it shows inactive. I read somewhere that it works after a soft reboot, will try that next.
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
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?
Before I start, I'd like to apologize if you don't understand something I say. English isn't my native language
Mega Audio ModOverview
Improve your audio experience
Install Audio Modification Library
Install DTS:X Ultra
Install ViPER4Android
A wide majority of you are probably already familiar with most of what happens here, in fact this module happens to be a collection of pre-existing Magisk modules helping keep your audio experience the best your device can provide. I earlier had to go through the pain of installing all of these modules every time I changed a ROM. (Which happened once or twice everyday) I, thus decided to make a module that automates the process for me and installs everything I need. I plan to keep updating this and learn even more magisk development in the future
To do:
Add some presets to the viper directory in Android folder (once I figure out how to write to /data via magisk modules)
Add some more audio associated improvements
Add some more modules
If you happen to have any idea on how to write to /data via magisk modules please reply to the thread..
If you have any suggestions please reply to the thread.
Credits @Team_DeWitt \ ViPer4Android
@UltraM8 @Nemuritor01 @JohnFawkes @LazerL0rd \ DTS:X Ultra
@Zackptg5 \ Audio Modification Library
I am not able to post links for some reason so please cope with me and copy and paste what I type below
Download:
Source: github.com/Maitreya29/Mega-Audio-Mod
Download: sourceforge.net/projects/mega-audio-mod/files/
reserved
reserved2
Can't get Viper driver to install. Even in permissive Selinux. DTS works. On Pixel 5
Your Android version is and have you a custom rom with custom kernel on your device or using stock rom?A lil bit more info where great.Cheers!!!
-CALIBAN666- said:
Your Android version is and have you a custom rom with custom kernel on your device or using stock rom?A lil bit more info where great.Cheers!!!
Click to expand...
Click to collapse
Android 11 stock rom
Magisk canary
Pixel 5