Den torsdagen den 23:e januari 2014 kl. 20:21:27 UTC+1 skrev Thomas Hermansson: > > 1. Connection to IOIO seems only to be established if IOIO chip is started >>> befor the App. (My app is based on the IOIOService example). >>> >> >> This is a known limitation of IOIOService, unrelated to this version. >> There's an open bug on that. I don't know how to fix it - it seems to be an >> Android limitation. Perhaps subscribing to the "connect" event by an >> activity or a broadcast receiver and passing the intent to the service is >> the right way to do it. >> > > Is there any ugly workaround for this? I was thinking about having a > TimerTask which runs every 60 seconds and then have it "try to connect" > somehow if a connections is not up and running? I just tried this by > calling the IOIOService.helper.restart() without any success. :-) >
Let me just rephrase this: It seems to work perfectly ok using a timer task this way. Even when the service is started at boot time it connects ok. (I read about someone else who had problems with this. //Thomas -- You received this message because you are subscribed to the Google Groups "ioio-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/ioio-users. For more options, visit https://groups.google.com/groups/opt_out.
