Hello,
I recently clean flashed stock 5.1.1 and installed Viper4Android but I cannot seem to get it to work system wide. It works fine through play music but it won't process for youtube, etc. I am using the latest Viper4Android version, latest busybox and SELinux is permissive. I moved the apk to /system/priv-app, rebooted, installed drivers, rebooted, then started setting it up. I don't know if this is a problem with the way I set it up or if it is simply because I am using a stock ROM. I have another device with Cyanogenmod and Viper4Android processes for everything. Any advice would be appreciated. Thanks.
I also installed Viper 2.3.3 over 5.1.1 but flashed it from recovery as it was suggested in one of the XDA posts. Also flashed build.prop and lib fixes that came with it. For some reason that flash cleared davlik cache, may that's the requirement for Viper. I think Viper is OK with YouTube but it's hard to say as sound is always different. Sometimes its low. Highly promoted Vevo videos sound loud.
Sent from my Nexus 7 using Tapatalk
I managed to get it working system wide shortly after posting. I first fully removed my existing V4A installation, by uninstalling the driver, deleting data and uninstalling the app through link2sd. I rebooted and then downloaded the viperlolli zip from the nexus 5 forums, extracted it, replaced the apk with the latest version, renamed the apk folder, re-zipped and flashed. I then installed the driver, rebooted, set it up, and it is processing system wide (Youtube, Spotify, Chrome Beta, Play Music, etc). I don't know what changes the author did in the zip, but it worked wonders.
Related
Hey i just got my Nexus 7 a couple days ago and successfully rooted it at 4.2.1 stock android.
Ive installed only a couple of apps and everything seems to be working. Then one day i decided
to try Beats Audio Installer Pro for Root v1.2. I installed it successfully. After loading my equalizer in
the stock google play, it loaded many equaliser bars than the stock 5 and then i tried changing them to test it. Nothing changed
even when i toggled it on or off. Then i decided to uninstall it. It reboots and loads normally.
Now when i clicked on my equalizer settign in the stock google play, it says: 'MusicFX has stopped'.
I tried factory reset and got nothing. At stock rooted, its still comes up with 'MusicFX has stopped'.
Even tried installing other equalisers on the market and they all stop working since im sure
the stock MusicFX process is needed for them to work. I have nothing else to try.
Help would be nice or i might return the device back to stock unrooted and check for warranty or something.
Thanks.
Obviously reinstalling stock will fix it. Because I am also having same problem but i don't wanna install stock again just for equilizer because my previous settings for musicfx seems to be working till now. If you get solution without installing stock again then plz do tell me. I am also waiting here eagerly.
Still no luck. MusicFX is still not working on my phone but but but I installed ROCKET MUSIC PLAYER, It comes with own equilizer and it's working fine whereas equilizers of other music apps are not working.
yvgamer94 said:
Hey i just got my Nexus 7 a couple days ago and successfully rooted it at 4.2.1 stock android.
Ive installed only a couple of apps and everything seems to be working. Then one day i decided
to try Beats Audio Installer Pro for Root v1.2. I installed it successfully. After loading my equalizer in
the stock google play, it loaded many equaliser bars than the stock 5 and then i tried changing them to test it. Nothing changed
even when i toggled it on or off. Then i decided to uninstall it. It reboots and loads normally.
Now when i clicked on my equalizer settign in the stock google play, it says: 'MusicFX has stopped'.
I tried factory reset and got nothing. At stock rooted, its still comes up with 'MusicFX has stopped'.
Even tried installing other equalisers on the market and they all stop working since im sure
the stock MusicFX process is needed for them to work. I have nothing else to try.
Help would be nice or i might return the device back to stock unrooted and check for warranty or something.
Thanks.
Click to expand...
Click to collapse
Using root browser you can copy audio configuration in other rooted nexus7 and paste in your your system/etc and also copy soundFX and paste in your system/ lib soundfx folder and change the permission to rw.r.r and reboot your device..but remember u need to delete all the files inserted by beats..you find it in your system/lib,system/etc,and system/bin.
sorry about the wait
I had totally forgot about this thread since i left my tablet for a long time.
How i fixed it was just returning it to the original rom. It was the new rom indeed and beats not being compatible with my nexus 7. It seems Beats trys to take over musix fx and stops it from working. I just tried other roms instead without beats and everything was fine. Seems beats doesn't work some some devices.
Anyway atm, my nexus 7 is dead and posted prior to this one.
Hey guys, I've currently on offical Cyanogenmod 13 nightly. The default AudioFX that came preloaded with the ROM sucks, so I tried a few audio mods that I found across XDA. Here are the ones that I tried:
A.R.I.S.E Sound System
http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
I installed the Deuteronomy Pack. The installation didn't gave me any errors. When I opened to Dolby Atmos app, it instanly crash. Viper4Andeoid gave me a message that the drivers are not installed. When I click to install, the app crashed. If even installed busybox and set SeLinux to permissive but it still won't work
XTREMEMusic
http://forum.xda-developers.com/android/software/mod-beatsaudio-e-xloud-installer-t3029951
The problem with this is the mod only works in music players, not in other apps like YouTube, Spotify, etc. After a while, the mod stopped working and I cannot hear any sound difference at all. I cannot get it back to start working.
Any help would be greatly appreciated
i have tried both and they work fine! v4a needs some time to install driver, when it askes just tap yes and don't touch anything until it says to reboot. and don't flash sound system on each other, only on untouched system. BTW i'm using divinebeats
Sorry, can't offer a solution but just thought I'd say that I have used both Leviticus and numbers version of arise and have had no problems with any cm13 or cm14 Roms. I always install it straight away with the ROM and Gapps (boot to twrp, flash: ROM > Gapps > arise). Never had to mess with SeLinux. Also, don't know if it could make any difference, but I only use open Gapps (pico) or banks dynamic Gapps
foomanjackel said:
Sorry, can't offer a solution but just thought I'd say that I have used both Leviticus and numbers version of arise and have had no problems with any cm13 or cm14 Roms. I always install it straight away with the ROM and Gapps (boot to twrp, flash: ROM > Gapps > arise). Never had to mess with SeLinux. Also, don't know if it could make any difference, but I only use open Gapps (pico) or banks dynamic Gapps
Click to expand...
Click to collapse
Try arise on dirty unicorns. For me, there is no difference, I even recorded it. Look at the attachment
I use only clean V4A from this guy http://forum.xda-developers.com/android/software/viperaudio-viperatmos-3-8-sq-driver-t3289075 and probably good old V4A 2.4.0.1 would be the same.
Works on latest CM13 nightly, permissive. Tried youtube just now, all good.
FPSUsername said:
Try arise on dirty unicorns. For me, there is no difference, I even recorded it. Look at the attachment
Click to expand...
Click to collapse
Sorry if it doesn't work for you. I am using it strictly for the boost in volume...it definitely does work for me!
One thing I did have to do is go to settings > apps, and enable storage permissions for both dolby Atmos and v4a.
I have a rooted LG Stylo 2 Plus (T-Mobile model). I recently encountered a problem where when I sideload some apks I get "App not installed. The package appears to be corrupt" and when downloading and then installing apps through the Google Play Store, I would get error 507. The apk work on other devices, and some apk will install, but there is other ones I need to install. I have tried clearing the cache of the package installer and Google play store and services. What should I do?
I have the exact same problem, same model (lgms550) running 7.0 (rooted, twrp and supersu, otherwise stock). Mine initially started when I installed xposed. When I flashed the uninstaller zip the package installer worked again (for a while...) Now every package throws "appears corrupt" and Playstore gives the 507 error. I've transferred the apps to my other phone (gs5) and they install fine so they're not bad downloads. Frankly I'm stumped and after hours of combing google for answers this is the first post that matches and oddly it's the same device. Maybe it's the ms550?
Fixed this by reflashing system from twrp.
First off, I feel it necessary to say WITHOUT THE CREW WORKING ON TWRP THERE WOULD HAVE BEEN DOZENS OF ANDROIDS BEING USED FOR SKEET SHOOTING BY MYSELF! A huge thanks. Thank God I took the time to do a quick backup with twrp before starting anything stupid. I still am unsure as to the original cause, it was only noticed after installing xposed but I've done any number of changes to this phone. If needed i can reset, make a backup, and upload for flashing in twrp for whoever wants it.
Seems like I had same or close to same with my T-Mobile Stylo 2 plus. (now unlocked on metro PCS)
A while back I had a weird issue where my default package installer would not install qpks. I downloaded another app from playstore and worked fine. I didn't pay much attention to it as I resolved the issue using a different app to install qpks.
Sent from my ph2n using XDA Labs
SM210 said:
Seems like I had same or close to same with my T-Mobile Stylo 2 plus. (now unlocked on metro PCS)
A while back I had a weird issue where my default package installer would not install qpks. I downloaded another app from playstore and worked fine. I didn't pay much attention to it as I resolved the issue using a different app to install qpks.
Sent from my ph2n using XDA Labs
Click to expand...
Click to collapse
I've traced the problem to having Mod Edit: warez installed. Seems the issue has been resolved with updates to Mod Edit: warez. The problem persisted even when using another app to install.
Hello guys,
Please accept my apologies if this topic was asked/discussed in other threads. I was unable to find an answer to this question with my searches.
For a while now, I have noticed that Magisk fails SafetyNet on Nougat stock ROM. If my memory serves me, it started with v16.0 and now with beta ver. 16.2 the issue is still ongoing.
Has anyone found a way to pass SafetyNet for stock ROM?
P.S. I have noticed that in Magisk Manager settings, the option "Magisk Hide" disables itself after reboot, I assume something prevents it from working properly (???).
Thanks a lot in advance,
Catalin D
I've been having the same issue and got no solutions other than using 15.3.
Isopropil said:
I've been having the same issue and got no solutions other than using 15.3.
Click to expand...
Click to collapse
Better than no solution at all!
I can confirm the same results. I went ahead and tried all versions from 15.3 to 16.3 - only 15.3 works.
Unfortunately that version is lacking something for me at least... Have you been able to get modules working in 15.3?
They fail to install directly from Magisk Manager. When I try to do it manually in TWRP, I get no errors but the modules are not there when I boot back into the system.
There's clearly some problems we're having that other devices aren't... And the fact that these problems seem to be handled silently doesn't help.
MelloZ said:
Better than no solution at all!
I can confirm the same results. I went ahead and tried all versions from 15.3 to 16.3 - only 15.3 works.
Unfortunately that version is lacking something for me at least... Have you been able to get modules working in 15.3?
They fail to install directly from Magisk Manager. When I try to do it manually in TWRP, I get no errors but the modules are not there when I boot back into the system.
There's clearly some problems we're having that other devices aren't... And the fact that these problems seem to be handled silently doesn't help.
Click to expand...
Click to collapse
I am also using 15.3 magisk with 5.5.5 manager and I have no issues. I have systemiser, debloater, busybox, greenify. the only mod that seems to be not working îs YouTube vanced. I uninstalled the system YouTube and the mod seems unable to install its version.
rzarectha said:
I am also using 15.3 magisk with 5.5.5 manager and I have no issues. I have systemiser, debloater, busybox, greenify. the only mod that seems to be not working îs YouTube vanced. I uninstalled the system YouTube and the mod seems unable to install its version.
Click to expand...
Click to collapse
Works fine here w/ same Magisk & Manager.
try this: Uninstall Vanced. Reinstall YouTube, but freeze it after install. Reboot. Redownload & install Vanced. Reboot. Unfreeze original YouTube & profit. Goodluck.
rzarectha said:
I am also using 15.3 magisk with 5.5.5 manager and I have no issues. I have systemiser, debloater, busybox, greenify. the only mod that seems to be not working îs YouTube vanced. I uninstalled the system YouTube and the mod seems unable to install its version.
Click to expand...
Click to collapse
amphi66 said:
Works fine here w/ same Magisk & Manager.
try this: Uninstall Vanced. Reinstall YouTube, but freeze it after install. Reboot. Redownload & install Vanced. Reboot. Unfreeze original YouTube & profit. Goodluck.
Click to expand...
Click to collapse
there's an even easier fix. Usually Vanced (iYTBP) doesn't work because there are two installs of Youtube (on /system/app and on /data/app) and it only replaces the one in /system. The solution is to deactivate auto-updates, then use a file manager (i recommend root browser all the way) to delete the /data/app/com.google.youtube folder (or however it is called, but the one that has the youtube apk inside).
and of course reboot after that
Whatever the problem was, it seems to have been fixed in the beta released today. (version name 16.4 - version code 1642) Working great.
Looking at his (topjohnwu's) changelog, it seems he made a ton of structure changes and improvements regarding MagiskHide, so it's no surprise this got fixed in the process.
May Magisk and the Axon 7 live long and prosper!
Okay so, ive tried every 6.0 ROM on the Shield forum for my portable and they all seem to have app crashing issues with the 6.0.1 pico Gapps (Setup, Play services, framework, play store all crashing, boot loops etc.)
I noticed i dont get these crashing errors whenever i boot the ROMs with no Gapps.
I spent hours and days researching why the crashing happens and ive seen things from "outdated/corrupted SU binary" to "incorrect permissions for 6.0.1 gapps" and i still dont know the cause.
SO i figured id try the apk route. i went to a certain APK site (not sure if we can link those) and grabbed every version for each gapp to see if i could get any of them installed. I found out when theres a corrupted app or incompatible app, android OS doesnt show the image for said APK/APP so i was able to weed out which apps would work.
Linked here are the apks i used to get the MM roms working with google/google apps again.
Install the PICO 6.0 GAPPS and then these APKs after getting into the OS to get going
The Pico-Apps are gonna make the initial boot time longer-- dont worry just let it load everything up (sometimes i had to button mash the shield button & home buttons to get past the boot animation-- sometimes it works and idky)
after installing all of the APKs, reboot the system, the OS is gonna initialize your apps again, might do it twice. after that youre good to go.
https://drive.google.com/drive/folders/1T9AXTYFcLg-dEUAfA7LdksUo_oPZ9yIl?usp=sharing