16

I created a small ActivityFile.java. After running it, it takes a while to show the Android Emulator on screen. After 10 minutes, I got this error.

Emulator: qemu-system-i386.exe: Unable to open 
C:\Android\.android\avd\MyNexus5API25.avd\data\misc\pstore\pstore.bin: Permission denied

I am a beginner to Android Studio, so do not the reason behind this issue.

Please help??

azro
  • 53,056
  • 7
  • 34
  • 70
user3624146
  • 369
  • 1
  • 5
  • 16
  • 1
    This file is also modified when saving state of the virtual machine on closing. If it fails, the machine would not start from saved state. If that's the situation you find yourself in, for time being choose Boot Option: "Cold Boot" in advanced settings of this virtual machine in AVD Manager. – mrówa Mar 13 '18 at 21:31

4 Answers4

24

Go to C:\Android.android\avd\MyNexus5API25.avd\data\misc, make right click on pstore, pick Properties and uncheck box Only for reading (Title may be a little different). This is a new non critical bug (about 2 days ago update), you should not attach importance to this.

Platon Efimov
  • 582
  • 2
  • 6
  • 25
  • I am a beginner in Android development.I created a simple app with one page only.When I run my App, the emulator gets launched but my app is not listed in the Home launcher. What might be the problem?? In addition to this,when emulator gets launched, it takes too much for a device to come online showing message as "Waiting for the target device to come online". Please help me in resolving these issues also. – user3624146 Jan 06 '18 at 00:30
  • 1) Some versions of Android have menu of applications, check this. 2) Android Studio can't install app on not ready device. Android emulator must turn on the device. If it is too long you should reinstall Android components on SSD, check RAM usage and make sure that the processor is powerful enough OR try debug on real device, it is usually already on. – Platon Efimov Jan 06 '18 at 06:24
  • 5
    I'm getting the error message in question upon closing the emulator. Trying this fix gets rid of the error for one shut down of the emulator. But then when I start and stop the emulator, the error shows up again and the directory is again marked as read only. – justarandomuser12345 Jan 09 '18 at 20:35
  • As the only bug report I found had no emulator files attached, I created a new bug report: https://issuetracker.google.com/73249556. Seeing exactly the symptoms as described by @justarandomuser12345. – A. L. Flanagan Feb 12 '18 at 22:13
0

just did this delete the lock file in this route and it worked for me C:\Users*your user*.android\avd/Nexus_4_API_22.avd/*.lock

0

I got the same problem and i solved it by recreating the AVD from scratch

  • use Android studio and delete the AVD first
  • delete the Folders according to your AVD name ex-: Nexus_5X_API_27 folder structure

  • create a new AVD from the Android Studio

Amila kumara
  • 439
  • 7
  • 12
0

project--> gradle --> xxclasspath 'com.google.gms:google-services:3.1.0'

classpath 'com.google.gms:google-services:3.2.0'

you have to change one.

Stephen Rauch
  • 47,830
  • 31
  • 106
  • 135