Fixed
Status Update
No update yet.
Comments
ro...@gmail.com
it does work but the rendered area is 1/4 of the window while the touch area is the full window
ie to press something in the top right of the drawn image, which is half of the window, you click in the top right of the window.
ie to press something in the top right of the drawn image, which is half of the window, you click in the top right of the window.
ro...@gmail.com
if you need a work around then download setresx and set it to 1400x900 WITHOUT HiDPI
You are actually running in that low resolution mode with HiDPI assets.
The retina display thing is a bit of a con really, I am very disappointed with it.
You are actually running in that low resolution mode with HiDPI assets.
The retina display thing is a bit of a con really, I am very disappointed with it.
db...@gmail.com
Thanks for the advice about setresx. I'll take a look at it. However, I'd like to keep the HiDPI and just have the emulator scale like everything else, or have it scale down but have the touch area scale down with it. But for right now it is not usable and I just have to use an actual device to develop with.
da...@yahoo.co.uk
It's a bit of a pain but you can set your res to 1400x900 as suggested above, launch the emulator and then change the resolution to what you'd like to work in. The emulator then works ok (for me at least).
je...@google.com
The problem is due to the QuickDraw-based graphics used in SDL 1.2.12. Those APIs have been deprecated for a long time. At least on the surface, SDL 1.2.15 uses newer APIs that have hopefully been updated to handle Retina scaling.
db...@gmail.com
Is the SDL lib something that ships with the OS or ships with the Android SDK? Do you recommend downloading 1.2.15 and overriding the current library?
je...@google.com
The emulator statically links a modified version of SDL; you can't replace it without forward-porting the Android modifications and rebuilding the emulator. I'm working on that.
Apart from the workarounds mentioned by others, with GPU acceleration enabled the Android display is correctly sized. Any external controls are still shrunk and covered by the Android display though, so that only really works with a soft-controls layout (on-screen keyboard and back/home/menu buttons).
Apart from the workarounds mentioned by others, with GPU acceleration enabled the Android display is correctly sized. Any external controls are still shrunk and covered by the Android display though, so that only really works with a soft-controls layout (on-screen keyboard and back/home/menu buttons).
ca...@gmail.com
I am also experiencing this issue too; it looks like you're right, the code for the Android Emulator is based on very outdated libraries and therefore does not scale correctly. This is a real pain; please let me know if anybody discovers a workaround other than the above.
je...@gmail.com
ghey!
ya...@gmail.com
yeah, seriously sucks! come on goog. get with the times!
ph...@bayfmail.com
Is there any ETA on a fix for this?
ca...@gmail.com
Just to say - for anyone looking for more workarounds. This is hardly a great one, but it does work although requires external display(s): hook up your external displays and run your Macbook in clamshell mode. (i.e. lid closed) Eclipse and the emulator will display as normal.
[Deleted User] <[Deleted User]>
I'm using SetResX (http://www.sendspace.com/file/mef6sk ) to change my resolution to 1680x1050. When I do this, the emulator starts up normally. It's working well for me.
je...@google.com
I just switched AOSP to use SDL 1.2.15 which does fix the MBP-Retina problems. This will likely be in the next SDK-tools release.
ya...@gmail.com
That's awesome thanks a lot! What kind of time frame do you think that'll be in? Is this something I could pull from main and build myself?
to...@gmail.com
I have had success running this on a second monitor, but that's only useful in the office. If I'm coding on the go, the emulator is almost worthless due to this defect.
ta...@gmail.com
I'll appreciate your sharing the ETA of this fix and how we can obtain it.
Many thanks,
Many thanks,
mi...@gmail.com
I have the same problems, also worked out connecting a second monitor, but when I move the AVD to the retina display it crashes.
ba...@gmail.com
I also have seen that sometimes only the emulator screen areas is shown and not the keyboard (that used to be shown on the right side of screen)
[Deleted User] <[Deleted User]>
Same issue here.
Really sucks to develop on the MPB Retina with this behaviour.
Really sucks to develop on the MPB Retina with this behaviour.
tr...@gmail.com
Another workaround is to use "Retina DisplayMenu" (http://www.reddit.com/r/apple/comments/vi9yf/set_your_retina_macbook_pros_resolution_to/ ), which adds a display menu to your menu bar so you can change resolutions manually. I didn't write it, but it works for me..use it at your risk.
It's the "HiDPI" resolutions that the android emulator has a problem with. So I usually start RDM, choose the non-HiDPI version of my current resolution, start the android emulator, and then switch back to my original HiDPI resolution. The emulator seems to work correctly with HiDPI after it's already running.
It's the "HiDPI" resolutions that the android emulator has a problem with. So I usually start RDM, choose the non-HiDPI version of my current resolution, start the android emulator, and then switch back to my original HiDPI resolution. The emulator seems to work correctly with HiDPI after it's already running.
je...@google.com
Retina support should be fixed in SDK Tools 21. The first preview release, which includes the fix, is available at http://tools.android.com/download/adt-21-preview .
js...@gmail.com
Thank you so much! I've been trying to figure out a fix to this forever.
ta...@gmail.com
Thanks so much! The SDK/ADT 21 seems having fixed the issue.
js...@gmail.com
i still get this error even after installing SDK/ADT 21:
emulator-arm[406:f07] Warning once: This application, or a library it uses, is using NSQuickDrawView, which has been deprecated. Apps should cease use of QuickDraw and move to Quartz.
emulator-arm[406] <Error>: The function `CGSFlushWindow' is obsolete and will be removed in an upcoming update. Unfortunately, this application, or a library it uses, is using this obsolete function, and is thereby contributing to an overall degradation of system performance. Please use `CGSFlushWindowContentRegion' instead.
It says that NSQuickDrawView and CGSFlushWindow are not to be used. Hopefully this is fixed in the SDK/ADT 21 release???
emulator-arm[406:f07] Warning once: This application, or a library it uses, is using NSQuickDrawView, which has been deprecated. Apps should cease use of QuickDraw and move to Quartz.
emulator-arm[406] <Error>: The function `CGSFlushWindow' is obsolete and will be removed in an upcoming update. Unfortunately, this application, or a library it uses, is using this obsolete function, and is thereby contributing to an overall degradation of system performance. Please use `CGSFlushWindowContentRegion' instead.
It says that NSQuickDrawView and CGSFlushWindow are not to be used. Hopefully this is fixed in the SDK/ADT 21 release???
ji...@gmail.com
Installing preview tool (21) work perfectly for me !! Thanks !!
sh...@gmail.com
Well I installed 21 to try and get the emulator working but I still see it at a quarter size.
For the people that say 21 fixes this, did you do anything else?
I'm still running Lion, not Mountain Lion if this helps.
For the people that say 21 fixes this, did you do anything else?
I'm still running Lion, not Mountain Lion if this helps.
sh...@gmail.com
[Comment deleted]
ev...@gmail.com
ADT 21 doesn't fix the problems with the emulator on MacBook Retina. Any ideas what to do to fix this new weird issue?
ph...@bayfmail.com
Are you sure you followed all the steps to correctly install the preview?
It works for me just fine.
It works for me just fine.
mi...@gmail.com
[Comment deleted]
dr...@gmail.com
[Comment deleted]
mi...@gmail.com
I managed to download ADT21, don't miss to set the "Enable Preview Tools" flag (http://tools.android.com/preview-channel ).
The emulator shows up correctly on my Retina Mac Pro, but D-Pad and Keyboard are missing.
If you need a D-Pad, do the following:
Before you set up a new AVD using ADT21, click "devices" on the top menu bar.
Create a custom device and you can enable d-pad and keyboard controls (using your computer keyboard).
If you need to test Google TV (w/o using Linux) and live in Germany, go to the Sony Web pagehttp://www.sony.de/hub/google-tv and order a "NSZ-GS7 Internet Player".
I got mine yesterday and it works perfectly to test your app before releasing it also for Google TV.
The emulator shows up correctly on my Retina Mac Pro, but D-Pad and Keyboard are missing.
If you need a D-Pad, do the following:
Before you set up a new AVD using ADT21, click "devices" on the top menu bar.
Create a custom device and you can enable d-pad and keyboard controls (using your computer keyboard).
If you need to test Google TV (w/o using Linux) and live in Germany, go to the Sony Web page
I got mine yesterday and it works perfectly to test your app before releasing it also for Google TV.
jo...@gmail.com
"I managed to download ADT21, don't miss to set the "Enable Preview Tools" flag (http://tools.android.com/preview-channel ).
The emulator shows up correctly on my Retina Mac Pro, but D-Pad and Keyboard are missing."
Works a treat - well done MichB!
The emulator shows up correctly on my Retina Mac Pro, but D-Pad and Keyboard are missing."
Works a treat - well done MichB!
ja...@gmail.com
I see that this was fixed in ADT21.
Can I use this fix without Eclipse?
Can I use this fix without Eclipse?
ni...@gmail.com
Note for Mac users: The "Enable Preview Tools" is located in Preferences, not in the Tools tab (as shown on the preview-channel site).
It took me longer than it should have to figure this out.
It took me longer than it should have to figure this out.
fa...@gmail.com
I have the same problem....
thanks :)
thanks :)
al...@gmail.com
Thanks! Enabled and downloaded preview tools -- everything works again!
[[ MBP Retina using 1920x1400 resolution ]]
To expand comment 26... This is exactly what I did.
From Eclipse, start the Android SDK Manager
From the top menu of the Android SDK Manager, choose Tools > Options
Check "Enable Preview Tools"
In the Android SDK Manager, I uninstalled the Android SDK Tools and Android SDK Platform Tools at the top, and re-installed the same from the Preview Channel directly below.
Close that, Back into Eclipse, Help > Check for Updates (just in case)
Start the AVM, start your virtual device
[[ MBP Retina using 1920x1400 resolution ]]
To expand comment 26... This is exactly what I did.
From Eclipse, start the Android SDK Manager
From the top menu of the Android SDK Manager, choose Tools > Options
Check "Enable Preview Tools"
In the Android SDK Manager, I uninstalled the Android SDK Tools and Android SDK Platform Tools at the top, and re-installed the same from the Preview Channel directly below.
Close that, Back into Eclipse, Help > Check for Updates (just in case)
Start the AVM, start your virtual device
ni...@gmail.com
Same issue I'm seeing as
I installed the Preview tools and ENABLED GPU Emulation.
Without GPU emulation the emulator seems to work okay with the latest tools. However, the GPU emulation causes the same problem with the inverted status bar.
I installed the Preview tools and ENABLED GPU Emulation.
Without GPU emulation the emulator seems to work okay with the latest tools. However, the GPU emulation causes the same problem with the inverted status bar.
t....@gmail.com
Hi everyone,
I'm new to Android development and recently tried transferring my project over to the new macbook pro retina display.
I was experiencing the same problem as everyone with the quarter screen. However after I tried installing ADT21 and restarting Eclipse i see the below error message. Eclipse can't find the SDK manager nor the SDK after the restart.
I've attached the screen shot below.
Appreciate any help!
I'm new to Android development and recently tried transferring my project over to the new macbook pro retina display.
I was experiencing the same problem as everyone with the quarter screen. However after I tried installing ADT21 and restarting Eclipse i see the below error message. Eclipse can't find the SDK manager nor the SDK after the restart.
I've attached the screen shot below.
Appreciate any help!
mi...@gmail.com
Hello t.shaom...@gmail.com ,
Folow the instructions on this link to solve your problem.
http://tools.android.com/preview-channel
Folow the instructions on this link to solve your problem.
sa...@gmail.com
This was apparently never fixed. Android SDK Platform-tools 23.0.1 and 23.1rc (as of 2015-11-17) still do not render correctly on Retina. My new 221dpi MBP 15" behaves as if it were a 1440x900 monitor out of the box, and the android emulator is rendering at that resolution, so I get a blocky emulated device at 110.5dpi instead of a smooth one. Can anyone follow up with a correct workaround, or some link to what happened to the work to port to the new SDL version?
Description
while developing Android applications (Emulator, DDMS, Eclipse support,
ant scripts...). Use the Developer templates for issues with Android
itself.
Please describe the problem in detail, with the following information (if
applicable)
Host OS: Mac OSX Lion 10.7.4
SDK tools version (available in the "About" section of the 'android' tool
UI): Revision 19
Eclipse version: Eclipse Indigo Version: Indigo Service Release 2 Build id: 20120216-1857
ADT plug-in version: 18.0.0.v201203301601-30676
Platform targeted by your project: 2.1
Version of the platform running in the emulator: 2.1
STEPS TO REPRODUCE:
1. New... Project... Android Project... Create from existing sample... 2.1... Notepad
2. Launch Notepad and emulator-arm loads but is 1/4 the size inside the window
EXPECTED RESULTS:
Emulator loads regular size and can interact with it
OBSERVED RESULTS:
Emulator loads 1/4 size in upper left hand corner of window and you cannot interact with it. I don't mind that it is 1/4 size. I just need to be able to interact with it. This is only a problem on the Retina MBP. All the same stuff works fine on my Macbook Air.
ADDITIONAL INFORMATION:
Attach sample project, etc.
If possible, try to reproduce using ApiDemos.
If the problem is happening in the emulator, consider attaching the output
of "adb bugreport"