I would recommend: 1. Using the precompiled HelloIOIO for doing these tests (just to rule out the possibility that you're building something wrong). 2. Trying either the IOIO as host or as device (which has to do with with side of the cable goes into the IOIO and which one to the Android). Make sure the switch on the IOIO is in the "A" (auto) mode.
On Tue, Oct 17, 2017 at 4:04 AM, Ilan Tal <[email protected]> wrote: > I finally managed to understand your question. No, the phone is definitely > controlling the IOIO and the IOIO is not the host. > I used your looper to control the IOIO - staying as close as i could to > your examples (Hello IOIO etc.) > > On Tuesday, October 17, 2017 at 7:35:17 AM UTC+3, Ytai wrote: >> >> I think you might be somewhat misusing the term OTG. USB OTG has to do >> with the ability of a device to switch between being a host on the USB bus >> to bring a device, based on which side of the cable it is connected to. >> Since all phones used to be only devices, manufacturers started using the >> term OTG to mean that their device can also be a host. >> The IOIO worked with Android long before any phones had host mode, so the >> lack of OTG support in itself is not a problem. Since it sounds like from >> your description that you're using the IOIO as a host, it is more likely >> that what you're seeing is a result of the bug I linked to rather than lack >> of support. >> Makes sense? >> >> >> On Oct 16, 2017 21:28, "Ilan Tal" <[email protected]> wrote: >> >> With the new phones your board simply doesn't exist under OTG. Nothing we >> could do would give signs of life. >> That is the contribution of the UTB OTG checker programs - they have no >> connection to your board. >> All of these programs claim that OTG is dead, so big surprise that the >> phone can't see your board under OTG. >> >> >> On Tuesday, October 17, 2017 at 7:21:59 AM UTC+3, Ytai wrote: >> >>> Is this the case for both directions? I.e. the IOIO as either host or >>> device? >>> >>> On Oct 16, 2017 21:11, "Ilan Tal" <[email protected]> wrote: >>> >>>> Hi Yitai, >>>> Unfortunately we have to accept the fact that phones less than about 1 >>>> year old no longer support OTG. >>>> Blue tooth is the only solution. >>>> The cable I asked about does nothing. >>>> >>>> There are several programs to check USB OTG on the phone itself. These >>>> are useful as an independent check, independent from your board. >>>> Any of them will work on "old" phones but will fail on new phones, >>>> indicating that the phone does not support OTG. >>>> The cable is simply a red herring and contributes nothing. >>>> >>>> Too bad that the OTG technology came and went within 5 years, but this >>>> seems to be the case. >>>> So we will switch our system from OTG to blue tooth. >>>> >>>> Thanks, >>>> Ilan >>>> >>>> >>>> On Thursday, October 12, 2017 at 5:04:44 PM UTC+3, Ilan Tal wrote: >>>>> >>>>> I would like to ask about the IOIO OTG on the latest phones. >>>>> To my amazement many of the latest phones no longer seem to support >>>>> OTG. >>>>> (What I see is that I can't make any connection with Hello IOIO.) >>>>> >>>>> There is a cable you can buy >>>>> https://www.amazon.com/dp/B009YPYORM?tag=won00-20 >>>>> that seems to solve the problem, but I'd like some feedback. >>>>> >>>>> Ideally, this might work: plug the micro usb into the phone and then >>>>> make a connection between one of the 2 male connectors to the IOIO. >>>>> I don't know who has experience with this. >>>>> >>>>> If that fails perhaps another possibility is to plug the micro usb >>>>> into the IOIO and use a male connector to blue tooth. >>>>> This is using the cable as a simple pass through, but I might be able >>>>> to use the other connector to supply 5 volts to the IOIO? >>>>> >>>>> Any suggestions? >>>>> Thanks, >>>>> Ilan >>>>> >>>>> -- >>>> 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 https://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 https://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 https://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 https://groups.google.com/group/ioio-users. For more options, visit https://groups.google.com/d/optout.
