Related
I cannot grant apps root permission. The screen comes up, it does its normal countdown from 3 and then makes the allow button's text white. At this point, clicking it does nothing. It does not acknowledge a click there. If I press and hold my finger on allow, and slide it to deny, deny gets highlighted like I'm about to click it.
Any thoughts?
integramodder said:
I cannot grant apps root permission. The screen comes up, it does its normal countdown from 3 and then makes the allow button's text white. At this point, clicking it does nothing. It does not acknowledge a click there. If I press and hold my finger on allow, and slide it to deny, deny gets highlighted like I'm about to click it.
Any thoughts?
Click to expand...
Click to collapse
yea, flash the latest supersu via recovery http://download.chainfire.eu/452/SuperSU/UPDATE-SuperSU-v2.02.zip
It's probably because you're using Lux or something that uses an overlay.
ふかつどう
simms22 said:
yea, flash the latest supersu via recovery http://download.chainfire.eu/452/SuperSU/UPDATE-SuperSU-v2.02.zip
Click to expand...
Click to collapse
I installed supersu from the app store and was able to grant it root access after immediately rebooting. I tried this afterwords and get a flashing error.
Lethargy said:
It's probably because you're using Lux or something that uses an overlay.
ふかつどう
Click to expand...
Click to collapse
I'm using twilight, does that create problems?
integramodder said:
I'm using twilight, does that create problems?
Click to expand...
Click to collapse
Probably.
Many ROMs also provide built in changable autobrightness :/
Hello any help and advice will be greatly appreciated. I accidentally disabled system.ui with Package Disabler Pro and now lost touch on the phone. The touch screen is still active because when the phone dims it lights back up when I touch it. However, I can't access any applications, menu's and the volume keys also appear to be disabled. I also can't scroll between home screens. The power button does work, I have not tried to restart the phone as of yet.
Is there anything I can do to re-enable the system.ui from Package Disabler?
I think that if you wipe your phone by recovery it should be right even if you will lose all your data file. Try and wait for another solution... it could be you will save your data file
fabiok81 said:
I think that if you wipe your phone by recovery it should be right even if you will lose all your data file. Try and wait for another solution... it could be you will save your data file
Click to expand...
Click to collapse
I was able to fix it by going into safe mode and disabling the administrative permissions to package disabler pro. Thank you the thread can be locked.
???
chungdae said:
I was able to fix it by going into safe mode and disabling the administrative permissions to package disabler pro. Thank you the thread can be locked.
Click to expand...
Click to collapse
I just did the same thing. I'm in safe mode, how do you disable admin permissions for that app?
berfles said:
I just did the same thing. I'm in safe mode, how do you disable admin permissions for that app?
Click to expand...
Click to collapse
Settings > Lock screen and security > (scroll to bottom) Other security settings > Device Administrators > Toggle the switch for PDP
Hi all, I've had quite a few issues with Viper4android, including extreme battery drain (since installing my phone will drain from 80% to 0% overnight with no use), and inconsistent volume in various apps (Spotify only has about 60% volume output with random bursts to 100%).
How can I remove all of its components and revert back to stock? I'm guessing it's more involved than just reflashing the stock rom, perhaps I need radio files + others too
My phone is a Samsung s6 edge plus (SM-G928i).
Thank you all, and apologies if this is in the wrong place!
ReaperZ said:
Hi all, I've had quite a few issues with Viper4android, including extreme battery drain (since installing my phone will drain from 80% to 0% overnight with no use), and inconsistent volume in various apps (Spotify only has about 60% volume output with random bursts to 100%).
How can I remove all of its components and revert back to stock? I'm guessing it's more involved than just reflashing the stock rom, perhaps I need radio files + others too
My phone is a Samsung s6 edge plus (SM-G928i).
Thank you all, and apologies if this is in the wrong place!
Click to expand...
Click to collapse
Actually, its much easier than reflashing your ROM (though that would work fine too)
All you have to do is hit the menu button/3 dot icons>uninstall drivers>reboot. And you're done.
Freewander10 said:
Actually, its much easier than reflashing your ROM (though that would work fine too)
All you have to do is hit the menu button/3 dot icons>uninstall drivers>reboot. And you're done.
Click to expand...
Click to collapse
Thanks for the prompt reply! I'll give that a whirl
ReaperZ said:
Hi all, I've had quite a few issues with Viper4android, including extreme battery drain (since installing my phone will drain from 80% to 0% overnight with no use), and inconsistent volume in various apps (Spotify only has about 60% volume output with random bursts to 100%).
How can I remove all of its components and revert back to stock? I'm guessing it's more involved than just reflashing the stock rom, perhaps I need radio files + others too
My phone is a Samsung s6 edge plus (SM-G928i).
Thank you all, and apologies if this is in the wrong place!
Click to expand...
Click to collapse
This just removes the drivers, uninstalling the app after removing drivers and re-enabling your stock audio(if you had to remove/disable it), this should put you back to stock.
Freewander10 said:
Actually, its much easier than reflashing your ROM (though that would work fine too)
All you have to do is hit the menu button/3 dot icons>uninstall drivers>reboot. And you're done.
Click to expand...
Click to collapse
Sent from my SM-S903VL using Tapatalk
Droidriven said:
This just removes the drivers, uninstalling the app after removing drivers and re-enabling your stock audio(if you had to remove/disable it), this should put you back to stock.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Excuse my ignorance but could you tell me how to re-enable my stock audio? I get the feeling this was removed during the installation process
ReaperZ said:
Excuse my ignore but could you tell me how to re-enable my stock audio? I get the feeling this was removed during the installation process
Click to expand...
Click to collapse
By extracting a copy of the audioFX apk from your stock firmware
Or
By extracting it from a nandroid backup if you have one
Or
Find someone with your device and have them upload a copy of it.
Or
Find a copy with a Google search for:
"Audiofx.apk(or whatever the stock audio is called on your device) for (your model number and firmware version)
FYI, you would have had to manually remove or disable your stock audio yourself. It wouldn't have happened automatically, so if you yourself didn't remove/disable it then you probably don't have anything to worry about.
Sent from my SM-S903VL using Tapatalk
ReaperZ said:
Excuse my ignorance but could you tell me how to re-enable my stock audio? I get the feeling this was removed during the installation process
Click to expand...
Click to collapse
Did you flash V4A via recovery? Or did you install the app manually?
If you don't see the stock Equalizer in your app drawer then it was probably removed during installation of V4A (when done via recovery) but if it was installed manually then the equalizer app should still be installed/visible in your app drawer. All you have to do is open the app and toggle the on/off button.
If the app was removed though, you'll have to reflash your ROM to get it back.
NB 1. If stock EQ was already enabled, you might wanna disable it and give V4A another shot. As I've personally experienced issues with both of them enabled.
NB 2. Uninstalling the drivers practically kills the app. But you can go ahead and uninstall it as recommended by @Droidriven
Freewander10 said:
Did you flash V4A via recovery? Or did you install the app manually?
If you don't see the stock Equalizer in your app drawer then it was probably removed during installation of V4A (when done via recovery) but if it was installed manually then the equalizer app should still be installed/visible in your app drawer. All you have to do is open the app and toggle the on/off button.
If the app was removed though, you'll have to reflash your ROM to get it back.
NB 1. If stock EQ was already enabled, you might wanna disable it and give V4A another shot. As I've personally experienced issues with both of them enabled.
NB 2. Uninstalling the drivers practically kills the app. But you can go ahead and uninstall it as recommended by @Droidriven
Click to expand...
Click to collapse
I flashed a recovery file for it. So I might just take the easy route and reflash my rom I might give it another crack when I get my new phone in April / May!
Freewander10 said:
Did you flash V4A via recovery? Or did you install the app manually?
If you don't see the stock Equalizer in your app drawer then it was probably removed during installation of V4A (when done via recovery) but if it was installed manually then the equalizer app should still be installed/visible in your app drawer. All you have to do is open the app and toggle the on/off button.
If the app was removed though, you'll have to reflash your ROM to get it back.
NB 1. If stock EQ was already enabled, you might wanna disable it and give V4A another shot. As I've personally experienced issues with both of them enabled.
NB 2. Uninstalling the drivers practically kills the app. But you can go ahead and uninstall it as recommended by @Droidriven
Click to expand...
Click to collapse
Yep, my installations on all devices I've had have been via app which required me manually removing/disabling stock audio.
I've encountered installations on some devices that required using terminal emulator or adb shell to implement correctly, slightly tricky stuff that I don't remember the details for.
Sent from my SM-S903VL using Tapatalk
ReaperZ said:
I flashed a recovery file for it. So I might just take the easy route and reflash my rom I might give it another crack when I get my new phone in April / May!
Click to expand...
Click to collapse
I'm guessing your stock EQ was deleted then.
Just flash your ROM and you should be fine. Keep in mind though that any other additions/modifications you made to your system partition will be overwritten.
Uninstall Flashed App - Viper4Android
Hey folks,
I am new to xda and so this question might not be appropriate for this particular thread -- I don't know, I guess I'll take my chance. So, upon rooting my android device last week I went ahead and downloaded the Viper4Android audio enhancer as a zip, and installed it through the TWRP recovery terminal. This flashed the app on the phone drive. However, the Viper4Android driver is not installing properly and all my attempts to fix that are going in vain, thus I think the best solution is to uninstall the app and install a new package following a specific xda thread instructions to the letter. So my question is how do I uninstall a flashed app? I can't seem to find the app folder when the installation files are located. The app is present in my app menu. I am a root user and have directory apps like Root Explorer, Magisk Manager, BusyBox, RomToolbox etc. Btw, I've read most of this thread, and it mainly discusses the removal of the drivers. (Which I presume never installed in my phone anyways, as Viper4Android never worked -- hence why I am looking to uninstall the whole thing, and try anew). I have a Moto g5 plus.
How should I proceed? What's the best tool to uninstall a flashed Viper4Android App?
Any help would be much appreciated!
Thanks,
Sjbay93 said:
Hey folks,
I am new to xda and so this question might not be appropriate for this particular thread -- I don't know, I guess I'll take my chance. So, upon rooting my android device last week I went ahead and downloaded the Viper4Android audio enhancer as a zip, and installed it through the TWRP recovery terminal. This flashed the app on the phone drive. However, the Viper4Android driver is not installing properly and all my attempts to fix that are going in vain, thus I think the best solution is to uninstall the app and install a new package following a specific xda thread instructions to the letter. So my question is how do I uninstall a flashed app? I can't seem to find the app folder when the installation files are located. The app is present in my app menu. I am a root user and have directory apps like Root Explorer, Magisk Manager, BusyBox, RomToolbox etc. Btw, I've read most of this thread, and it mainly discusses the removal of the drivers. (Which I presume never installed in my phone anyways, as Viper4Android never worked -- hence why I am looking to uninstall the whole thing, and try anew). I have a Moto g5 plus.
How should I proceed? What's the best tool to uninstall a flashed Viper4Android App?
Any help would be much appreciated!
Thanks,
Click to expand...
Click to collapse
Did you solve it ?coz i have the same issue
I found a fix for a flashed Viper4Android
Just run the same package you used to install the V4A and it will remove it
Pretty simple.
hit the thanks button if I helped
MAST1999 said:
Just run the same package you used to install the V4A and it will remove it
Pretty simple.
hit the thanks button if I helped
Click to expand...
Click to collapse
Hi, this is my first xda post so there is no thanks button yet . But I'll go on ahead and say "Thank You". You solved my problem so easily.
Help!!!
Liens Sparks said:
Hi, this is my first xda post so there is no thanks button yet . But I'll go on ahead and say "Thank You". You solved my problem so easily.
Click to expand...
Click to collapse
Hello please what package did you install to remove the flashed viper android
I saw someone made a post on one way to remove the distortion from V4A, but that method breaks Bluetooth audio. This is how you fix it without breaking Bluetooth:
1. Reboot to recovery, mount Vendor
2. go to 'Advanced' -> 'File manager'
3. Go to "/Vendor/lib64/audiofx/" and rename/remove libvolumelistener.so
4. Go to "/Vendor/lib/audiofx/" and rename/remove libvolumelistener.so
5. Reboot to system, install V4A
And that's it
Edit:
You can also just use one of the older versions of V4A without needing a fix of any kind.
Couldn't you get the same result on a file manager with root permission without having to go through TWRP and reboot?
stewykam said:
Couldn't you get the same result on a file manager with root permission without having to go through TWRP and reboot?
Click to expand...
Click to collapse
I believe at least one of those is read only while the system is on. I remember trying that before and it wouldn't let me.
TiklMiPickles said:
I believe at least one of those is read only while the system is on. I remember trying that before and it wouldn't let me.
Click to expand...
Click to collapse
Ahh... Just wondering. Thanks for the info though ?
Anyone who tried it out and could confirm on this?
Edit: Tried to poke around in my phone but there's no "audiofx" instead there's "soundfx" which still houses the (lib)volumelistener.so
TiklMiPickles said:
I saw someone made a post on one way to remove the distortion from V4A, but that method breaks Bluetooth audio. This is how you fix it without breaking Bluetooth:
1. Reboot to recovery, mount System and Vendor
2. go to 'Advanced' -> 'File manager'
3. Go to "/System/lib64/audiofx/" and rename/remove volumelistener.so
4. Go to "/Vendor/lib/audiofx/" and rename/remove libvolumelistener.so
5. Reboot to system, install V4A
And that's it
Click to expand...
Click to collapse
Notification helper do this job systemless
However, I have a problem always with whatsapp voice notes crackling an stuttering sound if its mininized or force screen off
Dude, you are telling the same thing that I have posted (I'm sure you're talking about my post). You are asking users to manually edit volumelistener.so and I suggested users to flash the notification helper magisk module which does the exact same job automatically and most important, systemlessly. Is it really needed to create the same post with different heading and tagline? I'm sure you don't even know what I was talking about or didn't even try the module. Or else you would have realized you are not giving anyone any different solution. And if the method I told users breaks Bluetooth audio, then your method will do the exact same thing. Guess why. Because you are telling people to do the same thing, but manually. But I'm sure you didn't even bother to check the github of the particular magisk module I was talking about or didn't even try contacting the dev to see how exactly it works. Now the main question, what different solution did you give the users here?
---------- Post added at 08:53 PM ---------- Previous post was at 08:46 PM ----------
Dna10 said:
Anyone who tried it out and could confirm on this?
Edit: Tried to poke around in my phone but there's no "audiofx" instead there's "soundfx" which still houses the (lib)volumelistener.so
Click to expand...
Click to collapse
This is what happens when someone decides to make a post without having complete knowledge about what he is saying.
Dna10 said:
Anyone who tried it out and could confirm on this?
Edit: Tried to poke around in my phone but there's no "audiofx" instead there's "soundfx" which still houses the (lib)volumelistener.so
Click to expand...
Click to collapse
You have to mount those partitions in recovery. If you didn't manually mount them, a lot of files/folders won't show
Rowdyy Ronnie said:
Dude, you are telling the same thing that I have posted (I'm sure you're talking about my post). You are asking users to manually edit volumelistener.so and I suggested users to flash the notification helper magisk module which does the exact same job automatically and most important, systemlessly. Is it really needed to create the same post with different heading and tagline? I'm sure you don't even know what I was talking about or didn't even try the module. Or else you would have realized you are not giving anyone any different solution. And if the method I told users breaks Bluetooth audio, then your method will do the exact same thing. Guess why. Because you are telling people to do the same thing, but manually. But I'm sure you didn't even bother to check the github of the particular magisk module I was talking about or didn't even try contacting the dev to see how exactly it works. Now the main question, what different solution did you give the users here?
---------- Post added at 08:53 PM ---------- Previous post was at 08:46 PM ----------
This is what happens when someone decides to make a post without having complete knowledge about what he is saying.
Click to expand...
Click to collapse
No, you said to full on remove the audiofx folder rather than fix the specific files that cause the problem. The magisk also removes more files than necessary, which breaks Bluetooth audio.
It's funny you say I should know what I'm talking about when you are the one spreading false information. Before you go around throwing shade, you should have checked to see if I was right.
slimshouki said:
Notification helper do this job systemless
However, I have a problem always with whatsapp voice notes crackling an stuttering sound if its mininized or force screen off
Click to expand...
Click to collapse
The magisk module is definitely easier and let's you have the fix systemlessly, but I use Bluetooth audio all the time, and this is the only way I've found to have working notifications, Bluetooth and V4A.
Is the WhatsApp issue with the magisk module or fix I listed?
TiklMiPickles said:
The magisk module is definitely easier and let's you have the fix systemlessly, but I use Bluetooth audio all the time, and this is the only way I've found to have working notifications, Bluetooth and V4A.
Is the WhatsApp issue with the magisk module or fix I listed?
Click to expand...
Click to collapse
Both make same behaviour
Btw, Magisk module do not break BT audio
slimshouki said:
Both make same behaviour
Btw, Magisk module do not break BT audio
Click to expand...
Click to collapse
That's strange, I just double checked and it breaks it for me on Havoc-OS, it also did on Siberia and AEX when I used those. Maybe it has to do with the rom or vendor/firmware? I'm using Havoc and 8.12.20
TiklMiPickles said:
No, you said to full on remove the audiofx folder rather than fix the specific files that cause the problem. The magisk also removes more files than necessary, which breaks Bluetooth audio.
It's funny you say I should know what I'm talking about when you are the one spreading false information. Before you go around throwing shade, you should have checked to see if I was right.
Click to expand...
Click to collapse
Its funny how you accuse me of spreading false information without even digging into the module or atleast check the github. This is what happens when a randon user decides to show up once in a blue moon. Here is the github link of the module: https://github.com/Magisk-Modules-Repo/nhr
If you still don't understand how it works and what it does, then I feel sad for your noobness. And can you please list out what the module removes more than volumelistener.so? Don't just go on make claims, prove it first. And also, I have attached a screenshot of my post. Please show me where did I suggest people to remove audiofx folder (which is again wrong. There is no audiofx folder on vendor partition. Its called soundfx). And next time, if you decides to challenge someone who is more active on XDA than you, first upgrade your profile. I didn't get those thanks count just like that. It's the appreciation that I got from others upon helping them. So don't teach me what I am suggesting other users. First raise your profile standard.
slimshouki said:
Both make same behaviour
Btw, Magisk module do not break BT audio
Click to expand...
Click to collapse
Yeah because that magisk module does nothing other than removing volumelistener.so systemlessly when you choose volume down (that's why I have suggested users to choose volume down when prompted) . And if you choose volume up, it removes notification_helper from audio_effect cfgs.
And Viper will only break BT audio if you don't know how to make BT work with Viper.
Rowdyy Ronnie said:
Yeah because that magisk module does nothing but removes volumelistener.so systemlessly when you choose volume down. And if you choose volume up, it removes notification_helper from audio_effect cfgs.
And Viper will only break BT audio if you don't know how to make it work with Viper.
Click to expand...
Click to collapse
Do you have any idea about whatsapp voice notes issue?
slimshouki said:
Do you have any idea about whatsapp voice notes issue?
Click to expand...
Click to collapse
I have sent a message to Zack regarding the issue. Let see if he can address the issue. By the way, can you do one test. Remove the module and flash it again. This time when asked to choose between volume up and down, select up to remove notification helper and see if it fixes your problem.
Rowdyy Ronnie said:
I have sent a message to Zack regarding the issue. Let see if he can address the issue. By the way, can you do one test. Remove the module and flash it again. This time when asked to choose between volume up and down, select up to remove notification helper and see if it fixes your problem.
Click to expand...
Click to collapse
I did that as well.and same issue
Rowdyy Ronnie said:
Yeah because that magisk module does nothing other than removing volumelistener.so systemlessly when you choose volume down (that's why I have suggested users to choose volume down when prompted) . And if you choose volume up, it removes notification_helper from audio_effect cfgs.
And Viper will only break BT audio if you don't know how to make BT work with Viper.
Click to expand...
Click to collapse
After doing some testing, it seems to be rom specific. AEX and Havoc-OS, it breaks Bluetooth audio, but I tested on Resurrection Remix and Syberia and it doesn't.
Rowdyy Ronnie said:
Yeah because that magisk module does nothing other than removing volumelistener.so systemlessly when you choose volume down (that's why I have suggested users to choose volume down when prompted) . And if you choose volume up, it removes notification_helper from audio_effect cfgs.
And Viper will only break BT audio if you don't know how to make BT work with Viper.
Click to expand...
Click to collapse
I've managed to track down the issue. It isn't the notification remover module that is causing the issue, it's the Audio Modification Library, which the notification remover tells you to install if you have V4A installed. I have found this to be the case with AEX, Havoc-OS and MSM Xtended. Removing the AML module fixes the issue.
Not work viper and Dolby...havoc rom
Just a simple magisk module to make put the clock in the center.
NOTES
-----------------
This will cause issues with android auto!
Confirmed working on OOS 11.0.5.6.KB05AA (Global Rom)
Installation
-------------------
Pre-requisites
Rooted Oneplus 8T
Android 11 Stable
Magisk Manager
Installation instructions
1. Download the module from here:
Center Clock Module
Right Clock Module (Put The Clock on The Right)
2. Copy to your phones storage
3. Open Magisk and select the modules icon
4. Click "Install from storage"
5. Navigate to the downloaded folder and choose the zip inside.
6. Allow it to complete and then reboot.
Enjoy your center clock leave a thanks, let me know if it doesn't work, and I will try to help as much as I can.
Troubleshooting
------------------------------
Magisk module failure.
This works for any magisk module failure.
1. Power off your phone by holding the power button, then turn it back on.
2. As your phone gets to the bootloader warning screen, press and hold volume up and down and continue to hold until the phone shows the boot animation.
3. You'll boot to safe mode, simply reboot once more.
4. On the next boot all your magisk modules will be disabled, remove the problematic module, and re-enable the functional ones.
Original mod made by @Tulsadiver @dianoandr & @dladz for the op. I just pretty much copied and pasted his OP. So thanks for that
tested this module myself, absolutely massive thanks to them for this.
mine
mine as well
And the clock on the right is possible in the future?
maquina80 said:
And the clock on the right is possible in the future?
Click to expand...
Click to collapse
working on it....
Jed!Master said:
working on it....
Click to expand...
Click to collapse
Mention this: Only for OxygenOS to save users from SystemUI error
Tried. Works great! Thanks...
Small suggestions:
Can you reduce the padding from the top. Now the status bar occupies more space. Also can ss be included with hh:mm?
IAMAB said:
Tried. Works great! Thanks...
Small suggestions:
Can you reduce the padding from the top. Now the status bar occupies more space. Also can ss be included with hh:mm?
Click to expand...
Click to collapse
you talking about military hours with seconds on it!? I'll see what can be done as far as the padding goes...
Jed!Master said:
you talking about military hours with seconds on it!? I'll see what can be done as far as the padding goes...
Click to expand...
Click to collapse
Thanks mate.
Working great, thank you!
maquina80 said:
Click to expand...
Click to collapse
Done check it out. Enjoy
Can you please post change log?
IAMAB said:
Can you please post change log?
Click to expand...
Click to collapse
Bruh, someone else is doing the mod I'm just testing it to make sure it works. If there was a change log it would be up there til then flash if you like if not then I guess you won't flash it
Hello
Do you think it works on 11.0.6.8?
T.A.R.D.I.S. said:
Hello
Do you think it works on 11.0.6.8?
Click to expand...
Click to collapse
I'm not sure. But isn't the latest global 11.0.6.7? Correct me if I'm wrong
I tried the module on 11.0.6.7, looked like systemui kept crashing. Was able to disable the module.
-Michael_ said:
I tried the module on 11.0.6.7, looked like systemui kept crashing. Was able to disable the module.
Click to expand...
Click to collapse
And with 11.0.6.9, i've the same issue
-Michael_ said:
I tried the module on 11.0.6.7, looked like systemui kept crashing. Was able to disable the module.
Click to expand...
Click to collapse
Same with 11.0.6.8.KB05BA
Black screen after reboot.
@Jed!Master can you update this for the most recent version of oos?