Viper4Android on Nexus 9 - Nexus 9 Android Development

I've searched all forums for a solution to make Viper4Android work on Nexus 9.
None has been working for me without killing Chromecast support.
So I've made two solutions to make it work:
TWRP, Root and Busybox is required!
As system app:
In TWRP install V4A_2.3.3.0_[Quality].zip
Boot Android and open V4A
(Uninstall and) Install driver
Reboot Android
As normal app:
In TWRP install V4A_Conf.zip
Boot Android
Install SELinuxModeChanger and set it for "Permissive" mode
Install V4A
Open V4A and install driver
Reboot Android
I've testet with Google Music and Wimp.
PLEASE hit thanks if this helps you!

If you're on another Lollipop device the tricky part in making the V4A driver stick, is to manually edit the audio_effects.conf on the "Vendor" partition. V4A only writes to the system audio_effects.conf.

trackloading said:
I've searched all forums for a solution to make Viper4Android work on Nexus 9.
None has been working for me without killing Chromecast support.
So I've made two solutions to make it work:
TWRP, Root and Busybox is required!
As system app:
In TWRP install V4A_2.3.3.0_[Quality].zip
Boot Android and open V4A
(Uninstall and) Install driver
Reboot Android
As normal app:
In TWRP install V4A_Conf.zip
Boot Android
Install SELinuxModeChanger and set it for "Permissive" mode
Install V4A
Open V4A and install driver
Reboot Android
I've testet with Google Music and Wimp.
PLEASE hit thanks if this helps you!
Click to expand...
Click to collapse
sweet i was looking in the viper4android main thread..i saw ur post. with link.. now i could install viper on my N9..
one question... its better if i flash into system app correct??

Lw00d said:
sweet i was looking in the viper4android main thread..i saw ur post. with link.. now i could install viper on my N9..
one question... its better if i flash into system app correct??
Click to expand...
Click to collapse
That's the one I'm using, so I don't have to be in permissive mode...

I'm getting " unfortunately V4a has stopped" after flashing super quality on Lollipopalooza Rom. any suggestions?

dom2684 said:
I'm getting " unfortunately V4a has stopped" after flashing super quality on Lollipopalooza Rom. any suggestions?
Click to expand...
Click to collapse
I got a similar response with the pure AOSP build, but not with these zips. I used the zips mentioned in the Q&A V4A thread. I think this only works with stock?

igothacked1 said:
I got a similar response with the pure AOSP build, but not with these zips. I used the zips mentioned in the Q&A V4A thread. I think this only works with stock?
Click to expand...
Click to collapse
Ahh gotcha thanks

this work great for me..
what are some preferred settings??

I got around to flashing the Super Quality zip and the V4A_conf.zip on the pure AOSP build. NuPlayer in Dev options is disabled and I'm running SELinux in permissive mode. I still can't get the driver to stick.

igothacked1 said:
I got around to flashing the Super Quality zip and the V4A_conf.zip on the pure AOSP build. NuPlayer in Dev options is disabled and I'm running SELinux in permissive mode. I still can't get the driver to stick.
Click to expand...
Click to collapse
I had to edit the audio_effects.conf file in the Vendor folder to get the driver to stick. Add the lines in Step 6 of the following link: http://www.hacktabs.com/how-to-impr...ity-with-viper4android-audio-drivers-effects/
Leave out the lines for xhifi and look at the screenshot for the location in the file to add the lines.
After you do this, try to add the driver again, then restart.

cor_mann said:
I had to edit the audio_effects.conf file in the Vendor folder to get the driver to stick. Add the lines in Step 6 of the following link: http://www.hacktabs.com/how-to-impr...ity-with-viper4android-audio-drivers-effects/
Leave out the lines for xhifi and look at the screenshot for the location in the file to add the lines.
After you do this, try to add the driver again, then restart.
Click to expand...
Click to collapse
I reverted to a backup before I flashed the Super Quality zip.
Which vendor folder? The /system/vendor/ folder that the driver creates or the /vendor/ folder in root? And the .conf file in /system/vendor/ already contains those lines. Even then, the driver won't stick.
If this provides more information, I'm using Dilligaf's kernel. But I'm positive that wouldn't affect the driver installation.
EDIT: Got it. I copied the audio_effects.conf in the /system/vendor/ folder and replaced the one in the /vendor/ folder. Driver sticks now

