CODEWITHSUNDEEP
androidemulation
stuXnet
stuXnet

Reputation: 4349

Android Emulator is (very) distorted

I guess a picture explains more than 1000 words...

enter image description here

This is the screen I get after booting - but the boot animation itself is already distorted. It's possible to interact with the emulator at the elements usual positions - in the screenshot, for example, if I'm clicking in the middle of the lower bar, the home button gets selected.

I had some other AVDs, this is the first one where this behavior occurs.

The config.ini for the AVD, running on Windows 7:

avd.ini.encoding=UTF-8
abi.type=x86
disk.dataPartition.size=200M
hw.accelerometer=yes
hw.audioInput=yes
hw.battery=yes
hw.camera.back=none
hw.cpu.arch=x86
hw.dPad=no
hw.device.hash2=MD5:750a657019b49e621c42ce9a20c2cc30
hw.device.manufacturer=User
hw.device.name=Samsung Tab
hw.gps=yes
hw.keyboard=yes
hw.lcd.density=160
hw.mainKeys=no
hw.ramSize=2048
hw.sdCard=no
hw.sensors.orientation=yes
hw.sensors.proximity=yes
hw.trackBall=no
image.sysdir.1=system-images\android-19\default\x86\
skin.dynamic=yes
skin.name=601x962
skin.path=601x962
tag.display=Default
tag.id=default
vm.heapSize=32

The device is a custom configuration, and I've created a Gist with my devices.xml

I've found this question here on SO, where the problem seems to be a wrong orientation (upside down) - the answer didn't really help me, and I hope that this bug doesn't exist for three years.

Is this a common problem, and is there some workaround?

Upvotes: 0

Views: 922

Answers (1)

Chris Stratton
Chris Stratton

Reputation: 40357

A diagonal display like this tends to be caused by a disagreement (usually by 1 pixel) about the width of the display between the code writing to a linear framebuffer and the code or hardware displaying it.

Your specification of a 601 pixel wide skin is very suspicious. Consider if the width should actually be 600.

Upvotes: 1

Related Questions