
Ritesh Mehandiratta • over 10 years ago
Enabler app is giving force close error
Hi i am trying to get started with OpenXC platform. for this we have to first install Enabler app.but when i install it and run it .it is giving me force close error with logcat .
04-29 11:13:26.984: W/UsbVehicleInterface(363): No USB service found on this device -- can't use USB vehicle interface
04-29 11:13:26.994: W/VehicleInterfaceFactory(363): class com.openxc.interfaces.usb.UsbVehicleInterface's constructor threw an exception
04-29 11:13:26.994: W/VehicleInterfaceFactory(363): java.lang.reflect.InvocationTargetException
04-29 11:13:26.994: W/VehicleInterfaceFactory(363): at com.openxc.interfaces.usb.UsbVehicleInterface.(UsbVehicleInterface.java:124)
04-29 11:13:26.994: W/VehicleInterfaceFactory(363): at java.lang.reflect.Constructor.constructNative(Native Method)
04-29 11:13:26.994: W/VehicleInterfaceFactory(363): at java.lang.reflect.Constructor.newInstance(Constructor.java:446)
04-29 11:13:26.994: W/VehicleInterfaceFactory(363): at com.openxc.interfaces.VehicleInterfaceFactory.build(VehicleInterfaceFactory.java:89)
04-29 11:13:26.994: W/VehicleInterfaceFactory(363): at com.openxc.remote.VehicleService.addVehicleInterface(VehicleService.java:164)
04-29 11:13:26.994: W/VehicleInterfaceFactory(363): at com.openxc.remote.VehicleService.addVehicleInterface(VehicleService.java:153)
04-29 11:13:26.994: W/VehicleInterfaceFactory(363): at com.openxc.remote.VehicleService.initializeDefaultSources(VehicleService.java:93)
04-29 11:13:26.994: W/VehicleInterfaceFactory(363): at com.openxc.remote.VehicleService.onBind(VehicleService.java:82)
04-29 11:13:26.994: W/VehicleInterfaceFactory(363): at android.app.ActivityThread.handleBindService(ActivityThread.java:2983)
04-29 11:13:26.994: W/VehicleInterfaceFactory(363): at android.app.ActivityThread.access$3400(ActivityThread.java:125)
04-29 11:13:26.994: W/VehicleInterfaceFactory(363): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2090)
04-29 11:13:26.994: W/VehicleInterfaceFactory(363): at android.os.Handler.dispatchMessage(Handler.java:99)
04-29 11:13:26.994: W/VehicleInterfaceFactory(363): at android.os.Looper.loop(Looper.java:123)
04-29 11:13:26.994: W/VehicleInterfaceFactory(363): at android.app.ActivityThread.main(ActivityThread.java:4627)
04-29 11:13:26.994: W/VehicleInterfaceFactory(363): at java.lang.reflect.Method.invokeNative(Native Method)
04-29 11:13:26.994: W/VehicleInterfaceFactory(363): at java.lang.reflect.Method.invoke(Method.java:521)
04-29 11:13:26.994: W/VehicleInterfaceFactory(363): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:868)
04-29 11:13:26.994: W/VehicleInterfaceFactory(363): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:626)
04-29 11:13:26.994: W/VehicleInterfaceFactory(363): at dalvik.system.NativeStart.main(Native Method)
04-29 11:13:26.994: W/VehicleInterfaceFactory(363): Caused by: com.openxc.sources.DataSourceException: No USB service found on this device -- can't use USB vehicle interface
04-29 11:13:26.994: W/VehicleInterfaceFactory(363): at com.openxc.interfaces.usb.UsbVehicleInterface.(UsbVehicleInterface.java:91)
04-29 11:13:26.994: W/VehicleInterfaceFactory(363): ... 19 more
04-29 11:13:26.994: W/VehicleService(363): Unable to add vehicle interface
04-29 11:13:26.994: W/VehicleService(363): com.openxc.interfaces.VehicleInterfaceException: class com.openxc.interfaces.usb.UsbVehicleInterface's constructor threw an exception
04-29 11:13:26.994: W/VehicleService(363): at com.openxc.interfaces.VehicleInterfaceFactory.build(VehicleInterfaceFactory.java:103)
04-29 11:13:26.994: W/VehicleService(363): at com.openxc.remote.VehicleService.addVehicleInterface(VehicleService.java:164)
04-29 11:13:26.994: W/VehicleService(363): at com.openxc.remote.VehicleService.addVehicleInterface(VehicleService.java:153)
04-29 11:13:26.994: W/VehicleService(363): at com.openxc.remote.VehicleService.initializeDefaultSources(VehicleService.java:93)
04-29 11:13:26.994: W/VehicleService(363): at com.openxc.remote.VehicleService.onBind(VehicleService.java:82)
04-29 11:13:26.994: W/VehicleService(363): at android.app.ActivityThread.handleBindService(ActivityThread.java:2983)
04-29 11:13:26.994: W/VehicleService(363): at android.app.ActivityThread.access$3400(ActivityThread.java:125)
04-29 11:13:26.994: W/VehicleService(363): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2090)
04-29 11:13:26.994: W/VehicleService(363): at android.os.Handler.dispatchMessage(Handler.java:99)
04-29 11:13:26.994: W/VehicleService(363): at android.os.Looper.loop(Looper.java:123)
04-29 11:13:26.994: W/VehicleService(363): at android.app.ActivityThread.main(ActivityThread.java:4627)
04-29 11:13:26.994: W/VehicleService(363): at java.lang.reflect.Method.invokeNative(Native Method)
04-29 11:13:26.994: W/VehicleService(363): at java.lang.reflect.Method.invoke(Method.java:521)
04-29 11:13:26.994: W/VehicleService(363): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:868)
04-29 11:13:26.994: W/VehicleService(363): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:626)
04-29 11:13:26.994: W/VehicleService(363): at dalvik.system.NativeStart.main(Native Method)
04-29 11:13:27.174: W/ActivityManager(60): Activity pause timeout for HistoryRecord{44e77280 com.openxc.enabler/.OpenXcEnablerActivity}
04-29 11:13:37.353: W/ActivityManager(60): Activity destroy timeout for HistoryRecord{44e77280 com.openxc.enabler/.OpenXcEnablerActivity}
this clearlyindicates that the enabler app when open it must be connected with USB device .please fix it or give guideline how to run it with driving.json file that you provided in getting started tutorial .
Comments are closed.
1 comment
Christopher Peplin • over 10 years ago
Hi Ritesh,
There was a regression in the latest release that introduced this error on Android 2.3 and 3.0/3.1 devices - it's been fixed in the latest version on GitHub (https://github.com/openxc/openxc-android) - v4.0.1.
I also highly recommend looking for assistance (if you need it) in the Google Group: https://groups.google.com/forum/?fromgroups#!forum/openxc - someone encountered this issue on Thursday last week and we started working on the fix.
Chris