Looking for a Odroid XU3 or XU3-Lite

Post Reply
samuelo
Posts: 11
Joined: Thu Apr 04, 2019 1:16 am
languages_spoken: english, german
ODROIDs: XU, XU3, XU4, C2
Has thanked: 5 times
Been thanked: 0
Contact:

Looking for a Odroid XU3 or XU3-Lite

Unread post by samuelo » Tue Jul 16, 2019 9:12 pm

Hi all :)

I'm desperately looking for an Odroid XU3 or XU3 Lite and was wondering if maybe someone has a unused one lying around at home somewhere :) I would obviously pay for it. I'm located in Switzerland, but I could also cover shipping costs from the US or Asia or whereever :)

I appreciate any help, kind regards
samuelo

User avatar
mad_ady
Posts: 6363
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4, C1+, C2, N1, H2, N2
Location: Bucharest, Romania
Has thanked: 144 times
Been thanked: 105 times
Contact:

Re: Looking for a Odroid XU3 or XU3-Lite

Unread post by mad_ady » Tue Jul 16, 2019 10:51 pm

Why do you need an xu3/lite and can't do with an xu4?

samuelo
Posts: 11
Joined: Thu Apr 04, 2019 1:16 am
languages_spoken: english, german
ODROIDs: XU, XU3, XU4, C2
Has thanked: 5 times
Been thanked: 0
Contact:

Re: Looking for a Odroid XU3 or XU3-Lite

Unread post by samuelo » Wed Jul 17, 2019 1:14 am

Because I need the USB OTG port and it has to work with the Android Open Accessory (AOA) protocol. I already tried the C2 and N2 as well, but unfortunately they have a bug in the Android so the AOA doesn't work (for more information see the thread here: viewtopic.php?t=31693 and here: viewtopic.php?f=178&t=34671). On the XU3 however it works like a charm.

User avatar
mad_ady
Posts: 6363
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4, C1+, C2, N1, H2, N2
Location: Bucharest, Romania
Has thanked: 144 times
Been thanked: 105 times
Contact:

Re: Looking for a Odroid XU3 or XU3-Lite

Unread post by mad_ady » Wed Jul 17, 2019 3:31 am

Oh, I forgot about that feature. Good luck!

User avatar
odroid
Site Admin
Posts: 31760
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID
Has thanked: 83 times
Been thanked: 241 times
Contact:

Re: Looking for a Odroid XU3 or XU3-Lite

Unread post by odroid » Wed Jul 17, 2019 9:36 am

AOAv1 (Protocol 1.0 for OTG device mode) was removed and we can't support it anymore.
AOAv2 (Protocol 2.0 for Host port) should work out of the box.
We will confirm the AOAv2 feature on the ODROID-N2 soon.
These users thanked the author odroid for the post:
samuelo (Wed Jul 17, 2019 10:47 pm)

User avatar
codewalker
Posts: 691
Joined: Mon Feb 25, 2013 11:03 am
languages_spoken: english
ODROIDs: all
Has thanked: 28 times
Been thanked: 20 times
Contact:

Re: Looking for a Odroid XU3 or XU3-Lite

Unread post by codewalker » Wed Jul 17, 2019 11:40 am

AOAv2 feature works fine on the ODROID-N2 Android 9.0.
Screenshot_20190717-113611.png
Screenshot_20190717-113611.png (88.91 KiB) Viewed 748 times
These users thanked the author codewalker for the post:
samuelo (Wed Jul 17, 2019 10:47 pm)

User avatar
odroid
Site Admin
Posts: 31760
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID
Has thanked: 83 times
Been thanked: 241 times
Contact:

Re: Looking for a Odroid XU3 or XU3-Lite

Unread post by odroid » Wed Jul 17, 2019 12:36 pm

@samuelo,
Since we have no USB host device can support AOA.V1 protocol, we have to find a PC software to emulate/simulate the AOA.V1.
Do you have any idea?

samuelo
Posts: 11
Joined: Thu Apr 04, 2019 1:16 am
languages_spoken: english, german
ODROIDs: XU, XU3, XU4, C2
Has thanked: 5 times
Been thanked: 0
Contact:

Re: Looking for a Odroid XU3 or XU3-Lite

Unread post by samuelo » Wed Jul 17, 2019 10:39 pm

@codewalker: hmm okay, I mean I tried it just when the N2 came out, so either there was a firmware update since then or my device really is using the AOAv1 protocol... I'll update the firmware and check later today or tomorrow.

@odroid: Sorry I do not know a way to simulate it. I am using a DJI remote controller for the DJI Mavic in case you have access to one of those. The DJI Go 4 app for example uses the AOA to connect to Smartphones (or in my case to the Odroid)

phaseshifter
Posts: 3452
Joined: Fri May 08, 2015 9:12 am
languages_spoken: english
ODROIDs: U-2,U3+,,XU-3,,XU3-LITE,,XU-4
C1+,,C-2,,,
N-1,,N-2,...other odroid acc`s as well
Has thanked: 35 times
Been thanked: 42 times
Contact:

Re: Looking for a Odroid XU3 or XU3-Lite

Unread post by phaseshifter » Fri Jul 19, 2019 8:55 pm

i have two of them xu3 lites....one has a bad media select switch and the other is in i cannot say perfect condition..but yes.. there you have it..all ports work fine as far as i know
Build It And They Will Come...Be Bold And Mighty Forces Will Come To Your Aid..!!!

samuelo
Posts: 11
Joined: Thu Apr 04, 2019 1:16 am
languages_spoken: english, german
ODROIDs: XU, XU3, XU4, C2
Has thanked: 5 times
Been thanked: 0
Contact:

Re: Looking for a Odroid XU3 or XU3-Lite

Unread post by samuelo » Sat Jul 20, 2019 1:39 am

@phaseshifter: Oh great, where are you from? (We could switch to PM if you want)

@codewalker: I did an update to the most recent Android 9 release, it still doesn't work. I assume this means it uses the AOAv1 :-/

User avatar
tobetter
Posts: 3764
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: X, X2, U2, U3, XU3, C1
Location: Paju, South Korea
Has thanked: 28 times
Been thanked: 128 times
Contact:

Re: Looking for a Odroid XU3 or XU3-Lite

Unread post by tobetter » Sat Jul 20, 2019 2:00 am

samuelo wrote:
Sat Jul 20, 2019 1:39 am
@phaseshifter: Oh great, where are you from? (We could switch to PM if you want)

@codewalker: I did an update to the most recent Android 9 release, it still doesn't work. I assume this means it uses the AOAv1 :-/
@codewalker is doing debugging AOAv1 on ODROID-C2 and -N2 and not finished yet. Let me help him to figure out.

phaseshifter
Posts: 3452
Joined: Fri May 08, 2015 9:12 am
languages_spoken: english
ODROIDs: U-2,U3+,,XU-3,,XU3-LITE,,XU-4
C1+,,C-2,,,
N-1,,N-2,...other odroid acc`s as well
Has thanked: 35 times
Been thanked: 42 times
Contact:

