Develop Bugs

ViPER4Android on HTC 10

Hey guys,
was anybody of you able to install ViPER4Android on HTC 10 7.0 Nougat?
There is an official Nougat version released, the apk run's perfectly, nonetheless the app everytime returns that the audio drivers need to be updated/installed. After pressing "yes", my phone tells me the audio drivers were installed and I need to reboot the phone.
After the reboot the same message that there is the need to install the sound drivers?! Tried it a few times now.
And yes, my phone is rooted.
... and would you say it would make a difference to install ViPER4Android even if the Boomsound of the HTC 10 is already pretty nice?!
Thanks guys....

Hi,
It is necessary the version 2.5.0.5 and in Zip, not in Apk!
Diverse file are needed to work.
It is integrated into my Rom Pyrana NO7-0.8 with Dolby.
@+

In my honest opinion, A.R.I.S.E can do the same as what Viper4Android can do except it actually has huge device support.
I used to use it but I now don't need it due to an upgrade of the speakers I was connecting it to, works almost identically and can sometimes fix the secondary speaker that doesnt work on some ROMs. nothing third-party seems to be better optimized for boomsound though, the standard is usually the nicest sounding.

LDAC 8.1

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?

[Mod/Magisk] Dolby Atmos™ [A9-12 ][OOS A10 + A11 Custom](Updated 6-25-21) full brightness fixes

So recently @guitardedhero release and version of Dolby atmos for android Pie and i was excite about it but it only for for android pie only,so i try downgrade back to 9.0.17 but apparently the mod cause the phone go straight to crashdump mode and like hour ago he release couple more version but i was already on android 10 but after messing around with flash script i was able flash it on OOS10 imma attach the file i mod here for specific only for OOS10 only since this the only version that work flawless on OOS10 other test version i try they either force close the app or audio loss, highly recommended flash it along with Ainur Narsil---haven't test with other mod yet but in my opinion Dolby itself already better
https://forum.xda-developers.com/android/software/app-dolby-atmos-axon-7-oreo-port-t3740508​
UPDATE: latest dolby re-port by reiryuki fixes full brightness issue working on (maybe)all custom rom available now for Oneplus 6t and maybe other device has FOD custom rom ! please head to his github repo link below for the download!
Download
Credit:
@guitardedhero (for The Port)
-Me (for testing and mod the file to work on OOS10)
-Reiryuki for the fix and new port
-Dolby (for Dolby Atmos)

_BГ@ckθut said:
So recently @guitardedhero release and version of Dolby atmos for android Pie and i was excite about it but it only for for android pie only,so i try downgrade back to 9.0.17 but apparently the mod cause the phone go straight to crashdump mode and like hour ago he release couple more version but i was already on android 10 but after messing around with flash script i was able flash it on OOS10 imma attach the file i mod here for specific only for OOS10 only since this the only version that work flawless on OOS10 other test version i try they either force close the app or audio loss, highly recommended flash it along with Ainur Narsil---haven't test with other mod yet but in my opinion Dolby itself already better
https://forum.xda-developers.com/android/software/app-dolby-atmos-axon-7-oreo-port-t3740508
Credit:
@guitardedhero (for The Port)
-Me (for testing and mod the file to work on OOS10)
-Dolby (for Dolby Atmos)
Click to expand...
Click to collapse
Can u help me why it would not open and crashing. I'm on iOS 10.3.0

tswb said:
Can u help me why it would not open and crashing. I'm on iOS 10.3.0
Click to expand...
Click to collapse
You had any sound mod install? And what magisk version you had?

I have install the Dolby atoms only and no audio mod. Latest magisk 20.3 and I try to set the storage it won't open the permission.how to get granted permission to the storage.

tswb said:
I have install the Dolby atoms only and no audio mod. Latest magisk 20.3 and I try to set the storage it won't open the permission.how to get granted permission to the storage.
Click to expand...
Click to collapse
Like dolby ask you to granted storage permission or magisk? Cause dolby not require to Grant any permission as far as i know!there is couple people has successful installed it without any issue so far

