2

I have searched for a long time for this, I have tried all the tricks I could find...

I have been debugging on the same device for a few months, deploying the app on other exact same devices flawlessly. But since last week, I can no longer connect to it. Connecting the device via USB, I can hear the computer's sound warn about the connected device, and I can see in Chrome that it is recognized

enter image description here

However, adb won't detect it.

enter image description here

Unfortunately, I have not access to root on the devices, so I'm not sure how to connect via TCP/IP.

What could possibly be the problem?

Note: I am working with Ubuntu.

Note 2: The devices run Android 4.4.2, as reported by the device, despite specs from various vendors say otherwise.

Update

I have verified my UDEV rules, so

$ lsusb
...
Bus 003 Device 123: ID 1f3a:1002 Onda (unverified) 
...

is the only device added when I connect the tablet via USB. And in my /etc/udev/rules.d/99-android.rules file (which I have already set over a year ago), I have the correct line

SUBSYSTEM=="usb", ATTRS{idVendor}=="1f3a", MODE="0666"

The Developer Options are

  • Take bug report
  • Desktop backup password
  • Stay awake
  • HDCP checking
  • Process Stats

Debugging

  • USB debugging (= ON)
  • Power menu bug reports
  • Allow mock locations (= ON)
  • Select debug app
  • (disabled) Wait for debugger
  • Verify apps over USB
  • Wireless display certification

Input

  • Show touches
  • Pointer location

Drawing

  • Show surface updates
  • Show layout bounds
  • Force RTL layout direction
  • Window animation scale
  • Transition animation scale
  • Animator duraction scale
  • Simluate secondary displays

Hardware acceleration rendering

  • Force GPU rendering
  • Show GPU new updates
  • Show hardware layers updates
  • Debug GPU overdraw
  • Debug non-rectangular clip operations
  • Force 4x MSAA
  • Disable HW overlays

Monitoring

  • Strict mode enabled
  • Show CPU usage
  • Profile GPU rendering
  • Enable GPU traces

Apps

  • Don't keep activites (= ON)
  • Background process limit (= standard)
  • Show all ANRs

(All options with values or set are indicated in the above list. If nothing is mentioned, then no value is set.)

Improve this question
15
  • 1
    Try revoking the rights for all devices from the phone and reconnect it again.
    – Prerak Sola
    Commented Nov 21, 2016 at 15:15
  • Have you set your device for debugging? Also, be aware that your device asks you for fingerprint acknowledge. If you do not grant this permission, adb wont work.
    – Tiago Dávila
    Commented Nov 21, 2016 at 15:15
  • @PrerakSola how do I do that?
    – Yanick Rochon
    Commented Nov 21, 2016 at 15:17
  • @TiagoDávila of course the device is on debug mode; I did deploy on this exact device many times already. And I'm not sure what you mean by "fingerprint"; the device never asked me anything, and just worked.
    – Yanick Rochon
    Commented Nov 21, 2016 at 15:18
  • 1
    @YanickRochon Just to confirm that you didn't have Chrome remote debugging on when trying stuff with adb. Also what is your 'adb version'.
    – Morrison Chang
    Commented Nov 21, 2016 at 19:33

3 Answers 3

Reset to default
2

Since you've got Chrome Remote debugging working, just make sure that Chrome debugging isn't running when doing things with adb on the command line.

I believe that Chrome has its own version of adb-server so that would conflict with the one used by Android Studio.

Improve this answer
1
  • Nailed it! Thanks!
    – Yanick Rochon
    Commented Nov 21, 2016 at 20:14
0

You need to enable the Developer Mode first in the Mobile and then connect the device to your linux machine. It require no drivers, happy debugging.

Improve this answer
1
  • Please, read the question carefully. I said that I have used this same device for debugging before... several times... then it stopped being listed last week. I then replied to comments by listing all the Developer Mode menu... entirely!
    – Yanick Rochon
    Commented Nov 21, 2016 at 16:54
0

yalok commented on 17 Apr @ gituhub threat https://github.com/anbox/anbox/issues/130

Managed to run the session-manager after:

sudo ln -s /snap/bin/anbox /usr/bin/anbox

adb device is now there:

$ adb devices
List of devices attached
emulator-6663   device
Improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.