igothacked1 said:
I reverted to a backup before I flashed the Super Quality zip.
Which vendor folder? The /system/vendor/ folder that the driver creates or the /vendor/ folder in root? And the .conf file in /system/vendor/ already contains those lines. Even then, the driver won't stick.
If this provides more information, I'm using Dilligaf's kernel. But I'm positive that wouldn't affect the driver installation.
EDIT: Got it. I copied the audio_effects.conf in the /system/vendor/ folder and replaced the one in the /vendor/ folder. Driver sticks now
Click to expand...
Click to collapse
Good to hear. I'm not sure why some people have to add the lines and others don't.

Hmmm... The /system/vendor folder is just a shortcut to the /vendor/ folder on my device, so it should be the same...?
I'm on pure stock and as I see the posts, the ones having problems is on other roms or kernels.

trackloading said:
Hmmm... The /system/vendor folder is just a shortcut to the /vendor/ folder on my device, so it should be the same...?
I'm on pure stock and as I see the posts, the ones having problems is on other roms or kernels.
Click to expand...
Click to collapse
You're right: I'm running Lollipopalooza ROM. That explains it.

Has anyone got convolver to work? The app sees all my irs files in the kernel folder, just has zero effect. Everything else works for me.
Swift keyed from my N9

mrshades812 said:
Has anyone got convolver to work? The app sees all my irs files in the kernel folder, just has zero effect. Everything else works for me.
Swift keyed from my N9
Click to expand...
Click to collapse
I haven't gotten mine to work either. I just noticed it. However, my Oneplus One has IRS working on 5.0.1. It could be how the driver is behaving?

trackloading said:
Hmmm... The /system/vendor folder is just a shortcut to the /vendor/ folder on my device, so it should be the same...?
I'm on pure stock and as I see the posts, the ones having problems is on other roms or kernels.
Click to expand...
Click to collapse
Igothacked said he was using my kernel/ramdisk, I'm not sure what ROM, but the kernel in my boot.img is completely stock, the only edits were to the ramdisk, and I'm positive that would not effect anything with this. I'm not sure about what Roms were being used, I guess it could make a difference, maybe permissions are slightly different or there is a difference with some symlinks with different roms and stock.

Thanks, also working on stock Acer A1-810 too.

I'm also running theLollipopalooza ROM and had to edit the file manually before the driver would install. All seems to be working fine now though. Thanks☺

Nevermind I re-read

Related

Album removed as default picture launcher

