Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Running existing emulators through andromatic doesn't work if the system image doesn't exist in the andromatic cache directory #7

Open
baltpeter opened this issue Jun 7, 2023 · 2 comments
Open

Running existing emulators through andromatic doesn't work if the system image doesn't exist in the andromatic cache directory #7

baltpeter opened this issue Jun 7, 2023 · 2 comments
Labels
help wanted Extra attention is needed UX

Comments

@baltpeter
Copy link
Member

Not sure what an elegant way of fixing this would be. But it's unfortunate.
@baltpeter baltpeter added the UX label Jun 7, 2023
@baltpeter baltpeter mentioned this issue Jun 7, 2023
Merged
@baltpeter
Copy link
Member Author

For me, the problem was that I had created the emulator through a non-andromatic avdmanager. It will also happen if you clear your cache directory after creating the emulator and don't re-download the system image.

@baltpeter baltpeter added the help wanted Extra attention is needed label Jun 27, 2024
@techware01
Copy link

techware01 commented Sep 19, 2024 •
edited
Loading

Hey,
just stumbled across the same issue. I figured it would be great to be able to specify a different android-home directory with all the required tools already installed, using the installation routine to the andromatic-cache-dir as a fallback. Further details in #10

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted Extra attention is needed UX
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@baltpeter @techware01