tswb said:
I have install the Dolby atoms only and no audio mod. Latest magisk 20.3 and I try to set the storage it won't open the permission.how to get granted permission to the storage.
Click to expand...
Click to collapse
Use Magisk 20.1 try it and test if works then update to Magisk 20.3 done

Mervingio said:
Use Magisk 20.1 try it and test if works then update to Magisk 20.3 done
Click to expand...
Click to collapse
OK I will try it. Thanks

it works this is the good news, the bad news is that my bluetooth then stops working, it can no longer be switched on

tswb said:
OK I will try it. Thanks
Click to expand...
Click to collapse
did you find a chance to try it ?
i wonder we loose modules or not after we downgrade to 20.1 ?
also dolby still works when we upgrade back to 20.3 ?

Can it work simultaneously with Dolby digital plus?
Also do I need to install anything (AML)?

lazye53 said:
Can it work simultaneously with Dolby digital plus?
Also do I need to install anything (AML)?
Click to expand...
Click to collapse
Give it a try! Haven't has time to test yet but i guess it should work!

the_poseidon said:
did you find a chance to try it ?
i wonder we loose modules or not after we downgrade to 20.1 ?
also dolby still works when we upgrade back to 20.3 ?
Click to expand...
Click to collapse
I got working on 20.1 but i notice the Bluetooth not working after I install the zip file.

tswb said:
I got working on 20.1 but i notice the Bluetooth not working after I install the zip file.
Click to expand...
Click to collapse
If you remove module Bluetooth is not longer working

Well guy there is a news testing zip... currently at work now but ill test it after work and let you guy know! I still using the same zip and don't has any problem with Bluetooth or anything but ill update the new zip here a little bit!

https://forum.xda-developers.com/an...-atmos-axon-7-oreo-port-t3740508/post81515331

I was reading through a lot of that thread and it looks like it's still based for pie and there was a section in there saying that you have to change your build prop setting to SDK level 28 if you are on oxygen 10 and Android 10 you'll be SDK 29 so I was getting force closes and I took a big risk when do the build prop edited my SDK level 228 and went straight into a bootloop. So I had to actually do a factory reset. I then restore from twrp, but I screwed up and restored everything what I should have just done a system and data restore only because then I did a soft brick and had to use the MSM tool and start all over again at Android 9! Lol.. so I know guitardedhero was making special media files for audio library they were . so extensions... I'm going to keep digging because on Android 10 I've got ice sound working which is an Asus driver and I can even change the four configurations as well as the 11 different sound profiles fall through terminal emulator. I also have a flashable DTS 2.0

groovemetal81 said:
I was reading through a lot of that thread and it looks like it's still based for pie and there was a section in there saying that you have to change your build prop setting to SDK level 28 if you are on oxygen 10 and Android 10 you'll be SDK 29 so I was getting force closes and I took a big risk when do the build prop edited my SDK level 228 and went straight into a bootloop. So I had to actually do a factory reset. I then restore from twrp, but I screwed up and restored everything what I should have just done a system and data restore only because then I did a soft brick and had to use the MSM tool and start all over again at Android 9! Lol.. so I know guitardedhero was making special media files for audio library they were . so extensions... I'm going to keep digging because on Android 10 I've got ice sound working which is an Asus driver and I can even change the four configurations as well as the 11 different sound profiles fall through terminal emulator. I also have a flashable DTS 2.0
Click to expand...
Click to collapse
Yeah that what im concerned about to change the builprop SDK to 28 instead of that i change a code on the zip so it bypass the SDK check to able it flash on SDK 29....it was a test but apparently i didn't has any problem about a Bluetooth or anything! And there is couple people successful flash it as well but imma caught up with lastest zip and lemme see if i could mod it to work on OOS 10!and yep by default it only support Android pie only! So imma try troubleshooting as much as possible before releasing it!

