Discussion:
Android connection
Lev Lafayette
2015-09-30 11:58:05 UTC
Permalink
Hi LUVers,

I'm trying do a wee bit of Android work (hey, it has a Linux kernel) and
have an Aldi Bauhn AT101-014 [1] and have the latest SDK installed and
updated (./android update sdk --no-ui).

I have the device connected via USB with developer mode, USB debugging
mode on, and a MTP connection [2] and have mtpfs installed. I am using
Debian Mint as the development system.

I understand that I have to modify /etc/udev/rules.d/51-android.rules and
possibly ~/.android/adb_usb.ini to include the vendor ID. This can be
determined from running lsusb as follows:

***@owl ~/src/android-sdk-linux/tools $ lsusb
Bus 004 Device 079: ID 2207:0011
(snip. The above is the relevant device; informative isn't it?)

I have created the file /etc/udev/rules.d/51-android.rules with the
following:

SUBSYSTEM=="usb", ATTR{idVendor}=="2207", MODE="0666", GROUP="plugdev"

I have created the file ~/.android/adb_usb.ini with the following:

0x<2207>

All of which I believe is in accord to what should be done. However when I
run

owl tools # adb start-server
owl tools # adb devices
List of devices attached

owl tools #

I would expecting some connectivity at this point.

[1] http://www.bauhn.com.au/_literature_140385/AT101-014_-_Instruction_Manual
[2] http://developer.android.com/tools/device.html

Thanks in advance,
--
Lev Lafayette, BA (Hons), GradCertTerAdEd (Murdoch), GradCertPM, MBA (Tech
Mngmnt) (Chifley)
mobile: 0432 255 208
RFC 1855 Netiquette Guidelines
http://www.ietf.org/rfc/rfc1855.txt
Lev Lafayette
2015-09-30 12:45:27 UTC
Permalink
Post by Lev Lafayette
0x<2207>
I mean of course

0x2207

.. just in case there's any confusion. :)
--
Lev Lafayette, BA (Hons), GradCertTerAdEd (Murdoch), GradCertPM, MBA (Tech
Mngmnt) (Chifley)
mobile: 0432 255 208
RFC 1855 Netiquette Guidelines
http://www.ietf.org/rfc/rfc1855.txt
Andrew McGlashan
2015-09-30 20:39:55 UTC
Permalink
Post by Lev Lafayette
Post by Lev Lafayette
0x<2207>
I mean of course
0x2207
.. just in case there's any confusion. :)
This might help you:

https://developer.android.com/tools/device.html#setting-up

Cheers
A.
Wayne Moulden
2015-09-30 21:21:39 UTC
Permalink
Post by Lev Lafayette
Post by Lev Lafayette
0x<2207>
I mean of course
0x2207
.. just in case there's any confusion. :)
--
Lev Lafayette, BA (Hons), GradCertTerAdEd (Murdoch), GradCertPM, MBA (Tech
Mngmnt) (Chifley)
mobile: 0432 255 208
RFC 1855 Netiquette Guidelines
http://www.ietf.org/rfc/rfc1855.txt
_______________________________________________
luv-main mailing list
http://lists.luv.asn.au/listinfo/luv-main
It _should_ be a permissions problem, I had the same issue sometime ago and
I had to add my user to the plugdev group then restart adb

Wayne
Lev Lafayette
2015-10-04 12:10:38 UTC
Permalink
Post by Andrew McGlashan
https://developer.android.com/tools/device.html#setting-up
Yeah, already followed that and linked it to on the original post.
Post by Andrew McGlashan
It _should_ be a permissions problem, I had the same issue sometime ago
and I had to add my user to the plugdev group then restart adb
Good catch, but it wasn't that either. I already had granted appropriate
permissions.

Turned out it that my venerable install of Debian Mint was just not
playing nice with the Android SDK. Without going into the gruesome details
CentOS (even an old version) did it straight away.

Thanks Andrew and Wayne for your advice.

All the best,
--
Lev Lafayette, BA (Hons), GradCertTerAdEd (Murdoch), GradCertPM, MBA (Tech
Mngmnt) (Chifley)
mobile: 0432 255 208
RFC 1855 Netiquette Guidelines
http://www.ietf.org/rfc/rfc1855.txt
Loading...