Problem with camera task in s4 mini

[Thorsten Rosendahl]

Good day all,

I have been using a timelapse task successfully on a xperia go or galaxy s3.

Moved over to a galaxy s4mini the task seems to stop working after a couple of minutes.

So to double check I added an alert/beep before and after the 'take photo' action.

While the beeps continue, I can not find new jpgs on the sdcard, even though the 'continue on error ' is unchecked.

Any advise ?

27-04-2014 E: 15.32.44#E: execute task: Camm

27-04-2014 Task: 15.32.44#Task: Take Photo [ Camera:Rear Filename:test Naming Sequence:Chronological Insert In Gallery:Off Discreet:On Resolution:3264x2448 Scene Mode:Auto White Balance:Daylight Flash Mode:Off Focus Mode:Infinity ]

27-04-2014 E: 15.32.44#E: exe: Camm / Take Photo [ Camera:Rear Filename:test Naming Sequence:Chronological Insert In Gallery:Off Discreet:On Resolution:3264x2448 Scene Mode:Auto White Balance:Daylight Flash Mode:Off Focus Mode:Infinity ]

27-04-2014 E: 15.32.44#E: condition matched

27-04-2014 E: 15.32.44#E: switch on ac 101

27-04-2014 E: 15.32.44#E: start proxy CameraProxyDiscrete, wait, time limit 12s

27-04-2014 E: 15.32.44#E: add wait type Proxy Group time 12

27-04-2014 E: 15.32.44#E: add wait type Proxy Group done

27-04-2014 E: 15.32.44#E: set proxy: true (startProxy)

27-04-2014 CameraProxy: 15.32.44#CameraProxy: cam: discrete: true

27-04-2014 E: 15.32.44#E: result: ok

27-04-2014 E: 15.32.44#E: stillWaiting: test Proxy Group

27-04-2014 E: 15.32.44#E: still waiting for Proxy Group: Camm

27-04-2014 E: 15.32.44#E: nothing chosen, check exit

27-04-2014 E: 15.32.44#E: wait for 1000ms

27-04-2014 WakeLockManager: 15.32.44#WakeLockManager: acquired partial lock for CameraProxy flags: 1 autorelease: true warn: true

27-04-2014 CameraProxy: 15.32.44#CameraProxy: no cams: 2

27-04-2014 CameraProxy: 15.32.44#CameraProxy: camera index 0 facing: 0 wanted facing: 0

27-04-2014 CameraProxy: 15.32.44#CameraProxy: getCameraIndexWithFacing: got 0 for facing 0

27-04-2014 CameraProxy: 15.32.44#CameraProxy: try open camera 0

27-04-2014 CameraProxy: 15.32.45#CameraProxy: res 3264x2448 scene mode: auto flash mode: off white balance: daylight

27-04-2014 CameraProxy: 15.32.45#CameraProxy: 3264x2448: supported: 3264x2448

27-04-2014 CameraProxy: 15.32.45#CameraProxy: setPictureSize 3264x2448

27-04-2014 CameraProxy: 15.32.45#CameraProxy: supported focus: auto infinity normal macro continuous-picture continuous-video continuous-picture-macro face-priority

27-04-2014 CameraProxy: 15.32.45#CameraProxy: set focus: infinity

27-04-2014 E: 15.32.45#E: wait finished

27-04-2014 E: 15.32.45#E: stillWaiting: test Proxy Group

27-04-2014 E: 15.32.45#E: still waiting for Proxy Group: Camm

27-04-2014 E: 15.32.45#E: nothing chosen, check exit

27-04-2014 E: 15.32.45#E: wait for 1000ms

27-04-2014 E: 15.32.46#E: wait finished

27-04-2014 E: 15.32.46#E: stillWaiting: test Proxy Group

27-04-2014 E: 15.32.46#E: still waiting for Proxy Group: Camm

27-04-2014 E: 15.32.46#E: nothing chosen, check exit

27-04-2014 E: 15.32.46#E: wait for 1000ms

27-04-2014 E: 15.32.47#E: wait finished

27-04-2014 E: 15.32.47#E: stillWaiting: test Proxy Group

27-04-2014 E: 15.32.47#E: still waiting for Proxy Group: Camm

27-04-2014 E: 15.32.47#E: nothing chosen, check exit

27-04-2014 E: 15.32.47#E: wait for 1000ms

27-04-2014 E: 15.32.48#E: wait finished

27-04-2014 E: 15.32.48#E: stillWaiting: test Proxy Group

27-04-2014 E: 15.32.48#E: still waiting for Proxy Group: Camm

27-04-2014 E: 15.32.48#E: nothing chosen, check exit

27-04-2014 E: 15.32.48#E: wait for 1000ms

27-04-2014 E: 15.32.49#E: wait finished

27-04-2014 E: 15.32.49#E: stillWaiting: test Proxy Group

27-04-2014 E: 15.32.49#E: still waiting for Proxy Group: Camm

27-04-2014 E: 15.32.49#E: nothing chosen, check exit

