Related
So i've seen a lot of viper/viper4arise ( + Dolby + etc ) on many threads...
with maybe way too many versions..
On 7.1.1 default OOS 4, I have mine worked just fine with the one coming from magisk repo.
I've tried the one from Magisk 14.5, processing says Abnormal..
and i can hear crackle sounds in the background when playing music.
Decided not to clutter my magisk modules with install/reinstall, i immediately restore from nandroid backup with clean magisk
( plus one google camera patch module only. )
So have anyone got anything worked on our new OOS 5.0 ?
preferably with Dolby atmos working ? i've never tasted this one on my 1+ device ever...
I also couln't get V4A to work with Magisk so I tried the one that I also have used in 7.1.1 and it seems to be working without any issues for now.
The link : https://androidfilehost.com/?fid=457095661767141554
Just flash it and you're good to go
Best Regards, Talpes
nicknacknuke said:
On 7.1.1 default OOS 4, I have mine worked just fine with the one coming from magisk repo.
I've tried the one from Magisk 14.5, processing says Abnormal..
and i can hear crackle sounds in the background when playing music.
Click to expand...
Click to collapse
If you're talking about the repo on the Magisk Manager, those V4A versions are horribly outdated.
Try the modules by ahrion, downloaded from the thread: https://forum.xda-developers.com/apps/magisk/module-viper4android-fx-2-5-0-5-t3577058
I personally have v2.0 working perfectly with Magisk 14.3. But also needed SELinux permissive module to process properly. Yeah, I know, a of folks are not going to want to set SELinux to permissive. But I'm just sharing what worked for me.
v2.3 wouldn't work properly for me. But one of the devs told me that I should delete all V4A and AML (Audio Mod Libs) and try to install through TWRP. Haven't had a chance to retry it doing all that. If you still have troubles, you can post the TWRP recovery log on the above thread, and they will try to help you out.
Dolby Atmos does not work on Oreo. Do NOT flash, bootloop is a possiblity.
This is how I got V4A working with OOS oreo. I had to set SELinux to permissive.
1. Use Magisk v14.5
2. Install 'Magisk SELinux Permissive Script' module by jman420 from within magisk manager (Modules -> + button -> select file)
https://forum.xda-developers.com/apps/magisk/module-magisk-selinux-permissive-script-t3577549
3. Reboot. Optional - Install 'Display SELinux status' module in magisk
4. Install 'Viper4Android FX for Magisk v14+' v4.0 by ShadySquirrel in magisk manager. You can get it from Magisk repo. (Other V4A modules might work too.)
5. Reboot and voila!
Okay... so far there are 3 alternatives to get this audio mod in Oreo
I will try them and test...
Let's say, this is my attempt to keep track of how to install in oreo..
Thank you guys for all the suggestions ( and warning ! )
talpes said:
I also couln't get V4A to work with Magisk so I tried the one that I also have used in 7.1.1 and it seems to be working without any issues for now.
The link : https://androidfilehost.com/?fid=457095661767141554
Just flash it and you're good to go
Best Regards, Talpes
Click to expand...
Click to collapse
did this version require any SELinux permissive trickery?
Brian
Yes it does but you don't have to install separate apps or magisk modules to archive that. After you flashed the whole thing, open Viper - Settings - Turn on developer mode and disable SELinux. That's it.
Talpes
redpoint73 said:
If you're talking about the repo on the Magisk Manager, those V4A versions are horribly outdated.
Try the modules by ahrion, downloaded from the thread: https://forum.xda-developers.com/apps/magisk/module-viper4android-fx-2-5-0-5-t3577058
I personally have v2.0 working perfectly with Magisk 14.3. But also needed SELinux permissive module to process properly. Yeah, I know, a of folks are not going to want to set SELinux to permissive. But I'm just sharing what worked for me.
v2.3 wouldn't work properly for me. But one of the devs told me that I should delete all V4A and AML (Audio Mod Libs) and try to install through TWRP. Haven't had a chance to retry it doing all that. If you still have troubles, you can post the TWRP recovery log on the above thread, and they will try to help you out.
Click to expand...
Click to collapse
On my attempt with your method, It installs just fine with TWRP, but fail on running.
- Installed just fine with TWRP, no errors. (*)
- Reboot, but i can not find the V4A apps in drawer...
- So i opened up the zip file, extract the APK from v4afx-v2.3.zip/system/app/ViPER4AdnroidFX.apk.
- Install it manually, then it shows up in drawer.
- Everytime i try to run it.. it keeps asking to install drivers. I assume because it wasn't install in /system
( confirm install, reboot, then it asks to install again when i open it ).
So i decide your method does not works well on my device... or i may have missed something in the steps.
( Stock OOS 5.0, Bluspark's 8.54 TWRP, Magisk 14.5 )
fluster84 said:
This is how I got V4A working with OOS oreo. I had to set SELinux to permissive.
1. Use Magisk v14.5
2. Install 'Magisk SELinux Permissive Script' module by jman420 from within magisk manager (Modules -> + button -> select file)
https://forum.xda-developers.com/apps/magisk/module-magisk-selinux-permissive-script-t3577549
3. Reboot. Optional - Install 'Display SELinux status' module in magisk
4. Install 'Viper4Android FX for Magisk v14+' v4.0 by ShadySquirrel in magisk manager. You can get it from Magisk repo. (Other V4A modules might work too.)
5. Reboot and voila!
Click to expand...
Click to collapse
Your method works OK on my device :good:
so we are only limited to v4A ? no Arise, or Dolby atmos ?
i see some OP3T users saying they got it working on their device with Oreo ..
talpes said:
I also couln't get V4A to work with Magisk so I tried the one that I also have used in 7.1.1 and it seems to be working without any issues for now.
The link : https://androidfilehost.com/?fid=457095661767141554
Just flash it and you're good to go
Best Regards, Talpes
Click to expand...
Click to collapse
It said aroma, i'm on stock ROM.. is it safe ?
I will take nandroid backup and try it...
EDIT:
My mistake for not understanding aroma installer.
Tried your method, only install v4a 2.5, and DD Plus..
No errors, when playing music, V4A says abnormal. Second tries, i can not even get the Driver Status to popup.
Dolby Digital seems to work, but it quit everytime i changed the mode, but sound does noticably change.
*rolling back to nandroid backup*
nicknacknuke said:
On my attempt with your method, It installs just fine with TWRP, but fail on running.
- Installed just fine with TWRP, no errors. (*)
- Reboot, but i can not find the V4A apps in drawer...
- So i opened up the zip file, extract the APK from v4afx-v2.3.zip/system/app/ViPER4AdnroidFX.apk.
- Install it manually, then it shows up in drawer.
- Everytime i try to run it.. it keeps asking to install drivers. I assume because it wasn't install in /system
( confirm install, reboot, then it asks to install again when i open it ).
So i decide your method does not works well on my device... or i may have missed something in the steps.
( Stock OOS 5.0, Bluspark's 8.54 TWRP, Magisk 14.5 )
Click to expand...
Click to collapse
You tried ahrion's module, v2.0 like I said (you listed all other version number details but that one)? Newer ones don't work for me; I tried 2.3 and 2.4, and same error you have - no V4A app in app tray.
Also, I'm on Magisk 14.3 (as mentioned) so another variable there.
redpoint73 said:
You tried ahrion's module, v2.0 like I said (you listed all other version number details but that one)? Newer ones don't work for me; I tried 2.3 and 2.4, and same error you have - no V4A app in app tray.
Also, I'm on Magisk 14.3 (as mentioned) so another variable there.
Click to expand...
Click to collapse
Could you upload v2.0?
redpoint73 said:
You tried ahrion's module, v2.0 like I said (you listed all other version number details but that one)? Newer ones don't work for me; I tried 2.3 and 2.4, and same error you have - no V4A app in app tray.
Also, I'm on Magisk 14.3 (as mentioned) so another variable there.
Click to expand...
Click to collapse
my bad for not paying attention
but i'm a bit reluctant to downgrade my magisk
i've managed to get mine working as per Post #5,
i saw there's a new version just came out from ahrion ( v4afx-v2.4.zip , 11/30/2017 ).
I might gonna give it a try also with magisk 14.5...
Hi,
I have a Nokia 7 Plus TA-1046 running official Android Pie 9.0 with September 2018 patch level and build number 00WW_3_22C. The bootloader is unlocked.
Upon booting a patched boot.img using MagiskManager 6.0 canary build with a debug version of Magisk 17.3 canary build as well, the system experiences some system glitches as follows:
1) Vibration intensity for haptic feedback is increased
2) Certain system gestures become unavailable like Lift to check phone or Swipe up from home
3) Double tap to wake becomes unavailable
4) Some other glitches I may have missed
The thing is that as soon as the system is restarted, said glitches disappear and the system returns to normal. The same is also observed even when Direct Install Magisk to the system after achieving root privileges and then uninstalling afterwards. No modules were used nor installed upon testing.
This did not happen back when the system was running Android Oreo 8.1. It seems that having Magisk is causing glitches to this system running Pie, at least on this hardware.
I could not zero in on where the issue may be, so perhaps someone would be able to guide me on troubleshooting this further. I'm attaching the debug logs upon patching the boot.img and booting it subsequently via fastboot.
I could also provide screenies for the missing gestures before and after applying the Magisk patch.
-ianp
EDIT: The XDA labs is having a hard time uploading and attaching a sub 10kb log file to this post, so I am providing a pastebin link to the install and run logs.
Install: https://pastebin.com/ZTAxxG50
Run: https://pastebin.com/15XCZ0Sc
I made the jump from MIUI10 to 11. Viper4android works fine on my other Android 10 device (after the small bootloop fix of deleting post-fs-data.sh in /data/adb/modules/Viper4AndroidFX).
I did the same procedure as I did with my other Android 10 device. Now every time I start v4a it just asks me to install the driver again.
Any ideas? SELinux is most likely enforcing but I'd rather not change that if I don't need to. I'm pretty sure it's permissive on my other handset.
droident said:
I made the jump from MIUI10 to 11. Viper4android works fine on my other Android 10 device (after the small bootloop fix of deleting post-fs-data.sh in /data/adb/modules/Viper4AndroidFX).
I did the same procedure as I did with my other Android 10 device. Now every time I start v4a it just asks me to install the driver again.
Any ideas? SELinux is most likely enforcing but I'd rather not change that if I don't need to. I'm pretty sure it's permissive on my other handset.
Click to expand...
Click to collapse
You didn't see this below?
https://forum.xda-developers.com/k20-pro/themes/guide-viperfx-miui-11-android-10-t3994621
droident said:
I made the jump from MIUI10 to 11. Viper4android works fine on my other Android 10 device (after the small bootloop fix of deleting post-fs-data.sh in /data/adb/modules/Viper4AndroidFX).
I did the same procedure as I did with my other Android 10 device. Now every time I start v4a it just asks me to install the driver again.
Any ideas? SELinux is most likely enforcing but I'd rather not change that if I don't need to. I'm pretty sure it's permissive on my other handset.
Click to expand...
Click to collapse
Is v4a really worth it in miui? There are inbuilt equilizers
Hi,
I've installed Magisk Manager 23014 and flashed the latest canary build.
When I go to settings and enable Zygisk it keeps perpetually telling me to "Reboot to apply changes", of course, I did but Zygisk remains disabled.
I'm on a Note 9, running DevBase v7.4 based on the S9FUH1 rom (Android 10)
Are you entirely sure that you have the 23014 Magisk binaries installed, and not just the app? This is the kind of behaviour we've seen when there's a mismatch between app and binaries versions.
What is the version info displayed in the Magisk app?
The Magisk version is: 7e9d4512 (23014)
Magisk App: 7e9d4512 (23014)
I just tried a full uninstall of the old Magisk install and then a fresh install of canary to make sure no previously installed modules could interfere, but no change unfortunately.
I'm also not seeing any errors in the log viewer of the magisk app
Could you post those logs?
Didgeridoohan said:
Could you post those logs?
Click to expand...
Click to collapse
Sure, please find the /cache/magisk.log and one saved from within Magisk Manager attached
So I run into the same problem. As I can't see anything useful in the magisk logs, I figured I'd check the dmesg.
This is one line that kind of triggers me, but I can't tell if it's significant:
Code:
[ 8.879227] init: Command 'start zygote_secondary' action=persist.sys.zygote.early=true (/init.rc:2197) took 0ms and failed: service zygote_secondary not found
This is on a Samsung J600fn.
Not sure if it makes a difference, but after disabling verity and encryption (either could be the culprit) it worked for me.
I had the same issue on my note 9. Disabling verity and encryption worked for me too as per FreakyJoosts post.
I used this (flashed via TWRP): https://mega.nz/file/6YszWYoB#dAQcttv6AvFK6HxY2oVuaGy-iouRG9uR77AnbXOqcWM
Which I got from this guide:
[Guide] Root Note 9 (Exynos) Android 10 (Q) With/Out Custom Recovery
How to Root Note 9 with Magisk on Android 10 (Q) without Custom Recovery (Eg.. TWRP) This method will work with most of the latest Samsung devices running Android 9/10. (Tested and Working on Galaxy Note 9 (Exynos) with Android 10 Q). WARNINGS...
forum.xda-developers.com
FreakyJoost said:
So I run into the same problem. As I can't see anything useful in the magisk logs, I figured I'd check the dmesg.
This is one line that kind of triggers me, but I can't tell if it's significant:
Code:
[ 8.879227] init: Command 'start zygote_secondary' action=persist.sys.zygote.early=true (/init.rc:2197) took 0ms and failed: service zygote_secondary not found
This is on a Samsung J600fn.
Click to expand...
Click to collapse
You may be right. But why don't you post it to GitHub before the stable release?
Anyway, try this build:
yujincheng08 said:
You may be right. But why don't you post it to GitHub before the stable release?
Anyway, try this build:
Click to expand...
Click to collapse
I found the problem on this forum.. not github. Also this thread didn't mention a github issue this would be linked to.
As for trying the other build. I already have it fixed. As mentioned before, I disabled encryption and verity.
Maybe @Adrixan can still try?
FreakyJoost said:
I found the problem on this forum.. not github. Also this thread didn't mention a github issue this would be linked to.
As for trying the other build. I already have it fixed. As mentioned before, I disabled encryption and verity.
Maybe @Adrixan can still try?
Click to expand...
Click to collapse
you can open a new issue on github at any time though.
Anyway, disabling encryption is not a gentle fix. You can try to re-enable the encryption for the try.
Today I faced the same problem. I had encryption off already but flashed so I figured that one of my modules causes this. So basicly just remove all old modules to enable Zygisk. Probably some outdated module blocks Zygisk.
I finally found a solution guys if your zygisk is not enabling even if you enable and you reboot or you install a GSI like pixel experience/pixel experience plus etc it has a solution
1: you have to be rooted
2: enable zygisk
3: download and flash pixel launcher mod here you can download it from a telegram link : Mod edit: Inactive TG link removed.
Install and flash and check zygisk should be enabled if it’s still not enabling send me logs
Only for Realme GT 2 (Snapdragon 888)
~15% performance increase
Pre Requisites: Rooted device
Original version: 530
Updated version: 615.65
Unstable Update: 682
How to Install: flash both the Magisk overlayfs module and Adreno GPU driver module given below and reboot
How to Uninstall: after flashing and rebooting come to Magisk modules section and remove both modules and reboot
Optional: Install bootloop protector Magisk module given below
Source: https://t.me/adreno_konabess/879129
Edit: Updated to 615.65 (1-2% performance increase from 615.50) and added Unstable 682 for people who wanna experiment (additional 3% performance increase over 615.65)
If some app doesn't work with it then add it to magisk hide and it will use stock drivers
I found in the group "updated" version of this drivers, with the old one I have problems with few applications, with this one for now I didn't have problems, some user report the about issue with firefox only.
Flash with Magisk.
b0nb0n3v said:
I found on the group "updated" version of this drivers, with the old one I have problems with few applications, with this one for now I didn't have problems, some user report the about issue with firefox only.
Flash with Magisk.
Click to expand...
Click to collapse
Nice, use the one that's more stable for you, for me genshin Impact had several artifacts/crashes with 615.50 so i resorted to 615
UNFORTUNATELY - After updating by DRIVERS through this method - my Whatsapp stopped working - the media stopped playing on my phone - don't know what went wrong - after removing the module - everything went back to normal!
I'm using RMX3312 on POS!
Prajwal_Beast said:
UNFORTUNATELY - After updating by DRIVERS through this method - my Whatsapp stopped working - the media stopped playing on my phone - don't know what went wrong - after removing the module - everything went back to normal!
I'm using RMX3312 on POS!
Click to expand...
Click to collapse
Hi, that didn't happen for me but I haven't tried pixel OS so can't confirm however you can try using the driver and adding WhatsApp to magisk hide apparently it uses stock drivers if u add app to magisk hide
Updated, actually works now and u can use 615.50 now
Latest driver from you are much better. I see one glitch on every version, as example I use Brave browser and have some tab, when I switch from active tab to inactive tab, some visual bugs/glitch are appeared. But this is not an issue. I will report after some day of tests.
Link to video of the glitch.
b0nb0n3v said:
Latest driver from you are much better. I see one glitch on every version, as example I use Brave browser and have some tab, when I switch from active tab to inactive tab, some visual bugs/glitch are appeared. But this is not an issue. I will report after some day of tests.
Link to video of the glitch.
Click to expand...
Click to collapse
Go to magisk manager and add the app that has these glitches to magisk hide, this will use stock drivers