Related
Greetings!
The latest beta (v14.1) of Magisk just dropped (Magisk Beta Thread), which is the first release to officially support Pixel (XL).
Before I spend more time investigating TWRP and Magisk combination, please refrain from flashing Magisk through TWRP installed in your boot image (because Magisk cannot get a 100% stock boot backup)
The recommended way to install Magisk on Pixel (XL) are
Fastboot boot this TWRP Image, and flash the Magisk zip
Get a stock boot image (download the full factory image here), and patch via Magisk Manager, then flash the patched boot by fastboot
Once you got over the ""initial pain" and get Magisk installed with proper stock boot image backup, it is very easy to migrate Magisk across OTA updates on Pixel devices.
This thread is not a support thread, all bug reports should be in the Magisk Beta Thread, discussions should be in Magisk General Discussions
------------------------------------------------------------------------------------------------
The followings are for Pixel (XL) developers:
I've written some descriptions on how Magisk works on Pixel devices in my Release Notes for v14.1.
You can directly check MagiskInit's code here. The code is fairly simple so you should get the idea.
However, I'm still fairly new to Pixel development, and I'm not sure how current custom roms and custom kernels workaround the skip_initramfs thing. Instead of trying all custom roms and custom kernels out, I think it would be easier for me to just open a thread and ask
I would like to have some insight from developers whether my Magisk solution can work well with current Pixel development projects. Since all my work is open source, if you have some suggestions to improve my work, please tell me and I'll be really grateful.
I've been waiting for this for a long time.Thank you.
Yaaay! Thank you! I've been waiting for official
Keep up the good work, and congrats!
Works fine here " Android 8.0 "
ElementalX + Magisk 14.1 + Twrp 3.1.1-0 ( Twrp Sticks ) Root also works.
Thanks OP!!!!
WOOOOT WOOOOT
Tylog said:
Works fine here " Android 8.0 "
ElementalX + Magisk 14.1 + Twrp 3.1.1-0 ( Twrp Sticks ) Root also works.
Click to expand...
Click to collapse
How did you flashed them what is your Order ?
I literally booted into recovery (via fastboot) nandroid backed up my boot partition and then flashed magisk so if anything goes wonky I have a backup
tessut said:
How did you flashed them what is your Order ?
Click to expand...
Click to collapse
Stock Boot img , TWRP , MagisK , reboot .
Back to recovery
ElementalX , TWRP , MagisK , reboot.
Done.
Hello
I am currently on stock , so for me the steps will be :
Fastboot TWRP , install Magisk and reboot
Reboot to recovery
EX kernel , TWRP, Magist and reboot
Correct ?
Everything works fine except mobile network connection after install 14.1 beta.
Can make/receive call, but can't connect to mobile network.
My install step is:
1.flash-all with opr3 full package.
2.Setup Pin code. ( mobile network works)
3.Flash both boot slot with stock boot.img. (mobile network works)
4.Boot to twrp 3.1 and install ElementalX 2.01 than reboot. (mobile network works)
5..Boot to twrp 3.1 and install Magisk 14.1beta than reboot. (mobile network fail)
6.Full uninstall Magisk with Magisk Manager than reboot. (mobile network works again)
Anyone has the same problem?
I'm still on a custom rom based on 7.1.2 and all i had to do is flash magisk 14.1 zip using twrp RC2. Everything works fine. Had to manually install magisk manager tho.
chowtom said:
Everything works fine except mobile network connection after install 14.1 beta.
Can make/receive call, but can't connect to mobile network.
My install step is:
1.flash-all with opr3 full package.
2.Setup Pin code. ( mobile network works)
3.Flash both boot slot with stock boot.img. (mobile network works)
4.Boot to twrp 3.1 and install ElementalX 2.01 than reboot. (mobile network works)
5..Boot to twrp 3.1 and install Magisk 14.1beta than reboot. (mobile network fail)
6.Full uninstall Magisk with Magisk Manager than reboot. (mobile network works again)
Anyone has the same problem?
Click to expand...
Click to collapse
No problem here was 8.0 stock latest installed 14.1 and everything works.
If i'm already rooted and on Su and SuHide, how does one go about installing Magisk
Rockstar! Nice to be certified once again...
Thank you
---------- Post added at 01:13 PM ---------- Previous post was at 01:08 PM ----------
Nexus6pMyPhone said:
If i'm already rooted and on Su and SuHide, how does one go about installing Magisk
Click to expand...
Click to collapse
Hello,
Follow the instructions on the SULite site for removal and also uninstall the SU app itself. Download the full September Oreo zip and remove the -w from the bat file. Then execute the bat file from bootloader which will flash the full Oreo image. This will give you a new boot image that is not rooted and one Magisk can patch.
Cheers
chowtom said:
Everything works fine except mobile network connection after install 14.1 beta.
Can make/receive call, but can't connect to mobile network.
My install step is:
1.flash-all with opr3 full package.
2.Setup Pin code. ( mobile network works)
3.Flash both boot slot with stock boot.img. (mobile network works)
4.Boot to twrp 3.1 and install ElementalX 2.01 than reboot. (mobile network works)
5..Boot to twrp 3.1 and install Magisk 14.1beta than reboot. (mobile network fail)
6.Full uninstall Magisk with Magisk Manager than reboot. (mobile network works again)
Anyone has the same problem?
Click to expand...
Click to collapse
Yep, worked fine after flashing rom then magisk. Rebooted to flash EX kernel, after coming back magisk manager said it wasn't installed. Rebooted, flashed magisk again, came back and I had no mobile network connection, and my wifi connection appeared to work fine but in actuality nothing loaded. Also, camera was totally blank.
Update: Magisk 14.2 (just released) seems to fix issues with networking and camera. Running EX and Magisk together without issue, except...
SafetyNet check in Magisk shows both checks as false, and I can confirm as I'm unable to sign into snapchat lol.
One more update: Netflix and root checker behave how they should with Magisk hide enabled, but SafetyNet test, Magisk's SafetyNet checker, and Snapchat don't. Have tried turning off USB debugging, Magisk Hide box is checked, and SELinux is Enforcing. Just trying to be thorough with info I give.
Are you able to use the sky go app with Magisk 14.1 on the Pixel? Suhide fails to hide root from sky go
any one have the issue where you don't have magisk manager installed after flashing 14.2? or am i doing something wrong?
[email protected] said:
any one have the issue where you don't have magisk manager installed after flashing 14.2? or am i doing something wrong?
Click to expand...
Click to collapse
you have to download and install the apk separately
EDIT: hm... not seeing a download for the 5.3.5 version of the app :S
EDIT 2: https://github.com/topjohnwu/MagiskManager/releases
there should be version 5.3.5
WarningHPB said:
you have to download and install the apk separately
EDIT: hm... not seeing a download for the 5.3.5 version of the app :S
Click to expand...
Click to collapse
yup, I didnt see it either so i assumed it must install apk while flashing like it used to.
i dont see any apk to download and i dont see anything mentioned about this.
attaching recovery log. hope it helps @topjohnwu
[email protected] said:
yup, I didnt see it either so i assumed it must install apk while flashing like it used to.
i dont see any apk to download and i dont see anything mentioned about this.
attaching recovery log. hope it helps @topjohnwu
Click to expand...
Click to collapse
apologies i edited my post a few times you might not have seen the second one there's a download link on the git hub
EDIT 2: https://github.com/topjohnwu/MagiskManager/releases
there should be version 5.3.5
Click to expand...
Click to collapse
Hi. Maybe some of you have these files but i'll share mod i use on custom roms and LOS 15.1.
I can add to OP more if you share on this topic
Original LOS 15.1 Thread by @OrdenKrieger https://forum.xda-developers.com/axon-7/development/unofficial-lineageos-15-1-zte-axon-7-t3800214
Google Camera for HDR+ and Portrait Mode on Front Camera
https://drive.google.com/open?id=1CZAoa_9HQDnrM-F1qIYDpczuHmZXrfZw
Use pico gapps to use GCam.
Change buttons back and recent. Thanks @kevte89
https://drive.google.com/open?id=1SjY1-uIZ0kTayJ0vouHP2LyaKWPHN_SV
Magisk 16.4 to Root.
https://github.com/topjohnwu/Magisk/releases/download/v16.4/Magisk-v16.4.zip
To Fix Daydream. Thanks to @LuccoJ
https://forum.xda-developers.com/showpost.php?p=76806563&postcount=303
Add the addonsu to root with Magisk (and remove addonsu) https://download.lineageos.org/extras
or
Just root within twrp 3.2.17 (@NFound) - tested by @DarkQuark
@WesTD why the need to use pico gapps? Can't you choose aroma and not install Google Camera or use gapps config to disable it being installed.
@raystef66 you need to install the addonsu, remove it and then install magisk? Why can't you just install magisk?
Dodgexander said:
@WesTD why the need to use pico gapps? Can't you choose aroma and not install Google Camera or use gapps config to disable it being installed.
@raystef66 you need to install the addonsu, remove it and then install magisk? Why can't you just install magisk?
Click to expand...
Click to collapse
You can install magisk when on 3217 as i heard without addonsu but this one runs 3216.
Just use the addonsu and then flash 16.4 and you'll be good to go.
EDIT : maybe 3.2.1.6 can root too without the addonsu but i never tested that. But like said no harm done to use the addonsu
Dodgexander said:
@WesTD why the need to use pico gapps? Can't you choose aroma and not install Google Camera or use gapps config to disable it being installed.
@raystef66 you need to install the addonsu, remove it and then install magisk? Why can't you just install magisk?
Click to expand...
Click to collapse
IDK why but camera has stopped if I install mini or higher
raystef66 said:
You can install magisk when on 3217 as i heard without addonsu but this one runs 3216.
Just use the addonsu and then flash 16.4 and you'll be good to go.
EDIT : maybe 3.2.1.6 can root too without the addonsu but i never tested that. But like said no harm done to use the addonsu
Click to expand...
Click to collapse
I'll have to try when I install it and report back here.
WesTD said:
IDK why but camera has stopped if I install mini or higher
Click to expand...
Click to collapse
Very strange when mini doesn't include camera. The only apps in mini that have anything to do with the camera are face detect and photos.
WesTD said:
Google Camera for HDR+ and Portrait Mode on Front Camera
https://drive.google.com/open?id=1CZAoa_9HQDnrM-F1qIYDpczuHmZXrfZw
Click to expand...
Click to collapse
Is HDR+ and Portrait Mode only working on the front camera?
Any news about the stock camera?
There have been flashable zips in the path if I'm not mistaken, none for oreo after all I know, right?
joaocandeias said:
Is HDR+ and Portrait Mode only working on the front camera?
Click to expand...
Click to collapse
Both rear and front
Just to update here with my findings.
1. Magisk 16.4 works fine installing straight, no reason to install addonsu.
2. Installed aroma gapps from open gapps and it works fine apart from bizarre occasional "Google has stopped " messages.
3. I can't comment on the Google camera shared here but the latest recommend pixel mod camera from here: https://www.celsoazevedo.com/files/android/google-camera/dev-arnova8G2/#apk285 works relatively well, crashed on me once trying slow motion but everything else seems to work. I did not come across the problem mentioned here where certain gapps break gcam.
This is all fresh install, unencrypted, A2017U using universal bootstack and U modem and Nfound TWRP .6.
Is there any reason you chose that exact version of Gcam @WesTD ?
I have been using the latest version arnovas mod and today it crashed quite often taking photos. It also didn't work well recording UHD video and lagged during one of my recordings.
WesTD said:
Hi. Maybe some of you have these files but i'll share mod i use on custom roms and LOS 15.1.
I can add to OP more if you share on this topic
Click to expand...
Click to collapse
You should add this magisk mod to fix issues with DayDream:
https://forum.xda-developers.com/showpost.php?p=76806563&postcount=303
Liquid5n0w said:
You should add this magisk mod to fix issues with DayDream:
https://forum.xda-developers.com/showpost.php?p=76806563&postcount=303
Click to expand...
Click to collapse
Thanks, added OP
Just a general, unimportant question. What's the deal with LOS-based ROMs and cLock? cLock displays weather with the aid of weather providers since Marshmallow I think.
On Oreo none of them seem to work. They install normally but the systems don't see them as providers. Not even Chronus which also acts as a provider.
Just wondering (out loud) why cLock is still included if it's not fully functional anymore.
ZTE Axon 7 A2017U, AospExtended v5.4 ROM, HellsGate Kernel, Multiboot, Tapatalk 4.9.3
Whenever I install magisk the device can't boot in the OS. It just boots in fastboot mode every time and the only way to get it back is re-install the OS from recovery mode (TWRP). So far I have tested with version 16.0 and 16.4, and got the same results on both.
Any idea why this is happening?
laglink said:
Whenever I install magisk the device can't boot in the OS. It just boots in fastboot mode every time and the only way to get it back is re-install the OS from recovery mode (TWRP). So far I have tested with version 16.0 and 16.4, and got the same results on both.
Any idea why this is happening?
Click to expand...
Click to collapse
Yes, it's normal. It was mentionened in other threasds already, that this happens. 16.7 should work though, only hide does not work properly.
WesTD said:
Change buttons back and recent. Thanks @kevte89
https://drive.google.com/open?id=1SjY1-uIZ0kTayJ0vouHP2LyaKWPHN_SV
Click to expand...
Click to collapse
The "swap back and recent" doesn't seem to be working. I'm running the 09/25 build of Lineage 15.1. After a flash and reboot, the buttons work exactly as before.
I tried finding the source of that file, but the user you linked doesn't seem to have any posts here. Could you link the source thread?
orangeisnon said:
The "swap back and recent" doesn't seem to be working. I'm running the 09/25 build of Lineage 15.1. After a flash and reboot, the buttons work exactly as before.
I tried finding the source of that file, but the user you linked doesn't seem to have any posts here. Could you link the source thread?
Click to expand...
Click to collapse
Or try this, mount Vendor : https://androidfilehost.com/?fid=1322778262903999789
raystef66 said:
Or try this, mount Vendor : https://androidfilehost.com/?fid=1322778262903999789
Click to expand...
Click to collapse
I've been pulling my hair out for the last few days trying to get the back button on the right side. Unfortunately, this one didn't work for me either. Am I doing something wrong? I reboot into TWRP 3.2.1-8, go to mount, select vendor, go to install, select file, voila. Everything says it installs, no errors, etc, and then there's no change when I boot into system again.
orangeisnon said:
The "swap back and recent" doesn't seem to be working. I'm running the 09/25 build of Lineage 15.1. After a flash and reboot, the buttons work exactly as before.
I tried finding the source of that file, but the user you linked doesn't seem to have any posts here. Could you link the source thread?
Click to expand...
Click to collapse
bradyarz said:
I've been pulling my hair out for the last few days trying to get the back button on the right side. Unfortunately, this one didn't work for me either. Am I doing something wrong? I reboot into TWRP 3.2.1-8, go to mount, select vendor, go to install, select file, voila. Everything says it installs, no errors, etc, and then there's no change when I boot into system again.
Click to expand...
Click to collapse
It should work under /verdor
Or do it manualy in /vendor/usr/keylayout/synaptics_dsx.kl or search that file
Code:
key 158 APP_SWITCH
key 102 HOME
key 187 BACK
key 143 WAKEUP
I used it in LOS16 and all other Pie roms and working ok. Never tried it on LOS15
After a few failed attempts (using Audio Modification module etc.) I found a way to get Viper working on the Mi 9. installed on the rooted Xiaomi.eu rom via TWRP and Magisk.
1. Download the Viper4Android_FX-v3.4.2.zip via Magisk but don't install it via Magisk
2. Boot to TWRP and flash the Viper zip and then adhere to the following:
- Press a volume button when prompted to do so
- Volume down (to choose vol key installation method)
- Vol up (for new 2.5.0.5)
- Vol up (for material, if preferred)
- Vol up (for system app)
- Vol up (for lib workaround to be installed)
3. Reboot
4. Via Magisk find and install "Init.d injector" and then reboot
Viper4Android should now be processing your audio!
Rommco05 said:
Installation from Magisk doesn't work? Just curious
Click to expand...
Click to collapse
Not the usual way. On my Pixel 2 XL, either the magisk module would work out of the box or using the Audio Modification Library module would make it work. I tried both of these ways, with no success the driver just wouldn't install. Tried the XDA labs apk, along with the Audio Modification Library, didn't work. Was even waiting a few minutes after boot as I know sometimes/some roms it takes a few minutes to initialise.
After lots of playing around of different versions, I tried that additional installation step of the lib workaround, which states that init.d support is needed too. With the use of that extra init.d module, it works!
I spent some time doing this and figured I'd help out others when they come to do it too!
I managed to install via Magisk?? Maybe due to a Magisk update?
*justintime* said:
I managed to install via Magisk?? Maybe due to a Magisk update?
Click to expand...
Click to collapse
Ahh yeah that's fair enough! Probably flashing via TWRP isn't necessary, so long as the additional init module is there too
Rommco05 said:
Installed init and after Viper4 from Magsik and didn't work, need flash ot trough twrp, today...
Click to expand...
Click to collapse
Ah tgats handy to know! My initial istructions remain valid then
Rommco05 said:
Installed init and after Viper4 from Magsik and didn't work, need flash ot trough twrp, today...
Click to expand...
Click to collapse
Funny with twrp it wasn't working for me...... Magisk had an update. "Check updates canary build' in manager.
And it was a straight away. Flash.... Only no equalizer in usb/dock out though for Android auto
Rommco05 said:
btw after last Magisk update I was able install Viper4 over manager. I also installed that last option (fix)
Click to expand...
Click to collapse
Thanks, that's handy to know!
I simply couldn't get viper4android to work and didn't have much luck with the init.d injector... I ended up following your steps and installed a custom kernel and emulated init.d via the kernel auditor app.... Now its working perfectly!
Have any of you tried the ainur sauron mod on the mi 9?
hi is it possible to get viper4android work with magisk flash? because i don't want twrp and loosing encryption.
when i flash trough magisk viper4android app doesn't appear?
thank you
(sorry for bad english)
dffhgg said:
hi is it possible to get viper4android work with magisk flash? because i don't want twrp and loosing encryption.
when i flash trough magisk viper4android app doesn't appear?
thank you
(sorry for bad english)
Click to expand...
Click to collapse
Possibly...
Have you tried rebooting? Otherwise I'm unsure I'm afraid....
cd993 said:
Possibly...
Have you tried rebooting? Otherwise I'm unsure I'm afraid....
Click to expand...
Click to collapse
yes for sure i rebooted many times but no success..
always viper4android doesn't appear
i also tried install via apk download viper4android then install there also not work, after reboot it reask to install driver.
dffhgg said:
yes for sure i rebooted many times but no success..
always viper4android doesn't appear
i also tried install via apk download viper4android then install there also not work, after reboot it reask to install driver.
Click to expand...
Click to collapse
And this is with the init d module as well?
with init.d injector module from magisk? yes i installed it alredy
dffhgg said:
with init.d injector module from magisk? yes i installed it alredy
Click to expand...
Click to collapse
And you're on the latest eu rom?
Hmm all I can suggest is to remove fully uninstall viper, the init d module and make sure no other audio mods are installed, reboot, then install viper again (ensuring to choose yes to the lib workaround) and the init d module.
If that doesn't work, then unfortunately I'm out of ideas as I tried lots 9f things and this was the only method that worked for me.
Good luck
yes i'm on 10.2.17
i will give it a try and let you know.
hope will work thank you
dffhgg said:
yes i'm on 10.2.17
i will give it a try and let you know.
hope will work thank you
Click to expand...
Click to collapse
I'm on the latest weekly 9.4.11, if that makes any difference
can i flash this version whithout data loss?
i tried reinstall everything but no succes
hi guys my problem is solved!
what i did:
change selinux to permissive with this tool: Kernel SEPolicy patcher https://zackptg5.com/android.php
now viper4android is detect driver its full work!
dffhgg said:
hi guys my problem is solved!
what i did:
change selinux to permissive with this tool: Kernel SEPolicy patcher https://zackptg5.com/android.php
now viper4android is detect driver its full work!
Click to expand...
Click to collapse
Great! I'll save that just in case I ever need it
keep getting the following error
Checking for Digest files
Skipping Digest check: no digest file found
on twrp 3.3.0 b8 and latest EU rom
Does anyone have Viper4Android successfully running on their F1? I just can't get it to work, I've tried everything from installing through Magisk to flashing the zip with TWRP, even tried different options during installation.
Driver Status is as follows:
Driver Version: 2.5.0.4
NEON Enabled: No
Enabled: No
Status: Abnormal
Audio Format: Unsupported
Processing: No
Sampling: 0
Running Stock Pie, no other Audio processing app installed.
BTW I've tried a search on Google but all solutions are mostly specific to previous Android versions or device/brand specific.
Thanks for any help
David C.
mantarkus said:
Does anyone have Viper4Android successfully running on their F1? I just can't get it to work, I've tried everything from installing through Magisk to flashing the zip with TWRP, even tried different options during installation.
Driver Status is as follows:
Driver Version: 2.5.0.4
NEON Enabled: No
Enabled: No
Status: Abnormal
Audio Format: Unsupported
Processing: No
Sampling: 0
Running Stock Pie, no other Audio processing app installed.
BTW I've tried a search on Google but all solutions are mostly specific to previous Android versions or device/brand specific.
Thanks for any help
David C.
Click to expand...
Click to collapse
UPDATE: Turn out this version of Viper4Android needs SELinux Disabled, I noticed this going through Viper4Android's settings where in Developer Mode there is an option to disable SELinux momentarily, doing this brought full processing to V4A.
I installed SELinx Switch to set as Permissive on reboot.
App works great now although I remember on my previous devices you didn't need SELinux control when installing V4A from Magisk.
If anyone has a better information and advice let me know but so far this worked great.
David C.
I always had better luck with the twrp aroma flashable zips. The ones that install from withing twrp or now you can install inside of Magisk though I don't know if we have Magisk for F1/F1P yet
Hi guys,
I will share with you how to install Viper4Android FX 2.7 without any hassle here.
Tested on Xiaomi Mi 9T Pro (raphael) on Custom ROM Evolution X A12.
Theoretically it should works also for Android 10 and 11.
Follow instruction below :
1. Download the zip here : https://github.com/programminghoch10/ViPER4AndroidRepackaged/releases
2. Install it via Magisk, THEN reboot.
3. Go to Viper4Android, turn Master Limiter ON to apply any effects.
3. Enjoy!
(NOTE: Keep the Legacy Mode always ON in V4A Settings.)
If you face problem such as V4A not processing audio from streaming services such as Spotify, Youtube, etc,. you may flash Audio Compatibility Patch and Audio Modification Library. Instruction as follow :
PLEASE make a backup of your data in case something goes wrong during the process.
1. Uninstall Viper4Android by flashing the .zip again via TWRP or remove it via Magisk and reboot.
2. download both ACP and AML :
- ACP https://john-fawkes.com/Downloads/acp.zip
- AML https://zackptg5.com/downloads/Audio-Modification-Library_v4.2.zip
3. Install both zip via Magisk in following order :
- AML , once complete do not reboot immediately, go back and install ACP instead.
- ACP ( during ACP installation PLEASE PAY ATTENTION, it will run a setup wizard and you need to respond all of the options appeared using volume key + and - , otherwise the setup will fail and ACP is not installed.
If you somehow missed the wizard step you can just flash the ACP again and retry try again.
If you are unsure which one is the suitable one for you, you can refer to my reference below )
Code:
Patch audio_policy ? | Yes
- Select Patch Method : | Vol Up - Patch (new logic)
Remove notification_helper ? | Yes
- Select Fix Method : | Vol Up : Remove notification_helper effect
Patch USB policy for dacs ? | No
Use Lib workaround ? | No
4. After you flashed the zips, you need to REBOOT to RECOVERY and CLEAR DALVIK CACHE.
5. Then reboot to System.
6. Install V4A via Magisk and then reboot again.
7. Go to Viper4Android, turn Master Limiter ON to apply any effects.
8. Keep the Legacy Mode always ON in V4A Settings.
In case your phone stuck in reboot process, you can force reboot to Recovery by press holding Power Button and Volume +, then clear dalvik cache again. If its not working then you can uninstall the Magisk by flashing Magisk Uninstaller via TWRP.
Big thanks to @programminghoch10 for making the zip really easy to install.
Source :
https://github.com/programminghoch10/ViPER4AndroidRepackaged
Credits :
@programminghoch10
@pittvandewitt
It can't work on Redmi K50 Pro. QAQ
hey mark,
it works for me (Galaxy A52 4G, LOS 19.1) only with RadioDroid with legacy mode off. if i play music with any other player (vlc, ezfolderplayer) i have to switch the legacy mode on, viper is activated but not processing.
any suggestions?
Peter_Petersen said:
hey mark,
it works for me (Galaxy A52 4G, LOS 19.1) only with RadioDroid with legacy mode off. if i play music with any other player (vlc, ezfolderplayer) i have to switch the legacy mode on, viper is activated but not processing.
any suggestions?
Click to expand...
Click to collapse
Yeah if thr V4A not processing you may install ACP and AML from Magisk, then clear the cache in TWRP (I would suggest to backup your data first just in case). I will share the instruction later this day, currently I'm not in front of my PC.
O2C14 said:
It can't work on Redmi K50 Pro. QAQ
Click to expand...
Click to collapse
Can you elaborate the problem ? is it not processing or it fail during the installation ?
Peter_Petersen said:
hey mark,
it works for me (Galaxy A52 4G, LOS 19.1) only with RadioDroid with legacy mode off. if i play music with any other player (vlc, ezfolderplayer) i have to switch the legacy mode on, viper is activated but not processing.
any suggestions?
Click to expand...
Click to collapse
I have updated the guide, please do check it out and let me know if its working on your end.
mark.dx said:
I have updated the guide, please do check it out and let me know if its working on your end.
Click to expand...
Click to collapse
Unfortunally, the same as before. I've done exactly the steps you describe in your (new) guide. AML, ACP, V4A, Wipe Delvik.
NEON: Enabled
Active: YES
Processing: NO
Only RadioDroid is working with disabled legacy mode.
I will do a clean install oft LOS (wipe all) and try it again.
Thanks for your efforts...
WBR
Peter_Petersen said:
Unfortunally, the same as before. I've done exactly the steps you describe in your (new) guide. AML, ACP, V4A, Wipe Delvik.
NEON: Enabled
Active: YES
Processing: NO
Only RadioDroid is working with disabled legacy mode.
I will do a clean install oft LOS (wipe all) and try it again.
Thanks for your efforts...
WBR
Click to expand...
Click to collapse
Hi Peter,
Sorry for your trouble, maybe you can try this method instead that I make for Android 11 here : https://forum.xda-developers.com/t/guide-viper4android-fx-for-android-11-based-custom-rom.4288611/
If it still fails, I would like to recommend to you Wavelet instead : https://forum.xda-developers.com/t/app-9-0-wavelet-headphone-specific-equalization.4097957/ its much simpler but very effective it even works non rooted and it have AutoEq with so many presets for various headphone and IEMs, worth to try.
For me this was enough for it to work perfectly not only in android 12L but in A11, 10 etc it works perfect
Link post: https://forum.xda-developers.com/t/...stortion-bluetooth-audio-issue.4012249/page-2
If it doesn't work try to copy the file in the following path data/adb/modules/viper and then activate the legacy mode and finally restart the phone should be working
(Sorry for my English)
Hey together,
i finally got Viper to work with all my audio apps.
LOS 19.1, Galaxy A52/4G, Magisk 24.1
My steps:
- remove AudioFX via Magisk Module AOSPsoundfxRemover-MagiskModule.zip
- install AML and ACP (mark.dx guide)
- reboot to recovery and clear dalvik cache
- reboot
- set selinux temporary to permissive
- install Viper4Android
- reboot
- enable Legacy Mode in Viper
done...
now, it's only necessary to install ViPER4AndroidFX-repackagedhoch25 and everything works fine on my Galaxy A52 4G 128 GB. Magisk 25.2.
@mark.dx , i gave wavelet a try, good app but the setting 'subwoofer' under 'bass' in Viper is indispensable for me. ;-)
WBR
Peter_Petersen said:
Hey together,
i finally got Viper to work with all my audio apps.
LOS 19.1, Galaxy A52/4G, Magisk 24.1
My steps:
- remove AudioFX via Magisk Module AOSPsoundfxRemover-MagiskModule.zip
- install AML and ACP (mark.dx guide)
- reboot to recovery and clear dalvik cache
- reboot
- set selinux temporary to permissive
- install Viper4Android
- reboot
- enable Legacy Mode in Viper
done...
@mark.dx , i gave wavelet a try, good app but the setting 'subwoofer' under 'bass' in Viper is indispensable for me. ;-)
WBR
Click to expand...
Click to collapse
glad that it finally worked for you. What's nice about Wavelet is the AutoEq feature is replacing convolver and DDC profile in V4A and they already providing tons of config for various headphones and IEMs.
I tried with oneplus 9 but didn't work, i dont know what else to do. I have selinux on permissive
The driver installation keeps looping on my redmi k50 pro. I tried all methods from the internet. Can anyone help pls?
Untzo said:
I tried with oneplus 9 but didn't work, i dont know what else to do. I have selinux on permissive
Click to expand...
Click to collapse
do you have AudioFX installed ? see previous post for reference
have you try to remove the V4A and use my guide ?
thinhdinh25 said:
The driver installation keeps looping on my redmi k50 pro. I tried all methods from the internet. Can anyone help pls?
Click to expand...
Click to collapse
mark.dx said:
have you try to remove the V4A and use my guide ?
Click to expand...
Click to collapse
of course. I think dolby atmost caused that problem
So I have a note 20 ultra and I have tried everything for the last few days to get Viper installed ad running
It just refuses to process (closest I've gotten to it working.) I'm now at a loss on what to do. Any suggestions?
dtk0kai said:
So I have a note 20 ultra and I have tried everything for the last few days to get Viper installed ad running
It just refuses to process (closest I've gotten to it working.) I'm now at a loss on what to do. Any suggestions?
Click to expand...
Click to collapse
turn off / disable any built in equalizer or other audio processing that come with the phone.
Dolby Atoms (stock A12 ROM) is switched off.
Still cannot get v4A drivers to install.
Auto reboots phone after trying to install v4a drivers - when I open v4a app, same problem repeats.
I've tried a 101 different ways based on XDA guides/ various different forums. Nothing has helped.
I've got s22 ultra snapdragon variant; on stock SamsungA12; rooted with TWRP & flashed multidisabler etc.
I think the v4a driver installation process is not happening successfully...... Need help please.
Have i done something wrong? Where can i get all the other features or have they been removed