-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Back & Restore avd not working #129
Comments
The same issue is seen here too. Did you ever get to fix it? @omritoptix |
A bit more data in case anyone else encounters this issue. I've found that if before stopping and rm the container I turn off the emulator phone on novnc, this issue goes away. |
same issue as above, i try to use docker volume, but it still not save any changes in avd every time i restart/stop the container. |
In the file src/app.py there is a lookup for 'hw.device.name={}', however in the config file for my emulator (Nexus 5), there are spaces around the equals sign. I changed it to 'hw.device.name = {}' and then re-built the image. It now works fine for me, remembering the avd state. |
The spacing issue appears to depend on the API version. I moved from API 27, where the spaces were needed, back to API 23, where the spaces must be removed. |
Operating System:
Ubuntu 18.04
Docker Image:
butomo1989/docker-android-x86-7.1.1
Docker Version:
17.12.1-ce
Docker-compose version (Only if you use it):
1.22.0
Docker Command to start docker-android:
docker-compose up --build -d
Expected Behavior
I installed an apk on a fresh avd.
I expected the former avd to be used (with the installed apk) once I restart docker compose with
docker-compose stop && echo 'y' | docker-compose rm && docker-compose up --build -d
Actual Behavior
The avd is initialized from scratch again and doesn't include the previously installed apk.
docker compose file
Update:
it seems like the file
devices.xml
is not created under the.android
directory which causes theis_initialized()
function to returnFalse
The text was updated successfully, but these errors were encountered: