[Module] aptx (HD) for Android 10 (probably 9 and 8 aswell)

Does this still work on Oreo or Pie for you (arm64 devices!)

  • Yes

    Votes: 2 22.2%
  • No

    Votes: 3 33.3%
  • walnuts are dangerous animals

    Votes: 4 44.4%

  • Total voters
    9

akd06

Member
Apr 17, 2018
34
1
8
Oh this will be a pain without root...

Ok so unzip the files, reboot to twrp and copy the folders inside "system" lib and lib 64 to your phone´s /system/lib+lib64 (if it ask to override, tap yes, it will merge both folders and not override anything.
Do the same with the folder vendor (lib and lib64).

Tt might be enough to only copy the lib64 folder once to /vendor/lib64 if your device is arm64, otherwise copy lib only.
Probably not neccessary to place files into system and vendor, only one of those.
My phone is arm64. There are vendor, sys, system ,etc folder if I access through twrp file manager. I copy the contents of vendor folder in your zip folder to my devices vendor/arm64 folder & similarly for arm64 folder in zip folder to my device system folder. Is that what you saying?
 

multiwirth

Senior Member
Dec 17, 2013
738
268
93
Gerstetten
www.youtube.com
My phone is arm64. There are vendor, sys, system ,etc folder if I access through twrp file manager. I copy the contents of vendor folder in your zip folder to my devices vendor/arm64 folder & similarly for arm64 folder in zip folder to my device system folder. Is that what you saying?
In case of arm64, you also only need lib64.
The extra files just makes sure that this module is compatible with all devices and arm64 ROMs will simply ignore the lib (32bit) versions of the files while lib64 doesn´t exist at all on armv7 and the files will end in nirvana while installation on such old devices.

So it will be enough to place lib64 from the zip to /vendor/lib64 through TWRP.
Maybe also /system/lib64, this depends on your ROM.
 

akd06

Member
Apr 17, 2018
34
1
8
In case of arm64, you also only need lib64.
The extra files just makes sure that this module is compatible with all devices and arm64 ROMs will simply ignore the lib (32bit) versions of the files while lib64 doesn´t exist at all on armv7 and the files will end in nirvana while installation on such old devices.

So it will be enough to place lib64 from the zip to /vendor/lib64 through TWRP.
Maybe also /system/lib64, this depends on your ROM.
Don't it make my phone into bootloop even if put files correctly.
 

multiwirth

Senior Member
Dec 17, 2013
738
268
93
Gerstetten
www.youtube.com
Don't it make my phone into bootloop even if put files correctly.
Usually no but since you already run a custom ROM, in case of bootloop just dirty flash your rom.zip again it will keep open gapps but delete any other modifications to /system and ofc. keeps your data.
Or backup /system through TWRP if you don´t have the rom.zip of your current ROM.
 

akd06

Member
Apr 17, 2018
34
1
8
Usually no but since you already run a custom ROM, in case of bootloop just dirty flash your rom.zip again it will keep open gapps but delete any other modifications to /system and ofc. keeps your data.
Or backup /system through TWRP if you don´t have the rom.zip of your current ROM.
Thanks for your advice. One last advice, pixel experience incremental update refuse to install. Any idea how to fix it?
 

multiwirth

Senior Member
Dec 17, 2013
738
268
93
Gerstetten
www.youtube.com
Thanks for your advice. One last advice, pixel experience incremental update refuse to install. Any idea how to fix it?
Uhm I'm not really familiar with pixel experience at all but i assume it's because you modified the system.
However if it's the same update format than for example LineageOS, it should still update since you download a full ROM for every update which overwrites /system anyways.

But to be 100% sure you should ask this in a pixel experience support thread.
 

akd06

Member
Apr 17, 2018
34
1
8
Uhm I'm not really familiar with pixel experience at all but i assume it's because you modified the system.
However if it's the same update format than for example LineageOS, it should still update since you download a full ROM for every update which overwrites /system anyways.

But to be 100% sure you should ask this in a pixel experience support thread.
While trying to copy contents of lib64 folder from zip folder to device's system folder, my device shows SYS & SYSTEM folders among others. The sys folder in device contains lot of folders, namely class, firmware, etc. But system folder which is blue in color contains nothing. In which folder shall I chose sys or system. Kindly advice.
 

multiwirth

Senior Member
Dec 17, 2013
738
268
93
Gerstetten
www.youtube.com
While trying to copy contents of lib64 folder from zip folder to device's system folder, my device shows SYS & SYSTEM folders among others. The sys folder in device contains lot of folders, namely class, firmware, etc. But system folder which is blue in color contains nothing. In which folder shall I chose sys or system. Kindly advice.
Sys is completely irrelevant and shouldn´t be touched.
Make sure to mount /system in TWRP before accessing it
 

akd06

Member
Apr 17, 2018
34
1
8
Ok. Thanks.
I followed your instructions & successfully copied the files in respective places using twrp. But after rebooting to system and connected to my car's bluetooth receiver which is aptxhd compatible, it still connect to default SBC irrespective of aptxhd settings in developer option. It means your files not suitable for pixel experience rom. However I didn't get any bootloop. Kindly comment. Thanks.
 

multiwirth

Senior Member
Dec 17, 2013
738
268
93
Gerstetten
www.youtube.com
I followed your instructions & successfully copied the files in respective places using twrp. But after rebooting to system and connected to my car's bluetooth receiver which is aptxhd compatible, it still connect to default SBC irrespective of aptxhd settings in developer option. It means your files not suitable for pixel experience rom. However I didn't get any bootloop. Kindly comment. Thanks.
You can still try to copy all files included in the zip so all lib and lib64 to /system and /vendor.
If pixel experience is aosp/lineage based, it should work.
Android 8+ natively supports aptx(HD) and expects the drivers in /system/lib64 or /vendor/lib64.
As soon as they're present, aptx should work.

If you want to, you could try LineageOS it's a very similar experience to stock android and will definitely work with aptx libs
 

akd06

Member
Apr 17, 2018
34
1
8
You can still try to copy all files included in the zip so all lib and lib64 to /system and /vendor.
If pixel experience is aosp/lineage based, it should work.
Android 8+ natively supports aptx(HD) and expects the drivers in /system/lib64 or /vendor/lib64.
As soon as they're present, aptx should work.

If you want to, you could try LineageOS it's a very similar experience to stock android and will definitely work with aptx libs
As per your instruction I tried to copy lib files also but no avail. For your information while copying aptx files in /vendor/lib64 folder, files get deleted (not saving) from /vendor/lib64 folder after rebooting to system. Although files saving in /system/lib & /system/lib64, /system/vendor/lib64 folder after rebooting. I tried to mount vendor partition from twrp but it is not selecting the check box as mi a1 supports only non treble rom. Pixel experience is non treble aosp like lineage os rom. Thanks.
 

akd06

Member
Apr 17, 2018
34
1
8
Hi, ey dev, work fine in my old Xiaomi A1 with LOS 17.1.

Thanks.
Is it possible to share build.prop of lineage 17.1? You have to use adb command " adb pull /system/build.prop" to get build.prop file to your adb folder from where run command prompt. I getting problem for installing aptx & aptxhd in my xiaomi mi A1 running pixel experience rom. Thanks.
 

akd06

Member
Apr 17, 2018
34
1
8
You can still try to copy all files included in the zip so all lib and lib64 to /system and /vendor.
If pixel experience is aosp/lineage based, it should work.
Android 8+ natively supports aptx(HD) and expects the drivers in /system/lib64 or /vendor/lib64.
As soon as they're present, aptx should work.

If you want to, you could try LineageOS it's a very similar experience to stock android and will definitely work with aptx libs
I tried again to install aptx & aptxhd in my xiaomi mi A1 phone but failed. I just came across a XDA post wherein in addition to transferring aptx & aptxhd lib files to device, it said to edit build.prop file with some codes pulled from device using abd command & twrp. The codes are : persist.bt.enable_aptxHD=true, persist.service.btui.use.aptex=1, persist.vendor.d2ap_offload_cap=sbc-aac-aptx-aptxhd. Kindly advice. Thanks.
 

multiwirth

Senior Member
Dec 17, 2013
738
268
93
Gerstetten
www.youtube.com
I tried again to install aptx & aptxhd in my xiaomi mi A1 phone but failed. I just came across a XDA post wherein in addition to transferring aptx & aptxhd lib files to device, it said to edit build.prop file with some codes pulled from device using abd command & twrp. The codes are : persist.bt.enable_aptxHD=true, persist.service.btui.use.aptex=1, persist.vendor.d2ap_offload_cap=sbc-aac-aptx-aptxhd. Kindly advice. Thanks.
The build.prop edit is only needed for android 7 (anything below this doesn´t support aptx at all except oem roms with preinstalled aptx).
On anything from oreo and up should natively support aptx as soon as the lib files are present.

You can still try to flash magisk and install the zip as module and if this doesn´t work, you can simply uninstall magisk either by flashing boot.img from your rom or running the uninstaller zip for magisk.
You can even disable superuser inside magisk, so it will only load the modules.
Since it´s systemless (no tampering to /system at all) it will be OTA compatible and survive OTA´s aswell (including all installed modules).
 

akd06

Member
Apr 17, 2018
34
1
8
The build.prop edit is only needed for android 7 (anything below this doesn´t support aptx at all except oem roms with preinstalled aptx).
On anything from oreo and up should natively support aptx as soon as the lib files are present.

You can still try to flash magisk and install the zip as module and if this doesn´t work, you can simply uninstall magisk either by flashing boot.img from your rom or running the uninstaller zip for magisk.
You can even disable superuser inside magisk, so it will only load the modules.
Since it´s systemless (no tampering to /system at all) it will be OTA compatible and survive OTA´s aswell (including all installed modules).
Thanks for your reply. Is there any possibility that pixel experience plus rom which my device currently running, completely removed the aptx & aptxhd drivers for the sake of better LDAC codec by the developer? My rom is based on android 10 which out of box supports only sbc & hd codec LDAC in bluetooth implementation. How do I sure that aptx & aptxhd driver present in my system? Any file details for those driver so that I can search for? Any such drivers you can provide. Waiting for your valuable feedback. Thanks.
 

multiwirth

Senior Member
Dec 17, 2013
738
268
93
Gerstetten
www.youtube.com
Thanks for your reply. Is there any possibility that pixel experience plus rom which my device currently running, completely removed the aptx & aptxhd drivers for the sake of better LDAC codec by the developer? My rom is based on android 10 which out of box supports only sbc & hd codec LDAC in bluetooth implementation. How do I sure that aptx & aptxhd driver present in my system? Any file details for those driver so that I can search for? Any such drivers you can provide. Waiting for your valuable feedback. Thanks.
I don´t have much info about LDAC but since it´s showing up in developer settings, i assume it´s aswell supported by AOSP out of the box.
I don´t have a LDAC compatible headset and it ´s some Sony proprietary stuff as far as i know, pretty unusual that you have it.
Anyways both APTX and LDAC should be able to co exist but chances are high,the LDAC drivers are integrated to the bluetooth stack itself just the way APTX-HD is integrated on official LineageOS on my OnePlus 3t so there are no files you could explore, it´s coded in source code on the bluetooth stack itself.

I may have a look if i can get Pixel Experience plus on my HTC One M9 and check it´s behavior (in LineageOS it supports the aptx libs just fine).
 

NEWTINGZ

Member
Mar 12, 2019
12
1
3
Hey Helllo :asking
What would the module do to android 6 ? ,oem Huawei rooted/unlocked magisk
Just By chance ,like Just spitballing you know :sneaky:
 

multiwirth

Senior Member
Dec 17, 2013
738
268
93
Gerstetten
www.youtube.com
Hey Helllo :asking
What would the module do to android 6 ? ,oem Huawei rooted/unlocked magisk
Just By chance ,like Just spitballing you know :sneaky:
Honestly, i expect it to do nothing, Android 6 doesn´t support aptx out of the box and i actually tried to find a way to get it working on my s3 mini running android 6 but no chance.
You need at least Android 7 to get aptx(HD) but this module won´t work on Android 7, needs a few more modifications in build.prop and someone who can test it as i do no longer have a device running old android 7.

I may add android 7 one day if there´s demand for it.
 

akd06

Member
Apr 17, 2018
34
1
8
I don´t have much info about LDAC but since it´s showing up in developer settings, i assume it´s aswell supported by AOSP out of the box.
I don´t have a LDAC compatible headset and it ´s some Sony proprietary stuff as far as i know, pretty unusual that you have it.
Anyways both APTX and LDAC should be able to co exist but chances are high,the LDAC drivers are integrated to the bluetooth stack itself just the way APTX-HD is integrated on official LineageOS on my OnePlus 3t so there are no files you could explore, it´s coded in source code on the bluetooth stack itself.

I may have a look if i can get Pixel Experience plus on my HTC One M9 and check it´s behavior (in LineageOS it supports the aptx libs just fine).
Hi, I have decided to flash custom rom of lineage 17.1 os to my xiaomi mi A1 device. What wil be the best gapp pkg for lineage os? After installing the rom, I will flash your aptxhd pkg for getting aptxhd. Kindly advice. Thanks.