V4A on Android P DP1? - Google Pixel Questions & Answers

Has anyone tried it out since we have root now? I'll try it myself if no one replies but just wanted to see if anyone tried. I'm running Arise Sound System on 8.1 and wanted to see if I could pull it off on P.
Edit: Ended up installing the developer preview and Viper. All of it works very well. Installed Arise Magnum Opus through TWRP and the magisk universal deep buffer remover and it works just as well as Oreo did for me, although I was told Dolby does not work with P.

Related

CyanogenOS 13 and V4A

Hello peeps! A longtime lurker, first time poster here.
Straight to the point. I upgraded my rooted OPO with the COS 13 ZNH0EAS2JK by Manudroid19. My kernel is the boeffla one for COS13. The user experience is smooth as all hell but i encountered a huge problem. I can't get Viper4Android to work at all, hell, even the built-in AudioFX didnt do anything. The apk works fine and it installs the driver without any problems. I've tried the phone speakers and a headset but any of the options in V4A don't do anything.
Has anyone got V4A to work on COS 13? Or even AudioFX? I've tried flashing V4A and tried the Play store version without any luck. What am i missing? Didn't have any problems with V4A on 12.1. Any ideas?
Thanks in advance!

Root OpenKirin Resurrection Remix 6.2.0

So I am running beta 3 of Ressurection Remix from OpenKirin website. Everything is smooth even after heavy tweaks. But I want to root this ROM. Reason is I want to uninstall built-in apps and some of my apps require root access. I already tried rooting the ramdisk.img. it failed. Even though it was rooted root access wasn't available. So can I directly flash latest magisk via elemental ROM TWRP? Or is there any other method?
Like you, I'm on the same build from yesterday, and obviously the minimum that I'd like to do is to root the ROM, since that we already miss a fully working TWRP and a compatible Xposed framework.
I discovered just yesterday topjohnwu's thread about patching the stock boot.img with the custom Magisk Manager apk for Huawei devices, but before doing everything I've decided to make a search on XDA, and I've stumbled upon this. So neither patching the stock ramdisk.img works?? Dammit. Becsuse standing by what i know, flashing latest Magisk on an A only GSI works, but i haven't read successful cases rooting an OpenKirin ROM yet.
I'd like to test this method, but i still have to setup some stuff on this ROM, and so i don't want to try something that could mess up system, trashing all the time that I've spent on configuring the device.
I'll update ya as soon as i can, if something useful should come out. I hope to update you soon!
Dude. I have done it and would like to tell you that it can be flashed normally. Currently enjoying root with all modules working. If you have an honor 6x just flash TWRP from elemental room thread and then latest magisk. So far no issues, no bootloop. However after first installation I recommend you to install via direct patch once again to ensure everything works. i.eif you still wanna know. This is way simpler
Thanks for letting me know mate, yeah i have a 6X. Actually I've installed TWRP and flashed latest stable Magisk, V17.1. Magisk is correctly detected by Magisk Manager.
Now, the file that i should provide to patch on Magisk Manager is stock EMUI 8.0 boot.img, correct?
Nope. If you have magisk installed just direct install once again via magisk manager and you're good to go
Thanks Mannan, I'm enjoying root goodies too now.
I take the chance to ask ya if sound mods like Viper/Dolby Atmos will also work or not as a Magisk module, since that time ago (but even recently) i saw some users that was saying in a couple of threads that flashing one of these would corrupt system files, and so EMUI 8 had to be flashed again.
First of all we aren't on EMUI 8bso no corruption. We are on Android 8.1 so any Sound Mod for this Firmware should work. Now I haven't flashed it yet cause mainly I have to find a working one and of the risk of soft brick. But I will try and let you know if I find a working one. Same goes for exposed framework
Got it. Well it would be great, especially Xposed in systemless version.
EDIT - going off topic a while, even you notice a charging time much slower than on stock? Before, i usually charged something like 60-65% in one hour, now it tooks at least 1 hour and an half to achieve the same percentage of battery. Gotta tweak this someway.
Tried installing Viper4android. Gives IO error while mounting driver. Xposed I havent tried
Mannan Qamar said:
Tried installing Viper4android. Gives IO error while mounting driver. Xposed I havent tried
Click to expand...
Click to collapse
Thanks for the feedback. Sadly i think that Xposed won't work too.

has anyone got viper4android working through magisk??

