Its a requirement with the USB chip that all read requests must be
multiples of the max packet size of the endpoint. In
AccessoryConnectionBootstrap replacing
if ( localInputStream_.read()== 1) {
with
byte[] buffer = new byte[64];
localInputStream_.read(buffer);
if ( buffer[0]== 1)
fixed the problem for me.
On Friday, February 7, 2014 5:16:04 PM UTC-5, Ytai wrote:
>
> Please see my last update to the bug:
> https://github.com/ytai/ioio/issues/76
> Apparently it's a Nexus 5 issue. Let me know if you can find a workaround.
> I haven't dug too deep into it.
> On Feb 7, 2014 2:13 PM, "Maxwell Doherty" <[email protected] <javascript:>>
> wrote:
>
>> I am trying to fix the IOIO-OTG to work with IOIOLibAccessory on the
>> Nexus 5 running 4.4.2. During connect the program gets stuck trying to soft
>> open the accessory. <code>
>> AccessoryConnectionBootstrap.Connection.waitForConnect()#if
>> (localInputStream_.read() == 1) </code> Is blocking and never returning
>> until the device is disconnected.(as warned). I do not know the next steps
>> for debugging lower than this. Any suggestions?
>>
>> On Monday, December 16, 2013 8:19:52 PM UTC-5, Ytai wrote:
>>>
>>> ADB mode stopped working in Android 4.2 or something around there. You
>>> should use OpenAccessory mode in this case (achieved by turning USB
>>> debugging off on the Android, and building your app against
>>> IOIOLibAccessory).
>>> Having that said, there's a particular issue that's been reported for N5
>>> (unrelated to KitKat) preventing the IOIO from working with it in either
>>> mode. However, the preliminary support for IOIO in device mode (which only
>>> works with a IOIO-OTG, unfortunately) is the current workaround for this
>>> issue.
>>> Since I don't have a N5, there's not much I can do about this at the
>>> moment. I'm hoping that someone that understands the internals to some
>>> extent will help me out here.
>>>
>>>
>>> On Mon, Dec 16, 2013 at 1:00 PM, martinarcher <[email protected]> wrote:
>>>
>>>> Hello,
>>>>
>>>> I have an IOIO V1 that I use at work to remotely reboot a large high
>>>> voltage piece of equipment. We have used it for a few years with an
>>>> application I wrote (running on an older Gingerbread HTC phone). We all
>>>> use newer phones (I have a Nexus 5 and we also have 2 Nexus 4's in the
>>>> group). With USB debugging enabled on the Kitkat devices, they simply
>>>> will
>>>> not acknowledge the IOIO being connected. I have tried by app as well as
>>>> the IOIO Manager->Programming screen. Both simply state they are waiting
>>>> for the IOIO to connect. As soon as I reconnect the same cable to the
>>>> Gingerbread phone it is recognized. Is there an issue with 4.4.2 and the
>>>> IOIO?
>>>>
>>>> Thanks!
>>>>
>>>> --
>>>> 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.
>>>>
>>>
>>> --
>> 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] <javascript:>.
>> To post to this group, send email to [email protected]<javascript:>
>> .
>> Visit this group at http://groups.google.com/group/ioio-users.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
--
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.
