Develop Reference

Emulator AVD does not scale display to 4k monitor

Since I upgraded my monitor to 4k, I have a problem with the Android emulator. On my system (KDE neon 5.15) the AVD does not scale the display of the device, but only the device itself, as it can be seen here: Display of Android device not scaled. So it's almost impossible for me to click on the right area on the display, as the input field of the touch gestures is also scaled correctly, but only the display itself is not. I already checked similiar problems on stack overflow like 4k display & Android emulator: fail, but non of them seem to have the same problem. Does any one else have experienced a similiar problem on Linux and 4k monitors?

I experienced the same problem with my Windows 10 computer. Here is a solution that works for me:
Switch your screen resolution to 1920 x 1080
Start the android emulator
While the emulator is running, switch your resolution back to 3840 x 2160 and it should be scaled properly
You will have to do this every time you start the emulator.
Once you have it running properly in 4k DO NOT close the emulator because you will have to repeat the above steps.
This worked for me on my Windows 10 machine. I am not sure how it would respond on Linux.

Android Studio Emulator vs real Device screen resolution

today I noticed something wired. I have got an Emulator Device running a resolution of 1440x2560. I was developing most of the time on this Emu Device and today I plugged in my cousins Galaxy S7 Edge, which has the same resolution, but I noticed that there was less screen space LOL I know it sounds stupid, but I know for sure because my Admob Ads weren't showing up anymore, and I saw that they didnt have enough space (width,height) to show up. After changing some width & heights settings inside my code the Ads did show up again, but this had me seriously confused. How could this even be possible? The Emu Device has the exact same screen resolution, the same Android Version (Marshmallow). Why would I have more space inside the emulator and less on a real device? Anyone noticed something familiar?

Android emulator is screen is blank

When I open the android emulator, it stays on a black screen.
The app I'm testing is small and basic.
I have the arm* type downloaded, and I set it to 300 RAM, but still nothing.

Emulator have many issue if you want good & fast emulator then uses genymotion Download from link https://www.genymotion.com/#!/. you will get different type of device and fast devices then emulator.

Why does one of my GenyMotion emulated devices show a black screen?

I have two devices in my GenyMotion application. One is nexus 7 4.2.2 API. The other is a saumsung galaxy s4 4.3 API. The nexus emulator starts up fine and works well. However when I tried starting the s4 emulator, the android loading screen doesn't even show up, all i get is a black screen. When I go to DDMS, the devices tab tells me that the samsung galaxy s4 is online and debuggable. Does anyone know how to fix this issue? It make more sense if both show a black screen but why does one show a black screen and the other doesn't. I don't see anything out of the ordinary in the console.

I just tested this, and notice the blank screen is due to Genymotion version mismatch. Once i downloaded the latest genymotion (v2.3.0) , i was able to see Galaxy S4 startup properly.
If you do not see the navigation bar, you can manually enable it in Configure virtual device, see below.

this worked for me : In Configure Virtual Device (as shown in ashoke's answer) I changed Screen size to one of predefineds resolutions.

Delphi XE5 Android app running slow on Google Nexus 10

We are evaluating Delphi XE5 specifically to see how easy it is to develop mobile apps. We have developed a simple Android app that scrolls through a TClientDataset using a DBNavigator. The application comprises a few input fields, labels and slider controls (TSwitch).
Everything works ok and sliders (animations) are responsive, except on a Google Nexus 10 (Android 4.3) where everything happens in slow motion. It is like the app is still running in emulator mode. (A sliding button takes over 2 seconds to move from left to right!)
We have successfully tested the app on a Samsung Galaxy S3 (Android 4.1.2) and a HTC One (4.2.2) and the UI is as responsive as one would expect.
Update.
We asked the question at Code Rage 8 and they are referring it to the R&D Department. Will update when or if we get an answer.

I see mention of the screen resolution in comments. Has it actually been determined that it is the screen resolution that is the issue here?
Can you go into the developer options on the Nexus and try anything there that forces GPU usage or whatever might potentially help things along graphics-wise?
And is there anything clue-like in logcat? Run monitor.bat in the Android SDK tools directory or, if the path to it has spaces in, then that won't work so run ddms.bat instead from the same location (DDMS doesn't abort due to spaces in the path).
It would be good to get more evidence on the problem, rather than (educated) guesswork.
If it turns out to be screen size, well that will be interesting for Embo.