« Back to Cius Developer Questions

Unable to debug on device: no permissions

Combination View Flat View Tree View
Threads [ Previous | Next ]
Unable to debug on device: no permissions
Answer
1/10/12 6:02 PM
After recieving a Cius loaner, I finally got 'Unknown Sources' and 'USB debugging' checked. I was never propmpted for a firmware update, so I guess there was none?  So in theory, I should be ready to debug on device, correct?  However, I still can't. When I plug in via USB and try to run, the device chooser shows a device with a serial number of "???????????" an AVD name of N/A and a Target of "unknown".  Every other device I plug in works properly.  Running ./adb devices gives me:
 
List of devices attached 
???????????? no permissions


Any suggestions on how to actually test an app on this device? 


Thanks.
Flag

RE: Unable to debug on device: no permissions
Answer
1/10/12 4:26 PM as a reply to Dave Vedder.
Can I ask what operating system you are running? These USB debugging problems are usually platform-related.

James Catalano
Flag

RE: Unable to debug on device: no permissions
Answer
1/10/12 4:27 PM as a reply to Dave Vedder.
Dave -

Are you using Windows? If so, you will need to install the USB drivers. You can find out more information about this topic here http://developer.cisco.com/web/cius-developer/usb-driver-installation

thanks
Amanda
Flag

RE: Unable to debug on device: no permissions
Answer
1/10/12 4:32 PM as a reply to Amanda Whaley.
Thanks for the quick replies!

I'm running Ubuntu Linux (11.10) Again, I've plugged in a couple phones and a Motorola Xoom, and they are "seen" and I can debug on them.

Thanks,

Dave
Flag

RE: Unable to debug on device: no permissions
Answer
1/10/12 4:44 PM as a reply to Dave Vedder.
When I've seen the 'No Permissions' message in the past it's either:
 
- Running ./adb not as root.  E.g.:
 
$ sudo ./adb devices
 
Or the ADB server service was started previously as non-root, in which case I had to kill the server first:
 
$ sudo ./adb kill-server
$ sudo ./adb devices
Flag

RE: Unable to debug on device: no permissions
Answer
1/10/12 4:49 PM as a reply to Dave Vedder.
Dave

Another solution is to follow the setup instructions found here for properly setting up hardware devices for debugging:

http://developer.android.com/guide/developing/device.html

Under step 4 of "Setting up a Device for Development", you'll see system specific instructions. Yours will obviously be for Ubuntu Linux, which is the 3rd bullet. Now technically, you should have had to do this for your other Android devices, so either you lucked out with the other ones or you did this a while ago and just forgot.

When you get to the part about a USB Vendor ID, you can use the one for Google (18D1) in this instance.

James Catalano
Flag

RE: Unable to debug on device: no permissions
Answer
1/10/12 4:53 PM as a reply to James Catalano.
For Ubuntu, you don't have to mess with the udev rules if you execute ADB via sudo.  If you do prefer to run ADB as a normal user, then the udev rules should enable that to work.
Flag

RE: Unable to debug on device: no permissions
Answer
1/10/12 5:14 PM as a reply to James Catalano.
Hooray! Thanks all for helping me through this. I now have my app running on a Cius. Turns out I needed to add the generic google vendor line in my 51-android.rules file, *and* kill-server and run adb devices as root before it clicked.

Thanks again, I really appreciate the help.

-Dave
Flag

RE: Unable to debug on device: no permissions
Answer
8/28/12 6:05 AM as a reply to Dave Vedder.
Now that Cius is apparently discontinued, could anyone please tell me an easy way to "Allow Unknown.." and do things like upgrade my Cius to Android 4.0?
 
Thanks!
 
DesigningJustin@gmail.com
Flag