Related
I am wondering, if any of you use maxxaudio on OxygenOS. Yesterday Iflashed MaxxAudio-CM13-_ahmed_radaideh-STABLE-v3.1.zip and it worked great. But today I was not able to get it to do its magic again. I reflashed it, and works again, but I am wondering if someone investigated more or can point me to working version for OxygenOS.
I only used ViPer4Android as a sound enhancer. Therefore the SELinuxMode has to be permissive instead of enforcing. There are apps where you can change this like SELinuxModeChanger.
Maybe Maxxaudio changes this while flashing, but it gets reset every time you reboot your device. Had this issue in the past, it may help in your case.
Falkenhorst said:
I only used ViPer4Android as a sound enhancer. Therefore the SELinuxMode has to be permissive instead of enforcing. There are apps where you can change this like SELinuxModeChanger.
Maybe Maxxaudio changes this while flashing, but it gets reset every time you reboot your device. Had this issue in the past, it may help in your case.
Click to expand...
Click to collapse
Can u give me flash able viper4Android zip
HatRiGt said:
Can u give me flash able viper4Android zip
Click to expand...
Click to collapse
Second post, and someone is already hijacking this thread. Why?!
Hey, How about installing the SEmodechanger app and using MaxxAudio? How was the Output and Quality after the mod? I tried installing Viper4Android but faced bugs like Slow Phone, Crashing Process and No Audio Output
I like turtles, does anyone else like turtles?
Sent from my ONEPLUS A3000 using Tapatalk
rickyx32 said:
I like turtles, does anyone else like turtles?
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
Well they taste good.
jvybihal said:
I am wondering, if any of you use maxxaudio on OxygenOS. Yesterday Iflashed MaxxAudio-CM13-_ahmed_radaideh-STABLE-v3.1.zip and it worked great. But today I was not able to get it to do its magic again. I reflashed it, and works again, but I am wondering if someone investigated more or can point me to working version for OxygenOS.
Click to expand...
Click to collapse
How about now ? Did you find a working MaxxAudio in OxygenOS. ahrion's work don't work on mm, the other with refined GUI crashed on OxygenOS.
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!
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?
Has anyone gotten Viper 4 Android to work with the pixel 6 pro yet? If not, are there alternatives? Any guides to doing this would be appreciated! I searched but didn't find much.
Android 12 (Viper4Android)
Has anyone managed to get Viper4Android working on the latest beta of Android 12? The usual methods don't work (makes sense, since its a new OS). Just curious. I like Android 12 so far, but might roll back to 11 if I can't get Viper going...
forum.xda-developers.com
Followed the guide in that thread and got it installed and seems to be working, any recommendations on the profiles for the speakers or the pixel buds a?
FabricatorGeneral said:
Seguí la guía en ese hilo y lo instalé y parece estar funcionando, ¿alguna recomendación sobre los perfiles para los altavoces o los botones de píxeles?
Click to expand...
Click to collapse
norteDon't put much Bass on the speakers because they over time deteriorateBass on the speakers because they over time deteriorate
For those that don't want to change their kernel to permissive due to security reasons, I used this method and is working fine for me. Legacy mode needs to be toggled on.
Viper4Android
Anyone get this working yet?
forum.xda-developers.com
Lughnasadh said:
For those that don't want to change their kernel to permissive due to security reasons, I used this method and is working fine for me. Legacy mode needs to be toggled on.
Viper4Android
Anyone get this working yet?
forum.xda-developers.com
Click to expand...
Click to collapse
i didnt have to change to permissive. the 2nd. file is a Android 12 fix, i believe if you use the fix you do not have to change to permissive....
AndroidAddict420 said:
i didnt have to change to permissive. the 2nd. file is a Android 12 fix, i believe if you use the fix you do not have to change to permissive....
Click to expand...
Click to collapse
I was referring to the method linked in Post #2 where they said they changed their kernel to permissive. The Android 12 fix file is from another thread which you started and posted the file it. You might want to add a link to your post so people know what "fix" file you are talking about since it's not in this thread, lest people might get confused about what you are talking about.
Or maybe I'll just link it here...
Interested in a Working Formula to get Viper4Android Working? (ROOT)
Viper4Android for Google Pixel 6/6 Pro and most other devices on Android 12... It the time of testing this Method, it worked in November 2021 and December 2021 builds for my Google Pixel 6.... 1) Make sure your BL is unlocked and you are...
forum.xda-developers.com
I installed by using the method I had to do for OP8T. Install Audio_Modification_Library Magisk Module (DO NOT REBOOT) -> Install Viper Magisk Module (DO NOT REBOOT) -> Open Viper App (this forces a reboot) -> Remove Audio_Modification_Library. It works great for me in apps like AIMP, but in apps like YouTubeVanced have never worked for me.
card13 said:
I installed by using the method I had to do for OP8T. Install Audio_Modification_Library Magisk Module (DO NOT REBOOT) -> Install Viper Magisk Module (DO NOT REBOOT) -> Open Viper App (this forces a reboot) -> Remove Audio_Modification_Library. It works great for me in apps like AIMP, but in apps like YouTubeVanced have never worked for me.
Click to expand...
Click to collapse
Strange it doesn't process with YouTubeVanced for you. It should. Have you tried giving this mod a shot?
EDIT: Actually I think the version located at John Fawkes site is newer than the XDA one, so adding that link.
Audio Compatibility Patch (Formerly Universal deep_buffer Remover) [MMTEx]
This fixes music and streaming apps (Spotify, Pandora, etc) that aren't processing audio effects for various equalizer applications through the modification of audio policy. Starting with v1.6 USB_policy patcher (upp) and Notification_helper...
forum.xda-developers.com
John Fawkes Playground
@Lughnasadh I'm not currently using the Compatibility Patch. It's mainly because last time I did on the OnePlus phones, my Bluetooth audio would get fubar'd and require a Factory Reset to fix.
Thanks to the community, the Viper4android works for me on Pixe6 PRO, BUT I am unable to activate any VIPER-DDC , Headset correction profiles loading takes no effect, tried a few I see them active but no change in sound. Previously my OnePlus 8Pro worked fine with the same version (Android 12). Does anyone experience similar issue ? Can you please try and let me know.
ansher said:
Thanks to the community, the Viper4android works for me on Pixe6 PRO, BUT I am unable to activate any VIPER-DDC , Headset correction profiles loading takes no effect, tried a few I see them active but no change in sound. Previously my OnePlus 8Pro worked fine with the same version (Android 12). Does anyone experience similar issue ? Can you please try and let me know.
Click to expand...
Click to collapse
I don't have answer for your question, perhaps go to their Telegram group to ask for help as you may have more chance there.
I do have something for your consideration. I used V4A for longer than I can remember but it must be over 10 years. However, seems the developer has already quitted the project for quite sometime, the driver has never been updated in the past 7-8 years, we are lucky that it is still working with A12. But everything has an end, I tried it on A13 Beta and it doesn't work with it. If you search the web, you properly going to find that so far no one is able to make it work with A13. The A13 is already in beta 4 and official release could be sometime in next month, unless you are going to give up to update to A13, you better start to find something to replace V4A, my choice is JamesDSP but you may find something better suit your needs.
I prefer presets because I don't know what I'm doing. I ended up moving to PowerAmp and am usually pleased with the sound. If only the developer would enable roor features, man that would be cool.
Thanks acwcanada for the suggestion. I looked at the thread and so far may stick with Android 12 (those crazy audiophiles ) because I could not find 2 key features available in Viper4Android.
1. Headphone frequency response correction (VIPER-DDC or AutoEQ in Wavelet). This feature does not even work for me in Pixel 6 pro A12L , workaround: install wavelet and use its AutoEQ feature.
2. Dynamic System feature of Viper4Android creates bass subharmonics using reference frequencies and algorithm (selectable by choosing headphone type), so it can inject them in the music making it feel much richer and restores lack of low frequencies without "booming" effect created by other bass boosters. So far nothing in this word can beat this Viper4Andoid's feature.
Some good news folks: Viper4Android and Wavelet can be stacked and work in tandem .
Perhaps going to write James to consider the above, unless I missed it.
Cheers and thanks Team !
I tried all custom roms possible and no one have sound, only with earphones.
I'm pretty sure it's note mo phone defective because was working before and didnt drop on the floor.
Any help would be immensely appreciated.
Thanks.
I have the same phone and have discovered the same problem after flashing any of the Android 11 custom ROM. No sound from speaker/ringer/media (except headphone jack). I found one suggested solution here, the last reply to the AOSPK ROM thread. The solution was to place 4 files into vendor/etc. I tried that and sure enough I got sound back with those ROMs but it broke the phone call function, couldn't make calls, dialers just ended call as soon as I tried to connect. Maybe this will work for someone else. Maybe someone else has a better solution. I'll try just replacing one file at a time and see if I can figure it out. If you find a solution let us know.
Kerplunk83 said:
I tried all custom roms possible and no one have sound, only with earphones.
I'm pretty sure it's note mo phone defective because was working before and didnt drop on the floor.
Any help would be immensely appreciated.
Thanks.
Click to expand...
Click to collapse
Oh and the easiest way to get back to stock is to use the Motorola Rescue assistant tool here. Just put your phone into bootloader mode and the Motorola tool will detect the phone, download the latest stock firmware and restore the phone.
Okay, I found the fix. From stock I installed AOSPExtended ROM from the Moto G6 Play forum. Initially everything seemed to work but no audio.
The fix reported in my last post, linked to the Telegram group was:
"For sound, add these 4 files to vendor/etc"
mixer_paths.xml
audio_platform_info.xml
audio_platform_info_jeter_p0.xml
mixer_paths_jeter_p0.xml
"
Copying all 4 files caused audio to work but cell calling broke.
Copy only the first 2 files without 'jeter_p0' in the name and audio was fixed and nothing else broke. Happy now. I assume this will fix the same problem with all the Android 11 roms I installed that caused this problem.
ianos21 said:
Okay, I found the fix. From stock I installed AOSPExtended ROM from the Moto G6 Play forum. Initially everything seemed to work but no audio.
The fix reported in my last post, linked to the Telegram group was:
"For sound, add these 4 files to vendor/etc"
mixer_paths.xml
audio_platform_info.xml
audio_platform_info_jeter_p0.xml
mixer_paths_jeter_p0.xml
"
Copying all 4 files caused audio to work but cell calling broke.
Copy only the first 2 files without 'jeter_p0' in the name and audio was fixed and nothing else broke. Happy now. I assume this will fix the same problem with all the Android 11 roms I installed that caused this problem.
Click to expand...
Click to collapse
I'm a n00b so I hope you can please excuse my ignorance but how did you copy the files to that folder? And how did you get the files from the source? Also does it fix the rotation? as I have a rotation problem as well
OK its within TWRP didn't know that, file manager
ianos21 said:
Okay, I found the fix. From stock I installed AOSPExtended ROM from the Moto G6 Play forum. Initially everything seemed to work but no audio.
The fix reported in my last post, linked to the Telegram group was:
"For sound, add these 4 files to vendor/etc"
mixer_paths.xml
audio_platform_info.xml
audio_platform_info_jeter_p0.xml
mixer_paths_jeter_p0.xml
"
Copying all 4 files caused audio to work but cell calling broke.
Copy only the first 2 files without 'jeter_p0' in the name and audio was fixed and nothing else broke. Happy now. I assume this will fix the same problem with all the Android 11 roms I installed that caused this problem.
Click to expand...
Click to collapse
Hi, friend.
I tried your solution, but it did not work on my phone, jeter xt-1922-9, i flashed pixel experience plus or lineage os 18.1, no one working on audio. no sound incoming call, no sound on youtube video.