This line is suspicious: 06-18 15:33:38.761 W/IntentResolver( 932): resolveIntent failed: found match, but none with CATEGORY_DEFAULT
Not even sure it's related, but you may want to try to play with the intent filter in the manifest file and see if you can somehow get the USB connection event to find its way to the app. On Wed, Jun 18, 2014 at 4:28 PM, Ted dy <[email protected]> wrote: > To add to this, I also have an HTC One M8 that won't communicate to the > IOIO. The IOIO works flawlessly with my Nexus 7 tablet. > Android recognizes the accessory and launches HelloIOIO but the LED does > not come on. Here are the relevant (I think) bits from my logcat > > 06-18 15:33:38.731 V/UsbDeviceManager( 932): [USBNET] USB UEVENT: > {USB_STATE=CONFIGURED, SUBSYSTEM=android_usb, > DEVPATH=/devices/virtual/android_usb/android0, SEQNUM=7878, ACTION=change} > 06-18 15:33:38.731 D/UsbDeviceManager( 932): [USBNET] handleMessage: 0; > mConnected=true, mConfiguration=false > 06-18 15:33:38.731 D/UsbDeviceManager( 932): entering USB accessory mode: > UsbAccessory[mManufacturer=IOIO Open Source Project, mModel=IOIO, > mDescription=IOIO Standard Application, mVersion=IOIO0500, mUri= > https://github.com/ytai/ioio/wiki/ADK, mSerial=N/A] > 06-18 15:33:38.731 W/CpuWake ( 932): >>nativeAcquireCpuPerfWakeLock() > 06-18 15:33:38.731 W/CpuWake ( 932): <<nativeAcquireCpuPerfWakeLock() > 06-18 15:33:38.731 I/ActivityManager( 932): START u0 {flg=0x10000000 > cmp=com.android.systemui/.usb.UsbResolverActivity (has extras)} from pid 932 > 06-18 15:33:38.741 D/UsbDeviceManager( 932): sendStickyBroadcast: > connected= true, configured= true; SetCurrentFunctions= accessory > 06-18 15:33:38.761 W/IntentResolver( 932): resolveIntent failed: found > match, but none with CATEGORY_DEFAULT > 06-18 15:33:38.841 I/ActivityManager( 932): Activity reported stop, but > no longer stopping: ActivityRecord{4255cc68 u0 > com.android.systemui/.usb.UsbResolverActivity t38 f} > 06-18 15:33:39.091 D/TelephonyRegistry( 932): This is not dual project > 06-18 15:33:40.271 W/ContextImpl(29005): Calling a method in the system > process without a qualified user: android.app.ContextImpl.startService:1719 > android.content.ContextWrapper.startService:501 > android.content.ContextWrapper.startService:501 > com.android.settings.PSReceiver.onReceive:36 > android.app.ActivityThread.handleReceiver:2845 > 06-18 15:33:40.291 W/InputMethodManagerService( 932): Window already > focused, ignoring focus gain of: > com.android.internal.view.IInputMethodClient$Stub$Proxy@426dc5b8 > attribute=EditorInfo { packageName=ioio.examples.hello, inputType=0x0, > imeOptions=0x0, privateImeOptions=null }, token = > android.os.BinderProxy@41ec7c48, client pid=29112, inputType=0x0 > 6-18 15:33:48.991 V/UsbDeviceManager( 932): [USBNET] USB UEVENT: > {USB_STATE=DISCONNECTED, SUBSYSTEM=android_usb, > DEVPATH=/devices/virtual/android_usb/android0, SEQNUM=7906, ACTION=change} > 06-18 15:33:48.991 W/Vold ( 370): Ignoring unknown switch > 'usb_connect2pc' > 06-18 15:33:48.991 V/UsbDeviceManager( 932): [USBNET] USB UEVENT: > {SUBSYSTEM=switch, SWITCH_STATE=0, > DEVPATH=/devices/virtual/switch/usb_connect2pc, SEQNUM=7907, ACTION=change, > SWITCH_NAME=usb_connect2pc} > 06-18 15:33:48.991 D/UsbDeviceManager( 932): [USBNET] update2: 10,0 > 06-18 15:33:48.991 D/UsbDeviceManager( 932): [USBNET] handleMessage: 10; > mConnected=true, mConfiguration=true > 06-18 15:33:48.991 D/UsbDeviceManager( 932): [USBNET] mHtcMode= 0 > 06-18 15:33:48.991 W/ContextImpl( 932): Calling a method in the system > process without a qualified user: > android.app.ContextImpl.sendStickyBroadcast:1521 > com.android.server.usb.UsbDeviceManager$UsbHandler.handleMessage:1489 > android.os.Handler.dispatchMessage:102 android.os.Looper.loop:157 > android.os.HandlerThread.run:61 > 06-18 15:33:49.001 D/UsbDeviceManager( 932): [USBNET] sendStickyBroadcast > ACTION_USB_CONNECT2PC: 0 > 06-18 15:33:49.011 D/MountService( 932): sharing = 0 > 06-18 15:33:49.011 D/MountService( 932): false PCTOOL.ISO > 06-18 15:33:49.011 I/Vold ( 370): current ISO is > /system/etc/PCTOOL.ISO target ISO is /system/etc/PCTOOL.ISO > 06-18 15:33:49.991 D/UsbDeviceManager( 932): [USBNET] handleMessage: 0; > mConnected=true, mConfiguration=true > 06-18 15:33:49.991 D/UsbDeviceManager( 932): exited USB accessory mode > 06-18 15:33:49.991 D/UsbDeviceManager( 932): > setEnabledFunctions(mtp,mass_storage; false; mAcmEnabled: true) > 06-18 15:33:49.991 D/UsbDeviceManager( 932): send Fake intent while > setEnabledFunctions > 06-18 15:33:49.991 D/UsbDeviceManager( 932): [USBNET] check if ACM should > be enabled > 06-18 15:33:50.001 D/UsbDeviceManager( 932): setUsbConfig(none) > 06-18 15:33:50.001 D/UsbDeviceManager( 932): > setUsbConfig(mtp,mass_storage,acm) > 06-18 15:33:50.221 D/UsbDeviceManager( 932): send Fake intent while > setUsbConfig > 06-18 15:33:50.221 D/UsbDeviceManager( 932): [USBNET] gotDisconnected, > disable acm function > 06-18 15:33:50.231 D/UsbDeviceManager( 932): > setEnabledFunctions(mtp,adb,mass_storage; false; mAcmEnabled: false) > 06-18 15:33:50.231 D/UsbDeviceManager( 932): send Fake intent while > setEnabledFunctions > 06-18 15:33:50.231 D/UsbDeviceManager( 932): sendStickyBroadcast: > connected= false, configured= false; SetCurrentFunctions= mass_storage > 06-18 15:33:50.231 D/UsbDeviceManager( 932): [USBNET] check if ACM should > be enabled > 06-18 15:33:50.231 D/UsbDeviceManager( 932): setUsbConfig(none) > 06-18 15:33:50.231 D/UsbDeviceManager( 932): > setUsbConfig(mtp,mass_storage) > 06-18 15:33:50.501 D/UsbDeviceManager( 932): send Fake intent while > setUsbConfig > 06-18 15:33:50.501 D/UsbDeviceManager( 932): sendStickyBroadcast: > connected= false, configured= false; SetCurrentFunctions= mtp,mass_storage > > On Tuesday, June 17, 2014 8:45:32 AM UTC-7, Ytai wrote: > >> It is possible that your power supply is not adequate. Try connecting it >> to your PC with *nothing* else connected to the IOIO (neither the LEDs >> nor the power supply you've made). Make sure the host mode switch is in the >> "A" position. Make sure the current limiting trimmer is all the way >> clockwise. >> >> >> On Sun, Jun 15, 2014 at 2:28 AM, Connor Taylor <[email protected]> wrote: >> >>> Hey there. So I recently purchased an IOIO-OTG board from Sparkfun >>> along with a bluetooth adapter and a string of Android addressable LEDs. >>> >>> I wired up a USB cable by stripping the ground and power cables and then >>> soldered them to the board to the GND and VIN ports respectively. I plugged >>> this into a USB power source. From there I took the USB OTG dongle and >>> plugged my phone (HTC One M8 running 4.4.2) via micro USB. >>> >>> My issue comes in when I try to use Hello IOIO or IOIO Hardware Tester >>> to verify connection. It doesn't detect it. I also tried it with the >>> Bluetooth dongle and my phone does not find the dongle. >>> >>> I tried plugging the board directly into my PC and tried using IOIODude >>> but it does not connect either. Under Device Manager it shows it as >>> IOIO-OTG(COM8) but it has a troubleshooting issue of "Device Will Not Power >>> On" >>> >>> I can get the stat light to show if I power the board and jumper the >>> BOOT and GND pins but other than that I'm at a loss. Any help would be >>> greatly appreciated. >>> >>> -- >>> 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 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.
