Use Reliable Alarms"
setting to "When Off". Using S6 Edge with 5.1.1, and Tasker set to "Never" in app optimization.Hmm... I'm afraid still no success on S6 edge, Android 5.1.1 ROM: G925FXXU3COI9 Rooted with Unikernel.Tasker v4.8b3m
I've set it to "when off" and it has started my calendar context on time.
The alarm icon in notification is the down side of this alternative solution, but at least there is a solution so thank you.
Nexus 6 not rooted, Android 6.
I don't have much that is affected by alarm times, but I changed the preference for reliable alarm to always, then to when off. In both cases my phone got very warm, as if the battery was being consumed heavily (which it actually was...full charge to 75% in about 45 minutes). I set it to never and the problem cleared. Circumstantial evidence, I know. Checking battery stats did not offer any useful info, as Tasker did not show up. I have not attempted to recreate the problem, yet, but will when I have some time. I also plan to reboot the phone before testing it again. Hopefully this was a one time occurrence.
Scott
--
You received this message because you are subscribed to the Google Groups "Tasker" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tasker+un...@googlegroups.com.
Visit this group at http://groups.google.com/group/tasker.
For more options, visit https://groups.google.com/d/optout.
It would seem that a reboot of the phone corrected whatever caused the earlier problem. I currently have reliable alarm set to always, for several hours, with no ill affects.
Scott
Do we have a list of all the phones that do require the "reliable alarm " switched on to have time context working correctly? which phones are affected by that time bug?
indeed, the alarm icon disappear a second or two after I switch on the phone, not a problem at all.Do we have a list of all the phones that do require the "reliable alarm " switched on to have time context working correctly? which phones are affected by that time bug?
I attempted to run Tasker 4.8b3 under Android 4.0.4 and these were the results ...
I installed Tasker and App Factory
I added a simple task with a Flash
It operated correctly
I did an Export to SD (Export as App was correctly shown as an option)
I exited Tasker
Tasker refused to load again
... Thom
Good question. No it is not grayed out. Same problem with current released version. Not a problem with previous beta version.
... Thom
Not to be sarcastic, but is the Tasker icon greyed out?
--
You received this message because you are subscribed to a topic in the Google Groups "Tasker" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tasker/f83LWBsBx9A/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tasker+un...@googlegroups.com.
What is the current Tasker policy on mm? Just to understand if it's better to set the screen off checks to 15 minutes instead of 10 minutes.
Tasker refused to load again
I did notice an improvement of the time settings.
Isnt the launcher responsible for launching any apps on the homescreen? Maybe its a bug with the launcher try a different one.
Also might be worth installing a logcat app to see if anythings actually happening when you click the tasker icon. first check whats going on when tasker does load and again when it doesn't load.
--
You received this message because you are subscribed to the Google Groups "Tasker" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tasker+un...@googlegroups.com.
Visit this group at http://groups.google.com/group/tasker.
For more options, visit https://groups.google.com/d/optout.
Jay M ︻芫══一
This launching after the first time problem exists in the production system and the current beta, It did not occur in the previous beta.
Nope. I tired playing with that and even disabled auto-rotate.
I observed that each wait action had a similar behavior as time context and 5-min restriction of Samsung (and may be 15-min restriction of Marshmallow) was applicable to them. Does anybody know if wait actions are also working well with new beta?
I'm using Tasker 4.8b3+ on an unrooted, stock Nexus 6 with Android build MRA58A and am having troubles with Event: Alarm Clock.
Nexus 6 not rooted, Android 6.
I don't have much that is affected by alarm times, but I changed the preference for reliable alarm to always, then to when off. In both cases my phone got very warm, as if the battery was being consumed heavily (which it actually was...full charge to 75% in about 45 minutes).
On Nov 24, 2015 9:20 AM, "Pent" wrote:
>
> I found an infinite loop when cancelling the reliable alarms which was probably the cause of the heaing.
> Suspect it's caused by the Android alarm manager code having a timing or thread bug somewhere, but tried to
> work around it.
>
Thanks. I'll try it again after next beta. I did actually encounter the problem again the next day, so it wasn't just a one time occurrence, meaning I'll probably be able to tell if your workaround fixed it.
Scott
- bugfix: Play Music Dir: was stopping after first track
Tasker.4.8b4m.apkInstalled on the LG Lucid ... reported successful ... refuses to load (even the first time).
Is there a corresponding App Factory for Tasker.4.8b4m.apk?
Tested 4.8 beta 4 on Xiaomi Mi4c with MIUI firmware (clean install, rebooted a couple of times): unfortunately none of the reliable alarm options make difference, the hourly profile I use does not get triggered.
I am running Tasker on ...
Does Tasker not run under 4.0.4 or is it just a quirk associated with the LG Lucid?
(Pursuing the LG Lucid is counterproductive my workaround was to create a Tasker app on the Droid Turbo 2 under 5.1.1 and install it on the LF Lucid running 4.0.4.)
... Thom
Does Tasker not run under 4.0.4 or is it just a quirk associated with the LG Lucid?
The List Files action seems to not be picking any files in my specified folder. Not sure why? Is that a bug?
Thanks
What is the difference between "Always" and "When Off" in regards to the alarm?
The List Files action seems to not be picking any files in my specified folder. Not sure why? Is that a bug?
Been using Reliable Alarms when off for more than 24 hours, and haven't had any issue, so far, with severe battery drain or overheating.
Scott