Related
Hey guys! It's me again... sorry So, I finally was able to make NoozXoide works with Spotify. It truly improves the sound, even with local files, different from others eq... But no, it's not enough. So, I decided to give up. I need Viper4Android, and only it.
When I was doing some research about sound mods without root, I remember finding an article which described how to install Viper4Android without rooting the device. I remember, though, it was necessairy to change SELinux Policies to permissive. But I can't find this article anywhere... So I figured it out it would be easier to ask you guys here. Also, I need to know if it's working with Android Nougat... I use Moto G4 Plus, just fyi.
Can you please help me?
(Sorry, I was in doubt about where should I post it)
http://stackoverflow.com/questions/...or-permissive-mode-in-android-4-4-4-and-above
I know how to change the SELinux, cause in most places they recomend an Selinux Changer... My doubt is, after changing Selinux, all I have to do is install Viper4Android..? Or do I have to install it before changing...? Do I have to keep it in permissive after installing the driver...?
Thanks!
Install with Permissive, but on every boot you need permissive
Won't work. Viper requires root in order to install its driver.
No root = no driver, regardless of what selinux is set to.
There are ways to flash the driver through a custom recovery, BUT, and I may be wrong, I believe you also need root in order to change selinux mode.
As far as I know, Viper won't work in enforcing mode, so even if you flash the driver, you'd still need root in order to change selinux for Viper to actually work.
How about installing a custom recovery, flashing the v4a driver and then try to set selinux to permissive with ADB?
Or just get magisk, there is a V4A systemless module.
Correct me if I'm wrong but If we just got magisk then we wouldnt need it without root because flash magisk and your rooted. No?
asafroid said:
Correct me if I'm wrong but If we just got magisk then we wouldnt need it without root because flash magisk and your rooted. No?
Click to expand...
Click to collapse
pretty much but you still need a custom recovery to flash Magisk and for most phones you need a unlocked bootloader to flash a custom recovery
Hey guys, I have a rooted US998 with magisk running on oreo. I was able to successfully install the latest viper4android, version 2.5.0.4, and driver installation went well. I rebooted, and when I check driver status, it says "enabled: yes status: normal". So you would think everything would be working fine. However, when I enable V4A, I hear no difference in the sound. I have an eq and several other changes, so I should definitely hear a difference in SQ when I enable V4A. I have tried both in neutron and poweramp. In poweramp, I turned off DVC (direct volume control), as the app suggest.
Any suggestions? To me, it seems that something on the phone is "overriding" the V4A output settings.
Thanks!
i can also confirm that turning the quad dac on or off makes no difference. Viper still doesn't do anything.
[/ATTACH]Working fine here
I've installed it with magisk
It's version 2.5.05
ricohz said:
Working fine here
I've installed it with magisk
Click to expand...
Click to collapse
you are using an earlier version than I am. I am going to uninstall the version I have now, and try to install through magisk modules the version you have and see if it works.
The version I installed was an apk downloaded from the official xda app thread.
son of a gun, that did it! I just installed the earlier version of v4a in the official thread and flashed the zip in twrp, rebooted, and all was good. Upon closer look, it seems that version that I used that was an apk install is actually an unofficial version of the app (despite being fully recognized as a magisk module). Too bad, I liked the UI much better . But glad to see it's now working. So anyone having issues w/ v4a, install the zip via recovery using the official app, not the unofficial apk.
Hisma said:
son of a gun, that did it! I just installed the earlier version of v4a in the official thread and flashed the zip in twrp, rebooted, and all was good. Upon closer look, it seems that version that I used that was an apk install is actually an unofficial version of the app (despite being fully recognized as a magisk module). Too bad, I liked the UI much better . But glad to see it's now working. So anyone having issues w/ v4a, install the zip via recovery using the official app, not the unofficial apk.
Click to expand...
Click to collapse
You can edit your thread topic to say SOLVED.
Sent via open market LG US998 V30/V30+
Hisma said:
son of a gun, that did it! I just installed the earlier version of v4a in the official thread and flashed the zip in twrp, rebooted, and all was good. Upon closer look, it seems that version that I used that was an apk install is actually an unofficial version of the app (despite being fully recognized as a magisk module). Too bad, I liked the UI much better . But glad to see it's now working. So anyone having issues w/ v4a, install the zip via recovery using the official app, not the unofficial apk.
Click to expand...
Click to collapse
If you like the material design that much, you can get the material look back. Reflash that same Viper4Android. Just pay close attention to the installation log in Magisk Manager and press Up on the Volume when it says "Test mode". Then you can select the "Material" design instead of Original before selecting which sound driver version you'd like.
I would like to know what you are saying about the sound with DAC in connection with Viper4Android. Is there now Rome, where you can turn on the DAC, but not the default settings of LG has? because I found that faked the sound with Viper. Would be glad about feedbacks. I'd love to use only viper, but with the built in DAC together it sounds better again. but just without the stupid sound profiles of LG.
Hisma said:
son of a gun, that did it! I just installed the earlier version of v4a in the official thread and flashed the zip in twrp, rebooted, and all was good. Upon closer look, it seems that version that I used that was an apk install is actually an unofficial version of the app (despite being fully recognized as a magisk module). Too bad, I liked the UI much better . But glad to see it's now working. So anyone having issues w/ v4a, install the zip via recovery using the official app, not the unofficial apk.
Click to expand...
Click to collapse
So are you saying you chose the older version in the magisk module?
Nothing I do seems to work.
Sent from my LG-H932 using XDA Labs
Install the fallowing Magisk Modules ViPER4Android FX, Audio Compatibility Patch, Audio Modification Library and Selinux Permissive reboot and you should be good to go.
So one of the reason why I rooted my phone 2 days ago was because of font style and Dolby Atmos. I waited so long and it's still not coming. I decided to root. I unlocked bootloader, installed TWRP, installed MAGISK, basically everything you need to do to install Pixel Experience. I went to an article about how to install Dolby Atmos on rooted device. I downloaded the zip and flashed it using TWRP. The app was there, but when I opened it, it just crashed. I ended up recovering my device to a state right before I installed that Dolby. Any clue?
Hi If I'm not mistaken, Dolby in Pocophone only works on Oreo systems ... I installed Dolby in all my root phones, but it was impossible in Pocophone, I guess due to lack of development, So I gave up on installing it.
You can download flash zip her https://forum.xda-developers.com/android/software/mm-p-dolby-digital-plus-arise-20181115-t3868192
For work you need set se Linux to permissive.
If you let se Linux to enforcing, the app is force closing many times and unstable for usage
AndreSkywalker said:
You can download flash zip her https://forum.xda-developers.com/android/software/mm-p-dolby-digital-plus-arise-20181115-t3868192
For work you need set se Linux to permissive.
If you let se Linux to enforcing, the app is force closing many times and unstable for usage
Click to expand...
Click to collapse
Uh, what is se Linux? Sorry, I am completely new to rooting. Just literally rooted my phone about 2 days ago...
I just checked the article you posted. Apparently there are many people complaining about it being not working. Guess I'll wait until someone actually manage to make a compatible one. Also that one was Dolby Digital though, not Dolby Atmos..
nazagato said:
Hi If I'm not mistaken, Dolby in Pocophone only works on Oreo systems ... I installed Dolby in all my root phones, but it was impossible in Pocophone, I guess due to lack of development, So I gave up on installing it.
Click to expand...
Click to collapse
So a more modern android version won't work? That's a huge bummer to be honest.
Maybe try to get Dirac like in HavocOS cause it seems realy good
Triparadox said:
Uh, what is se Linux? Sorry, I am completely new to rooting. Just literally rooted my phone about 2 days ago...
I just checked the article you posted. Apparently there are many people complaining about it being not working. Guess I'll wait until someone actually manage to make a compatible one. Also that one was Dolby Digital though, not Dolby Atmos..
Click to expand...
Click to collapse
Se Linux is a configuration in kernel. I have many audio mods in pocophone (like a dolby atmos, viper4android and ainur sauron). For make this mods work, you need a custom kernel with support for se Linux permissive.
After installing a custom kernel (Franco Kernel for example) you can mark Se Linux permissive in several ways. I use a simple application that set up Se Linux to permissive on boot of the phone. The application name is if "The SeLinux switch" . That done dolby atmos will work without problems.
AndreSkywalker said:
Se Linux is a configuration in kernel. I have many audio mods in pocophone (like a dolby atmos, viper4android and ainur sauron). For make this mods work, you need a custom kernel with support for se Linux permissive.
After installing a custom kernel (Franco Kernel for example) you can mark Se Linux permissive in several ways. I use a simple application that set up Se Linux to permissive on boot of the phone. The application name is if "The SeLinux switch" . That done dolby atmos will work without problems.
Click to expand...
Click to collapse
Wait wait.. I'm lost.. You mentioned a bit about custom kernel. What is that? All I have done is unlock bootloader, install twrp, install magisk, install custom rom pixel experience. What is kernel? What is custom kernel? What's the function of it? How do we change it? What should I do? Do I just flash several zip or apks to make it work? If possible, please explain in non technical terms.. Some articles I found are just too complicated or use too many technical terms that I don't know..
Triparadox said:
Wait wait.. I'm lost.. You mentioned a bit about custom kernel. What is that? All I have done is unlock bootloader, install twrp, install magisk, install custom rom pixel experience. What is kernel? What is custom kernel? What's the function of it? How do we change it? What should I do? Do I just flash several zip or apks to make it work? If possible, please explain in non technical terms.. Some articles I found are just too complicated or use too many technical terms that I don't know..
Click to expand...
Click to collapse
It may seem complicated to those unfamiliar with roms mods, but over time you will get used to it. Basically to customize a cellphone there are three steps.
1) unlock bootloader and install custom recovery (TWRP)
2) Install a custom rom and root (magisk)
3) Install a custom kernel
You stopped at step 2, you do not need to do step 3, but if you want to further customize you should install a custom kernel (modify sound quality, CPU usage, GPU, battery). The kernel is the basic configuration between the hardware (physical part of the phone) and the software (android).
Anyway to install a kernel is very easy, just flash the kernel zip, just as you did the rom. download this kernel for example https://forum.xda-developers.com/poco-f1/development/kernel-canting-0-1-t3907883.
After flashing the kernel just install the application I passed previously, open the application and choose the option if linux to permissive, after that dolby atmos will work without problems
Triparadox said:
So one of the reason why I rooted my phone 2 days ago was because of font style and Dolby Atmos. I waited so long and it's still not coming. I decided to root. I unlocked bootloader, installed TWRP, installed MAGISK, basically everything you need to do to install Pixel Experience. I went to an article about how to install Dolby Atmos on rooted device. I downloaded the zip and flashed it using TWRP. The app was there, but when I opened it, it just crashed. I ended up recovering my device to a state right before I installed that Dolby. Any clue?
Click to expand...
Click to collapse
Happened same to me yesterday.I tried dolby and it crashed.So now I'm using Viper4Android, it works great.I can send you settings for headset:
Headset
Master Power: ON
PlaybackAGC: ON
Effect Strength: Moderate
Firequalizer: ON
Preset: R&B
Headphone Surround: ON
Effect Level: 2
Viper Bass: ON
Bass Boost: 3.5dB
Viper Clarity: ON
Clarity: 3.5dB
Cure Tech+: ON
Binaural Level: Extreme
Cheers
AndreSkywalker said:
It may seem complicated to those unfamiliar with roms mods, but over time you will get used to it. Basically to customize a cellphone there are three steps.
1) unlock bootloader and install custom recovery (TWRP)
2) Install a custom rom and root (magisk)
3) Install a custom kernel
You stopped at step 2, you do not need to do step 3, but if you want to further customize you should install a custom kernel (modify sound quality, CPU usage, GPU, battery). The kernel is the basic configuration between the hardware (physical part of the phone) and the software (android).
Anyway to install a kernel is very easy, just flash the kernel zip, just as you did the rom. download this kernel for example https://forum.xda-developers.com/poco-f1/development/kernel-canting-0-1-t3907883.
After flashing the kernel just install the application I passed previously, open the application and choose the option if linux to permissive, after that dolby atmos will work without problems
Click to expand...
Click to collapse
Ah ok. Thanks. At least I know where I am at and what step is doing the kernel is. So all I have to do is to download the custom kernel and flash it to the system using TWRP, then I flash the dolby atmos like I did previously but it should not work because I have custom kernel. One quick question, after/before flashing the custom kernel, is there anything I need to wipe? I believe I remember I wiped the cache and DAVIX previously otherwise it wouldn't work.
Triparadox said:
Ah ok. Thanks. At least I know where I am at and what step is doing the kernel is. So all I have to do is to download the custom kernel and flash it to the system using TWRP, then I flash the dolby atmos like I did previously but it should not work because I have custom kernel. One quick question, after/before flashing the custom kernel, is there anything I need to wipe? I believe I remember I wiped the cache and DAVIX previously otherwise it wouldn't work.
Click to expand...
Click to collapse
No wipes. Just flash kernel via TWRP. After this flash dolby atmos and reboot. Open app and set se Linux to permissive Mode. Dolby atmos work it
AndreSkywalker said:
No wipes. Just flash kernel via TWRP. After this flash dolby atmos and reboot. Open app and set se Linux to permissive Mode. Dolby atmos work it
Click to expand...
Click to collapse
I just did what you told me. I flashed the kernel via TWRP and then flashed the Dolby zip. Then I reboot to the system. Next I installed the apk for SELinux. Opened that app and granted it superuser for 10 mins to change from enforcing to permissive. Opening Dolby seems to still be forced closing.
Triparadox said:
I just did what you told me. I flashed the kernel via TWRP and then flashed the Dolby zip. Then I reboot to the system. Next I installed the apk for SELinux. Opened that app and granted it superuser for 10 mins to change from enforcing to permissive. Opening Dolby seems to still be forced closing.
Click to expand...
Click to collapse
Are you using version 6.5 of Dolby Atmos? Check the list of modules installed on your magisk. I will take a screenshot of my pocophone.
AndreSkywalker said:
Are you using version 6.5 of Dolby Atmos? Check the list of modules installed on your magisk. I will take a screenshot of my pocophone.
Click to expand...
Click to collapse
i don't see any module.
Triparadox said:
i don't see any module.
Click to expand...
Click to collapse
Where did you download dolby atmos? Download the latest version from this link below, only this version works on Android pie. After downloading it, tweet the Dolby Atmos 6.5 flash you downloaded. After rebooting dolby should appear in the magisk module list
https://forum.xda-developers.com/android/software/mm-p-dolby-digital-plus-arise-20181115-t3868192
AndreSkywalker said:
Where did you download dolby atmos? Download the latest version from this link below, only this version works on Android pie. After downloading it, tweet the Dolby Atmos 6.5 flash you downloaded. After rebooting dolby should appear in the magisk module list
https://forum.xda-developers.com/android/software/mm-p-dolby-digital-plus-arise-20181115-t3868192
Click to expand...
Click to collapse
Yeah, thanks for that. I downloaded the top one because I thought that was the newest version. It works fine now. Also is it also happening to you that you can't really change the setting for custom and the movie profile and music profiled doesn't seem to have any difference? Game one does make it louder tho.
Triparadox said:
Yeah, thanks for that. I downloaded the top one because I thought that was the newest version. It works fine now. Also is it also happening to you that you can't really change the setting for custom and the movie profile and music profiled doesn't seem to have any difference? Game one does make it louder tho.
Click to expand...
Click to collapse
I use dolby atmos with viper4android. Dolby atmos is effective with the headset, without the headset it doesn't work very loudly, while viper4android works both ways.
I see that there's some activity previously for various Blackview phones, Is it too much to hope for that someone will be able to do something for this phone?
Hi, I own one Blackview BV9900 (no Pro) and managed to do some work on it. Pro version has pretty the same hardware, so it should work on it too:
- root works with no problems with Magisk (just download stock boot.img, update it with MagiskManager app and flash),
- I've also managed to build working TWRP recovery ROM and I think I'll try to push it to twrp repositories when find some time.
Where am I to find the stock boot.img?
rollerce said:
Where am I to find the stock boot.img?
Click to expand...
Click to collapse
I found stock firmware officially shared on Blackview forum: http://bbs.blackview.hk/viewtopic.php?f=291&t=532819
Izzat going to work for the pro?
Can't say. Manufacturer haven't published firmware for pro version yet. It is likely to work since the hardware is similar to non-pro, but I've tested in only on non-pro version and it works.
It'll throw an error of it's not compatible, though?
Unfortunately it is not that simple. Even if it's not compatible it usually flashes successfully anyway and problems begin with boot from such partition (boot-loop etc.) and then you will need original ROM (or another compatible) to make device usable again.
Maybe try to ask on this Blackview forum if this non-pro images are compatible with pro version. I think there is huge chance for that.
Issues
Hey,
Have the BV9900 using Verizon. Since the 1st day using the phone I'm unable to receive calls from iPhones. Went to Verizon to see if they had a setting I missed. Nope. Had them dial my number from their iPhones and they all failed to connect. I can call out to iPhones. Contacted BV and was told to save an file and send it to them, which I did and the reply was no problem found.
They just pushed out an update, which after downloaded I now have an issue making ANY calls out. Sometimes it will connect for a few seconds and then fail. The only way to make a call now is be disabling the LTE Enhanced setting under Network. The side effect of doing that is nothing else works. No texts, news, anything!
I now see that someone else is also having the same issue.
This BV9900 replaced a BV9500 (the brick) and has zero issues with that phone. Yes its a different version of andriod, but still was able to receive and place any calls to anyone. I took the SIM out of the 9900 and put it in the 9500 and everything worked.
Not sure what to do as BV does not have an answer or appear to even care.
Thanks
Hi, finally managed to share my rooted boot and custom recovery images. Both have been successfully flashed into my BV9900 and worked fine. Maybe this can be useful to someone.
Recovery image with Twrp:
https://www.androidfilehost.com/?w=files&flid=313541
Boot image patched with Magisk (also you need to install MagiskManager app to manage root access in the system):
https://www.androidfilehost.com/?w=files&flid=313543
Can you assist me? When I restart into bootloader menu I get the annoying noise windows makes when you unplug something from USB, and the device manager window flashes. Fastboot devices returns with nothing even when phone is in fast boot mode.... GAH
I'm having the same problem with connecting in fastboot mode as well.
I'm using Ubuntu and didn't have any problems with connecting device via USB. Maybe try to install latest USB drivers (https://www.getdroidtips.com/download-blackview-bv9900-usb-drivers/) or run Ubuntu live (or install) and access device from it - it's really easy.
dzert127 said:
I'm using Ubuntu and didn't have any problems with connecting device via USB. Maybe try to install latest USB drivers (https://www.getdroidtips.com/download-blackview-bv9900-usb-drivers/) or run Ubuntu live (or install) and access device from it - it's really easy.
Click to expand...
Click to collapse
This is honestly a completely useless answer. "Just use ubuntu" is not helpful.
As far as drivers, I've tried so many different options to no effect.
dzert127 said:
Hi, I own one Blackview BV9900 (no Pro) and managed to do some work on it. Pro version has pretty the same hardware, so it should work on it too:
- root works with no problems with Magisk (just download stock boot.img, update it with MagiskManager app and flash),
- I've also managed to build working TWRP recovery ROM and I think I'll try to push it to twrp repositories when find some time.
Click to expand...
Click to collapse
I tried this before I saw this thread with the 9900 pro. The checksum or something doesn't add up with the flashed magisk edited boot.img and puts it in a boot loop.. I had to reflash the original boot.img. no root on my pro yet. Original IMG is 30ish megabytes and the patched one is 10mb. An I doing something wrong?
[Edit] I forgot to unlock bootloader. Did it with fastboot. The magisk edited boot.img flashed. Now that I have basic proof of rootability, I'll probably flash SuperSU instead.
Root for the BV9900 Pro?
pbsavages said:
I tried this before I saw this thread with the 9900 pro. The checksum or something doesn't add up with the flashed magisk edited boot.img and puts it in a boot loop.. I had to reflash the original boot.img. no root on my pro yet. Original IMG is 30ish megabytes and the patched one is 10mb. An I doing something wrong?
[Edit] I forgot to unlock bootloader. Did it with fastboot. The magisk edited boot.img flashed. Now that I have basic proof of rootability, I'll probably flash SuperSU instead.
Click to expand...
Click to collapse
So Im confused. Did this method work for you in the BV9900 Pro or not?
mattchapa said:
So Im confused. Did this method work for you in the BV9900 Pro or not?
Click to expand...
Click to collapse
The magisk root method works with the patched boot.img, though it is a systemless root only. I couldn't get a custom recovery to work yet but haven't look at it in a couple weeks. I was waiting for more people to get this device for it to gain momentum.
Thank you. I'll give it a go then.
I have the BV9900 PRO too and would love to get installed LineageOS GSI on it. Tried the unofficial TWRP 331 on my BV9900pro without success - boot loop. It looks like that the PRO is more different compared to the BV9900.
unofficialtwrp.com/blackview-bv9900-twrp-3-3-1-root/
still no successful Root/Recovery possible?
Can anyone help me to get TWRP recovery installed on the Blackview BV9900Pro, please ? Can't find a working TWRP for the Pro.
As written above, the version for the (non Pro) BV9900 doesn't work.
Thanks for any help!
Hey,
Yesterday I've rooted my phone with this method: https://forum.xda-developers.com/t/tutorial-twrp-and-root-nord-2.4340477/
Worked as it should, thanks.
Now I try to install viper4android on the device (main reason I've rooted it ), but I can't get it work.
Everytime I install it, then install the driver and reboot, it detects no driver, so again install driver etc...
I've tried audi modification library, v4a fx legacy, flashed the drivers in TWRP, and so many things. The weird thing is that, magisk can't install the apk, I have to do it manually. Even tried to set SELinux permissive, but I couldn't change it.
Anyone can help me? Tinkering phone was easier back in the day
Thanks!
szmoki42 said:
Hey,
Yesterday I've rooted my phone with this method: https://forum.xda-developers.com/t/tutorial-twrp-and-root-nord-2.4340477/
Worked as it should, thanks.
Now I try to install viper4android on the device (main reason I've rooted it ), but I can't get it work.
Everytime I install it, then install the driver and reboot, it detects no driver, so again install driver etc...
I've tried audi modification library, v4a fx legacy, flashed the drivers in TWRP, and so many things. The weird thing is that, magisk can't install the apk, I have to do it manually. Even tried to set SELinux permissive, but I couldn't change it.
Anyone can help me? Tinkering phone was easier back in the day
Thanks!
Click to expand...
Click to collapse
Hi,
Unfortunately, it doesn't work for me either and there is currently no solution to the problem
Man that just s#cks.
If anyone knows something, please don't hold it