Take the 2-minute tour ×
Android Enthusiasts Stack Exchange is a question and answer site for enthusiasts and power users of the Android operating system. It's 100% free, no registration required.

I try to send an intent using an android-shell. The app starts, "su" works nice, but when I enter something like "adb shell am broadcast -a android.intent.action.SCREEN_ON" I receive an error:

error: device not found

when trying to list the devices with

adb devices

the result list is empty.

WHat am I am doing wrong? (My tablet is rooted, of course)

share|improve this question
2  
Do you have USB debugging enabled? –  Ryan Conrad Nov 7 '12 at 16:55
    
Yes. But should not matter as I am not connecting by USB but have a console-App directly on my device –  Ole Albers Nov 8 '12 at 9:57
    
AFAIR the adb deamon on the device is only running if USB debugging is enabled. –  Robert Dec 8 '12 at 17:03

1 Answer 1

up vote 1 down vote accepted

If you are using the terminal app on your device then you don't need to use "adb shell". You just need to run the "am broadcast -a android.intent.action.SCREEN_ON". I don't know why you would want to run that from your terminal app since the screen would already be on.

You need to have USB debugging on if you are trying to connect via the console on your PC to your device. You also need to have the drivers installed if you are using a Windows machine.

share|improve this answer
    
SCREEN_ON was just the maximum simple example to show my problem. Atually I use "org.prowl.torque.REQUEST_TORQUE_QUIT" to end the torque-App –  Ole Albers Nov 8 '12 at 12:38

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.