[SOLVED] HTC Sensation isn't recognized in Linux for Debugging

ZiGi55

Member
Aug 9, 2011
43
12
0
www.androidshed.com
YES, i have watched the n00bs video and my mum wasn't very happy about the call.

I've posted this question in stackoverflow too.

ANYWAY, I'm using the Eclipse IDE.

I can only see question marks in the Android Device Chooser; where I'd usually find numbers. it's like I didn't add udev rules for the device

It's a Sensation 4g from T-Mobile to be exact. I tried with an HTC Inspire and it worked fine, logcat also worked fine but not with this newer Handset.

The sensation works fine on windows but i prefer developing on linux; Ubuntu 11.04 to be more specific

And also, I can use the sensation as a disk drive on Ubuntu but the problem remains. I usually connect the handset in "Charge Only" mode; this seems to allow debugging just fine on the HTC Inspire.

this is my terminal output from $lsusb
Code:
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 09da:054f A4 Tech Co., Ltd 
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
[B]Bus 001 Device 004: ID 0bb4:0c86 High Tech Computer Corp.[/B]   //THIS IS THE ONE!!!
Bus 001 Device 002: ID 0c45:62c0 Microdia Sonix USB 2.0 Camera
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
and Here's the contents of my "rules" file: $sudo gedit /etc/udev/rules.d/51-android.rules

Code:
SUBSYSTEM=="usb_device", SYSFS{idVendor}=="0bb4", MODE="0666"
I don't understand why it works fine with the older HTC handset but not with this one.

AND YES, I REMEMBERED TO TURN DEBUGGING ON THE PHONE; it works in windows remember?

sadly, I wasn't allowed to post his in the developers forum because i'm a n00b and I don't deserve it.

SUMMARY:
I want to debug my HTC Sensation in Ubuntu!
 
Last edited:

M!W

Member
Apr 17, 2010
9
1
0
Did you also run this command?
Code:
chmod a+r /etc/udev/rules.d/51-android.rules
Sometimes you need to kill adb first.
You can do this by invoking this command:
Code:
sudo adb kill-server
Hope that helps ;-)
 
Last edited:

ZiGi55

Member
Aug 9, 2011
43
12
0
www.androidshed.com
Hi M!W

Thanks for the answer.

I remember doing something similar before without success. I tried again using your commands and sadly nothing changed :(

It's never simple with me XD

Sent from my HTC Sensation Z710a using XDA Premium App
 

smakked

Senior Member
Nov 26, 2010
150
20
0
Gold Coast
Looks like you are missing somehting from your udev rules
mine looks like:
Code:
#HTC Sensation
SUBSYSTEM=="usb", SYSFS{idVendor}=="[0bb4]", MODE="0666"
SUBSYSTEM=="usb",ATTR{idVendor}=="[0bb4]",ATTR{idProduct}=="[0c86]",SYMLINK+="android_adb"
SUBSYSTEM=="usb",ATTR{idVendor}=="[0bb4]",ATTR{idProduct}=="[0c86]",SYMLINK+="android_fastboot"
 

ZiGi55

Member
Aug 9, 2011
43
12
0
www.androidshed.com
[SOLVED]

Looks like you are missing somehting from your udev rules
mine looks like:
Code:
#HTC Sensation
SUBSYSTEM=="usb", SYSFS{idVendor}=="[0bb4]", MODE="0666"
SUBSYSTEM=="usb",ATTR{idVendor}=="[0bb4]",ATTR{idProduct}=="[0c86]",SYMLINK+="android_adb"
SUBSYSTEM=="usb",ATTR{idVendor}=="[0bb4]",ATTR{idProduct}=="[0c86]",SYMLINK+="android_fastboot"
WORKS LIKE A CHARM! i just removed the "[]" brackets, maybe it would've worked anyway :D

THANKS A HEAP! I've clicked thanks
 

jr3074

Member
Dec 31, 2013
12
0
0
www.apkcoy.com
SUBSYSTEM=="usb", SYSFS{idVendor}=="[0bb4]", MODE="0666"
SUBSYSTEM=="usb",ATTR{idVendor}=="[0bb4]",ATTR{idProduct}=="[0c86]",SYMLINK+="android_adb"
SUBSYSTEM=="usb",ATTR{idVendor}=="[0bb4]",ATTR{idProduct}=="[0c86]",SYMLINK+="android_fastboot"
Finally i can break this problem.