Any way to make viper work on OOS13? I've tested several methods of replacing files and every time it asks to install the driver
First need to found disable Dolby in oxygenos
ScarletWizard said:
Theres a new alpha version ,2.0 ,64 bit viper . It might work for your device
Also oxgyen0s is unique enough that it's gonna need its own custom post-fs-data.sh for viper
I donated money to the dev of v4a and he got me viper working
Click to expand...
Click to collapse
Can you share? Or where can I find it please.
ScarletWizard said:
Theres a new alpha version ,2.0 ,64 bit viper . It might work for your device
Also oxgyen0s is unique enough that it's gonna need its own custom post-fs-data.sh for viper
I donated money to the dev of v4a and he got me viper working
Click to expand...
Click to collapse
Yah, if you could share magisk module, that would be great!
I actually got a viper4android working from the 10 pro forums. Just install this apk AND magisk module then reboot. The newest version is the only one working. Also, when you see the properties, it says the driver is unknown and viper is not enabled, but it definitely is. The only known issue from my device is that when the bass exceeds a certain point (pretty high) the audio will cut out for a second. https://github.com/AndroidAudioMods/ViPER4Android/releases
Lastly, I am in oxygen13, if that makes any difference
Edit:. Nevermind, over Bluetooth it is not working for me yet.
Ah, didn't check that the apk and module are in that same link. I just installed them both, rebooted and it's all working. Even says enabled and processing.
JPower123 said:
I actually got a viper4android working from the 10 pro forums. Just install this apk AND magisk module then reboot. The newest version is the only one working. Also, when you see the properties, it says the driver is unknown and viper is not enabled, but it definitely is. The only known issue from my device is that when the bass exceeds a certain point (pretty high) the audio will cut out for a second. https://github.com/AndroidAudioMods/ViPER4Android/releases
Lastly, I am in oxygen13, if that makes any difference
Click to expand...
Click to collapse
Thank you so much! I've been trying for a couple hours using different versions of the app and different methods of installing drivers. This works with no problems.
OnePlus 10T 5G running Oxygen OS 13, CPH2417_11_C.22.
Related
Hey Guys!
I actually have been looking for a way to get Viper4Android working today. And i actually found a method to do it. By luck, OnePlus posted the Oxygen 3.0 based on android 6.0.1 today. This version of android is compatible with the newest version of Viper4Android. This version actually comes without an equalizer like 2.2... but oh well. I liked viper way better anyway.
Just wanted to give my 2 cents to the forum.. just wanted to let people know there is opportunity here to enjoy better music while you are waiting for CM 13 like me =)
How i got it to work:
- First install Oxygen 3.0 with a custom TWRP created for Oxygen 3.0 (see this url: link to oneplus forums)
- Secondly, use the custom made SuperSU (credits to @Yash98) = this link
- When the phone is updated and rooted, you can install BusyBox through the app store. After you did that download the APK of Viper on your phone via the original XDA thread
- Don't run it yet. Download SELinuxModeChanger via the original XDA thread.
- Change the mode to permissive, go back to Viper and install the drivers. It'll ask you for a reboot, do so. After the reboot open Viper4Android and press the 3 dots on the right high corner. Examining the driver status would show that the driver is enabled. If it's not. Try to empty the google music cache & removing the data (i did so somewhere in the process).
Hope this can make anybody happy. I'm an audiophile so i'm more than happy.
- Shakaraja.
The new Beta of OxygenOS 3.0 does NOT come with any audio enhancements, so you may even flash packages of audio mods, as I did
MaxtremePL said:
The new Beta of OxygenOS 3.0 does NOT come with any audio enhancements, so you may even flash packages of audio mods, as I did
Click to expand...
Click to collapse
Can you share the audio mods you used?? Thanks
---------- Post added at 10:43 PM ---------- Previous post was at 10:42 PM ----------
shakaraja said:
Hey Guys!
I actually have been looking for a way to get Viper4Android working today. And i actually found a method to do it. By luck, OnePlus posted the Oxygen 3.0 based on android 6.0.1 today. This version of android is compatible with the newest version of Viper4Android. This version actually comes without an equalizer like 2.2... but oh well. I liked viper way better anyway.
Just wanted to give my 2 cents to the forum.. just wanted to let people know there is opportunity here to enjoy better music while you are waiting for CM 13 like me =)
How i got it to work:
- First install Oxygen 3.0 with a custom TWRP created for Oxygen 3.0 (see this url: link to oneplus forums)
- Secondly, use the custom made SuperSU (credits to @Yash98) = this link
- When the phone is updated and rooted, you can install BusyBox through the app store. After you did that download the APK of Viper on your phone via the original XDA thread
- Don't run it yet. Download SELinuxModeChanger via the original XDA thread.
- Change the mode to permissive, go back to Viper and install the drivers. It'll ask you for a reboot, do so. After the reboot open Viper4Android and press the 3 dots on the right high corner. Examining the driver status would show that the driver is enabled. If it's not. Try to empty the google music cache & removing the data (i did so somewhere in the process).
Hope this can make anybody happy. I'm an audiophile so i'm more than happy.
- Shakaraja.
Click to expand...
Click to collapse
Thanks for the detailed guide... Will test now thanks
anees167 said:
Can you share the audio mods you used?? Thanks
Click to expand...
Click to collapse
Divine Beats by Royal Seeker (DolbyDigital+ version) located at:
http://theroyalseeker.github.io/
In order for this mod to work you need permissive SElinux
I'm not able to install custom recovery it just gets stuck at the one plus logo. And when I reboot normally it gets back to stock recovery. Any solution plz
Did you disable boot to stock recovery and also you may have to fastboot recovery
Can I reduce the loudest sound of OxyGenOS3 with Viper4Android?
I have distorted sound using the v4a. How fix it?
Bluetooth doesn't work when V4A drivers is installed.
Anyone can solved this problem?
Thanks, got it working. Don't notice too much difference in sound, but maybe I just haven't foudn the right settings yet.
It dosent work getting distorted sound
viper4android install than sound break problem is fix?
mohamm3edadam said:
I'm not able to install custom recovery it just gets stuck at the one plus logo. And when I reboot normally it gets back to stock recovery. Any solution plz
Click to expand...
Click to collapse
You need the TWRP version meant for H2OS. You will find it in any H2OS based ROM thread.
Skick3 said:
Can I reduce the loudest sound of OxyGenOS3 with Viper4Android?
Click to expand...
Click to collapse
Yes, there are options. Find gain controls and tweak them to your preference.
ras_fyah said:
I have distorted sound using the v4a. How fix it?
Click to expand...
Click to collapse
Akhil701 said:
It dosent work getting distorted sound
Click to expand...
Click to collapse
If you still are on OOS 2.2.x then V4A will not work. This fix is specifically meant for OOS 3.
If you are on OOS 3, then try reflashing OOS 3 with a clean flash. This might fix it, but only if you are on OOS 3.
mvha said:
Bluetooth doesn't work when V4A drivers is installed.
Anyone can solved this problem?
Click to expand...
Click to collapse
Did you install the right drivers? And also check if you set the SELinux mode to Permissive.
locxFIN said:
Thanks, got it working. Don't notice too much difference in sound, but maybe I just haven't foudn the right settings yet.
Click to expand...
Click to collapse
Search XDA Forums for V4A profiles and use a preferred profile according to your type of music.
whwhdtk5689 said:
viper4android install than sound break problem is fix?
Click to expand...
Click to collapse
Only if you have flashed the latest beta of OOS 3. This fix is OOS 3 specific and DOES NOT APPLY TO OOS 2.
arch_geek said:
Only if you have flashed the latest beta of OOS 3. This fix is OOS 3 specific and DOES NOT APPLY TO OOS 2.
Click to expand...
Click to collapse
yes. i'm oos 3.0 MM.
wow i'm install now viper4android !
thank you !
arch_geek said:
Did you install the right drivers? And also check if you set the SELinux mode to Permissive.
Click to expand...
Click to collapse
You've Got a Point. I have installed wrong version of V4A. Now working all. Thank You
Sorry for the noob question and if I'm posting at the wrong place. When you first install OOS 3.0 it's not rooted right? How do I root it? Thanks for the help.
shakaraja said:
Examining the driver status would show that the driver is enabled. If it's not. Try to empty the google music cache & removing the data (i did so somewhere in the process).
Click to expand...
Click to collapse
Hm i had the same problem. Driver Status was false.
My Workaround was i clicked in Viper many Menus up an down. Lock Effect Mode disable to speaker. UI Setting to Expert and suddenly the Driver Status was True.
No cleaning data. I didn´t installed google play music.
With Viper4Anroid on OO2 Oxygen3 the sound are definitly noiser and better. (Master Gain (Limiter) / Output Gaine -20db)
Thx for the hint with these app.
_Epix_ said:
Sorry for the noob question and if I'm posting at the wrong place. When you first install OOS 3.0 it's not rooted right? How do I root it? Thanks for the help.
Click to expand...
Click to collapse
How to root your phone. You find it in these guide
> http://forum.xda-developers.com/oneplus-2/general/guides-how-to-guides-beginners-t3146568
Last time I used viper was the nexus 4 days almost 2 years ago... They have improved the audio (most likely new audio hardware on OP2) but yh it sounds a lot better then stock oxygenOS 3 it does the job till Maxxaudio is back
MaxtremePL said:
Divine Beats by Royal Seeker (DolbyDigital+ version) located at:
http://theroyalseeker.github.io/
In order for this mod to work you need permissive SElinux
Click to expand...
Click to collapse
Thank you soooo much! This did the trick. I was so frustrated with the MM update until you saved my ears with this suggestion. :good:
_Epix_ said:
Sorry for the noob question and if I'm posting at the wrong place. When you first install OOS 3.0 it's not rooted right? How do I root it? Thanks for the help.
Click to expand...
Click to collapse
If you flashed OOS 3, it is highly likely that the build was not a pre-rooted build. To root follow this guide at this link :
http://forum.xda-developers.com/oneplus-2/general/guides-how-to-guides-beginners-t3146568
anees167 said:
Last time I used viper was the nexus 4 days almost 2 years ago... They have improved the audio (most likely new audio hardware on OP2) but yh it sounds a lot better then stock oxygenOS 3 it does the job till Maxxaudio is back
Click to expand...
Click to collapse
Actually V4A can be tweaked to sound better than MaxxAudio. Try XtremeMUSIC mod by androidexpert35. It includes V4A as an addon.
Link to the above mod is here: http://forum.xda-developers.com/android/software/mod-beatsaudio-e-xloud-installer-t3029951
&roid said:
Thank you soooo much! This did the trick. I was so frustrated with the MM update until you saved my ears with this suggestion. :good:
Click to expand...
Click to collapse
Try XtremeMUSIC mod. Link: http://forum.xda-developers.com/android/software/mod-beatsaudio-e-xloud-installer-t3029951
OnePlus seems to have enabled aptX codecs in the new OB5/14 for the OnePlus 3/T.
For those of you who don't want to wait until the stable release and also would rather not flash the open beta, @Chaosgod27 has extracted the related files for use in the stable release. These files can be placed within OOS 4.1.X to enable aptX mode. These files are different from the old aptX-enabling files that were broken in OOS since updating to 7.1.1.
Edit: It seems there's some issues with the stacks. Playback does use aptX, but music is playing at a slightly higher pitch and faster than it should be.
I've dug around through the files in the new open beta and found the files myself. It seems there were a few missing before. The issue with the raised pitch and fast playback should be gone now.
Flashable Zip (through custom recovery, does not require Magisk): View attachment 4121507
Magisk Module (same thing, just systemless): View attachment 4121508
There was an issue before with some missing files that caused playback to run too fast and with a higher pitch. That has been fixed now. If anyone flashed the old Magisk module, I would advise you to download the new one in the OP and flash over it. I've also included a flashable zip for those of you who aren't using Magisk.
Anova's Origin said:
There was an issue before with some missing files that caused playback to run too fast and with a higher pitch. That has been fixed now. If anyone flashed the old Magisk module, I would advise you to download the new one in the OP and flash over it. I've also included a flashable zip for those of you who aren't using Magisk.
Click to expand...
Click to collapse
Thanks a million
Thank you, I have installed it but it seems to have a lot more problems (noise/cracking as in packets lost or something) than the previous version that I was using and which I got from here:
https://forum.xda-developers.com/oneplus-3/themes/mod-aptx-codec-t3521228
Is there any way to uninstall this version and return to "old default" (from where I can get back to the aptx version from above)?
xclub_101 said:
Thank you, I have installed it but it seems to have a lot more problems (noise/cracking as in packets lost or something) than the previous version that I was using and which I got from here:
https://forum.xda-developers.com/oneplus-3/themes/mod-aptx-codec-t3521228
Is there any way to uninstall this version and return to "old default" (from where I can get back to the aptx version from above)?
Click to expand...
Click to collapse
If you used the Magisk module, simply delete the module and reboot.
If you flashed the regular zip, you'll have to dirty flash your ROM to restore to default.
Hi @Anova's Origin, how do i know if this mod is working or not?
Vixiebalistic said:
Hi @Anova's Origin, how do i know if this mod is working or not?
Click to expand...
Click to collapse
Use a logcat app (Catlog / Matlog) and search for an aptx entry in the recorded logs after you connected your aptx capable device via Bluetooth to your aptx enabled phone...
You should be able to find something if it's working, otherwise it wouldn't show any aptx entry
Sent from my OnePlus3T using XDA Labs
Edit 2: Nevermind, it's working now. Idk what the problem was.
Didn't work for me on OOS 4.1.6 on Oneplus 3T I can't turn on Bluetooth. Anyone else having this problem? Also, have the drivers been updated in a newer OB?
Edit: I am using magisk v13.3
vini2710 said:
Didn't work for me on OOS 4.1.6 on Oneplus 3T I can't turn on Bluetooth. Anyone else having this problem? Also, have the drivers been updated in a newer OB?
Click to expand...
Click to collapse
Nope... Working fine here with op3t 4.1.6. Did u make back up before flashing?
Vixiebalistic said:
Nope... Working fine here with op3t 4.1.6. Did u make back up before flashing?
Click to expand...
Click to collapse
I used magisk so no worries (v13.3)
Edit: It's working. Yay! Thank you for the good work with this module!
how about op3T 4.1.7? Is it work?
qwealan said:
how about op3T 4.1.7? Is it work?
Click to expand...
Click to collapse
It works flawlessly for me on OOS 4.1.7 on my op3t
Sent from my ONEPLUS A3003 using Tapatalk
Anyone, test Magisk module with lineageOS Rom ?
vinicentus said:
It works flawlessly for me on OOS 4.1.7 on my op3t
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
I use Magisk Module on OOS4.1.7 but i cant use aptX (use catlog search "aptx" ). are you use zip flash or use Magisk too?
qwealan said:
I use Magisk Module on OOS4.1.7 but i cant use aptX (use catlog search "aptx" ). are you use zip flash or use Magisk too?
Click to expand...
Click to collapse
I am using magisk (v14)
Working on OP3T with OOS 4.5.1 + Magisk 14.0. Those libs where updated to show battery for devices in OB15, update needed.
Thanks very much! Looking for this about a week long and finally solved
My device is OP3T, with H2OS V3.5 stable, no magisk
can I share this to oneplusbbs.com?
I've finally figured this out!
This is a scientific breakthrough! Not really... lol
So, I've managed to make SafetyNet pass using a "custom" Magisk build.
I grabbed it from here and so far I've flashed this build and it coaxed SafetyNet into passing. On one treble ROM, ToxycOS, it completely made SafetyNet pass, both ctsProfile and basicIntegrity. On RR official though, it only made basicIntegrity pass. However, that's completely better than nothing at all!
This is how I got SafetyNet to pass completely, it only works if basicIntegrity is passing while ctsProfile if failing.
•Magisk builds: https://github.com/ianmacd/MagiskBuilds
•Magisk I flashed that got SafetyNet to pass: https://github.com/ianmacd/MagiskBuilds/blob/master/Magisk-v16.5-20180621-ianmacd.zip
•Guide to get SafetyNet to pass: https://github.com/phhusson/treble_experimentations/issues/116
Thanks to @topjohnwu for making Magisk possible
Big thanks to @ianmacd for making these Magisk builds
Why did I post this?
I posted this because Magisk 16.6 kept on bootlooping for me, no matter what I did. I'm pretty sure it patches the kernel instead of the ramdisk so it causes a bootloop, again, not 100% sure what it's doing, but either way, it's bootlooping for me. These builds *hopefully* don't bootloop. I flashed 16.5 and it's working great.
crayonicle said:
Why did I post this?
I posted this because Magisk 16.6 kept on bootlooping for me, no matter what I did. I'm pretty sure it patches the kernel instead of the ramdisk so it causes a bootloop, again, not 100% sure what it's doing, but either way, it's bootlooping for me. These builds *hopefully* don't bootloop. I flashed 16.5 and it's working great.
Click to expand...
Click to collapse
yo you can always change the device's fingerprint in order to make safetynet pass using a magisk module
crayonicle said:
Why did I post this?
I posted this because Magisk 16.6 kept on bootlooping for me, no matter what I did. I'm pretty sure it patches the kernel instead of the ramdisk so it causes a bootloop, again, not 100% sure what it's doing, but either way, it's bootlooping for me. These builds *hopefully* don't bootloop. I flashed 16.5 and it's working great.
Click to expand...
Click to collapse
Which version on 16.5 did you use i meant the build date
adb debug working?
huawei p8 lite 2017
phh treble rom gsi vanilla v22
Thanks to everyone but the guy who actually discovered and documented this? Hmph!
It works on BDN-L34
I passed the test successfully following this guide.
I used a Huawei Mate SE (BND-L34) running phusson's [AOSP 8.1 - Phh-Treble] v22. Then downloaded iammacd'smagisk build that the op provided and zip flashed it through TWRP. Then logged on android and uninstalled the magisk manager app (which was an older version) and then downloaded the newest one available and installed it as an apk. After that I opened the app and went to "downloads" and looked for MagiskHide Props, installed the module and rebooted phone. Then as the op did, I followed cawilliamson's instructions on how to set up MagiskHide Props the only difference being that I set up the fingerprint using Huawei mate 9 since Honor 7x were not listed.
I was running and failing at different points the SafetyNet test until I completed the process. Thats it, thanks to crayonicle for research and compiling such great information and to the other people that made it possible. :good:
IonDEfeso said:
I passed the test successfully following this guide.
I used a Huawei Mate SE (BND-L34) running phusson's [AOSP 8.1 - Phh-Treble] v22. Then downloaded iammacd'smagisk build that the op provided and zip flashed it through TWRP. Then logged on android and uninstalled the magisk manager app (which was an older version) and then downloaded the newest one available and installed it as an apk. After that I opened the app and went to "downloads" and looked for MagiskHide Props, installed the module and rebooted phone. Then as the op did, I followed cawilliamson's instructions on how to set up MagiskHide Props the only difference being that I set up the fingerprint using Huawei mate 9 since Honor 7x were not listed.
I was running and failing at different points the SafetyNet test until I completed the process. Thats it, thanks to crayonicle for research and compiling such great information and to the other people that made it possible. :good:
Click to expand...
Click to collapse
Have an Mate 9. What can I do for now? The Magisk-v16.5-20180621-ianmacd.zip dosen´t work for me. It´s bootloped!
chrisaw said:
Thanks to everyone but the guy who actually discovered and documented this? Hmph!
Click to expand...
Click to collapse
I got his permission to post this on Telegram.
Don't worry.
krlosoul said:
adb debug working?
huawei p8 lite 2017
phh treble rom gsi vanilla v22
Click to expand...
Click to collapse
It seems to be. You can always try and test it yourself.
Ashley david said:
Which version on 16.5 did you use i meant the build date
Click to expand...
Click to collapse
2018-6-21
BTW ive just updated to the "MagiskManager-v16.8-2018071902" which is ianmacd's lastest build posted and (first of all isnt bootlooping) and is also passing all of the SafetyNet tests. Also installed the lastest version of the Magisk Manager app 5.8.3 (129) successfully. Not sure if is helpful to report that but since it boot-looped me when I tried to update it last time, so now I consider it an achievement lol. I first uninstalled magisk manager through android uninstall (not the magisk uninstall, which unroots you and delete modules) then installed the new version manually.
-----------------------------------------------------------------------
mcc2005 said:
Have an Mate 9. What can I do for now? The Magisk-v16.5-20180621-ianmacd.zip dosen´t work for me. It´s bootloped!
Click to expand...
Click to collapse
I am no expert but what ROM are you running? I used to have RRO v6 and the boot loping happened to me when I updated magisk to lastest version through the app. Try flashing the older magisk you had before?
If not I think you will have to go back to stock which is what I had to do when that happened to me. I used a stock oreo zip rom for my device (BND-L34) and this guide now since you have the MATE 9 I dont know what the procedures and files needed for that one.
Using a BDN-L34 (Mate SE)
Back to report that I successfully flashed [8.1.0][TREBLE] Pixel Experience [AOSP][r36][2018/07/14] by jhenrique09 (8.1.0-20180714-0200-OFFICIAL) and sucessfully installed the last Magisk version (and app) and passed all the tests (even better it help me bypass the "google uncertified device" messages i was getting). To pass the SafetyNet I downloaded the MagiskHide on the Magisk app "Downloads" then ran a terminal emulator with the following commands.
Code:
su
props
Then only needed to set the fingerprint by doing:
1 > F > * > ** > Y > Y (This last option will make the device reboot, needed to pass SafetyNet, but you can reboot later by writing N)
*Note that you need to select your phones brand in the options given there.
**Select your phone model (or any other model with the same fingerprint reader or compatibility, guess you can try out different models and check if any works, at your own risk though, I dont know if there could be grave repercussions.)
IonDEfeso said:
*Note that you need to select your phones brand in the options given there.
**Select your phone model (or any other model with the same fingerprint reader or compatibility, guess you can try out different models and check if any works, at your own risk though, I dont know if there could be grave repercussions.)
Click to expand...
Click to collapse
You dont exactly need to select your device model. I followed this guide using an Honor 7x. Worked well.
crayonicle said:
You dont exactly need to select your device model. I followed this guide using an Honor 7x. Worked well.
Click to expand...
Click to collapse
Yeah I selected honor 9 for my Mate SE, I just mentioned that since I dont know how serious would it be the implications of selecting a totally different model for another phone but yeah just didn't wanted to tell people to select whatever and then suddenly their fingerprint isn't working or something like that haha. Btw i used the same guide you provided the first time i did everything he pointed but then realized that only the first step was enough so only did that.
steven360 said:
You dont exactly need to select your device model. I followed this guide using an Honor 7x. Worked well.
Click to expand...
Click to collapse
I did it on a Moto G5 with the latest Viper OS Oreo release, it doesn't work, can you help me please?
HourlongTuna5 said:
I did it on a Moto G5 with the latest Viper OS Oreo release, it doesn't work, can you help me please?
Click to expand...
Click to collapse
I'm afraid that this fix might be for Huawei only (no proof yet), maybe perhaps you can try with a similar moto phone?
(First time posting here please correct me if this is in the wrong place)
Hello
I have recently rooted my Pixel 2 XL with TWRP and Magisk and wanted to install Viper4Android. But when i try to install the drivers it stops and I get the message
"Installation failed at patching system"
I have the audio modification Library and also got it working on Android 10 before but 11 doesn't work right now.
My question is:
Has anybody already installed V4A on Android 11 successfully and knows a way to do it or will I have to wait for the official release and an updated V4A?
Unfortunately I have the same error with Pixel 2 XL and android 11 (also worked with 10).
I also tried "tricky" install procedures (like this: https://www.the***********.com/install-viper4android-android-10-guide/) but no success yet.
I think the issue is related to Magisk canary and only happens on Pixel 2 (and XL) devices with android 11.
viper4android & Android 11
I have the same issue as well..
Can't get anyone to answer, been to several site, asking the same question
R3vation said:
(First time posting here please correct me if this is in the wrong place)
Click to expand...
Click to collapse
The following thread will get the eyes of most people using Viper
https://forum.xda-developers.com/android/apps-games/app-viper4android-fx-2-6-0-0-t3774651
R3vation said:
I have recently rooted my Pixel 2 XL with TWRP and Magisk and wanted to install Viper4Android. But when i try to install the drivers it stops and I get the message
"Installation failed at patching system"
I have the audio modification Library and also got it working on Android 10 before but 11 doesn't work right now.
My question is:
Has anybody already installed V4A on Android 11 successfully and knows a way to do it or will I have to wait for the official release and an updated V4A?
Click to expand...
Click to collapse
A logcat of the install process would be my starting point. You also do not specify which version of Magisk you are using? If you wish to respond to me, use the above thread, but there will be people with a lot more targeted understanding of your issues on that thread.
DiamondJohn said:
The following thread will get the eyes of most people using Viper
https://forum.xda-developers.com/android/apps-games/app-viper4android-fx-2-6-0-0-t3774651
A logcat of the install process would be my starting point. You also do not specify which version of Magisk you are using? If you wish to respond to me, use the above thread, but there will be people with a lot more targeted understanding of your issues on that thread.
Click to expand...
Click to collapse
I'm also having same problem on pixel 4 XL and it's the new Android and magisk and also the way viper4android installation works i talked to dewitt and he say he will work on that as soon as he knows what changed in magisk
Scytherblack said:
I'm also having same problem on pixel 4 XL and it's the new Android and magisk and also the way viper4android installation works i talked to dewitt and he say he will work on that as soon as he knows what changed in magisk
Click to expand...
Click to collapse
Same for P4. Let me know that he says?
Xdevillived666 said:
Same for P4. Let me know that he says?
Click to expand...
Click to collapse
Yes sir that's only reason i switched back to Android 10 and Dewitt said he dont have no Android 11 running device to test so we'll just wait until android 11 is stable os and they release it for more device
I reckon we'll just need to be patient until the Devs look at compatibility upgrade for Android 11 - that has now been officially released. Everything works for me on my freshly rooted P4XL running R11, apart from V4A. But V4A is my most loved root app (next to Adblock, of course)
@R3vation
I have recently rooted my Pixel 2 XL with TWRP and Magisk and wanted to install Viper4Android. But when i try to install the drivers it stops and I get the message
"Installation failed at patching system"
Click to expand...
Click to collapse
In Magisk grant Viper4Android root permission, then all is good.
jwoegerbauer said:
@R3vation
In Magisk grant Viper4Android root permission, then all is good.
Click to expand...
Click to collapse
Tried that - few times now, no joy...
There might be hope...
Just tried this and it does seem to be working. Haven't fully tested it yet though. But I didn't bootloop and viper seems to work. Pixel 3a XL on Android 11. Rooted with Magisk Canary, e66b0bf3 (20425).
YouTube link
SirAugustine said:
Just tried this and it does seem to be working. Haven't fully tested it yet though. But I didn't bootloop and viper seems to work. Pixel 3a XL on Android 11. Rooted with Magisk Canary, e66b0bf3 (20425).
YouTube link
Click to expand...
Click to collapse
Works for me as well
SirAugustine said:
Just tried this and it does seem to be working. Haven't fully tested it yet though. But I didn't bootloop and viper seems to work. Pixel 3a XL on Android 11. Rooted with Magisk Canary, e66b0bf3 (20425).
YouTube link
Click to expand...
Click to collapse
Thanks mate
Same issue on Android 11 on my Oneplus 8 Pro. Would love an answer, or an alternative to Viper for the time being. Its one thing I can't seem to live without.
SirAugustine said:
Just tried this and it does seem to be working. Haven't fully tested it yet though. But I didn't bootloop and viper seems to work. Pixel 3a XL on Android 11. Rooted with Magisk Canary, e66b0bf3 (20425).
YouTube link
Click to expand...
Click to collapse
Can anyone confirm the safety of this file? Ichigo Kywrosaki is an anime character
State.of.mind said:
Can anyone confirm the safety of this file? Ichigo Kywrosaki is an anime character
Click to expand...
Click to collapse
The customize.sh is completely different, as well as the module.prop. They use completely different install methods.
This unofficial build seems to install the app as a system app, while the official module installs it as a user app. As a result, permissions are granted in a system-level config file, though none look suspicious.
I haven't compared APK files, so I don't know anything about the actual app code.
The only thing that I consider mildly suspicious is the fact that the app copies native audio library binaries into certain locations; these could potentially be malicious. I doubt that they are, though.
After installing this, my Pixel 3a has been randomly reporting 'missing codec' when attempting playback of FLAC files via MediaMonkey.
I also recently got the TRN BT20S bluetooth adapters for my IEMs, could be the intersection of the two, will keep testing.
Restart usually clears things up, but not the best solution.
I'm missing something, how do you download this form the link?
BracesForImpact said:
I'm missing something, how do you download this form the link?
Click to expand...
Click to collapse
Click the description of the video and there is a google drive link to dload it from
JackRandalt said:
This is why I never use Viper. I prefer Whatsapp. It never has such issues.
Click to expand...
Click to collapse
Wut? Whatsapp is a message app.
Hello,
After not touching any root related stuff in the last 2 years, I decided to root my new oneplus nord 2. It is running android 11.
I have magisk manager and I wanted to install an audio mod on it. First I tried Viper4Android, which didn't work in any way I tried, and cannot change SELinux to permissive sadly. V4A keeps prompting me to install the drivers even tho they are visible in Magisk.
After that I went to JamesDSP and tried installing that too. Tried both flashing it with Magisk, as well as installing the apk. In both cases as soon as I open the JamesDSP app, it opens up for half a second than closes again.
I've noriced the audio mod apps are kind of finicky. Was hoping some of you guys might be able to suggest some things I can try that I am unaware of. Or maybe an audio mod alternative that I haven't heard about?
NimeniAltu666 said:
Hello,
After not touching any root related stuff in the last 2 years, I decided to root my new oneplus nord 2. It is running android 11.
I have magisk manager and I wanted to install an audio mod on it. First I tried Viper4Android, which didn't work in any way I tried, and cannot change SELinux to permissive sadly. V4A keeps prompting me to install the drivers even tho they are visible in Magisk.
After that I went to JamesDSP and tried installing that too. Tried both flashing it with Magisk, as well as installing the apk. In both cases as soon as I open the JamesDSP app, it opens up for half a second than closes again.
I've noriced the audio mod apps are kind of finicky. Was hoping some of you guys might be able to suggest some things I can try that I am unaware of. Or maybe an audio mod alternative that I haven't heard about?
Click to expand...
Click to collapse
Ok I will taste some audio mods and let you know which is working for nord2
You're the real MVP. There's a chance I did something wrong or some detail I've missed along the way as quite some things have changed since I was into rooting and all these stuff.
NimeniAltu666 said:
You're the real MVP. There's a chance I did something wrong or some detail I've missed along the way as quite some things have changed since I was into rooting and all these stuff.
Click to expand...
Click to collapse
Sorry for I was using GSI today I will revert to OOS and then flash flash the audio mm OD and report back here
Hello, have you managed to get anything to work for an audio mod?
NimeniAltu666 said:
Hello, have you managed to get anything to work for an audio mod?
Click to expand...
Click to collapse
No tried each and every mod not working
Similar problem.. and the problem is ONLY switch seLinux - permessive/ ... How to be, I don't know
DeMiane said:
Similar problem.. and the problem is ONLY switch seLinux - permessive/ ... How to be, I don't know
Click to expand...
Click to collapse
We are releasing custom rom with Dolby Atmos working sooom
pankspoo said:
We are releasing custom rom with Dolby Atmos working sooom
Click to expand...
Click to collapse
link please
DeMiane said:
link please
Click to expand...
Click to collapse
Not released till now
pankspoo said:
Not released till now
Click to expand...
Click to collapse
)) Then why answer ...