24/7 timelapse get killed after 24 hours

1) Yes I pressed home, checked that button on desktop widget is green and left phone in this state.
I already did similar test - I set capture interval on 2hrs and let working the software for 24 hours. I successfully got 12 photos.
2) Yes I mean LED flash. I use smatphone as remote control system that take photos from my country village and send photos to me (Dropsync). I monitor indoor temperature, because in Russia sometimes it is quite cold ;) Now I use external USB lamp to workaround this problem but this is not cool.

>>So you mean this problem ONLY happens when you set the interval to 12hr, right?

No, my feeling is that it fails if recording duration is more than 24hrs. Before 24/7timelaps I tried Tina Timelaps (it supports LED flash control, btw and it is free) and it stopped also after 24hrs (I receive only 2 photos taken with 12 hrs interval). I thougth that problem was that Tina did not support background mode (I left Tina in foreground). That is why I decided to try 24/7timelaps. So, as a result, I see that both programs stop working after roughly 24hrs. I will play more with the software and let you know results.

I will help with logs, no problem. My company develops VVoIP software for iOS and Android and I am quite experienced guy ;)

Usage of DropBox is my personal "invention" :), where can I find your article?

If you will have a chance to implement LED flash support please use long time periods for exposure measuring, auto focusing and capturing. I played with Tina on defferent smartphones and found that it very often failed to take pictures properly. Smartphone's camera works unreliably in poor light conditions and it need more time to take picture

Here is description of my smartphone
http://market.yandex.ru/model-spec.xml?modelid=9330090&hid=91491

I can tell you your assumption about the 24hr duration bug is not correct. I have personally run this app for way more than 24hrs. In fact, I was running a long term test here before you submit this post and it had been running over 48hr.

Here are examples of the many tests I have made, many are over 24hr using 247timelapse
http://247timelapse.com/time_lapse_app_battery_life_comparison

Having said that, I think the problem lies in the very long capture interval you have used.
In fact, I found a bug in our app while trying to reproduce your problem.
However, this bug is related to power consumption and not directly related to the problem you described. If you set your capture interval at 12hr, do you notice your phone becomes warm? I did... and this is the bug. The phone is supposed to be ice cold. If you set your capture interval back to default, 60 seconds, your phone should be ice cold and consumes very little power despite so many photos it is taking. This is the unique advantage I am trying to market 247timelapse.

It will take me a while to reproduce your problem, before I can try to find a fix.

It is good to know you are IT competent. It will help a lot when we are trying to find the cause of the problem.

The article I mentioned about Dropsyn or similar can be found at
http://247timelapse.com/photo_sync

I will try to add an option to allow you to control the exposure.
This will hopefully help with what you are trying to capture.

There is already an option in 247timelapse to enable auto-focus.
We use infinity by default because autofocus tends to cause camera problems.
After all, we expect most of our users to be capturing outdoors scenery.

Different phone have different camera implementation and it is difficult to make an app that works on all phones. 247timelapse should work reliably in most phones due to our developer's extensive in using the camera code and feedback in another camera related app. It is not surprising to know that other time lapse app is not reliable.

I bet no time lapse app developer have actually tried to capture photos for durations as long as I had ;)

I found your phone, it looks like a China made clone of Samsung Galaxy Nexus
http://www.fly-phone.com/devices/smartphones/iq445_genius/
Glad to know 247timelapse works fine on it.

Would you like me to contact you here when I have a new app for you to try?
Or you prefer me to e-mail you directly? (I can see your e-mail address here.)

>>I can tell you your assumption about the 24hr duration bug is not correct
Yes, it was my mistake. I did not receive photos on my dropbox account in time and made such wrong assumption. Actually I did not receive photos because of  problems with internet 3G GSM connection that was not stable there. I received captured photos later and could check capturing time. But I still found a strange thing that might be interesting for you. look at the screen shot  I've done from my  DB. You can see that for some reasons  capturing period shifted on 90mins - it looks strange for me (8:17, 20:17, 8:17, 21:30 why???).

https://db.tt/vSWAFl3I

It mistically correlates with content of my photos - photos 1,2,3 are good and others black. It is due to planned service works on my village in that time when power was temporarily shuted down. After global power cycle my external USB LED lamp did not switched on - it is waiting me to press its power button manually (I need LED flash control in your program - external lamp is a failure point of my innovative monitoring system! ). After that event capturing period stays stable.

I will check teperature of my Fly445 but it is a little bit difficult - the weather is cold now ;) during my previous tests, smartphone was cold as a stone :)
Thanks or articles, I've found something new for me.

Feel free to contact me directly, I will help you with tests, no problem. The only restriction I have that my house is 80km from me (btw, russians call such houses "dacha") and I visit it on weekends.

From your screenshot, it is clear that the 24/7 timelapse continues to work after 24hr. The initial bug you reported is non-existent. I have "rejected" this specific bug.

2013-11-27 08:17:22
2013-11-27 20:17:22
2013-11-28 08:17:23
-> time shift here
2013-11-28 21:30:29
2013-11-29 09:30:31
2013-11-29 21:30:35
2013-11-30 09:30:36

The 90 mins shift seems to be related to the lost of power to your phone.
Maybe your phone did something and causes this behaviour, I have no idea at the moment.
Do you notice the time shift happens in the first black photo only?

Unless you see this major time shift happens consistently, I won't investigate further into this problem.

I have already scheduled to add LED flash support. Will let you know when I have an apk for you to try.

About power consumption, I usually run the phone without connecting to power supply and watch the battery %. You can see the battery % embedded on the photo too. If you run 247timelapse with battery only, at 1 min interval you should be to capture many photos with only a small drop in battery life. After I set my phone (Galaxy Nexus, Android 4.0.4) with the 12hr capture interval with screen off, I do see my phone battery get drained rapidly and battery completely flat in a few hours, compared to >30hr battery life normally. You can see the battery drop like 5-10% in as little as 30mins due to this bug. If the phone drain battery like this, you can feel it becomes warm. FYI, all the other timelapse app I have tested so far all drain battery like this, i.e. you can expect your battery to be completely flat in around 5hr. If you can't feel the heat, you can always look at battery %.

Note: not all phone can capture photo with the screen off using 247timelapse without power supply connected.

I have draw a table recently on this
http://247timelapse.com/247timelapse_compatibility

Assuming your phone can capture photo with the screen off using 247timelapse without power supply connected, when you get the chance to visit your "dacha" house, let me know if your phone suffers from this power related problem or not because I am looking at fixing bug.