0

When I run an app from Eclipse and the Android Device Chooser comes up, some devices start with the Debug column set to Yes. This allows you to debug an app on the device without setting debuggable in the manifest to true. Does anyone know how to change this on the phone? I'd love to be able to set this Debug attribute set to Yes for any given phone. Any way including rooting and installing a particular ROM is a welcome suggestion if it works. Just to pre-empt it, Settings > Applications > Development and enable USB debugging is not the answer.

The only other question I found related was this: Android Device Chooser - Debug column, but there weren't any good answers to this there.

Android Device Chooser

Community
  • 1
  • 1
kabuko
  • 36,028
  • 10
  • 80
  • 93
  • Is the HT16BVS00148 device rooted? – Greg Giacovelli Oct 29 '11 at 10:19
  • I didn't root it, but it's a pre-release phone from a manufacturer that may possibly be de facto rooted. I have full access to all directories in shell. – kabuko Oct 30 '11 at 03:18
  • Yeah that's pretty much the same thing. Like I bet if you do something like, adb -s root, you will get a shell. And if you do it on the non debuggable one, you will get an error. – Greg Giacovelli Nov 01 '11 at 16:22
  • Yep, if I try to run `adb root`, I get "adbd is already running as root". I'm *pretty* sure that I've had another device which was rooted which wasn't debug though. So it's probably correlated but not 1-to-1. – kabuko Nov 01 '11 at 17:22
  • Sorry I was on the train. I meant adb shell, and then type su. Like log me in as root. adb root will just start the daemon as root (that's your host machine permissions). There is probably a debug flag on at the os Image too which reports this – Greg Giacovelli Nov 01 '11 at 18:54
  • `su` works on the debug device. I think `adb root` is relevant actually. If I do `adb root` for a non-debug device I get "adbd cannot run as root in production builds". – kabuko Nov 01 '11 at 19:28

1 Answers1

0

While I haven't been able to pin it down with definitive evidence, it seems this is due to the ROM being signed with test keys. While forums like XDA abound in mentions of test keys in relation to getting root, and you can find on StackOverflow how to detect test keys, I have as of yet been unable to find any information on what signing with test keys does. As far as I can tell though, this is one of those things.

Community
  • 1
  • 1
kabuko
  • 36,028
  • 10
  • 80
  • 93