Hi guys
I want to open this thread to talk about tasker and possibility to set dt2w only when the proximity sensor is not covered
https://docs.google.com/file/d/0B5DaTWX-IUMjUGVWZFFOOW0wQ1k/edit?usp=docslist_api
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After run app, switch your finger on proximity sensor, if icon on statusbar say that profile run, it is OK, otherwise click on dt2w'button and swith your finger on proximity sensor
Changelog 2.71
New UI
Partially fix to battery
THIS IS A ALPHA APP
IS FOR ALL SMARTPHONE THAT HAVE DT2W LOCATE AT sys/android_touch/doubletap2wake
To do:
S2S
S2W
T2W
Old, how to create a profile
_________________________________________________________________________________
The solution that I have found is:
1 buy and download tasker from play store
------------- ------------- ------------- ------------- ------------- ------------- ------------- -------------
2 on the window TASK
create a task, click script, you will call it "on"
Put this line on command
echo 2 > /sys/android_touch/doubletap2wake
2a Tick on root permission
2b Tick on root permission
------------- ------------- ------------- ------------- ------------- ------------- ------------- -------------
3 on the window TASK
create a task, click script, you will call it "off"
Put this line on command
echo 0 > /sys/android_touch/doubletap2wake
3a Tick on root permission
3b optional
you can set optionally a timeout which power off dt2w, if kernel support it, when proximity sensor isn't covered, so:
Add another script into TASK "OFF"
Put this line on command
echo "#" > /sys/android_touch/wake_timeout
(# is time that you choose for power off dt2w)
------------- ------------- ------------- ------------- ------------- ------------- ------------- -------------
4 on the window PROFILE*
create a profile*
State/sensor/proximity sensor
And associate with it the task off
------------- ------------- ------------- ------------- ------------- ------------- ------------- -------------
5 on the window PROFILE*
create a profile*
State/sensor/proximity sensor
Tick inverted
And associate with it the task on
------------- ------------- ------------- ------------- ------------- ------------- ------------- -------------
According to ROM/kernel, this tips can not work
Sometimes, in fact, after a few minutes that proximity sensor is covered, the phone not wake with dt2w.
So just add some other profile
For example
Profile/state/display/display state/off with task "on"
Profile/event/display/off with task "on"
Because the problem is not deactive dt2w when the display is off, but reactive it !
So you can long-tap on the previous proximity sensor profile option and set as this picture
Now long tap to on the previous not proximity sensor and display state off profile option and set as this picture
P.s. in any program or script about dt2w MUST BE DEACTIVE
This is a solution
But will not the definitely solution
So if you have another one
Post it!
-------------_-----_-----------_-------------_-----------_
another feature in tasker
See the picture
For explain it
The green want to say that if the variable profile enter on work, will work the ask associated (in this case "not proximity sensor" happen when the proximity sensor is NOT covered, and dt2w is on)
The red want to say that if the variable profile enter off work, will work the ask associated (in this case "not proximity sensor" will off when the proximity sensor is COVERED, and dt2w is off)
this other mechanism not only allows you to have only one profile, but allows you to turn off in the options, the monitor of the proximity sensor, saving battery
To create it, long tap on task called "on" and click on "add exit task", choosing "off"
What appear will this
Let's try and report feedback
-------------_-----_-----------_-------------_-----------_
A third solution been found!
Maybe the most efficienty
This wake phone when the sun light hit the proximity sensor
Add a profile
State/proximity sensor/light
Put a interval from 10 to 100 (or whetever you want)
Will this :
Or you can set a specif time for a different range of light
Inviato dal mio Nexus 5 utilizzando
Awesome! Thanks a lot, now i try.
Just a question
"2b optional
you can set optionally a timeout which power off dt2w, if kernel support it, when proximity sensor isn't covered, so:
Add another script into TASK "ON"
Put this line on command
echo "#" > /sys/android_touch/wake_timeout
(# is time that you choose for power off dt2w)"
The "#" are seconds, right? Not minutes or other strange things.
Minutes! As all kernel trick
Just use you for a test
A seen another feature in tasker
See the picture
For explain it
The green want to say that if the variable profile enter on work, will work the ask associated (in this case "not proximity sensor" happen when the proximity sensor is NOT covered, and dt2w is on)
The red want to say that if the variable profile enter off work, will work the ask associated (in this case "not proximity sensor" will off when the proximity sensor is COVERED, and dt2w is off)
this other mechanism not only allows you to have only one profile, but allows you to turn off in the options, the monitor of the proximity sensor, saving battery
To create it, long tap on task called "on" and click on "add exit task", choosing "off"
What appear will this
Let's try and report feedback
Inviato dal mio Nexus 5 utilizzando Tapatalk
Please wait, for some reason Tasker have delete ALL my configuration, profiles and task
Does this save battery?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Second solution maybe
I'm testing
Inviato dal mio Nexus 5 utilizzando Tapatalk
Hi,
it sounds interesting
But i tried and doesn't work for me on nexus 5 stock with franco kernel!
The kernel could be the problem?? or what?
I've try now the "new" solution, but i still need to keep on the proximity sensor from the monitor tab.
And I don't see good results for the battery savings.
Dragusdrake I try the another feature it work,I using kangakat ROM faux kernel.thanks
Sent from my Nexus 5 using XDA Premium 4 mobile app
ThemeSong said:
I've try now the "new" solution, but i still need to keep on the proximity sensor from the monitor tab.
And I don't see good results for the battery savings.
Click to expand...
Click to collapse
ehm
maybe you wrong something cause the second solution work also with monitor off
what ROM you use?
ssl3vin said:
Hi,
it sounds interesting
But i tried and doesn't work for me on nexus 5 stock with franco kernel!
The kernel could be the problem?? or what?
Click to expand...
Click to collapse
off sure!
franco not implement dt2w in his kernel
Inviato dal mio Nexus 5 utilizzando Tapatalk
First page update with third solution
Inviato dal mio Nexus 5 utilizzando Tapatalk
Interesting thread. I'm trying to to setup dt2w so that it activates when a notification received and then turns off after a couple of minutes. This works when the screen is on but doesn't when it's turned off. Basically, writing '2' into /sys/android_touch/doubletap2wake does not turn on dt2w, unless I wake the phone with the power button. It seems you had a similar problem but I'm not sure how you solved this?
Ok
You need to see the settings
For example if you use profile that work with proximity sensor, you need to activate it by monitor off
Or
Just move parameters to turn on dt2w
Now i come back to first solution
But with this preference
Keep on My test
Hmm, did not manage to get it working. I want to enable DT2W when a notification is received, I don't want to use proximity sensor or anything else. For some reason it doesn't work, I can't enable DT2W while the screen is off.
Good idea!
I try and work!
For example
If you not work, check if task have root permission
The "use root" checkbox is checked, I don't know why it doesn't work Here's what happens. When I receive a notification, DT2W doesn't work. If I wake up the phone with power button, and immediatelly turn it off, then DT2W works. What kernel are you using, perhaps it has something to do with that?
I use elementalX and i try also other kernel
But
With charizardX , labodj's kernel, and bricked kernel , for me , tasker not work
I also use elementalX but can't get it to work. Damn! At least I know it's possible.
When you receive a notification you set task "on" or whatever you called it on enter task?
Or maybe set different time to monitoring off in the preference
@Dragusdrake
Oi!
[emoji16]
I downloaded your app and set up.
but, don't seems to work [emoji15]
something else to do?
n5sk7.8.1.Robbie09.08gapps239art
CD350twrp2.7.1.0rd2.08v4a
----------------------------------------------------------------------------
have doubts about Slim? click here:
http://slimroms.net/index.php/faqandmanual
Related
This quick tutorial will allow you to use an NFC tag to wake up your phone and launch directly into your favorite application. It will also bypass any PIN/pattern/password you have configured.
I've been trying to do this for a while and have been hunting down information/tools in XDA to try to unlock my pattern protected Note 2 and directly launch my remote app (Unified Remote) when I touch the NFC tag on the living room coffee table. The biggest challenge was to find a NFC screen-off mod that worked for the Note 2 (most were for the S3).
Tools:
Tasker (important: make sure you update to the latest version)
NFC Task Launcher
Writable NFC tags
Secure Settings (be sure to enable Device Admin)
NFC Screen Off Mod (attached), got it from here. Confirmed working for stock LJ1 and LJ3 odex rooted. WARNING: This mod might work on stock 4.1.2 but will cause annoying popups saying 'NFC Service has been stopped'.
Root (but I'm guessing if you have any of the above you're already rooted)
(optional but recommended) Titanium Backup
(optional) Unified Remote
1. Use TB to make a backup of your NFC Service apk (in case you get issues after flashing the modded one)
2. Flash the attached NFC Screen Off Mod using CMW
3. Create a task (Wake) in Tasker with the following actions:
EDIT: Make sure Tasker has 'enabled external access' option switched on in settings (Thanks SenK9)
Plugins -> Secure Settings -> Wake Device -> Screen and Keyboard lights on (30 sec or whatever you want)
Plugins -> Secure Settings -> Keyguard -> Off (this will also disable any PIN/pattern/password you have)
(optional) Misc -> Say -> "Device is awake" (or whatever you want it to say)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4. Prepare a writeable tag in NFC Task Launcher with the following actions:
Tasker -> Tasker Task -> Wake (or the name of your task)
(optional) Launch application -> Unified Remote (can also place this in your Task but I prefer to keep them separate since I use my task for other things as well)
[Add whatever you want to do here (launch app, play music, etc..)]
Note: Keyguard disable didn't work for me at first, so you may need to reboot your phone.
That's it! Hope this helped someone
Let me know if this works for you and if you have any recommendations or improvements I'd be happy to update the post with your suggestions.
Good work gabster21! Work well for me on stock LJ3. Followed your instructions and it worked without problem. Much better than the Samsung TecTiles app that I've been using.
Glad to hear it worked!
On a similar note I just finished automating my phone to start my favorite playlist on my HTPC using NFC with the screen off. It involves EventGhost (with several plugins) and sending an http get command from Tasker. I can post a tutorial on that if people are interested.
Can confirm that this mod works on N7105 (deodex LJ4), thanks!
Any idea why step 3 above only unlocks the screen temporarily before it locks again? I'm using standard pattern lock.
gabster21 said:
Glad to hear it worked!
On a similar note I just finished automating my phone to start my favorite playlist on my HTPC using NFC with the screen off. It involves EventGhost (with several plugins) and sending an http get command from Tasker. I can post a tutorial on that if people are interested.
Click to expand...
Click to collapse
A tutorial will be appreciated very much
wrapper said:
Any idea why step 3 above only unlocks the screen temporarily before it locks again? I'm using standard pattern lock.
Click to expand...
Click to collapse
Did you set the timeout value to 30 seconds? Otherwise I think it defaults to 3 sec
arvin2212 said:
A tutorial will be appreciated very much
Click to expand...
Click to collapse
Working on it.. got overloaded at work but will definitely post when I have time!
um....didnt work....
my nfc task launcher got response say run the task, tasker set the task as secure setting, but cant screen on and unlock device
im sure the nfc is ready while screen off, coz when i wake the device, nfc task launcher had the notification say it ran the task
Have you enabled device admin and helper in the secure settings app?
Sent from my GT-N7100 using xda premium
gabster21 said:
Have you enabled device admin and helper in the secure settings app?
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
i do....
emprize said:
i do....
Click to expand...
Click to collapse
Strange.. Keyguard Unlock didn't work for me at first either but a reboot fixed the issue. Try adding something to the task (like some sound) for debugging to see if the task is executing properly.
I personally use tasker without nfc. (probably will try nfc soon) For instance, when I get in my car and plug my phone in my aux, the phone automatically opens up Poweramp. (power amp has an option to continue playing on aux insert but not just opening the program.) Also when poweramp is running I have it disable my pattern lock.
Hey guys, just getting into some of this stuff, particularly with tasker.
Boodies, can someone conceivably set up the tasker so that the NFC tag is on the back of the cardock for my Note II and when my phone comes into contact it arms GPS and pops up poweramp as part of the same action?
Clockwerks77 said:
Hey guys, just getting into some of this stuff, particularly with tasker.
Boodies, can someone conceivably set up the tasker so that the NFC tag is on the back of the cardock for my Note II and when my phone comes into contact it arms GPS and pops up poweramp as part of the same action?
Click to expand...
Click to collapse
You would to have 'Secure Setfings' installed (with Helper) need to setups a task with these actions:
-> Plugins -> Secure Settings -> GPS -> ON
-> App -> Launch -> Poweramp
Then call this task from NFC task launcher programmed in a tag
Clockwerks77 said:
Hey guys, just getting into some of this stuff, particularly with tasker.
Boodies, can someone conceivably set up the tasker so that the NFC tag is on the back of the cardock for my Note II and when my phone comes into contact it arms GPS and pops up poweramp as part of the same action?
Click to expand...
Click to collapse
and to add to Gabster, here is a FANTASTIC site to learn tasker.
LEARN TASKER
Works for me
Thank you OP
Welcome
Can anyone provide the NFC screen off mod for N7105 XXDLK7 (4.1.2)? Thanks
wrapper said:
Can anyone provide the NFC screen off mod for N7105 XXDLK7 (4.1.2)? Thanks
Click to expand...
Click to collapse
dude im on sprint's note2 n the **** works fine for me....
as is, that is
Hey guys, new to this thread and sorry if asked but I'm running PA alpha3 and I installed zip but now my NFC check box went missing. Am I missing something?
Sent from my SPH-L900 using xda premium
Better Keyguard
The app is for People who dont use any security-lockscreen (like Pin, Pattern or Face unlock) and just like the fastest way to reach the homescreen after turning the device on. Many Roms allow to disable the key guard completly. So u see the homescreen right after turning on the device. But this way, unwanted misuse can happen, by accidentelly wakeing up the phone, while carrying it in your pocket.
Because of this and because iam not using a MIUI-Rom anymore (which had the very same feature), i set up a Tasker profile, which enables the proximity sensor for 1 sec, every time the display is turned on. If the sensor is not covered in that moment, nothing further will happen, if it is, the display will be turned off right away.
Later I decided to export this Profile as app via App Factory (Tasker Plugin), because I thought others would like such a feature too.
The app passed tests on my Galaxy SII (AOSP: Android 4.2.2) and on a Xperia Z (Stock Rom: Android 4.1.2) from a buddy of mine.
After Installation
1. Of course, to turn the screen off, u need to enable BK as device-admin.
2. To test: Press power button to turn off the display, keep the proximity sensor covered (usually located in right or left upper corner of the phone) while pressing the power button again to turn the display on. If its turned off again within 1 second, the test can be considered passed.
3. Note: On the Xperia Z (and some other devices), i noticed that any Lockscreen/Keyguard has to be disabled to make the App work. (It seems that the proxy sensor is not working in lockscreen)
Since Iam no programmer and the fact, that this is a Tasker-Project, my abilities for improvements or Bugfixing are very limited. Maybe some1 will pickup the idea and write a REAL app of this kind. Ofc only if the Chinese have not yet patented their MIUI-feature. :laugh:
I uploaded the Tasker-Project-Files as well.
Just would like to know ur thoughts about this.
Changelog:
1.0 - First release
1.1 - Added a UI allowing to adjust some options (show/hide notification, try to disable built in keyguard, launch on boot: Always, Never, Remember last state)
- Toggling the state shows now a tiny flash message
1.2 - Added option to show a warning message before display goes off. If the sensor is uncovered quick enough, display will stay on and the warning message will be dismissed.
(disadvantages: Tasker provides only 2 relevant massage types for that purpose. One can be dismissed by the back key, which is bad for devices with capacitive buttons, since these buttons are not locked while the warning message is shown. So I decided to go with the second type, which is not dismissable by the back key, but also not overlapping the status bar, so it is still expandable).
2nd: Somehow this version is not working along with lockscreen at all. So, if you want to see a warning message before screen goes off, u need to disable any kind of lockscreen (even normal swipe).
If you want to use it along with a lockscreen, you need to try it with Bk 1.1 or 1.0
1.3 - Added an option to show the warning message over lockscreen (only if the app is working in lockscreen at all and u need to tell it, if u are using a lockscreen or not)
Removed because of no further advantage.
1.4 - Slightly reworked UI with new Szene-elements from latest Tasker version (Checkbox and Drop-down menu). This version equals 1.1 in functionality, since i thought the app was inflated too much with stuff that actually didnt work correctly. Furthermore i also used the latest version of App-Factory to create the app, since "Pent" (the dev of Tasker) released at least two updates for Tasker and the App-Factory plugin since i uploaded BK_1.2. So this one might work more reliable now.
Here the UI
Field tests revealed that a enabled keyguard (normal swipe lockscreen or whatever) prevents Bk from working properly in some cases. If Your Rom doesnt allow to disable the key guard, try the new disable built in keyguard option. If your Rom does allow it, use the native setting to disable the lockscreen rather than Bk ones.
Reuploaded the first release, becuase the file had a Tasker created filename (Better_keyguard.4.apk) and did not reflect the actual version number.
Best regards
Chillmann
OK 9 views so far. But i would realy appreciate a response of any kind
No matter if its "... well done, working as intended" or "... fu, its chewing up all my battery"
Please, just give a response!
Thx in advance
Chillmann
i tried and test it "DO NOTHING nothing at all" jst stay @ notification saying BK is active ( i have activated system administration) probably describing how it work and what it does will be more useful some screenshot.
I am on Slimbean 4.2.2 build 4
Samsung galaxy s2 GT-I9100
Hi aryan1312,
many thx for responding!
I rewrote the introduction to better underline the app's purpose and added a "After installation" annotation with instructions of how to test the functionality.
Since the app got no menu, there would be nothing to show in a screenshot. Ill try to put a youtube video online soon, that will show what it does.
i tried and test it "DO NOTHING nothing at all" jst stay @ notification saying BK is active ( i have activated system administration) probably
Click to expand...
Click to collapse
I hope u just didnt know how to test it, because u got the very same set up as i do (sgs2 on slim beam 4.2.2+dori9.14). Would be quite strange, if its not working even with same hardware + software. On my phone, i allways notice a weak red glow coming from the proximity sensor, if its active. (during a call or if a sensor related Tasker-profile is running) Maybe u watch out for that glow right after turning on the display. That would indicate the app's functionality too.
Best regards
Chillmann
Chillmann said:
Hi aryan1312,
many thx for responding!
I rewrote the introduction to better underline the app's purpose and added a "After installation" annotation with instructions of how to test the functionality.
Since the app got no menu, there would be nothing to show in a screenshot. Ill try to put a youtube video online soon, that will show what it does.
I hope u just didnt know how to test it, because u got the very same set up as i do (sgs2 on slim beam 4.2.2+dori9.14). Would be quite strange, if its not working even with same hardware + software. On my phone, i allways notice a weak red glow coming from the proximity sensor, if its active. (during a call or if a sensor related Tasker-profile is running) Maybe u watch out for that glow right after turning on the display. That would indicate the app's functionality too.
Best regards
Chillmann
Click to expand...
Click to collapse
Thanks for giving the description more accurately. Now i have better understanding of how it work. previously i was using slide2wake (dori function) i think that y it is not workin, will try with power button now
Edit: Work absolutely fine, even with slide2wake and PIN lock
don't think it will affect much battery performance since it activate proximity sensor for jst 1 sec
Great work
New version uploaded, check OP
Greets
Chillmann
What if I have no proximity sensor? Can it work? Nah, just kidding it's a nice app but I'd really would like it if it's notification could be swiped away and if there would be a warning like in the miui because now it's more like miui idea not like a miui style. I'm still going to use this app and tell my friend which also has similar problem about this app
Sent from my R800i using xda premium
After I've watched a movie it suddenly stopped working... I've even relaunched it and nothing... I guess that reboot will help me.
Sent from my R800i using xda premium
Nope, it didn't. Actually it's not working at all now...
Sent from my R800i using xda premium
Hi olokos,
thx for testing!
olokos said:
What if I have no proximity sensor? Can it work? Nah, just kidding it's a nice app but I'd really would like it if it's notification could be swiped away and if there would be a warning like in the miui because now it's more like miui idea not like a miui style. I'm still going to use this app and tell my friend which also has similar problem about this app
Sent from my R800i using xda premium
Click to expand...
Click to collapse
I added a option to enable a warning message before screen goes off. To the non permanent notification, sorry but I can't see the advantage. Why not disable the notification completely?
olokos said:
After I've watched a movie it suddenly stopped working... I've even relaunched it and nothing... I guess that reboot will help me.
Sent from my R800i using xda premium
Click to expand...
Click to collapse
olokos said:
Nope, it didn't. Actually it's not working at all now...
Sent from my R800i using xda premium
Click to expand...
Click to collapse
uhm, thats really strange. At 1st I thought it was androids memory management who threw Bk out of the cache. But even not working after reboot is bad. As stated in the OP, iam no programmer, so I have neither a clue why it stopped working, nor I know how to fix it
I think it has something to do with the way, Tasker exports profiles into apps.
U can try to delete app data (if not already removed) to get it working again. But if it keeps stopping to work, deleting data is no real solution.
Iam sorry I did no long time testing prior to posting here. During quick tests I recognized, that Bk wouldn't show the option menu by pressing the app icon after Tasker performed one of its tasks. Removing Bk from recents app list did fix that. But this is completely different to ur experience.
I hope it is a very rarely occurring bug or related only to few devices. Otherwise the app would be unusable. :crying:
Hopefully
Chillmann
After disabling swipe unlock in JB it is working but when JB screen lock is working normally, your app is not working... I'm not using any other key lock (pattern, pin) or anything. I just have to swipe to unlock. If you are going to fix it then I promise I'll spread the word
Sent from outer space using RPG
olokos said:
After disabling swipe unlock in JB it is working but when JB screen lock is working normally, your app is not working... I'm not using any other key lock (pattern, pin) or anything. I just have to swipe to unlock. If you are going to fix it then I promise I'll spread the word
Sent from outer space using RPG
Click to expand...
Click to collapse
Hi olokos,
well, in order to make a message appear over the lockscreen, i had to use the 3rd message type, which tasker provides. I never thought it would be relevent, since it doesnt block any input. Unfortunetly, that makes this feature to an eye candy without further purpose.
As I stated in the "After installation" paragraph, i found out that some roms prevent the proximity sensor from working in lockscreen. After updating my own decive to slim bean 4.2.2 build5, Bk stopped working in lockscreen too.
In order to use the warning message over lockscreen, u need to test the functionality without the "show warning" option. If it works and ur display is turned off as intended, u can enable "show warning". But u also have to tell the app wether a lockscreen is in use or not.
hope its fitting ur desire a little more now
Edit: found out that it wasn't my rom preventing the sensor from working in lockscreen, but its not working since Bk 1.2
So, if you want to see a warning message before screen goes off, u need to disable any kind of lockscreen (even normal swipe).
If you want to use it along with a lockscreen, you need to use Bk 1.1
Sorry i couldn't turn it into real MUI style :/
Chillmann
Hey bro i have shared ur post link to slimbean post wish u dont have issue with it ... if any problem plz inform i wil remove the link :fingers-crossed:
OP updated
perfect one
Working like a charm on nexus 4 stock ROM 4.4.2 ART runtime
Works on my galaxy s4 stock rom 4.2.2. Works only without a lock screen though. Using v1.4 of better keyguard. The UI is in a mess refer to screenshot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
THX for testing! Well ur S4 got some more Pixel than my old S2 ^^
Ill try to rework the UI next time I can get my hands on a high resolution device in order to test different settings for UI creation.
Greets
Chillmann
Sent from my GT-I9100 using XDA Free mobile app
Chillmann said:
Better Keyguard
The app is for People who dont use any security-lockscreen (like Pin, Pattern or Face unlock) and just like the fastest way to reach the homescreen after turning the device on. Many Roms allow to disable the key guard completly. So u see the homescreen right after turning on the device. But this way, unwanted misuse can happen, by accidentelly wakeing up the phone, while carrying it in your pocket.
Because of this and because iam not using a MIUI-Rom anymore (which had the very same feature), i set up a Tasker profile, which enables the proximity sensor for 1 sec, every time the display is turned on. If the sensor is not covered in that moment, nothing further will happen, if it is, the display will be turned off right away.
Later I decided to export this Profile as app via App Factory (Tasker Plugin), because I thought others would like such a feature too.
The app passed tests on my Galaxy SII (AOSP: Android 4.2.2) and on a Xperia Z (Stock Rom: Android 4.1.2) from a buddy of mine.
After Installation
1. Of course, to turn the screen off, u need to enable BK as device-admin.
2. To test: Press power button to turn off the display, keep the proximity sensor covered (usually located in right or left upper corner of the phone) while pressing the power button again to turn the display on. If its turned off again within 1 second, the test can be considered passed.
3. Note: On the Xperia Z (and some other devices), i noticed that any Lockscreen/Keyguard has to be disabled to make the App work. (It seems that the proxy sensor is not working in lockscreen)
Since Iam no programmer and the fact, that this is a Tasker-Project, my abilities for improvements or Bugfixing are very limited. Maybe some1 will pickup the idea and write a REAL app of this kind. Ofc only if the Chinese have not yet patented their MIUI-feature. :laugh:
I uploaded the Tasker-Project-Files as well.
Just would like to know ur thoughts about this.
Changelog:
1.0 - First release
1.1 - Added a UI allowing to adjust some options (show/hide notification, try to disable built in keyguard, launch on boot: Always, Never, Remember last state)
- Toggling the state shows now a tiny flash message
1.2 - Added option to show a warning message before display goes off. If the sensor is uncovered quick enough, display will stay on and the warning message will be dismissed.
(disadvantages: Tasker provides only 2 relevant massage types for that purpose. One can be dismissed by the back key, which is bad for devices with capacitive buttons, since these buttons are not locked while the warning message is shown. So I decided to go with the second type, which is not dismissable by the back key, but also not overlapping the status bar, so it is still expandable).
2nd: Somehow this version is not working along with lockscreen at all. So, if you want to see a warning message before screen goes off, u need to disable any kind of lockscreen (even normal swipe).
If you want to use it along with a lockscreen, you need to try it with Bk 1.1 or 1.0
1.3 - Added an option to show the warning message over lockscreen (only if the app is working in lockscreen at all and u need to tell it, if u are using a lockscreen or not)
Removed because of no further advantage.
1.4 - Slightly reworked UI with new Szene-elements from latest Tasker version (Checkbox and Drop-down menu). This version equals 1.1 in functionality, since i thought the app was inflated too much with stuff that actually didnt work correctly. Furthermore i also used the latest version of App-Factory to create the app, since "Pent" (the dev of Tasker) released at least two updates for Tasker and the App-Factory plugin since i uploaded BK_1.2. So this one might work more reliable now.
Here the UI
Field tests revealed that a enabled keyguard (normal swipe lockscreen or whatever) prevents Bk from working properly in some cases. If Your Rom doesnt allow to disable the key guard, try the new disable built in keyguard option. If your Rom does allow it, use the native setting to disable the lockscreen rather than Bk ones.
Reuploaded the first release, becuase the file had a Tasker created filename (Better_keyguard.4.apk) and did not reflect the actual version number.
Best regards
Chillmann
Click to expand...
Click to collapse
Hi,
I just find your app. I really need n app like this, but it doesn't want to work for mi ( for test i cover the sensors and try to use the screen and i can). Is it compatible with kitkat based roms? I have a N4. Can you suggest another test method if mine is useless?
Just to let you know, I'vee take your idea and modified it.
SOme newer devices with tap-on screens can be triggered in your pocket. This app works, but it doesn't work if you have a standard slide lock screen - so I modified tasker to check for screen unlock andd proximity, rather than screen on and proximity... then if your device turns on in your pocket and then tries to unlock, it will go off again - this works around it not working with a lock screen.
Good idea checking for lock screen :thumbup:
Did you share your work somewhere?
Best regards, Chillmann
Sent from my GT-I9100 using XDA Free mobile app
I recently put together a very "rudimentary" widget to quickly toggle slide/sweep to wake functionality on the kernel I am running.
I originally just created it for myself, but figured why not share with the community in case anyone else might find it of use. Since this was mainly for my own use, it has no special configuration options, etc, just a cut and dry widget to use to toggle as opposed to shell commands / scripts, etc.
Since I originally posted it in the thread for the kernel I am using, I will link to that specific post for downloads (so as to maintain a single download point).
The widgets (choose between sweep2wake or doubletap2wake versions), should work on any kernel supporting either:
/sys/android_touch/sweep2wake
/sys/android_touch/doubletap2wake
as the mechanism for enabling / disabling this option.
It's nice for random times when you know you are not going to be using your phone and want to save some battery (and don't prefer / want to use scripts, tasker, locale, etc).
At any rate here's the link:
Download Here --> Download Post
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
For questions, comments, etc, let's use this thread, instead of the post thread, so as to not clutter that thread with off-topic stuff. Thanks!
And thanks to the kernel devs who made this feature available in the first place!
nice ..
I would suggest putting the apk's here and linking the post in the kernel thread to this thread.
munchy_cool said:
nice ..
I would suggest putting the apk's here and linking the post in the kernel thread to this thread.
Click to expand...
Click to collapse
Thanks. When / if I update the toggles, I'll move them over then, since I'll have to reload / reset anyway.
PS:-works like a charm
munchy_cool said:
PS:-works like a charm
Click to expand...
Click to collapse
Great. Thanks for the confirmation. It seems so far, I'm in the minority for when I originally created the widget just for "sweep2wake" (in terms of download count at least).
Do I need to be rooted? Does it work on stock Android if I just install it via APK installer app ?
rbs_uk said:
Do I need to be rooted? Does it work on stock Android if I just install it via APK installer app ?
Click to expand...
Click to collapse
I'm not sure you can install a custom kernel on an un-rooted phone (can't say I've ever tried though).
Since the widget requires a custom kernel that supports the wake feature, root is required (as well as so the widget can write to the necessary /sys/ file as well).
This is a very nice and well realized idea, thanks op, I'm testing Dt2w right now and it seems to work flawlessly.. One question: can we use both of widgets at the same time? For example, s2s to turn the screen off and Dt2w to turn it on?
Ps. Choosing Franco as supported kernel it's the best choice ever
Inviato dal mio Nexus 5 utilizzando Tapatalk
memnoc said:
This is a very nice and well realized idea, thanks op, I'm testing Dt2w right now and it seems to work flawlessly.. One question: can we use both of widgets at the same time? For example, s2s to turn the screen off and Dt2w to turn it on?
Ps. Choosing Franco as supported kernel it's the best choice ever
Click to expand...
Click to collapse
Thanks. Screen off is not controlled by the widget, as this can be enabled via other configuration flags. Since it does not have any impact on battery, I don't / didn't see the point in creating a toggle for it (once it's enabled, there's really no reason / need to toggle frequently).
So, you can manually enable the s2s to turn the screen off and leave it that way, and use the d2tw widget for that piece.
JsChiSurf said:
Thanks. Screen off is not controlled by the widget, as this can be enabled via other configuration flags. Since it does not have any impact on battery, I don't / didn't see the point in creating a toggle for it (once it's enabled, there's really no reason / need to toggle frequently).
So, you can manually enable the s2s to turn the screen off and leave it that way, and use the d2tw widget for that piece.
Click to expand...
Click to collapse
Nice, I'll try it in combo with Trickster mod and I'll report back.. The problem I always had with third party apps is that after few hours of stand by the Dt2w is just being disabled.. I hope your workaround doesn't suffer from the same issue
EDIT: sweep to sleep isn't working even if selected through Trickster mod.. Sweep to wake instead it's perfect.. I guess there is a specific module for s2s isn't it?
Inviato dal mio Nexus 5 utilizzando Tapatalk
memnoc said:
Nice, I'll try it in combo with Trickster mod and I'll report back.. The problem I always had with third party apps is that after few hours of stand by the Dt2w is just being disabled.. I hope your workaround doesn't suffer from the same issue
Inviato dal mio Nexus 5 utilizzando Tapatalk
Click to expand...
Click to collapse
Unless there is some other setting somewhere in place writing to the /sys/ file, it should stay on/off until you toggle once again. If not, something else is coming into play.
JsChiSurf said:
Unless there is some other setting somewhere in place writing to the /sys/ file, it should stay on/off until you toggle once again. If not, something else is coming into play.
Click to expand...
Click to collapse
See the edit to my previous post
Inviato dal mio Nexus 5 utilizzando Tapatalk
memnoc said:
See the edit to my previous post
Inviato dal mio Nexus 5 utilizzando Tapatalk
Click to expand...
Click to collapse
What specific kernel are you using? Though this is technically out of the scope of this thread, I've seen that the implementation for enabling (I don't use) varies by kernel and perhaps trickster mod is not compatible as a result.
JsChiSurf said:
What specific kernel are you using? Though this is technically out of the scope of this thread, I've seen that the implementation for enabling (I don't use) varies by kernel and perhaps trickster mod is not compatible as a result.
Click to expand...
Click to collapse
I'm using the Franco r33 test version from your op (the link I followed through) Said that, it's not really an issue, as far as I'm concerned your mod with this kernel doesn't suffer from battery drain. I tried every single kernel supporting those gestures and the drain was always remarkably high. On a side note, the widget comes really in handy if you want to save battery and this is very important. Just so you know, Trickster works with bricked from show-p, both for s2s and s2w (and for Dt2w obviously) but it's not sustainable as the battery drain is quite unbelievable sometimes. Sorry for the ot, if you'll ever spend some time on this I'll be grateful, but there's no really need to. Keep up the good job here.
Inviato dal mio Nexus 5 utilizzando Tapatalk
memnoc said:
I'm using the Franco r33 test version from your op (the link I followed through) Said that, it's not really an issue, as far as I'm concerned your mod with this kernel doesn't suffer from battery drain. I tried every single kernel supporting those gestures and the drain was always remarkably high. On a side note, the widget comes really in handy if you want to save battery and this is very important. Just so you know, Trickster works with bricked from show-p, both for s2s and s2w (and for Dt2w obviously) but it's not sustainable as the battery drain is quite unbelievable sometimes. Sorry for the ot, if you'll ever spend some time on this I'll be grateful, but there's no really need to. Keep up the good job here.
Click to expand...
Click to collapse
I'm not sure what trickster mod writes to, but if you issue from a shell prompt for the franco.kernel derivative:
Code:
echo 1 > /sys/android_touch/s2w_s2s
This will manually enable sweep2sleep, by running your finger from right to left across the bottom navigation bar.
And to enable permanently, add the following file to your /sdcard:
Code:
/sdcard/fkSettings/fks2s
Doing the above will give both (in combination with the widget) of what you are looking for / want (sweep to wake AND sweep to sleep).
JsChiSurf said:
I'm not sure what trickster mod writes to, but if you issue from a shell prompt for the franco.kernel derivative:
Code:
echo 1 > /sys/android_touch/s2w_s2s
This will manually enable sweep2sleep, by running your finger from right to left across the bottom navigation bar.
And to enable permanently, add the following file to your /sdcard:
Code:
/sdcard/fkSettings/fks2s
Doing the above will give both (in combination with the widget) of what you are looking for / want (sweep to wake AND sweep to sleep).
Click to expand...
Click to collapse
I finally did it now I'm able to place both of your widgets in my home (Dt2w and s2w) so I can enable/disable them as I need, plus through the shell and a common file manager it's very easy to set s2s permanently, so I can get rid of hardware buttons once for all and wake/put to sleep the N5 just using the touchscreen. Most importantly, I have zero battery drains with Franco r33 kernel you built to work with the modules, and it's quite an achievement. If you plan on making a donate version I'll be your first paying customer
Inviato dal mio Nexus 5 utilizzando Tapatalk
memnoc said:
I finally did it now I'm able to place both of your widgets in my home (Dt2w and s2w) so I can enable/disable them as I need, plus through the shell it's very easy to set s2s permanently, so I can get rid of hardware buttons once for all and wake/put to sleep the N5 just using the touchscreen. Most importantly, I have zero battery drains with Franco r33 kernel you built to work with the modules, and it's quite an achievement. If you plan on making a donate version I'll be your first paying customer
Click to expand...
Click to collapse
Awesome, glad you got it going!
but you need a custom kernel?
fraussantin said:
but you need a custom kernel?
Click to expand...
Click to collapse
Yes, I've not seen a stock kernel that supports the sweep or tap to wake feature.
I've updated the thread title for those that may not realize this
Ok thanks.
what kind of kernel do you recommend to use to only have this mod?
Thank
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Okay so we all know by now that you can enable the "Charging LED" to use as a Notification light.
A lot of people have been having issues with getting it up and running, so here is a in depth look at whats needed to get it going.
Click to expand...
Click to collapse
Sections :
Kernels
Pre-Requisites
General Settings
Root Settings
Per-Notification Settings
SuperUser Settings
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
Purchase from the playstore : Light Flow PAID APP
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
Custom Kernels
After Flashing a new kernel you may find that Light Flow will no longer work with the previous settings, you can either clear its cache and data and start again or uninstall and re install.
Click to expand...
Click to collapse
Kernels tested :
Elemental X - Needs Mixer Mode (? 1 Report of working without needing mixer enabled)
Franco's - Does not need mixer mode
Stock CM - Needs Mixer Mode
Stock - Needs Mixer Mode
*If you have used Light Flow with another kernel please PM me and I'll add it to the list*
--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--
Pre-Requisites
1. You MUST be Rooted for this to work
2. The PAID / Donate Version of Light Flow, if yours says LIGHT FLOW LIGHT it is not officially supported by the dev !
3. Make Sure you have a fresh install of light flow so everything is set to default values to make this easy to follow.
--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--
General Settings
1. Once your in Light Flow allow it Root Access if Superuser asks and allow it accessibility access to notifications ( YOU MUST ALLOW THIS ! )
2. Hit the Three horizontal lines in the top left corner of the screens and head for settings
3. Go into General Settings and make sure all the following Settings are Ticked :
Enable Light Flow
Show LED in Priority Mode
Enable Clear All
Accessibility check
Version Upgrade Reminder ( you don't need this one but i keep it on regardless )
You may find that Lightflow will run in the foreground and leave a persistent notification, this is done to solve issues with the app from stopping running in some cases.
So far I have not had this issue with the N6 so you can go ahead and untick that in Settings -> Persistent Icon.
--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--
Root Settings
Back in the settings menu go into Device Settings and Root
You need to enable the following options if your system is set to SELinux - Enforcing
Direct Mode
Root Mode
Run Every Command as Root
Nexus 5 force LED Reset ( this mode does not have to be enabled unless you have issues with your LED messing up )
If your system is set to Permissive you can Untick :
Run Every command as root
Nexus 5 force LED Reset ( this mode does not have to be enabled unless you have issues with your LED messing up )
Click to expand...
Click to collapse
--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--
Per-Notification Settings
This is all the settings you need to let light flow have control of the LED, now you need to configure Notifications to use the light.
Head into the Notification settings and select one of the Default Profiles ( Im using charging battery )
You need to scroll across the screen to the tab called "LIGHT", on this page scroll down until you see Enable Mixer Mode make sure this is ticked.
Depending on your kernel you may find you don't need to enable Mixer mode, however its more than likely you will need mixer mode enabled !
Now you have control over the 3 Primary colors R/G/B and their brightness ( 1-20 ) - I have played with the brightness settings here and it seems to not affect the LED as of Version 3.51.1
If you are using the LED without mixer mode, you will find that it can't display any colors that are not Red or Green or Blue it.
For example picking Orange from the color picker resulted in a Green LED.
You have the same settings for each color however the SOLID option is the only one that seems to work !
You can select 1 LED on or all 3 on and mix them together to make other colors but because of the led it does not work as well as the Nexus 5's LED.
--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--
Red / Blue / Green LEDs
SUPERSU Settings
You may find that Flightflow appears to show SU notifications constantly, this is because Show notifications is enable in your SU app.
Dive into settings and un-tick the option.
Click to expand...
Click to collapse
Thanks for pulling this together.
Only problem now is 8-10 second delay for screen to wake up.
Finally seems to work better. This morning w/ slightly different settings it was unusable. Any way to make them flash? A flashing sms light would be perfect.
hutzdani said:
1. Once your in Light Flow allow it Root Access if Superuser asks and allow it accessibility access to notifications ( YOU MUST ALLOW THIS ! )
Click to expand...
Click to collapse
use the one in Settings > Sounds & Notifications > App Notifications > Light Flow (Enable) not the one in Accessibility.
The one in accessibility has a warning, "this option is not recommended to be used in android 4.3 upwards and the new notification access method should be used instead"[b/]
I use the one in Sounds & Notifications and LED works fine.
Other than that, great guide. Should help people get it to work Hopefully the LED can be worked on and we won't need Light Flow in the future.
Has messaging been fixed yet for texts?
Thanks for the tutorial.
It would be great to have this guide as a Sticky.
It's weird so picking the color from the circle drop down doesn't choose the color. You have to tweak/create the color yourself in the mixer options. Either way I like it because it works. Now we just need flashing.
jawmail said:
It's weird so picking the color from the circle drop down doesn't choose the color. You have to tweak/create the color yourself in the mixer options. Either way I like it because it works. Now we just need flashing.
Click to expand...
Click to collapse
The colour picker works for me, even without enabling the mixer option.
Hand76 said:
Has messaging been fixed yet for texts?
Click to expand...
Click to collapse
Its working for my "google messenger" ( blue and white chat bubbles icon) I have selected SMS as the notification.
springer.music said:
The colour picker works for me, even without enabling the mixer option.
Click to expand...
Click to collapse
OK yes it does work either way, thanks still trying to learn this app.
How can I get this massage to go away. It's keep poping up every 30 sec. It's driving me crazy
NICEGYPT said:
How can I get this massage to go away. It's keep poping up every 30 sec. It's driving me crazy
Click to expand...
Click to collapse
Uncheck show notifications within settings of SuperSU.
You should add that the Notifications Off app will make the persistent notification icon go away but keep all the functionality.
Lightflow is working perfectly for me with elementalx kernel without mixer. I have the charging led enabled by the kernel. Also you need permissive selinux for this to work.
poczynek said:
You should add that the Notifications Off app will make the persistent notification icon go away but keep all the functionality.
Click to expand...
Click to collapse
You can disable this in the Light Flow settings :
Settings -> Persistent Icon : Now untick run in foreground
No extra App needed
zephiK said:
use the one in Settings > Sounds & Notifications > App Notifications > Light Flow (Enable) not the one in Accessibility.
The one in accessibility has a warning, "this option is not recommended to be used in android 4.3 upwards and the new notification access method should be used instead"[b/]
I use the one in Sounds & Notifications and LED works fine.
Other than that, great guide. Should help people get it to work Hopefully the LED can be worked on and we won't need Light Flow in the future.
Click to expand...
Click to collapse
Great to see you took my advice ? 'Happy New Year' ?2?0?1?5?
hutzdani said:
You can disable this in the Light Flow settings :
Settings -> Persistent Icon : Now untick run in foreground
No extra App needed
Click to expand...
Click to collapse
Yes but if you do you miss out on some led notifications.
poczynek said:
Yes but if you do you miss out on some led notifications.
Click to expand...
Click to collapse
I've disabled "Run in foreground" and so far I haven't missed any notification (yet).
I've also enabled the "Reduce wake" option and so far so good.
poczynek said:
Yes but if you do you miss out on some led notifications.
Click to expand...
Click to collapse
That's weird it must be for some notifications dependent on the app, which notifications are you using ?
Im using ( All set to dismiss on Battery or when notification is cleared ) :
Charged Battery
Charging
Missed Call
SMS ( Google Messenger ) Recived
Click to expand...
Click to collapse
Also having "Reduce wake" seems to make no difference to how the app effects the battery for me ( might make it use 1 or 2% more but its not a massive impact that would be the difference between 1 days usage and not )
zephiK said:
use the one in Settings > Sounds & Notifications > App Notifications > Light Flow (Enable) not the one in Accessibility.
The one in accessibility has a warning, "this option is not recommended to be used in android 4.3 upwards and the new notification access method should be used instead"[b/]
I use the one in Sounds & Notifications and LED works fine.
Other than that, great guide. Should help people get it to work Hopefully the LED can be worked on and we won't need Light Flow in the future.
Click to expand...
Click to collapse
Yeah i saw that message, however i have had it enabled in one or the other or both and had no issues YET so i decided to leave this one out as the app seems to function correctly if you just follow what it asks for so people can get set up as easy as possible.
So I know I'm not the only one having problems with notifications. The issues I have found with every firmware up to 137 are:
1. Regardless of Doze settings, enters IDLE in five minutes.
2. Sometimes, regardless of Doze settings, never gets out of IDLE into IDLE_MAINTENANCE
So to work around these issues, the only way to do it is to disable Doze. Disabling Doze will potentially cost you battery life, but you will get notifications from email client and any other software, as if it were Lollipop.
So what's a good way to do this easily? Tasker is the best answer I've come up with.
Here are the instructions which worked for me. This has solved all the notification issues I have had, but it's a little bit of a pain.
1. Make sure your phone is rooted. Purchase and install Tasker.
2. Create a task. Action category is Code-> Run Shell. Command is -- dumpsys deviceidle disable --. Check Use Root. Then click the lower right hand corner to make an icon, and go back to Tasks menu. Long press the task you made to highlight it, then choose the menu in the upper right and choose export. Export it 'As App' (it may prompt you to install something)
Run this app every time you start up your phone, or set it to auto run in the app settings. Make sure it has root permission. If you did this correctly, it will disable doze until the phone reboots, and Doze won't interfere with notifications anymore.
Hopefully all these issues get fixed soon!
duraaraa said:
So to work around these issues, the only way to do it is to disable Doze.
Click to expand...
Click to collapse
Have you also tried selecting the Performance plan?
Performance setting still won't work.
Sent from my HUAWEI NXT-AL10 using XDA Premium 4 mobile app
Maybe it can help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my HUAWEI NXT-L29 using Tapatalk
somboons said:
Maybe it can help.
View attachment 3632622
Sent from my HUAWEI NXT-L29 using Tapatalk
Click to expand...
Click to collapse
How did you get in that setting? I can't find it in my phone 'setting'
snugroho3 said:
How did you get in that setting? I can't find it in my phone 'setting'
Click to expand...
Click to collapse
That is greenify app.
Sent from my HUAWEI NXT-L29 using Tapatalk
Is greenify working ok without xposed?
sure thing, xposed only enables some extra functions. been using greenify without xposed for a long time now
I have to hand it to you. This worked. I was skeptical, but as soon as I disabled doze using this method, all of my notifications became instant. Absolutely no delay. It's a shame to have to give up doze to get notifications to work correctly, but it makes the phone 100% more usable. Thanks, man. This thread hasn't had anywhere near enough attention.
Making apps system apps, whitelisting, performance mode, locking apps in memory, and turning off doze for individual apps (not to mention tweaking the doze settings) - None of that worked. Doze is seriously broken on this phone. None of my other phones on 6.0 have this issue. Thanks for figuring this out. I was going to park the phone until an ASOP or Cyanogenmod ROM came out.
duraaraa said:
So I know I'm not the only one having problems with notifications. The issues I have found with every firmware up to 137 are:
1. Regardless of Doze settings, enters IDLE in five minutes.
2. Sometimes, regardless of Doze settings, never gets out of IDLE into IDLE_MAINTENANCE
So to work around these issues, the only way to do it is to disable Doze. Disabling Doze will potentially cost you battery life, but you will get notifications from email client and any other software, as if it were Lollipop.
So what's a good way to do this easily? Tasker is the best answer I've come up with.
Here are the instructions which worked for me. This has solved all the notification issues I have had, but it's a little bit of a pain.
1. Make sure your phone is rooted. Purchase and install Tasker.
2. Create a task. Action category is Code-> Run Shell. Command is -- dumpsys deviceidle disable --. Check Use Root. Then click the lower right hand corner to make an icon, and go back to Tasks menu. Long press the task you made to highlight it, then choose the menu in the upper right and choose export. Export it 'As App' (it may prompt you to install something)
Run this app every time you start up your phone, or set it to auto run in the app settings. Make sure it has root permission. If you did this correctly, it will disable doze until the phone reboots, and Doze won't interfere with notifications anymore.
Hopefully all these issues get fixed soon!
Click to expand...
Click to collapse
I made and run this app but i dont know If it has root permission and doze gets disable or not. How can i control if it has root permission and doze gets disable or not after i run this app?
HUAWEI NXT-AL10 cihazımdan Tapatalk kullanılarak gönderildi
johnweber7375 said:
I made and run this app but i dont know If it has root permission and doze gets disable or not. How can i control if it has root permission and doze gets disable or not after i run this app?
HUAWEI NXT-AL10 cihazımdan Tapatalk kullanılarak gönderildi
Click to expand...
Click to collapse
You can check using adb.
I don't have the phone now (it's bricked) so I'm sorry to say I can't be sure the command is right, but I think you should see something like disabled if you run
adb shell dumpsys deviceidle
Then you will know that it worked.
greyhulk said:
I have to hand it to you. This worked. I was skeptical, but as soon as I disabled doze using this method, all of my notifications became instant. Absolutely no delay. It's a shame to have to give up doze to get notifications to work correctly, but it makes the phone 100% more usable. Thanks, man. This thread hasn't had anywhere near enough attention.
Making apps system apps, whitelisting, performance mode, locking apps in memory, and turning off doze for individual apps (not to mention tweaking the doze settings) - None of that worked. Doze is seriously broken on this phone. None of my other phones on 6.0 have this issue. Thanks for figuring this out. I was going to park the phone until an ASOP or Cyanogenmod ROM came out.
Click to expand...
Click to collapse
I spend a LOT of time figuring it out, but it was definitely Doze.
The dead giveaway is that Hangouts (high priority message so Doze doesn't matter) worked fine.
I'm happy it works for you. Let's hope Huawei fixes this. Most Chinese users don't really care about Google Cloud Messaging and get their notifications through other services which Doze doesn't affect, so I'm thinking they're not likely to fix it, but we'll see.
Anyone that disabled doze can check how big of an impact it is on battery life?
Also anyway to fix without root?
I solve this issue by giving priority to the important apps notification and all warking perfect now
My device is L29 with kangvip rom
somboons said:
Maybe it can help.
View attachment 3632622
Sent from my HUAWEI NXT-L29 using Tapatalk
Click to expand...
Click to collapse
Thanks mate it helped me solving the notification issue without needing to root my phone.
This does indeed work. Have a look at this thread as well.
http://forum.xda-developers.com/android/apps-games/root-doze-settings-editor-android-t3235130
I wonder if there is some parameter in an apk or in the kernel I can edit so when you flash a ROM doze is disabled by default.
Thanks buddy for that doze thread!
I disabled hangouts and the battery life got much much better
Other notifications I have set via the settings--->notification panel---->notification manager and set according to the app use
bibiner said:
Anyone that disabled doze can check how big of an impact it is on battery life?
Click to expand...
Click to collapse
No difference at all for me. Standby time is just as good. Huawei's own "Doze" still works if you want it to, also.
bibiner said:
Also anyway to fix without root?
Click to expand...
Click to collapse
Yes you can run that command with ADB without root and it will work just as well. Just be sure to have USB debugging enabled in developer options. The part about root is so that you can use Tasker to automate the process instead.
somboons said:
That is greenify app.
Sent from my HUAWEI NXT-L29 using Tapatalk
Click to expand...
Click to collapse
Thanks for the greenify hint mate!