I removed Album as the default picture launcher like done by venkat kamesh (link to original thread is at the end) for other Xperia models following his nice tutorial , after installing you can choose which app will be used for opening your pictures out of the camera.
Updated 27/03/16
Instructions for MM (use the attached file SemcCameraUI-generic-xhdpi-release.apk)
device needs to be rooted
make a backup of your original "/system/priv-app/SemcCameraUI-generic-xhdpi-release/" folder so you can restore the original behaviour if needed.
copy my SemcCameraUI-generic-xhdpi-release.apk to "/system/priv-app/SemcCameraUI-generic-xhdpi-release/" folder to override the original file
change the permissions of SemcCameraUI.apk to the ones the original app has (rw-r--r--):
Code:
chmod 644 SemcCameraUI-generic-xhdpi-release.apk
delete oat folder
reboot - enjoy!
Instructions for LP (use the attached file SemcCameraUI.apk)
device needs to be rooted
make a backup of your original "/system/priv-app/SemcCameraUI" folder so you can restore the original behaviour if needed.
copy my SemcCameraUI.apk to "/system/priv-app/SemcCameraUI/" folder to override the original file
change the permissions of SemcCameraUI.apk to the ones the original app has (rw-r--r--):
Code:
chmod 644 SemcCameraUI.apk
reboot - enjoy!
Big thanks to venkat kamesh!!!
Original threads
http://forum.xda-developers.com/crossdevice-dev/sony-themes-apps/mod-camera-album-default-app-t3139667
http://forum.xda-developers.com/crossdevice-dev/sony-themes-apps/tut-how-to-remove-album-default-xperia-t3219268
will it work with marshmallow?
No, this version is only working for Lollipop.
I will make a MM version in the following days and post it here.
I'm.using this xposed module to accomplish the same thing.
http://forum.xda-developers.com/xposed/modules/mod-xperia-camera-enhancements-t3260643
I managed to modify the apk, unfortunately it doesn't start any longer, no idea why ... Any hints what could go wrong after recompiling the apk with apktool and cause the app to crash? I did it the same way as with LP ...
civicsr2cool said:
I'm.using this xposed module to accomplish the same thing.
http://forum.xda-developers.com/xposed/modules/mod-xperia-camera-enhancements-t3260643
Click to expand...
Click to collapse
This doesn't work on my MM system, I guess its only for LP ...
Thorstenk said:
This doesn't work on my MM system, I guess its only for LP ...
Click to expand...
Click to collapse
Yeah, I haven't made the jump to mm for a lot of reasons, xposed modules being a big one
Should work by now with MM, see first post for instructions!
Happy Easter
didn't work on mm (32.1.A.A.163), didn't appear in drawer and oat folder didn't recreate himself after reboot, permissions are correctly set, even wiped cache and dalvik/art cache through recovery. is there a problem with the apk ? could you post md5 of SemcCameraUI-generic-xhdpi-release.apk plz
sheraro said:
didn't work on mm (32.1.A.A.163), didn't appear in drawer and oat folder didn't recreate himself after reboot, permissions are correctly set, even wiped cache and dalvik/art cache through recovery. is there a problem with the apk ? could you post md5 of SemcCameraUI-generic-xhdpi-release.apk plz
Click to expand...
Click to collapse
On my device it works without having the oat-folder and as far as I know the oat-folder won't be created again, because the apk is deodexed ...
I just downloaded my file again and did the whole process again and it still works .
Did you do it (copy the file and set the permissions) via adb?
Could you try it again?
md5 is: 43774a75b358b255ca629c0bfd56e289
md5 is correct, I set permissions with total commander, I did it with root explorer too, the permissions are correctly set (rw-,r--,r--) but camera app is nowhere to be found ... I will try with adb and see
The camera is missing after I did this.
Tried it on Marshmallow, can you help bro?
Followed the instructions carefully. Thank you
Tried via adb, doesn't work as well.
Upon checking the file SemcCameraUI-generic-xhdpi-release.apk its still my default apk and not the one i pushed with adb (the one i downloaded here), the oat folder was still there as well. Pretty sure I deleted it via adb as well and no error showed up.
Update: Tried it again via adb, this time SemcCameraUI-generic-xhdpi-release.apk pushed properly with correct permissions and oat folder deleted as well. But the camera is now missing again. Any ideas? Thank you
I had somehow similar problems that I can't explain ... just copy back your original files including the oat folder and check if its working again (it should) and afterwards try it again. For me it works ...
Thorstenk said:
I had somehow similar problems that I can't explain ... just copy back your original files including the oat folder and check if its working again (it should) and afterwards try it again. For me it works ...
Click to expand...
Click to collapse
Thanks but tried it like 3 times already, no luck still.
Not working for me either on 6.0.1 -.-
Seems like .apk is broken or something (when opening .apk get parsing error )
and when replacing original .apk Camera disappears like the other ones said
Thorstenk said:
I had somehow similar problems that I can't explain ... just copy back your original files including the oat folder and check if its working again (it should) and afterwards try it again. For me it works ...
Click to expand...
Click to collapse
Hello, what about using Xposed to create a module like the one working for Lollipop?
it would be a lot easier for people instead of replacing files, messing with odex files and It could probably support all the MM releases. If i have some time i could try to do it, but i'm not as skilled as you.
Apart from that, thank you a lot for the work! I've been searching this since ever.
modified camera for MM 6.0.1
Herewith modified camera file from 32.2.A.0.224
For me it works like a charm.
Enjoy!!
bruno.trudo said:
Herewith modified camera file from 32.2.A.0.224
For me it works like a charm.
Enjoy!!
Click to expand...
Click to collapse
can you make a new one with .253 plz ?
Sure, I can. Please send me appropriate SemcCameraUI-generic-xhdpi-release.apk file.
I am still on .224
Thanks! Here it is : https://drive.google.com/file/d/0B9nyD39hGfrkTWxOczkwdXZZcnc/view?usp=drivesdk

