Database Develop

[TIPS] Hide the notification manager screen

Hello
If you want to hide the notification manager screen, in order to show batery status, sound volume.... when you hit taskbar
delete the key HKEY_LOCAL_MACHINE\Services\NOTIFICATIONMANAGER
other tips here : http://htc-touch-diamond.forumactif.../astuces-diverses-diamond-2-t12018.htm#145527 (french forum)

It is recommeded to backup the registery setting before you delete it.
Good tip!

when i try to delet the key it says "access denied" - how comes?

Maybe is it in use?

may be. but how not use it? even if i disable touch flo it is still active.

woelv said:
may be. but how not use it? even if i disable touch flo it is still active.
Click to expand...
Click to collapse
Just delete every item under
HKEY_LOCAL_MACHINE\Services\NOTIFICATIONMANAGER

this is exactly what i tried when i got the hint "no access"

I started my D2 in safemode (with Safemode or PocketPlus) and then i could successfully delete this registry branch.

After doing that I noticed that the green light is not blinking anymore when there is a SMS or MMS....

rexriver said:
After doing that I noticed that the green light is not blinking anymore when there is a SMS or MMS....
Click to expand...
Click to collapse
Great! No more disturbing for your quality life.

I don't know, if my device states (or stated) new sms or mms by blinking lights because I never looked at it.

Any programs out there that can modify the LEDs apart from xperiatweak?

As title says, because my xperiatweak keeps crashig..

Illuminara or something similar in name to that. Allows you to change the leds and apply patterns to events etc.
Used it and it worked well.

http://forum.xda-developers.com/showthread.php?t=501001
Just search...

How to make hte messaging LEDs change to rainbow pulses?
I dont know hwo to use illumeneria.,.

I would like to know this aswell.
Change new SMS to rainbow pulses (same as when you turn on the phone), would be cool.
Is it possible with Illumineria?

Light Manager Compatiblity

Someone reported that after updated to Android 5.1.1. Missed call and Gmail LED notification does not work anymore in both normal mode and alternating mode. They are always blinking the default blue color LED.
https://play.google.com/store/apps/details?id=com.koo.lightmanager
Is there anyone having the same problem as well?

mckoo said:
Someone reported that after updated to Android 5.1.1. Missed call and Gmail LED notification does not work anymore in both normal mode and alternating mode. They are always blinking the default blue color LED.
https://play.google.com/store/apps/details?id=com.koo.lightmanager
Is there anyone having the same problem as well?
Click to expand...
Click to collapse
Yup, all the regular system apps controlled by the Samsung setting are always blue. It still blinks, but I can only get my added AndChat app notification to blink the orange that I have it set to. And when my phone goes into prority only at night, all notifications including my added apps are the default solid blue, doesn't even blink. Hope we get it fixed, I absolutely hate not being able to customize my LEDs.
I wonder if any apps work better with root? I am also stuck waiting on a new root method since I updated to 5.1.1 before reading about the bootloader lock.

meh3884 said:
Yup, all the regular system apps controlled by the Samsung setting are always blue. It still blinks, but I can only get my added AndChat app notification to blink the orange that I have it set to. And when my phone goes into prority only at night, all notifications including my added apps are the default solid blue, doesn't even blink. Hope we get it fixed, I absolutely hate not being able to customize my LEDs.
I wonder if any apps work better with root? I am also stuck waiting on a new root method since I updated to 5.1.1 before reading about the bootloader lock.
Click to expand...
Click to collapse
Thanks for the info. Does Light Manager work when you disable "LED indicator" in the system settings?
Have you tried enabling Priority for Light Manager? See if when you phone goes into priority only at night, will your added apps LED still working with Light Manager?

mckoo said:
Thanks for the info. Does Light Manager work when you disable "LED indicator" in the system settings?
Have you tried enabling Priority for Light Manager? See if when you phone goes into priority only at night, will your added apps LED still working with Light Manager?
Click to expand...
Click to collapse
I will try setting light manager to priority and let you know what happens.
Also, as a note, my orange AndChat notification stopped working today. It's just a solid blue all the time. I haven't changed anything - seems Samsung's LED controller is finicky about its control. Email, etc still blinks default blue.
edit: Also, forgot to answer - No, the LED doesn't work at all if I disable the LED indicator in the system settings.

