This is an Android issue.
A workaround has been discussed on another thread that  involves
registering an activity for this event and forwarding it to the service. I
haven't tried this personally, but I believe this should be the right
approach.


On Mon, Jun 9, 2014 at 3:53 AM, Nicolas Girardin <[email protected]>
wrote:

> Any progress?
>
> Seems that <intent-filter><action
> android:name="android.hardware.usb.action.USB_ACCESSORY_ATTACHED"
> /></intent-filter> is still not recognized when put inside the <service>
> tag.
>
> On Friday, June 28, 2013 4:15:38 PM UTC+2, Peakon wrote:
>>
>> Thanks Ytai
>>
>> I suspected that it may be something to do with the fact that open
>> accessory assigned to a service rather than main activity but wanted to
>> make sure that I have not messed something up. Of cause until 4.2 I always
>> used ADB connection and Bluetooth for debugging. I will try to figure out
>> the way to get it working but I am pretty new to Android so probably
>> chances of finding solution quite low.
>>
>> Thank you for your help again.
>>
>> On Friday, 28 June 2013 05:35:36 UTC+1, Ytai wrote:
>>>
>>> Hmmmm....
>>> I'm suspecting it is something to do with the AndroidManifast.xml file
>>> and with the fact that the intent-filter is used with a service instead of
>>> an activity. What seems to be happening is that the Android OS doesn't pass
>>> the accessory connection event to a service, only to an activity. I'm
>>> wondering if this is indeed not supposed to work or maybe I just did it
>>> wrong. It would be great if you can spend some time looking into this, or
>>> otherwise, feel free to open a bug on the IOIO repo, so that I'll
>>> eventually do it.
>>>
>>>
>>> On Thu, Jun 27, 2013 at 1:31 AM, Peakon <[email protected]> wrote:
>>>
>>>> Dear Ytai and All
>>>>
>>>> I have tried prebuild HelloIOIOService apk from 3.26 archive and this
>>>> one app have given the same problem - no connection on reconnect. I have
>>>> also tried this on different phone running Gingerbread and still the same
>>>> problem. I wonder if anyone tried runnign HelloIOIOService and if it worked
>>>> on reconnect?
>>>>
>>>>
>>>> On Tuesday, 25 June 2013 20:39:41 UTC+1, Peakon wrote:
>>>>>
>>>>> Sorry I've just added unfiltered logcat in case I missed something
>>>>> with the previous one
>>>>>
>>>>> On Tuesday, 25 June 2013 19:30:22 UTC+1, Peakon wrote:
>>>>>>
>>>>>> I also uninstalled IOIOSimple app and now when I plugin the cable I
>>>>>> get the following message see file 488.jpg. If I cancel this message and
>>>>>> than start IOIOService I get the same message as before about using
>>>>>> Accessory mode for IOIOService and connection works OK as before and
>>>>>> reconnection does not work as before.
>>>>>>
>>>>>> On Tuesday, 25 June 2013 19:19:51 UTC+1, Peakon wrote:
>>>>>>>
>>>>>>> 06-25 19:06:56.860: I/ActivityManager(391): Start proc
>>>>>>> ioio.examples.hello_service for service ioio.examples.hello_service/.
>>>>>>> HelloIOIOService: pid=16036 uid=10081 gids={50081, 3003, 3002}
>>>>>>> 06-25 19:11:40.899: D/UsbDeviceManager(391): entering USB accessory
>>>>>>> mode: UsbAccessory[mManufacturer=IOIO Open Source Project,
>>>>>>> mModel=IOIO, mDescription=IOIO Standard Application, mVersion=IOIO0326,
>>>>>>> mUri=https://github.com/ytai/ioio/wiki/ADK, mSerial=N/A]
>>>>>>> 06-25 19:12:52.642: D/UsbDeviceManager(391): entering USB accessory
>>>>>>> mode: UsbAccessory[mManufacturer=IOIO Open Source Project,
>>>>>>> mModel=IOIO, mDescription=IOIO Standard Application, mVersion=IOIO0326,
>>>>>>> mUri=https://github.com/ytai/ioio/wiki/ADK, mSerial=N/A]
>>>>>>> 06-25 19:13:10.087: D/IOIOConnectionRegistry(16510): Successfully
>>>>>>> added bootstrap class: ioio.lib.impl.SocketIOIOConnectionBootstrap
>>>>>>> 06-25 19:13:10.095: D/IOIOConnectionRegistry(16510): Successfully
>>>>>>> added bootstrap class: ioio.lib.android.bluetooth.Blu
>>>>>>> etoothIOIOConnectionBootstrap
>>>>>>> 06-25 19:13:10.110: D/IOIOImpl(16510): Waiting for IOIO connection
>>>>>>> 06-25 19:13:10.110: D/IOIOImpl(16510): Waiting for IOIO connection
>>>>>>> 06-25 19:13:14.095: I/IncomingState(16510): IOIO Connection
>>>>>>> established. Hardware ID: SPRK0016 Bootloader ID: IOIO0304 Firmware ID:
>>>>>>> IOIO0326
>>>>>>> 06-25 19:13:14.095: I/IOIOImpl(16510): IOIO connection established
>>>>>>> 06-25 19:13:24.298: I/IOIOProtocol(16510): IOIO disconnected
>>>>>>> 06-25 19:13:24.626: D/IOIOImpl(16510): Waiting for IOIO connection
>>>>>>> 06-25 19:13:25.657: D/IOIOImpl(16510): Waiting for IOIO connection
>>>>>>> 06-25 19:13:25.712: D/IOIOImpl(16510): Waiting for IOIO connection
>>>>>>> 06-25 19:13:30.009: D/UsbDeviceManager(391): entering USB accessory
>>>>>>> mode: UsbAccessory[mManufacturer=IOIO Open Source Project,
>>>>>>> mModel=IOIO, mDescription=IOIO Standard Application, mVersion=IOIO0326,
>>>>>>> mUri=https://github.com/ytai/ioio/wiki/ADK, mSerial=N/A]
>>>>>>>
>>>>>>>
>>>>>>> On Tuesday, 25 June 2013 14:53:44 UTC+1, Ytai wrote:
>>>>>>>>
>>>>>>>> What do you see in logcat after running the failure case?
>>>>>>>>
>>>>>>>>
>>>>>>>> On Mon, Jun 24, 2013 at 12:07 PM, Peakon <[email protected]> wrote:
>>>>>>>>
>>>>>>>>> Hi Ytai
>>>>>>>>>
>>>>>>>>> I have IOIOSimple app and HelloIOIOService installed on my phone.
>>>>>>>>> I have switched USB debugging off an connected the phone to IOIO. I 
>>>>>>>>> got the
>>>>>>>>> message as on the picture 483. I disconnected the cable, counted to 
>>>>>>>>> 10 and
>>>>>>>>> plugged it back in. Connection worked again no problem. I killed 
>>>>>>>>> IOIOSimple
>>>>>>>>> app and started HelloIOIOService I got the message as on the picture 
>>>>>>>>> 485. I
>>>>>>>>> ticked the box Use by default for this USB accessory and OKed it.
>>>>>>>>> Connection worked and yellow LED was flashing. I disconnected USB 
>>>>>>>>> cable
>>>>>>>>> counted to 10 and plugged it back and got the message as 483 again. 
>>>>>>>>> The
>>>>>>>>> phone does not recconect to the HelloIOIOService.
>>>>>>>>>
>>>>>>>>> Please help.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Monday, 24 June 2013 06:18:33 UTC+1, Ytai wrote:
>>>>>>>>>
>>>>>>>>>> There's a apparent Android bug that prevents an accessory
>>>>>>>>>> connection from being detected if it's plugged out and then in again 
>>>>>>>>>> too
>>>>>>>>>> quickly (1 second or so). Could it be that this is what you're 
>>>>>>>>>> actually
>>>>>>>>>> seeing, or is it happening even if you're waiting a few seconds 
>>>>>>>>>> before
>>>>>>>>>> reconnecting?
>>>>>>>>>> Also, what exactly do you mean by "the message that no accessory
>>>>>>>>>> devices found and no connection achieved"?
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Sat, Jun 22, 2013 at 6:49 AM, Peakon <[email protected]> wrote:
>>>>>>>>>>
>>>>>>>>>>>  Hi Everyone
>>>>>>>>>>>
>>>>>>>>>>> I have a problem running HelloIOIOService in accessory mode. If
>>>>>>>>>>> I start HelloIOIOService i get a message about using as USB 
>>>>>>>>>>> accessory
>>>>>>>>>>> device. I tick the box and apply yes and get connection working OK.
>>>>>>>>>>>
>>>>>>>>>>> If I unplug the usb cable to IOIO and plug it back I get the
>>>>>>>>>>> message that no accessory devices found and no connection achieved. 
>>>>>>>>>>> If I
>>>>>>>>>>> stop the service and restart it again the connection is working as 
>>>>>>>>>>> if I
>>>>>>>>>>> have done it for the first time.
>>>>>>>>>>>
>>>>>>>>>>> I use IOIO V1 Bootloader 3.04 Firmware 3.26. The phone Galaxy
>>>>>>>>>>> Nexus - Android 4.2.2. I have USB debugging switched off when 
>>>>>>>>>>> connecting in
>>>>>>>>>>> accessory mode. Also connection via Bluetooth work OK when USB 
>>>>>>>>>>> debugging is
>>>>>>>>>>> enabled.
>>>>>>>>>>>
>>>>>>>>>>> If I use IOIOSimle App in accessory mode it works fine with
>>>>>>>>>>> connecting and disconnecting usb cable.
>>>>>>>>>>>
>>>>>>>>>>> I guess the problem with HelloIOIOService may be related to the
>>>>>>>>>>> Manifest configuration? Any ideas how to correct that?
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> 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].
>>>>>>>>> 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].
>>>> 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].
> 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.

Reply via email to