As of March 8th, 2015, rovo89 has updated the Xposed framework to Alpha 2, removing the need to have SELinux set to permissive.
So me and a few other guys over in the Xposed Thread were having issues getting our Nexus 6 devices to run the new Xposed Alpha properly. It kept throwing out errors that Xposed wasn't installed and modules didn't work. After a bunch of trial and error, we figured out how to make it work (at least for us)! So if you're having similar issues, try this workaround until Xposed is updated to fix this (although it may be a Nexus 6 error only).
Note: Make sure you already have Xposed installed. http://forum.xda-developers.com/xposed/official-xposed-lollipop-t3030118
Here's a list of which modules are working or not working for some people.
Although these modules have been reported to be functional for some users, the modules may behave differently on our device.
Method 1
1. Make sure SELinux is set to Permissive. You can set it to permissive using this root app, if your kernel isn't permissive by default. https://play.google.com/store/apps/details?id=com.mrbimc.selinux
2. When rebooting into your system after setting SELinux to permissive, enable the Xposed modules that you want.
3. From inside the Xposed app, perform a soft reboot.
4. When the device fully boots up, Xposed should now be fully working. If you still have issues, converting Xposed to a system app might help.
Method 2 Thanks to skaforey
1. Download this script from post #65
2. Extract the file to the root of your sdcard.
3. Using a Terminal Emulator, type the following commands:
Code:
su
cd /sdcard/
sh initd.sh
4. Reboot and Xposed should now be working without a soft reboot needed.
Method 3
1. Flash one of the these zips, which does the same thing as Method 2, but easier! Thanks to both 4got and rootSU
Both files do the same thing
Zip 1 (by 4got)
Zip 2 (by rootSU)
2. Everything should be fully working now!
Not all ROM/Kernel configurations support init.d scripts!
Method 4
1. Use a kernel that's been set to permissive by default. Please don't bother/annoy devs to make their kernels permissive.
Here's a version of LeanKernel modified by Imoseyon to be permissive be default.
LeanKernel (Permissive)
2. Everything should be working. Flashing another kernel will disable Xposed again, unless the kernel is permissive or you fallback on other methods.
Method 5 Thanks to flar2 and shivindera.
Required SuperSU to be installed.
This method differs from Method 3 because the script to set SELinux to permissive is located in /system/su.d (instead of init.d) and allows for compability with more ROM/Kernel configurations. This post by flar2 will better explain what this script does.
1. Flash this zip by shivindera.
2. Everything should be working
Note: For advanced users who already have files in /system/su.d/ please remove the "delete" line from the updater-script so as to not lose any of your already pre-existing files.
Please post here if it worked for you. So far for us over at the Xposed thread, it seems to have worked. Thanks guys! Enjoy your modules!
The problem I imagine is that xposed activates on boot before the selinux mode changer changes the permissive flag. The soft reboot doesnt envoke the default mode as a full boot does, so the mode changer app has already done what is needed.. On the n5 we had a permissive kernel by @sykopompos. I imagine if we had that, we wouldn't need the soft reboot. Is there such a thing for the n6?
rootSU said:
The problem I imagine is that xposed activates on boot before the selinux mode changer changes the permissive flag. The soft reboot doesnt envoke the default mode as a full boot does, so the mode changer app has already done what is needed.. On the n5 we had a permissive kernel by @sykopompos. I imagine if we had that, we wouldn't need the soft reboot. Is there such a thing for the n6?
Click to expand...
Click to collapse
I'm sure it could be made. I guess it's up to the kernel devs to make the default permissive.
EDIT: I was reading the Xposed thread, and you're right! Xposed runs at boot, but SELinux Changer sets SELinux to Permissive after Xposed runs, which is why a soft reboot works, because your restarting Xposed while SELinux is at Permissive. So yes, a kernel set to permissive to default will do the trick without this workaround.
Dude this worked! Thanks so much!
Worked for me too!
Worked here!
Sent from my Nexus 6 using XDA Free mobile app
Oh but a full reboot removes it again...
poczynek said:
Oh but a full reboot removes it again...
Click to expand...
Click to collapse
Yes. Read above.
I think Kernel Devs won't do such a thing, flar2 for example said for his ElementalX Kernel he won't set it to Permissive for various Reason. I imagine other Devs have a similar Opinion.
But I'm sure rovo will fix it in time
D-m-x said:
I think Kernel Devs won't do such a thing, flar2 for example said for his ElementalX Kernel he won't set it to Permissive for various Reason. I imagine other Devs have a similar Opinion.
But I'm sure rovo will fix it in time
Click to expand...
Click to collapse
I'm sure he will not sure how though. We can't delay xposed start up because ART is not JiT so all instructions run at boot rather than when you run a "command"
Nope. I did manage to bork my app drawer lol. Might be the theme update though.
negativzeroe said:
Nope. I did manage to bork my app drawer lol. Might be the theme update though.
Click to expand...
Click to collapse
The top picture is normal, working or not...
Yep this made it work. Thanks. However does that mean when we boot we will then have to soft boot to get it enabled everytime until either rovo fixes it somehow or kernel debs set their default to SELinux permissive?
rootSU said:
The top picture is normal, working or not...
Click to expand...
Click to collapse
I also set xGEL to have a 5 column app drawer, no-go.
bmg1001 said:
So me and a few other guys over in the Xposed Thread were having issues getting our Nexus 6 devices to run the new Xposed Alpha properly. It kept throwing out errors that Xposed wasn't installed and modules didn't work. After a bunch of trial and error, we figured out how to make it work (at least for us)! So if you're having similar issues, try this workaround until Xposed is updated to fix this (although it may be a Nexus 6 error only).
Note: Make sure you already have Xposed installed. http://forum.xda-developers.com/xposed/official-xposed-lollipop-t3030118
1. Make sure SELinux is set to Permissive. You can set it to permissive using this root app, if your kernel isn't permissive by default. https://play.google.com/store/apps/details?id=com.mrbimc.selinux
2. When rebooting into your system after setting SELinux to permissive, enable the Xposed modules that you want.
3. From inside the Xposed app, perform a soft reboot.
4. When the device fully boots up, Xposed should now be fully working. If you still have issues, converting Xposed to a system app might help.
PLEASE PLEASE PLEASE post here if it worked for you. So far for us over at the Xposed thread, it seems to have worked. Thanks guys! Enjoy your modules!
Click to expand...
Click to collapse
Its working great for me.
Switching to permissive worked for me. Thank you
Nexus 6
Works now, thank you.
Damn, so I'm the only one that it still doesn't work for?
flonker said:
Damn, so I'm the only one that it still doesn't work for?
Click to expand...
Click to collapse
Are you following the instructions closely? Using g a known lollipop compatible module? Tinted status bar seems easiest test to me.
rootSU said:
Are you following the instructions closely? Using g a known lollipop compatible module? Tinted status bar seems easiest test to me.
Click to expand...
Click to collapse
Tried it with YouTube AdAway, I'll try tinted status bar.
Related
Having root now, is it possible to remove/change/delete the verizon boot logo? Its bright and overall annoying. Plus, any less VZW branding on my phone the better.
Or is that something that will require a custom recovery?
Xposed Framework -> Xblast Tools module -> Build.prop Tweaks section
i wouldnt attempt anything until i could make a nandroid
oneandroidnut said:
i wouldnt attempt anything until i could make a nandroid
Click to expand...
Click to collapse
Ya, this is holding me back from removing "custom" in the phone and the unlock screen on startup as well.
I don't really like messing with things that deep without a backup.
jsk23 said:
Ya, this is holding me back from removing "custom" in the phone and the unlock screen on startup as well.
I don't really like messing with things that deep without a backup.
Click to expand...
Click to collapse
i agree i messed with and somehow got all apps in mw using xposed but that was deep enough for me right now!
I changed my custom to official with no issues ....using wanam
Sent from my SM-N900V using xda app-developers app
oneandroidnut said:
i agree i messed with and somehow got all apps in mw using xposed but that was deep enough for me right now!
Click to expand...
Click to collapse
I was able to used Xposed Framework to get rid of the Custom Logo just fine. Try it, I dont think you will have any issues (Although it did take me a few tries to get it to work)
:good:
Lightyear25 said:
I was able to used Xposed Framework to get rid of the Custom Logo just fine. Try it, I dont think you will have any issues (Although it did take me a few tries to get it to work)
:good:
Click to expand...
Click to collapse
I don't want to risk anything lol
Sent from my SM-N900V using Tapatalk now Free
blap017 said:
I changed my custom to official with no issues ....using wanam
Sent from my SM-N900V using xda app-developers app
Click to expand...
Click to collapse
I don't see this anywhere in Wanam.
Lightyear25 said:
I was able to used Xposed Framework to get rid of the Custom Logo just fine. Try it, I dont think you will have any issues (Although it did take me a few tries to get it to work)
:good:
Click to expand...
Click to collapse
Details please.
The officiate status change is under security hacks. .. fake system status.
Sent from my GlaDos Baked Potato
Edit. The lock symbol showed at boot up the first reboot. But never after. Done a few today.
Legato Bluesummers said:
The officiate status change is under security hacks. .. fake system status.
Sent from my GlaDos Baked Potato
Edit. The lock symbol showed at boot up the first reboot. But never after. Done a few today.
Click to expand...
Click to collapse
I was looking for a way to remove the VZW boot animation, thanks though.
Easy guide for getting rid of the CUSTOM logo and symbol at boot.
First, you have to install Xposed Framework, this is just an APK that you download from http://forum.xda-developers.com/showthread.php?t=1574401
Once you install the APK, simply head to the Google Play store and download the Wanam Module at https://play.google.com/store/apps/details?id=ma.wanam.xposed&hl=en
Once Wanam is installed, go into Xposed, and put a check on the module "Wanam" then go into Wanam and then go Security Hacks - Fake System Status.
Note: It took me rebooting a few times and toggling it on and off to get it to work, but was worth it, that logo was U G L Y.
Lightyear25 said:
Easy guide for getting rid of the CUSTOM logo and symbol at boot.
First, you have to install Xposed Framework, this is just an APK that you download from http://forum.xda-developers.com/showthread.php?t=1574401
Once you install the APK, simply head to the Google Play store and download the Wanam Module at https://play.google.com/store/apps/details?id=ma.wanam.xposed&hl=en
Once Wanam is installed, go into Xposed, and put a check on the module "Wanam" then go into Wanam and then go Security Hacks - Fake System Status.
Note: It took me rebooting a few times and toggling it on and off to get it to work, but was worth it, that logo was U G L Y.
Click to expand...
Click to collapse
Not being able to make a backup still bothers me. But this Verizon logo and the unlock boot screen are starting to annoy me. Has anyone who has modified either of these had any issues or complications yet? That may reassure me a bit.
No issues that I've seen. Did it 6 am this morning. Haven't had a problem all day. Done a few more reboots when I tweaked more stuff. Still running great.
Sent from my GlaDos Baked Potato
Guys why don't you just apply the boot animation manually? Here is how:
1. Download your boot animation and extract it if it's 7zipped up, you will have 2 files in .qmg file format
2. Use a root browser on your phone to navigate to /system/media
3. Rename bootsamsung.qmg to .bak and also bootsamsungloop.qmg to .bak(so you can revert rather than just deleting them)
4. Ensure that your custom boot animation is named bootsamsung.qmg and bootsamsungloop.qmg and copy them to /system/media
5. Reboot and it should work!
Very good
Hi, guys! I had nothing to do last night so I created one simple app: SELinuxModeChanger
All it does is switches SELinux mode to permissive. And does this automatically everytime you reboot your device.
short QA:
Q: Why to change SELinux mode?
A: SELinux in "enforcing" breaks some rooty apps like titanium backup, ultimate dynamic navbar and bunch of GMD apps. Switching it to "permissive" is the easiest temporal fix to make those app work until devs not added support of enforcing mode
Q: Why it's not a init.d script?
A: Wasn't sure that stock kernels support init.d scripts, so made the most universal way Will add init script as an option later, tho
Q: Will it hurt my device?
A: No, it will not.
Its great. I got call master working again with this. Thank you.
Sent from my Nexus 5 using xda premium
It does not automatically change from enforcing to permissive. I have enabled notifications. After booting up, it shows 'changed to enforcing' whereas I had set it to 'permissive' successfully before the reboot.
Using Franco kernel on 5.0.1.
Sent from my Nexus 5 using XDA Free mobile app
Available on F-Droid now. Thanks!
https://f-droid.org/repository/browse/?fdfilter=selinuxmodechanger&fdid=com.mrbimc.selinux
dioxide95 said:
It does not automatically change from enforcing to permissive. I have enabled notifications. After booting up, it shows 'changed to enforcing' whereas I had set it to 'permissive' successfully before the reboot.
Using Franco kernel on 5.0.1.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Items this app
Sent from my Nexus 5
hey guys, just wondering if there are any viper4android users out there and if anyone has managed to get it working on the N6P
driver wont stick for me. I miss my EQ!
This post helped out in the nexus 5x forums,
Post- http://forum.xda-developers.com/showpost.php?p=63486621&postcount=7
richie.slayer said:
This post helped out in the nexus 5x forums,
Post- http://forum.xda-developers.com/showpost.php?p=63486621&postcount=7
Click to expand...
Click to collapse
Thanks! worked for me.
I was able to get it installed using the steps in the 5X forum, but only works in compatibility mode. Has anyone got it working in normal mode?
edd247 said:
I was able to get it installed using the steps in the 5X forum, but only works in compatibility mode. Has anyone got it working in normal mode?
Click to expand...
Click to collapse
nope... would really really hope someone figures this out. viper is a must have for me. #2 reason to why I must root my phones.
johnp357 said:
nope... would really really hope someone figures this out. viper is a must have for me. #2 reason to why I must root my phones.
Click to expand...
Click to collapse
Yep, mine is running in normal. I do have SELinuxModeChanger set to permissive. Did you try that? Did you disable musicFX? Besides that I did exactly what was listed in the nexus 5x set-up.
veggicide said:
Yep, mine is running in normal. I do have SELinuxModeChanger set to permissive. Did you try that? Did you disable musicFX? Besides that I did exactly what was listed in the nexus 5x set-up.
Click to expand...
Click to collapse
where is the musicFX disable option? looked everywhere on the 6p and couldn't find it??
well, I don't know why but it seems to work now... without locating the musicFX disable option... followed the direction like on the link for the nexus 5 but also installed selinuxmodechanger and set to permissive. that seemed to work.
veggicide said:
Yep, mine is running in normal. I do have SELinuxModeChanger set to permissive. Did you try that? Did you disable musicFX? Besides that I did exactly what was listed in the nexus 5x set-up.
Click to expand...
Click to collapse
I am using systemless root and the selinuxmodechanger app does not work with this root method, so I used the permissive zip from flar2. I disabled musicfx and it still wont work in normal mode
---------- Post added at 09:35 AM ---------- Previous post was at 09:34 AM ----------
johnp357 said:
where is the musicFX disable option? looked everywhere on the 6p and couldn't find it??
Click to expand...
Click to collapse
go to settings, apps, then hit menu in top right, press show system, then scroll to find musicfx, then press disable
[/COLOR]
go to settings, apps, then hit menu in top right, press show system, then scroll to find musicfx, then press disable[/QUOTE]
changing musicfx back and forth didn't change the sound. but I know that the sound changed following the instructions and adding permissive option on selinux so maybe removing the file from the directory affected this?
I also followed the steps from the 5x forum and I am unable to get the driver to stick. I am rooted the non systemless way.
I had to use rootbrowser to delete the audio_effects.conf permanently. Once I did that, it worked
Sent from my Nexus 6P using Tapatalk
rpinnocent said:
I had to use rootbrowser to delete the audio_effects.conf permanently. Once I did that, it worked
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Where is this file located? Also where is the viper for Android apk located?
Sent from my Nexus 6P using XDA Free mobile app
It works for me in Google Play Music but not in PowerAMP, also only with Compatible mode.
I wish it worked perfectly fine
shinta86 said:
I also followed the steps from the 5x forum and I am unable to get the driver to stick. I am rooted the non systemless way.
Click to expand...
Click to collapse
Same here, can't get the driver to stick
bsg411 said:
Where is this file located? Also where is the viper for Android apk located?
Sent from my Nexus 6P using XDA Free mobile app
Click to expand...
Click to collapse
File is located in system/vendor/etc and the apk is in the OP
Sent from my Nexus 6P using Tapatalk
Does viper4android give us system wide audio control? Such as allowing us to change the gain on the top/bottom speakers?
Edit: Dw I found out it does. Just need to root and get it now then.
I'm having constant problems keeping this working. I did everything told in http://forum.xda-developers.com/showpost.php?p=63486621&postcount=7 yet every other day I get the issue of going into Google Music, playing music, and when I try to go to settings to get to Viper EQ, the music stops and Viper tells me all of a sudden that the driver isn't installed again (when it definitely was and was working fine).
Also, lately when I go into the SELinuxModeChanger app, it shows Enforcing is chosen, even right after I change it to Permissive. It keeps changing back on its own, even after root permissions are granted.
This wasn't happening until recently.
Running Elemental X's kernel if that matters.
Any ideas?
So I couldn’t wait any more so this weekend I rooted and got my Viper ON. Viper is one of the main reasons that I root. This is what I did:
1) I get TWRP and rooted by doing this:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
2) Now that I’m rooted, I get busy box working
3) I didn’t need to change my SEL Mode by doing this.
4) I Boot into TWRP and I flashed the attach zip. “ViPER4Android-supolicy.zip”
5) Disable MusicFX and then I went into system/vendor/etc and killed “audio_effects.conf”
6) Open Viper and install best Driver
7) I had to re-flash the zip 2-3 times without wiping before I got it working.
Now my 6P is on MDB08M, Crypted, enforcing mode with TWRP and rooted with Viper.
edit: here more info about the the attached zip:
http://forum.xda-developers.com/showthread.php?p=61242973#post61242973
boxcar8028 said:
So I couldn’t wait any more so this weekend I rooted and got my Viper ON. Viper is one of the main reasons that I root. This is what I did:
1) I get TWRP and rooted by doing this:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
2) Now that I’m rooted, I get busy box working
3) I didn’t need to change my SEL Mode by doing this.
4) I Boot into TWRP and I flashed the attach zip. “ViPER4Android-supolicy.zip”
5) Disable MusicFX and then I went into system/vendor/etc and killed “audio_effects.conf”
6) Open Viper and install best Driver
7) I had to re-flash the zip 2-3 times without wiping before I got it working.
Now my 6P is on MDB08M, Crypted, enforcing mode with TWRP and rooted with Viper.
edit: here more info about the the attached zip:
http://forum.xda-developers.com/showthread.php?p=61242973#post61242973
Click to expand...
Click to collapse
thanks, this worked great for me but I don't have music fx to disable.
Looking for the mod that disabled the need to unlock with pin or password after a reboot first before Fingerprint will work
I know this has been disabled in some custom Roms I'm just wondering how to do it myself? Is there a flashable zip or something I have to remove?
I'm currently on superstock 2.8 but it does not have this feature
Thanks
This can be done using an Xposed module Fingerprint Enabler.
GrippingSphere said:
This can be done using an Xposed module Fingerprint Enabler.
Click to expand...
Click to collapse
Thanks but I'm looking for a mod that doesn't involve xposed
What are the main reasons/apps you guys rooted your pixel 2 for? And does anyone know if Xposed works on the pixel 2?
Clayton993 said:
What are the main reasons/apps you guys rooted your pixel 2 for? And does anyone know if Xposed works on the pixel 2?
Click to expand...
Click to collapse
Only for Adaway app!!!
ApoelEllhnwn said:
Only for Adaway app!!!
Click to expand...
Click to collapse
All I have done as well.
That's funny because that's the first thing I installed too. But I now have viper4android going for louder volumes.
EXKM to control the kernel and brighten up the colors some. Titanium Backup for backing apps. Custom Quick Settings to add a few custom tiles. I like adding one to get me into recovery/bootloader easily.
Xposed is not available yet for Oreo.
https://forum.xda-developers.com/showthread.php?p=74880035#post74880035
jb789 said:
Xposed is not available yet for Oreo.
https://forum.xda-developers.com/showthread.php?p=74880035#post74880035
Click to expand...
Click to collapse
Should have waited 10 mins before posting lol
https://forum.xda-developers.com/showpost.php?p=75128500&postcount=48
https://www.xda-developers.com/xposed-framework-for-android-oreo-beta/
Looks like beta is released. Who will be the first to try lol
Adaway and no tether check since I am on Verizon's grandfathered unlimited data plan.
welp I have successfully installed xposed SDK 27 on my Verizon pixel 2. rooted with magisk, TWRP, and bootloader unlocked obviously.
I installed the module from Magisk along with the modified xposed installer it provides. then went in to the xposed installer app, granted root, rebooted in to recovery and installed the magisk patched xposed zip with TWRP. booted back up, and xposed installer says xposed is installed.
however I can no longer pass safety net. is there a reason for this? doing some research it seems that systemless xposed will do this.
Sent from my Pixel 2 using Tapatalk
---------- Post added at 03:23 PM ---------- Previous post was at 03:21 PM ----------
bigwhat said:
welp I have successfully installed xposed SDK 27 on my Verizon pixel 2. rooted with magisk, TWRP, and bootloader unlocked obviously.
I installed the module from Magisk along with the modified xposed installer it provides. then went in to the xposed installer app, granted root, rebooted in to recovery and installed the magisk patched xposed zip with TWRP. booted back up, and xposed installer says xposed is installed.
however I can no longer pass safety net. is there a reason for this? doing some research it seems that systemless xposed will do this.
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
upon further use, the xposed app crashes quite frequently. I guess revo89 is aware of this issue.
Sent from my Pixel 2 using Tapatalk
bigwhat said:
welp I have successfully installed xposed SDK 27 on my Verizon pixel 2. rooted with magisk, TWRP, and bootloader unlocked obviously.
I installed the module from Magisk along with the modified xposed installer it provides. then went in to the xposed installer app, granted root, rebooted in to recovery and installed the magisk patched xposed zip with TWRP. booted back up, and xposed installer says xposed is installed.
however I can no longer pass safety net. is there a reason for this? doing some research it seems that systemless xposed will do this.
Sent from my Pixel 2 using Tapatalk
---------- Post added at 03:23 PM ---------- Previous post was at 03:21 PM ----------
upon further use, the xposed app crashes quite frequently. I guess revo89 is aware of this issue.
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
If you read the article you will see where they corrected it. If you use xposed at all you lose SafetyNet.
bigwhat said:
welp I have successfully installed xposed SDK 27 on my Verizon pixel 2. rooted with magisk, TWRP, and bootloader unlocked obviously.
I installed the module from Magisk along with the modified xposed installer it provides. then went in to the xposed installer app, granted root, rebooted in to recovery and installed the magisk patched xposed zip with TWRP. booted back up, and xposed installer says xposed is installed.
however I can no longer pass safety net. is there a reason for this? doing some research it seems that systemless xposed will do this.
Sent from my Pixel 2 using Tapatalk
---------- Post added at 03:23 PM ---------- Previous post was at 03:21 PM ----------
upon further use, the xposed app crashes quite frequently. I guess revo89 is aware of this issue.
Click to expand...
Click to collapse
Tis alternative Xposed installer is working better with fewer crashes. Use the test build posted towards the end of the thread.
https://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758/post75139549
I rooted for Adaway, Magisk Hide, Viper4Android, and Button Mapper so I can launch the flashlight with the screen off. It just doesn't seem to work very well. Any thoughts?
JRJ442 said:
EXKM to control the kernel and brighten up the colors some. Titanium Backup for backing apps. Custom Quick Settings to add a few custom tiles. I like adding one to get me into recovery/bootloader easily.
Click to expand...
Click to collapse
Which app did u use for custom quick settings?
infamousvincci said:
Which app did u use for custom quick settings?
Click to expand...
Click to collapse
There are a few different ones. But Custom Quick Settings is my favorite. https://play.google.com/store/apps/details?id=com.quinny898.app.customquicksettings. I added the bottom 4 in the screenshot. Double click the TWRP tile takes me straight into bootloader in case I want to fastboot a radio or something.
Custom Navigation Bar
Kernel Settings (low memory tweaks, etc)
Pixel 2 USB Audio Control (fixing the USB DAC)
TWRP / full backups
Titanium Backup
Substratum without Andromeda
Ad blocking
Device charging control (Magic Charging Switch)
Viper4Android (Optimizing device speakers)
Waiting on my Pixel still but will root for AdAway and Titanium so I can restore some apps settings.
PuffDaddy_d said:
I rooted for Adaway, Magisk Hide, Viper4Android, and Button Mapper so I can launch the flashlight with the screen off. It just doesn't seem to work very well. Any thoughts?
Click to expand...
Click to collapse
Viper4android here too. Though I've noticed it makes the audio in videos played via chrome browser on Facebook crackle and pop...
danbrown162 said:
Viper4android here too. Though I've noticed it makes the audio in videos played via chrome browser on Facebook crackle and pop...
Click to expand...
Click to collapse
I tried installing the Viper4Android for Magisk 15 module via the Magisk Manager app on my Pixel 2 XL, but all I got was the stupid "There's an internal problem with your device" message on boot, and the V4A app just says I/O error. What is the correct way to get it to work?
Ekitrak said:
I tried installing the Viper4Android for Magisk 15 module via the Magisk Manager app on my Pixel 2 XL, but all I got was the stupid "There's an internal problem with your device" message on boot, and the V4A app just says I/O error. What is the correct way to get it to work?
Click to expand...
Click to collapse
You're installing the wrong version.
Install this one on the list of modules in magisk and it will handle the rest.
Your are going to get some options in the installer so read your options.
BTW "internal problem" message is common. I get it also on every reboot. There's a mod you can do to hide that.