Add VS Code run-and-debug configurations for the Android emulator

F5 now builds, installs and attaches the debugger on the emulator, with the
emulator booted automatically first, so there is no manual setup step between
opening the project and stepping through code.

tool/start_emulator.ps1 backs the preLaunchTask and is idempotent: it returns in
about three seconds when a device is already attached, so re-launching the
debugger cannot stack emulator instances. It fails with a useful message when
the AVD is missing rather than hanging until a timeout.

Five configurations rather than one, because they answer different questions.
The profile-mode entry matters most for what comes next: debug builds run the
Dart VM unoptimised, so the radar animation always looks worse than it is, and
milestone 3's acceptance criterion is about whether it runs smoothly. The
Windows entry trades the map away for a launch that takes seconds, which is
worth it for pure UI work.

Verified on this machine: the script cold-boots the AVD and waits for
sys.boot_completed, and a second run exits immediately.

Also removes the broken pixel_7_-_api_35 AVD, which could not boot because its
system image was never installed. That returned 4.8 GB, taking free disk from
3.5 GB to 10.7 GB.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

This commit is contained in:

Alby96

2026-09-10 12:36:36 +02:00

co-authored by

Claude Opus 5

parent 7c0a1bd180

commit 75c4c55f81

5 changed files with 260 additions and 0 deletions

									
										Nuvolari/.vscode/extensions.json
									
Vendored

		+7
		
												View File
												
				@@ -0,0 +1,7 @@

				{

				  "recommendations": [

				    "dart-code.flutter",

				    "dart-code.dart-code",

				    "ms-vscode.powershell"

				  ]

				}