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?
First, this is my setup.
Running stock rooted with elemental x kernel.
OS - Jan Patch
Magisk - v16.2
Magisk Manager - v5.6.4
Elemental X- P2-1.05
Twrp - latest
I did search as best I can on these forums but found just bits and pieces and still no solution. If there is one mods please delete and I'll search again.
So my issue is at some point I could no longer overwrite files to my system. I do have a modified host that I did awhile back and that sticks. But I can no longer overwrite that and others. I have es file pro and it can't do it. When I check permissions for system to be rw it switches back to ro when I go back into permissions. I have root browser by jrummy and that lets me change files but it doesn't stick after reboot. I also un checked the radio button avb/dm-verity in Magisk Manager but it too doesn't stick when I back out of app and go back in. Did I not do something correctly when installing Magisk? In Magisk thread it says your /system will only be modified if root is installed to /system. But doesn't explain how to do that. Sorry for long post, hopefully someone can point me in the right direction.
Edit:
Solved.
I got it, I think those two radio buttons are settings for when you update magisk or patch boot. They were both selected by default, so I unchecked them and installed magisk v16.0 through the manager and now I can write to system. Es File Explorer still not working but at least the other file manager is. Mods you can delete this thread.
I found a permanent fix for the Bluetooth battery drain bug on stock 7.1, the last n108 release.
Root is required for this fix.
First, go to developer settings and enable Bluetooth hci Snoop log. Reboot. Then disable the Bluetooth hci log. Reboot.
Next, using a root file explorer (I used ES file explorer), navigate to /system/etc/Bluetooth/
Open bt_stack.conf
Near the top is "BtSnoopConfigFromFile=false"
Change it to true, then make sure the following two lines are set to false.
BtSnoopLogOutput=false
BtSnoopExtDump=false
Save the file and reboot.
After some browsing on the nextbit forums, someone had identified that the Bluetooth Snoop hci log was being written to the root directory of /sdcard/, causing significant battery drain. Their solution was to toggle the Bluetooth log on in developer settings, reboot, turn it off, then reboot again. It would always turn itself back on though. This prevents that.
(Bluetooth hci log is a file where android literally records all Bluetooth traffic information, which as you might imagine is CPU and I/o intensive. Normally used by devs for troubleshooting).
I decided to go back to stock due to constant bugs and freezes with the lineage 14.1 builds. Battery life has even been a little better on stock, with rock solid stability.
This prevents the battery drain aspect, but the battery settings still has a reporting error that attributes much more drain to Bluetooth than it should. I'm still getting 3-4hrs screen on time with lots of Bluetooth use after this fix. Better battery stats will provide accurate drain stats.
This is excellent information - thanks for posting - however, I get stuck when trying to save the proposed changes to bt_stack.conf; the file is read-only and I cannot figure out how to change it to allow me to save the changes. How did you do that on the stock ROM?
Bleser said:
This is excellent information - thanks for posting - however, I get stuck when trying to save the proposed changes to bt_stack.conf; the file is read-only and I cannot figure out how to change it to allow me to save the changes. How did you do that on the stock ROM?
Click to expand...
Click to collapse
Is your phone rooted? I used ES File explorer with "root mode" enabled. You can only make changes to the file with a root elevated program. There is also solid file explorer and root file explorer as other options that may work. I should have mentioned root is required.
I believe ES file explorer changes the permission automatically when in root mode, to allow changes. Other apps may require manually changing the permissions of the BT config file.
I did also run 'hide magisk manager" in the magisk settings.
boxes said:
Is your phone rooted? I used ES File explorer with "root mode" enabled. You can only make changes to the file with a root elevated program. There is also solid file explorer and root file explorer as other options that may work. I should have mentioned root is required.
I believe ES file explorer changes the permission automatically when in root mode, to allow changes. Other apps may require manually changing the permissions of the BT config file.
Click to expand...
Click to collapse
Hi @boxes,
No, it is not rooted. I will try ES File explorer. Thanks!
Bleser said:
Hi @boxes,
No, it is not rooted. I will try ES File explorer. Thanks!
Click to expand...
Click to collapse
You will need to be rooted to do this. If you root with magisk, then you can still pass the safetynet check.
Rooting the robin is very easy luckily.
Follow these steps to unlock the bootloader and flash TWRP.
https://forum.xda-developers.com/nextbit-robin/general/guide-install-twrp-root-robin-t3334171
(Use this TWRP rather than the one on that thread-)
https://forum.xda-developers.com/ne...recovery-twrp-3-0-0-0-touch-recovery-t3334152
Then download magisk from here-
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Also download the magisk manager APK. Flash magisk from TWRP then install magisk manger in android.
boxes said:
Is your phone rooted? I used ES File explorer with "root mode" enabled. You can only make changes to the file with a root elevated program. There is also solid file explorer and root file explorer as other options that may work. I should have mentioned root is required.
I believe ES file explorer changes the permission automatically when in root mode, to allow changes. Other apps may require manually changing the permissions of the BT config file.
Click to expand...
Click to collapse
boxes said:
You will need to be rooted to do this. If you root with magisk, then you can still pass the safetynet check.
Rooting the robin is very easy luckily.
Follow these steps to unlock the bootloader and flash TWRP.
https://forum.xda-developers.com/nextbit-robin/general/guide-install-twrp-root-robin-t3334171
(Use this TWRP rather than the one on that thread-)
https://forum.xda-developers.com/ne...recovery-twrp-3-0-0-0-touch-recovery-t3334152
Then download magisk from here-
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Also download the magisk manager APK. Flash magisk from TWRP then install magisk manger in android.
Click to expand...
Click to collapse
Thanks again for your help!
boxes said:
I found a permanent fix for the Bluetooth battery drain bug on stock 7.1, the last n108 release.
Root is required for this fix.
First, go to developer settings and enable Bluetooth hci Snoop log. Reboot. Then disable the Bluetooth hci log. Reboot.
Next, using a root file explorer (I used ES file explorer), navigate to /system/etc/Bluetooth/
Open bt_stack.conf
Near the top is "BtSnoopConfigFromFile=false"
Change it to true, then make sure the following two lines are set to false.
BtSnoopLogOutput=false
BtSnoopExtDump=false
Save the file and reboot.
After some browsing on the nextbit forums, someone had identified that the Bluetooth Snoop hci log was being written to the root directory of /sdcard/, causing significant battery drain. Their solution was to toggle the Bluetooth log on in developer settings, reboot, turn it off, then reboot again. It would always turn itself back on though. This prevents that.
(Bluetooth hci log is a file where android literally records all Bluetooth traffic information, which as you might imagine is CPU and I/o intensive. Normally used by devs for troubleshooting).
I decided to go back to stock due to constant bugs and freezes with the lineage 14.1 builds. Battery life has even been a little better on stock, with rock solid stability.
This prevents the battery drain aspect, but the battery settings still has a reporting error that attributes much more drain to Bluetooth than it should. I'm still getting 3-4hrs screen on time with lots of Bluetooth use after this fix. Better battery stats will provide accurate drain stats.
For extra security you can change the permissions of the .conf file to read only for all groups.
Click to expand...
Click to collapse
Bless you! I should have looked into this earlier but never got around to it, having just left Bluetooth off except when charging. Will see if I can do a bind mount over the file with Magisk so I can leave the system image read-only.
---------- Post added 3rd July 2018 at 12:00 AM ---------- Previous post was 2nd July 2018 at 11:57 PM ----------
In the process of looking this up, I discovered a Magisk module to fix the Bluetooth config problem already exists:
https://forum.xda-developers.com/apps/magisk/module-disable-bluetooth-hci-snoop-log-t3680223
You do not need to edit your system image, just install Magisk and then use Magisk Manager to install this module.
iscaela said:
Bless you! I should have looked into this earlier but never got around to it, having just left Bluetooth off except when charging. Will see if I can do a bind mount over the file with Magisk so I can leave the system image read-only.
---------- Post added 3rd July 2018 at 12:00 AM ---------- Previous post was 2nd July 2018 at 11:57 PM ----------
In the process of looking this up, I discovered a Magisk module to fix the Bluetooth config problem already exists:
https://forum.xda-developers.com/apps/magisk/module-disable-bluetooth-hci-snoop-log-t3680223
You do not need to edit your system image, just install Magisk and then use Magisk Manager to install this module.
Click to expand...
Click to collapse
I tried that and it didn't work for me, I replied to the thread a while back. At least with magisk v16.
Are you concerned about passing the safetynet check? I ran the check in magisk manager and passed, both ctsProfile:true and basicIntegrity:true
I'm still able to download apps from the play store that block rooted/modified devices. Magisk is masking the changes perhaps.
edit: I tinkered with magisk, enabling "hide magisk manager" and now it wont pass safetynet check. So I reinstalled magisk manager. This time I didnt "hide magisk manager", but I enabled "magisk core only mode" and checked the box for "Magisk Hide" and "Systemless Hosts" (I use adaway), now it passes the safetynet check again.
boxes said:
I tried that and it didn't work for me, I replied to the thread a while back. At least with magisk v16.
Are you concerned about passing the safetynet check? I ran the check in magisk manager and passed, both ctsProfile:true and basicIntegrity:true
I'm still able to download apps from the play store that block rooted/modified devices. Magisk is masking the changes perhaps.
Click to expand...
Click to collapse
After installing the module, I had to turn "Enable Bluetooth HCI snoop log" on in "Developer options", reboot, and turn it back off again, but it seems to have worked and /sdcard/btsnoop_hci.log stopped growing in size.
The file was also not recreated after I deleted it and rebooted one more time. So I think the extra steps are necessary whether using the module or editing the original file in the system image (there's lingering config data which could in theory be handled in the module as well if ).
boxes said:
edit: I tinkered with magisk, enabling "hide magisk manager" and now it wont pass safetynet check. So I reinstalled magisk manager. This time I didnt "hide magisk manager", but I enabled "magisk core only mode" and checked the box for "Magisk Hide" and "Systemless Hosts" (I use adaway), now it passes the safetynet check again.
Click to expand...
Click to collapse
I've had Magisk installed since I first got the phone and except for a brief period in mid 2017, SafetyNet checks have been passing with "Magisk Hide" alone, without selecting "core only mode" (which disables modules). I'm also using "Systemless hosts" for AdAway.
@iscaela
How long has it been since you did that? Just the process of enabling/disabling in dev options would fix it for a day or two in my experience.
boxes said:
@iscaela
How long has it been since you did that? Just the process of enabling/disabling in dev options would fix it for a day or two in my experience.
Click to expand...
Click to collapse
Just over 12 hours today. I've rebooted twice recently and it's stayed the same. I doubt there's a time component to it reverting, the config loading is pretty simple.
Interestingly, bluedroid is still listening on port 8872 as documented at https://android.googlesource.com/platform/external/bluetooth/bluedroid/+/master/doc/btsnoop_net.md but isn't producing any traces.
iscaela said:
Just over 12 hours today. I've rebooted twice recently and it's stayed the same. I doubt there's a time component to it reverting, the config loading is pretty simple.
Interestingly, bluedroid is still listening on port 8872 as documented at https://android.googlesource.com/platform/external/bluetooth/bluedroid/+/master/doc/btsnoop_net.md but isn't producing any traces.
Click to expand...
Click to collapse
So the most recent reboot did enable the setting and created /sdcard/btsnoop_hci.log again. The reason appears to be the module leaves BtSnoopConfigFromFile=false.
I'm going to update the module to edit this and report back.
Looks like the updated Magisk module works, I've posted it to the other thread:
https://forum.xda-developers.com/ap...bluetooth-hci-snoop-log-t3680223/post76987430
I was trying to boost the headphone volume on my pixel 2 xl but I'm getting permission error on every root browser/explorer
is there a fix to this the phone is rooted latest security patch android pie November update
magiskv17,3
and can this problem be fixed by flashing the edited file with twrp?
file location /Vendor/etc/mixer_paths_tavil_taimen.xml
hovo222 said:
I was trying to boost the headphone volume on my pixel 2 xl but I'm getting permission error on every root browser/explorer
is there a fix to this the phone is rooted latest security patch android pie November update
magiskv17,3
and can this problem be fixed by flashing the edited file with twrp?
file location /Vendor/etc/mixer_paths_tavil_taimen.xml
Click to expand...
Click to collapse
I posted this on another thread and had worked for them.
What has worked for me in the past was to uncheck the two radio buttons on magisk main screen. {The two advanced items} then I would press the install button right below. After doing that I would be able to change files in directories I once couldn't. Worth a shot
Fe Mike said:
I posted this on another thread and had worked for them.
What has worked for me in the past was to uncheck the two radio buttons on magisk main screen. {The two advanced items} then I would press the install button right below. After doing that I would be able to change files in directories I once couldn't. Worth a shot
Click to expand...
Click to collapse
Worked, thank you :laugh:
Pixel 2 in root how I do read and write permission? Exactly please
oraned said:
Pixel 2 in root how I do read and write permission? Exactly please
Click to expand...
Click to collapse
If you are rooted then any root explorer should have the ability to read and write. If you have magisk manager installed and your root explorer is not writing them try this.
Open magisk manager and uncheck the two radio buttons on magisk main screen. {The two advanced items} then I would press the install button right below. After doing that I would be able to change files in directories I once couldn't.
oraned said:
Pixel 2 in root how I do read and write permission? Exactly please
Click to expand...
Click to collapse
If you mean how to change read/write permissions, you would use a good root file explorer like Solid Explorer, or Root Explorer. :good:
Fe Mike said:
If you are rooted then any root explorer should have the ability to read and write. If you have magisk manager installed and your root explorer is not writing them try this.
Open magisk manager and uncheck the two radio buttons on magisk main screen. {The two advanced items} then I would press the install button right below. After doing that I would be able to change files in directories I once couldn't.
Click to expand...
Click to collapse
U can help how to do thet pls
What part? The rooted or magisk? Do you have the Verizon variant? If so none of this will work
@Fe Mike: I believe he has an unlocked device and also believe he is rooted since he was asking about sound mods in one of the Viper4Android threads in the P2XL forum here. At the same time, he apparently expects people to hold his hand while he muddles through the process, as you appear to be discovering for yourself. Help him, but at some point he'll have to go it alone.