I am new in android development.
I created the sample hello world and try to run it on a emulated nexus 7 system.
I am using android studio 1.8.14.
When I run the application, I am getting this message in andoid studio:
Waiting for device.
Target device: test_nexus_7 [emulator-5554]
Uploading file
local path: C:\Users\m\AndroidStudioProjects\MyApplication\app\build\outputs\apk\app-debug.apk
remote path: /data/local/tmp/com.example.m.myapplication
Installing com.example.m.myapplication
DEVICE SHELL COMMAND: pm install -r "/data/local/tmp/com.example.m.myapplication"
Error: Could not access the Package Manager. Is the system running?
what is the problem and how can I fix it?
It may be a known bug. Does this solve your issue?
"2 Error: could not access the package manager. Is the system running?
You may have gotten this error while attempting to run an Android application on an emulator or device using Android Studio. 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."
Read more at http://www.airpair.com/android/bugs-annoying-android-developers#1vMSj7GfowjRvMLG.99
Other suggestions: wait for the emulator to fully start up, which could take longer than you expected, or try debugging on an Android device, which is faster and has access to native functionality, rather than in an emulator.
Related
In Android Studio were it was supposed to show physical device list it keeps saying Loading Devices...I tried every possible answers I found online, killing ADB from task manager, reinstalling platform tool, reinstalling android studio, manually running ADB, starting ADB server manually, even starting android studio as admin. I removed anti-virus. But nothing is working.
Problem here is that when I run the adb devices it is able to detect my phone but android studio doesn't.
NOTE: I have my phone on in debug mode, with file transfer permission.
here is a screen shot of android studio, and the cmd
I have searched the internet and tried everything I have come across, but I cannot figure out what I am doing wrong. I cannot attach the debugger to my Android process in Android Studio.
I have built an app in Android Studio 2.3.3 on a virtual machine using VirtualBox and running Ubuntu 16.04.2. I have installed the app on my device, a Getac Data Logger, and have noticed that my app opens for a couple of seconds, displaying a blank white screen, and then crashes. So, I have attempted to debug the app on my device to find the problem. When I click on the "Attach debugger to Android process" icon, I can see my device as an option, however, when I select my device the OK button is grayed out. There is no way for me to move forward with this process. Sometimes the warning "debug info can be unavailable, please close other application using ADB: Monitor, DDMS, Eclipse" pops up, but not every time.
Does anyone have any ideas as to what I am missing? Does it have something to do with the limitations of working on a virtual machine?
Things I have tried:
Making sure I have allowed USB debugging on my device
Selecting all kinds of combinations of show all processes/auto/java/etc
Commands: adb kill-server, then adb start-server; adb kill-server, then adb -P 5038 start-server
Waiting to plug in my device until I launch the debugger attachment
Building debug variant
Adding android: debuggable="true" to my application in my AndroidManifest.xml, then noticing it was not necessary after building the debug variant and taking it back out
Disabling and re-enabling the ADB integration through Tools/Android/Enable ADB integration
Closing Android Studio and then opening it again
Changing the adb port
Invalidating cache/restart
Uninstalling the app, clean build, reinstalling the app
Installing the MTP using the command: apt-get install mtpfs. It says that mtpfs is already the newest version, but the Ubuntu error "Unable to open MTP device '[usb:001,021]'" does persist, just not always.
Revoking USB debugging authorizations, exiting out of Android Studio and my VirtualBox, rebooting everything, and setting it all up again.
PLEASE NOTE:
I am brand new to development (a little over a year experience in web development), brand new to app development (this is the very first app I am creating), brand new to Android Studio (again, very first app).
My device is showing up in the debugger as an option. It is just that the OK button is grayed out, no way to move forward.
I do NOT have Eclipse or Monitor (and therefore not DDMS either) running.
EDIT: I have noticed that "#com.android.ddmlib - Adb rejected connection to client '[numbers]': closed" is showing up in my terminal several times with several different number combinations. Not sure what this means. Perhaps I am running DDMS? I thought that was something that runs through Monitor?
Unplug your phone from your PC. Then plug it back in. On the pop-up, make sure you set it to “Media Sync (MTP)”.
I had intellij Idea IDE and Android Studio 4 Canary were open with Android projects at the same time, after closing both the IDEs and opening only android studio, I was able to attach the debugger to the app process.
Device connected: emulator-5554
Device is online: emulator-5554
Target device: AVD_for_Nexus_4 [emulator-5554]
Uploading file
local path: /home/verma/AndroidStudioProjects/Icandy1/App/build/apk/App-debug-unaligned.apk
remote path: /data/local/tmp/com.google.icandy1.app
Installing com.google.icandy1.app
DEVICE SHELL COMMAND: pm install -r "/data/local/tmp/com.google.icandy1.app"
Error: Could not access the Package Manager. Is the system running?
I got the above errors. Could anyone please solve this issue from Android Studio.
This is bug https://code.google.com/p/android/issues/detail?id=62113. From the bug report:
Our theory is that the IDE is trying to install the APK while the
emulator is still starting up, before it's ready to have things
installed in it. If that theory is correct, we need to have the IDE do
better detection of what state the emulator is in and have it wait
until it's ready; in the meantime, try working around it by launching
the emulator by hand, letting it get to the lockscreen and unlocking
it, and then leaving it running while you iteratively build and launch
apps from the IDE.
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:
Update:
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 devices to 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 , YOUR_FULL_APK_PATH is of any .apk file path in
your system.
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
Memory Options:
RAM: 512
VM Heap: 192
Iternal Storage: 200
SD Card:
Size:200
This Is Worked for me
1)Close Solution.
2)Close Emulator.
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)
Remove this emulator (in the AVD)
Install this emulator (in the AVD) :)
When trying to run my program on an emulator I get this error:
Device connected: emulator-5554
Device is online: emulator-5554
Target device: avd1 [emulator-5554]
Uploading file
local path: C:\Users\peter\AndroidStudioProjects\MyApplicationProject\MyApplication\build\apk\MyApplication-debug-unaligned.apk
remote path: /data/local/tmp/com.bat.myapplication
Installing com.bat.myapplication
DEVICE SHELL COMMAND: pm install -r "/data/local/tmp/com.bat.myapplication"
Error: Could not access the Package Manager. Is the system running?
any ideas? my paths, javahome etc, seem right....
Just wait until emulator be loaded completely, once it finished then you could simply run your application.
I had the same issue once.
First run only the emulator (it takes several minutes), and once it's loaded (the UI will change), then you run your program.
As other have said, this error occurs because the emulator is still in the process of launching. An attempt to access the package manager, for the device, at this time causes an error.
It's just a simple timing issue. Here are the steps to avoid this error:
Wait until the emulator 'lock screen' is showing.
Run the 'app' again (^R in most IDE's).
Choose the running device (Should be the same emulator).
App should install without error.