Hi Guys,
As many of you may know, there is a common issue with all aosp roms, at least, all I've checked, related to the bluetooth.
For those who doesn't know what i'm talking about, the problem is this: while calling using any BT headset / car kit, the phone app freezes After the second / third call and you will no longer hear anything Until reboot.
Well, I've checked several roms, and all of them have the same issue.. I just would like to share this information and ask If someone has found any aosp rom that works correctly.
I've checked omnirom, slimkat, probam, paranoidandroid... and all of them have the problem. Of course, I tested using latest version available (03-01-14), fresh clean install, stock kernel, etc...
After flashing OTA update Phoenix ROM 16.7 i noticed that i couldn't send files thru bluetooth. Tried 3rd party bluetooth file transfer from playstore and its working but the built in bluetooth won't sends files. Phoenix ROM 16.0 bluetooth was fine i didn't face any issue(s) but current version of ROM had bluetooth issue. Does someone encountered this problem?Please give me idea to fix this problem..
I have the same problem, i cant pair my headset, bluetooth doesnt work on phoenix 16.7 and ditto 3.2, what to do ?? On hurricane v8 bluetooth works.
Hello guys and girls,
I wanted to go back to the good old jellybean 4.3.x roms which were declared as 'stable' releases and i ve installed the viper4android app.
The driver installation went fine until after reboot that there is no audio effect working.
I ve been trying with the latest viper version 2.3.3.0 on every jellybean 4.3.x roms and the same problem occured.
I want to have the viper4android working as normal mode. The compatible mode is partially working on some players and i mostly listen to the internet radio called tuneIn. obviously the audio effects on that isnt working, even being in compatible mode.
Is there any possible workaround or fixes or even any methods to get the audio effects working there? Or is it only a child' s desease on all provided jb 4.3.x roms that the audio effects arent working??!
Thanks in advance
Sent from my LG-E980 using XDA Free mobile app
So I have been trying to get LDAC or apt-X working on my razer phone but it has not worked. I am on the latest stock ROM rooted with magisk (via ADB not TWRP) and with the rayglobe magisk module installed but it just stays on AAC. My headphones are Sony WH-1000XM2 and LDAC was working when using the resurrection remix ROM from the development thread but I had to uninstall the ROM due to instability and no sign of progression. Any help would be appreciated.
Firebuster said:
So I have been trying to get LDAC or apt-X working on my razer phone but it has not worked. I am on the latest stock ROM rooted with magisk (via ADB not TWRP) and with the rayglobe magisk module installed but it just stays on AAC. My headphones are Sony WH-1000XM2 and LDAC was working when using the resurrection remix ROM from the development thread but I had to uninstall the ROM due to instability and no sign of progression. Any help would be appreciated.
Click to expand...
Click to collapse
They locked it down somehow I think. I have 2 threads in here asking for help but no one seems to be able to help me. For added reference, here is the error produced even when all the files are added with root to enable aptx or ldac
I installed the magisk aptx&aptxHD module and modified /system/vendor/build.prop then aptx got working.
(I couldn't test with aptxHD or LDAC cos I have no compatibe device with them.)
Code:
persist.vendor.bt.a2dp_offload_cap=sbc-aac
to
Code:
persist.vendor.bt.a2dp_offload_cap=sbc-aptx-aptXHD
This is the same parameter the magisk module set to /system/build.prop.
To guess, LDAC will may work if an appropriate value set to the prop.
ClubRaptor said:
I installed the magisk aptx&aptxHD module and modified /system/vendor/build.prop then aptx got working.
(I couldn't test with aptxHD or LDAC cos I have no compatibe device with them.)
to
This is the same parameter the magisk module set to /system/build.prop.
To guess, LDAC will may work if an appropriate value set to the prop.
Click to expand...
Click to collapse
This worked to enable switching to them however now Bluetooth just crashes. I changed it to persist.vendor.bt.a2dp_offload_cap=sbc-aptx-aptxhd-ldac
Edit:
Some interesting notes. I tried a few steps to debugging including readding AAC to the list which did nothing but if I only add aptx then the Bluetooth app no longer crashes however no sound plays so I'm guessing it's the lib files that are not correct? I just used the aptx package in magisk so if there's any other that I'm missing or other suggestions that would be useful
Firebuster said:
This worked to enable switching to them however now Bluetooth just crashes. I changed it to persist.vendor.bt.a2dp_offload_cap=sbc-aptx-aptxhd-ldac
Edit:
Some interesting notes. I tried a few steps to debugging including readding AAC to the list which did nothing but if I only add aptx then the Bluetooth app no longer crashes however no sound plays so I'm guessing it's the lib files that are not correct? I just used the aptx package in magisk so if there's any other that I'm missing or other suggestions that would be useful
Click to expand...
Click to collapse
I still can't get it to switch to aptx (the one I want) or ldac. It still falls back to SBC usually or aac if I'm on a different speaker. Any idea what I'm doing wrong? I'm on slot a on my device, rooted with magisk and I have tried multiple aptx modules. Is there a specific build.prop editor you use? Both my speakers and headphones support it and work with other devices and I'm still getting the error I replied with above (page one)
I'm an experienced rooter, so don't be afraid to fully explain any steps I may be missing out!
manor7777 said:
I still can't get it to switch to aptx (the one I want) or ldac. It still falls back to SBC usually or aac if I'm on a different speaker. Any idea what I'm doing wrong? I'm on slot a on my device, rooted with magisk and I have tried multiple aptx modules. Is there a specific build.prop editor you use? Both my speakers and headphones support it and work with other devices and I'm still getting the error I replied with above (page one)
I'm an experienced rooter, so don't be afraid to fully explain any steps I may be missing out!
Click to expand...
Click to collapse
I used root explorer and changed the build.prop entries in system\vendor\. In the first place I used the root essentials build.prop editor which shows a different build.prop. other than that I literally just edited that line and that allowed me to change it. I can't think of anything else I did other than install a bunch of library files which I'm guessing you found the same ones as me because it was very limited on what was available and up to date
Firebuster said:
I used root explorer and changed the build.prop entries in system\vendor\. In the first place I used the root essentials build.prop editor which shows a different build.prop. other than that I literally just edited that line and that allowed me to change it. I can't think of anything else I did other than install a bunch of library files which I'm guessing you found the same ones as me because it was very limited on what was available and up to date
Click to expand...
Click to collapse
OK, awesome. You rock. That got it to select aptx - now my 2nd problem, no audio! I can see in dev options and bt settings that it's showing aptx, but I get no audio (well, I get an almost click click click noise) then my Bluetooth adaptor for my headphones crashes. And it forces my headphones to turn off. I tried 3 different magisk modules for the library files, any ideas - I was getting SBC audio before
manor7777 said:
OK, awesome. You rock. That got it to select aptx - now my 2nd problem, no audio! I can see in dev options and bt settings that it's showing aptx, but I get no audio (well, I get an almost click click click noise) then my Bluetooth adaptor for my headphones crashes. And it forces my headphones to turn off. I tried 3 different magisk modules for the library files, any ideas - I was getting SBC audio before
Click to expand...
Click to collapse
Sounds like the same problem I am having. Aptx doesn't work and aptx HD and LDAC just crash Bluetooth. Genuinely have no idea where to go from here. It must be a driver or library file. Real shame it's not working.
Edit: seems to be looping these messages in catlog
Firebuster said:
Sounds like the same problem I am having. Aptx doesn't work and aptx HD and LDAC just crash Bluetooth. Genuinely have no idea where to go from here. It must be a driver or library file. Real shame it's not working.
Click to expand...
Click to collapse
OK, so last night and this morning I have been just messing with things. I no longer crash my headphones and force them to turn off, but I still have no audio over aptx - though at least it's not crashing my headphones (Bluetooth in the phone was always OK). There is one error I'm getting and I'm not sure if its related of not, but is to do with a buffer failing to release. See my screenshots of logs (just documenting here for reference)
so basically i went your path a few days ago and dropped that idea. please post updates if you manage to get aptx\aptx hd\ldac working (Razer Phone + Sony WH-1000 XM2)
hatemosphere said:
so basically i went your path a few days ago and dropped that idea. please post updates if you manage to get aptx\aptx hd\ldac working (Razer Phone + Sony WH-1000 XM2)
Click to expand...
Click to collapse
Cc @Firebuster
So, I might be an experienced rooter (no 1 click toolkits here) I am NOT a developer. I've tried a combination of a bunch of things to try and get this to work, and nothing has!
I did however get it to work by installing a GSI (basically a rom) to the device, but even that was painful to get working (well, installed). Now running AOSP 8.1 GSI w/gapps and I flashed magisk for root. I then installed the Aptx magisk module from the built in repo and it works perfectly fine. Not sure if It's something in razer software as I'm technically more up to date now so it's not like I was using the wrong drivers.
Can't find a decent dolby atmos I can install that will work along side v4a, all the magisk modules are for android 7 or 6.
Otherwise that's the only way I have found so far, sorry guys! - benefit is, other than AOSP's ****ty camera app (use the gcam port instead), literally everything works fine, and I even get stronger vibration on a GSI
manor7777 said:
Cc @Firebuster
So, I might be an experienced rooter (no 1 click toolkits here) I am NOT a developer. I've tried a combination of a bunch of things to try and get this to work, and nothing has!
I did however get it to work by installing a GSI (basically a rom) to the device, but even that was painful to get working (well, installed). Now running AOSP 8.1 GSI w/gapps and I flashed magisk for root. I then installed the Aptx magisk module from the built in repo and it works perfectly fine. Not sure if It's something in razer software as I'm technically more up to date now so it's not like I was using the wrong drivers.
Can't find a decent dolby atmos I can install that will work along side v4a, all the magisk modules are for android 7 or 6.
Otherwise that's the only way I have found so far, sorry guys! - benefit is, other than AOSP's ****ty camera app (use the gcam port instead), literally everything works fine, and I even get stronger vibration on a GSI
Click to expand...
Click to collapse
Yeah I might move onto that too. To try to fix the Bluetooth issues. I can only assume razer excluded some of the functionality but since it's baked into android 8 I don't see why they would remove it.
Razer and their development team is already informed about this issue, and they have correctly addressed it, and all the Bluetooth issues (which were a few), in the upcoming update MR2. No ETA.
linuxct said:
Razer and their development team is already informed about this issue, and they have correctly addressed it, and all the Bluetooth issues (which were a few), in the upcoming update MR2. No ETA.
Click to expand...
Click to collapse
so i've just got a new update and now i'm wondering if we should try this again...
hatemosphere said:
so i've just got a new update and now i'm wondering if we should try this again...
Click to expand...
Click to collapse
Go ahead, I can't since I'm on a Pie GSI.
If anyone has an LDAC BT Headset please give this a try.
cc @Firebuster
Great news, I just spent 2 hours updating my phone, with flashing back to stock because the OTA did not want to update me since I had Magisk, then putting everything back like before.
The update did not change anything.
Tried to do my research on issues with the Razer phone before getting it, but I guess this is just one of those things you don't comprehend until actually having the device in your hands. I came from a Oneplus One on Lineage OS and am comfortable with flashing (but no experience with GSI yet).
My razer phone is stock and not rooted. Anything I can do to contribute to test getting Apt-X working? The settings says my phone is up to date (build number OPM1.171019.011-RZR-180803.6033).
Got the official Pie installed - no LDAC nor AptX still.
cubeover said:
Got the official Pie installed - no LDAC nor AptX still.
Click to expand...
Click to collapse
you installed the official pie update for the razer phone 1?
hello, a few months ago I put a GSI on my moto G30 (ArrowOS), I actually liked this GSI a lot... but I can't use some phone functions like bluetooth and headphones on the P2 output...
I use headphones a lot and I was using one with a USB Type-C output but this headphones is having some problems and I want to go back to using my JBL bluetooth headphones that I stopped using because it doesn't connect with my cell phone...
But I don't remember how to put a GSI and I don't even know a good one that I can have a good performance on battery and in games...
Can someone help me?
Hi. GSI performance doesnt varry that much if at all so pick any you like best.
Look at phhusson's GSI List to find a GSI that is compatible
(Must be a higher or equal Android version to the one your phone has stock and the GSI shoud be A/B and arm64)
Your problems sound quite generic and are mentioned in the GSI Troubleshooting FAQ
Such as:
Wired headphones not getting detected.Solution 1Enable alternative headphones detection in phh settings and reboot
This one ^ worked for me and should work for you too i believe.
Bluetooth connecting to device and then disconnectingTry disabling A2DP offload in phh settings
I've tried this too but cant remember if it worked, what works for me is going to the Bluetooth settings for the device and disabling HD Audio.
You can find more fixes on the link above.
About installing the GSI first flash the stock ROM and then follow Sammm77's GSI Flashing Guide.
You can try ArrowOS again with the fixes above and see if they work or pick another GSI.
If you need any clarifications i would be more than happy to help!
KAN7A said:
Hi. GSI performance doesnt varry that much if at all so pick any you like best.
Look at phhusson's GSI List to find a GSI that is compatible
(Must be a higher or equal Android version to the one your phone has stock and the GSI shoud be A/B and arm64)
Your problems sound quite generic and are mentioned in the GSI Troubleshooting FAQ
Such as:
Wired headphones not getting detected.Solution 1Enable alternative headphones detection in phh settings and reboot
This one ^ worked for me and should work for you too i believe.
Bluetooth connecting to device and then disconnectingTry disabling A2DP offload in phh settings
I've tried this too but cant remember if it worked, what works for me is going to the Bluetooth settings for the device and disabling HD Audio.
You can find more fixes on the link above.
About installing the GSI first flash the stock ROM and then follow Sammm77's GSI Flashing Guide.
You can try ArrowOS again with the fixes above and see if they work or pick another GSI.
If you need any clarifications i would be more than happy to help!
Click to expand...
Click to collapse
man, you really helped me alout...
i tried these two methods
-Enable alternative headphones detection in phh settings and reboot
-Try disabling A2DP offload in phh settings (in this case I restarted the phone too)
and both starting working again