(Development) Eclipse cannot send packages to my Pulse (2.1)

[Guest]

Greetings fellow Pulse users.

I'm getting started with Android development using a T-Mobile Pulse U8220 as my development target. I'm using Eclipse with the SDT plugin, everything is set up correctly and several VMs have been created, each working fine.

My problem however is that when asking Eclipse to send new builds to the Pulse and not the VMs, it fails.

Here's my setup:

T-Mobile Pulse (Paul's latest rooted 2.1, USB debugging enabled)

Ubuntu 10.04

Eclipse (from repo)

SDK r06 in /home/steve/android-sdk-linux_86/

I am starting adb with, 'sudo /home/steve/android-sdk-linux_86/tools/adb start-server'.

I can interact with the Pulse a little using 'adb shell', but when running 'adb devices' I get this:

/opt/android-sdk-linux_86/tools/adb devices

List of devices attached

???????????? device

Additionally, 'adb logcat' doesn't seem to report anything.

Running those commands with sudo doesn't seem to change anything either. Many killings of the adb service and even restarting the machine didn't solve the problem.

I believe this is what's preventing Eclipse from being able to deploy packages to the Pulse, it doesn't have permissions to access the device or something?? I seem to remember the device being picked up just fine with adb when it was running an earlier Android build. Did something change with 2.1?

I've also tested with Fedora 13, same problem. Windows XP works well but I don't have it running on anything of mine.

Any help would be muchly appreciated. I'm probably missing something quite fundemental :(

Edited May 29, 2010 by Guest

[Guest McSpoon]

I've seen that bug before but it went away after we recompiled the kernel. But that was for Android 1.5.

See this thread, there are some ADB commands you can try:

adb shell

echo 1 > /sys/kernel/logger/log_main/enable // ** '1' is enable log_main,

echo 2 >/sys/kernel/logger/log_main/priority // ** '2' is the log level, you can get the level number from the android source code.

If that doesn't help then we may have to wait for Huawei to release the Pulse Android 2.1 kernel source code so we can recompile it. Last time we didn't even have to make any modifications, it just worked after recompiling the kernel. :( It's bizarre and annoying.

[Guest]

there are some ADB commands you can try:

adb shell

echo 1 > /sys/kernel/logger/log_main/enable // ** '1' is enable log_main,

echo 2 >/sys/kernel/logger/log_main/priority // ** '2' is the log level, you can get the level number from the android source code.

These lines enabled support for logcat using 'adb logcat' which is some progress, thanks :(

Still no luck in uploading packages to the device using Eclipse.

[Guest McSpoon]

Hopefully when Huawei release the new kernel source code we'll be able to figure out how to make it report the device ID (or whatever) instead of '????????'. But at the moment the Android 2.1 ROMs only have the stock kernel.

I presume that 'adb install file.apk' still works? So you might be able to find alternative ways to test your package on the device. It's just a shame that it breaks the Eclipse integration.

[Guest Roman Kapl]

Yes, I have the same problems. As far as I can tell(from googling), the stock kernels do not report serial number. So Eclipse crashes just on that. You have to

• wait for somebody to recompile the kernel
  
• recompile adb and cahnge the register_transport function so that it reports fake serial number
  

[Guest]

I presume that 'adb install file.apk' still works?

Yeah, this is how I have been getting around the problem so far.

recompile adb and change the register_transport function so that it reports fake serial number

I will look into this, thanks.

Edited May 30, 2010 by Guest