27-04-2014 E: 15.32.49#E: wait for 1000ms

27-04-2014 E: 15.32.50#E: wait finished

27-04-2014 E: 15.32.50#E: stillWaiting: test Proxy Group

27-04-2014 E: 15.32.50#E: still waiting for Proxy Group: Camm

27-04-2014 E: 15.32.50#E: nothing chosen, check exit

27-04-2014 E: 15.32.50#E: wait for 1000ms

27-04-2014 E: 15.32.51#E: wait finished

27-04-2014 E: 15.32.51#E: stillWaiting: test Proxy Group

27-04-2014 E: 15.32.51#E: still waiting for Proxy Group: Camm

27-04-2014 E: 15.32.51#E: nothing chosen, check exit

27-04-2014 E: 15.32.51#E: wait for 1000ms

27-04-2014 E: 15.32.52#E: wait finished

27-04-2014 E: 15.32.52#E: stillWaiting: test Proxy Group

27-04-2014 E: 15.32.52#E: still waiting for Proxy Group: Camm

27-04-2014 E: 15.32.52#E: nothing chosen, check exit

27-04-2014 E: 15.32.52#E: wait for 1000ms

27-04-2014 E: 15.32.53#E: wait finished

27-04-2014 E: 15.32.53#E: stillWaiting: test Proxy Group

27-04-2014 E: 15.32.53#E: still waiting for Proxy Group: Camm

27-04-2014 E: 15.32.53#E: nothing chosen, check exit

27-04-2014 E: 15.32.53#E: wait for 1000ms

27-04-2014 E: 15.32.54#E: wait finished

27-04-2014 E: 15.32.54#E: stillWaiting: test Proxy Group

27-04-2014 E: 15.32.54#E: still waiting for Proxy Group: Camm

27-04-2014 E: 15.32.54#E: nothing chosen, check exit

27-04-2014 E: 15.32.54#E: wait for 1000ms

27-04-2014 E: 15.32.55#E: wait finished

27-04-2014 E: 15.32.55#E: stillWaiting: test Proxy Group

27-04-2014 E: 15.32.55#E: still waiting for Proxy Group: Camm

27-04-2014 E: 15.32.55#E: nothing chosen, check exit

27-04-2014 E: 15.32.55#E: wait for 1000ms

27-04-2014 E: 15.32.56#E: wait finished

27-04-2014 E: 15.32.56#E: stillWaiting: test Proxy Group

27-04-2014 E: 15.32.56#E: wait timeout type Proxy Group

27-04-2014 E: 15.32.56#E: removeWait: Proxy Group

27-04-2014 E: 15.32.56#E: set proxy: false (stillWaiting)

27-04-2014 E: 15.32.56#E: finished waiting for Proxy Group (task Camm)

[Pent]

Please try with a much lower resolution and not Discrete checked.

Thanks,

Pent

[Thorsten Rosendahl]

Same, but later.

On the s3 it runs in discrete with 8m resolution all night long.

[Pent]

Looks like maybe the setFocus call is hanging. I'll put some more logging in for next update, could you post a similar log then please ?

Thanks,

Pent

[Thorsten Rosendahl]

Sure I can.
I am using infinite right now. You want me to test with AF or some other mode first?

--
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/kMsSOm4rovU/unsubscribe.
To unsubscribe from this group and all its topics, 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.

[Pent]

I am using infinite right now. You want me to test with AF or some other mode first?

Doesn't hurt to try.

Pent

[Thorsten Rosendahl]

Unpredictable results.
I tried a job with 60 shots and 60 seconds pause in between .
Sometimes you end up with 3 pictures taken, sometimes 45.
Doesn't matter if auto/normal/infinity is chosen.
Continuous mode crashes immediately.

--

[Pent]

I just released an update if you want to send me a log with infinite focus.

Pent

[Thorsten Rosendahl]

Thanks.
27 instead of 59 pics captured. Log attached.

Am 30.04.2014 15:13 schrieb "Pent" <crafty...@gmail.com>:

I just released an update if you want to send me a log with infinite focus.

Pent

--

[Thorsten Rosendahl]

any progress ?

thanks

[Pent]

any progress ?

Thanks for bumping, missed it.

Couldn't see any occasion in the log where the picture wasn't taken and written to a file.

Pent

[Thorsten Rosendahl]

as I wrote the SD card (using file explorer, not album) was only showing 27 instead of 59 pics.

the problem does not appear on S3, neither it does on S4 Zoom.

I could live with S4 Zoom, but have the problem that the lens is driving in and out between the shots, assuming the wear will kill it kind of fast.....

--

[Pent]

as I wrote the SD card (using file explorer, not album) was only showing 27 instead of 59 pics.

The first log you gave me the shot wasn't being taken, the last log they were being taken and
written to the card. I was therefore presuming that you've given me a log where all the shots
were successful, whereas I need to see one which isn't successful.

In any case: if some of the shots in the last log you gave me failed, there's nothing I can do
about it. The log shows the shot is taken and the OS reports that the data has been written to the card.

Pent