Mobileread
PRS-T1 getting adb working
#1  mrspaceman 11-07-2011, 01:39 PM
I am trying to get 'adb devices' to work reliably

I update my
Code
~/.android/adb_usb.ini
to look like this:

Code
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x054c
I have updated my
Code
/etc/udev/rules.d/51-android.rules
to look like this:

Code
SUBSYSTEMS=="usb", ATTRS{idVendor}=="2080", MODE="0666", OWNER="andy"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="054C", MODE="0666", OWNER="andy"
I have restarted udev.
I have rebooted my PC and my prs-t1, still adb devices shows nothing.

This was working last night, and I had it working on my work PC all day, so does anyone know what has gone wrong?
Reply 

#2  porkupan 11-07-2011, 03:57 PM
For me the only thing that lets ADB be detected on the PC (be it Windows or Linux) is actually toggling the "Enable ADB over USB" checkbox while connected to the USB. If you reboot the reader while connected, it gets detected as well.

Something about the sequence of ADB and other USB processes in the reader coming up. I cannot explain it.

What works for me every time is clicking on the checkbox to turn it off, then immediately turning it back on.
Reply 

#3  EowynCarter 11-07-2011, 04:03 PM
Quote
What works for me every time is clicking on the checkbox to turn it off, then immediately turning it back on.
Yup, i have to do that too.
Reply 

#4  mrspaceman 11-08-2011, 01:43 AM
okay, I'll keep that in mind, thanks.
Reply 

#5  uboot 11-12-2011, 01:03 PM
I don't get it to work It's Windows 7 x64 and Android SDK for Android 2.2

enable-adb is installed on my PRS-T1

I edited the driver inf file according to http://translate.google.com/translate?hl=en&rurl=translate.google.com&sl=ru&u= http://www.the-ebook.org/forum/viewtopic.php?t=21458 for both - the x86 and the x64 section - and the driver is now running properly (shows up in device manager as Android Composide ADB interface).

Now, when toggling USB debugging in android settings, the device appears/disappears as expected in windows device manager and the small robot shows up on the notification bar on the reader.

So, everything should be fine.

But "adb kill-server" followed by "adb devices" still does not show any devices :*(
Reply 

#6  porkupan 11-13-2011, 09:02 AM
Did you edit %USERPROFILE%\.android\adb_usb.ini ?
Reply 

#7  uboot 11-13-2011, 05:11 PM
yes, I did... but guess what???? I just re-checked the file and did a minor change which resolved the issue:

0x054c -> 0x054C

Reply 

#8  hitoriblog 11-24-2011, 06:18 PM
enable-adb-jp, disable-adb-jp please!
Reply 

#9  dare 01-28-2012, 10:50 AM
Quote uboot
I don't get it to work It's Windows 7 x64 and Android SDK for Android 2.2
Me too... I just don't get the driver installed as it should.

I ever only get a generic USB Mass Storage Device shown in the Device Manager (DM). On trying to install the USB driver for that one, Windows tells me that this is not possible.

If I try to install the driver beforehand via "legacy hardware" in the DM, I have a branch "Android Phone" in the DM after de- and reenabling USB debugging, but its subbranch is "unknown device" - while still having also the entries under Mass Storage Device and Portable Devices.

Also USBDeview shows me nothing else than a "Sony PRS-T1 Setting Device" with the known VID_054C&PID_05C2 and the serial number, but nothing of a VID_054C&PID_05C2&MI_01.

I don't really understand how Windows handles this stuff, but shouldn't toggling the USB debug mode result in that different mode/MI? What does the DM show for you guys when you have an ADB connection?

Any help appreciated!
Reply 

#10  dare 01-28-2012, 12:10 PM
There is, however, alway hope
I just took an ADB over WiFi widget from the market, put it on the launcher and configured it for lazyness to port 5555, enabled incoming connections as pointed out by sonic74 earlier, and simply connected from my PC. Hosianna!
Reply 

  Next »  Last »  (1/7)
Today's Posts | Search this Thread | Login | Register