Two differences: it's now SUBSYSTEM (no plural), and the group has changed from androiddev to plugdev (the former does not exist on recent systems, the latter does and usually is assigned at least to the first user).Īdditionally, you might need to add the vendorID to your ~/.android/adb_usb.ini (one ID per line, in hex notation): # ANDROID 3RD PARTY USB VENDOR ID LISTĪ few comments from a newer Linux distribution. Following example line shows how it looks for the Wileyfox Swift:¹ SUBSYSTEMS="usb", ATTRS="2282", MODE="0666", GROUP="plugdev", SYMLINK+="android%n" Having those details, we need a root shell on our Linux machine to edit (or create, if it doesn't yet exist) the /etc/udev/rules.d/les file. These specify the vendor (2970) and the device itself (2282). We now need the numbers at the end of the above line: 2970:2282. For the Wileyfox Swift this is a "nameless device": Bus 004 Device 003: ID 2970:2282 Then connect the device and run the command again.
For that, with the Android device NOT connected, grab a shell and run the command lsusb. Identify the deviceįirst we need to know how the device identifies on the USB bus. Go back to the main page of the Settings menu, and close to the bottom you should see the "Development" (or "Developers") settings now.
If you don't have that entry in your settings menu, go to Settings › About, scroll to the "Build number", and hammer it like a monkey until your device congratulates you having become a developer.
0 kommentar(er)
