Android: AdbCommandRejectedException getting properties for device

  • by

Problem

From Android Studio, the connection to the device for debugging was not getting established. The ADB logs gave the repeated error,

PropertyFetcher: AdbCommandRejectedException getting properties for device ????????????: insufficient permissions for device

Solution

  1. As described in the documentation, Using Hardware Devices, a file /etc/udev/rules.d/51-android.rules was created.
  2. Using the lsusb -v command, the vendor id (idVendor) and product id (idProduct) were found.
  3. For Micromax Canvas Unite 2 (A106), the following line was added to the file, /etc/udev/rules.d/51-android.rules,
    SUBSYSTEM=="usb", ATTR{idVendor}=="0c45", ATTR{idProduct}=="64ad", MODE="0666", GROUP="plugdev"
  4. The device was disconnected from the PC. On the device, choosing Settings -> Developer option, gives a list of options. Among these, Revoke USB debugging authorization was clicked. When the device is reconnected to PC using the USB, it shows the dialog, Allow USB debugging? Click OK.This solved the problem and the debug connection with the device was established.

0 0 votes
Article Rating
Subscribe
Notify of
0 Comments
Inline Feedbacks
View all comments

You may like these, also

  • POSIX message queues in Linux 1.0 POSIX Message queues POSIX interprocess comunication (IPC) was introduced in the POSIX.1b standard (IEEE Std 1003.1b-1993) for real time…
  • POSIX Shared Memory in Linux 1.0 Shared Memory Shared memory is the fastest method of interprocess communication (IPC) under Linux and other Unix-like systems. The…
  • POSIX Semaphores in Linux 1.0 Semaphores Semaphores are used for process and thread synchronization. Semaphores are clubbed with message queues and shared memory under…
  • fork and exec system calls in Linux 1.0 fork and exec system calls Suppose we wish to write a "shell program" which would execute another program. Now,…
  • Connecting two computers with Ethernet LAN cable Quite often, we wish to connect two computers back to back using an Ethernet LAN cable. It may be because…
  • D-Bus Tutorial 1.0 D-Bus D-Bus is a mechanism for interprocess communication under Linux and other Unix-like systems. D-Bus has a layered architecture.…
  • Socket programming using the select system call 1.0 Client-Server Paradigm The Client-Server paradigm divides the software architecture of a system in two parts, the server and its…
  • System V message queues in Linux 1.0 Message queues Message queues are one of the interprocess communication mechanisms available under Linux. Message queues, shared memory and…
  • POSIX Threads Synchronization in C 1.0 POSIX Threads Synchronization POSIX Threads provide multiple flows of execution within a process. The threads have their own stacks…
  • System V Shared Memory in Linux 1.0 Shared Memory Shared memory is one of the three interprocess communication (IPC) mechanisms available under Linux and other Unix-like…