Repository navigation
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #132, based on
04a63198. Reduce emulator RAM adds an opt-in launch profile for eligible x86_64 phone AVDs on Windows x64. The switch applies at the next Mobile Dev start. Switching it off restores the AVD's configured allocation. The Windows profile passes only the additional-memoryargument. Apple Silicon keeps its existing defaults and guest optimizers.Windows device evidence
The MCP preference, boot, shutdown, install and launch tools ran against isolated WHPX AVDs. Android 16 Google APIs and Android 17 Google Play each completed stock → on → off → on → off. The final package repeated the Android 16 on/off pair on the retained AVD and ran the full Android 17 sequence. A fresh MCP server recognized the running profile on each image.
The first stock boot on each image initialized the fixture. The installed APK digest, private test value and deliberately disabled Print Spooler matched on all 10 subsequent cold boots. All 250 Android 16 user-0 package flags matched. On Android 17, two NFC packages disabled themselves during setup. A separate stock-only AVD reproduced both changes. Measurements cover idle memory on one Windows 11 host. API 35 eligibility is covered by configuration tests. Method, devices and restoration results
Why package optimization remains open
After avdslim restored packages and removed its marker on Android 16, an immediate emulator stop left 38/38 packages disabled with v1.0.16 and 11/38 with v1.0.17 on the next cold boot. In an isolated synthetic adb test, v1.0.17 issued 70 distinct enable operations for either an empty or a null list, including a package disabled before the test. Even a successful single-package restore converted Android's default flag into explicitly enabled. Durable per-user state and recovery across interrupted boots remain separate work.
Validation
android.ram_profile.boot.durationdistribution records boot completion time and outcome. Boot identifiers stay local and serve only to detect when a restart is required.