3

Just started with Android Studio. The problem is that my emulator contents (not the emulator window itself) show too big. Following is a snapshot:

enter image description here

So my question is different than this post where the problem seems to be that the emulator window itself is larger than the screen. Also I tried following steps given in this post, but that doesn't help much. Anyone can help me with this?

Note: I have already downloaded the skin from vendor's website and supplied correct physical screen size and resolution in the config files.

Zoe
  • 27,060
  • 21
  • 118
  • 148
dotNET
  • 33,414
  • 24
  • 162
  • 251
  • Does this happen with every new emulator you create? – Shami Dec 14 '14 at 18:53
  • @Ethan: I tried creating the same emulator twice (I have the same physical phone with me, so I was trying to get it running in the emulator too), and it happened on both occasions. The built-in device profiles (such as Nexus 4) however seem to run just normal size. – dotNET Dec 14 '14 at 18:56
  • Hope this will solve your problem http://stackoverflow.com/questions/7777475/the-window-of-the-emulator-is-too-big-than-a-mobile-screen – Shami Dec 14 '14 at 18:57
  • @Ethan: I do not see the options mentioned in that post. They are probably working with Eclipse, not Android Studio. – dotNET Dec 14 '14 at 19:02
  • @dotNET What is the density shown in the AVD's "Resolution" column? – matiash Dec 14 '14 at 22:10
  • @matiash: `320 x 480: mdpi`, which is exactly what the physical dimensions of my phone are. BTW AVD doesn't allow me to set that `mdpi` to any other value. Out of curiosity, I created a duplicate profile and manually edited it to `hdpi`, but even that profile doesn't look any better. – dotNET Dec 15 '14 at 04:13
  • Did you find a solution to this? I updated my Android Studio and the emulator looks like it's doing something similar. – OldTinfoil Jun 15 '16 at 13:36
  • @IntrepidBrit: No. Has been a long time since then. Don't even remember where did I end up with this. – dotNET Jun 15 '16 at 15:17
  • I just ended up doing a completely fresh install. Not a great solution, but at least I can carry on. – OldTinfoil Jun 16 '16 at 09:14

1 Answers1

1

I had similar problem. I was trying to create Nexus 6P device with the following command

avdmanager create avd -n nexus6p -k "system-images;android-25;google_apis;x86" -b x86 -c 1000M -d 11

Later I read somewhere, there are issues with resolution compatibility of your computer and the device you intend to create. Nexus 6P (in my case, it has id of 11; you can check them with avdmanager list device command) is a very high resolution display device. I issued following command

avdmanager create avd -n nexus6p -k "system-images;android-25;google_apis;x86" -b x86 -c 1000M -f

without specifying any specific device. It asked if I wished to create a custom hardware profile with default answer being no. I simply pressed enter so that it created a standard hardware profile. The resulting avd did not have this problem. I emulated the device with following command

./emulator -avd nexus6p -gpu off -qemu -m 2047 -enable-kvm

In my case, switching off gpu was necessary to prevent crashing of the emulated device.

srinivasu u
  • 1,393
  • 11
  • 12