Updated to latest Dolby Atmos 0.727 zip and it attached on the first page... I'll leave 0.64 zip there just in case anyone need it! And once 727 zip it work without any problem on 10.3.0 for me at least (testing on AAC,LDAC even aptx HD) but let me know

groovemetal81 said:
I was reading through a lot of that thread and it looks like it's still based for pie and there was a section in there saying that you have to change your build prop setting to SDK level 28 if you are on oxygen 10 and Android 10 you'll be SDK 29 so I was getting force closes and I took a big risk when do the build prop edited my SDK level 228 and went straight into a bootloop. So I had to actually do a factory reset. I then restore from twrp, but I screwed up and restored everything what I should have just done a system and data restore only because then I did a soft brick and had to use the MSM tool and start all over again at Android 9! Lol.. so I know guitardedhero was making special media files for audio library they were . so extensions... I'm going to keep digging because on Android 10 I've got ice sound working which is an Asus driver and I can even change the four configurations as well as the 11 different sound profiles fall through terminal emulator. I also have a flashable DTS 2.0
Click to expand...
Click to collapse
I would like to personally apologise to you for posting information that caused much frustration and inconvenience for you.
That was irresponsible of me to state workarounds to circumvent a restriction I implemented without knowing the risks that could be involved and not just taking out the restriction myself.
Thank you for sharing your experience. If I had not seen it just now, I would have still assumed such an action you took to be harmless.
I did remove this restriction many versions ago after learning that many were having success on Android 10 and the latest zip a couple hours ago seems to provide a much higher success rating and the support for existing audio mods and their effects seems to now be in place if you ever get an itch to try again without needing to do any hacky, ill-advised stuff like what I said last week.
:good:

My Bluetooth stops working after flashing. Reflash of OOS was necessary to get it back.

GSI images - bluetooth audio issue

Hi all,
have a motorola one zoom (parker), could test succesfully 3 GSI roms,
(Lineage, Havoc OS, and plain AOSP 10 222), in all of them, bluetooth audio
is not working, after pairing/connection with bt device, audio seems to move to
the device connected, but just after audio comes back playing on local cell phone,
as if bt is crashed.
I have found in this forum some threads saying to remove 2 specific file
from /vendor/overlay. None of those 2 files is there, and overlay just have
some subdirectories.
Changing codec seems not helping.
This is the only obstacle i have with GSI images, bt on stock image of course work,
would be great any help.
thanks !

Found this in the logs
A2DP_VendorLoadEncoderAptx: cannot open aptX encoder library libaptX_encoder.so: dlopen failed: library "libaptX_encoder.so" not found

I finally installed magisk aptX(HD) codec package, that was for Lineage, above error gone away, but i am now still getting
AD2P_VendorLoadDecodeLdac : cannot open ldac decoder.
libldacBT_dec.so not found

For android 10 posted my solution here
A2DP broken after updating to Motorola's Android 10 stock ROM · Issue #1404 · phhusson/treble_experimentations
I'm running the Android 10 vanilla GSI on a Motorola Moto G7 Play since February, while it was previous running Motorola's stock Android 9 ROM. To get A2DP working on the Moto G7 Play we had to dis...
github.com

Question Dolby or viper aosp rom what to install ?

question currently running PixelOS rom and i'm rooted would like to instal a sound enhancer was going to do vipper but after watching Munchy 2021 video it looks like a pain in the azz ,and not sure if that method will work on android 13 unless changed since then what are my options ? Im rooted is their a simple instal module or something I can install ? just want to enhance the sound of a bluetooth speaker , I know this rom comes with miui headphone enhancer but it only works if you plug in head phones kind of a waste , any suggestions or help would be great!

Install Arrow and ZTE A2019 Pro Dolby Magisk Module
And bobs your uncle

Viper almost never worked good for me. Since A10 lol better to go for Dolby. I'm using the ZTE one too