Related
On my rooted "samsung galaxy S4 active" (GT-i9295) ... I have been happy with the cm-12.1-20160822-NIGHTLY-jactivelte.zip ... until I used it for telephoning now
The microphone level is really really low. The person on the other end can hardly understand me. And the soundrecorder also has very very low volume.
There are workarounds. I have googled a lot, and found instructions how to root-edit files in /system/ - which all did not help, because one file from the workaround wasn't even existing in my device.
There seems to be another way, using STweaks, but for the above mentioned cm-12.1-... it says "Sorry, no kernel support".
So I am looking for alternatives, please help. Some ideas:
a completely different ROM than the cm-12.1-20160822-NIGHTLY-jactivelte.zip - any chance for an Android 6.0.1 anytime soon?
a different kernel which is compatible with i9295 and my (seems to be newest?) CM12.1, with which I can use STweaks or something similar
another app which allows to change the mic boost level
an instructions manual for cm12.1 which tells me which system files to edit how
your way - what else could I do?
Thanks a lot!
Try CM13.1 https://drive.google.com/drive/u/0/mobile/folders/0B7vmsLnZghSUZ0o0aEtLNUdYR1E
Hello everyone..
am I new here, ók, yes, but you should help me because you maybe the only one can help.
So, I'm with my lovely s3mini tried several ROMs but finally I'm on resurrection remix, my problem its can't run spirit FM radio don't [email protected] that I have to configure it or try with it anymore...I'm not so noon...
8 have seen @lot of mods shipping a working FM app with it but surely failed to use any of it in that ROM, at least most libraries come from 7.1.2 open source project different from native or modded to custom ui or anything..
@nyway, please developers, I need your help, i need one of theese working apps with libraries it uses to get FM works in a flashable zip file, to know I have full [email protected] my mobile so try anything manners. Thanks all in advance.
ahmeddalloul said:
Hello everyone..
am I new here, ók, yes, but you should help me because you maybe the only one can help.
So, I'm with my lovely s3mini tried several ROMs but finally I'm on resurrection remix, my problem its can't run spirit FM radio don't [email protected] that I have to configure it or try with it anymore...I'm not so noon...
8 have seen @lot of mods shipping a working FM app with it but surely failed to use any of it in that ROM, at least most libraries come from 7.1.2 open source project different from native or modded to custom ui or anything..
@nyway, please developers, I need your help, i need one of theese working apps with libraries it uses to get FM works in a flashable zip file, to know I have full [email protected] my mobile so try anything manners. Thanks all in advance.
Click to expand...
Click to collapse
Read this & this to get fm radio. Also a bedtime reading here, about the "thanks in advance".
mauam said:
Read this & this to get fm radio. Also a bedtime reading here, about the "thanks in advance".
Click to expand...
Click to collapse
Really thank you friend, I've tried many versions from @Round..but its the only working one...but I noticed that the other versions became able to access fm,,no accessible fm,,is no more shown,...as if it should be unlocked first...but..again..I should unlock again " open it with that version mentioned" then go to other...so I deleted them..now I'm with working spirit FM app.
That's good, but I wanted the version @LREady come with stock on my 7.1.2 android from one [email protected] developers
. ..
At @ll, thank you very much...sorry for my English...
Feel free to correct me, I'm still learning, and thanks for understand.
New build up at sx.ix5.org, use version 2018-10-30.
Changelog here: https://sx.ix5.org/changelog.html
Install guide: Flashing AOSP on Xperia XZ
XDA:DevDB Information
AOSP Pie based on Sony Open Devices Project, ROM for the Sony Xperia XZ
Contributors
local__hero, fastbooking, oshmoun
Source Code: https://git.ix5.org/felix/local-manifests-ix5/src/branch/ix5-customizations
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: .184 / .192
Based On: AOSP
Version Information
Status: Nightly
Created 2018-11-09
Last Updated 2019-05-17
Reporting bugs
Important: Read the bug list before posting. Anyone can add bugs to the list, just follow the rules.
If you have questions, ask them in this thread: Xperia XZ Pie ROMs Questions and Answers Thread
Don't make me ask you for logs every time!
I will repeat the rules again here:
Rules:
New bugs must include version where error popped up and which oem version you are using
Only reproducible errors
Should include adb logcat (linked in a pastebin service like https://del.dog)
Must include clear description what is wrong
If it is a visual/SystemUI bug, only report it here
If it is an internal bug(e.g. fingerprint crashes device), report it to the Sony bugtracker as well!
Always try to fix the bug yourself first! Then submit a pull request to Sony
Must search if error has already been reported (bug tracker, this document, dev buglist)
If you've reported the issue somewhere else already and just want to track it here as well, add a link
Before reporting a bug, always make sure to isolate it. That means, wipe everything, install only the ROM without GApps and Magisk and see if the problem still exists. Only then report the bug!
---
If you have questions, ask them in this thread: Xperia XZ Pie ROMs Questions and Answers Thread
---
In 9.11
1. Everything still works
2. Charging with plugged at screen off works
3. On gcam portrait mode and night photo gives purple glitched image
And phone seems to be faster.
Bug: 9.11 with oem v2- Clean install
- Hotspot not working
- Phone call issue - Mic and speaker not working, cannot hear anything or say anything << Listed in the bug
- Top speaker not working
Still testing.
An update
Yes, we know calling is kinda broken right now on both oem versions. Yes, we know you have problems with dualsim devices because you didn't flash the dualsim patcher. Yes, battery life isn't very good because we are testing out some increased CPU frequencies so video doesn't stutter. (you can go back to the 11-05 build which has the old CPU freqs and compare).
We're aware of a lot of these issues, and they are all tracked in the current buglist (see post #2).
Development happens mostly in the Sony open devices program, with a few heroic volunteers contributing. Right now, a lot of work is being done to get the current flagships(think XZ2, XZ3) to a semi-stable state, but work for our device is done as well.
You can check progress in the sonyxperiadev repos. E.g. recently, some changes to the telephony HAL integration have been made, see the common device repo.
Why is it taking so long to fix all this?
Sony buys many of their processors from Qualcomm. Lots of stuff in phones is proprietary and covered in patents, and you can only get the source code if you sign an NDA. So even if Sony wanted to, they could not release the source for a lot of things.
See all the files with the name "qti" in them? That's Qualcomm Technologies, Inc. See all the repos named something like "qcom-something-something"? That's Qualcomm.
When there's a problem, we have to report it to Sony, who report it to Qualcomm. This takes time already. And don't forget Qualcomm has suppliers as well, and so on and so on. The same is true for other parts, e.g. the Wi-Fi chips are from Broadcom.
Then, support for hardware stuff is on many levels. A lot of low-level drivers that are driving the hardware are on the /odm partition(the one that the oemv1/v2 blobs get flashed to). Then there is work to be done tweaking the actual hardware abstraction layer(HAL) interfaces that work with these driver blobs. Then there are kernel drivers that can go wrong and mess up. Then it can be a problem somewhere higher up in the Android frameworks. Lots of detective work.
If new blobs from Qualcomm come out, Sony itself needs to do some testing, and then releases a new oem version. It won't just magically work, we need to tweak the SODP vendor side as well. It could be as easy as changing a version to a newer one, but it could also be a lot harder. The sonyxperiadev crew knows what's needed to integrate these new blobs, but it still takes time and testing.
Qualcomm provide the a lot of the source code to work with their hardware and blobs from the higher-level Android side in their CodeAurora forum (CAF) repositories. The relevant changes then get merged into the sonyxperiadev repos and we can test if it works(or if something new is broken...).
For more info, read the Android documentation on hardware etc.
The chip in our phone, the MSM8996, is quite old already(even the SDM845 in the XZ2/3 is already quite old in processor standards). We can be luck that Qualcomm still provides support. But it's not a priority to them, they want to sell new
ones of course. That is also a reason updates can take longer.
Regarding full forced-reboot crashes:
Sadly, as of now, for some people the "/sys/fs/pstore" folder does not get populated after a crash. This is important to diagnose what happened.
You can apply this patch to force a kernel panic on every reboot, but I would recommend that you do
so only if you know what you are doing.
Regarding battery life:
Please install BetterBatteryStats
and find out what is draining the battery.
This could really help us out! But first, make sure you are not running any GApps, because the Google Mobile Services are a massive pile of battery drain.
If you absolutely have to use GApps, please run only the "pico" GApps version!
---
About the posts here:
Like 90% of posts here and in the old thread are full of people who just plain refuse to read, asking how to install or demanding someone help them out with something that has already been answered time and time again. This makes it extremely annoying for the us who have to scroll through pages of useless stuff to find the genuine bug reports. You do realize this site is literally named "xda-developers", right? If you're unclear on the concept, please read this: https://forum.xda-developers.com/showpost.php?p=16682226&postcount=2441
"This doesn't work!" - "This thing crashes!" - That gives us almost no clue what is happening. We need logs, or we can't do anything about it. I have only one phone, and I only use the stock ROM. There are a lot of nice testers who send others and me helpful bug reports, with detailed explanations in what circumstances it occured, with proper logs.
With that info, the Sony open devices team and us can actually look into issues.
So please, if something doesn't work AND we are not aware of it yet, post it to the bug list (not here!) and attach a link to a log that you uploaded, e.g. to a service like hastebin.com.
nhicko95 said:
how is battery life?
Click to expand...
Click to collapse
Test it out, please. And don't forget to report the diagnosed battery stats.
DarkPrinciple said:
I should be able to get to 12 lunch with my battery being more than 50%
Click to expand...
Click to collapse
I've tweaked for more performance right now, but you can use 11-05 to get old CPU freqs. Also, please help hunt down what is draining the battery, it's most likely too many held wakelocks, but it could be any number of things.
bihslk said:
So what is the latest and best working version of this rom?
Click to expand...
Click to collapse
It's literally in the first post.
bihslk said:
Rom is pretty OK but really annoying top speaker bug. Only lower one works.
Click to expand...
Click to collapse
That is already in the bug list. Please read the bug list before posting.
Update 2018-11-16
Some new developments are happening.
Oem binaries version 3 are out. This should give improved power management. The SODP team has also worked on getting audio handling during calls to work. A big thanks to oshmoun for his work on the audio manager. This change was introduced on the 11-15 build. The issue of no call audio when a bluetooth headset is connected is still present as of now.
Changed IRQ handling (PR by Angelo/"kholk"). This should give better battery life and maybe faster wakeup from deep sleep. But could also lead to instabilities and crashes. Send logs & pstore, see post #2. This change was introduced on the 11-15 build.
Testing kernel 4.9.137 i in progress (we are currently on .103). This means stability and security enhancements from upstream linux. Thanks to Nathan Chance who opened this pull request..
But some of those upstream changes might be incompatible with our Sony kernel, so we have to test that. Send logs & pstore, see post #2. This change was introduced in the 11-16 build. If the 11-15 and 11-16 builds are unstable, revert to an older one. But please be brave and run them for at least a day to get us logs of potential crashes.
---
optixperiaa said:
I am always confused about "flash latest stock ftf" part about roms as a newbie.. if we flash sony's ftf how can we flash rom ? isnt it overwrite ?
Click to expand...
Click to collapse
Your phone software is made up of many layers. The ROMs like omni or this AOSP-based one only modify your /system and /boot partitions.
But when you update your stock firmware via flashtool, you also update your phone modem firmware, your qnovo charging controller firmware, your lower-level bootloaders etc. That is why we instruct you to update to the latest stock firmware. You could theoretically skip flashing /system in flashtool(because it will get overwritten anyway, as you've already discovered) and directly flash a custom ROM afterwards.
When you're coming from omni, there is no need to flash stock firmware again in between, because your other partitions stay the same. Just a new /oem is needed.
viori said:
flash omni_kagura-2018-11-20_UNOFFICIAL_TESTBUILD-2
Click to expand...
Click to collapse
Again, please keep this thread about development for AOSP. The omni builds are not meant for you.
If you have trouble installing then simply don't use it.
DO NOT POST HERE FOR HELP OR YOU WILL BE REPORTED. Read everything before posting.
If you have questions, ask them in this thread: AOSP 9.0 Pie builds for F8331/F8332
The OP has requested that you do not post questions in this thread, please use the thread he states in the OP to do that.
If you have questions, ask them in this thread: AOSP 9.0 Pie builds for F8331/F8332
Click to expand...
Click to collapse
Thanks
Thread cleaned
General update
Newer builds will have selinux set to "enforcing". Most denials should have been fixed or are irrelevant. If you encounter any problems, selinux-related or anything else, please report them to the Sony bugtracker or - even better - submit a pull request to the selinux-policy repo.
Update 1: vendor blobs aren't binderized correctly atm, so no network. You can set selinux back to permissive to fix most issues atm.
The Wi-Fi hotspot has been fixed thanks to oshmoun. In newer builds, it should be using less battery.
Next thing we're going to tackle is deep sleep and battery drain. Big pain point and one of the last blockers, apart from the camera and bluetooth in-call audio.
You might have noticed that the omnirom device trees have been updated to 9.0. Nightly testing builds work fine, but they have the same issues as the AOSP-based ones.
Work is also under way to get a Pie-based TWRP recovery stable, with support for FDE encryption(this means that you will be able to back up your encrypted installations). Mounting /userdata works, but the builds are not ready for public release yet.
Update
New build up (2018-12-08)
Camera key works
Update to December security patch(12-05, r21)
Fingerprint should not crash device on enrollment any more
Allow setting lower minimum brightness
Double-tap-to-wake off by default(but can be enabled)
Plugging in charger with screen off should be fixed
Once again, I invite anyone who would like to help out or just learn a bit about building and tweaking to take a look at the sources posted here.
There will be a guide on how to build only the kernel and experiment with a custom boot.img shortly.
The build guide on sx.ix5.org for reproducing these AOSP builds should bring you up to speed, and if you need help building or just want to chat, the telegram group in post #1 is open to you.
local__hero said:
New build up (2018-12-08)
Camera key works
Update to December security patch(12-05, r21)
Fingerprint should not crash device on enrollment any more
Allow setting lower minimum brightness
Double-tap-to-wake off by default(but can be enabled)
Plugging in charger with screen off should be fixed
Once again, I invite anyone who would like to help out or just learn a bit about building and tweaking to take a look at the sources posted here.
There will be a guide on how to build only the kernel and experiment with a custom boot.img shortly.
The build guide on sx.ix5.org for reproducing these AOSP builds should bring you up to speed, and if you need help building or just want to chat, the telegram group in post #1 is open to you.
Click to expand...
Click to collapse
Great job.
I already built a custom Pie kernel about a week ago to gain better performance but the charging bug was driving me insane :crying:
I guess now's the time to go back to the mighty Pie and try building a nice and hopefully stable Marrow Kernel.
Cheers
Finally a new build is out!
I can't pass safety net on latest build.
Any ideas what should I use ?
Since modules for spoofing fingerprint simply don't work.
I tried universal safety net fix but with no avail.
V 12.15
Charging working fine. But i have problem with camera, photos are very dark.
Sometimes touch screen not working and i need to switch the screen and on again.
ov2rey said:
Sometimes touch screen not working and i need to switch the screen and on again.
Click to expand...
Click to collapse
Disable Dt2w
oem v4 is out
DahakePL said:
Disable Dt2w
Click to expand...
Click to collapse
Thank you It's work!
Layns said:
oem v4 is out
Click to expand...
Click to collapse
i am testing v4 on latest build aosp_f8331_2018-12-21-NIGHTLY-permissive.
Screen unable to display after update to oem v4
https://developer.sony.com/file/download/software-binaries-for-aosp-pie-android-9-0-kernel-4-9-tone/
ov2rey said:
Thank you It's work!
i am testing v4 on latest build aosp_f8331_2018-12-21-NIGHTLY-permissive.
Screen unable to display after update to oem v4
https://developer.sony.com/file/download/software-binaries-for-aosp-pie-android-9-0-kernel-4-9-tone/
Click to expand...
Click to collapse
I tried it works fine but the camera sucks and the sound is bad, the screen opening with double tap is running slow, the charge is a little quick
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?