Hi, Strange, i think you are a wizard. I actually tried that before getting the same error but when I read your suggestion and tried again it suddenly works. ADB install likewise. Now ...is there currently a way to enable it from commandline? Florian 2011/6/28, Ken Perry <whistler@xxxxxxxxxxxxx>: > > You can do > > Adb shell > > While your emulator is running and you should get a linux # command line > where you can do simple commands like ls to prove that your emulator is even > running. It sounds like it is not. > > Ken > > -----Original Message----- > From: programmingblind-bounce@xxxxxxxxxxxxx > [mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Florian-achtige > Sent: Tuesday, June 28, 2011 4:42 AM > To: programmingblind > Subject: some android issues, need help > > Hi, > > I thought let's play with the android SDK. I was bored so installed it > and grabbed some packages, probably way more then I actually need. > Then, I created an AVD (android virtual device) and launched it. > I couldn't use it yet , but I knew that beforehand . I'd read about > the adb command though, and that it can install packages using the > commandline. So I decided to make sure talkback is installed and > grabbed the latest off googleCode. > But I am running into a problem. When I issue > adb -e install talkback.apk > > I first get: > ADB: protocol fault (no status) > > And when i try again: > Error: device not found. > > While the emulator is at least opened. I can't tell you if it is > running for obvious reasons. Apparently on Linux this can be fixed by > running adb as root ...but what does one do on windows? > > Thanks a lot, > Florian > __________ > View the list's information and change your settings at > //www.freelists.org/list/programmingblind > > __________ > View the list's information and change your settings at > //www.freelists.org/list/programmingblind > > __________ View the list's information and change your settings at //www.freelists.org/list/programmingblind