I'm trying to run an emulator and have created multiple emulators to test my app. For some reason, after I restarted my Adb, I am getting this Connection Error.
My emulators were working fine before I pressed to restart. I'm also using a Mac and not Windows.
Thanks!
I found out the answer.
For some reason ADT lost my emulator that I was using even though it was checked so I had to go to Run -> Run Configuration then click Target and manually choose one emulator and press Run at the bottom.
Hope this helps anyone else who runs into this issue!
Here's a link to the youtube video that I found that helped me.
https://www.youtube.com/watch?v=7PSONc6iyQQ
Related
Well a windows 10 update broke sleep, the computer went to sleep with the emulator open and now that's broken. When I run an app to launch in the emulator it will boot the emulator but won't install just time out. When I try and run an app into a running emulator instance Studio says:
com.android.ddmlib.AdbCommandRejectedException: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Error while Installing APK
I've followed some of the other threads here. I've tried changing
the environmental variable in control panel, but in fact I think it
pointed to the right place originally, where the sdks are these
days.
I've tried restarting the PC. I did try deleting a couple of
adb files, that didn't work.
I've tried deleting all the sdks and
downloading them again.
I've tried uninstalling and updating Android
Studio, several times. Now on AS 3.1, still not working.
Bit of a nightmare really.
How do I set the vendor keys? Using AS console commands? Can anyone point me to a dummies guide, this is a bit of a tangent for me, wish I could fix it from the GUI.
The working fix for this particular issue is to enable Developer options on your emulator and enable "USB Debugging".
OK so eventually downloading a nexus 4 x86 image android 27, with no play store worked. Sorry if this is repetition. Long live working emulators
Combining answers from here and there gives an answer that also worked for me in IntelliJ IDEA. I assume the issue is the same, since the emulator and AVD is the same.
Option 1:
Restart the emulator from AVD
Option 2:
Wipe the emulator data
Option 3: Stop the emulator. Then make sure it is up to date and try again.
If it still does not work, restart the adb server and retry.
adb kill-server && adb start-server
If it still does not work, perhaps your adb is out of date... somehow. This was the case for me. Running the following fixed that for me.
adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
emulator-5554 device
If it is now working for some emulators but not newly created ones, take note of the message in the emulator selection box: "Press Ok in the Allow USB Debugging Dialog"
Sadly, there is no such dialog. So go and enable Developer Mode in the settings of your emulated OS by tapping the Build Number several times. Then go to the Developer Settings and enable USB debugging.
After recent upgrades of emulator, the virtual device*) stays unauthorized. When I cold boot the emulator, sometimes I see the expected confirmation dialog, but this dialog goes away immediately, leaving no chance to click 'OK'.
We're aware of this problem and plan to fix it soon.
* Here, I was running x86 with API 28 and Google Play on Windows 10. I don't know which other scenarios are effected.
For anyone who might encounter this in the future -- I mean the ultimate issue of receiving the error, "This adb server's $ADB_VENDOR_KEYS is not set" despite not having any (or any sufficient) opportunity to click OK...
Resolution: In the Developer Settings, select the option to, "Remove existing authorized adb keys on device." Repeat the previous action -- the prompt will once again appear, as if the very first time.
-Mike
Go to developer options in your device and click on 'Revoke USB debugging authorizations'. Disconnect and reconnect your device. You'll get a prompt on your device to authorize your computer to connect to your device. click on 'OK' and your set.
Basically, the authorization key has gone out of date or it's no longer present. So, we just have to set a new autorization key and revoke the old ones.
The connection to adb is down, and a severe error has occured.
You must restart adb and Eclipse.
squares_senior_project] Please ensure that adb is correctly located at 'C:\Users\Nick\android-sdks\platform-tools\adb.exe' and can be executed.
I have been continually getting the above error when I try to run my application for the past 4 days now. I can start the emulator through the AVDM and run an older version of my app that has already been loaded, but for some reason the emulator wont update the app anymore and I cant figure out why. When I try to run it once the emulator is up and running I get the error: createRenderThread failed to connect. I have restarted my computer, eclipse, and the adb. I thought it may have been something with my firewall keeping the computer from recognizing the emulator but I cant see any thing that seems to be related to eclipse, I could be wrong though. This is my senior project and the dead line is approaching and i'm getting desperate so any and all suggestions would be greatly appreciated. Thank you.
I have been working for a year with eclipse, but after I upgraded to the Android SDK Tools v20, the emulator doesn't work (absolutely nothing happens). I have everything installed as always, but when I run the emulator, it doesn't appear anymore (althought just after installing SDK Tools v20 it worked twice).
I have even installed again the SO (Linux Mint), after I tried everything I read here, at curiously, the emulator worked 4 or 5 times. The symptoms are these:
-when I run the app, nothing happens in my laptop, but if I put the mouse over the green triangle for running the app, it says: run (already running)
-I've tried to kill the server with adb but doesn't work
-If I list the devices with adb devices, it doesn list any device, even if eclipse says that is running the emulator
-I've tried two different versions of Eclipse: Juno and Galileo, but it's the same
-I've tried to run an emulator independently, but it doesn't work
-I've created several AVD, with different APIs and characteristics, but nothing happens
Does anybody has any solution to this?
Thanks
Good idea to make :Project ->clean
Window ->AVD Manager -> pick your virtual device ->Edit-> Snapshot(make sure is disabled) ->Edit AVD (try again, if still not working , then try to launch the emulator directly from AVD Manager -> Start).
Once the emulator is starting then you can check back the snapshot option again.
If nothing of that works, then try to uninstall/Install SDK again.
I wonder if anyone has faced the same problem.
When we done some modification on the code, as the emulator is running; is there any way we could see the instant change without closing the emulator?
Sometimes when I made changes on the code then run the emulator, the amendment that I made doesn't seem to show on the emulator even after I clean the project.
Does anyone have any idea how to solve this?
Thanks.
Eclipse has an option under 'Run' in the menu bar to build, and run. This will re-package the application and send it to either your AVD, or attached android phone.
I moved my Android project to a laptop and now I get this when I hit Debug. Sounds like this is a bug? This shouldn't happen via Eclipse as far as I know.
Re-installation failed due to different application signatures.
The weirdest thing is this happened after I upgraded sdk/adt and Eclipse to support SDK 2.2 It was working fine earlier, and now it doesn't, so it might be a bug.
It happens because keystores on your laptop and original pc are different. it's called debug.keystrore
and located in %USER_HOME%/.android/ folder. TO be more specific it happens because eclipse tries to push apk with reinstall key. So you have two options
Share debug.keystore between various development pc's
Manually uninstall your apk from device ( using adb )
I also got the same problem and fixed it. you should do the following to fix it,
Uninstall the application from your mobile if you load it
already.
To uninstall goto settings->application->manage application.
Run the application again and choose the mobile
Hope this will help you
After you copy debug.keystore to your PC, you need to rebuild project on PC.
I had the same issue using the Droid emulator. I solved it by uninstalling the package from the application settings in the emulator as you would a normal device. On the next run, it reinstalled and the error went away.
I got the same problem and fixed it by just wiping the user data on the emulator. My guess is that the emulator keeps the project installed unless you wipe the data, so if your new project doesn't match some internal parameters it doesn't like it and won't reinstall it.
I also had the same problem and fixed it by uninstalling the app and reinstall it again.
ah i think i found your answer:
Why does the app signature change in Android after a classpath change?
its changed if you change the classpath
After searching and checking the phone, i came to know that i am currently developing 2nd version of this application which is already downloaded from android market in my phone, now as this app is signed and having different signatures this is throwing the above error.
Now, to resolve this issue, i had just uninstalled the app from mobile and run/install the application again.
I had the same issue with the emulator and i ran the command "adb uninstall TheNameOfPackage". Of course you must first go to the directory where the adb.exe has been installed, usually C:\Program Files\Android\android-sdk\platform-tools, and then run the above command.
For me after I copied all of my keystore files from my machine at home, I had to do a Project->clean. After that it worked perfectly.
When i tried to uninstall the application from my device after this issue occurs, i cannot able to find the app in my device. I don know where it gone. Then i uninstalled using adb,
adb -d uninstall <app package name>
This is the answer who are facing the issue similar to my problem.
I had the same issue.
To fix it I uninstalled the old .apk of the project from my device.
Go to device/emulator Settings -> Apps, find your app and uninstall it.
Or
In Android Studio open tab "Gradle" (on the right side), open:
appName
..appName
...Tasks
....install
.....uninstallAll
and click twice on this task to execute it.
Important note:
If you still get this error after uninstalling, try to Build->Clean Project.
If you still get this error, even if in your device Settings->Apps list you have no this app already, try to Build->Clean Project