How can I correct an AVD Emulator's inconsistent display size?
+0
−0
How can I extend the length of an emulator? I ask because, when I invoked android-studio today, my AVD emulator was incorrectly sized, to the extent that input tap events are mis-calibrated, rendering it nigh unusable:
$HOME/Android/Sdk/emulator/emulator -avd $($HOME/Android/Sdk/emulator/emulator -list-avds) -verbose, initially, appears to operate as expected, except that its touch remains mis-calibrated:
My Environment
-
-
#!/usr/bin/env sh rpm -qf $(command -v android-studio) \ --queryformat "$( cat <<'EOF' Name: %{NAME} Version: %{VERSION} Release: %{RELEASE} Architecture: %{ARCH} Install Date: %{INSTALLTIME:date} Size: %{SIZE} Signature: %{SIGPGP:pgpsig} Source RPM: %{SOURCERPM} Build Date: %{BUILDTIME:date} Build Host: %{BUILDHOST} Packager: %{PACKAGER} Vendor: %{VENDOR} EOF )"$'\n' | yq -P -
Name: android-studio Version: 2025.3.2.6 Release: 1.fc43 Architecture: x86_64 Install Date: Tue 03 Mar 2026 19:03:14 GMT Size: 3389182154 Signature: EdDSA/SHA256, Tue 03 Mar 2026 15:54:11 GMT, Key ID e43dbfe05c4f92a3 Source RPM: android-studio-2025.3.2.6-1.fc43.src.rpm Build Date: Tue 03 Mar 2026 15:28:25 GMT Build Host: d98174fd17b5 Packager: veuxit <[email protected]>, like-engels <[email protected]> Vendor: Terra
-
-
-
#!/usr/bin/env sh cat $HOME/.android/avd/$($HOME/Android/Sdk/emulator/emulator -list-avds).avd/config.ini -
AvdId=Pixel_Tablet PlayStore.enabled=true abi.type=x86_64 avd.ini.displayname=Pixel Tablet avd.ini.encoding=UTF-8 disk.dataPartition.size=6G fastboot.chosenSnapshotFile= fastboot.forceChosenSnapshotBoot=no fastboot.forceColdBoot=no fastboot.forceFastBoot=yes hw.accelerometer=yes hw.arc=false hw.audioInput=yes hw.battery=yes hw.camera.back=virtualscene hw.camera.front=emulated hw.cpu.arch=x86_64 hw.cpu.ncore=4 hw.dPad=no hw.device.hash2=MD5:4eeb2eb720b193342b0f2b948e427ed5 hw.device.manufacturer=Google hw.device.name=pixel_tablet hw.gps=no hw.gpu.enabled=yes hw.gpu.mode=auto hw.gyroscope=yes hw.initialOrientation=portrait hw.keyboard=yes hw.lcd.density=320 hw.lcd.height=1600 hw.lcd.width=2560 hw.mainKeys=no hw.ramSize=2048 hw.sdCard=yes hw.sensors.light=yes hw.sensors.magnetic_field=yes hw.sensors.orientation=yes hw.sensors.pressure=no hw.sensors.proximity=no hw.trackBall=no image.sysdir.1=system-images/android-CANARY/google_apis_playstore_ps16k/x86_64/ runtime.network.latency=none runtime.network.speed=full sdcard.size=512M showDeviceFrame=yes skin.dynamic=yes skin.name=pixel_tablet skin.path=/home/RokeJulianLockhart/Android/Sdk/skins/pixel_tablet tag.display=Google APIs PlayStore tag.displaynames=Google APIs PlayStore,Page Size 16KB,AI Glasses Compatible tag.id=google_apis_playstore tag.ids=google_apis_playstore,page_size_16kb,ai_glasses_compatible target=android-CANARY vm.heapSize=192
-
1 answer
+0
−0
-
Install the Command-Line Tools (alongside the SDK):
-
Insofar as it's the sole AVD emulator (not image) installed:
#!/usr/bin/env sh $HOME/Android/Sdk/cmdline-tools/latest/bin/avdmanager delete avd -n $($HOME/Android/Sdk/emulator/emulator -list-avds) $HOME/Android/Sdk/cmdline-tools/latest/bin/sdkmanager "system-images;android-CANARY;google_apis_playstore_ps16k;$(uname -m)" $HOME/Android/Sdk/cmdline-tools/latest/bin/avdmanager create avd -k "system-images;android-CANARY;google_apis_playstore_ps16k;$(uname -m)" -d pixel_tablet --name CANARY_google_apis_playstore_ps16k_pixel_tablet $HOME/Android/Sdk/emulator/emulator -avd $($HOME/Android/Sdk/emulator/emulator -list-avds) -verboseOtherwise, specify the name.
My suspicion of the cause is that, because the new version of the emulator is rotated, and does not include a border, when it was updated, this caused the previous image to become inconsistent:
0 comment threads
0 comment threads