Hi,
I have taken a step forward to unlock and root my device (7days wait time ahead)..only for viper4android and dolby effects.
I have seen some folk saying that they got bootloop after installing viper4android through magisk. Has anybody out there got succeed in installing viper4android and dolby atmos through magisk???
Please share your experience and steps to follow. If it doesnt work, then i wont unlock my device:angel:. Please reply as soon as possible. Thanks.
Dolby not working fine. If you want you can try from here :
https://forum.xda-developers.com/an...lby-digital-plus-arise-20181115-t3868192/amp/
If it gives 'remote service has stopped' error, one user said that flashing viper from android solved it.
Now, as for viper, i am on eu rom miui 12 beta 20.4.30, the viper i downloaded from magisk app seems to be working okay.
You may try.
If any error occurs you may delete the module from data/adb/modules through the twrp.
sssaini007 said:
Dolby not working fine. If you want you can try from here :
https://forum.xda-developers.com/an...lby-digital-plus-arise-20181115-t3868192/amp/
If it gives 'remote service has stopped' error, one user said that flashing viper from android solved it.
Now, as for viper, i am on eu rom miui 12 beta 20.4.30, the viper i downloaded from magisk app seems to be working okay.
You may try.
If any error occurs you may delete the module from data/adb/modules through the twrp.
Click to expand...
Click to collapse
Got viper working good but dolby for android 10 is very buggy, so i gave up on dolby.
Finally,
My audio system has:
1. Viper4android
2. Dolby working, it closes when you change some switch, but still effect will work, just open again.
3. Anir Sauron MK III audio Mod - Magisk.
4. ICESound Magisk Mod
5. DTS X Ultra
vivek12341 said:
Hi,
I have taken a step forward to unlock and root my device (7days wait time ahead)..only for viper4android and dolby effects.
I have seen some folk saying that they got bootloop after installing viper4android through magisk. Has anybody out there got succeed in installing viper4android and dolby atmos through magisk???
Please share your experience and steps to follow. If it doesnt work, then i wont unlock my device:angel:. Please reply as soon as possible. Thanks.
Click to expand...
Click to collapse
I was trying that, i am on miui 12 indian rom and trying to do unlocking bootloader. after 7 days i was try again and the mi tool say 168.
i just want magisk on miui 12 indian rom and glad to having viper4android too
will you please guide me to unlock the bootloader? and it also delightful if you send the link of twrp and magisk for it, and thanks for those magisk modules, I'll definitely try if I will success to root.
vivek12341 said:
Finally,
My audio system has:
1. Viper4android
2. Dolby working, it closes when you change some switch, but still effect will work, just open again.
3. Anir Narsil audio Mod - Magisk.
4. Installed XtremeMusic Magisk Module which comes with an app that can enhance audio to Top quality 32bit 384khz and heavy clarity.
Click to expand...
Click to collapse
The 4th module sound like bull****. Our device can only output up to 24bit/192khz, there's no way it can output 32bit/384khz through software.
Never_Sm1le said:
The 4th module sound like bull****. Our device can only output up to 24bit/192khz, there's no way it can output 32bit/384khz through software.
Click to expand...
Click to collapse
Yes its bull****...and i have changed my current mod list. Have a look.
Never_Sm1le said:
The 4th module sound like bull****. Our device can only output up to 24bit/192khz, there's no way it can output 32bit/384khz through software.
Click to expand...
Click to collapse
Sauron still works on Android 10? I thought it only work on 9? Or are you confused with Narsil?
Ifi you want to use Dolby first you have to make your system permissive.
vivek12341 said:
Hi,
I have taken a step forward to unlock and root my device (7days wait time ahead)..only for viper4android and dolby effects.
I have seen some folk saying that they got bootloop after installing viper4android through magisk. Has anybody out there got succeed in installing viper4android and dolby atmos through magisk???
Please share your experience and steps to follow. If it doesnt work, then i wont unlock my device:angel:. Please reply as soon as possible. Thanks.
Click to expand...
Click to collapse
Hey bruh yeah i did please follow the steps
1)Download viper 2.7.1.6
2)Flash through magisk don't reboot ...not yet
3)Open V4A app let it install drivers and after that it will reboot.
4)Flash ACP if you have any crackling sound
vivek12341 said:
Got viper working good but dolby for android 10 is very buggy, so i gave up on dolby.
Click to expand...
Click to collapse
Please share how you do this

working Dolby Atmos oos 10 with gcam