meh3884 said:
I will try setting light manager to priority and let you know what happens.
Also, as a note, my orange AndChat notification stopped working today. It's just a solid blue all the time. I haven't changed anything - seems Samsung's LED controller is finicky about its control. Email, etc still blinks default blue.
edit: Also, forgot to answer - No, the LED doesn't work at all if I disable the LED indicator in the system settings.
Click to expand...
Click to collapse
Thanks for helping in testing.
I just thought of something. Is your device rooted? I'm not sure if it will work if you put Light Manager to be as system app as well?

I'm not rooted and having the same issue. I hope there is a fix for this.
Whatsapp appears to be flashing with my colors but the default system email is still lighting blue (i don't want ANY light for email) but there doesn't appear to be a way to turn it off

mckoo said:
Thanks for helping in testing.
I just thought of something. Is your device rooted? I'm not sure if it will work if you put Light Manager to be as system app as well?
Click to expand...
Click to collapse
No problem, happy to help.
1. No change on setting to priority mode except that Gmail, etc continued to blink blue instead of solid blue. AndChat continues to be solid blue. I have no idea at one point the orange light I had it set to worked, but it's been all solid blue since yesterday morning.
2. No root, there is not currently a root method for android 5.1.1 on the S6 due to the exploit being patched. We are waiting for a new root method, hopefully soon!

Custom Color Issues
Does anyone else have an issue where the custom colors dont flash the color you chose? I got it to work once but after that it just blinks to the closest default colors... e.i. i want it to flash a celeste color but it it just blinks blue.. any help is appreciated

blv7 said:
Does anyone else have an issue where the custom colors dont flash the color you chose? I got it to work once but after that it just blinks to the closest default colors... e.i. i want it to flash a celeste color but it it just blinks blue.. any help is appreciated
Click to expand...
Click to collapse
Yes, I have mentioned above having that problem. My added app briefly showed the colour I chose, but now everything - added and system apps - show the default blue, either blinking or solid.
Other LED manager apps are also not working. Looks like Samsung made some kind of change in 5.1.1. For now we'll have to sit tight as we are out of luck.

meh3884 said:
No problem, happy to help.
1. No change on setting to priority mode except that Gmail, etc continued to blink blue instead of solid blue. AndChat continues to be solid blue. I have no idea at one point the orange light I had it set to worked, but it's been all solid blue since yesterday morning.
2. No root, there is not currently a root method for android 5.1.1 on the S6 due to the exploit being patched. We are waiting for a new root method, hopefully soon!
Click to expand...
Click to collapse
Too bad that there is no root method currently.
Please check if the notification access for Light Manager is enabled? I heard that some users complaining that the notification access for Light Manager will get disabled automatically when the device is rebooted.
Also try using alternating mode, I think AndChat will not work in normal mode.

blv7 said:
Does anyone else have an issue where the custom colors dont flash the color you chose? I got it to work once but after that it just blinks to the closest default colors... e.i. i want it to flash a celeste color but it it just blinks blue.. any help is appreciated
Click to expand...
Click to collapse
What app notification are you referring to?

Does anyone with the S6 Edge on 5.1.1 have light manager working for missed calls, had it working on led blinker before the 5.1.1 update.

mckoo said:
Too bad that there is no root method currently.
Please check if the notification access for Light Manager is enabled? I heard that some users complaining that the notification access for Light Manager will get disabled automatically when the device is rebooted.
Also try using alternating mode, I think AndChat will not work in normal mode.
Click to expand...
Click to collapse
Yes, light manager has notification access. I think this is why some notifications are able to blink. The system default is a solid blue light. There is no issue with my phone on 5.1.1 causing the notification access to be turned off after reboot.

I rooted my S6 today on 5.1.1. I still can't get Light Manager or Light Flow to work properly even with root. Light Manager some notifications blink blue, but others stay solid blue - no reaction to custom colour changes. Light Flow will not show the LED *at all* even with "root mode" activated.

meh3884 said:
I rooted my S6 today on 5.1.1. I still can't get Light Manager or Light Flow to work properly even with root. Light Manager some notifications blink blue, but others stay solid blue - no reaction to custom colour changes. Light Flow will not show the LED *at all* even with "root mode" activated.
Click to expand...
Click to collapse
Thanks for the info.
Since your device is rooted, could you please try putting Light Manager app as system app see if it works?

Still not working on s6 edge?

I am on Android 5.1.1 and I am one of the ones reporting that Light Manager no longer works.
Today, though, I did something that may provide a clue to the problem. Perhaps McKoo is reading...
I just installed the latest version of Light Manager Pro on my S6 Edge. I then configured it to my preferences and rebooted the phone. As soon as the phone came up, I used my PC to send myself a text message. Now here is the important part. As soon as the text message was received, and before the alert notification took place, my LED started blinking according to the color and speed I configured in Light Manager for SMS messages (orange, every two seconds). However, as soon as the notification process alerted me to the text message (which I am assuming is a Samsung / Android process), my LED flashing reverted back to the standard blue flash every 5 seconds.
I sure hope the information above is helpful because I really like the Light Manager application. It provided the functionality that Android and Samsung forgot!

Thanks for the explanation.
The LED notification on Samsung devices used to be the first come first serve basis. However from Touchwiz 5.1.1. onwards, like what you have noticed, it had changed to last come first serve basis. Actually right after the Samsung / Android process generates the standard blue LED, Light Manager will generate the orange LED one more time but at this time Light Manager can no longer override the standard blue LED (I am not sure why as well).
If you are using alternating mode, Light Manager will keep on generating LED notification according to the "Interval Of Change" that you have set. However this only happens when you have more than one notification. Could you try generating the 2nd notification (Let say generating a Gmail LED notification after you have generated an SMS LED notification), see if it can override the standard blue LED?
Suddenly I have an idea, could you please go to Light Manager > Advanced Settings > Enable Logging and enable it? Then do the testing above and send me the generated log.txt file which will be generated in your internal storage under a folder named "LightManager". I suspected that maybe Touchwiz 5.1.1 drops / ignores all the notification access detection related to system apps. I might be able to know by analyzing the log.txt file.
Thank you.

mckoo said:
Thanks for the info.
Since your device is rooted, could you please try putting Light Manager app as system app see if it works?
Click to expand...
Click to collapse
Sorry for the delay. I set the app as a system app via Titanium Backup, set it up again, and have no change in behaviour unfortunately.
Sent from my SM-G920T using XDA Free mobile app

Have also a rooted 5.1.1 so I can test all necessary to make app working

Screen off with timed prox sensor

I've looked for a solution but none of them work.
I'm looking for a simple Profile to turn the screen off when the proximity sensor is covered, which is simple.
But I don't want the profile to trigger if the sensor is just briefly covered so I want to add a task to only trigger the profile if the sensor is covered for 5 seconds.
I've tried adding a Wait task but that doesn't work. According to the tutorials I've seen, a Wait task should work. When I pass my hand over the sensor instead of turning off immediately, it waits 5 seconds then turns off.
I'm looking for similar functionality to the F-Droid app F2L.
Thanks.

i'm in the same, what i do is when the sensor and no light switch time of screen to 15s. I set time of screen to 2m.
Using your way you have to make 2 profiles 1 with sensor on off variable, the second with a entry task with wait 5 seconds and screen off and exit task to stop the first one. the second profile must be activate when the variable of the first one is set to true (or what ever you want)
Enviado desde mi SM-G900M mediante Tapatalk

Spookymyo said:
I've looked for a solution but none of them work.
I'm looking for a simple Profile to turn the screen off when the proximity sensor is covered, which is simple.
But I don't want the profile to trigger if the sensor is just briefly covered so I want to add a task to only trigger the profile if the sensor is covered for 5 seconds.
I've tried adding a Wait task but that doesn't work. According to the tutorials I've seen, a Wait task should work. When I pass my hand over the sensor instead of turning off immediately, it waits 5 seconds then turns off.
I'm looking for similar functionality to the F-Droid app F2L.
Thanks.
Click to expand...
Click to collapse
Proximity Sensor.prj.xml
Download the project and import it.
A code shell is used to power off the screen, so root is needed. If you don't have root, then use System Lock tasker action.
I hope it's working as you want.
EDIT: Ops, someone already replied. I was writing this post.

#Henkate said:
Proximity Sensor.prj.xml
Download the project and import it.
A code shell is used to power off the screen, so root is needed. If you don't have root, then use System Lock tasker action.
I hope it's working as you want.
EDIT: Ops, someone already replied. I was writing this post.
Click to expand...
Click to collapse
Thanks for the reply. I downloaded your XML project from media fire but when I tried to import it I got an error saying it failed to import data. I checked the XML in a text editor and noticed a lot of text strings with "media fire" and "Google". I don't think that should be the case.
Edit: Nevermind. I opened it in a different browser and it downloaded the proper file. I'll test it and see if it's what I was taking about.
Edit 2: That's money dude! That's so much easier than I thought. I had 4 different tasks and a few different variables. Thanks a ton!
Edit 3: I added a notification sound when the screen actually turns off. That way I'm not wondering if it did or not.
I noticed that when I turn the screen back on the flash text (Please wait 5 seconds) always displays. Does this mean that your project is always polling the proximity sensor even when the screen is off? In Tasker preferences, under the monitor tab, I have the proximity setting at No.

Spookymyo said:
Thanks for the reply. I downloaded your XML project from media fire but when I tried to import it I got an error saying it failed to import data. I checked the XML in a text editor and noticed a lot of text strings with "media fire" and "Google". I don't think that should be the case.
Edit: Nevermind. I opened it in a different browser and it downloaded the proper file. I'll test it and see if it's what I was taking about.
Edit 2: That's money dude! That's so much easier than I thought. I had 4 different tasks and a few different variables. Thanks a ton!
Edit 3: I added a notification sound when the screen actually turns off. That way I'm not wondering if it did or not.
I noticed that when I turn the screen back on the flash text (Please wait 5 seconds) always displays. Does this mean that your project is always polling the proximity sensor even when the screen is off? In Tasker preferences, under the monitor tab, I have the proximity setting at No.
Click to expand...
Click to collapse
I'm glad I helped you. I'm still a noob
I've tried again and it seems that you're right about the flash text. And I've figured out why: because when screen was going on after it was off, the variable %PROX still had value 1 (so it was triggering the profile), but then it was going to 0. I think that's it. In any case, I've made some changed and now that problem is gone.
I've made following changes:
- added two profiles to know if the screen is locked or unlocked. When it's unlocked, it also means that the screen is on
- added a state not call any, so the screen won't turn off when you're in a call (because when you have the phone at ear, the proximity sensor stays on, so we don't want our profile gets triggered that time)
- added a state display on at proximity profile which play with the %PROX variable, so the proximity sensor won't get triggered when you have the phone in pocket for example. It will trigger only if the screen is on
NEW version here
PS: let me know how it goes with the battery drain , if is minor or major. I'm just curious because i didn't use a profile with proximity sensor and I don't need this one.

#Henkate said:
I'm glad I helped you. I'm still a noob
I've tried again and it seems that you're right about the flash text. And I've figured out why: because when screen was going on after it was off, the variable %PROX still had value 1 (so it was triggering the profile), but then it was going to 0. I think that's it. In any case, I've made some changed and now that problem is gone.
I've made following changes:
- added two profiles to know if the screen is locked or unlocked. When it's unlocked, it also means that the screen is on
- added a state not call any, so the screen won't turn off when you're in a call (because when you have the phone at ear, the proximity sensor stays on, so we don't want our profile gets triggered that time)
- added a state display on at proximity profile which play with the %PROX variable, so the proximity sensor won't get triggered when you have the phone in pocket for example. It will trigger only if the screen is on
NEW version here
PS: let me know how it goes with the battery drain , if is minor or major. I'm just curious because i didn't use a profile with proximity sensor and I don't need this one.
Click to expand...
Click to collapse
This version didn't work at all. It won't display the flash text. And it won't turn off the screen, it only dims. I'll just modify the first one with some of your new code.

Spookymyo said:
This version didn't work at all. It won't display the flash text. And it won't turn off the screen, it only dims. I'll just modify the first one with some of your new code.
Click to expand...
Click to collapse
Huh, it worked for me.
Do like you said.

I tried something a little different with the exception of using two profiles.
Profile one: Cover Closed
State-Proximity Sensor -> Task: Screen Off(Wait; one sec.,Turn Off; Dim off, Lock on)
Profile two: Cover open
State-Not Proximity Sensor -> Task: Screen On(Stop; Task Screen Off, Turn On; Block Time five hundred)

Tasker keep screen on Android 12 issue

Hi,
I have set up the display timeout option with the settings below but it doesn't seem to work. I am using an oppo phone on Android 12.
Create a new task. Select the “+” button. Select “Display” followed by “Display timeout” Select the time span you want to set and then save. Now select “Profile” and click “+” and then “Applications” Mark the applications for which you want to activate this Tasker profile.
Then I open the app but after 15 seconds the screen turns off which is the default device screen timeout.
Is there no way to override this? Maybe get tasker to somehow keep interacting with the screen to keep it on?
I've tried this on a few apps and have got two different messages..
One says screen will stay on for 15 seconds which is the system screen time out.
Other says tasker will keep screen on but still times out after 15 seconds.
Really want this to work as some apps like games I don't want timing out after 15 seconds and I don't want to increase the system time to couple of mins for every app.

Hi,
I have the same problem on my OPPO A74 with Android 11 ((ColorOS Version V11.1). It seems impossible to create a task to change the screen time out; not in connection with a profile, shortcut or widget. The amazing thing, though - when you test the task in Tasker it works perfectly fine.
Media Volume, I think, also doesn't work. Other app connected profiles like autorotate or display brightness work well. I wanted to test more but I can't find the time.
I really miss the screen timeout though. It drains the battery too much to set it constantly to 15 minutes or so, but for some apps less simply is annoying.
The developer created some apk to help with some OPPO related problems, unfortunately, it didn't help with this one (sorry, I can't remember exactly what it was).
A kind of workaround: Once you've activated the Developer Options an your phone you can enable "Keep screen on while charging". When you need longer screen time, just plug into a charger.
But using a Tasker Profile would be much nicer.
Hope somebody knows a better trick.

Not sure if following could help your situation ( only for your gaming situation )
Create a new Profile, choose > apps > add your game apps in it. click left top arrow when finisning add gaming apps.
Tasker will pops-up task list > creat new task > Screen > Turn on.
** when above profile is complete , click the task when you are still in Profile list. Hold the task, it should pops-up with option exit task. Choose this as exit task.
Play around to see if this profile is working when gaming apps in foreground, screen never turn off.
EDIT: Try first not move the task as exit task. ( make the task as normal entry task )

eeeemc said:
Not sure if following could help your situation ( only for your gaming situation )
Create a new Profile, choose > apps > add your game apps in it. click left top arrow when finisning add gaming apps.
Tasker will pops-up task list > creat new task > Screen > Turn on.
** when above profile is complete , click the task when you are still in Profile list. Hold the task, it should pops-up with option exit task. Choose this as exit task.
Play around to see if this profile is working when gaming apps in foreground, screen never turn off.
Click to expand...
Click to collapse
Thanks for your reply.
Creating the profile is not the problem. It just seems that Tasker cannot change the system's setting. As mentioned, there is no problem when you create a profile allowing the screen to rotate using a speciffic app (and others as well ) I have no idea, why it does not work for the screen timeout.

Dreamcatcher0664 said:
Thanks for your reply.
Creating the profile is not the problem. It just seems that Tasker cannot change the system's setting. As mentioned, there is no problem when you create a profile allowing the screen to rotate using a speciffic app (and others as well ) I have no idea, why it does not work for the screen timeout.
Click to expand...
Click to collapse
I use no screen timeout, I use "screen turn on" in your situation as my op., enough I've not tried it on my Samsung A71.

eeeemc said:
I use no screen timeout, I use "screen turn on" in your situation as my op., enough I've not tried it on my Samsung A71.
Click to expand...
Click to collapse
"Display / turn on" works fine when I want the screen to turn on with a notification. But the screen turns dark after the system timeout has passed. I've also tried "Display / Stay On / with Wireless, AC or USB Power" and with the AutoInput Plugin "Screen Off Or On: Turn On / Timeout Never" but the screen always turns dark.
Those Profiles always worked on my other Smartphones (LG -D405, LG-K10 and Moto G6). I believe, it's the ColorOs that's causing the trouble.

Dreamcatcher0664 said:
"Display / turn on" works fine when I want the screen to turn on with a notification. But the screen turns dark after the system timeout has passed. I've also tried "Display / Stay On / with Wireless, AC or USB Power" and with the AutoInput Plugin "Screen Off Or On: Turn On / Timeout Never" but the screen always turns dark.
Those Profiles always worked on my other Smartphones (LG -D405, LG-K10 and Moto G6). I believe, it's the ColorOs that's causing the trouble.
Click to expand...
Click to collapse
below is a task ONLY FOR ROOTED DEVICE., no harm to try even if your's not root.
New task , run shell command , in the command input
there is a button 'use root' , check that button also.
settings put system screen_off_timeout 200000
** 200000 I'm not sure sure equals to how many second., just give it a try and if you get a longer screen on time from your issue it means it is working.
also, make another separate task, search for 'custom setting'. look up from there I thingk it is in system something about screen timeout.
EDIT: run shell command task suggest you run it manually., than see if it works. if not, restart device to check if it requires a restart in order to accept new timeout settings.

eeeemc said:
below is a task ONLY FOR ROOTED DEVICE., no harm to try even if your's not root.
New task , run shell command , in the command input
there is a button 'use root' , check that button also.
settings put system screen_off_timeout 200000
** 200000 I'm not sure sure equals to how many second., just give it a try and if you get a longer screen on time from your issue it means it is working.
also, make another separate task, search for 'custom setting'. look up from there I thingk it is in system something about screen timeout.
EDIT: run shell command task suggest you run it manually., than see if it works. if not, restart device to check if it requires a restart in order to accept new timeout settings.
Click to expand...
Click to collapse
I feel like I'm in Star Trek - "To boldly go, where no one has gone before" XD
When I try your suggestion, I only receive the message that my device isn't rooted.
Btw, for some tasks it is necessary to enable the Write Secure Setting Permission (f.e. Set Assistant), where xou have to setup ADB on your PC. Would such a procedure be registered by the phone as rooting? Anyway, I don't think I would dare to do something I know so little of.

Another solution I was thinking of, is it possible to create a tasker quick tile/ quick setting to change the system screen timeout.
So instead of having it change for certain apps which isn't working at the moment.
Maybe if we can change it from the system so will be for all apps. You can create two separate quick tiles to toggle between different screen timeout settings.

The newest version of Tasker (6.0.9) comes with Tasky.
Tasky offers the possibility to activate premade profiles. One of them is "Keep Display Awake For Apps". And that one works with my OPPO Phone.
I also tried "Auto-Mute Apps", another profile I couldn't get working. It also works fine.
To switch between Tasker and Tasky you just have to click on the "Three-Dots-Button" in the right top corner. It's not like switching apps but using different user interfaces.
Good luck!
- Sorry to say, but this seems to work for some apps and not for others. But at least sometimes it does work.

Thanks for replying back to this thread to inform me. I tried it and it works for the app I was trying to make it work for which is good! Makes it so much easier now.