Related
arm64 is now officially supported: See here
Old OP
Hello Everyone,
I have successfully compiled Xposed for android 5.1.x for arm64 devices.
I have so far tested this on my Nexus 9 running a custom CyanogenMod based Android 5.1 ROM with SELinux disabled (It may work on ROM's with SELinux enabled but testing has to be conducted.).
Install zip is attached to this post. (The SDK 22 one) This will only install Xposed framework for Android 5.1 for arm64 devices. Please see the original Lollipop post to get the other files you need. (Hint: you only need the Xposed APK from that post.)
I compiled this based off of @romracer's source code for Xposed on Android 5.1.x.
So far I have tested the module Lolistat, It seems to be working well.
Please be patient during boot, let your device boot 10 minutes before reporting that it is "bootlooping"
====================
For Android 5.0.x
I have also compiled Xposed for Android 5.0.x for arm64 devices. I have had mixed results from testers so far. The install zip is also attached to this OP (The SDK 21 one). Many HTC M9 users have reported this caused a boot-loop for them. This will only install Xposed framework for Android 5.0.x for arm64 devices. Please see the original Lollipop post to get the other files you need. (Hint: you only need the Xposed APK from that post.)
Remember to always backup all data before using. Use at your own risk.
Please note: There will most likely be arm64 related bugs with both of these. See this post for more information.
Please be patient during boot, let your device boot for 10 minutes before reporting that it is "bootlooping"
just in case...
I got a new m9 in the box, thinking about waiting to activate it since xposed wouldn't work on it yet.
Sim-X said:
I got a new m9 in the box, thinking about waiting to activate it since xposed wouldn't work on it yet.
Click to expand...
Click to collapse
I could also compile Xposed arm64 for android 5.0 if there is enough interest.
Sim-X said:
I got a new m9 in the box, thinking about waiting to activate it since xposed wouldn't work on it yet.
Click to expand...
Click to collapse
Somebody would need to be willing to test, but I could try to compile Xposed for it.
Well, if you're willing to test and support it, you can post unofficial files for testing...
I have a Nexus 9 with Android 5.0 myself and it's running fairly well. I haven't used any complex modules though.
Be aware that 64-bit ROMs need different handling in a couple of places and break some expectations. For example, initZygote() will be executed twice, as there are two app_processXX processes now. Modules might not expect this. I also didn't succeed to enforce a certain startup order of the processes (app_process64 before app_process32) yet, so results might be a bit random. There are probably more differences like this and it's generally more complex than on 32-bit ROMs. That's why I have only posted files for ARM so far. On the other hand, if you're willing to look into issues that come up (e.g. installation problems, crashes, things that are not working) and do some pre-analysis, that's fine and could bring the project forward. If nothing to major comes up, I can then also include official files with the next version. Additional support would be very welcome anyway.
Framework installation zip attached to OP.
good
Only for 5.1?
auggie246 said:
Only for 5.1?
Click to expand...
Click to collapse
I made a version for android 5.0 but I would need somebody to test it before I release it.
5.0 for samsung galaxy s6 ?
koko115 said:
5.0 for samsung galaxy s6 ?
Click to expand...
Click to collapse
Are you kidding? Move along!
subscribed.
Feel free to post any problems you have with this here. (arm64 related problems)
Rastapop 5.1 on n9 with selinux on. I can install xposed fine but rebooting after enabling YouTube adaway and gravitybox causes a never ending boot logo
YouTube adaway works fine
For me
Guitarboarder28 said:
Rastapop 5.1 on n9 with selinux on. I can install xposed fine but rebooting after enabling YouTube adaway and gravitybox causes a never ending boot logo
Click to expand...
Click to collapse
From my understanding, gravitybox is not compatible with Android 5.1 at all.
joshuabg said:
From my understanding, gravitybox is not compatible with Android 5.1 at all.
Click to expand...
Click to collapse
Ohhh didn't even think about that. Would make sense
Thanks for taking this on, joshuabg. I couldn't believe it when I saw this thread. I thought that 5.1 jumped the arm64 shark and we'd never see xposed for N9.
Anyway, I flashed on AICP 4/6 with FireIce K8.3, SELinux disabled and it booted just fine. Tried the following modules, and I see what rovo meant in his post above. It's really hit or miss with the modules just like the [SUPER ALPHA] xposed for 32 bit arm devices. Thanks again for rolling this out to test.
YouTube Adaway - seemed to work, jumped to dozens of random videos and no ads
Minmin Guard - app opened and seemed to operate normally but I think it may have blocked ads across the board without my telling it to do so. I think it also caused an XDA Free force close on opening that wouldn't go away
Swype Tweaks - caused Swype to FC anytime the keyboard should have launched
Yup my bad. Gravitybox says right in the description it'll cause a boot loop on 5.1. Everything is working perfectly. Thanks!
Thats my first productive creation for XDA, so dont be to hard to me
I don't like to have features, which I never use, so I always disable or remove everythink i dont need.
On my custom roms I always diable the multi user mode by adding the following line to the build.prop:
Code:
fw.max_users=1
I was annoyed to edit this file after each ROM update.
So I created this module. It just adds the above mentioned line to the build.prop.
It is really simple, but now I don't need to edit the build.prop.
Maybe for someone this can be useful.
It works with:
- Android 6.x (Tested on OnePlus X and OnePlus 3 with CM13)
- Android 7.x (Tested on LOS 14.1 and OxygenOS 4.5.x)
v1.3: Update to Magisk Template 1400 (14.0).
Looks good but I would change the modid to something other than template. This is in the config.sh file and defines the folder it uses under /magisk. Anyways I used your zip as a template for my own build.prop edits that I will post shortly. I'll throw a little credit your way too.
Sorry, I was on vacation and than really busy...
@shinji257: Thank you for the hint. I changed it and uploaded the mod as v 1.1.
And actually I found already a similar magisk module created by user @FHC1998:
https://forum.xda-developers.com/apps/magisk/magisk-multiuser-enable-disable-t3552643
dima-82 said:
Sorry, I was on vacation and than really busy...
@shinji257: Thank you for the hint. I changed it and uploaded the mod as v 1.1.
And actually I found already a similar magisk module created by user @FHC1998:
https://forum.xda-developers.com/apps/magisk/magisk-multiuser-enable-disable-t3552643
Click to expand...
Click to collapse
That module probably still works (haven't updated it since posted) but the Magisk template is not updated.
My module does pretty much the same thing as yours, there is only one more line on the prop that I add.
fw.show_multiuserui=0
This disable all the UI and configurations sections for multiuser. Its not obligatory, but for me it makes sense to disable the interface aswell if you are disabling the function.
You can add that if the multiuser options keep showing even after disabling multiuser.
FHC1998 said:
That module probably still works (haven't updated it since posted) but the Magisk template is not updated.
My module does pretty much the same thing as yours, there is only one more line on the prop that I add.
fw.show_multiuserui=0
This disable all the UI and configurations sections for multiuser. Its not obligatory, but for me it makes sense to disable the interface aswell if you are disabling the function.
You can add that if the multiuser options keep showing even after disabling multiuser.
Click to expand...
Click to collapse
When I looked for the build.prop settings to disable multi user functionality I found the mentioned line as well.
But I cannot see any difference if I add it. At least it has not effect on my phone (OnePlus 3, CM13).
dima-82 said:
When I looked for the build.prop settings to disable multi user functionality I found the mentioned line as well.
But I cannot see any difference if I add it. At least it has not effect on my phone (OnePlus 3, CM13).
Click to expand...
Click to collapse
It depends on the device, I originally tested on a few, and some needed this line.
For instance, I tested your module on my device (ZenFone 2 laser) and it worked perfectly without the line, but on my friend's ZenFone 2 it kept showing the UI even though not allowing creating more users.
@dima-82 Module works great for me. I'm running a OP3T on offical LineageOS. All the multiuser stuff is gone from the settings and notification shade.
Sent from my ONEPLUS A3000 using Tapatalk
mp3deviant721 said:
@dima-82 Module works great for me. I'm running a OP3T on offical LineageOS. All the multiuser stuff is gone from the settings and notification shade.
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
Thanks for the feedback.
The official LineageOS for OP3T is Android 7.x? Nightly builds?
dima-82 said:
Thanks for the feedback.
The official LineageOS for OP3T is Android 7.x? Nightly builds?
Click to expand...
Click to collapse
The build I'm running is 7.1.1. Haven't tried 7.1.2 yet. Yes on the "nightly" build.
Sent from my ONEPLUS A3000 using Tapatalk
@dima-82,
Hello, I used your module to enable multi user mode, all I did is edited the file inside the .zip where the string to disable the multi user mode is located, and replaced it with the two strings to enable it.
Now I was wondering since this works, could I make a thread with the mod?
I would obviously credit You, and link to Your profile and this thread.
Here is the module on my device :silly:
dariomrk said:
@dima-82,
Hello, I used your module to enable multi user mode, all I did is edited the file inside the .zip where the string to disable the multi user mode is located, and replaced it with the two strings to enable it.
Now I was wondering since this works, could I make a thread with the mod?
I would obviously credit You, and link to Your profile and this thread.
Click to expand...
Click to collapse
Of course you can do.
But as mentioned in post #3 there was already a similar module. I think it does exactly what you need.
dima-82 said:
Of course you can do.
But as mentioned in post #3 there was already a similar module. I think it does exactly what you need.
Click to expand...
Click to collapse
Oh, I didn't see that, I will check if it does the exactly same thing (probably yes)...
---------- Post added at 03:06 PM ---------- Previous post was at 03:05 PM ----------
Just checked it out, and yes it does the exactly same thing
Please I need multiuser enable magisk module for Android 6
dima-82 said:
And actually I found already a similar magisk module created by user @FHC1998:
https://forum.xda-developers.com/apps/magisk/magisk-multiuser-enable-disable-t3552643
Click to expand...
Click to collapse
Here
Got bootloop after the install of this module.
Device: Zuk Z2
ROM: AEX 4.4
Unofficial Magisk 13.2 (170716)
I am running it on official Magisk 13.2 without any issues.
Did you also install other modules?
dima-82 said:
I am running it on official Magisk 13.2 without any issues.
Did you also install other modules?
Click to expand...
Click to collapse
Yes have other 5 modules
You installed / activated only this very one module and got a bootloop?
Before I created this module I edited the build.prop manually. And if you make a mistake there, you will get a bootloop as well.
May be your OS does not support this property.
I tested on my devices only, and it worked always.
Eventually you can try an other module from @FHC1998, which should do the same:
https://forum.xda-developers.com/showpost.php?p=71936097&postcount=3
jhobc said:
Got bootloop after the install of this module.
Device: Zuk Z2
ROM: AEX 4.4
Unofficial Magisk 13.2 (170716)
Click to expand...
Click to collapse
You could eventually try this mod:
https://forum.xda-developers.com/apps/magisk/module-single-user-mod-t3639486#post73160966 by @seebz
As the Android ecosystem has matured over the years, fewer and fewer users find reasons why they should root their device. There’s a growing trend of users choosing to stay on the stock firmware, either because they find the experience satisfactory or don’t want to play a cat-and-mouse game with Google’s SafetyNet API. But if you asked a user back in early 2016 why they rooted their phones, perhaps the number one reason that was given was so they could install the Xposed Framework. It’s been over a year since Android 7.0 Nougat was first released, but the long wait is finally over: official Xposed Framework for Android Nougat is finally available.
Why install the Xposed Framework?
Want to get custom ROM features without flashing a custom ROM? The mother of all Xposed Modules for tweaking your ROM, known as GravityBox, has you covered. Want to customize display settings on a per-app basis? Try App Settings. How about customizing certain applications like Hangouts? Or modifying Instagram so you can download whatever posts you like?
posed gives developers the ability to modify pretty much whatever they want—mostly aimed at individual applications but even system-wide features can be modified. The examples we listed is just the tip of the iceberg. The number of additional features you can add or apps you can modify is incredible—just search through the official Xposed Module repository to see for yourself. Keep in mind that some modules might need to be updated for this new release and for Nougat support, so be sure to check before installing them on your Nougat ROM!
How do Xposed Modules work?
The gist of it is that the Xposed Framework allows modules to “hook” into the Java methods of any application—be it user-installed or a system application. Xposed lets modules execute their own methods before, during, or in place of the original methods of the target application.
For instance, imagine a method used in the Gmail application that posts notifications for new emails. By default, the method creates a new notification with buttons to archive/delete or reply to the email. A Xposed Module could be made to hook into this method and add a new button such as “mark as read.” (Yes, there’s already a Module for just that.)
The above is an over-simplification of the end result of what the Xposed Framework allows its modules to do. The Framework itself is incredibly complex and making it work nearly universally on rooted devices—without needing a custom ROM—is why Xposed for Android Nougat has taken so long to complete. *install at your own risk, I'm not responsible for anything you do to your device.
Source link:
XDA
https://www.xda-developers.com/official-xposed-framework-android-nougat/
https://forum.xda-developers.com/showthread.php?t=3034811
Xposed
http://repo.xposed.info/
Installation:
Download the xposed zip file and flash it in recovery (framework files)
Now install the xposed apk
Reboot mobile
*dont open the app before installing the zip
Download link:
xposed-v88.2-sdk24-arm64.zip (7.0)
http://dl-xda.xposed.info/framework/sdk24/arm64/
xposed-v88.2-sdk25-arm64.zip (7.1)
http://dl-xda.xposed.info/framework/sdk25/arm64/
Xposed 3.1.4.apk
https://forum.xda-developers.com/attachment.php?attachmentid=4319220&d=1509453299
Download any module of your choice
http://repo.xposed.info/module-overview
What's the point of this thread? Is it just to get a few likes? Xposed is well known and people should refer to the original Xposed thread.
Besides your instructions are wrong.. and please be careful of which framework you use.. on stock it is sdk24 on other customers roms it depends on the Android version.
spunxhoe said:
What's the point of this thread? Is it just to get a few likes? Xposed is well known and people should refer to the original Xposed thread.
Besides your instructions are wrong.. and please be careful of which framework you use.. on stock it is sdk24 on other customers roms it depends on the Android version.
Click to expand...
Click to collapse
I use what I want, you don't want to take care about me and this thread., head to the source link to read the full thread that's all.
I think it's a good idea to share the magisk's modules we have installed.
-mi A1 gcam
-youtube vanced
Google lens enabler
Google sans mod font
HAL3 enabler
iOS11.1 emoji
Unified hosts adblock
YouTube vanced
Android O APT-X libraries: Android Oreo officially supports APT-X bluetooth audio, however not all phones have the needed library files. This module simply places the missing APT-X(HD) and LDAC files in your system if you don't already have it. Enjoy better bluetooth audio!
Busybox for Android NDK: As a byproduct of building my own static busybox compiles in all supported Android architectures for my AIK-mobile package I figured I might as well offer them up separately as well since there weren't any providers making Android x64 builds when I was researching. The installer detects what architecture (ARM/ARM64, x86/x86_64, MIPS/MIPS64) your device uses and installs the correct busybox binary accordingly. It then cleans up any symlinks from a possible previous installation in the same directory and generates new symlinks directly from the output of the installed binary. Detects and supports "systemless" root via SuperSU/Magisk installation as well.
Systemless Xposed: This is a port of rovo89's Xposed framework to work systemless-ly through Magisk.
SDK 27 (Android 8.1)
AirAudio - stream your music!
Android O APT-X libraries
Audio Compatibility Patch
Mi Mix 2 Snapchat Volume Fix
Unified Hosts Adblock
ViPER4Android FX Materialized
Magic Charging Switch (mcs)
kremmit said:
Android O APT-X libraries: Android Oreo officially supports APT-X bluetooth audio, however not all phones have the needed library files. This module simply places the missing APT-X(HD) and LDAC files in your system if you don't already have it. Enjoy better bluetooth audio!
Busybox for Android NDK: As a byproduct of building my own static busybox compiles in all supported Android architectures for my AIK-mobile package I figured I might as well offer them up separately as well since there weren't any providers making Android x64 builds when I was researching. The installer detects what architecture (ARM/ARM64, x86/x86_64, MIPS/MIPS64) your device uses and installs the correct busybox binary accordingly. It then cleans up any symlinks from a possible previous installation in the same directory and generates new symlinks directly from the output of the installed binary. Detects and supports "systemless" root via SuperSU/Magisk installation as well.
Systemless Xposed: This is a port of rovo89's Xposed framework to work systemless-ly through Magisk.
SDK 27 (Android 8.1)
Click to expand...
Click to collapse
Did you installed Xposed on MIUI?
Adriano-A3 said:
Did you installed Xposed on MIUI?
Click to expand...
Click to collapse
No I haven't anymore. But at the time of writing i had and it was working.
Why do you ask?
kremmit said:
No I haven't anymore. But at the time of writing i had and it was working.
Why do you ask?
Click to expand...
Click to collapse
I'm going to install it on MIUI 9.5.8.
Adriano-A3 said:
I'm going to install it on MIUI 9.5.8.
Click to expand...
Click to collapse
I'm on RR rom and it worked ok.
Adriano-A3 said:
I'm going to install it on MIUI 9.5.8.
Click to expand...
Click to collapse
Did it work for you? I'm still on 9.1 because I need Xposed.
kurtextrem said:
Did it work for you? I'm still on 9.1 because I need Xposed.
Click to expand...
Click to collapse
I didn't try. I sold my Mix 2.
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