I did not missed it. I already took a look at the code, saw the changes to the manifest. Still need to make the time for some tests. Thank you.
On Tue, Mar 10, 2015 at 5:52 PM, Ytai Ben-Tsvi <[email protected]> wrote: > You probably missed my post about the topic. I think I've addressed most > of those issues and the master branch on GitHub should have a version that > is more reliable (no release bundle yet). Feel free to check it out and let > me know if you're still seeing issues with it. > > On Wed, Feb 25, 2015 at 2:39 AM, Ionut Bungeanu <[email protected]> > wrote: > >> Yes, I did saw the list including more devices. >> To overcome the issue with android not triggering an event/intent I have >> changed the wait() from waitForConnect() to wait(500), essentially pooling >> for the accessory (same for the device connection). When a fast reconnect >> happens is when you may end up with more than one accessory in the list. >> >> Most probably this requires some changes in connection bootstrap open() >> method to not simply default to the first return accessory/device, and >> probably some changes in the state logic. (but I am sure you know better) >> >> USB attache intents are activity intents, where usb detach intents are >> broadcast intents. >> So instead off pooling, one can use an translucent activity to receive >> attach event in onCreate, and then simply finish (before setContentView, so >> the activity is actually never visible), and send the event down to IOIO >> connection manager. >> >> I didn't follow any of this to a full working solution (time >> constraints), I decided to stick with USB connection. >> >> >> miercuri, 25 februarie 2015, 06:31:46 UTC+2, Ytai a scris: >>> >>> Thanks for the insights! >>> Have you ever actually seen this list including more than one device? In >>> any case, from previous tests it didn't seem like my app has any way of >>> knowing that anything had changed at all, since I get no connect / >>> disconnect events. >>> I'm considering a pretty serious workaround which involves having >>> "keep-alive" functionality on both ends of the line, although even that >>> might not suffice if the Android app is stuck on a read() and there's >>> nobody on the other side to send anything. >>> >>> On Tue, Feb 24, 2015 at 6:44 AM, Ionut Bungeanu <[email protected]> >>> wrote: >>> >>>> you can try force USB to reset by updating *sys.usb.config, *something >>>> like >>>> *setprop sys.usb.config mtp,adb* >>>> from an adb root shell, or from java su process >>>> >>>> *ProcessBuilder pb = new ProcessBuilder(new String[]{"su", >>>> "-c","setprop mtp,adb"});* >>>> *pb.redirectErrorStream(true).start();* >>>> >>>> >>>> you may need to adapt the code and replace *mtp,adb* with whatever >>>> *getprop **sys.usb.config *returns when your connection is working >>>> normally. >>>> >>>> >>>> >>>> @Ytai for accessory mode, is my impression that when a fast disconnect >>>> happens, UsbManager.getAccessoryList() will report two (or more) >>>> accessories, from which only one is good, but the IOIO framework I think it >>>> always assumes the first, and this is not always right. >>>> >>>> miercuri, 18 februarie 2015, 08:25:28 UTC+2, Andries Kruger a scris: >>>> >>>>> Hi, >>>>> >>>>> I've been using the IOIO for a few weeks now. I have a rooted phone >>>>> that connects to the IOIO-OTG and I'm using the IOIOService to handle the >>>>> board. Everything has been going pretty well. There is just one issue I am >>>>> struggling to fix/workaround. >>>>> >>>>> A little background: The phone will be installed in a vehicle where I >>>>> don't have access to it. It will be collecting data as the driver goes on >>>>> his way. I need to IOIO to start and work flawlessly without issues and if >>>>> issues are detected, the phone should be able to fix itself. I've got this >>>>> working pretty well now. >>>>> >>>>> The issue I'm currently experiencing is that the IOIO gets >>>>> disconnected from the phone (well sort off). The phone is being powered by >>>>> the IOIO but the connection to the board is dead. It is kinda hard to >>>>> replicate this problem but I have managed to do this by wiggling the USB >>>>> connection and I think it might be caused by the vibrations in the >>>>> vehicle. >>>>> I do think I have a pretty good quality USB-OTG cable and the other cable >>>>> is the stock Samsung cable that came with the phone. Eventually I'll try >>>>> to >>>>> solder the connections together but I would like to have some sort of way >>>>> to fix the problem in the software should it occur. There are 3 things >>>>> that >>>>> fix the problem: >>>>> 1) Enable/Disable USB Debugging >>>>> 2) Cycle the power on the IOIO >>>>> 3) Restart the phone >>>>> >>>>> Restarting the phone will probably be the easiest solution but then we >>>>> loose data for as long as it takes the phone to restart. I have no way of >>>>> cycling the power on the IOIO without human intervention and it doesn't >>>>> look like I can change the state of USB debugging even when I'm rooted. >>>>> >>>>> Does anyone know of a way I can programmatically fix this? >>>>> >>>>> PS: I have latest versions of firmware installed. >>>>> >>>> -- >>>> 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/d/optout. >>>> >>> >>> -- >> 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/d/optout. >> > > -- > You received this message because you are subscribed to a topic in the > Google Groups "ioio-users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/ioio-users/3rIOoc-QfrU/unsubscribe. > To unsubscribe from this group and all its topics, 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/d/optout. > -- 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/d/optout.