Re: Looking for a Odroid XU3 or XU3-Lite

Unread post by phaseshifter » Sat Jul 20, 2019 10:27 am

you should keep a look out at amerdroid reseller often has refurbished xu3-lite`s.i have a couple and they work fine but cpu power is lower than an xu3 by 200Mhz and i think 100Mhz..on the cpu cores..
Build It And They Will Come...Be Bold And Mighty Forces Will Come To Your Aid..!!!

User avatar
codewalker
Posts: 691
Joined: Mon Feb 25, 2013 11:03 am
languages_spoken: english
ODROIDs: all
Has thanked: 28 times
Been thanked: 20 times
Contact:

Re: Looking for a Odroid XU3 or XU3-Lite

Unread post by codewalker » Mon Jul 22, 2019 9:48 am

I have been trying to enable USB Accessory on C2 and N2.
I'm sorry, please wait a little longer.

I tried to use USB Accessory on C1(KitKat), It worked like XU3 lite.
I hope it helps you.
These users thanked the author codewalker for the post:
samuelo (Mon Jul 22, 2019 7:59 pm)

samuelo
Posts: 11
Joined: Thu Apr 04, 2019 1:16 am
languages_spoken: english, german
ODROIDs: XU, XU3, XU4, C2
Has thanked: 5 times
Been thanked: 0
Contact:

Re: Looking for a Odroid XU3 or XU3-Lite

Unread post by samuelo » Mon Jul 22, 2019 8:00 pm

@codewalker: ah that's great to hear :D I could get my hands on a C1 and will try it out today, thanks!

edit: C1 with Kitkat (4.4.4) doesn't work either. Are you sure you tested the AOAv1?

User avatar
tobetter
Posts: 3764
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: X, X2, U2, U3, XU3, C1
Location: Paju, South Korea
Has thanked: 28 times
Been thanked: 128 times
Contact:

Re: Looking for a Odroid XU3 or XU3-Lite

Unread post by tobetter » Fri Aug 09, 2019 1:09 am

samuelo wrote:
Mon Jul 22, 2019 8:00 pm
@codewalker: ah that's great to hear :D I could get my hands on a C1 and will try it out today, thanks!

edit: C1 with Kitkat (4.4.4) doesn't work either. Are you sure you tested the AOAv1?
We are testing AoAv1 with ODROID-C2 and ODROID-N2 with a couple of patches and hope to release this week or next week after some testing.
These users thanked the author tobetter for the post (total 2):
samuelo (Fri Aug 09, 2019 4:34 am) • codewalker (Fri Aug 09, 2019 6:21 am)

samuelo
Posts: 11
Joined: Thu Apr 04, 2019 1:16 am
languages_spoken: english, german
ODROIDs: XU, XU3, XU4, C2
Has thanked: 5 times
Been thanked: 0
Contact:

Re: Looking for a Odroid XU3 or XU3-Lite

Unread post by samuelo » Fri Aug 09, 2019 4:35 am

This is great news! Thanks for the effort, I really hope it works...

User avatar
codewalker
Posts: 691
Joined: Mon Feb 25, 2013 11:03 am
languages_spoken: english
ODROIDs: all
Has thanked: 28 times
Been thanked: 20 times
Contact:

Re: Looking for a Odroid XU3 or XU3-Lite

Unread post by codewalker » Mon Aug 12, 2019 12:04 pm

These users thanked the author codewalker for the post:
samuelo (Mon Aug 12, 2019 10:27 pm)

samuelo
Posts: 11
Joined: Thu Apr 04, 2019 1:16 am
languages_spoken: english, german
ODROIDs: XU, XU3, XU4, C2
Has thanked: 5 times
Been thanked: 0
Contact:

Re: Looking for a Odroid XU3 or XU3-Lite

Unread post by samuelo » Mon Aug 12, 2019 10:33 pm

@tobetter, @codewalker:
I tested the test firmware for N2 with my device (DJI Mavic remote controller)... now it recognizes the USB Accessory and the dialogue box pops up (where you select which app to use the device with). However, after that it doesn't work as it should. It seems to me that the initial handshake now completes well, but there is still some issue in the data transmission part. If it is any help to you, is there any output I could log to facilitate the debug process?

User avatar
tobetter
Posts: 3764
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: X, X2, U2, U3, XU3, C1
Location: Paju, South Korea
Has thanked: 28 times
Been thanked: 128 times
Contact:

Re: Looking for a Odroid XU3 or XU3-Lite

Unread post by tobetter » Tue Aug 13, 2019 11:34 am

samuelo wrote:
Mon Aug 12, 2019 10:33 pm
@tobetter, @codewalker:
I tested the test firmware for N2 with my device (DJI Mavic remote controller)... now it recognizes the USB Accessory and the dialogue box pops up (where you select which app to use the device with). However, after that it doesn't work as it should. It seems to me that the initial handshake now completes well, but there is still some issue in the data transmission part. If it is any help to you, is there any output I could log to facilitate the debug process?
Can you grab any logs from N2 or your accessory?
Have you set the VID/PID of N2 on your accessory as well?
By any chance, have you tried to run with C2?

samuelo
Posts: 11
Joined: Thu Apr 04, 2019 1:16 am
languages_spoken: english, german
ODROIDs: XU, XU3, XU4, C2
Has thanked: 5 times
Been thanked: 0
Contact:

Re: Looking for a Odroid XU3 or XU3-Lite

Unread post by samuelo » Tue Aug 13, 2019 7:42 pm

tobetter wrote:
Tue Aug 13, 2019 11:34 am
samuelo wrote:
Mon Aug 12, 2019 10:33 pm
@tobetter, @codewalker:
I tested the test firmware for N2 with my device (DJI Mavic remote controller)... now it recognizes the USB Accessory and the dialogue box pops up (where you select which app to use the device with). However, after that it doesn't work as it should. It seems to me that the initial handshake now completes well, but there is still some issue in the data transmission part. If it is any help to you, is there any output I could log to facilitate the debug process?
Can you grab any logs from N2 or your accessory?
Have you set the VID/PID of N2 on your accessory as well?
By any chance, have you tried to run with C2?
So I tried with the C2 as well, and it reacts the same way as the N2: The dialogue box pops up, but it seems further data exchange is hindered. When plugging in the device I get the following logcat output (on the C2):

Code: Select all

[b]08-13 10:25:25.198  4802  4802 E DJIUsbAccessoryReceiver: android.hardware.usb.action.USB_STATE
08-13 10:25:25.198  4802  4802 E DJIUsbAccessoryReceiver: android.hardware.usb.action.USB_STATE: is connected[/b]
08-13 10:25:25.248  3289  3289 W PathParser: Points are too far apart 4.030360828967057
08-13 10:25:25.248  3289  3289 W PathParser: Points are too far apart 4.030360538880159
[b]08-13 10:25:25.366  4802  4802 E DJIUsbAccessoryReceiver: android.hardware.usb.action.USB_STATE
08-13 10:25:25.366  4802  4802 E DJIUsbAccessoryReceiver: android.hardware.usb.action.USB_STATE: is connected
08-13 10:25:25.383  3185  3201 I UsbDeviceManager: Setting USB config to accessory,adb[/b]
08-13 10:25:25.385  4802  4809 I art     : Debugger is no longer active
08-13 10:25:25.386  3289  3313 I art     : Debugger is no longer active
08-13 10:25:25.386  3479  3511 I art     : Debugger is no longer active
08-13 10:25:25.386  3641  3670 I art     : Debugger is no longer active
08-13 10:25:25.386  3504  3547 I art     : Debugger is no longer active
08-13 10:25:25.386  3497  3546 I art     : Debugger is no longer active
08-13 10:25:25.387  3492  3533 I art     : Debugger is no longer active
08-13 10:25:25.387  3185  3191 I art     : Debugger is no longer active
08-13 10:25:25.387  3279  3324 I art     : Debugger is no longer active
08-13 10:25:25.388  4761  4769 I art     : Debugger is no longer active
08-13 10:25:25.388  4356  4363 I art     : Debugger is no longer active
08-13 10:25:25.388  4736  4749 I art     : Debugger is no longer active
08-13 10:25:25.388  3617  3632 I art     : Debugger is no longer active
08-13 10:25:25.389  4779  4786 I art     : Debugger is no longer active
08-13 10:25:25.389  4127  4134 I art     : Debugger is no longer active
08-13 10:25:25.389  4383  4390 I art     : Debugger is no longer active
08-13 10:25:25.389  3517  3565 I art     : Debugger is no longer active
08-13 10:25:25.389  4098  4107 I art     : Debugger is no longer active
[b]08-13 10:25:25.398  3279  3279 D MtpService: starting MTP server in MTP mode
08-13 10:25:25.720  4802  4802 E DJIUsbAccessoryReceiver: android.hardware.usb.action.USB_STATE
08-13 10:25:25.720  4802  4802 E DJIUsbAccessoryReceiver: android.hardware.usb.action.USB_STATE: is connected
08-13 10:25:25.889  3185  3201 D UsbDeviceManager: entering USB accessory mode: UsbAccessory[mManufacturer=DJI, mModel=T600, mDescription=DJI Inspire 1, mVersion=v0.0.0.0, mUri=www.dji.com, mSerial=000000000000000]
08-13 10:25:25.889  3185  3201 I ActivityManager: START u0 {flg=0x10000000 cmp=com.android.systemui/.usb.UsbConfirmActivity (has extras)} from uid 1000 on display 0
08-13 10:25:25.918  4802  4802 E com.example.bridge.ConnectionActivity: onPause
08-13 10:25:25.930  4802  4802 E DJIUsbAccessoryReceiver: android.hardware.usb.action.USB_STATE
08-13 10:25:25.931  4802  4802 E DJIUsbAccessoryReceiver: android.hardware.usb.action.USB_STATE: is connected
08-13 10:25:25.993  3185  3204 I ActivityManager: Displayed com.android.systemui/.usb.UsbConfirmActivity: +70ms (total +54m1s176ms)
08-13 10:25:39.825  2861  3213 D audio_hw_primary: out_set_parameters(kvpairs(routing=2), out_device=0x2)[/b]
[b]08-13 10:25:39.831  3185  4354 I ActivityManager: START u0 {act=android.hardware.usb.action.USB_ACCESSORY_ATTACHED flg=0x10000000 cmp=com.example.bridge/dji.sdk.sdkmanager.DJIAoaControllerActivity (has extras)} from uid 10015 on display 0[/b]
08-13 10:25:39.835  3185  3528 W InputMethodManagerService: Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@243d1be attribute=null, token = android.os.BinderProxy@4deb6dd
08-13 10:25:39.836  2861  3213 D audio_hw_primary: start_output_stream(adev->out_device=0x2, adev->mode=0)
08-13 10:25:39.836  2861  3213 D audio_hw_primary: select_devices(mode=0, out_device=0x2)
08-13 10:25:39.836  2861  3213 D audio_hw_primary: select_devices : hs=0 , hp=0, sp=2, hdmi=0x0,earpiece=0x0
08-13 10:25:39.836  2861  3213 D audio_hw_primary: select_devices : in_device(0x4), mic_in(0x4), headset_mic(0)
08-13 10:25:39.836  2861  3213 D audio_hw_primary: select_devices : output_standby=1,input_standby=1
08-13 10:25:39.836  2861  3213 D audio_hw_primary: *start_output_stream, open card(0) port(0)
08-13 10:25:39.836  2861  3213 D audio_hw_primary: channels=2---format=0---period_count4---period_size1024---rate=48000---
08-13 10:25:39.895  2861  3213 D AudioFlinger: mixer(0xf4540000) throttle end: throttle time(62)
[b]08-13 10:25:39.931  4802  4802 E DJIUsbAccessoryReceiver: com.dji.accessory.USB_ACCESSORY_ATTACHED
08-13 10:25:39.932  4802  4802 E DJIUsbAccessoryReceiver: getModel: T600
08-13 10:25:39.933  4802  4802 E DJIUsbAccessoryReceiver: getManufacturer: DJI
08-13 10:25:39.933  4802  4802 E DJIUsbAccessoryReceiver: hasPermission 
08-13 10:25:39.933  4802  4802 E DJIUsbAccessoryReceiver: openAccessory: UsbAccessory[mManufacturer=DJI, mModel=T600, mDescription=DJI Inspire 1, mVersion=v0.0.0.0, mUri=www.dji.com, mSerial=000000000000000]
08-13 10:25:39.934  4802  4802 E DJIUsbAccessoryReceiver: mFileDescriptor: mInputStream=java.io.FileInputStream@453b935
08-13 10:25:39.935  4802  4802 E DJIUsbAccessoryReceiver: mFileDescriptor: FileDescriptor=true
08-13 10:25:39.935  4802  4802 E linkDeamon: stopDaemon AOA[/b]
08-13 10:25:39.936  4802  4802 E c       : djisocket destroy
08-13 10:25:39.936  4802  4802 E daemon  : destroy wifi 1
08-13 10:25:39.937  4802  4802 E a       : djisocket destroy
08-13 10:25:39.937  4802  4802 E daemon  : destroy wifi 2
08-13 10:25:39.937  4802  4802 E b       : udt destroy 1 9000
08-13 10:25:39.937  4802  4802 E b       : udt destroy 2 9000
08-13 10:25:39.937  4802  4802 E daemon  : destroy wifi 3
08-13 10:25:39.938  4802  4802 E P3CCameraService: udt destroy 1 9001
08-13 10:25:39.938  4802  4802 E P3CCameraService: udt destroy 2 9001
08-13 10:25:39.938  4802  4802 E daemon  : destroy wifi 4
08-13 10:25:39.938  4802  4802 E SwUdpService: sw udt destroy 1 N/A
08-13 10:25:39.938  4802  4802 E SwUdpService: sw udt destroy 2 N/A
08-13 10:25:39.938  4802  4802 E daemon  : destroy wifi 5
08-13 10:25:39.939  4802  4802 E b       : djisocket destroy
08-13 10:25:39.939  4802  4802 E daemon  : destroy wifi 6
08-13 10:25:39.940  4802  4802 E a       : djisocket destroy
08-13 10:25:39.940  4802  4802 E daemon  : destroy wifi 7
08-13 10:25:39.989  3185  3539 W InputMethodManagerService: Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@674bca attribute=null, token = android.os.BinderProxy@4deb6dd
08-13 10:25:39.996  3289  3438 D OpenGLRenderer: endAllStagingAnimators on 0xdf02d880 (RippleDrawable) with handle 0xdff524e0
08-13 10:25:39.997  4802  5063 E a       : event:ConnectOK
08-13 10:25:39.998  4802  4885 E a       : receive msg MSG_RETRY_DETECT_ENABLE
08-13 10:25:39.999  4802  5063 E a       : send MSG_RETRY_DETECT_ENABLE
08-13 10:25:39.999  4802  4885 E a       : isWifiLink:false isWifiConnected:false isMobileDataEnabled:false
08-13 10:25:40.001  4802  4802 E com.example.bridge.ConnectionActivity: onResume
08-13 10:25:41.999  4802  4885 E a       : receive msg MSG_RETRY_DETECT_ENABLE
08-13 10:25:42.001  4802  4885 E a       : isWifiLink:false isWifiConnected:false isMobileDataEnabled:false
08-13 10:25:42.885  2861  3213 D audio_hw_primary: do_output_standby(0xf61ac380)
08-13 10:25:44.003  4802  4885 E a       : receive msg MSG_RETRY_DETECT_ENABLE
08-13 10:25:44.003  4802  4885 E a       : isWifiLink:false isWifiConnected:false isMobileDataEnabled:false
08-13 10:25:46.004  4802  4885 E a       : receive msg MSG_RETRY_DETECT_ENABLE
08-13 10:25:46.005  4802  4885 E a       : isWifiLink:false isWifiConnected:false isMobileDataEnabled:false
08-13 10:25:48.006  4802  4885 E a       : receive msg MSG_RETRY_DETECT_ENABLE
08-13 10:25:48.007  4802  4885 E a       : isWifiLink:false isWifiConnected:false isMobileDataEnabled:false
08-13 10:25:49.999  4802  4885 E a       : receive msg MSG_RETRY_DETECT_ENABLE_TIMEOUT
I put the lines I found interesting in bold. Especially the line " linkDeamon: stopDaemon AOA" suggests that the AOA protocol is stopped immediately after starting it
I could do the same for the N2...

The code on the device in not open source so I don't know what is going on there... (I can not set the VID/PID) all I know is that with the Odroid XU3 it works fine, so maybe you could check what VID/PID the XU3 announces?

edit: I just realized bold doesn't work in the codeblock, sorry :p

edit2: I had a look at the logcat output of the XU3 where the connection works. It's the following:

Code: Select all

8-13 12:55:03.476  5934  5934 E DJIUsbAccessoryReceiver: android.hardware.usb.action.USB_STATE
08-13 12:55:03.477  5934  5934 E DJIUsbAccessoryReceiver: android.hardware.usb.action.USB_STATE: is connected
08-13 12:55:03.646  5934  5934 E DJIUsbAccessoryReceiver: android.hardware.usb.action.USB_STATE
08-13 12:55:03.648  5934  5934 E DJIUsbAccessoryReceiver: android.hardware.usb.action.USB_STATE: is connected
08-13 12:55:03.667  3317  3383 I UsbDeviceManager: Setting USB config to accessory,adb
08-13 12:55:04.470  5934  5934 E DJIUsbAccessoryReceiver: android.hardware.usb.action.USB_STATE
08-13 12:55:04.471  5934  5934 E DJIUsbAccessoryReceiver: android.hardware.usb.action.USB_STATE: is connected
08-13 12:55:05.402  3317  3383 D UsbDeviceManager: entering USB accessory mode: UsbAccessory[mManufacturer=DJI, mModel=T600, mDescription=DJI Inspire 1, mVersion=v0.0.0.0, mUri=www.dji.com, mSerial=000000000000000]
08-13 12:55:05.433  3317  3383 I ActivityManager: START u0 {act=android.hardware.usb.action.USB_ACCESSORY_ATTACHED flg=0x10000000 cmp=com.example.bridge/dji.sdk.sdkmanager.DJIAoaControllerActivity (has extras)} from uid 1000 on display 0
08-13 12:55:05.442  5934  5934 E com.example.bridge.ConnectionActivity: onPause
08-13 12:55:05.495  5934  5934 E DJIUsbAccessoryReceiver: android.hardware.usb.action.USB_STATE
08-13 12:55:05.496  5934  5934 E DJIUsbAccessoryReceiver: android.hardware.usb.action.USB_STATE: is connected
08-13 12:55:05.497  5934  5934 E DJIUsbAccessoryReceiver: com.dji.accessory.USB_ACCESSORY_ATTACHED
08-13 12:55:05.499  5934  5934 E DJIUsbAccessoryReceiver: getModel: T600
08-13 12:55:05.499  5934  5934 E DJIUsbAccessoryReceiver: getManufacturer: DJI
08-13 12:55:05.501  5934  5934 E DJIUsbAccessoryReceiver: hasPermission 
08-13 12:55:05.502  5934  5934 E DJIUsbAccessoryReceiver: openAccessory: UsbAccessory[mManufacturer=DJI, mModel=T600, mDescription=DJI Inspire 1, mVersion=v0.0.0.0, mUri=www.dji.com, mSerial=000000000000000]
08-13 12:55:05.505  5934  5934 E DJIUsbAccessoryReceiver: mFileDescriptor: mInputStream=java.io.FileInputStream@1f835d9
08-13 12:55:05.506  5934  5934 E DJIUsbAccessoryReceiver: mFileDescriptor: FileDescriptor=true
08-13 12:55:05.508  5934  5934 E linkDeamon: stopDaemon AOA
08-13 12:55:05.509  5934  5934 E c       : djisocket destroy
08-13 12:55:05.509  5934  5934 E daemon  : destroy wifi 1
08-13 12:55:05.510  5934  5934 E a       : djisocket destroy
08-13 12:55:05.510  5934  5934 E daemon  : destroy wifi 2
08-13 12:55:05.511  5934  5934 E b       : udt destroy 1 9000
08-13 12:55:05.511  5934  5934 E b       : udt destroy 2 9000
08-13 12:55:05.512  5934  5934 E daemon  : destroy wifi 3
08-13 12:55:05.512  5934  5934 E P3CCameraService: udt destroy 1 9001
08-13 12:55:05.513  5934  5934 E P3CCameraService: udt destroy 2 9001
08-13 12:55:05.513  5934  5934 E daemon  : destroy wifi 4
08-13 12:55:05.513  5934  5934 E SwUdpService: sw udt destroy 1 N/A
08-13 12:55:05.515  5934  5934 E SwUdpService: sw udt destroy 2 N/A
08-13 12:55:05.515  5934  5934 E daemon  : destroy wifi 5
08-13 12:55:05.516  5934  5934 E b       : djisocket destroy
08-13 12:55:05.516  5934  5934 E daemon  : destroy wifi 6
08-13 12:55:05.517  5934  5934 E a       : djisocket destroy
08-13 12:55:05.517  5934  5934 E daemon  : destroy wifi 7
08-13 12:55:05.630  3317  3568 W InputMethodManagerService: Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@199dd2b attribute=null, token = android.os.BinderProxy@7c94987
08-13 12:55:05.637  5934  6174 E a       : event:ConnectOK
08-13 12:55:05.638  5934  5987 E a       : receive msg MSG_RETRY_DETECT_ENABLE
08-13 12:55:05.640  5934  5987 E a       : isWifiLink:false isWifiConnected:false isMobileDataEnabled:false
08-13 12:55:05.642  5934  6174 E a       : send MSG_RETRY_DETECT_ENABLE
08-13 12:55:05.647  5934  5934 E com.example.bridge.ConnectionActivity: onResume
08-13 12:55:05.666  5934  5993 E DJIPackManager: pack senderType=17 cmdSet=10
08-13 12:55:05.762  5934  5993 E DJIPackManager: post DataCameraEvent.ConnectOK RC
08-13 12:55:05.762  5934  5987 E wm220   : ****resetSwitchFromWifiFlag
08-13 12:55:06.486  5934  5939 I art     : Do partial code cache collection, code=54KB, data=61KB
08-13 12:55:06.488  5934  5939 I art     : After code cache collection, code=50KB, data=58KB
08-13 12:55:06.488  5934  5939 I art     : Increasing code cache capacity to 256KB
08-13 12:55:07.053  5934  6059 D HttpsHelper: verified, return
08-13 12:55:07.449  5934  6045 D HttpsHelper: verified, return
08-13 12:55:07.481  5934  6061 I onLoad  : loaded onLoad.cpp :JNI_OnLoad() go to end --> upgrade verify
08-13 12:55:07.482  5934  6061 D UpgradeVerify: load lib suc
08-13 12:55:07.643  5934  5987 E a       : receive msg MSG_RETRY_DETECT_ENABLE
08-13 12:55:07.645  5934  5987 E a       : isWifiLink:false isWifiConnected:false isMobileDataEnabled:false
I noticed that also here the line "linkDeamon: stopDaemon AOA" is called and it works anyway.

samuelo
Posts: 11
Joined: Thu Apr 04, 2019 1:16 am
languages_spoken: english, german
ODROIDs: XU, XU3, XU4, C2
Has thanked: 5 times
Been thanked: 0
Contact:

Re: Looking for a Odroid XU3 or XU3-Lite

Unread post by samuelo » Tue Aug 13, 2019 9:58 pm

Okay, so further I tried using the official DJI Go 4 app to communicate with the RC and had a look at the logcat output of the N2. There I came across the following error messages:

Code: Select all

08-13 12:03:01.344  4065  4120 W System.err: Caused by: android.system.ErrnoException: write failed: ENODEV (No such device)
08-13 12:03:01.344  4065  4120 W System.err: 	at libcore.io.Linux.writeBytes(Native Method)
08-13 12:03:01.344  4065  4120 W System.err: 	at libcore.io.Linux.write(Linux.java:288)
08-13 12:03:01.344  4065  4120 W System.err: 	at libcore.io.BlockGuardOs.write(BlockGuardOs.java:348)
08-13 12:03:01.344  4065  4120 W System.err: 	at libcore.io.IoBridge.write(IoBridge.java:526)
08-13 12:03:01.344  4065  4120 W System.err: 	... 9 more
08-13 12:03:01.345  4065  4120 W System.err: java.io.IOException: write failed: ENODEV (No such device)
08-13 12:03:01.345  4065  4120 W System.err: 	at libcore.io.IoBridge.write(IoBridge.java:531)
08-13 12:03:01.345  4065  4120 W System.err: 	at java.io.FileOutputStream.write(FileOutputStream.java:381)
08-13 12:03:01.345  4065  4120 W System.err: 	at dji.midware.usb.P3.UsbAccessoryService.sendmessage(SourceFile:304)
08-13 12:03:01.345  4065  4120 W System.err: 	at dji.midware.data.manager.P3.ServiceManager.sendmessage(SourceFile:366)
08-13 12:03:01.345  4065  4120 W System.err: 	at dji.midware.data.manager.P3.t.a(SourceFile:242)
08-13 12:03:01.345  4065  4120 W System.err: 	at dji.midware.data.manager.P3.t.a(SourceFile:41)
08-13 12:03:01.345  4065  4120 W System.err: 	at dji.midware.data.manager.P3.t$b.handleMessage(SourceFile:195)
08-13 12:03:01.345  4065  4120 W System.err: 	at android.os.Handler.dispatchMessage(Handler.java:106)
08-13 12:03:01.345  4065  4120 W System.err: 	at android.os.Looper.loop(Looper.java:193)
08-13 12:03:01.345  4065  4120 W System.err: 	at android.os.HandlerThread.run(HandlerThread.java:65)
08-13 12:03:01.345  4065  4120 W System.err: Caused by: android.system.ErrnoException: write failed: ENODEV (No such device)
and these:

Code: Select all

08-13 12:45:17.961  2995  3017 I UsbDeviceManager: Setting USB config to accessory,adb
08-13 12:45:17.995  3883  3890 W android.traceu: Receiving file descriptor from ADB failed (socket 32): Success
08-13 12:45:17.995  3828  3835 W gedprovisionin: Receiving file descriptor from ADB failed (socket 31): Success
08-13 12:45:17.995  3802  3809 W m.android.emai: Receiving file descriptor from ADB failed (socket 31): Success
08-13 12:45:17.995  3760  3775 W viders.calenda: Receiving file descriptor from ADB failed (socket 32): Success
08-13 12:45:17.995  3828  3835 E gedprovisionin: Something went wrong getting fds from adb. Retry!: Success
08-13 12:45:17.995  3802  3809 E m.android.emai: Something went wrong getting fds from adb. Retry!: Success
08-13 12:45:17.995  3883  3890 E android.traceu: Something went wrong getting fds from adb. Retry!: Success
08-13 12:45:17.995  3760  3775 E viders.calenda: Something went wrong getting fds from adb. Retry!: Success
08-13 12:45:17.995  3601  3616 W android.smspus: Receiving file descriptor from ADB failed (socket 31): Success
08-13 12:45:17.995  3601  3616 E android.smspus: Something went wrong getting fds from adb. Retry!: Success
08-13 12:45:17.995  3684  3696 W ndroid.calenda: Receiving file descriptor from ADB failed (socket 31): Success
08-13 12:45:17.995  3739  3750 W ndroid.contact: Receiving file descriptor from ADB failed (socket 32): Success
08-13 12:45:17.995  3684  3696 E ndroid.calenda: Something went wrong getting fds from adb. Retry!: Success
08-13 12:45:17.995  3711  3719 W ndroid.keychai: Receiving file descriptor from ADB failed (socket 26): Success
08-13 12:45:17.995  3739  3750 E ndroid.contact: Something went wrong getting fds from adb. Retry!: Success
08-13 12:45:17.995  3711  3719 E ndroid.keychai: Something went wrong getting fds from adb. Retry!: Success
08-13 12:45:17.995  3594  3603 W droid.launcher: Receiving file descriptor from ADB failed (socket 26): Success
08-13 12:45:17.995  3673  3682 W d.process.acor: Receiving file descriptor from ADB failed (socket 11): Success
08-13 12:45:17.995  3594  3603 E droid.launcher: Something went wrong getting fds from adb. Retry!: Success
08-13 12:45:17.995  3673  3682 E d.process.acor: Something went wrong getting fds from adb. Retry!: Success
08-13 12:45:17.995  3863  3870 W ackageinstalle: Receiving file descriptor from ADB failed (socket 31): Success
08-13 12:45:17.995  3575  3585 W d.process.medi: Receiving file descriptor from ADB failed (socket 31): Success
08-13 12:45:17.995  3863  3870 E ackageinstalle: Something went wrong getting fds from adb. Retry!: Success
08-13 12:45:17.995  3575  3585 E d.process.medi: Something went wrong getting fds from adb. Retry!: Success
08-13 12:45:17.995  3218  3233 W ndroid.setting: Receiving file descriptor from ADB failed (socket 40): Success
08-13 12:45:17.995  3218  3233 E ndroid.setting: Something went wrong getting fds from adb. Retry!: Success
08-13 12:45:17.995  3554  3562 W com.android.se: Receiving file descriptor from ADB failed (socket 31): Success
08-13 12:45:17.995  3554  3562 E com.android.se: Something went wrong getting fds from adb. Retry!: Success
08-13 12:45:17.995  3302  3311 W id.ext.service: Receiving file descriptor from ADB failed (socket 11): Success
08-13 12:45:17.996  3302  3311 E id.ext.service: Something went wrong getting fds from adb. Retry!: Success
08-13 12:45:17.996  3146  3156 W ndroid.systemu: Receiving file descriptor from ADB failed (socket 31): Success
08-13 12:45:17.996  3146  3156 E ndroid.systemu: Something went wrong getting fds from adb. Retry!: Success
08-13 12:45:17.996  3845  3852 W timeinitialize: Receiving file descriptor from ADB failed (socket 31): Success
08-13 12:45:17.996  3127  3141 W putmethod.lati: Receiving file descriptor from ADB failed (socket 26): Success
08-13 12:45:17.996  3917  3924 W odroid.setting: Receiving file descriptor from ADB failed (socket 40): Success
08-13 12:45:17.996  3211  3221 W m.android.phon: Receiving file descriptor from ADB failed (socket 26): Success
08-13 12:45:17.996  3845  3852 E timeinitialize: Something went wrong getting fds from adb. Retry!: Success
08-13 12:45:17.996  3127  3141 E putmethod.lati: Something went wrong getting fds from adb. Retry!: Success
08-13 12:45:17.996  2995  3001 W system_server: Receiving file descriptor from ADB failed (socket 39): Success
08-13 12:45:17.996  3211  3221 E m.android.phon: Something went wrong getting fds from adb. Retry!: Success
08-13 12:45:17.996  3917  3924 E odroid.setting: Something went wrong getting fds from adb. Retry!: Success
08-13 12:45:17.996  2995  3001 E system_server: Something went wrong getting fds from adb. Retry!: Success
08-13 12:45:17.996  3161  3179 W com.droidlogic: Receiving file descriptor from ADB failed (socket 26): Success
08-13 12:45:17.996  3802  3809 W m.android.emai: Receiving file descriptor from ADB failed (socket 31): Connection reset by peer
08-13 12:45:17.996  3161  3179 E com.droidlogic: Something went wrong getting fds from adb. Retry!: Success
08-13 12:45:17.996  3802  3809 E m.android.emai: Something went wrong getting fds from adb. Retry!: Connection reset by peer
08-13 12:45:17.996  3901  3908 W BluetoothRemot: Receiving file descriptor from ADB failed (socket 11): Success
08-13 12:45:17.996  3883  3890 W android.traceu: Receiving file descriptor from ADB failed (socket 32): Connection reset by peer
08-13 12:45:17.996  3650  3658 W id.printspoole: Receiving file descriptor from ADB failed (socket 32): Success
08-13 12:45:17.996  3601  3616 W android.smspus: Receiving file descriptor from ADB failed (socket 31): Connection reset by peer
08-13 12:45:17.996  3883  3890 E android.traceu: Something went wrong getting fds from adb. Retry!: Connection reset by peer
08-13 12:45:17.996  3901  3908 E BluetoothRemot: Something went wrong getting fds from adb. Retry!: Success
08-13 12:45:17.996  3601  3616 E android.smspus: Something went wrong getting fds from adb. Retry!: Connection reset by peer
08-13 12:45:17.996  3650  3658 E id.printspoole: Something went wrong getting fds from adb. Retry!: Success
08-13 12:45:17.996  3828  3835 W gedprovisionin: Receiving file descriptor from ADB failed (socket 31): Connection reset by peer
08-13 12:45:17.996  3828  3835 E gedprovisionin: Something went wrong getting fds from adb. Retry!: Connection reset by peer
08-13 12:45:17.997  3518  3526 W droid.deskcloc: Receiving file descriptor from ADB failed (socket 31): Success
08-13 12:45:17.997  3518  3526 E droid.deskcloc: Something went wrong getting fds from adb. Retry!: Success
08-13 12:45:17.997  4004  4011 W droid.bluetoot: Receiving file descriptor from ADB failed (socket 31): Success
08-13 12:45:17.997  4004  4011 E droid.bluetoot: Something went wrong getting fds from adb. Retry!: Success
08-13 12:45:17.998  3760  3775 W viders.calenda: Receiving file descriptor from ADB failed (socket 32): Connection reset by peer
08-13 12:45:17.998  3760  3775 E viders.calenda: Something went wrong getting fds from adb. Retry!: Connection reset by peer
08-13 12:45:18.032  4056  4057 I adbd    : initializing functionfs
08-13 12:45:18.032  4056  4057 I adbd    : opening control endpoint /dev/usb-ffs/adb/ep0
08-13 12:45:18.033  4056  4057 I adbd    : functionfs successfully initialized
08-13 12:45:18.033  4056  4057 I adbd    : registering usb transport
08-13 12:45:18.063  2995  3017 W Looper  : Slow dispatch took 103ms android.fg h=com.android.server.usb.UsbDeviceManager$UsbHandlerLegacy c=null m=2
08-13 12:45:19.153  2809  2809 I Binder:2809_5: type=1400 audit(0.0:134): avc: denied { read } for name="gralloc.odroidn2.so" dev="mmcblk0p12" ino=703 scontext=u:r:surfaceflinger:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=1
08-13 12:45:19.153  2809  2809 I Binder:2809_5: type=1400 audit(0.0:135): avc: denied { open } for path="/vendor/lib/hw/gralloc.odroidn2.so" dev="mmcblk0p12" ino=703 scontext=u:r:surfaceflinger:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=1
08-13 12:45:19.153  2809  2809 I Binder:2809_5: type=1400 audit(0.0:136): avc: denied { getattr } for path="/vendor/lib/hw/gralloc.odroidn2.so" dev="mmcblk0p12" ino=703 scontext=u:r:surfaceflinger:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=1
08-13 12:45:19.153  2995  2995 I android.display: type=1400 audit(0.0:137): avc: denied { read } for name="gralloc.odroidn2.so" dev="mmcblk0p12" ino=703 scontext=u:r:system_server:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=1
08-13 12:45:19.153  2995  2995 I android.display: type=1400 audit(0.0:138): avc: denied { open } for path="/vendor/lib/hw/gralloc.odroidn2.so" dev="mmcblk0p12" ino=703 scontext=u:r:system_server:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=1
08-13 12:45:19.153  2995  2995 I android.display: type=1400 audit(0.0:139): avc: denied { getattr } for path="/vendor/lib/hw/gralloc.odroidn2.so" dev="mmcblk0p12" ino=703 scontext=u:r:system_server:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=1
08-13 12:45:19.153  2995  2995 I android.display: type=1400 audit(0.0:140): avc: denied { execute } for path="/vendor/lib/hw/gralloc.odroidn2.so" dev="mmcblk0p12" ino=703 scontext=u:r:system_server:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=1
08-13 12:45:19.154  2796  2933 I [Gralloc]: framebuffer hal alread move to hwcomposer
08-13 12:45:20.434  2995  3017 D UsbDeviceManager: entering USB accessory mode: UsbAccessory[mManufacturer=DJI, mModel=T600, mDescription=DJI Inspire 1, mVersion=v0.0.0.0, mUri=www.dji.com, mSerial=000000000000000]

User avatar
codewalker
Posts: 691
Joined: Mon Feb 25, 2013 11:03 am
languages_spoken: english
ODROIDs: all
Has thanked: 28 times
Been thanked: 20 times
Contact:

Re: Looking for a Odroid XU3 or XU3-Lite

Unread post by codewalker » Wed Aug 14, 2019 9:23 am

result of lsusb for XU3 before connecting accessory.

Code: Select all

[/media/codewalker/projects/android-open-accessory-bridge]$ lsusb
Bus 002 Device 002: ID 8087:8000 Intel Corp. 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 05e3:0620 Genesys Logic, Inc. 
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 107: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x UART Bridge / myAVR mySmartUSB light
Bus 003 Device 118: ID 18d1:4e42 Google Inc. Nexus 7 (debug)
Bus 003 Device 117: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 003 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 003 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[/media/codewalker/projects/android-open-accessory-bridge]$ 
result of lsusb for XU3 after connecting accessory.

Code: Select all

[/media/codewalker/projects/android-open-accessory-bridge]$ lsusb
Bus 002 Device 002: ID 8087:8000 Intel Corp. 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 05e3:0620 Genesys Logic, Inc. 
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 107: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x UART Bridge / myAVR mySmartUSB light
Bus 003 Device 116: ID 18d1:0004 Google Inc. 
Bus 003 Device 114: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 003 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 003 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
If you want n2 to act like xu3, Edit /vendor/init/hw/init.odroid.usb.rc

Code: Select all

on property:sys.usb.config=adb && property:sys.usb.configfs=1
    write /config/usb_gadget/g1/idProduct 0x4e40

on property:sys.usb.config=accessory && property:sys.usb.configfs=1
    write /config/usb_gadget/g1/idProduct 0x0003

on property:sys.usb.config=accessory,adb && property:sys.usb.configfs=1
    write /config/usb_gadget/g1/idProduct 0x0004

Code: Select all

[/media/codewalker/projects/android-open-accessory-bridge]$ 
[/media/codewalker/projects/android-open-accessory-bridge]$ lsusb
Bus 002 Device 002: ID 8087:8000 Intel Corp. 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 05e3:0620 Genesys Logic, Inc. 
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 107: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x UART Bridge / myAVR mySmartUSB light
Bus 003 Device 066: ID 18d1:4e40 Google Inc. Nexus 7 (fastboot)
Bus 003 Device 061: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 003 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 003 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Code: Select all

[/media/codewalker/projects/android-open-accessory-bridge]$ lsusb
Bus 002 Device 002: ID 8087:8000 Intel Corp. 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 05e3:0620 Genesys Logic, Inc. 
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 107: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x UART Bridge / myAVR mySmartUSB light
Bus 003 Device 069: ID 18d1:0004 Google Inc. 
Bus 003 Device 061: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 003 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 003 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[/media/codewalker/projects/android-open-accessory-bridge]$ 

Post Reply

Return to “General Topics”

Who is online

Users browsing this forum: No registered users and 1 guest