Devices won't be recognized on Ubuntu

395 views
Skip to first unread message

Junichi Chiba

unread,
Jul 14, 2015, 1:00:03 AM7/14/15
to ope...@googlegroups.com
Hi,

I'm a test engineer at an ebook company.
I have ran through two trial installs, one on Mac Yosemite, the other on Ubuntu 15.04 desktop.
While Mac install fully enjoys Plug-and-Play with all the Android devices around my desk,
including FJL22*, Nexus5*, ISW-11F *, P04D *, Galaxy S2, Xperia SO-05D, SH09D, 
Ubuntu somehow won't recognize some devices (marked with asterisk).

Arrows FJL22, for example, is recognized on Mac as
INF/provider 36021 [*] Found device "91d6d990" (offline)
INF/reaper 36020 [reaper001] Device "91d6d990" is present
INF/provider 36021 [*] Registered device "91d6d990"
INF/provider 36021 [*] Device "91d6d990" is now "device" (was "offline")
INF/device:support:push 36240 [91d6d990] Sending output to "tcp://127.0.0.1:7116"
INF/device 36240 [91d6d990] Preparing device
INF/device:support:sub 36240 [91d6d990] Receiving input from "tcp://127.0.0.1:7114"
INF/device:support:sub 36240 [91d6d990] Subscribing to permanent channel "*ALL"
INF/device:support:properties 36240 [91d6d990] Loading properties

while it's not on Ubuntu.
INF/reaper 6306 [reaper001] Device "91d6d990" is present
INF/provider 6308 [*] Registered device "91d6d990"
INF/provider 6308 [*] Providing all 1 of 2 device(s); ignoring "91d6d990"
INF/reaper 6306 [reaper001] Reaping device "91d6d990" due to heartbeat timeout
WRN/util:datautil 6312 [*] Device database does not have a match for device "91d6d990" (model "undefined"/"undefined")

I read and checked through the troubleshooting section in Readme.
- PTP and MTP -- I tried both. It's seems it does not matter for 91d6d990.
- adb version 1.0.31 is running for sure (1.0.32 on my Mac)
- adb authentication -- Looks like ok. It seems already privileged and a dialog doesn't appear on the devices.
- adb whitelist -- I'm not sure what this means exactly, but I guess a device fine on Mac install should pass it on another install.
- USB cable and power -- should be ok. STF notices a new device is connected.

I doubt if the correct device list hasn't been fetched somewhere around stf-device-db,
or adb is not able to know correct model names for some devices in the way STF recognizes.
Do you know what I should check?

Many thanks for your advice.

Gunther

unread,
Jul 14, 2015, 7:53:52 AM7/14/15
to Junichi Chiba, ope...@googlegroups.com
Hi!

Basically the reason might be that Ubuntu it includes libmtp, 
which creates permission problems with the devices.

The easy way to fix it would be to run adb as root:
sudo adb

The "proper way" would be to set up the permissions as described here (in the Ubuntu Linux section):

But you might want to deploy using CoreOS as well:

So try with this, and if it still fails just tell us;)

Regards,
Gunther Brunner

--
You received this message because you are subscribed to the Google Groups "OpenSTF" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openstf+u...@googlegroups.com.
To post to this group, send email to ope...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openstf/a6980a9b-5ec0-4437-9802-a4c067c2256f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Junichi Chiba

unread,
Jul 14, 2015, 11:17:04 PM7/14/15
to ope...@googlegroups.com, gun...@gmail.com, junichi....@gmail.com
Hi,

Thanks, the easy way fixed the problem.
I tried sudo adb start-server and sudo stf local (since it fails without sudo now).
The devices are recognized on Ubuntu correctly.

I will try the other proper ways shortly.
I noticed the deployment document had an update. It's very helpful.
Thank you very much!
Reply all
Reply to author
Forward
0 new messages