Date: Tue, 20 Nov 2018 10:32:15 +0100 From: Matthias Apitz <guru@unixarea.de> To: freebsd-usb@freebsd.org Subject: Re: Android Debug Bridge (adb) on FreeBSD && smartphone BQ E4.5 Message-ID: <20181120093215.GA2789@c720-r314251> In-Reply-To: <560aee91-f5b9-94bd-60f3-86f10aa6aab5@selasky.org> References: <20181120054609.GA2728@c720-r314251> <1e7ba4e7-a8ef-b51c-8a2b-fdabf4d37a32@selasky.org> <20181120080620.GA22119@sh4-5.1blu.de> <560aee91-f5b9-94bd-60f3-86f10aa6aab5@selasky.org>
next in thread | previous in thread | raw e-mail | index | archive | help
El día martes, noviembre 20, 2018 a las 09:09:24a. m. +0100, Hans Petter Selasky escribió: > > Of course. And it worked with the same cable on an Ubuntu 18.10 laptop > > out of the box. On start on the device popped up a message box and asking > > if I want to allow this connection. I ack'ed and had the shell prompt in > > the xterm where I started 'adb shell'. > > > > Did you run adb as root? > Yes. > Maybe you need to add some VID/PID via the environment. Works with my phone. > > What does "adb devices -l" output? Yesterday and today morning it produced an empty list. Now it works. In the root xterm, where I start the 'adb start-server' it says now n addition to: ... adb I 2592 100164 usb_libusb.cpp:399] check_device(): Probing usb device 2a47:0c02 adb I 2592 100164 usb_libusb.cpp:418] check_device(): Device bus: 0, address: 4 adb I 2592 100164 usb_libusb.cpp:259] check_usb_interface(): Interface have not 2 endpoints, ignoring adb I 2592 100164 usb_libusb.cpp:280] check_usb_interface(): Forced Android interface protocol v.1 adb I 2592 100164 usb_libusb.cpp:280] check_usb_interface(): Forced Android interface protocol v.1 adb I 2592 100164 usb_libusb.cpp:288] check_usb_interface(): Device: 2a47:0c02 iclass: ff, isclass: 42, iproto: 1 ep: 83/2-> adb I 2592 100164 usb_libusb.cpp:298] matches adb I 2592 100164 usb_libusb.cpp:314] check_usb_interfaces(): Interface 1 of 2a47:0c02 matches Android device adb I 2592 100164 usb_libusb.cpp:473] check_device(): Device matches Android interface adb I 2592 100164 usb_libusb.cpp:327] register_device(): Registering 0x7fffffffda20 [JU000143] as USB transport adb I 2592 100164 transport.cpp:1012] transport: 0x802428000 init'ing for usb_handle 0x8024250c0 (sn='JU000143') adb I 2592 100164 transport_usb.cpp:85] transport: usb adb I 2592 100164 transport.cpp:591] transport: JU000143 registered adb I 2592 100164 usb_libusb.cpp:614] usb_init(): finished adb I 2592 100164 transport_local.cpp:315] transport: local client init adb I 2592 100164 adb_auth_host.cpp:431] adb_auth_init adb I 2592 100164 adb_auth_host.cpp:292] home '/root' adb I 2592 100164 adb_auth_host.cpp:322] user key '/root/.android/adbkey' adb I 2592 100164 adb_auth_host.cpp:265] read_key '/root/.android/adbkey' adb I 2592 100164 fdevent.cpp:152] fdevent_install (fdevent 14 A) adb I 2592 100164 fdevent.cpp:198] fdevent_set: (fdevent 14 AR), events = 1 * daemon started successfully * and in the unpriv xterm it says: $ adb devices -l List of devices attached JU000143 device ugen0.4 product:krillin model:Aquaris_E4_5_Ubuntu_Edition device:krillin $ adb shell phablet@ubuntu-phablet:~$ I don't know why it works now, but not yesterday and today morning with the same installation, same device. Only the cable is now different. I will check at home with the cable I used this morning. matthias -- Matthias Apitz, ✉ guru@unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub October, 7 -- The GDR was different: Peace instead of Bundeswehr and wars, Druschba instead of Nazis, to live instead of to survive.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20181120093215.GA2789>