Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

https://github.com/morrisseyai/avdedit

AVDEdit is a basic Android Virtual Device editor which allows direct editing of values which are not editable or accessible via the standard AVD Manager.
https://github.com/morrisseyai/avdedit

Last synced: 19 days ago
JSON representation

AVDEdit is a basic Android Virtual Device editor which allows direct editing of values which are not editable or accessible via the standard AVD Manager.

Host: GitHub
URL: https://github.com/morrisseyai/avdedit
Owner: morrisseyai
Created: 2022-04-13T13:35:56.000Z (about 2 years ago)
Default Branch: main
Last Pushed: 2022-04-21T14:09:09.000Z (about 2 years ago)
Last Synced: 2024-01-14T13:16:28.671Z (6 months ago)
Language: Kotlin
Size: 989 KB
Stars: 4
Watchers: 2
Forks: 0
Open Issues: 0
Metadata Files:
- Readme: README.md

Lists

awesome-compose-for-desktop - AVDEdit - Android Virtual Device editor (Projects using Compose for Desktop)

README

# AVDEdit
AVDEdit is a basic Android Virtual Device editor which allows direct editing of values which are not editable or accessible via the standard AVD Manager.

![AVDEdit screenshot](screenshots/avdedit.png)

## Feature todo list

- [x] Allow selection of AVD
- [x] Display list of config settings with checkboxes for true/false/yes/no values
- [x] Functionality to edit existing and add new config settings
- [x] Save function
- [ ] Allow user to choose their AVD directory instead of using platform default
- [ ] Provide a way to delete settings

## Motivation
I created this app out of frustration that running a single Android emulator would frequently see my CPU pegged at 500-800% for no reason, killing my MacBook's battery very quickly.

While investigating this behaviour I found [this StackOverflow answer](https://stackoverflow.com/a/42203744) which outlined a few mystical AVD settings which can be set by editing a config file, but not by using the actual AVD Manager provided by Android Studio.

Despite my skepticism, I tried disabling `hw.audioInput` and `hw.audioOutput` and sure enough it really did put an end to the constant inexplicably high CPU usage by the emulator.

I could have spent time trying to understand *why* certain settings created this problem, but realistically I don't care, I just want to get things done without the emulator nuking my battery, and it was a great excuse to learn more about Compose for Desktop.