Time syncs with v1.8 do not appear to work...

[mldewey]

unless I have the Syncml app in the foreground (current app on the screen).

All I did was set the Time Sync to On and put in a 2 hour interval. When I checked 6 hours later, I noticed the last time synced hadn't changed even though it should have run (sync) at least two times. I then set the interval to two minutes and watched (in the foreground) to see if the sync kicked off and it did. So, I left the interval for two minutes and checked back an hour later and, again, it did not kick off.

I am running a Samsung Captivate with version 2.1-update 1 of the firmware...Build Number ECLAIR.UCJH7.

Any ideas?

[bfo]

Can you check in the "log" menu of the Android client if there are errors for these sync sessions ? You see there time and potential errors.

If there is not enough memory available the app might be suspended.

Regards,
Beat

[mldewey]

There are no log entries except for those where I had Syncml in the foreground and, for those entries, all is good. In other words, there are no error entries at all in the logs...just successes. For the time period where Syncml was in the "background" there are no entries whatsoever...good or bad.

I don't believe memory is an issue (show 91MB free) either, otherwise, I wouldn't expect it to run in the foreground either.

[bfo]

Ok, thanks for clarification.

In the "adb logcat" all alarm calls are shown with log entries.
Are they available in "background" as well or are they suppressed on your device ?

Regards,
Beat

[mldewey]

Originally Posted by bfo

Ok, thanks for clarification.

In the "adb logcat" all alarm calls are shown with log entries.
Are they available in "background" as well or are they suppressed on your device ?

Regards,
Beat

/me gives back a blank stare.

If the logs are suppressed, it is by default. How can I tell?

By the way. It appears to be working sporadically now. I believe part of the problem was that I use Advanced Task Killer. I had set it to Auto-kill at a safe level and have since turned it off. Since then it has been working a little better...still not consistent. I just sent off some logs to show what is going on. I have the interval set at 2 minutes right now to get near instant feedback on whether it is working or not.

[bfo]

I've installed the Advanced Task Killer as well, however not using it with the auto-kill feature activated.

The Synthesis Android client can restart, even after killed with the Advanced Task Killer, but it might leave out some of the alarms when killed during the setup phase. So I propose not to use the auto kill feature with the Android SyncML client, especially also because the whole software must be fully restarted after a kill, which is time and resource consuming.

Regards,
Beat