Tasker "Take Picture" not saving when phone is locked

923 views
Skip to first unread message

Andrew Walton

unread,
Jun 15, 2013, 8:46:20 PM6/15/13
to tas...@googlegroups.com
I did a search within this group and on Google, and can't come up with anything.

I created a profile that executes when an incorrect password has been entered 3 times when the phone is locked. When this happens, a front picture and rear picture are taken and e-mailed along with GPS coordinates.

This works flawlessly if I manually run the profile.

When I test this by inputting the password incorrectly three times, everything works as it should (e-mail sent and received) with one exception: the pictures are not sent. They are not saved anywhere on my phone. I know that the task is running because the variable I'm using to name the photos is being incremented as expected. 

Again, when manually running the task, the photos are saved and e-mailed just fine, this only occurs when the profile is invoked by inputting an incorrect password 3 times.

Any ideas? (I am running a Droid Razr HD (XT926), rooted, unlocked bootloader, and custom ROM (Nexesque))

Matt R

unread,
Jun 16, 2013, 7:44:56 PM6/16/13
to tas...@googlegroups.com
Maybe the photos aren't working because the screen is locked?

Matt

Mike L

unread,
Jun 16, 2013, 7:57:02 PM6/16/13
to tas...@googlegroups.com
No it's not that, this works on my phone. Is the accessibility settings turned on for Tasker? Maybe you need that to do things over the lock screen?

Rich D

unread,
Jun 17, 2013, 9:59:02 PM6/17/13
to tas...@googlegroups.com

> Any ideas? (I am running a Droid Razr HD (XT926), rooted, unlocked bootloader, and custom ROM (Nexesque))

I would try a small wait just after the take photo action..

Rich..

Racing Turtle

unread,
Jul 29, 2014, 7:24:24 PM7/29/14
to tas...@googlegroups.com
Andrew,

I am experiencing the same challenge. The caveat is, that to the best of my recollection, is that photos USED 2 BE successfully saved when the screen was locked. One of the very first things I tested after initially writing my scripts (weeks ago?) was to observe how they would behave when the screen was locked. I recall being pleasantly surprised when they performed in screen lock mode.

Running a non-rooted Samsung Galaxy S3 on Verizon.
Tasker Accessibility Setting is enabled.

Verizon pushed an update (4.2.2) out a few weeks ago and I finally bit the bullet and allowed the update. Cause? I am not qualified to say.

Earlier today I tried using "Secure Settings Plugin" to unlock screen, take photo, and lock screen.

That did the trick. The photo was saved to file. I do not consider it an elegant solution but it worked.

I have yet to ascertain whether a photo is taken and not saved to file or perhaps the camera did not take a photo, so there was no image to save.

rturtle.


Reply all
Reply to author
Forward
0 new messages