ABSTRACT (i.e., TLDR version)
I present a way to integrate Texter; Tasker; a preferred SMS app that also gives popup notifications; and SL4A+Perl such that when using Texter, I can mark incoming SMS as read; clear notifications; clear popups; and re-sleep the phone. Profiles+scripts in the second post.
INTRODUCTION
In a nutshell: I wanted to use Tasker to remove notifications of unread SMS messages while using Texter. This proves difficult because I use an SMS app that has popup notifications. These profiles+scripts exit the popup notification, clear the unread notification, then puts your phone back to sleep.
Texter is an Android app/Google Chrome extension that lets you send SMS messages from your computer with your phone number. Super cool! It's kind of glitchy at times but overall a solid app, and it'll get better with time. It's currently in closed beta but they're adding new people all the time. I'd hop on that ASAP.
Texter clears unread SMS notifications when you hit "Close" or "Reply", but by Android design it cannot clear the notification bar and LED. I keep my phone on my desk when using my computer, so having the unread notification on both my phone and my computer are kind of annoying. So I wanted to use Tasker to clear those notifications. Turns out Tasker cannot mark messages as read itself, so I use SL4A and the Android port of my favorite scripting language, Perl. It's easy to write a script using SL4A and Perl for Android (or your language of choice - but I provide a Perl script, so you may as well use that) to clear unread SMS notifications for you.
OVERVIEW OF PROFILES
This first post will be a discussion of each profile I use; next post will have the profiles/scripts themselves, and possibly a changelog as I mess around with this system.
My system consists of 5 profiles and 1 widget-task:
WIDGET-TASK: USE TEXTY
This task simply sets or clears a variable %TEXTY, to denote if we are at a computer and would prefer to use Texter vs our phones to send SMS messages. It also sets a permanent notification and changes the widget icon to show that you're in Texter-mode vs regular SMS mode.
PROFILE: TEXTY ACTIVE
This is the heart and soul of the profile scheme. When you receive an SMS, if %TEXTY is set it fires the Perl script that clears your SMS notification, then opens your preferred SMS app to clear the notification bar. Bonus: if you use a popup SMS notification (GO SMS, Handcent, Chomp, etc), this will also clear the popup for you!
PROFILE: TEXTY DISPLAY ON/OFF
Naively using %SCREEN to denote if the screen is on/off to enable or disable Texter functionality does not work all the time - I have found that my phone sometimes lags between receiving a text message and actually popping up the notification. So if %SCREEN ~ on, the main profile might not fire the go-back-to-sleep tasks.
Thus we need a way to account for this lag. I created a new variable %TEXTYSCN that denotes when the screen is on/off, accounting for that lag. Basically, I wait 15 seconds after screen on before setting %TEXTYSCN = on; if the screen has been on for that long, it's probably because I wanted to use it.
When I set %TEXTYSCN = off, I wait 15 seconds beforehand IF IT'S ALREADY SET TO OFF. This seems weird at first, but it's kind of like an interrupt handling mechanism - if you receive a text, your screen will turn on. That starts the 15 second count before %TEXTYSCN = on - until those 15 seconds are up, %TEXTYSCN ~ off. Now that the popup notification is cleared, the display shuts off. If we flipped %TEXTYSCN = off right now and we're inside that 15 second timer, %TEXTYSCN will get set back to on - and subsequent popup notifications won't get cleared. Note that I only wait if %TEXTYSCN ~ off. If it's on, that means we're choosing to sleep the phone after we've used it for something.
[NOT SURE IF NEEDED, NEEDS MORE TESTING] PROFILE: PHONE OFFHOOK/IDLE
Not sure if I need these profiles yet - all it does is disable the main profile if we're on a call, and restart it once we hang up. GO SMS doesn't popup notify when I'm in a call, and after a call I can clear the notifications as I please. I'm not entirely sure of using the main profile during calls yet (what happens if I get a text in the middle of a call and my screen was off at the time? It'll run the main profile, GO HOME, then display off. This might be disorienting the next time I look down and I'm at the Home screen rather than the In-Call screen) so I'll just disable the clear-SMS. Maybe in a later iteration I'll disable the go-home part but clear SMS.
ON TO POST #2!
APPS YOU NEED
See post #1 for links to all required apps.
Android 2.2+
Tasker
Texter
SL4A
Perl for Android (or your interpreter of choice, but the script I provide is for Perl)
INSTALLATION <----VERY IMPORTANT! DOES NOT WORK STRAIGHT OUT OF THE BOX.
Download Tasker_Texty_V1.2.zip. Place all files ending with "prf.xml" into /sdcard/Tasker/profiles . Place Texty.tsk.xml into /sdcard/Tasker/tasks . Import all profiles and tasks by opening Tasker; hit Menu; hit Profile Data; "Import One Profile" and "Import One Task". Place markSMSread.pl into /sdcard/SL4A/scripts .
Create the Texty (it's now officially named Texter, but I didn't want to bother changing the words in the profiles, not to mention "Texty" sounds way better to me) widget on your home screen. Check out the Tasker website if you need help on how to do this.
Open up the "Texty Profile" profile. Change "Load App" from "Messaging" to your favorite SMS app (or keep it as default if that's what you prefer.)
Remove the "Type: System Lock" action, and replace it with "Display->System Lock". You will need to give Tasker administrative capabilities.
As necessary, change the "wait" values in the Texty Active; Texty Display On; and Texty Display Off profiles. See below, "Scripts and Profiles", on the rationale for this.
Enjoy the wonderful amalgamation of Texter, Tasker, and Android! Happy texting
ADVANCED: SCRIPTS AND PROFILES
I include this section redundantly so people can see what exactly goes into the setup. This way you can be confident that you're customizing your profiles exactly how you want to, and you can see my rationale for why I used certain numbers, variables, etc.
Tasker cannot clear the unread SMS notification on its own, so I use SL4A to do it. Here is the Perl script I use (you can of course use your own script and programming language if you'd like):
Code:
use strict;
use warnings;
use Android;
# See http://goo.gl/Qw0WK for original code
my $droid = Android->new();
my $msgs = $droid->smsGetMessageIds(1);
my $i = 0;
while ($msgs->{result}[$i]){
$droid->smsMarkMessageRead([$msgs->{result}[$i]], 1);
$i++;
}
I will assume you're familiar with Tasker language. At some point I will just post profiles you can import. If you need help with any steps, just ask! I'll do my best to respond in a timely fashion.
Note before importing/creating profiles: You need to make sure %TEXTY is clear on boot. I don't know if variables are cleared on phone restarts; I took no chances and wrote into my Boot profile to clear %TEXTY. If someone can let me know, that would be appreciated.
WIDGET-TASK: "TEXTY"
Initial Icon: Texty app look
Notes: You may need to write everything without the "Set Widget Icon"; make the widget; then edit the task and re-make the widget. Tasker looks for widgets to change icons, and it can't change the icon of a non-existent widget.
1) If %TEXTY ! Set
2) Notify (title: "Texty Active"; icon: whatever you want; permanent: ON)
3) Set Widget Icon (name: Texty; icon: whatever you want, I use the stock SMS icon)
4) Variable set (%TEXTY to 1)
5) Stop
6) End If
7) If (%TEXTY Is Set)
8) Set Widget Icon (name: Texty, icon: original Texty icon)
9) Notify Cancel (title:"Texty Active")
10) Variable Clear: %TEXTY
11) End If
PROFILE: TEXTY ACTIVE
Condition: Event: Received Text
Notes: Mess around with the wait statements to see if there's a sweet spot. You might find a 2 second wait might open and close your SMS program before the popup notify comes up. I'm still trying to find all the right numbers myself. (I think I've settled on 5, but that could change all willy-nilly like)
1) If %TEXTY is set
2) Wait 5 seconds
3) IF %TEXTYSCN !~ on
4) Load App: your SMS app of choice (to clear the notification bar and/or popup notifies)
5) SL4A: markSMSread.pl
6) Wait 1 second
7) Go Home
8) System Lock
9) End If
10) End If
PROFILE: DISPLAY ON
Condition: Event: Display On
Notes: Adjust the wait: if it's too long, the main profile will clear your popup notify and sleep your phone if you receive a message soon after starting to use your phone; too short and the main profile might not clear your popup notify at all [see the wait statement in the Texty Active profile]
1) If %Texty Is set
2) Wait 10 seconds
3) Variable set: %TEXTYSCN to on
4) END IF
PROFILE: DISPLAY OFF
Condition: Event: Display Off
Notes: Adjust the wait: if it's too long, the main profile won't clear your popup notify if you receive a text shortly after display turns off; too short and %TEXTYSCN might accidentally get flipped to on.
1) If %Texty is set
2) Wait 15 seconds IF %TEXTYSCN ~ off
3) Variable set: %TEXTYSCN to off
4) End if
PROFILE: PHONE OFFHOOK
Condition: Event: Phone Offhook
1) Profile Status: Texty Active -> Off IF %TEXTY is set
PROFILE: PHONE IDLE
Condition: Event: Phone Idle
1) Profile Status: Texty Active -> ON
PROFILE: CLEAR TEXTYSCN
Condition: Event: Variable cleared: %TEXTY
1) Variable Clear: %TEXTYSCN
Conclusion
I hope my work has helped anyone else as obsessive as I am about the meshing of their technology. I am of the school of thought that anything I do on my phone I should be able to do on my computer, and vice versa - I use Chrome to Phone, android2cloud, etc - I don't ever want to be tethered to any single device. These Tasker profiles have gotten me one step closer to realizing that dream.
CREDITS
brandall: for his excellent Tasker work! He was the inspiration for me to write this post up.
Max from the android-scripting Google group: for helping me create the markSMSread.pl script.
The developers of Texty, Tasker, GO SMS, and SL4A. Without them, there wouldn't be us.
TO DO
further testing to find edge cases, etc
CHANGELOG
Code:
v1.2:
-->fixed import bug - because System Lock action requires admin capabilities, Tasker would not import. Now requires user to manually add action.
-->restored markSMSread.pl workaround - Texter only clears SMS when you hit "close" or "reply", but the notification does not go away.
-->added more installation instructions
v1.1:
-->removed markSMSread.pl workaround - Texter now clears SMS notifications on its own.
-->added v1.1 .zip to easily import profiles.
v1.0:
-->initial release
Please hit the Thanks button if I helped you with your Texter experience!
Nice work mate!
Sent from my HTC Desire HD using XDA Premium App
Tasker profiles updated to v1.1! Texter now clears the SMS notification when you hit "Reply" or "Close" in Chrome. So I removed the SL4A workaround to clear SMS notifications for you. I am still testing for edge cases, and might bring back the workaround if the SMS doesn't clear the vast majority (or all) of the time. Also finally added profile .zip so you can just import your tasks instead of fiddling with the UI so much.
The Texty Active profile won't load into Tasker. It gives me an error.
bartimeus said:
The Texty Active profile won't load into Tasker. It gives me an error.
Click to expand...
Click to collapse
What's the error say? Details would be nice to help out on this.
Sorry about that, forgot my manners.
"Error: import of Texty_Active.prf.xml
failed: failed to import profile data."
Thank you for coming up with and supporting these.
bartimeus said:
Sorry about that, forgot my manners.
"Error: import of Texty_Active.prf.xml
failed: failed to import profile data."
Thank you for coming up with and supporting these.
Click to expand...
Click to collapse
Hmm, that's not a very illuminating error message What version of Tasker are you running, and what version of Android? The "Screen Lock" task in this profile requires Tasker to get admin capabilities; maybe Tasker does not allow one to import anything that requires root/admin capability.
Also, do you have the stock Messaging app installed? I use "Load App: Messaging" by default.
I am not at home right now but when I get home I will upload a profile that does not have the "Screen Lock" task. If that imports properly, you will have helped me close a tough bug thanks!
I am running version 1.0.17, Android 2.3(Cyanogenmod 7 Nightly 100) Phone is Inspire 4G.
I have the stock messaging app but use Handcent as my main one.
bartimeus said:
I am running version 1.0.17, Android 2.3(Cyanogenmod 7 Nightly 100) Phone is Inspire 4G.
I have the stock messaging app but use Handcent as my main one.
Click to expand...
Click to collapse
Try to import the attached profile. I removed the "System Lock" task. I have a feeling that'll let you import.
In other news, I think I will add back the markSMSread.pl SMS-clearing workaround. Without it, the popup notify is killed but the unread notification remains. Once you hit close/reply in Texter, it will mark the SMS as read - but that doesn't clear the notification. Once I get verification that the "System Lock" task is what's causing problems, I'll update to v1.2.
Okay, it let me import that file. Now I have all 6 profiles and the task imported. How do I switch the app it uses from Messaging to Handcent?
bartimeus said:
Okay, it let me import that file. Now I have all 6 profiles and the task imported. How do I switch the app it uses from Messaging to Handcent?
Click to expand...
Click to collapse
Great. In the Texty Active profile, hit "Open App" and select Handcent from it.
You'll also need to re-add the System Lock action (hit the plus sign, Display->System Lock) and put it under "Go Home" if you want the screen to dark after it receives a text message.
Thanks for verifying this bug for me. As I said, I will upload v1.2 with the markSMSread.pl workaround as soon as I can. I'll also remove the System Lock action; users will have to add them themselves.
Version 1.2 added to second post. It brings back the Perl workaround - Texter only clears the unread SMS notification when you hit "Reply" or "Close". Even though it clears the unread notification in the system, it does NOT clear the notification bar. (This is especially true if you're not using the stock Messaging app.)
Also, there was a bug (feature?) where Tasker could not import the "Texty Active" profile - this is because the "System Lock" action I use to sleep the phone requires admin capability. You must add this action yourself and allow Tasker admin privileges, if it asks.
Finally, install instructions updated to reflect the use of the Perl script and adding the "System Lock" action.
Thanks to bartimeus for helping debug!
Running into the same error as before when I try to import the Texty: Active profile....
What do we do after we make the widget? Do we have to hit it and activate the task and just leave it running all the time?
I couldn't find anything called "Perl for Android" on the market so I only installed SL4A, do I have to DO anything with this once I have it installed and the script in the correct folder?
Lastly, when I go in and add the the Lock command it asks me for code, what do I need to enter? It says "Error: Code: Please enter text"
bartimeus said:
Running into the same error as before when I try to import the Texty: Active profile....
Click to expand...
Click to collapse
crap. i'll look into what could be causing that. Did you import before installing SL4A? I wonder if the profile can't find SL4A upon import and then fails. In the meantime, I do list the exact steps you need to produce the profile on your own, so you could create the profile yourself. I'm really sorry about that - this is my first time writing profiles and sharing them with other people, so I'm sure there will be issues in the process.
What do we do after we make the widget? Do we have to hit it and activate the task and just leave it running all the time?
Click to expand...
Click to collapse
Hit the widget whenever you want to use Texty at your computer. When you're done, hit it again. I think it would only be useful to turn off the popup notify and kill the new-SMS notification if we're sitting at the computer. So yes, when you're using Texty, you should leave the task running the entire time.
I couldn't find anything called "Perl for Android" on the market so I only installed SL4A, do I have to DO anything with this once I have it installed and the script in the correct folder?
Click to expand...
Click to collapse
Check the link to Perl for Android in the first post. This is absolutely required - SL4A does not provide the script interpreters, just the API to use them
Lastly, when I go in and add the the Lock command it asks me for code, what do I need to enter? It says "Error: Code: Please enter text"
Click to expand...
Click to collapse
Note that there is a difference between "Lock" and "System Lock". You should be using the latter, not the former.
Okay, I figured out that it is a passcode that it wants. I couldn't find something called System Lock under Display but I will look again.
Nevermind. I am dumb. I found System Lock
I guess tasker hadn't updated in forever or something but I have it all working now. Perl Installed and SL4A installed. All seems well enough, just need to wait for a text now =P
Thank you.
bartimeus said:
Nevermind. I am dumb. I found System Lock
I guess tasker hadn't updated in forever or something but I have it all working now. Perl Installed and SL4A installed. All seems well enough, just need to wait for a text now =P
Thank you.
Click to expand...
Click to collapse
Haha, no worries! Non-market Tasker doesn't really remind you to update that often. I guess I should put in the OP that you need the latest version of Tasker; I can't guarantee older versions, as you just found.
I appreciate any feedback about the profile system I set up. I'm always trying to tweak it, and really I find myself playing with the numbers kind of regularly to hit the "sweet spot".
Been looking for something like this...great job....errr, I should say, just set this up, hope it works and if it does, then great job.
Now if only I could get something similar for all the other notifications I take action on on my computer (calendar appts, gchat etc.) Gmail works fine
I know this is wicked old, but the Perl Script does not work anymore... I have a 4.2.2 ROM and it won't mark them as read.
Related
Calendar Silencer is an app that is responsible for muting your phone during meetings / dates / movies .... and unmuting your phone when the meeting ended.
features included:
import events from all or specified calendars
creating filters based on words or phrase that you don't want your event to include
enable notification before the alarm start
choose silent mode (silent , silent + vibrate)
Precede event to now in case meeting start early
postpone event based on user's interval
open original event to edit
Auto schedule events ( auto poilot mode ) - full version feature
contacts exception - enable specified contacts to override silent mode full version feature
quick tutorial - settings
specify which calendars you want to watch - default all.
choose silent mode - silent or vibrate.
enable notifications - enable this to receive notification a minute before the event start .
choose time to scan - select how much time you wish for the app to scan ahead.
quick tutorial - settings
from the main screen slide left or press the right button on the top right corner to move to events screen.
from the events screen tap menu and "update from calendar" to get a list updated events.
tap on an event to get list of actions.
actions include :
schedule - this will schedule the event to mute when the event start
delete - delete the event from application database - not from the calendar itself
create filters - create filters from this event's title
start event now - start event now and schedule unmute when the events suppose to end for early starting meeting
postpone event for meeting the goes beyond expected
open event - open original event event in calendar for editing purpose
from the events screen slide left or press the right button on the top right corner to move to filters screen.
note that in free version there is only 1 type of filters which are "ignore this" filter.
this filter type will specify words that if found in the event title the event will be ignored/
full version feature - auto schedule filter
this filter type will auto schedule an event if the the filter exist in the event title/
from the filters screen slide left or press the right button on the top right corner to move to exceptions screen. this screen can be reached from main screen
select contacts for whom the phone will ring even in silent mode
http://market.android.com/details?id=com.swarly.silencer.app
enjoy and rate
Jesus... This is pretty darn handy for school.
Testing it now!
very handy...wish this had been around sooner as I bought Tasker and configured a bunch of profiles to serve the same purpose as what this app seems to do much more simply. Looks great
Not bad
How about Touchdown support? That would make this incredibly handy for Exchange users!
navalynt said:
How about Touchdown support? That would make this incredibly handy for Exchange users!
Click to expand...
Click to collapse
Touchdown actually does not sync anything to the device.
since this app read local synced events it can't read Touchdown settings or data (events for that matter).
If you wish to use Exchange calendar you can always sync your exchange account to the device using ActiveSync like this
settings -> accounts and sync -> add account -> Microsoft Exchange ActiveSync
once you synced you device this app will be able to read Exchange calendar.
anyway thanks for the advice and ill try to add support for remote Exchange
update:
i added an "add new calendar account " button in settings for those who don't have their account configured
I bought the full version but just can't get it to work.
I went to "Events list" and pressed menu > Update from calendar, and I can see all my events in the list. But it just says "will schedule - event".
Then I go to the "Filters list" and see "all. schedule", yet my phone does not go silent when my events start.
The on/off button is very confusing. When the button is red and says "off", does it mean that it is off, or that I should press it if I wish to turn it off?
Thanks!
8ESP said:
I bought the full version but just can't get it to work.
I went to "Events list" and pressed menu > Update from calendar, and I can see all my events in the list. But it just says "will schedule - event".
Then I go to the "Filters list" and see "all. schedule", yet my phone does not go silent when my events start.
The on/off button is very confusing. When the button is red and says "off", does it mean that it is off, or that I should press it if I wish to turn it off?
Thanks!
Click to expand...
Click to collapse
Hi.
the on/off button indicate the current state, meaning when the button is green and it's say "on" that mean that auto schedule is enabled
"all schedule" is the default filter that indicate that all events will be scheduled.
please pay attention that even event will be scheduled automatically only if the on/off button is in "on" state.
Pay attention that Calendar Silencer will not schedule events that already in progress, for example if you have event that start in 12:00 and you started the auto schedule in 12:05 the event will not be schedule.
if you enabled notifications please notice that the notification will disappear once the event has started, pressing the notification will clear the notification but also will cancel the alarm
let me know if have any more problems
Still nothing.
http://i.imgur.com/4avGn.png
http://i.imgur.com/Upp6O.png
http://i.imgur.com/U0UXg.png
What am I missing?
MIUI rom HTC Desire.
*edit*
It was MIUIs fault, thanks for the support Swarly!
The app now works brilliantly! Highly recommended!
fix for MIUI Rom
Disable option Settings>Programs>Calls>Anti wiretapping and it should work
I've been using a different app that seems to have this same feature set, and has been around longer.
How is this better than other competing apps that perform the same functions?
timehunter said:
I've been using a different app that seems to have this same feature set, and has been around longer.
How is this better than other competing apps that perform the same functions?
Click to expand...
Click to collapse
I cant compare these competing apps you are talking about because i don't know exactly what apps are you talking about .
I can answer you this:
before i wrote this app i looked in the market for something that will fulfill these requirements:
easy to use
work with synced calendars like exchange or Gmail calendar
will have to option to fire and forget
i downloaded several apps including paid ones and I couldn't find what i was looking for.
the ones that was simple couldn't work with synced calendars.
and those who could work with synced calendars were overkill ( profile apps that could do almost anything ) were to complicated to operate and demanded a lot of configurations and frustration.
So I decided to do my best to fulfill the goals i wrote to myself and try to keep it as simple as possible .
Because I cant look at every tool/app that exist in the market there may be an app out there that does serve the same functionality , but odds are that it either not do exactly the same or is a lot more complicated then this one.
Regards
Swarly
error during level 2
i've been using tasker but recently i starder cleaning my app list and noticed that i was using a mighty appp like tasker for just silencing the phoe when i was "busy" in my calendar.
i found your app which probably does what i want but i got intro trouble with it. i get an error when i try to turn it on (error during level 2) and the app crashes when i want to switch to the events tab (second tab).
also i haven't been able to test the filter option: i just want my phone to go silent when o am "busy" in the calendar - that's it. does the filter option allow for such a setup?
I've been looking for something like this since I first got an android phone THanks!
cpitzu said:
i've been using tasker but recently i starder cleaning my app list and noticed that i was using a mighty appp like tasker for just silencing the phoe when i was "busy" in my calendar.
i found your app which probably does what i want but i got intro trouble with it. i get an error when i try to turn it on (error during level 2) and the app crashes when i want to switch to the events tab (second tab).
also i haven't been able to test the filter option: i just want my phone to go silent when o am "busy" in the calendar - that's it. does the filter option allow for such a setup?
Click to expand...
Click to collapse
hi
Unfortunately busy mode is not yet supported in this app but its a good idea i will add asap.
please check the program version I'm updating and fixing bug almost on daily basis.
the current program version is 1.2.24
additionally if you can please report the problem using the report error button so i can have an idea about where to start looking for problems
about the error please let me know what kind of device you have
finally I started my semester and once the courses started i found some bugs and problems with my app
* fixed bug for overlapping event
* fixed bug with contact exception functionality
* minor bugs regarding event scheduling were fixed
I'll publish another big update soon that will be focused on performance.
as promised I released big update
major Performance update - from now list load faster and scroll much smother
overlaping event detection method was changed from the core from now no more false detection that caused problems
added warings to warn users that don't have calendars installed
as always I"m open to new suggestions and improvement ideas
I've posted this before, but it got buried and other people have asked about it so I figured I'd put it in its own thread. I find the notification light very annoying at night, but the only way I could find to shut off the notifications was buggy at best. This way will allow you to pick whatever triggers you have access too in tasker to control whether the light is allowed to turn on or not.
Some background: when a notification comes in, the system sets the file led_pattern in /sys/devices/virtual/sec/led to something non-zero. 3 is a slow blinking blue light, 1 is solid red, I forget what the others are now. When the screen is turned on, this is reset to zero, and when the screen is turned off, if the notification bar hasn't been opened (and the program with the notification hasn't been opened) the value is reset to something non-zero. So, I created a simple task to change the value back to zero:
Create a new task, then select Script>Shell. Enter the following command:
echo 0 > /sys/devices/virtual/sec/led/led_pattern
Check the 'Use Root' box
Then your task is done. Try it once to make sure you have accepted whatever superuser popups (you'll need to always allow this for it to work on its own).
Now create a profile, and for the context select Event>UI>Notification. You may need to check tasker on the accessibility menu if you haven't already (it will prompt you if necessary). Add whatever other contexts you want (I have a variable that's set when I turn on my nighttime menu that I check for so the light will blink during the day but not at night). You could easily just pick a block of time to turn it off instead. If you don't add other contexts this will always block your light, so make sure you've done some check to block it only at night. Add the task you created to this profile.
Next create another profile with the context State>Display>Display State set to Off, and add in the other secondary (ie night time) contexts. Call the same task you created above. This will prevent the light coming back on if you turn the display on and off at night after receiving a notification.
The only quirk I've found so far is that if you receive a google voice text, the light instantly turns purplish/pink normally. On my phone it will come on for a split second before tasker can kill it.
If you have any issues with this please let me know and I'll see what I can figure out.
I turn my phone over so the light and screen are face down. Case has a lip on it so screen doesn't touch the table. Problem solved.
-Hai guise don't feel like looking at 5 pages but I haz problems on the pre-alpha release and I don't know why.
joshindc said:
I've posted this before, but it got buried and other people have asked about it so I figured I'd put it in its own thread. I find the notification light very annoying at night, but the only way I could find to shut off the notifications was buggy at best. This way will allow you to pick whatever triggers you have access too in tasker to control whether the light is allowed to turn on or not.
Some background: when a notification comes in, the system sets the file led_pattern in /sys/devices/virtual/sec/led to something non-zero. 3 is a slow blinking blue light, 1 is solid red, I forget what the others are now. When the screen is turned on, this is reset to zero, and when the screen is turned off, if the notification bar hasn't been opened (and the program with the notification hasn't been opened) the value is reset to something non-zero. So, I created a simple task to change the value back to zero:
Create a new task, then select Script>Shell. Enter the following command:
echo 0 > /sys/devices/virtual/sec/led/led_pattern
Check the 'Use Root' box
Then your task is done. Try it once to make sure you have accepted whatever superuser popups (you'll need to always allow this for it to work on its own).
Now create a profile, and for the context select Event>UI>Notification. You may need to check tasker on the accessibility menu if you haven't already (it will prompt you if necessary). Add whatever other contexts you want (I have a variable that's set when I turn on my nighttime menu that I check for so the light will blink during the day but not at night). You could easily just pick a block of time to turn it off instead. If you don't add other contexts this will always block your light, so make sure you've done some check to block it only at night. Add the task you created to this profile.
Next create another profile with the context State>Display>Display State set to Off, and add in the other secondary (ie night time) contexts. Call the same task you created above. This will prevent the light coming back on if you turn the display on and off at night after receiving a notification.
The only quirk I've found so far is that if you receive a google voice text, the light instantly turns purplish/pink normally. On my phone it will come on for a split second before tasker can kill it.
If you have any issues with this please let me know and I'll see what I can figure out.
Click to expand...
Click to collapse
Tasker is a confusing app to me. I've tried to enter this in a few times but can't seem to get it to work. Is there any chance you could help me out and let me know more of a step by step? This guide seems to jump around a bit (it could be my extreme lack of experience with Tasker). This sounds like it is exactly what I am looking for though. The led on the GS3 is so freaking bright it lights up my whole room when it is charging at night. I *could* turn it over as suggested above but I have two problems with that:
A) We are better than our phones, aren't we? We should be able to get them to bend however we want! Why compromise?
B) I use my phone as my alarm clock and I don't want to fumble around to flip it over before I can silence it while I'm still mostly asleep.
Thanks for the guide. I will have to give this a try. I tried something else but it didn't seem to have any effect. Any idea where to find the other codes to make the LED turn on differently when you want?
---------- Post added at 06:29 PM ---------- Previous post was at 06:24 PM ----------
Relentless D said:
Tasker is a confusing app to me. I've tried to enter this in a few times but can't seem to get it to work. Is there any chance you could help me out and let me know more of a step by step? This guide seems to jump around a bit (it could be my extreme lack of experience with Tasker). This sounds like it is exactly what I am looking for though. The led on the GS3 is so freaking bright it lights up my whole room when it is charging at night. I *could* turn it over as suggested above but I have two problems with that:
A) We are better than our phones, aren't we? We should be able to get them to bend however we want! Why compromise?
B) I use my phone as my alarm clock and I don't want to fumble around to flip it over before I can silence it while I'm still mostly asleep.
Click to expand...
Click to collapse
Don't know if you are aware or not, but you can turn off the LED while charging using the build in settings. Go to Settings -> LED indicator and uncheck Charging. It shouldn't light up at all until you get some kind of notification.
ADC_112358132134 said:
Thanks for the guide. I will have to give this a try. I tried something else but it didn't seem to have any effect. Any idea where to find the other codes to make the LED turn on differently when you want?
---------- Post added at 06:29 PM ---------- Previous post was at 06:24 PM ----------
Don't know if you are aware or not, but you can turn off the LED while charging using the build in settings. Go to Settings -> LED indicator and uncheck Charging. It shouldn't light up at all until you get some kind of notification.
Click to expand...
Click to collapse
Yea I know. The thing is that I would like it to light up while charging (and change color when charged) just not between 11PM and 7AM
So, I haven't tested it for this (although I am now...) because I just have the charging LED setting turned off. I think this should work fine, although if you've killed the battery full notification you might get the green light coming on once charging completes (which you can probably deal with with an additional profile). Here's a more detailed description of the task setup:
1) Open Tasker and go to the 'Tasks' tab at the top of the screen.
2) Click on the green [+] at the bottom of the page to create a new task. Then name it something (LED kill?) and tap the green check button.
3) Click the [+] in the lower right hand corner to add an Action to your task.
4) Select 'Script', then 'Run Shell' from the Menus that pop up.
5) Under 'Command' type "echo 0 > /sys/devices/virtual/sec/led/led_pattern" without the quotes
6) Check the 'Use Root' box, then click the green check at the bottom of the window.
7) Now you should see the Task Edit window. Click the blue 'play' button at the bottom right of the window to run the task now. If you get a Superuser popup make sure you've checked the box to remember your selection, and accept the SU request. Now tap the green check box to save the task.
* Now you have a task that can turn off the light, but you need a way to trigger it. In tasker you do this by setting up profiles, which you can think of as triggers that will call the task. We want to trigger it to kill the LED whenever the phone turns it on. The phone will turn on or change the light at 2 different times:
A) When you receive a notification
B) When you turn off the screen (This will 'reset' the led if you turn on the screen and then turn it back off without clearing the notification) It will also turn on the led if the phone is charging and you've left that setting checked.
So, lets proceed:
8) Tap the 'Profiles' Tab at the top of the screen.
9) Tap the green [+] to create a new profile. Name it something like "Notification Kill" and click the green check box.
10) Select 'Event', then 'UI', then 'Notification' from the menus that pop up. Click the green check at the bottom of the Notification window that pops up (all the default settings are fine).
10a) At this point I think I was prompted the first time I did this to add Tasker to the accessibility permissions. If this happens, scroll down in the accessibility settings window that pops up and check the box next to Tasker. Then hit the back button to go back to Tasker.
11) Now select the task you just created (LED Kill) from the Task Selection window that pops up
* Now if you leave Tasker you should be blocking all notification LED lights. But you only want to turn them off at night! So you need to add another Context to this profile.
12) Long press on the Context (left hand side of the profile you just created where it says 'Notification *,*' and has a Orange ! triangle)
13) Select 'Add' from the popup, then select 'Time'
14) Pick the time range that you want the LED turned *OFF*. In your case you should pick From: 23:00 and To: 07:00.
15) Click the green Check and you're done with this profile.
* Now you've taken care of the (A) reason for the light coming on. But you need to take care of (B) as well, in case you check your phone during the 'night' hours, or if it's plugged in.
16) Repeat step (9), but name it 'ScreenOffLEDKill' or something easier to type.
17) Select 'State', then 'Display', then 'Display State' from the popup menus.
18) Make sure 'Off' is selected from the 'Is' dropdown menu, and click the green check box.
19) Select the task you created earlier again (LED Kill)
20) Repeat Steps 12-15 for this profile (Long press on 'Display State Off'...)
Now you should be set! If this still isn't working let me know and I'll try and troubleshoot it with you.
Relentless D said:
Yea I know. The thing is that I would like it to light up while charging (and change color when charged) just not between 11PM and 7AM
Click to expand...
Click to collapse
ADC_112358132134 said:
Thanks for the guide. I will have to give this a try. I tried something else but it didn't seem to have any effect. Any idea where to find the other codes to make the LED turn on differently when you want?
Click to expand...
Click to collapse
Just try different numbers. You can test it out and actually make the lights come on with the screen on from terminal emulator/adb or play with the tasker shell options. Try the following commands after getting superuser rights (by typing 'su' in the terminal emulator):
echo 7 > /sys/devices/virtual/sec/led/led_pattern
You get a slightly pulsing blue led. Substitute other numbers for the 7 and play around. You can turn off the LED by setting it to 0. You can also try echoing a value to led_b, led_g, or led_r, which will turn on the blue, green, and red leds (probably 255 is the maximum value). From what I've seen, whatever you set last overwrites whatever else you've done. So, if you set pattern to 7, then led_b to 255, the led will switch to solid blue from the pulsing light. If you then set led_r to 100, it will switch to dim red, but it won't maintain the led_b setting. I don't really have any interest in further customizing the led so I haven't played around with it much more. I haven't really figured out how to use led_blink either. If you find out more post here!
Josh
joshindc said:
Now you should be set! If this still isn't working let me know and I'll try and troubleshoot it with you.
Click to expand...
Click to collapse
Beautiful! I'll punch this in tomorrow at work. Thank you so much for helping me out!
Thank you so much for this post. Your method works perfectly. This is exactly something that I was trying to do but couldn't figure out. Great job! :good:
Just FYI, when Tasker updates from the market, it appears that sometimes the update disables the tasker accessibility service. If that happens this technique will no longer work. So, make sure to check that the accessibility service is still enabled after a Tasker update.
Thought I add a mapping of the colors to save some time to the next person...
Code:
0 = Disabled
1 = Static Red
2 = Blinking red (fast)
3 = Blinking blue (slow)
4 = Blinking red (slow)
5 = Green
6 = Static blue
7 = Static pulsing blue
Awesome, informative thread! Giving it a bump for those who want more, better information. Could anybody post the XML code in color-coded format? It helps me understand how to set it up exactly. Thanks to you for the hard work!
joshindc said:
I haven't really figured out how to use led_blink either. If you find out more post here!
Click to expand...
Click to collapse
This is a bit off topic, but since you went there I'll share some of my findings on led_blink. It turns out you can use it to create any color, but I haven't figured out how to make it... uh... blink.
At first, since led_blink usually contains 0 0 0, I thought it was simply the rgb colors with values up to 255 (just like with led_r, led_g, led_b). But, after a lot of trial-and-error, I found that it's actually hex. But that's not all. You also have to send led_blink additional information. Let me try to explain.
If you echo a string of numbers to led_blink, it seems to ignore the first two. The next two are red, then green, then blue (spaces are interpreted as zero, it seems). So, if you sent:
echo 00ff0000 > /sys/devices/virtual/sec/led/led_blink
you'd get a solid bright red light. But, here's the thing... led_blink would only contain "ff 0 0", since the first two numbers don't seem to stick. If you tried to send green the way you would intuitively think ("0 255 0"), you'd get led_blink set to "25 50 0" - which, to be fair, is still mostly green. Using the hex values plus the leading two digits, you can make the led any solid color you want.
So, what's left to figure out is:
What do the first two numbers mean, if anything? It doesn't seem to matter what they are.
How do you make it blink?
I swear, at one point when I was messing around with numbers (I wrote a Tasker task to make it easier to write to and read from led_blink) that I saw it rapidly blinking, but I don't know how I got there.
If someone can figure out how to get it blinking, Tasker would become a serious Light Flow alternative.
LightFlow can handle this and all notification aspects so much easier and with 1 button click (versus Tasker).
I use the hell out of Tasker, but I use LightFlow for ALL notifications - lights, sounds, vibrations, pop-up windows, etc. And you can set it to kill any notifications of any type you set by time of day. At 10:30pm all my lights stop flashing and come back on at 6:30am for example.
Does it work on any device? Or it is only for Galaxy S3
Sent from my GT-I9300 using Tapatalk 2
iirc led control from the play store has "night time" setting that will disable the led during times you specify
I'm using this command to turn off the led for specific Whatsapp groups, using specific contexts.
Sent from my GT-I9300 using Tapatalk 2
joshindc said:
So, I haven't tested it for this (although I am now...) because I just have the charging LED setting turned off. I think this should work fine, although if you've killed the battery full notification you might get the green light coming on once charging completes (which you can probably deal with with an additional profile). Here's a more detailed description of the task setup:
1) Open Tasker and go to the 'Tasks' tab at the top of the screen.
2) Click on the green [+] at the bottom of the page to create a new task. Then name it something (LED kill?) and tap the green check button.
3) Click the [+] in the lower right hand corner to add an Action to your task.
4) Select 'Script', then 'Run Shell' from the Menus that pop up.
5) Under 'Command' type "echo 0 > /sys/devices/virtual/sec/led/led_pattern" without the quotes
6) Check the 'Use Root' box, then click the green check at the bottom of the window.
7) Now you should see the Task Edit window. Click the blue 'play' button at the bottom right of the window to run the task now. If you get a Superuser popup make sure you've checked the box to remember your selection, and accept the SU request. Now tap the green check box to save the task.
* Now you have a task that can turn off the light, but you need a way to trigger it. In tasker you do this by setting up profiles, which you can think of as triggers that will call the task. We want to trigger it to kill the LED whenever the phone turns it on. The phone will turn on or change the light at 2 different times:
A) When you receive a notification
B) When you turn off the screen (This will 'reset' the led if you turn on the screen and then turn it back off without clearing the notification) It will also turn on the led if the phone is charging and you've left that setting checked.
So, lets proceed:
8) Tap the 'Profiles' Tab at the top of the screen.
9) Tap the green [+] to create a new profile. Name it something like "Notification Kill" and click the green check box.
10) Select 'Event', then 'UI', then 'Notification' from the menus that pop up. Click the green check at the bottom of the Notification window that pops up (all the default settings are fine).
10a) At this point I think I was prompted the first time I did this to add Tasker to the accessibility permissions. If this happens, scroll down in the accessibility settings window that pops up and check the box next to Tasker. Then hit the back button to go back to Tasker.
11) Now select the task you just created (LED Kill) from the Task Selection window that pops up
* Now if you leave Tasker you should be blocking all notification LED lights. But you only want to turn them off at night! So you need to add another Context to this profile.
12) Long press on the Context (left hand side of the profile you just created where it says 'Notification *,*' and has a Orange ! triangle)
13) Select 'Add' from the popup, then select 'Time'
14) Pick the time range that you want the LED turned *OFF*. In your case you should pick From: 23:00 and To: 07:00.
15) Click the green Check and you're done with this profile.
* Now you've taken care of the (A) reason for the light coming on. But you need to take care of (B) as well, in case you check your phone during the 'night' hours, or if it's plugged in.
16) Repeat step (9), but name it 'ScreenOffLEDKill' or something easier to type.
17) Select 'State', then 'Display', then 'Display State' from the popup menus.
18) Make sure 'Off' is selected from the 'Is' dropdown menu, and click the green check box.
19) Select the task you created earlier again (LED Kill)
20) Repeat Steps 12-15 for this profile (Long press on 'Display State Off'...)
Now you should be set! If this still isn't working let me know and I'll try and troubleshoot it with you.
Click to expand...
Click to collapse
I have à Sony xperia Z with jelly bean.
Do you know where i can find the folder there?
In the folder sys/devices/virtual there is no folder sec....
I can't find where i can turn off the charging led at night.
Thanks @joshindc! You are the man. I've been looking for something like this forever. This LED Profile works great! Thanks again. :highfive:
Cheers.
joshindc said:
So, I haven't tested it for this (although I am now...) because I just have the charging LED setting turned off. I think this should work fine, although if you've killed the battery full notification you might get the green light coming on once charging completes (which you can probably deal with with an additional profile). Here's a more detailed description of the task setup:
1) Open Tasker and go to the 'Tasks' tab at the top of the screen.
2) Click on the green [+] at the bottom of the page to create a new task. Then name it something (LED kill?) and tap the green check button.
3) Click the [+] in the lower right hand corner to add an Action to your task.
4) Select 'Script', then 'Run Shell' from the Menus that pop up.
5) Under 'Command' type "echo 0 > /sys/devices/virtual/sec/led/led_pattern" without the quotes
6) Check the 'Use Root' box, then click the green check at the bottom of the window.
7) Now you should see the Task Edit window. Click the blue 'play' button at the bottom right of the window to run the task now. If you get a Superuser popup make sure you've checked the box to remember your selection, and accept the SU request. Now tap the green check box to save the task.
* Now you have a task that can turn off the light, but you need a way to trigger it. In tasker you do this by setting up profiles, which you can think of as triggers that will call the task. We want to trigger it to kill the LED whenever the phone turns it on. The phone will turn on or change the light at 2 different times:
A) When you receive a notification
B) When you turn off the screen (This will 'reset' the led if you turn on the screen and then turn it back off without clearing the notification) It will also turn on the led if the phone is charging and you've left that setting checked.
So, lets proceed:
8) Tap the 'Profiles' Tab at the top of the screen.
9) Tap the green [+] to create a new profile. Name it something like "Notification Kill" and click the green check box.
10) Select 'Event', then 'UI', then 'Notification' from the menus that pop up. Click the green check at the bottom of the Notification window that pops up (all the default settings are fine).
10a) At this point I think I was prompted the first time I did this to add Tasker to the accessibility permissions. If this happens, scroll down in the accessibility settings window that pops up and check the box next to Tasker. Then hit the back button to go back to Tasker.
11) Now select the task you just created (LED Kill) from the Task Selection window that pops up
* Now if you leave Tasker you should be blocking all notification LED lights. But you only want to turn them off at night! So you need to add another Context to this profile.
12) Long press on the Context (left hand side of the profile you just created where it says 'Notification *,*' and has a Orange ! triangle)
13) Select 'Add' from the popup, then select 'Time'
14) Pick the time range that you want the LED turned *OFF*. In your case you should pick From: 23:00 and To: 07:00.
15) Click the green Check and you're done with this profile.
* Now you've taken care of the (A) reason for the light coming on. But you need to take care of (B) as well, in case you check your phone during the 'night' hours, or if it's plugged in.
16) Repeat step (9), but name it 'ScreenOffLEDKill' or something easier to type.
17) Select 'State', then 'Display', then 'Display State' from the popup menus.
18) Make sure 'Off' is selected from the 'Is' dropdown menu, and click the green check box.
19) Select the task you created earlier again (LED Kill)
20) Repeat Steps 12-15 for this profile (Long press on 'Display State Off'...)
Now you should be set! If this still isn't working let me know and I'll try and troubleshoot it with you.
Click to expand...
Click to collapse
Seems cool. Will try out
I stumbled upon a Tasker plugin from BlackDino that lets you change the Galaxy S3 LED settings. It might be a bit easier to use and gives some extra functionality.
http://forum.xda-developers.com/showthread.php?t=2117829
Hi
After 2 years developing and improving Rules Engine I have created Automated Device for 4.0+ devices.
This program is rules engine that let your device behave automatically according to conditions and execute actions
Please submit any comment, error, suggestion here.
Android Market link
Direct link to APK
Automated Device is an application designed to let you automate the behaviour of your device. It is based in rules. The user can define many rules to define the device's state in different situations.
A rule is defined by:
Conditions: When every condition (AND clause) o at least one (OR clause) in a rule is satisfied then the rule is satisfied. Examples:
From Monday to Friday, between 12:00 and 05:00 (Time-Date condition)
To be inside (or outside) my home (Position condition)
Bluetooth state is ON (Hardware condition)
Battery level between 0% and 20%
Incoming phone call
Incoming SMS containing some word
Power state, battery or connected
Screen state
Other rule is matched or not
Other program is running or not
Phone state (ringing...)
Calendar appointments. This condition is matched when current date is inside of the appointment and the appointment text contain a user defined word
Brightness mode
autosync state
Network type (GPRS, HSPA, CDMA, LTE, etc)
Device connectivity state
Headphone state
Car mode
Dim state
Wifi hotspot
To be connected to a wifi network specified by its name
To receive a SMS/MMS comming from some phone number or with its text containing some word or phase
Ambient light
Ambient temperature
Pressure
Proximity sensor level
Some phone number is calling you (ringin), or is in call with you, or just called you
Mobile operator name
Actions to be executed when the rule passes from unmached to matched: Actions to be executed when every condition is satisfied. Each one can be applied once or periodically while the rule is matched Examples:
Set Bluetooth OFF
Set device volume
Launch a program
Kill a program
Apply a profile. A profile is compound by actions. So when the rule applies a profile it simply execute its associated actions.
Set different kinds of sound levels (system, notification, alarms, etc)
Set Brightness mode (automatic / manual) and bright level
Set autosync state
Play a song
Send SMS
Send Email. You can include many variables, like free memory and disk, last caller, battery statistics, sensors values (pressure, light, temperature, etc)
Car mode
Set wallpaper
Set ringtone (android ringtone or user mp3)
Screen off timeout
Dim state
Wifi hotspot
Play a system notification
Vibrate some milliseconds
Show popup message with free text and variables
Show a tob bar notification with free text and variables
Enable / Disable rules.
Sent variables (temperature, position, etc) to a web server as HTTP parameters
Open system dialogs, like 3G/2G, Tethering, etc
Actions to be executed when the rule passes from matched to unmatched. (The same ones like the above section)
The device broadcast many events, like battery level, time, etc. Those events are processed by Automated Device and the rules are evaluated.
Important: When a rule is applied then It wont be applied again until it doesn't satisfy it previously. For example, if a rule condition is "Battery level less than 15%" and the action is "Play a song" and current battery level is 10% then the song will play. But it wont play again until the rule wont be satisfied and then satisfied again. So if the battery level raises to 20% and then decreases again to 8% then it will play the song again. This avoid loops so a rule is executed many times.
Sections:
SWITCHERS: This window lets you change the state of Wifi, Bluetooth, etc. It also lets you set a time-out. When the time expires the program will set the previous state. It also lets you "lock" a profile with/without time limit. For example, if you go the cinema you could lock the profile "Silent". When Automated Device is locked it wont execute any rule
PROFILES: A profile is a set of actions. This section lets you define and apply right now a profile. For example, you could create the profile "Meeting". Its actions would be speaker to vibrate, flight mode and send a SMS. The three actions would be applied. You could establish a timeout. During this time the program WONT apply any rule. In this way the program wont apply other rule that could change the speaker state, for example. Once the timer expires then the engine will be enabled again.
NEW PROFILE: This dialog lets you choose a name and description for the new profile.
ACTIONS: Here you can choose the set of actions associated to the profile.
RULES: In this windows you can manage your rules and create new ones. If the background of the rule is RED it means the rule isn't met right now. If the background is GREEN it means the rule is met right now.
RULE INFORMATION: This screen lets you manage the name and description and shows how many conditions and actions the rule has. It lets you set the priority of the rule. If two rules match at the same time then this priority will solve conflicts. For example, if both rules are going to change the audio state. It also lets you add/edit/remote more actions/conditions.
RULE CONDITIONS: This screen lets you add / remove / edit conditions. There are several types of conditions:
WEEK DAY AND TIME: You can select some weekdays and then a begin time and end time. For example, Monday and Tuesday from 22:00 to 06:00
ENTER/EXIT A PLACE: You must choose a location and a radius. So if you choose a "Enter a place condition" then the condition will be met if you are inside. If you choose "Exit a a place condition" then the condition will be met if you are outside.
STATUS CONDITIONS: There are many conditions related with some hardware status. For example, you could use WIFI ON. This condition is matched when the WIFI state is ON
LOG: This screen shows the application log. Each log line has a category: Debug, Info, Warning and Error. Here you know what happens inside the program. You can see a rules history. And you can clear it and export it by email.
SETTINGS: Hare you configure the program.
Launch at boot time: If selected the the program will be launched at boot time.
Log level. This options lets you choose what kind of log events you want to store.
Automated Device enabled. If disabled then It wont process events.
Show icon notificacion in the top bar.
EXPERIMENTAL: Location autorefresh interval. By default Android doesnt allow location changes when the screen is off. This option try to fix it.
Log changes
V2.0.45 (2014-03-08)
Compatibility between accessibility service and OK Google
NFC tags can be detected with the program in background
V2.0.38 (2014-03-04)
Action HTTP Request uses GET instead of POST
New Variable. Last HTTP Status for action HTTP request
Flag feature action. Set value to a Variable value
Accessibility can be disabled
Bug fixing
V2.0.37 (2014-03-02)
Condition NFC. Use your NFC tags as conditions
Option to disable Accessibility service
Bug fixing
V2.0.30 (2014-02-21)
New action: Text speech. You can use free text and variables
New Flag: Last top bar notification text
New Condition: Detect a top bar notification. You can filter by program sender, text or none
With these features you can, for example, let AD read aloud the notifications coming from gmail, line, etc
New option in home windows: Export. It takes your rules and convert them into text to share it with developer and other users
V2.0.27 (2014-02-19)
Improved disable/enable lock screen
Bug fixing
V2.0.24 (2014-02-18)
Improved Sound action: Added BT call sound
Vibrate if internal error is optional
Improved Variables: time, date and flag value
Improved Bar Notification action: persistent. You decide if the user can dismiss the notification with his finger
Improved set flag action: Persistent. Choose if the flag is removed when a rule is modified and all the rules are re-evaluated
Improved set flag action: Numeric operations: You can increment or decrement a flag (if numeric)
Improved flag condition: New comparators: bigger, bigger or equals, lower, lower or equals
V2.0.43 (2014-03-07)
Flight mode switcher, condition and action enabled. Only for rooted devices with Xposed and Flight mode helper
V2.0.36 (2014-02-25)
Option backup the database
Option restore the database from a previous version
So you can do a backup, play with new rules, conditions....and restore if you are not happy with the result
Support for xlarge screens
V2.0.23 (2014-02-17)
Improved action Show notification bar. The user can select a custom icon
New action: Dismiss a notification bar. So you can, for example, display a notification bar when a rule or profile is applied and remove it when it doesnt match
Bug fixing
V2.0.21 (2014-02-15)
New action: set call forwarding status
New conditions: On booting and On shutting down
Bug fixing
V2.0.18 (2014-02-14)
Switcher to enable/disable lock screen
New action: Enable / Disable lock screen
V2.0.17 (2014-02-13)
Improved location condition
New action: Set a flag value
New condition: check a flag value
See active flags from home window menu
V2.0.22 (2014-02-16)
New action: Send Android Intent
New action: Call forwarding (international)
Bug fixing
V2.0.16 (2014-02-12)
Bug fixing
Program status condition allows to search between all the processes or only the foreground ones
V2.0.15 (2014-02-11)
New Location system: Google play services.Check settings page
Added command in home window to recreate the database
V2.0.14 (2014-02-10)
Bug fixing
Improved BT connected device. Now works with multiple devices at the same time
V2.0.11 (2014-02-09
Bug fixing
Added compatibility without telephony system, like tablets
New condition: Phone Signal Strength
New condition: Device orientation (facing up/down)
V2.0.8 (2014-02-08)
Periodic actions are executed in a background thread, solving problems related with network actions (send mail, http post)
Bug fixing
V2.0.7 (2014-02-07)
New condition: Dock state
V2.0.6 (2014-02-06)
Actions execution delay now included in Action repeat window
Changed bar notification icon (white)
New Condition: Battery temperature
V2.0.5 (2014-02-05)
New condition: Lock screen state
V2.0.4 (2014-02-04)
Bug fixing....
V2.0.3 (2014-02-03)
Fixed send email action
Bug fixing...
V2.0.2 (2014-01-27)
Back button in home page hides the GUI
Menu button in home page shows menu drawer
V2.0.1 (2014-01-26)
Fix icon bar notification
Several optimizations
V2.0 (2014-01-15)
Automated Device is ported to Android 4.x and named Automated Device to leverage android 4.x power
Fixed automated backup/restore data from/to google account
reuploaded apk to set release google maps api key
danielherrero said:
reuploaded apk to set release google maps api key
Click to expand...
Click to collapse
Added to Android Market
https://play.google.com/store/apps/details?id=com.dhr.automateddevice
Looks promising
Sent from my LG-P990 using xda app-developers app
V2.0.1 Uploaded
Fix icon bar notification
Several optimizations
Uploaded to market V2.0.2
Back button in home page hides the GUI
Menu button in home page shows menu drawer
good work :good:
Awesome
very handy & user-friendly app :good:
it is easier to use than tasker :laugh:
Thanks!!
Enviado desde mi SM-N9005 usando Tapatalk 4
Lets try it
Vamos a probarla, compadre madrileño
It is not compatible with my Nexus 7 2013 ?
Gesendet von meinem Nexus 7 mit Tapatalk
NFC-SMARTAGS said:
Can we use it with nfc
Envoyé de mon GT-S6500 en utilisant Tapatalk
Click to expand...
Click to collapse
Currently I am programming one condition and one action with nfc
Enviado desde mi SM-N9005 usando Tapatalk 4
Strange. I wonder what condition fails...
Enviado desde mi SM-N9005 usando Tapatalk 4
Hi there,
When I choose 'send email' as an action on a lost wifi connection it doesn't do anything, even though the phone switches to 3G
Hallahan said:
Hi there,
When I choose 'send email' as an action on a lost wifi connection it doesn't do anything, even though the phone switches to 3G
Click to expand...
Click to collapse
Thanks, I already know it. I use a gmail account to send mails but google is rejecting them because they are very far (Spain, USA). I am going to create web service in my web server. So the device will contact my server and this one will send the email
danielherrero said:
Thanks, I already know it. I use a gmail account to send mails but google is rejecting them because they are very far (Spain, USA). I am going to create web service in my web server. So the device will contact my server and this one will send the email
Click to expand...
Click to collapse
Isn't it just the fact that Google only accepts sending email when you, or I, log on to their smtp servers using a valid username and password? So if you are able to send the mail that way, the problem should be solved...
Great idea, nice work.
sent from public phone using coins.
Playstore says latest version not compatible with my device (HP Touchpad running CM11).
Just designed for phones?
Hallahan said:
Isn't it just the fact that Google only accepts sending email when you, or I, log on to their smtp servers using a valid username and password? So if you are able to send the mail that way, the problem should be solved...
Click to expand...
Click to collapse
See what Google sent a few minutes ago. It's no related with user and password but an Gmail account sending emails from Spain usa France etc using the same account
Hi Daniel,
Someone recently used your password to try to sign in to your Google Account [email protected]. This person was using an application such as an email client or mobile device.
We prevented the sign-in attempt in case this was a hijacker trying to access your account. Please review the details of the sign-in attempt:
Monday, February 3, 2014 12:05:14 PM UTC
IP Address: 31.20.201.179
Location: The Netherlands
If you do not recognize this sign-in attempt, someone else might be trying to access your account. You should sign in to your account and reset your password immediately.
Enviado desde mi SM-N9005 usando Tapatalk 4
Every time I try to enter the enter or exit location in rules, the app force closes. KitKat Moto g. ROM has a gps bug though. Can't get lock.
Is there a way to lengthen the "time on" for the lockscreens w/o entering password?
Title asks it all 8)
Looking to extend the awake time for the lockscreen while it's waiting for one to enter the password, unlock pattern, etc.
EDIT: Reason being - while using the Xposed Quick Access module it would be nice if the screen didn't off itself after a couple of seconds whilst I'm reading whatever info I have set for Quick Access-ability.
Thanks!
Sooo... I think I've solved this issue with a Tasker task. Tested with an n = 1 data set, but that one was a success. Looking forward to future testings to see if this works and solves the issue.
For those interested - in Tasker, I set up an app profile and triggered screen on, never timeout while that app is open / on-screen. Not the most perfect task since I'll have to actively remove the app from the screen for the phone to operate the lock function as normal, but I think it'll work for what I was hoping to do.
- Using Xposed Notification mod, I can pull down the notification menu down when I receive a new notification (an email for example).
- Or even better, using the Dynamic Notifications app I can open the email straight from the dynamic notification (similar to the function found on the Moto X for those not familiar).
- Then through the Xposed Quick Access mod, the email opens right over the lockscreen without going through the whole unlocking the phone process saving a few motions, clicks, etc.
- Then the Tasker task takes over and keeps the screen on whilst I'm reading / responding to the email, then when I delete the email and the lockscreen appears, the Tasker task ends and the screen goes back into default screen off / timeout mode.
Hopefully this will help someone else out in the future, or give someone else another idea! 8)
The purpose of this widget is to make it easier for elderly people to make phone calls and read SMS.
You can download it from the site: https://easyjoin.net/index.html#otherapps
There are various applications like this, but none were as simple and essential as I needed it, so I decided to create one. I share it in case it's useful to others.
Unlike other solutions this is a widget and not a launcher. The widget shows a dial panel, icons to show contacts and SMS and you can have buttons for a quick dial contact and device flashlight.
You can configure the widget from the application.
It is recommended to use a launcher that allows you to remove any other item from the home page and that allows you to lock the home page so as to prevent the person using the phone from removing the widget.
Personally I have used Nova but I would like to know if there are other launchers that can offer the above features in a better way.
The Neo-Launcher home page lock is great and is what I currently recommend.
It needs Android 4.1 (Jelly Bean) or newer.
Uses the following permissions:
android.permission.CALL_PHONE: to initiate a phone call. If you don't give this permission the application will open the default dialer app with the selected telephone number.
android.permission.READ_CONTACTS: to read the contacts to be displayed.
android.permission.READ_SMS: to read the SMS to be displayed.
android.permission.CAMERA: to use the flashlight.
Powered by EasyJoin.net
Thanks. I have been looking for a good widget for my mom's phone. I like the clear numbers in boxes. There are a couple of changes that I think will make this more usable. The spaces to the left and right of the 0 button should have star and number sign buttons. Also, isn't the Android hang up button built into the Android calling screen? It seems this widget's hang up button is just for clearing the typed numbers? If so, it would be simpler for a senior to see this visually as CLEAR or something like that, or turn it into a backspace button .
The way I have set up my mom's phone is that her few contacts are shortcuts on the screen so there is no need to see the contacts icon. You have the option to disable the sms icon in the dialing window which is great, but an option to remove the contacts icon would be good to have also.
---------- Post added at 12:19 AM ---------- Previous post was at 12:16 AM ----------
Also, maybe remove the keep alive service which is just for getting back into the settings? Just have the settings as a one and done when you add the widget since there aren't many options.
Thank you. Simplicity.
Simple and Clean is the way that this dial pad makes my grandmothers phone work.
Update 1.0.1
- Enabled default tick sound on a button's press.
Update 1.1
It has been removed the permission to create a service in foreground and the relative notification.
It has been removed the permission to listen to the arrival of new SMS.
Permission to make phone calls has become optional. If it is not given, the default phone application with the selected phone number will open.
The icons for contacts and SMS are displayed only when corresponding permissions are given to the app.
The contact list is automatically updated when the device contacts are changed.
The icon to cancel the choice of number and/or contact has been replaced by the one with an "X" - it is no longer the one with the handset down.
The icon to close the contact and SMS list has been moved to the bottom.
Update 1.2
The dial and cancel buttons are visible only when a phone number has been typed/selected.
You can set the name and phone number of a contact to get a speed dial button.
It is possible to have a button to turn on the phone flashlight.
For devices using Android M and newer, the buttons and icons you see in the widget depend on the permissions given to the app. For Lollipop and older devices there are switches to decide what you see in the widget.
Update 1.3
You can view SMS and contacts with a smaller font.
Installed but only goes to set permissions screen.
Thanks