I installed android studio and tried to run easy projects.
But I caught strange error message:
Waiting for device. /usr/local/idea/android-studio/sdk/tools/emulator -avd Nexus-4-18-xhdpi -netspeed full -netdelay none emulator: emulator window was out of view and was recentered Device connected: emulator-5554 Device is online: emulator-5554 Target device: Nexus-4-18-xhdpi [emulator-5554] Uploading file local path: /home/nazar/Documents/coursera-android/Examples/HelloAndroid/out/production/HelloAndroid/HelloAndroid.apk remote path: /data/local/tmp/course.examples.HelloWorld.HelloWorld Installing course.examples.HelloWorld.HelloWorld DEVICE SHELL COMMAND: pm install -r "/data/local/tmp/course.examples.HelloWorld.HelloWorld" Error: Could not access the Package Manager. Is the system running?
I couldn’t figure out why this happen?
I installed sdk version and configured emulator. Any suggestions?
Here is emulator confiuration:
I tried to install Genymotion device and use few virtual devices, but caught:
Waiting for device. Target device: genymotion-nexus_4___4_4_2___api_19___768x1280-192.168.56.101:5555 Uploading file local path: /home/nazar/Documents/coursera-android/Examples/HelloAndroid/out/production/HelloAndroid/HelloAndroid.apk remote path: /data/local/tmp/course.examples.HelloWorld.HelloWorld Installing course.examples.HelloWorld.HelloWorld DEVICE SHELL COMMAND: pm install -r "/data/local/tmp/course.examples.HelloWorld.HelloWorld" WARNING: linker: libdvm.so has text relocations. This is wasting memory and is a security risk. Please fix. Error: Could not access the Package Manager. Is the system running?
How to solve this error?
First make sure you are running Android Studio version above 0.3.2 because there was some issue reported regarding the same in AS 0.3.2 . If it is not you can update it from
Help >Check for update.
If you are already running AS above 0.3.2 :
Seems like issue is with your emulator not with Android Studio. It may happen that you are trying to install application before even the emulator started properly.
Wait till the home screen appears in the emulator before trying to install any application.
Also try to install any apk in Emulator from command line
Steps to install
- Go to $Android_SDK_DIR\platform-tools, right click there keeping
shift key pressed and Chose “Open Command Window here”.
- Run command
adb devicesto make sure yout emulator is running
properly. It will show all your running emulators.
- Now if emulators are showing properly, type the command
adb install, YOUR_FULL_APK_PATH is of any .apk file path in
Please update if this works fine.
The most common cause of this error is simple: You have to manually unlock your Android Virtual Device by swiping the “lock” icon on the screen. Security measures prevent the emulator from letting you connect the debugger before doing this.
The problem is resolved:
In Android Studio
- Start run/debug
- if you see the message
- Do not closed the AVD, just click on run/debug again, the Application will be running when you unlock the application.
The same problem but different solution, I modified my Virtual Device, I changed Memory option and Internal Storage, and it works fine.
RAM:512 , VM HEap: 192, Internal Storage=200, SD Card Size: 200 for Device Nexus 4 android 4.2.2.
In my case this error was caused by SELinux. I got to set SELinux to permissive.
adb shell su 0 setenforce 0
I had this issue, but I found that simply killing the emulator and restarting it worked. There seems to be some sort of race condition where the emulator has not initialized before Android Studio tries to launch the apk and so you get the package error.
I had this too, and using this config worked for me :
Device: Nexus One
Target: Android 4.2.2 -api level 17
CPU/ABI: ARM (armeabi-v7a)
Keyboard: Hardware keyboard present
VM Heap: 192
Iternal Storage: 200
This Is Worked for me
3)Run Emulator and Wait till it launch completely and shows Home Screen.
4)After that only Open Solution And Clean,Rebuild and Try to deploy Application.
The same happened to me right now. I don’t know if there is another but for me the following worked:
- Opened AVD (Android Virtual Device) Manager
- Started virtual device
- Hit the Run button again (that one at status bar)
Explanation: The problem happened because of timeout. Once device had started, the Android Studio could comunicate with him. (v 0.5.3)