I've been experimenting with different magisk mods on oxygen os 10 beta and found a complete working Dolby Atmos port that also doesn't crash gcam with dotfix like it used too on pie.
Here's the link for the Dolby Atmos magisk module
https://forum.xda-developers.com/showpost.php?p=81683221&postcount=4342
All I had to do to make it work was install a custom kernel and everything worked with no faults or crashes.
My choice of kernal was the latest blusparks kernel but should work with all the popular ones
Update:
I did some testing and can confirm the latest module through the thread posted works...
https://forum.xda-developers.com/android/software/app-dolby-atmos-axon-7-oreo-port-t3740508/page473
Use the Google drive link provided in comments on that page and download Dolby rc4 because rc5 is faulty and will be taken down.
Also download the acdb module in that Google drive link and install that too.
This now makes it work without clashing with OnePlus audio FX aswell as keeping the device certificate as OnePlus instead of Sony like it was with the last module posted. All still works with gcam and dotfix.
For reference my device is on oos10 stable and has blusparks custom kernel and selinux is set to permissive as some people mention it makes Dolby crash with enforcing.
I flashed this "blu_spark_r198-oos_op5-op5t_8ba46c0b8.zip" Kernel on OOS10 Beta 2 but not boot the device
You will have to flash stock kernel to recover from that if not reflash the ROM over your existing install should be fine... That isn't a problem with the Dolby module and to be fair doesn't happen to anyone on the blusparks forum page so something with that install definitely went wrong I would post a logcat of sorts on their page and see if the answer can be found there. Like mentioned you can use any supported custom kernel for your ROM if you can't get blusparks working which I am very sure is some error in the install process as that's not normal than you could use new kernel or lazy kernel to name a few.
I can't explain better without knowing your exact process you took but can guarantee that is not the normal outcome for installing this or any kernel for boot loop something you have done or the zips install process has made an error sorry
Like I said for support on the kernel check with the developer on his page sorry you had this problem
Are you flashing Magisk Canary or Magisk Stable? Magisk Canary builds after Magisk Stable 20.4 currently cause bootloop but will likely be fixed in a later Magisk release (no ETA).
That was on the first and last page of the blusparks kernel thread which I would recommend quickly reading through any mods thread before installing it to know if you can use it or if you will gain problems.
Not sure if this applies to you but that's the only mention of bootloops in the last year or so on that thread. Hopefully this might help you
You just have to set selinux to permissive.
The app is not turning on
dDranzer said:
The app is not turning on
Click to expand...
Click to collapse
it's the same with me
Other than making sure ityou are using selinux set as permissive and having a custom kernel there isn't anything that can go wrong but I ain't doubting it ain't working for you.
Try my setup which is using blusparks kernal other than installing that I have done nothing else so if not working there must be another module or something that's stopping this from happening. Even though what your explaining usually points to your selinux being enforcing as that's what every Dolby has done for years it either opens but won't power on or it crashes and closes as opening.
I can confirm I personally have 3 OnePlus 5t devices in my house that all have this working under the latest stable oxygen os 10 with the latest gcam and dotfix installed and only had to install bluspark to make dolby open up.
By the way for anyone using this module the only one I know supported is the zip in the link posted. Not the rest of the modules from that thread, atleast none I've tried so if you want it to work don't try searching for newer versions through that thread.
If you do find a more updated version or a fix for the ones posted newer than this module please inform us all through this thread.
Thank you so much ahh! I love this compare to a viper in my opinion.

Viper working?

rooted With Magisk. Installed viper and can’t get it to enable. Has anyone got it working on this phone?
soundneedle said:
rooted With Magisk. Installed viper and can’t get it to enable. Has anyone got it working on this phone?
Click to expand...
Click to collapse
I followed the steps here and it is working fine.
mbk17 said:
I followed the steps here and it is working fine.
Click to expand...
Click to collapse
Wow. Thank you so much. Easiest thing I've ever had to do. Just flash the viper mod on that YT page. Really makes my AirPods Max come to life.
soundneedle said:
Wow. Thank you so much. Easiest thing I've ever had to do. Just flash the viper mod on that YT page. Really makes my AirPods Max come to life.
Click to expand...
Click to collapse
I was surprised how easy it was as well. It is certainly one of the best reasons to root.
Can someone share the file with me? The Youtube link with viper is not working anymore so I was unable to get the zip. I need viper in my life. Please .
@kirschdog1 I was able to make Viper work with the following steps.
Install Viper from Magisk Repo.Reboot and open app to install drivers.
Install busybox Magisk module and reboot.
Install Audio Modification Library module and reboot.
I don't know why but installing all three at the same time didn't seem to work for me.
I am running a Pixel 4a with dec security patch, rooted with magisk beta. I used the zip linked in the following post.
I also set it from SELinux permissive to enforcing, by disabling a boot script in the magisk module.
[APP][ALL ROOT SOLUTIONS][6.0+]ViPER4Android FX 2.7
ViPER4Android FX By pittvandewitt and MrWhite214 Introduction Many users are enhancing their smartphone audio experience with the popular ViPER4Android software, but some of us have a hard time installing the driver or they don't like the look...
forum.xda-developers.com
kirschdog1 said:
Can someone share the file with me? The Youtube link with viper is not working anymore so I was unable to get the zip. I need viper in my life. Please .
Click to expand...
Click to collapse
There you go
Has anyone been able to use viper on android 11 other than using magisk version 21, and using an updated viper version
soundneedle said:
rooted With Magisk. Installed viper and can’t get it to enable. Has anyone got it working on this phone?
Click to expand...
Click to collapse
Viper seems so, now I still need to know about connection recording ... Then I use this ROM
I am on latest Magisk Canary and Viper works fine for me by following this guide.
I tried everything with magisk version and the other puhlic versions around with about every thread I found. The mentioned above I also tried. But it only worked when I switch selinux to permissive. With magisk canary 22 104
Im on most actual mai update

Categories

Resources