Related
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.
Hello everybody. I have Magisk and couldn't install Viper module, neither the usual viper .zip via TWRP.
Have you been able to install any of the available audio mods on your Z2 Play?
I too am interested.
I prefer the Atmos version, ViPERAtmos 4.8 Sony Beats Universal Edition, but I don't think it's compatible with Nougat.
Any advice would be greatly appreciated!
I installed ARiSE sound system in my z2 play, which contains Viper and Dolby Atmos
I have a module called viper 4arise installed and its working very well
danielmn97 said:
I installed ARiSE sound system in my z2 play, which contains Viper and Dolby Atmos
Click to expand...
Click to collapse
Could you post a link to the download / thread that worked for you? I can try to install and make a simple tutorial for other folks.
Thanks!
Here https://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709 install the last stable version
Thanks! I've looked at ARISE a few times, but it seems life meant steps to install. I guess I'm going to have to bear it.
Does it sound as good at Atmos?
I manage to install it. It's overall pretty simple. You can extract the installation .prop file to /emulated/0 and edit it there to get a 1 cycle install. Otherwise your first try will do just that and return an error (so you'll have to edit the file anyways).
I tried all versions of viper there but none worked (all showed abnormal status) also, remember to mark for installation the Magisk compatibility.
I'm using Atmos, working very nicely, but still wish Viper had worked...
dainezi said:
I manage to install it. It's overall pretty simple. You can extract the installation .prop file to /emulated/0 and edit it there to get a 1 cycle install. Otherwise your first try will do just that and return an error (so you'll have to edit the file anyways).
I tried all versions of viper there but none worked (all showed abnormal status) also, remember to mark for installation the Magisk compatibility.
I'm using Atmos, working very nicely, but still wish Viper had worked...
Click to expand...
Click to collapse
That's weird, I have Viper and atmos working in my device. Previously I set SElinux permissive and installed Busybox
Oh that must be it. I have it on enforcing. Will test with permissive then. Thanks!
Well, it worked! AriSE with SELinux mode changer set to permissive.
Thanks a lot!
With Dolby and viper our speakers sound WAY better! Headphones are even more awesome!
Hello there,
I've checked out a few threads but can't find any pertaining to my exact situation.
So I'm on OB28, so Oreo OOS, tried a few proposed sound mods but none of them seem to work or else I'm doing something wrong.
Flashed a few compatible TWRP recoveries and rooted. Tried that ARISE mod but either the mods I'm interested in don't work or seem to give me FCs on reboot. Tried random dolby zips which don't do anything. I've even had a "factory data reset" message on startup with an automatic reboot to recovery.
Is there any decent audio mod that works on Oreo OOS (preferably Dolby)? If so, please show me how to get this done.
Thanks
There is no practical way to get Dolby Atmos working on Oreo as of now. Dolby Digital, however, can work. You can flash this mod by guitardedhero:
https://forum.xda-developers.com/showpost.php?p=74880570&postcount=31701
Note that every other audio mod needs to be removed including any in Magisk for this to work. Viper can be flashed after this works but not a priori. SELinux permissive is necessary.
therightperson_630 said:
Hello there,
I've checked out a few threads but can't find any pertaining to my exact situation.
So I'm on OB28, so Oreo OOS, tried a few proposed sound mods but none of them seem to work or else I'm doing something wrong.
Flashed a few compatible TWRP recoveries and rooted. Tried that ARISE mod but either the mods I'm interested in don't work or seem to give me FCs on reboot. Tried random dolby zips which don't do anything. I've even had a "factory data reset" message on startup with an automatic reboot to recovery.
Is there any decent audio mod that works on Oreo OOS (preferably Dolby)? If so, please show me how to get this done.
Thanks
Click to expand...
Click to collapse
get the addon zip from experience os it has viper dolby atmos and they both work
v.konvict said:
get the addon zip from experience os it has viper dolby atmos and they both work
Click to expand...
Click to collapse
Can confirm just did this on Nitrogen 8.1 Dolby & Viper working, great "trick"
gmlogan said:
Can confirm just did this on Nitrogen 8.1 Dolby & Viper working, great "trick"
Click to expand...
Click to collapse
not sure what the dev did with but it works well even when compared to official zips from viper4arise thread
v.konvict said:
get the addon zip from experience os it has viper dolby atmos and they both work
Click to expand...
Click to collapse
Thanks, nice to see one that works! the add-ons are a nice touch too. I think my arise config file must have been wrong.
does it work in enforcing or permissive..i mean with the addon @v.konvict @therightperson_630
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?
Well I've been trying hardly to get the regular magisk viper4android to work, didn't work.
Seems y'all need to use the legacy version from the magisk installer to get it to work until the devs are solving the problem.
It's because of the separation of USB I guess.
If someone needs further assistance or advices feel free to comment!
I don't have my phone yet but last I heard magisk was not the way to get a working v4a for anyone. the last working version I had came from an apk install of version 2.7.1.0
[APP][ALL ROOT SOLUTIONS][6.0+]ViPER4Android FX 2.7
ViPER4Android FX By pittvandewitt and MrWhite214 Introduction Many users are enhancing their smartphone audio experience with the popular ViPER4Android software, but some of us have a hard time installing the driver or they don't like the look...
forum.xda-developers.com
I have made it work using audio modification library and audio compatibility patch
anyone with it working on enforcing 3.1 please share which version/s you used, steps required etc
@NoxOn3 @proyectos3d