We are aware of the autostart issue. When the phone boots, many
things start at the same time. If there is insufficient memory, then
Webkey is not got started. In my Nexus One Webkey starts on boot, but
DroidWall starts about only half of the boots.
Webkey is registred to android.net.conn.CONNECTIVITY_CHANGE, which
gets called when the network state changes. As a workaround, we should
check that whether Webkey should have started, and start if necessary.
With this solution Webkey will start after a while. We haven't got
time to implement and test this solution, we are working on ICS fixes
and the python environment, but try to fix this within a week.
> Is it possible to have Tasker start the service via an action intent?
Should we provide an intent? An activity? (I'm doing the C++ stuff,
I'm not so familiar with the Android's lifecycle.)
Best wishes,
Peter
I see. Then we need an intent, which starts the service. We can do
that. And maybe a checkbox to enable it for security reasons.
Thanks,
Peter