Q -how to disable heads-up, removing system apps, clear all notofications - One (M8) Q&A, Help & Troubleshooting

Hello there! i'm a fresh owner of an HTC M8 (european version 5.02 stock rooted with S-ON), i have a few issues,maybe some of you can help me:
1.Is there a way to disable the native lollipop heads-up?
Before i had a Galaxy S5, LG G3, and it worked with the SQlite editor procedure https://www.youtube.com/watch?v=It2WKA3XB-8, , but when installing SQlite in the M8 (grant supersu acces and all of that) it says that no database found (attached a screenshot below) , the same thing happens on my Moto G 2014, so i thought it can't be that i have the S-ON, i tried also changing SElinux to permissive but no luck
2.I can't uninstall system apps, i tried many system uninstaller apps, titanium backup, etc...after it says they are uninstalled, they appear back after a reboot, the only way i had to deal with this is freezing them...can it be the S-ON thing?
3.Is there any mod to add a 'clear all' button to the notification drawer without having to S-OFF?
THANKS

hauhauhau7 said:
Hello there! i'm a fresh owner of an HTC M8 (european version 5.02 stock rooted with S-ON), i have a few issues,maybe some of you can help me:
1.Is there a way to disable the native lollipop heads-up?
Before i had a Galaxy S5, LG G3, and it worked with the SQlite editor procedure https://www.youtube.com/watch?v=It2WKA3XB-8, , but when installing SQlite in the M8 (grant supersu acces and all of that) it says that no database found (attached a screenshot below) , the same thing happens on my Moto G 2014, so i thought it can't be that i have the S-ON, i tried also changing SElinux to permissive but no luck
2.I can't uninstall system apps, i tried many system uninstaller apps, titanium backup, etc...after it says they are uninstalled, they appear back after a reboot, the only way i had to deal with this is freezing them...can it be the S-ON thing?
3.Is there any mod to add a 'clear all' button to the notification drawer without having to S-OFF?
THANKS
Click to expand...
Click to collapse
Set SELinux to permissive.
Set /system to R/W
Clear all recents is available in ViperOneM8 through the HUB (I have the .zip file, but I'm not sure I should share it without permission). You can also set SELinux to permissive and /system to R/W through Venom Tweaks with a simple click.
Shameless ROM promotion activated.

xunholyx said:
Set SELinux to permissive.
Set /system to R/W
Clear all recents is available in ViperOneM8 through the HUB (I have the .zip file, but I'm not sure I should share it without permission). You can also set SELinux to permissive and /system to R/W through Venom Tweaks with a simple click.
Shameless ROM promotion activated.
Click to expand...
Click to collapse
thanks,will try it

Related

[Working] Viper4Android Bullhead (Full guide)

I'm not a dev so i cannot help you with bugs etc... I will not take any creds regard this program only wanted to share what i know and as always i'm not responsible for anything that happens to your devices..
Sorry for my bad English..
I've found a working method for V4A to work on Nexus 5X, and i know there are many threads about this...
I was looking around and found some solutions, but it seemed like there was not a specific thread about installing or was actually working.
It does not seem like you need permissive kernel for this to work (I've tried both Permissive and Enforcing, and both work).
Nexus 6's V4A have worked, but it it's missing audio focus sometimes. I've not got any FC. Dolby and Dolby Plus works too
I'm running:
ROM: ResurrectionRemix MM v5.6.4
Kernel: Jolla Kernel v6.0-Beta
Recovery: TWRP v3.0.0-0
What you will need:
-Nexus 5x (obviously)
Busybox (Recomended): meefik (Free)
Busybox: Stephen (Stericson) (Free)
Viper4Android (Recomended, but Doby is not included): Nexus 5 V4A
Viper4Android: Nexus 6 V4A
Install Method
1. First download Es File Explorer (or any other file explorer with root/system access).
2. Open File explorer and grant read write permission (in es file explorer you must go to left side panel and grant root access and then click on the text and choose "Mount R/W"). Then give "/", "/system" and "/vendor" r/w permission.
3. Afterwards you go to "/system/vendor/etc/" rename "audio_effects.conf" to "audio_effects.conf.bak" (in case something goes wrong or if you want to go back later. This is because V4A makes its own version of "audio_effects.conf". You will have to do it because in MM and V4A does not r/w for some reason.. It will then make its own file and it will work. If you want to go back to normal, just delete the "audio_effects.conf" V4A made and delete the ".bak" at the end of the original file. Also uninstall the driver from V4A, then use a system app remover to delete V4A. Then reboot).
4. Install the Busybox Version you prefer from Google Play Store. I'm currently running Busybox v1.24.1 (installed to "/system/xbin")
5. Go into recovery and take a backup (just to be on the safe side) before you flash the V4A of you liking, but I would suggest LolliViper (I will only link to the website not the file itself).
Then your done, if you have any questions or need help I can try my best. i cannot promise i can help tho..

How to disable guest access and multi-user support on Android Marshmallow?

Hi,
Is there a way to disable guest access and multi-user support on Android Marshmallow?
The adb commands and build.prop mods for Lollipop don't want to work on Marshmallow
I have a stock rom, root, twrp on my Nexus 5X
I am trying to figure this out also...
So, you can actually do this just with a root explorer. Go to the root system folder, and edit the build.prop (using ES text editor or whatever), adding a line at the end:
fw.show_multiuserui=0
Save the build.prop, boot to recovery, wipe dalvik and cache, and reboot. This worked for me on a Dell Venue 8 7840, running 5.1.1 stock and rooted and also on a Oneplus X, running RR 6.0.1 (based on CM13).
Pan Skrzetuski said:
So, you can actually do this just with a root explorer. Go to the root system folder, and edit the build.prop (using ES text editor or whatever), adding a line at the end:
fw.show_multiuserui=0
Save the build.prop, boot to recovery, wipe dalvik and cache, and reboot. This worked for me on a Dell Venue 8 7840, running 5.1.1 stock and rooted and also on a Oneplus X, running RR 6.0.1 (based on CM13).
Click to expand...
Click to collapse
This disables multi user, but the annoying icon is still displayed on the lock screen and in the notification shade. Anyone know how to remove these?

Can't get Viper4Android working on my M8 running GPE 6.0 ROM

I'm struggling with installing Viper4Android on my device.
I tried installing using either the apk from the original thread (http://forum.xda-developers.com/showthread.php?t=2191223). It install successfully but I keep getting a driver install prompt, after installing the driver and rebooting.
Things I already tried without success:
- Installed BusyBox with BusyBox app (https://play.google.com/store/apps/details?id=ru.meefik.busybox)
- Setting the SELinux mode to permissive using SELinuxModeChanger app (http://forum.xda-developers.com/showthread.php?t=2524485)
- Setting the SELinux mode to permissive using flashable permissive.zip
- Installing the apk from the Material design Viper4Android thread (http://forum.xda-developers.com/android/software/app-material-viper4android-2-3-4-0u-t3190352)
- Flashing the .zip from the same thread.
I'm currently running Android 6.0 GPE, flashable version (http://forum.xda-developers.com/showthread.php?t=2708589)
Root access is granted through SuperSU, so no problem on that matter I suppose.
2. With a File Manager(Solid Explorer Recommended) locate " /system/etc/htc_audio_effects.conf" and rename "htc_audio_effects.conf" to "htc_audio_effects.bak" (Renaming this file will make it inactive but while keeping it backed up just in case this doesn't work for you, however it appears this file is not needed as no negative effects occur, and this should fix V4A.)
3. Reboot Device.
And if this doesn't work I thin you should grant storage permission for V4A under settings. I hope I can help you!
Duccibreeezy said:
2. With a File Manager(Solid Explorer Recommended) locate " /system/etc/htc_audio_effects.conf" and rename "htc_audio_effects.conf" to "htc_audio_effects.bak" (Renaming this file will make it inactive but while keeping it backed up just in case this doesn't work for you, however it appears this file is not needed as no negative effects occur, and this should fix V4A.)
3. Reboot Device.
And if this doesn't work I thin you should grant storage permission for V4A under settings. I hope I can help you!
Click to expand...
Click to collapse
Thanks mate!! This worked for me.
Thanks for ur help

[DEBLOAT] Wileyfox Debloater - Quickly clean your Nougat-based Wileyfox device!

Hey all!
As you all know, Wileyfox has started rolling out Nougat for their devices, starting with the codenamed marmite family (Swift 2, 2 Plus and 2X models). With this new update, Wileyfox has also included a bunch of BLOATWARE I personally NEVER expected from them. I mean, I didn't request ads in my launcher, and why do I need to forcefully use Truecaller dialer instead of the cleaner, AOSP-based one? That's why I've created this Wileyfox Debloater tool, to keep the system apps as clean and stockish as possible.
App removals included:
- AndroidPay
- BasicDreams
- BookmarkProvider
- Google Books
- Chrome
- CMFileManager
- Drive
- Duo
- Gmail
- GooglePrintRecommendationService
- GoogleTTS
- Hangouts
- Keep
- Maps
- Google Music
- News and Weather
- PhotoTable
- talkback
- Google Videos
- WFChromeCustomization
- Youtube
- Contacts
- FoxHole
- Mms
- SnapdragonGallery
- TrueCaller
- All bundled-apps from /system/vendor/bundled-app
- Possibly more in the future.
(Note: All the moved Google Apps were removed for the sole reason that they can also be downloaded from the Play Store.)
App additons / other features included:
- Google Contacts, in replacement of the half-dummy, prebundled Contacts app (which was missing link with the Dialer).
- Google Dialer, in replacement of TrueCaller.
- Google Messages, in replacement of Wileyfox Mms app.
- AOSP's Launcher3, in replacement of FoxHole (Wileyfox's Launcher).
- Framework and permission files for Google Dialer to work.
- Small tweaks in the build.prop, including drop of min processors to work from 2 to 1, and rise of maximum processors to work from 4 to 8, as well as increasing the Android compiler default amount of processors from 4 to 6.
- Possibly more in the future, too.
Warning:
Code:
Your device's system partition [B]IS NOW [COLOR="Red"]TAMPERED[/COLOR][/B]. This implies two things:
1. You WILL NOT BE ABLE TO INSTALL ANY NEWER OTAs ON IT.
(To learn how to properly upgrade your device, kindly check post [URL="https://forum.xda-developers.com/swift-2/development/debloat-wileyfox-debloater-quickly-t3587536/post72258926#post72258926"]#25[/URL])
2. Your device MAY NOT BE ABLE TO BOOT UNLESS YOU DISABLE DM-VERITY.
(And to do so, the quickest way is to [B]install[/B] [B][URL="https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445"]Magisk[/URL][/B].)
Downloads:
- For the latest Wileyfox Swift 2, Swift 2 Plus and Swift 2X firmware: Wileyfox-TOS118C-Debloater--11-05-17.zip
(For version TOS089 check Wileyfox-TOS089-Debloater--10-04-17.zip)
- For more Wileyfox devices, coming soon
Installation instructions:
1. Update your device to Nougat
2. Unlock your bootloader and flash TWRP
3. Download the latest version zip
4. Boot into TWRP, make a backup if you wish (although is highly recommended), choose Install and locate and flash the ZIP.
5. Reboot and enjoy!
6. Are you missing missed calls notifications? Is the caller ID always showed as a number instead of a contact name during phone calls? Check post #16!
Uninstall instructions:
Check post #6
Enjoy, and don't forget to leave a Thanks if you loved it!
I'm also dissapointed that the OS is far from the pure AOSP.
But it is possible to tweak it without losing the future OTAs:
1. Install google launcher, google messenger
2. Install google phone from apk mirror - this version is working on my phone - http://www.apkmirror.com/apk/google...-7-0-140861421-nonnexus-android-apk-download/
3. Deactivate truecaller, duo, news, ... - but be careful, some apps are needed for the system and remember to activate all apps before the OTA update...
rivierakid said:
I'm also dissapointed that the OS is far from the pure AOSP.
But it is possible to tweak it without losing the future OTAs:
1. Install google launcher, google messenger
2. Install google phone from apk mirror - this version is working on my phone - http://www.apkmirror.com/apk/google...-7-0-140861421-nonnexus-android-apk-download/
3. Deactivate truecaller, duo, news, ... - but be careful, some apps are needed for the system and remember to activate all apps before the OTA update...
Click to expand...
Click to collapse
That is also a possibility but:
1. Launcher3 conflicts with the already installed launcher, so it's impossible to get that out of the way
2. I got latest version working here using the required libraries (extracted from a Pixel), so yeah, probably both possibilities are just fine
And for the third one, just wanted to say there's no need to reactivate them (if you manage to deactivate them, ofc), and, all of the packages the script moves are stored in a safe place (/system/__bloat), so they can be restored from there
I don't remember if I had a problem with a previous OTA update for Wileyfox, but I was not able to install an update without reactivation a disabled app.
I'm not sure...
You could select a default launcher and the phone has really enough RAM, so I think it is not necessary to remove the FoxHole from the system.
But anyway, nice work! You could provide an uninstall instructions - if it is really possible. I hope that there can be an OTA update in the future...
The final solution for this is LineageOS, if they provide the source
Excellent! Thanks for providing this...such a stupid shame that Wileyfox decided to do this. I'm just hoping that they now release their sources so that we can start working on a proper release of Lineage!
*Edit: Nice! https://bitbucket.org/wileyfox/kernel-wileyfox-msm8937/commits/all*
JT
rivierakid said:
But anyway, nice work! You could provide an uninstall instructions - if it is really possible. I hope that there can be an OTA update in the future...
Click to expand...
Click to collapse
Of course. The debloater doesn't delete any of your system apps, but move them to /system/__bloat. There you'll find 3 folders, the app, the priv-app and the vendor one, just cut and paste them back to /system and the deleted apps will come back. Also, don't forget to remove the framework files and permissions the debloater installs, such as /system/framework/com.google.android.dialer.support.jar and /system/etc/permissions/com.google.android.dialer.support.xml. You can also remove the the GoogleContacts, GoogleDialer, GoogleMessages and Launcher3 folders from /system/priv-app, and revert the build.prop tweaks (lines 164 and 165, change values from 1 and 8 to 2 and 4, line 196, change value from 6 to 4).
Reverting all of that, your system will go back as it came with the Nougat OTA.
Hello,
thanks for your effort to the community.
I have a question.
How do I install this? I've tried it with twrp but everytime I install twrp my device won't boot.
To repair this I flashed the newest "system.img".
But I can't replace my stock recovery.
linuxct said:
Of course. The debloater doesn't delete any of your system apps, but move them to /system/__bloat. There you'll find 3 folders, the app, the priv-app and the vendor one, just cut and paste them back to /system and the deleted apps will come back. Also, don't forget to remove the framework files and permissions the debloater installs, such as /system/framework/com.google.android.dialer.support.jar and /system/etc/permissions/com.google.android.dialer.support.xml. You can also remove the the GoogleContacts, GoogleDialer, GoogleMessages and Launcher3 folders from /system/priv-app, and revert the build.prop tweaks (lines 164 and 165, change values from 1 and 8 to 2 and 4, line 196, change value from 6 to 4).
Reverting all of that, your system will go back as it came with the Nougat OTA.
Click to expand...
Click to collapse
Any chance of updating debloater to change the UI colour scheme from orange back to blue?
JT
MCPoppa said:
I have a question.
How do I install this? I've tried it with twrp but everytime I install twrp my device won't boot.
To repair this I flashed the newest "system.img".
But I can't replace my stock recovery.
Click to expand...
Click to collapse
Try downloading version 3.0.2-0 from TWRP download website, and flash it via the command
Code:
fastboot flash recovery <name-of-the-file>.IMG
Replacing name of the file for the actual filename of it. To enter fastboot mode, you should see a warning when you boot up your device. Hit any volume keys, and, using them, choose the fastboot mode and select it with the power key. Now you should be able to use the fastboot commands.
jdtanner said:
Any chance of updating debloater to change the UI colour scheme from orange back to blue?
JT
Click to expand...
Click to collapse
I'm already working on it... But it'll surely require substratum, which probably won't work out of the box just by flashing it from the recovery. I'm looking for solutions
linuxct said:
Try downloading version 3.0.2-0 from TWRP download website, and flash it via the command
Code:
fastboot flash recovery <name-of-the-file>.IMG
Replacing name of the file for the actual filename of it. To enter fastboot mode, you should see a warning when you boot up your device. Hit any volume keys, and, using them, choose the fastboot mode and select it with the power key. Now you should be able to use the fastboot commands.
I'm already working on it... But it'll surely require substratum, which probably won't work out of the box just by flashing it from the recovery. I'm looking for solutions
Click to expand...
Click to collapse
Everytime i installed twrp i got stuck in a bootloop :/
MCPoppa said:
Everytime i installed twrp i got stuck in a bootloop :/
Click to expand...
Click to collapse
Okay, can you try doing "fastboot boot" and the name of the image instead of flashing it? It will avoid bootloops, since it just boots to the image. Keep me posted, please.
linuxct said:
Okay, can you try doing "fastboot boot" and the name of the image instead of flashing it? It will avoid bootloops, since it just boots to the image. Keep me posted, please.
Click to expand...
Click to collapse
Still doesnt let me boot up after I installed your debloat zip.
Everytime I install or boot to twrp 3.1.0 or 3.0.2 for marmite i get a boot loop and a "dm-verity .." screen.
I've tried different versions of twrp and different methods like "fastboot flash" and "fastboot boot" but everytime I flash something it gets stuck on booting up.
When I was on Marshmello I had this "dm-verity" message too but I could modify my system as I wanted and it booted up everytime, i had TWRP, your Speakermod, Magisk Mask etc installed no problem.
I think it has something todo with the update to Nougat.
How did you bring it run on your device?
MCPoppa said:
Still doesnt let me boot up after I installed your debloat zip.
Everytime I install or boot to twrp 3.1.0 or 3.0.2 for marmite i get a boot loop and a "dm-verity .." screen.
I've tried different versions of twrp and different methods like "fastboot flash" and "fastboot boot" but everytime I flash something it gets stuck on booting up.
When I was on Marshmello I had this "dm-verity" message too but I could modify my system as I wanted and it booted up everytime, i had TWRP, your Speakermod, Magisk Mask etc installed no problem.
I think it has something todo with the update to Nougat.
How did you bring it run on your device?
Click to expand...
Click to collapse
I explained it last night here, but I also stated it in the OP:
linuxct said:
Warning:
Code:
Your device's system partition [B]IS NOW [COLOR="Red"]TAMPERED[/COLOR][/B]. This implies two things:
1. You WILL NOT BE ABLE TO INSTALL ANY NEWER OTAs ON IT.
[B]2. Your device MAY NOT BE ABLE TO BOOT UNLESS YOU DISABLE DM-VERITY.[/B]
(And to do so, the quickest way is to [B]install[/B] [B][URL="https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445"]Magisk[/URL][/B].)
Click to expand...
Click to collapse
linuxct said:
I explained it last night here, but I also stated it in the OP:
Click to expand...
Click to collapse
Thanks, i've installed magisk mask again and the message didn't appeared.
I've also flashed your debloater and everything works fine.
Can I now flash TWRP or do I have to boot it up via fastboot everytime?
MCPoppa said:
Thanks, i've installed magisk mask again and the message didn't appeared.
I've also flashed your debloater and everything works fine.
Can I now flash TWRP or do I have to boot it up via fastboot everytime?
Click to expand...
Click to collapse
Try flashing it to your recovery partition, my guess is that now that DM-verity is disabled everything should work fine
Cheers!
Quick update post after two days of usage, yesterday I noticed I didn't receive any notifications on missed calls, and that the caller ID always showed as a number although I had it added as a contact.
I realised that I didn't have any "Phone" app chosen as default in Android settings, so I was missing those notifications until I opened the Google Dialer app.
In case it happens to you, to sort it out go into Settings > Apps, then hit the gear in the top right corner and make sure you've a config similar to this one (Launcher3, Google's "Phone" and Google's "Messages" chosen as default Home, Phone and Messaging apps).
I hope this is clear for everyone, since it's not something I can fix on my side/requires the user to do the change
I have TWRP, SuperSU, and Magisk. Marshmallow boots with no problem, but I get the dm-verity screen on boot with the message "dm-verity is not started in enforcing mode".
Does this mean dm-verity is disabled because it is not enforcing, or do I need to do something to stop the whole dm-verity screen appearing before I can successfully upgrade, debloater, and boot Nougat?
Ianharding said:
I have TWRP, SuperSU, and Magisk. Marshmallow boots with no problem, but I get the dm-verity screen on boot with the message "dm-verity is not started in enforcing mode".
Does this mean dm-verity is disabled because it is not enforcing, or do I need to do something to stop the whole dm-verity screen appearing before I can successfully upgrade, debloater, and boot Nougat?
Click to expand...
Click to collapse
Firsts things first: After heavily modding the system like you did on Marshmallow, make sure not to update your device through the regular OTA but using a recovery image like the ones posted in this device's forum.
For magisk: are you sure you flashed it correctly? Magisk disables that dmverity message you are mentioning, so maybe you installed an old version or wasn't properly flashed.
My advice is: download everything: the recovery image, the debloater and Magisk. Boot into TWRP, wipe EVERYTHING if possible, including Data cache dalvik cache and system partitions. Once done, flash the recovery image zip, and right after that, without rebooting, flash the debloater and magisk. Reboot and everything should work perfectly
If I use this to debloat my WileyFox does it mean I won't be able to use Android Pay?
digidude512 said:
If I use this to debloat my WileyFox does it mean I won't be able to use Android Pay?
Click to expand...
Click to collapse
As soon as you root any Marshmallow/Nougat phone Android Pay will not work, according to this article
I have never used Android Pay so it doesn't make any difference to me. My phone is much better now that I have debloated it. I also installed Evie Launcher and Halo Browser, both small minimalist apps and everything is really smooth.
Instead of a Debloater, could the Stock ROM not be debloated and rezipped as a custom 'Lite' version?

Missing SuperSU app icon

I recently (2 days ago) fastboot installed the 8.1 update on my Pixel XL 128 (kept data). Following that, I rooted using TWRP and flashable zips; AROMA installer, SuperSU v2.82, and suhide v1.08. After all of this, I went in to confirm root access by using root explorer and by opening the Super SU app. So far everything is good.
Today, I noticed that my Super SU icon is missing from the folder that I have placed it in (I'm using Nova Launcher). No big deal, I'll just search for it and place it back in the folder. No, SuperSU isn't found when I do a search. I switched over to pixel launcher and went into the app drawer, and the icon is missing from there as well. Google play shows that SuperSU Pro is installed, it is in my list of apps in the settings menu, and root checker confirms that it is installed and that my phone is still rooted and passes safetynet check.
I rebooted my phone thinking that may restore the icon, and not only did the Super SU icon not reappear, but I'm now missing another app icon. I haven't figured out yet which app it is that's disappeared after the reboot.
I've tried uninstalling and reinstalling SuperSU Pro through the Play store and the icon still doesn't show up. When I uninstall SuperSU Pro, and try to install SuperSU, it will not install.
Anyone have any idea as to why this is happening or how to fix it?
mntnbkr said:
I recently (2 days ago) fastboot installed the 8.1 update on my Pixel XL 128 (kept data). Following that, I rooted using TWRP and flashable zips; AROMA installer, SuperSU v2.82, and suhide v1.08. After all of this, I went in to confirm root access by using root explorer and by opening the Super SU app. So far everything is good.
Today, I noticed that my Super SU icon is missing from the folder that I have placed it in (I'm using Nova Launcher). No big deal, I'll just search for it and place it back in the folder. No, SuperSU isn't found when I do a search. I switched over to pixel launcher and went into the app drawer, and the icon is missing from there as well. Google play shows that SuperSU Pro is installed, it is in my list of apps in the settings menu, and root checker confirms that it is installed and that my phone is still rooted and passes safetynet check.
I rebooted my phone thinking that may restore the icon, and not only did the Super SU icon not reappear, but I'm now missing another app icon. I haven't figured out yet which app it is that's disappeared after the reboot.
I've tried uninstalling and reinstalling SuperSU Pro through the Play store and the icon still doesn't show up. When I uninstall SuperSU Pro, and try to install SuperSU, it will not install.
Anyone have any idea as to why this is happening or how to fix it?
Click to expand...
Click to collapse
Use a file explorer to extract SuperSU, open the common folder, install SuperSU.apk
Homeboy76 said:
Use a file explorer to extract SuperSU, open the common folder, install SuperSU.apk
Click to expand...
Click to collapse
As I mentioned, Super SU Pro is installed, there just isn't an icon for it. I'm also missing another (yet to be determined) icon.
mntnbkr said:
As I mentioned, Super SU Pro is installed, there just isn't an icon for it. I'm also missing another (yet to be determined) icon.
Click to expand...
Click to collapse
Is it possible that you have SuperSu and suhide (you mentioned you installed it) hidden? Try toggling your volume rocker - Vol UP, then Vol Down - 3 times in succession within 3 sec. That should unhide the apps if they are hidden.
Good luck.
S
sb1893 said:
Is it possible that you have SuperSu and suhide (you mentioned you installed it) hidden? Try toggling your volume rocker - Vol UP, then Vol Down - 3 times in succession within 3 sec. That should unhide the apps if they are hidden.
Good luck.
S
Click to expand...
Click to collapse
I can vouch for this possibility. My wife managed to hide her SuperSU icon (and SU Hide icon) this way. I still have no idea how she managed to complete the up down sequence needed, and I went on a wild goose chase until an XDA user suggested that it might have happened.
sb1893 said:
Is it possible that you have SuperSu and suhide (you mentioned you installed it) hidden? Try toggling your volume rocker - Vol UP, then Vol Down - 3 times in succession within 3 sec. That should unhide the apps if they are hidden.
Good luck.
S
Click to expand...
Click to collapse
You sir, are my new hero. I had no idea that this was even a thing. I just toggled the volume rocker and the icons magically appeared! Where is the setting that determines which apps will be hidden when you toggle the vol buttons... and how long has this feature been around?
mntnbkr said:
You sir, are my new hero. I had no idea that this was even a thing. I just toggled the volume rocker and the icons magically appeared! Where is the setting that determines which apps will be hidden when you toggle the vol buttons... and how long has this feature been around?
Click to expand...
Click to collapse
Glad it worked. Truth be told - I learned about it in much the same way. It is a core feature of suhide and the "hide apps" functions seems to survive some upgrades, reroots, reflashes of SuperSu/suhide. One of the first steps I take before sideloading a new OTA is to "unhide" SuperSu / suhide so that I am able to see them in the app drawer once I have completed the upgrade process. Once I have verified everything, including root and hiding of root is working properly, I then toggle the volume rocker to hide them again. (I need this for a few apps that detect root by looking for the presence of these apps.)
The volume rocker command and other capabilities of suhide are covered in detail in the suhide thread (linked below) and are also described in the "About" tab within suhide.
https://forum.xda-developers.com/apps/supersu/suhide-lite-t3653855/page2
Good luck!
sb1893 said:
Glad it worked. Truth be told - I learned about it in much the same way. It is a core feature of suhide and the "hide apps" functions seems to survive some upgrades, reroots, reflashes of SuperSu/suhide. One of the first steps I take before sideloading a new OTA is to "unhide" SuperSu / suhide so that I am able to see them in the app drawer once I have completed the upgrade process. Once I have verified everything, including root and hiding of root is working properly, I then toggle the volume rocker to hide them again. (I need this for a few apps that detect root by looking for the presence of these apps.)
The volume rocker command and other capabilities of suhide are covered in detail in the suhide thread (linked below) and are also described in the "About" tab within suhide.
https://forum.xda-developers.com/apps/supersu/suhide-lite-t3653855/page2
Good luck!
Click to expand...
Click to collapse
Great info. Thanks again!
sb1893 said:
Is it possible that you have SuperSu and suhide (you mentioned you installed it) hidden? Try toggling your volume rocker - Vol UP, then Vol Down - 3 times in succession within 3 sec. That should unhide the apps if they are hidden.
Good luck.
S
Click to expand...
Click to collapse
There is an update for suhide, it's 109 version and there is a new version of SuperSU Sr 5 version. When you ticking off the app in suhide, don't hide suhide you only need to turn it blue which is hide from other apps, do the same with the SuperSU app as well. The rest is simple. You will be certified, pass safety net and you will be set to go.

Categories

Resources