I'm looking from an app that would:
1) Hide target app's icon, status bar and list of open applications
2) Have a disguised icon for the app itself, when I click it it asks for a password.
3) After entering the password, I get the list of apps that i've hidden
4) clicking an app lunches it
5) when screen locks the app disapear from list of open application and must enter password again to access that app (or perhaps time based).
Thanks.
Note: This might be a Samsung specific setting, I dunno.
I'm new to Android, so making a custom shortcut or script to do something like that is currently out of reach. According to a little research, there is a command (requires root) to toggle "Negative colors". I have tested it and it does work (even though it blocks the regular method from changing that setting until the device is restarted).
echo 1 > /sys/class/mdnie/mdnie/negative
What would be the most user-friendly application to make a shortcut to do that?
Or is there some other way to more quickly and easily toggle Settings > Accessibility > Negative colors?
Thanks.
This is killing me, and given the original thread is labeled "Lollipop", I thought i would start a more relevant thread subject so people can find it. The problem is in the new Samsung UI 2.1 update re-enables pop-up notifications, and the old method below doesn't "fix them" like it has since Lollipop. Here is the link with details to the original thread:
https://forum.xda-developers.com/android/general/howto-4-to-disable-heads-notifications-t3197660
My hopes are that someone knows how to disable these in UI 2.1. They just kill me when I am trying to type messages and a window keeps popping up over my work with incoming messages. Stupid and so GD iOS'ish it's ridiculous!! The answer before UI 2.1 was the simple command "adb shell settings put global heads_up_notifications_enabled 0" which Samsung must have changed the control variable. I am really hoping someone technical can tell us the new way to disable these annoying pop-ups again which we've been able to do so since Galaxy S5!
I've been asked by a lot of friends on how to disable those notifications which pop up on the top of your phone's screen. They are mistakenly called "pop-up notifications", but their real name is Heads-Up notifications and can be really useful, but sometimes they are extremely annoying. Specially if you need to use a button or something that is located on the top of the screen right when the notification appears. Some ROMs do allow to turn them off in the Settings, but most of them don't.
So in this thread (which is my first here on XDA) I'm gonna put all the info I gathered during my research about disabling the Heads-Up notifications. These methods will COMPLETELY disable them for all applications while MAINTAINING regular notifications in the status bar. All of these methods are free. Some require a rooted device and some don't.
1- ADB method (using your computer) [FREE]
Before trying this method, make sure you have installed Android ADB in your computer, that your phone is connected AND that you have "USB debugging" option enabled in the phone Settings.
If you don't have Android ADB, you can download it here: http://forum.xda-developers.com/show...php?p=48915118. If you have any questions concerning ADB and how to use it, take a look at this thread: http://forum.xda-developers.com/show....php?t=2225405
a) Open a terminal and check if the device is connected using the following command:
Code:
adb devices
b) You should see your phone on the list that appears. Now use the following command:
Code:
adb shell settings put global heads_up_notifications_enabled 0
c) Reboot your phone.
d) Done!
Click to expand...
Click to collapse
It looks like this is now available in the app and the adb hack isn't needed any longer. It would still be nice to apply a global default with this hack rather than changing each app individually. It's there, under "Message notifications" and is called "Show as Pop-up".
madfusker said:
It looks like this is now available in the app and the adb hack isn't needed any longer. It would still be nice to apply a global default with this hack rather than changing each app individually. It's there, under "Message notifications" and is called "Show as Pop-up".
Click to expand...
Click to collapse
Yeah! There's the option to change it.
For example on the Samsung Message app:
Go to notification settings, tap in "General Notifications" (tap on the letters, don´t tap the toggle switch) and then you would find the option "Show as pop-up".
You have to do it individually for each app, in FB messenger and Whatsapp is a little different, but you would find "show as pop-up" by tapping in the letters in each option in the notification settings.
Hope this help!
This option to change it manually for individual app has been there since Android 9 in Samsung. But that's a pain! Every time you install a new app you have to disable it. The option to completely disable heads up notification would be nice for the One UI 2.1
Hello. I made a script that runs AOD when we get a notification. Works on EMUI 11
We need the Tasker app: Link to google play
1. Download the Tasker app and give permissions via ADB: adb shell pm grant net.dinglisch.android.taskerm android.permission.WRITE_SECURE_SETTINGS
2. Turn on AOD in the system settings and in the Display mode tab: select Scheduled
3. Download AOD CONTROL
4. Start the Tasker app, click on the "house" icon (lower left corner) and select import project (import AOD_CONTROL.prj.xml)
5. Go to the "TASK" tab, hold down "START" until it is highlighted in orange and click on the "play" icon (upper right corner)
6. That's it, enjoy the AOD turning on with notifications on EMUI 11
Wojtekbass said:
Hello. I made a script that runs AOD when we get a notification. Works on EMUI 11
We need the Tasker app: Link to google play
1. Download the Tasker app and give permissions via ADB: adb shell pm grant net.dinglisch.android.taskerm android.permission.WRITE_SECURE_SETTINGS
2. Turn on AOD in the system settings and in the Display mode tab: select Scheduled
3. Download AOD CONTROL
4. Start the Tasker app, click on the "house" icon (lower left corner) and select import project (import AOD_CONTROL.prj.xml)
5. Go to the "TASK" tab, hold down "START" until it is highlighted in orange and click on the "play" icon (upper right corner)
6. That's it, enjoy the AOD turning on with notifications on EMUI 11
Click to expand...
Click to collapse
Did you do it? Can you give me a screenshot?
Screenshot of what? With Tasker?
As you know, in emui 11 the "aod switch 1" command does not work properly. The notification is shown only after the screen is turned on and off. I used a trick. I turned on the aod, and used the command "aod_scheduled_switch" which is responsible for switching between showing notifications all day and showing in certain hours. With the commands aod_start and stop (hour and minute) I set 00.00 which will cause that aod will not turn on until you receive a notification (command ui / notification in profile)
Wojtekbass said:
Screenshot of what? With Tasker?
Click to expand...
Click to collapse
How does tasker work? I'm asking because I don't know because I don't use it.
seacrab said:
How does tasker work? I'm asking because I don't know because I don't use it.
Click to expand...
Click to collapse
The script runs the system aod when you get an SMS, a message from the messenger etc.
Wojtekbass said:
The script runs the system aod when you get an SMS, a message from the messenger etc.
Click to expand...
Click to collapse
I'm going to give you the ADB command on the computer? Or does Tasker maneger?
Via the computer, I recommend Mininal ADB and Fastboot. Before entering the command, you need to enable USB debugging on your phone (Developer options): System & Updates -> Developer Options -> USB Debugging. If you do not have "Developer options" you have to go to About phone and click 9 times on "built number" then the "Developer Options" option will appear in System $ updates.
For beginners, I recommend: How to use Tasker to take Android to the next level article
Thank you, my friend. I will try. I hope I can
Wojtekbass said:
The script runs the system aod when you get an SMS, a message from the messenger etc.
Click to expand...
Click to collapse
Wojtekbass said:
The script runs the system aod when you get an SMS, a message from the messenger etc.
Click to expand...
Click to collapse
I ran a command with the ADB. Everything's normal. Aod is active and working the way you do. But it doesn't animate
What do you mean "But it doesn't animate"? Stock AOD has no animation ?! This script only runs aod when you get a notification
Wojtekbass said:
What do you mean "But it doesn't animate"? Stock AOD has no animation ?! This script only runs aod when you get a notification
Click to expand...
Click to collapse
Now I understand, my friend. If the Aod is closed or disabled, it allows it to run when the notification arrives. Thanks.
This is an alternative to the notification diode (which the Huawei P30 Pro does not have)
Is there a free alternative to Tasker app?
I exported this script as an application.
Grant permissions:
adb shell pm grant pl.aodnotify android.permission.WRITE_SECURE_SETTINGS
See if it works
Thanks for the effort but not working for me, maybe i did something wrong? I installed the apk and granted every permission i've been asked but can't see notifications.
Wojtekbass said:
I exported this script as an application.
Grant permissions:
adb shell pm grant pl.aodnotify android.permission.WRITE_SECURE_SETTINGS
See if it works
When typing command ans executing, thé following Line appears message
" Security exception: Package pl.aodnotify has not requested permission android.permission.WRITE.SECURE.SETRINGS "
Click to expand...
Click to collapse
@Wojtekbass
Plus I can't five any autorisation...nothing appears
Wojtekbass said:
I exported this script as an application.
Grant permissions:
adb shell pm grant pl.aodnotify android.permission.WRITE_SECURE_SETTINGS
See if it works
Click to expand...
Click to collapse
Finally i got it working BUT notification badge is always on so aod is working with badge of the aodnotify ap inside.
I disabled bubbles , badge, etc but Always aodnotify bubble informing no active profile (2on2 authorised)
ADB is needed.
Run
Code:
adb shell "settings get secure sysui_qs_tiles"
Save output of previous command
Prepare next command like this
Code:
adb shell "settings put secure sysui_qs_tiles '${previous command's output},nfc'"
Of course don't add ${}. It should look like this example:
Code:
adb shell "settings put secure sysui_qs_tiles 'wifi,bt,cell,rotation,airplane,dnd,location,custom(com.google.android.gms/.nearby.sharing.SharingTileService),flashlight,battery,hotspot,screenrecord,custom(com.dolby.daxappui/.DaxTileService),nfc'"
Now old AOSP NFC tile should be added to QS panel, but it may or may not work right now. It will appear in an unaccessible state and clicking on it may do nothing, but long pressing will open nfc settings.
We can sort of fix it. We need to open QS panel and move to the page with a newly added nfc tile. Then we run this command
Code:
adb shell "cmd statusbar click-tile nfc"
The SystemUI will crash and restart, but after that our nfc tile is usable. It still appears in an unaccessible state, but clicking on it will now successfully turn on nfc, and turn it off, depending on the situation. This UI bug is the only inconvenience. QS tile also reflects changes when nfc was enabled in settings or through Gpay right away, without any delay, so this tile works much better than any 3rd part one that relies on write_secure_setting permission.
After reboot, system_update etc. this tile may stop working, but if it doesn't disappear completely from QS panel, then redoing point 6 is necessary. If it is entirely gone, then the whole procedure must be repeated.
Bonus for future:
Sony have added it's custom nfc tile and also one for lte and sound in xperia 1 II (and as it turns out also 5 ii), that were used in other sony devices, for example xperia 5 with android 11 and a lot of older models. Sadly, event though they can be added using the same method, they can't be used, because they don't show up in QS panel, but they are saved in sysui_qs_tiles and are recognized by the system (behave like a ghost). Maybe Sony will do something about it in future update, since as it seems they were aware of the issue and started fixing it. I found about it from a one smart guy on 4pda here an here.
Maybe someone smarter than me, could hack up an app, that hooks up to those sony's custom services for enabling nfc, and make our own nfc tile, that actually works. I don't know if it is even possible. Porting com.sonyericsson.settings from xperia 5's android 11 firmware may also be some way out, but for sure out of the scope of my abilities.
They (sony) could also fix this built-in AOSP NFC QS tile. The code for it is literally publicly available, because it was fixed in GrapheneOS. If anyone from sony is reading this, please fix it ASAP, since it isn't anything difficult, but annoys every single time.