[TIMOB-9892] Android: Emulator: MacBook Pro Retina Display: Emulator is improperly sized and touch events are inaccurate

GitHub Issue	n/a
Type	Bug
Priority	Medium
Status	Closed
Resolution	Not Our Bug
Resolution Date	2013-08-01T22:56:15.000+0000
Affected Version/s	Release 2.1.0
Fix Version/s	n/a
Components	Android
Labels	allen-review, core, qe-and060112
Reporter	Dustin Hyde
Assignee	Allen Yeung
Created	2012-07-05T16:23:30.000+0000
Updated	2017-03-29T16:09:38.000+0000

Description

The Android Emulator is improperly displayed and the touch events are inaccurate on the MacBook Pro Retina Display. This is an android issue: http://code.google.com/p/android/issues/detail?id=33383 Attached image courtesy of: http://stackoverflow.com/users/147333/corey-d Steps to Reproduce: 1. Buy a MacBook Pro w/Retina Display. 2. Install Titanium Studio and the Android SDK. 3. Open Titanium Studio and create a new Titanium Mobile project. 4. Run project in Android Emulator. Actual Result: Emulator is poorly displayed. Expected Result: Emulator should display properly and receive events in the correct location.

Attachments

File	Date	Size
Retina Android Emulator.jpeg	2012-07-05T16:23:30.000+0000	603574

Comments

Bill Dawson 2012-09-25

[Android Issue 33383](http://code.google.com/p/android/issues/detail?id=33383) is still not resolved, but it does have an assignee and a status of "FutureRelease". Some participants in the discussion indicate that a preview of ADT 21 may have fixed the resolution problem (though the virtual keyboard and trackball are missing.) Moving this JIRA ticket to next sprint to check Android's status again then.
Chris Barber 2013-08-01

[~dhyde] Could you please re-investigate this issue? The Android issue 33383 was resolved in July 2012 and so in theory a recent Android 4.x emulator will work properly on a retina MacBook Pro. Thanks!
Dustin Hyde 2013-08-01

I think this was fixed a long time ago. I remember it eventually went away, and I've never seen it again. I use a retina machine every day.
Chris Barber 2013-08-01

Resolving as not our bug and that we believe it has been fixed.
Lee Morris 2017-03-29

Closing with reference to the above comments.

JSON Source