Related
Hi,
I just got my Google WiFi 3-kit and it seems that the channel they work on (149) wasn't supported in my country (NL) so I made a simple Magisk module to change the region to [EU]
This 'fix' is simpy a change to "wifi-service.jar" which can be located in /system/framework/
Source: https://github.com/thomasvt1/extendwifi
DOWNLOAD
Updates v7
Update OOS to 4.5.10
Add support for Magisk v14.0
Special thanks to:
- https://forum.xda-developers.com/pixel/themes/mod-wifi-country-code-fix-root-required-t3558044
Would there be any benefit to flashing this if I'm in the US, or do they all have the NL flag?
The wifi region is selected based on the SIM in your phone. Most people won't need this, care, or notice.
Second, this is probably illegal since it changes your phone to use frequencies that are not allowed in the users home country. Is anyone going to get caught or in trouble for this? Unlikely. But it also won't be useful unless you've purchased hardware that broadcasts on frequencies not allowed in your country. IE, Google WiFi hasn't been released in Europe yet and doesn't officially follow EU frequency range. Which is why it's useful for @Thomasvt but not for anyone else.
@PokemonTotalWar: Long answer? No.
@PokemonTotalWar: For US users, probably not, except if you use channel 12/13 from the 2.4GHz spectrum. > https://en.wikipedia.org/wiki/List_of_WLAN_channels
@Raharazod Actually Google WiFi is released in the EU. (France, Germany and the UK) http://www.androidpolice.com/2017/06/26/google-wifi-may-coming-france-monday/ as for my country. All Apple products, and my laptop happily use the 5GHz network without any modification except my OnePlus 5.
Thomasvt said:
@Raharazod Actually Google WiFi is released in the EU. (France, Germany and the UK) http://www.androidpolice.com/2017/06/26/google-wifi-may-coming-france-monday/ as for my country. All Apple products, and my laptop happily use the 5GHz network without any modification except my OnePlus 5.
Click to expand...
Click to collapse
OH! I thought it was still pending release over here. Wasn't really keeping a close eye.
Well it shouldn't.
There ARE 5Ghz bands that are allowed in the EU, just not all of them. I was assuming that your module enabled ones that weren't otherwise allowed.
I've got my phone bootloop
Thomasvt said:
Hi,
I just got my Google WiFi 3-kit and it seems that the channel they work on (149) wasn't supported in my country (NL) so I made a simple Magisk module to change the region to [EU]
This 'fix' is simpy a change to "wifi-service.jar" which can be located in /system/framework/
Source: https://github.com/thomasvt1/extendwifi
DOWNLOAD
Updates v7
Update OOS to 4.5.10
Add support for Magisk v14.0
Special thanks to:
- https://forum.xda-developers.com/pixel/themes/mod-wifi-country-code-fix-root-required-t3558044
Click to expand...
Click to collapse
After installing module I've got my phone bootloop. May you define place for the original wifi-service.jar file during module installation.
Thanks, Kinger
Kinger1970 said:
After installing module I've got my phone bootloop. May you define place for the original wifi-service.jar file during module installation.
Thanks, Kinger
Click to expand...
Click to collapse
Just use 'magisk mount' and remove it from /magisk.
What O2OS are you running?
Thank you for quick response
Thomasvt said:
Just use 'magisk mount' and remove it from /magisk.
What O2OS are you running?
Click to expand...
Click to collapse
Thank you, restored system easily. Problem I'm not running O2OS system on phone I've crashed, installed on different phone by mistake.
Thank you, cheers!
I got another Problem on oreo closed beta 2.
After update from 4.5.14 my 5ghz wont connect with settings in router auto channel..
This means channels 36 above until 52 wont work.
If i sett a special channel like 52 above my 5ghz wifi connects to my op5..
Did OnePlus messed something up?
Located in Germany op5 A5000
Hi Dimontiman,
Have you tried with the official OxygenOS Open Beta 1? Since leaked closed beta 1 and 2 were not made for public and lots of bugs.
Did it give any errors when adding the module in Magisk?
If still doesn't work on official open beta 1, then perhaps an update to this module would be required perhaps.
keepasa said:
Hi Dimontiman,
Have you tried with the official OxygenOS Open Beta 1 (8.0)?
Click to expand...
Click to collapse
Yes both open beta 1 and xlosed beta 2
Same Wifi Problems
I do have a Oxygen (leaked build 1) version on my github: https://github.com/thomasvt1/extendwifi/tree/4.5.2 (just download as zip).
I haven't been able to get smali working yet with the open beta 1. I'm not sure if the closed beta one works on the open beta.
Edit: My version from git still does work with the open beta 1. Just tested.
Edit2: New updated version for Open Beta 1: https://github.com/thomasvt1/extendwifi/tree/O2_Open1 [just downoad zip and use in magisk]
Thomasvt said:
I do have a Oxygen (leaked build 1) version on my github: https://github.com/thomasvt1/extendwifi/tree/4.5.2 (just download as zip).
I haven't been able to get smali working yet with the open beta 1. I'm not sure if the closed beta one works on the open beta.
Edit: My version from git still does work with the open beta 1. Just tested.
Edit2: New updated version for Open Beta 1: https://github.com/thomasvt1/extendwifi/tree/O2_Open1 [just downoad zip and use in magisk]
Click to expand...
Click to collapse
Hey
Appreciate your work, what does your module change exactly?
Additional to OP
Dimontiman said:
Hey
Appreciate your work, what does your module change exactly?
Additional to OP
Click to expand...
Click to collapse
It changes just one file; https://github.com/thomasvt1/extendwifi/tree/O2_Open1/system/framework
And then just the setCountryCode method as per this guide;
https://forum.xda-developers.com/pixel/themes/mod-wifi-country-code-fix-root-required-t3558044
open beta is supported?
enskje said:
open beta is supported?
Click to expand...
Click to collapse
https://github.com/thomasvt1/extendwifi/archive/O2_Open1.zip
This is for Open Beta 1
Small update for Openbeta 1 - the region didn't apply every boot so I fixed that;
https://github.com/thomasvt1/extendwifi/archive/O2_Open1.zip
Thomasvt said:
Small update for Openbeta 1 - the region didn't apply every boot so I fixed that;
https://github.com/thomasvt1/extendwifi/archive/O2_Open1.zip
Click to expand...
Click to collapse
Hey can you update this version to magisk repo as i cant use the zip on magisk
Dimontiman said:
Hey can you update this version to magisk repo as i cant use the zip on magisk
Click to expand...
Click to collapse
Sorry the magisk repo version will only be the stable version of OxygenOS.
Maybe try a file explorer to select the zip, I know ES File Explorer works when using the 'file way' and not the 'normal android way'.
I hope this helps!
Thomasvt said:
Sorry the magisk repo version will only be the stable version of OxygenOS.
Maybe try a file explorer to select the zip, I know ES File Explorer works when using the 'file way' and not the 'normal android way'.
I hope this helps!
Click to expand...
Click to collapse
If i flash the zip from twrp, can stock be afterwards restored? I mean to uninstall
Hello!
First sorry if my English is basic, because im French ^^
Yup, so i open this thread cuz i want to be sure to find the right version before install Xposed on my phone.
I found that i need SDK23 on web but i dont know if it's right and if it's a ARM or ARM64 and im really not sure then i prefer ask here before make a bull****
I'm actually on Meizu Pro 6 (not Pro 6 plus) on last Flyme 6.3.0.0G (but i use Nova Prime launcher) and my phone is rooted from Meizu roots setting.
(Edit: it's Android 6.0, Processor is a "MTK MT6797" and Graphic chip "ARM Mali T880 MP4")
I want to install Xposed to use the advanced setting from some of my apps like Greenify and take a look to the other possibility but before install Xposed i want to know something, actually (if necessary) i can flash my meizu with recovery mod to come back to factory without any problems (i already make it after roots to make a fresh install with unrooted flyme) so i wanna ask, if i install Xposed can i still use recovery mod if needed a day?
Thanks in advance and sorry if the answer was already on this forum, i have search but don't find for Pro 6
Click to expand...
Click to collapse
Back & hi,
Ok so if someone look a day for the same thinks, i have find the solutions and the answer to all my question on the Meizu groups by ChatDexter on Telegram.
So for the Meizu Pro 6 (not plus) you just need to roots your phone with the simple way of Flyme :
* It's 100% safe and easy and you still can use recovery mode (press power+up volume to start your phone and when vibrate, press 2 time volume up to open recovery) after reboot to unroot if needed one day don't be afraid..
And if you don't know how to root the Meizu Pro 6 it's very easy :
Open "Parameter" and go to -> "Fingerprints and security" then enter and follow step on "Administrator authorization" read/accept and reboot; after that you will be roots (you can use the free apps Root Checker Basic) to see the roots work fine..
Ok so now for xposed framework you need XposedInstaller v3.1.1 (APK), there is the link :
[add manually the SSL]mega.nz/#!SI0DwJoY!kgbtYOZScUfub7aPVLu7s9t7qwL4MsG7Ga-DhHEnSWQ
*receive directly from an admin of Meizu groups of Telegram and upload to my mega.
(EDIT : im new on forum and after writing all my post i see than i can't post a link after post minimum 10 msg with my account to previent spam.. i understand but for this post it's really sad.. than im sorry, but to post link i have remove the https : // before my 3 link of the post, just add it manually to open it and i hope xda moderator will undertand and i hope fix it , if not sorry im new on xda.. if someone need the link add me on Telegram at "Orbit4L")
*And im not 100% sure but i thinks it's only for the Meizu Pro 6, in any case it work perfectly for my Pro 6 (with flyme 6.3.0.0G rooted).
Ok so after download, you just need to launch the apk, the installer will automatically detect your device to find the last version of xposed framework, you must see that on "YOUR DEVICE" detection :
#1 Android 6.0 (Marshmallow, API 23)
# 2 Meizu PRO 6
#3 arm64
Click to expand...
Click to collapse
if you don't see that it's than you are not on Meizu Pro 6 so stop this tutorial immediately..
If it's okay first verify your battery level is ok (personally i have make that with 100% to be safe)
Then now you can press INSTALL/UPDATE button, a dialog box will appear, wait few time and after 3/4 line you will see "Done" (if it's not done it's than you have not pro 6 roots or make something wrong in the step, idk im not an pro but for me all was perfect the first try..)
Ok then now in the bottom of this dialog box you will see a message for reboot your system, wait the countdown or press reboot directly..
Your phone will reboot and when Flyme loading logo will appear dont worry if it take few min (not really long, i thinks 2/3max for me) and after that you will see a status 0->100% for xposed installer optimize your apps for xposed (just wait without make anything) and when 100% is done flyme will start just fine as always, unlock your sim/phone pass, and you will see your phone start as always with all your apps exactly like before start the XposedInstaller apk, but now, Xposed is installed and work fine
open it and you must see that :
[add manually the SSL]i.imgur.com/io5Tqo2.jpg
And here you can start using the application by adding your modules
For proofs here is my Greenify Pro plug-in finally installed and fully functional
[add manually the SSL]i.imgur.com/YjloCHS.jpg
Here, i know that many of you are perfectly comfortable with xposed, but for those like me who want to install it for the first time, (on a Meizu Pro 6 in any case) it can seem complicated and warnings can scare, that's why after a long search, then directly ask advice to Admin of Meizu groups from Telegram and then performed the procedure on my own Pro 6 (Not Pro 6 Plus^^), i decide to share this tutorial that i hope again will not violate no rules of the XDA Forum and give a big pleasure to interested people :good:
Looking forward android friends and thx to xda for this awesome Forum (even if i found the solution elsewhere, i know than Pro 6 is not on last phone and meizu not the best way for xposed :silly
Hi there,
I use/used to use CrossBreeder lite ( Github / XDA ), and it hasn't been updated in awhile by its developer. You can no longer install it if your Magisk version is greater than v16.3. The actual module works fine, that code doesn't need to be touched, as it works fine on my device on v18.1 (which had the module installed since v15), it's just the installation part that needs to be updated. I'm trying to update it using the latest Magisk Module Template, but I'm having some issues. I never made a Magisk module/Android app before. I got it to install, but, it's basically just a blank module, it won't install the actual main files (/sbin/.magisk/img/<module>/system/*). My updated repo is here, if an experienced dev could look at my newest commit and maybe tell me what I'm doing wrong, or missing/forgetting, or any other help would be highly appreciated. Thanks!
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?