Can't get Viper4Android working on my M8 running GPE 6.0 ROM

I'm struggling with installing Viper4Android on my device.
I tried installing using either the apk from the original thread (http://forum.xda-developers.com/showthread.php?t=2191223). It install successfully but I keep getting a driver install prompt, after installing the driver and rebooting.
Things I already tried without success:
- Installed BusyBox with BusyBox app (https://play.google.com/store/apps/details?id=ru.meefik.busybox)
- Setting the SELinux mode to permissive using SELinuxModeChanger app (http://forum.xda-developers.com/showthread.php?t=2524485)
- Setting the SELinux mode to permissive using flashable permissive.zip
- Installing the apk from the Material design Viper4Android thread (http://forum.xda-developers.com/android/software/app-material-viper4android-2-3-4-0u-t3190352)
- Flashing the .zip from the same thread.
I'm currently running Android 6.0 GPE, flashable version (http://forum.xda-developers.com/showthread.php?t=2708589)
Root access is granted through SuperSU, so no problem on that matter I suppose.
2. With a File Manager(Solid Explorer Recommended) locate " /system/etc/htc_audio_effects.conf" and rename "htc_audio_effects.conf" to "htc_audio_effects.bak" (Renaming this file will make it inactive but while keeping it backed up just in case this doesn't work for you, however it appears this file is not needed as no negative effects occur, and this should fix V4A.)
3. Reboot Device.
And if this doesn't work I thin you should grant storage permission for V4A under settings. I hope I can help you!
Duccibreeezy said:
2. With a File Manager(Solid Explorer Recommended) locate " /system/etc/htc_audio_effects.conf" and rename "htc_audio_effects.conf" to "htc_audio_effects.bak" (Renaming this file will make it inactive but while keeping it backed up just in case this doesn't work for you, however it appears this file is not needed as no negative effects occur, and this should fix V4A.)
3. Reboot Device.
And if this doesn't work I thin you should grant storage permission for V4A under settings. I hope I can help you!
Click to expand...
Click to collapse
Thanks mate!! This worked for me.
Thanks for ur help

How to Enable Viper with Stock Rooted Android 7

Various links in Google world. Some worked. Others had issues. To keep this simple I am going to attach two files to use. This is based on the use of Magisk for rooting your setup. It does NOT work if you are only using SuperUser. The mods that stated how to do this with SU did NOT work for me, so I will not include anything with regards to that. Again, this is working for me with latest just posted Android 7 firmware for my SM-G925T and rooted with Magisk and TWRP recovery installed. Please don't ask if you are not rooted or no TWRP or whatever. They ARE required and Magisk is required too. Plus go to Playstore and make sure BusyBox is installed. I would also uninstall any prior versions of Viper prior to doing this. Or use Titanium BU to delete so as NOT to have competing files. After the above, take the attached file audio_effects.conf and replace the one located in your system\etc folder. The file is zipped simply to allow uploading. This is NOT installable from recovery. Simply unzip to use the conf file. Disregard the backup file in this zipped upload. The .bak is not needed. You will need an app like root explorer to do this. Make sure you set the file permissions the same as the app you are replacing. This is important. Permissions must be the correct same as the original file. Finally...take the attached v4afx_v1.4 zip and install from TWRP recovery. Reboot and should be good to go. If done correctly the left menu in viper that shows driver status will show everything processing, enabled, and working when Viper is ON and music is playing
Added webcam shot showing driver status. A screen shot would remove that window showing driver status.
Do you randomly lose root after this install?

Arise - Installation question (Solved - Thanks matt1313!)

Hopefully this is an easy one that'll soon fall to the bottom, but...
I can't find any installation instructions for Arise Audio unless it's being referred to as something else entirely and I'm just not grasping the lingo.
I have the November update, and I have Magisk and TWRP installed and working (I can reboot to recovery and flash - and I can install mods in Magisk).
Could someone please point me in the right direction for installing Arise?
Thanks in advance!
Edit - solved thanks to matt1313 - instructions added here in case anyone needs them so you don't have to scroll - be sure to thank matt1313's posts here, though.
Have TWRP and Magisk installed/working and SELinux in Permissive mode (I used the Snoke R11 permissive kernel)
Download file linked below the quote section.
Extract "arise_customize.prop" from the zip (within the zip this file is located using this path: /getting_started/your_system/)
Edit the prop file (I used NotePad++) and change the following lines - you'll be putting the "true" part in:
install.core=true
install.v4a_2.5.0.5=true
install.ddplus=true
install.v4a_profiles=true
Save and copy that file to the root of your phone's internal storage (sdcard).
Copy the zipfile to your phone's internal storage/sdcard.
Reboot phone into TWRP and install the zipfile.
Click to expand...
Click to collapse
Zipfile: https://androidfilehost.com/?fid=889964283620765959 (Hope this is ok to link)
Original Thread for A.R.I.S.E. Sound Systems™: https://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
Thanks again to matt1313.
Start from the beginning
https://forum.xda-developers.com/showthread.php?t=3379709
Sent from my Pixel 2 XL using Tapatalk
Thanks for pointing that out (I probably should have included that link in my OP...)
There is just so much there, it's hard to tell what is current and what might be out of date. I'm over 3000 pages in on that topic and I'll keep going. My hope was that someone who had done this recently on the 2XL had a step-by-step, or could point to someone elses quick guide. Figured I couldn't be the only one a little overwhelmed by the size of that topic - but I suppose I'll get through it eventually.
PhoenixPath said:
Thanks for pointing that out (I probably should have included that link in my OP...)
There is just so much there, it's hard to tell what is current and what might be out of date. I'm over 3000 pages in on that topic and I'll keep going. My hope was that someone who had done this recently on the 2XL had a step-by-step, or could point to someone elses quick guide. Figured I couldn't be the only one a little overwhelmed by the size of that topic - but I suppose I'll get through it eventually.
Click to expand...
Click to collapse
I'm using ARISE+Magnum+Opus+20171114+Stock+Edition.zip
Extract prop file out of zip. Add true to:
Core
Viper
DD+
Save it in root of sdcard.
Then disable musicfx
Reboot to twrp flash arise.
You need permissive kernel.
Sent from my Pixel 2 XL using Tapatalk
Awesome. (Installed snoke R11 already).
Already got the zip from here (just wasn't sure it would be the right one): https://androidfilehost.com/?fid=889964283620765959
So I should be good to go after a few edits.
The prop just stays on the root of the sdcard, right? it doesn't need to be moved anywhere?
Thanks so much.
Edit: Yep, that did it - Downloaded the file linked above, extracted the "arise_customize.prop" from it and set:
install.core=true
install.v4a_2.5.0.5=true
install.ddplus=true
install.v4a_profiles=true
Copied that file to the root of the SDScard, copied the zipfile to my flash folder on my sdcard, reboot to recovery and flashed it.
V4A and Dolby both verified installed and working.
I know I said it above and thanked your post, but...thanks again. Hope you're having a great Thanksgiving.
Forgot add true to profiles also
Audiophile sounds good to me.
Sent from my Pixel 2 XL using Tapatalk

[ROOT]Stock and Magisk patched boot images

Until TWRP is available for this device, root must be done by flashing patched boot image via fastboot. I'm still in the waiting period for the bootloader unlocking, but I prepared files in the meantime. Maybe someone will find them useful. Attached are stock boot and patched image with Magisk 21.1, EEA ROM version. Just unzip them and flash from fastboot.
Full version: V12.0.6.0.QJSEUXM_20201117
Edit: patched boot image reuploaded, the previous one didn't work (at least on my phone). This one has been tested and is working fine.
hello,
having the EEA version 12.0.6.0, as a boot patch can I immediately give the modded boot, in fastboot?
carabot said:
hello,
having the EEA version 12.0.6.0, as a boot patch can I immediately give the modded boot, in fastboot?
Click to expand...
Click to collapse
You can flash patched boot image directly, or just hotboot it (fastboot boot patched_image.img) and install Magisk from Magisk manager.
hello,
I did and at the moment everything is ok.
thanks
but there is a strange thing, Mixplorer, it does not change the permissions of the files, yet it has root permissions
I think the root is not perfect, I can't change the permissions of the files
carabot said:
I think the root is not perfect, I can't change the permissions of the files
Click to expand...
Click to collapse
Which files on which partition with what kind of permissions? RO partitions must be remounted as RW, but it's not always possible and using Magisk is usually a better and safer approach.
hello
let's talk about system partition files how can I remount as RO?
using Mixplorer, if I click comeback as RO, it tells me failed
carabot said:
hello
let's talk about system partition files how can I remount as RO?
using Mixplorer, if I click comeback as RO, it tells me failed
Click to expand...
Click to collapse
I keep my system partition RO so I can apply OTA updates, so I haven't tried it. You could try another app (for example Total commander), but you will be probably out of luck because of Android 10 limitation. Read more detailed explanation here https://android.stackexchange.com/q...m-partition-locked-to-read-only-in-android-10
I would suggest using Magisk module for system modifications.
hi
i tried other app manager like root explorer and es explorer, but the result is the same. i also installed magiskhideprops module, but my phone is not supported as fingerprint yet
What are you trying to achieve?
the terminal command to try to mount as RO would you know?
_mysiak_ said:
What are you trying to achieve?
Click to expand...
Click to collapse
full root to modify root files
carabot said:
full root to modify root files
Click to expand...
Click to collapse
I meant which files do you want to modify and why..
carabot said:
the terminal command to try to mount as RO would you know?
Click to expand...
Click to collapse
It's in the link above, along with explanation why it might be impossible to do.
I wanted to change the audio files regarding the volume, I wanted it a little higher
carabot said:
I wanted to change the audio files regarding the volume, I wanted it a little higher
Click to expand...
Click to collapse
Why don't you do it with a Magisk module? Once you install a module, you can edit it directly in /data/adb/modules folder.
i read android 10 problem, would you recommend me to mount with termux, installing vim?
_mysiak_ said:
Why don't you do it with a Magisk module? Once you install a module, you can edit it directly in /data/adb/modules folder.
Click to expand...
Click to collapse
i don't know about magisk modules that can affect volume controls
carabot said:
i don't know about magisk modules that can affect volume controls
Click to expand...
Click to collapse
If you know how to edit system mixer files, you should be able to build your own module (or adapt one of the existing ones). But of course it's up to you, I'm just offering a well known and working solution to your problem.
_mysiak_ said:
If you know how to edit system mixer files, you should be able to build your own module (or adapt one of the existing ones). But of course it's up to you, I'm just offering a well known and working solution to your problem.
Click to expand...
Click to collapse
unfortunately no, I edit the audio value of the system files, but I don't know how to build a module
Hello
the twrp for gauguin is online, to mount it i have to go back to the stock boot?

Categories

Resources