I'm wondering if it is possible to run a kernel with KCAL support on a Verizon-functional ROM such as Viper.
Specifically, LeeDroid kernel has support for KCAL but LeeDroid ROM doesn't have support for Verizon devices yet.
Would flashing LeeDroid kernel work on Viper or stock-based ROM?
If anyone wants to know, I would like to run the m9 KCAL (to compensate for the poor stock color calibration) at the same time as with aptx support (I don't know of an AOSP ROM with support for aptx in the audio stack).
So, KCAL + aptx, I wonder if its possible?
xdadevnube said:
I'm wondering if it is possible to run a kernel with KCAL support on a Verizon-functional ROM such as Viper.
Specifically, LeeDroid kernel has support for KCAL but LeeDroid ROM doesn't have support for Verizon devices yet.
Would flashing LeeDroid kernel work on Viper or stock-based ROM?
If anyone wants to know, I would like to run the m9 KCAL (to compensate for the poor stock color calibration) at the same time as with aptx support (I don't know of an AOSP ROM with support for aptx in the audio stack).
So, KCAL + aptx, I wonder if its possible?
Click to expand...
Click to collapse
This *might* work.
andybones said:
This *might* work.
Click to expand...
Click to collapse
Unfortunately, I don't have an m9 to try it out on. I was thinking of upgrading the the m9, I'm just trying to figure out what this thing is capable of. If LeeDroid ends up supporting Verizon (stated that there has been no time to implement Verizon support in the thread), then it might be good to go.
One problem is that I believe a logcat is required to verify aptx support (and must actually connect to an aptx device, AFAIK), so most people probably don't pay attention to whether aptx is working.
Stock ROMs work, but every single AOSP/GPE ROM on the m8 doesn't support aptx (I checked with Catlog app).
xdadevnube said:
Unfortunately, I don't have an m9 to try it out on. I was thinking of upgrading the the m9, I'm just trying to figure out what this thing is capable of. If LeeDroid ends up supporting Verizon (stated that there has been no time to implement Verizon support in the thread), then it might be good to go.
One problem is that I believe a logcat is required to verify aptx support (and must actually connect to an aptx device, AFAIK), so most people probably don't pay attention to whether aptx is working.
Stock ROMs work, but every single AOSP/GPE ROM on the m8 doesn't support aptx (I checked with Catlog app).
Click to expand...
Click to collapse
The kernel may work on a Verizon ROM, while he works on support as well.
Interesting. I can see if its working on a few ROMs if wanted - just need to know how. We don't have gpe, I wish there was a m9 gpe. But cm13 is stable.
Stock sense ROMs are nice as well
Related
I'm already s-offed, unlocked bootloader, on MM firmware and MM Leedroid.
Not using Android pay, so I have SuperSU installed.
Is there a way to install Viper Audio along with ZeroInfinity's sound mod without any conflict?
And also, I saw a lot of Viper variants and got a little bit confused. Which one works best with HTC 10 in your opinion?
Any help is appreciaed
BrianKuo1853 said:
I'm already s-offed, unlocked bootloader, on MM firmware and MM Leedroid.
Not using Android pay, so I have SuperSU installed.
Is there a way to install Viper Audio along with ZeroInfinity's sound mod without any conflict?
And also, I saw a lot of Viper variants and got a little bit confused. Which one works best with HTC 10 in your opinion?
Any help is appreciaed
Click to expand...
Click to collapse
As far as I know, there is no conflict.
What the ZeroInfinity's sound mod touches is only the HTC BoomSound profiles. Which also work when unmodified.
Meaning, V4A should work as normal (but will need different tuning based on whatever BoomSound profile you have selected).
I tried it once, but I didn't fancy it.
I can't say which is best, I believe that also falls on preference and what earbuds or whatever you use for audio.
Ariac Konrel said:
As far as I know, there is no conflict.
What the ZeroInfinity's sound mod touches is only the HTC BoomSound profiles. Which also work when unmodified.
Meaning, V4A should work as normal (but will need different tuning based on whatever BoomSound profile you have selected).
I tried it once, but I didn't fancy it.
I can't say which is best, I believe that also falls on preference and what earbuds or whatever you use for audio.
Click to expand...
Click to collapse
Did you installed the apk and it works well? The driver doesn't install properly on my phone :/
BrianKuo1853 said:
Did you installed the apk and it works well? The driver doesn't install properly on my phone :/
Click to expand...
Click to collapse
Nope, I flashed it.
Get the latest flashable V4A.
If you have any errors, check out this thread.
Ariac Konrel said:
Nope, I flashed it.
Get the latest flashable V4A.
If you have any errors, check out this thread.
Click to expand...
Click to collapse
Finally got it working! Thanks a lot!
Does anybody know of any ROM/Custom that actually has advanced calling working for the Verizon HTC One M9
Gmoney1988 said:
Does anybody know of any ROM/Custom that actually has advanced calling working for the Verizon HTC One M9
Click to expand...
Click to collapse
Two that I've tried and work for me on my Verizon M9 ---
@Golv 's Port ROM from HTC10 ICE to our M9
https://forum.xda-developers.com/showpost.php?p=67358627&postcount=2164
I'm running this right now and VoLTE works properly - problem is I restored from a backup because when I tried to reflash clean version I got stuck at setup screen - easier to just restore backup instead of trying to figure out why.
and...
@LeeDroid 's One M9 V8.3.0-Stable.zip
http://www.leedroid.co.uk/Stable
sidjohn said:
Two that I've tried and work for me on my Verizon M9 ---
@Golv 's Port ROM from HTC10 ICE to our M9
https://forum.xda-developers.com/showpost.php?p=67358627&postcount=2164
I'm running this right now and VoLTE works properly - problem is I restored from a backup because when I tried to reflash clean version I got stuck at setup screen - easier to just restore backup instead of trying to figure out why.
and...
@LeeDroid 's One M9 V8.3.0-Stable.zip
http://www.leedroid.co.uk/Stable
Click to expand...
Click to collapse
OK I will check those out. Thank you
Running LeeDroid's here and as sidjohn mentioned, Advanced Calling does work. Viper's older build, 4.3.0, has it as well. Viper had a 5.x.x series that was based off of an M10 port, so it didn't work. Their latest, proper M9 Nougat based, doesn't have it though....
I don't believe that any non-HTC-based build, i.e. Cyanogen, Lineage, etc has it working.
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?
I'm interested in getting Moto Mods (especially the jbl mod, which keeps many users from custom roms) working on custom roms. Other moto devices can do it, so it should be possible for our moto z play too.
@TeamMex got it working in his Nougat rom, partially on his oreo rom. So there is a chance.
What is needed for working mods? I see Moto Mods Manager and My JBL Soundboost apps on my phone that i can link to my mod. Is there something needed in the system? I read about audio routing? Isn't that anything else than routing audio to bluetooth or to headphones?
McFlypants said:
I'm interested in getting Moto Mods (especially the jbl mod, which keeps many users from custom roms) working on custom roms. Other moto devices can do it, so it should be possible for our moto z play too.
@TeamMex got it working in his Nougat rom, partially on his oreo rom. So there is a chance.
What is needed for working mods? I see Moto Mods Manager and My JBL Soundboost apps on my phone that i can link to my mod. Is there something needed in the system? I read about audio routing? Isn't that anything else than routing audio to bluetooth or to headphones?
Click to expand...
Click to collapse
Frameworks base, frameworks native, frameworks av, system core, libiio, greybus drivers, and sepolicy is needed to make it work, about JBL it need to use prebuilt audio binary.
TeamMex said:
Frameworks base, frameworks native, frameworks av, system core, libiio, greybus drivers, and sepolicy is needed to make it work, about JBL it need to use prebuilt audio binary.
Click to expand...
Click to collapse
Could this probably help? It's working here on griffin
The pdf is also refering on addison
McFlypants said:
Could this probably help? It's working here on griffin
The pdf is also refering on addison
Click to expand...
Click to collapse
yup if you know how to do that
I'm not able to do this because i don't know that much about building android roms.
Why is it possible on griffin and not on addison?
Is there a way to have LDAC bluetooth codec back?
I have Android 9, many months ago was available from Developer Menu, but with latest security patches, it does not work anymore: you can select LDAC from Developer Options but the settings disappear as soon as you get out from the menu.
Before it worked (I have Sony MD-1000X headphone which supports LDAC).
nicosea said:
Is there a way to have LDAC bluetooth codec back?
I have Android 9, many months ago was available from Developer Menu, but with latest security patches, it does not work anymore: you can select LDAC from Developer Options but the settings disappear as soon as you get out from the menu.
Before it worked (I have Sony MD-1000X headphone which supports LDAC).
Click to expand...
Click to collapse
Hello there I am Lacia the official maintainer of posp my latest official build includes the LDAC bluetooth codec so feel free to try it out! you can also join our telegram group over at https://t.me/pospdaisy
I have the same problem, and don't really care about installing a custom rom.
Any help?
nicosea said:
Is there a way to have LDAC bluetooth codec back?
I have Android 9, many months ago was available from Developer Menu, but with latest security patches, it does not work anymore: you can select LDAC from Developer Options but the settings disappear as soon as you get out from the menu.
Before it worked (I have Sony MD-1000X headphone which supports LDAC).
Click to expand...
Click to collapse
On stock, not even AAC Bluetooth can be selectable after like April 2019 update version (my father's Pioneer car system does have AAC BT mode). It can be selected in Dev Opts, but after you exit the option, it will revert back to SBC (normal) mode and also the audio did not changed too. I guess it's another bug by Xiaomeme that haven't fixed.
...and I have moved out to just using custom ROMs long ago, then these modes (AAC, APTX, etc.) works as intended.
RFD80M-75679 said:
On stock, not even AAC Bluetooth can be selectable after like April 2019 update version (my father's Pioneer car system does have AAC BT mode). It can be selected in Dev Opts, but after you exit the option, it will revert back to SBC (normal) mode and also the audio did not changed too. I guess it's another bug by Xiaomeme that haven't fixed.
...and I have moved out to just using custom ROMs long ago, then these modes (AAC, APTX, etc.) works as intended.
Click to expand...
Click to collapse
Could you tell me which custom ROM / ROMs are you using with Mi A2 Lite to have Aptx and LDAC back (and where to find these ROMs)?
Thank you
nicosea said:
Could you tell me which custom ROM / ROMs are you using with Mi A2 Lite to have Aptx and LDAC back (and where to find these ROMs)?
Thank you
Click to expand...
Click to collapse
On POSP (and I think many AOSP-based ROMs), it managed to activate the AAC Bluetooth automatically with my father's car stereo. On virtually any Android Pie custom ROMs, most can switch modes to APTX (when I did have the KZ Earphones Bluetooth module with APTX, now dead due to my KZ BT module's capacitor died suddenly).
Ok, I managed to keep stock rom and add at least aptx support with unlocked bootloader + magisk + magisk modules.
Just hope that Xiaomi will fix this with Android 10 update
Matyt said:
Ok, I managed to keep stock rom and add at least aptx support with unlocked bootloader + magisk + magisk modules.
Just hope that Xiaomi will fix this with Android 10 update
Click to expand...
Click to collapse
Any guide or instructions to do that? I'm not so experience with ROMs and magisk...
If I understood you well I need to:
- unlock bootloader
- install magisk and than magisk modules (I can Google)
But no need for root rights and a full custom ROM like POSP, correct?
And no support for Ldac anyway?
nicosea said:
Any guide or instructions to do that? I'm not so experience with ROMs and magisk...
If I understood you well I need to:
- unlock bootloader
- install magisk and than magisk modules (I can Google)
But no need for root rights and a full custom ROM like POSP, correct?
And no support for Ldac anyway?
Click to expand...
Click to collapse
Magisk is a rooting tool (like SuperSU) and using modules need root (but custom ROM isn't needed if you just want stock). You need an unlocked bootloader, Magisk manager APK, a patched boot.img (should be matched your stock version 10.0.x.0) and some steps to have it rooted.
https://forum.xda-developers.com/mi...gisk-proper-support-ota-t3836952/post77498252
I unlocked the bootloader using this:
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-unlock-bootloader-losing-user-data-t4053743
Then installed magisk using this:
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952 (scroll until the end of the thread to find the jan 2020 patched .img)
And then, installed a magisk module for aptx.
No LDAC for now.