> > 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. :-) What is the actual problem? As you are able to get some connect event for a normal Activity without any problems it should be solvable/workaroundable. Could you point me in a direction of where to start look in the IOIO code. When I start a service today and the IOIO is connected, do you get any event at all, or do you just simple try to connect once when the service starts? > >> 2. After aprox two hours connection was dropped. (Samsung Galaxy 4, USB >> connection, IOIOAccessoryLib used, power submitted with a 12V, 3A >> poweradapter) - and not established. >> > > The "not established" part is because of the above. Why it was dropped I > don't know... > It ran smoother this night with no connection, so I will "withdraw" this error until further notice. :-) > > >> 3. TWIMaster api runs fine, but suddenly stops sending/receiving data. I >> powercycled the i2c chip to make sure it did not hang without any result. >> As the twi.writeRead blocks until a response is returned I run the The >> twi.writeRead command in a separate thread and interrupt it if no answer >> is returned within 5 sec. But once this problem occurs, there is no way to >> recover but to rerun the Application. >> > > Interesting. Does it also happen with nothing connected over I2C? If so, I > might be able to reproduce and test this. > I don´t think it would be possible to test this without any I2C device. If you try run the writeRead and there is no i2c device answering, then it will block everytime, and then you would never know if there is an error or not. However I think that this problem was only occuring when running over bluetooth. Will continue to look. But if the error remains, would you be interested in me sending over a device with a i2c humidity sensor connected (and software). -- 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.
