Android emulator screen fills up only some fraction part of actual android emulator screen
First thing first,
Using Android Studio 2.3.3
Problem:
My emulator screen is covering the only partial amount of screen available for emulator, i.e top left of the emulator and rest part is just a black screen.
See the pic I have attached.
Things I tried:
1) Restarting emulator
2) trying different emulator
3) changing pixels, density of emulator device,
4) run -> edit configuration ..blah blah blah...
Nothing helped!!
Note:
My issue is not emulator's size but effective screen size.
please help if somebody could have come across this issue :(
IMPORTANT EDIT: I guess, this issue has something to do with the laptop I am using, DELL Latitude, touch screen (14-inch QHD touch display (2,560×1,440 resolution).
Because the same emulator works properly in other display laptops.
android 
android-studio android-emulator edited Aug 10 '17 at 8:14
Harsh
14016
asked Aug 1 '17 at 10:24
eRaisedToXeRaisedToX
1,5221125
add a comment |
First thing first,
Using Android Studio 2.3.3
Problem:
My emulator screen is covering the only partial amount of screen available for emulator, i.e top left of the emulator and rest part is just a black screen.
See the pic I have attached.
Things I tried:
1) Restarting emulator
2) trying different emulator
3) changing pixels, density of emulator device,
4) run -> edit configuration ..blah blah blah...
Nothing helped!!
Note:
My issue is not emulator's size but effective screen size.
please help if somebody could have come across this issue :(
IMPORTANT EDIT: I guess, this issue has something to do with the laptop I am using, DELL Latitude, touch screen (14-inch QHD touch display (2,560×1,440 resolution).
Because the same emulator works properly in other display laptops.
android android-studio android-emulator edited Aug 10 '17 at 8:14
Harsh
14016
asked Aug 1 '17 at 10:24
eRaisedToXeRaisedToX
1,5221125
check this stackoverflow.com/questions/29737499/…
– Salman500
Aug 1 '17 at 10:29
I saw that...didn't help , I don't see any emulator tab in run->edit configuration
– eRaisedToX
Aug 1 '17 at 10:30
rotate screen from given rotation function in menu bar .
– Kevan Aghera
Aug 3 '17 at 11:21
@kevanaghera , "rotate" ???? No man !! that has nothing to do with it. I had tried all basic stuff.
– eRaisedToX
Aug 3 '17 at 13:33
It happen a few times to me and closing and re-opening the emulator fixed the problem. It usually happend when I closed my laptop lid without putting it to sleep first. I know that restarting it didn't fixed your problem, but maybe you can find a similar pattern.
– Iulian Popescu
Aug 11 '17 at 11:09
add a comment |
First thing first,
Using Android Studio 2.3.3
Problem:
My emulator screen is covering the only partial amount of screen available for emulator, i.e top left of the emulator and rest part is just a black screen.
See the pic I have attached.
Things I tried:
1) Restarting emulator
2) trying different emulator
3) changing pixels, density of emulator device,
4) run -> edit configuration ..blah blah blah...
Nothing helped!!
Note:
My issue is not emulator's size but effective screen size.
please help if somebody could have come across this issue :(
IMPORTANT EDIT: I guess, this issue has something to do with the laptop I am using, DELL Latitude, touch screen (14-inch QHD touch display (2,560×1,440 resolution).
Because the same emulator works properly in other display laptops.
android android-studio android-emulator edited Aug 10 '17 at 8:14
Harsh
14016
asked Aug 1 '17 at 10:24
eRaisedToXeRaisedToX
1,5221125
First thing first,
Using Android Studio 2.3.3
Problem:
My emulator screen is covering the only partial amount of screen available for emulator, i.e top left of the emulator and rest part is just a black screen.
See the pic I have attached.
Things I tried:
1) Restarting emulator
2) trying different emulator
3) changing pixels, density of emulator device,
4) run -> edit configuration ..blah blah blah...
Nothing helped!!
Note:
My issue is not emulator's size but effective screen size.
please help if somebody could have come across this issue :(
IMPORTANT EDIT: I guess, this issue has something to do with the laptop I am using, DELL Latitude, touch screen (14-inch QHD touch display (2,560×1,440 resolution).
Because the same emulator works properly in other display laptops.
android android-studio android-emulator android android-studio android-emulator edited Aug 10 '17 at 8:14
Harsh
14016
asked Aug 1 '17 at 10:24
eRaisedToXeRaisedToX
1,5221125
edited Aug 10 '17 at 8:14
Harsh
14016
asked Aug 1 '17 at 10:24
eRaisedToXeRaisedToX
1,5221125
edited Aug 10 '17 at 8:14
Harsh
14016
edited Aug 10 '17 at 8:14
Harsh
14016
edited Aug 10 '17 at 8:14
Harsh
14016
14016
asked Aug 1 '17 at 10:24
eRaisedToXeRaisedToX
1,5221125
asked Aug 1 '17 at 10:24
eRaisedToXeRaisedToX
1,5221125
asked Aug 1 '17 at 10:24
eRaisedToXeRaisedToX
1,5221125
1,5221125
check this stackoverflow.com/questions/29737499/…
– Salman500
Aug 1 '17 at 10:29
I saw that...didn't help , I don't see any emulator tab in run->edit configuration
– eRaisedToX
Aug 1 '17 at 10:30
rotate screen from given rotation function in menu bar .
– Kevan Aghera
Aug 3 '17 at 11:21
@kevanaghera , "rotate" ???? No man !! that has nothing to do with it. I had tried all basic stuff.
– eRaisedToX
Aug 3 '17 at 13:33
It happen a few times to me and closing and re-opening the emulator fixed the problem. It usually happend when I closed my laptop lid without putting it to sleep first. I know that restarting it didn't fixed your problem, but maybe you can find a similar pattern.
– Iulian Popescu
Aug 11 '17 at 11:09
add a comment |
check this stackoverflow.com/questions/29737499/…
– Salman500
Aug 1 '17 at 10:29
I saw that...didn't help , I don't see any emulator tab in run->edit configuration
– eRaisedToX
Aug 1 '17 at 10:30
rotate screen from given rotation function in menu bar .
– Kevan Aghera
Aug 3 '17 at 11:21
@kevanaghera , "rotate" ???? No man !! that has nothing to do with it. I had tried all basic stuff.
– eRaisedToX
Aug 3 '17 at 13:33
It happen a few times to me and closing and re-opening the emulator fixed the problem. It usually happend when I closed my laptop lid without putting it to sleep first. I know that restarting it didn't fixed your problem, but maybe you can find a similar pattern.
– Iulian Popescu
Aug 11 '17 at 11:09
check this stackoverflow.com/questions/29737499/…
– Salman500
Aug 1 '17 at 10:29
check this stackoverflow.com/questions/29737499/…
– Salman500
Aug 1 '17 at 10:29
I saw that...didn't help , I don't see any emulator tab in run->edit configuration
– eRaisedToX
Aug 1 '17 at 10:30
I saw that...didn't help , I don't see any emulator tab in run->edit configuration
– eRaisedToX
Aug 1 '17 at 10:30
rotate screen from given rotation function in menu bar .
– Kevan Aghera
Aug 3 '17 at 11:21
rotate screen from given rotation function in menu bar .
– Kevan Aghera
Aug 3 '17 at 11:21
@kevanaghera , "rotate" ???? No man !! that has nothing to do with it. I had tried all basic stuff.
– eRaisedToX
Aug 3 '17 at 13:33
@kevanaghera , "rotate" ???? No man !! that has nothing to do with it. I had tried all basic stuff.
– eRaisedToX
Aug 3 '17 at 13:33
It happen a few times to me and closing and re-opening the emulator fixed the problem. It usually happend when I closed my laptop lid without putting it to sleep first. I know that restarting it didn't fixed your problem, but maybe you can find a similar pattern.
– Iulian Popescu
Aug 11 '17 at 11:09
It happen a few times to me and closing and re-opening the emulator fixed the problem. It usually happend when I closed my laptop lid without putting it to sleep first. I know that restarting it didn't fixed your problem, but maybe you can find a similar pattern.
– Iulian Popescu
Aug 11 '17 at 11:09
add a comment |
12 Answers
12
active
oldest
votes
I was having the same problem too. I think it started happening when I updated to Android Studio 3.0 Beta 1, but I'm not 100% sure of that.
FIX:
Anyway, to fix this, you can use Software Graphics in the emulator options, rather than Hardware. Slower, but at least it works.
edited Aug 13 '17 at 4:48
eRaisedToX
1,5221125
answered Aug 11 '17 at 4:27
Knuckles the EchidnaKnuckles the Echidna
85811321
hi, yeah it worked that way ,so +1, but it is too slow.... any other work around? I mean it is that slow that one can't use it , so the core problem remains the same that I am forced to use real device. (earlier , because it was too small and now because it is too slow). I am using studio 2.3.3 , should I change that?
– eRaisedToX
Aug 11 '17 at 5:12
Unfortunately I haven't found any other way to fix this. I also have a Dell laptop btw, just not the same model (I have a Mobile Precision 5520). I guess we'll have to wait till they fix this, because I'm positive this started happening recently. I don't think this is a matter of Android Studio, since we're using different version, so maybe it's another update to a different component that they introduced which you and I happened to download.
– Knuckles the Echidna
Aug 11 '17 at 20:16
Your's is the closest answer , so I accept it, but since the bounty has expired and given to some other answer by community , I cant give you that. thanks!
– eRaisedToX
Aug 13 '17 at 4:16
1
No, no this can't be a solution, it's incredibly slow!!
– Gamal Mohamed
Apr 21 '18 at 12:50
add a comment |
I am running Archlinux and I had exactly the same problem because I have $QT_SCALE_FACTOR set to 2 by default. Setting it back to 1 for the emulator fixed the problem:
env QT_SCALE_FACTOR=1 Android/Sdk/emulator/emulator -avd api25
answered May 27 '18 at 6:30
dvimdvim
1,39811016
Changing this settings works, but for me correct value was 0.667. So better way would be playing with it to check which value is good for your environment.
– Konstantin Labun
Jul 9 '18 at 6:03
2
For people using Android Studio find your installation folder and addexport QT_SCALE_FACTOR=1to yourstudio.shsomewhere in the beginning. Note that in KDE that factor must be1 / <display scale>. E.g0.5when you scaled your display by 2.
– Machisuji
Sep 17 '18 at 22:01
add a comment |
Try this and hopefully it works for you -
Go to
Toolsin Android Studio and openAVD ManagerIt will open all your virtual devices. Click on the Virtual device you want to edit and click the Pencil icon which will enable you to edit the device.
Click on
Changewhere it lists the device name. For example, for me my device name is Nexus 5X and lists the resolution of the device.In the Select a Device screen, click on
New Hardware Profileand change the resolution to 1080 x 1920 px.- Save the changes and run it again. If it still doesn't work, change the skin of the device.
- If still doesn't work, then make a new hardware profile with a new device.
answered Aug 3 '17 at 15:40
Ankit SharmaAnkit Sharma
409414
If you look at the question, I had asked it 2 days back and since then I have tried all these basic stuff which everyone knows ..! So , Unluckily , I have tried all those so called "still" from your answer . and you know what it "still" does not work.. Believe me, bounty awarded to the question (by me) is worth it.
– eRaisedToX
Aug 3 '17 at 17:14
add a comment |
I have this similar issue. It happened after using an external monitor that has lower resolution (1440 x 900) than my laptop (2160 x 1440) has. There are couple of ways you can fix it until Google fix the issue.
- if you match your PC's resolution to your external monitor's resolution. Then you can return back to your PC's resolution.
- If you lower the scaling of your PC ( mine was 150% > 125% or 100%) from Display Settings. Run the emulator. Again, you can return back to your original scaling, emulator screen won't change. This is the one I prefer.
Note: this is not a permanent solution. You may need to change scaling/resolution again if you change your scaling or resolution to the one you had issue with. I have tested this only on Windows 10 Pro, but this approach might work on Mac as well.
answered Nov 10 '17 at 22:35
BenazirBenazir
314
Worked for me! but it's still a hack, hopefully we find a real solution for this..
– Gamal Mohamed
Apr 21 '18 at 12:50
add a comment |
Open the Emulator and press Ctrl+Up_Key to increase the scale and Ctrl+Down_Key to scale down. (Cmd+KUp / Cmd+KDown if you are on mac)
answered Aug 3 '17 at 11:24
aaron0207aaron0207
1,2851516
I dont know what do you mean by "Right Click the Project Folder"... What I have tried is --- Run ->Edit Configuration->target select as emulator,,, but then there is NO option for scale and all.. can you post some screen shots
– eRaisedToX
Aug 3 '17 at 13:52
Try my updated answer
– aaron0207
Aug 4 '17 at 6:35
yeah bro..I tried...all those..that increases the size of device plus the screen but ratio remains same (screen covering only 30% of device)No clue what's wrong...!
– eRaisedToX
Aug 4 '17 at 7:53
Worked for me for Nexus 4 simulator, on 15.6 inch mac.
– Martin Berger
2 days ago
add a comment |
Have you already tried other emulator? I suggest Try bluestacks
go the tab Emulator (next to the General tab), and in Additional command line options, write
-scale 100.X
Press alt + space + M
Pls. see landscape also and revert back to portrait
answered Aug 10 '17 at 6:49
user8256287user8256287
14111
1
Which Emulator Tab you are talking about , If I go to Run -> Edit Configuration I see some tabs , but no emulator tab .. pls post screen shot if you can.
– eRaisedToX
Aug 10 '17 at 8:48
add a comment |
This looks like an incompatibility with windows scaling.
Try setting scale to 100% in display settings of Windows (right click on desktop).
answered Aug 10 '17 at 11:57
Rishabh KohliRishabh Kohli
737
Worked for me! but it's still a hack, hopefully we find a real solution for this..
– Gamal Mohamed
Apr 21 '18 at 12:49
add a comment |
*Software rendering is very slow to be usable
Better Fix
You can fix the scaling issue when using the Hardware rendering by simply making windows override the scaling setting. How?, it's very easy.
Simply locate the .exe file for the emulator that you are using, (e.g. "qemu-system-armel.exe" for ARM and "qemu-system-x86_64.exe" for x86).
To make sure which .exe file, just run the emulator then use task manager to locate the .exe file is running, see the screenshot.
locate the .exe file using task manager
In my case it was in this location:
"C:Users[Username]AppDataLocalAndroidSdkemulatorqemuwindows-x86_64qemu-system-x86_64.exe"
Now just right click on the file then click on properties then choose the "Compatibility" tab. Under "Settings" at the bottom, click on "Change high DPI settings".
A new window will open. Tick the last checkbox "Override high DPI scaling behavior." under "High DPI scaling override".
Then select from the drop down below it "System" (this is very important or it will not make any difference!), see the screenshot below. Now just hit OK and OK. And that's it, problem solved :)
override scaling settings for the .exe file
answered Jun 25 '18 at 18:50
WaelWael
111
Thanks! This worked for me, required restarting android studio
– grantka
Jul 8 '18 at 17:40
add a comment |
I ran into this issue a while ago and have been struggling for it until now.
Solution seems to be:
Go to C:UsersYourUserAppDataLocalAndroidSdkemulator
Here, right click on emulator.exe, click Properties and go to Compatibility. Here, check: "Override high DPI scaling behavior. Scaling performed by: APPLICATION".
This should fix the issue on any Windows 10 machine with display scaling activated.
answered Apr 30 '18 at 10:58
akseliakseli
249110
add a comment |
In case someone ran into this issue on Linux, here is a fix:
QT_AUTO_SCREEN_SCALE_FACTOR=0 emulator -avd <Name of your virtual device>
answered Aug 29 '18 at 11:09
qedqed
9,7491266116
add a comment |
Just go to display setting and change it to 100%.this normally happens if you have a fourteen inch laptop and below
answered Nov 11 '18 at 13:11
tarustarus
11
add a comment |
On Windows with high resolution screens I have to change the "high DPI setting" from application to system.
- Close Android Studio If it's open
- Right Click Android studio icon on desktop
- Select properties--> Compatibility
- Click "Change high DPI setting"
- Under "High DPI scaling override" section from the drop down list select System
- Click OK on both screens.
However, if you want to just run the emulator using PowerShell on windows by running "emulator '@your_device_name'" command, you would still have the same issue. to fix this issue you basically need to Right click the emulator you want to run and follow the steps from 3 to 6.
The default path for the emulators on windows is:
C:UsersREPLACE_IT_WITH_YOURSAppDataLocalAndroidsdkemulatorqemuwindows-x86_64
Alternatively to open the emulator's properties:
1. Run android studio
2. Select Tools and then AVD Manager
3. Run the emulator you want to use
4. Right click emulator on the task bar
5. Right click *.exe and choose properties
6. Follow the steps from 3 to 6 to change "high DPI setting"
answered Nov 2 '18 at 0:23
Alireza BayatAlireza Bayat
11
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f45435272%2fandroid-emulator-screen-fills-up-only-some-fraction-part-of-actual-android-emula%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
12 Answers
12
active
oldest
votes
12 Answers
12
active
oldest
votes
active
oldest
votes
active
oldest
votes
I was having the same problem too. I think it started happening when I updated to Android Studio 3.0 Beta 1, but I'm not 100% sure of that.
FIX:
Anyway, to fix this, you can use Software Graphics in the emulator options, rather than Hardware. Slower, but at least it works.
edited Aug 13 '17 at 4:48
eRaisedToX
1,5221125
answered Aug 11 '17 at 4:27
Knuckles the EchidnaKnuckles the Echidna
85811321
hi, yeah it worked that way ,so +1, but it is too slow.... any other work around? I mean it is that slow that one can't use it , so the core problem remains the same that I am forced to use real device. (earlier , because it was too small and now because it is too slow). I am using studio 2.3.3 , should I change that?
– eRaisedToX
Aug 11 '17 at 5:12
Unfortunately I haven't found any other way to fix this. I also have a Dell laptop btw, just not the same model (I have a Mobile Precision 5520). I guess we'll have to wait till they fix this, because I'm positive this started happening recently. I don't think this is a matter of Android Studio, since we're using different version, so maybe it's another update to a different component that they introduced which you and I happened to download.
– Knuckles the Echidna
Aug 11 '17 at 20:16
Your's is the closest answer , so I accept it, but since the bounty has expired and given to some other answer by community , I cant give you that. thanks!
– eRaisedToX
Aug 13 '17 at 4:16
1
No, no this can't be a solution, it's incredibly slow!!
– Gamal Mohamed
Apr 21 '18 at 12:50
add a comment |
I was having the same problem too. I think it started happening when I updated to Android Studio 3.0 Beta 1, but I'm not 100% sure of that.
FIX:
Anyway, to fix this, you can use Software Graphics in the emulator options, rather than Hardware. Slower, but at least it works.
edited Aug 13 '17 at 4:48
eRaisedToX
1,5221125
answered Aug 11 '17 at 4:27
Knuckles the EchidnaKnuckles the Echidna
85811321
hi, yeah it worked that way ,so +1, but it is too slow.... any other work around? I mean it is that slow that one can't use it , so the core problem remains the same that I am forced to use real device. (earlier , because it was too small and now because it is too slow). I am using studio 2.3.3 , should I change that?
– eRaisedToX
Aug 11 '17 at 5:12
Unfortunately I haven't found any other way to fix this. I also have a Dell laptop btw, just not the same model (I have a Mobile Precision 5520). I guess we'll have to wait till they fix this, because I'm positive this started happening recently. I don't think this is a matter of Android Studio, since we're using different version, so maybe it's another update to a different component that they introduced which you and I happened to download.
– Knuckles the Echidna
Aug 11 '17 at 20:16
Your's is the closest answer , so I accept it, but since the bounty has expired and given to some other answer by community , I cant give you that. thanks!
– eRaisedToX
Aug 13 '17 at 4:16
1
No, no this can't be a solution, it's incredibly slow!!
– Gamal Mohamed
Apr 21 '18 at 12:50
add a comment |
I was having the same problem too. I think it started happening when I updated to Android Studio 3.0 Beta 1, but I'm not 100% sure of that.
FIX:
Anyway, to fix this, you can use Software Graphics in the emulator options, rather than Hardware. Slower, but at least it works.
edited Aug 13 '17 at 4:48
eRaisedToX
1,5221125
answered Aug 11 '17 at 4:27
Knuckles the EchidnaKnuckles the Echidna
85811321
I was having the same problem too. I think it started happening when I updated to Android Studio 3.0 Beta 1, but I'm not 100% sure of that.
FIX:
Anyway, to fix this, you can use Software Graphics in the emulator options, rather than Hardware. Slower, but at least it works.
edited Aug 13 '17 at 4:48
eRaisedToX
1,5221125
answered Aug 11 '17 at 4:27
Knuckles the EchidnaKnuckles the Echidna
85811321
edited Aug 13 '17 at 4:48
eRaisedToX
1,5221125
edited Aug 13 '17 at 4:48
eRaisedToX
1,5221125
edited Aug 13 '17 at 4:48
eRaisedToX
1,5221125
1,5221125
answered Aug 11 '17 at 4:27
Knuckles the EchidnaKnuckles the Echidna
85811321
answered Aug 11 '17 at 4:27
Knuckles the EchidnaKnuckles the Echidna
85811321
answered Aug 11 '17 at 4:27
Knuckles the EchidnaKnuckles the Echidna
85811321
85811321
hi, yeah it worked that way ,so +1, but it is too slow.... any other work around? I mean it is that slow that one can't use it , so the core problem remains the same that I am forced to use real device. (earlier , because it was too small and now because it is too slow). I am using studio 2.3.3 , should I change that?
– eRaisedToX
Aug 11 '17 at 5:12
Unfortunately I haven't found any other way to fix this. I also have a Dell laptop btw, just not the same model (I have a Mobile Precision 5520). I guess we'll have to wait till they fix this, because I'm positive this started happening recently. I don't think this is a matter of Android Studio, since we're using different version, so maybe it's another update to a different component that they introduced which you and I happened to download.
– Knuckles the Echidna
Aug 11 '17 at 20:16
Your's is the closest answer , so I accept it, but since the bounty has expired and given to some other answer by community , I cant give you that. thanks!
– eRaisedToX
Aug 13 '17 at 4:16
1
No, no this can't be a solution, it's incredibly slow!!
– Gamal Mohamed
Apr 21 '18 at 12:50
add a comment |
hi, yeah it worked that way ,so +1, but it is too slow.... any other work around? I mean it is that slow that one can't use it , so the core problem remains the same that I am forced to use real device. (earlier , because it was too small and now because it is too slow). I am using studio 2.3.3 , should I change that?
– eRaisedToX
Aug 11 '17 at 5:12
Unfortunately I haven't found any other way to fix this. I also have a Dell laptop btw, just not the same model (I have a Mobile Precision 5520). I guess we'll have to wait till they fix this, because I'm positive this started happening recently. I don't think this is a matter of Android Studio, since we're using different version, so maybe it's another update to a different component that they introduced which you and I happened to download.
– Knuckles the Echidna
Aug 11 '17 at 20:16
Your's is the closest answer , so I accept it, but since the bounty has expired and given to some other answer by community , I cant give you that. thanks!
– eRaisedToX
Aug 13 '17 at 4:16
1
No, no this can't be a solution, it's incredibly slow!!
– Gamal Mohamed
Apr 21 '18 at 12:50
hi, yeah it worked that way ,so +1, but it is too slow.... any other work around? I mean it is that slow that one can't use it , so the core problem remains the same that I am forced to use real device. (earlier , because it was too small and now because it is too slow). I am using studio 2.3.3 , should I change that?
– eRaisedToX
Aug 11 '17 at 5:12
hi, yeah it worked that way ,so +1, but it is too slow.... any other work around? I mean it is that slow that one can't use it , so the core problem remains the same that I am forced to use real device. (earlier , because it was too small and now because it is too slow). I am using studio 2.3.3 , should I change that?
– eRaisedToX
Aug 11 '17 at 5:12
Unfortunately I haven't found any other way to fix this. I also have a Dell laptop btw, just not the same model (I have a Mobile Precision 5520). I guess we'll have to wait till they fix this, because I'm positive this started happening recently. I don't think this is a matter of Android Studio, since we're using different version, so maybe it's another update to a different component that they introduced which you and I happened to download.
– Knuckles the Echidna
Aug 11 '17 at 20:16
Unfortunately I haven't found any other way to fix this. I also have a Dell laptop btw, just not the same model (I have a Mobile Precision 5520). I guess we'll have to wait till they fix this, because I'm positive this started happening recently. I don't think this is a matter of Android Studio, since we're using different version, so maybe it's another update to a different component that they introduced which you and I happened to download.
– Knuckles the Echidna
Aug 11 '17 at 20:16
Your's is the closest answer , so I accept it, but since the bounty has expired and given to some other answer by community , I cant give you that. thanks!
– eRaisedToX
Aug 13 '17 at 4:16
Your's is the closest answer , so I accept it, but since the bounty has expired and given to some other answer by community , I cant give you that. thanks!
– eRaisedToX
Aug 13 '17 at 4:16
1
1
No, no this can't be a solution, it's incredibly slow!!
– Gamal Mohamed
Apr 21 '18 at 12:50
No, no this can't be a solution, it's incredibly slow!!
– Gamal Mohamed
Apr 21 '18 at 12:50
add a comment |
I am running Archlinux and I had exactly the same problem because I have $QT_SCALE_FACTOR set to 2 by default. Setting it back to 1 for the emulator fixed the problem:
env QT_SCALE_FACTOR=1 Android/Sdk/emulator/emulator -avd api25
answered May 27 '18 at 6:30
dvimdvim
1,39811016
Changing this settings works, but for me correct value was 0.667. So better way would be playing with it to check which value is good for your environment.
– Konstantin Labun
Jul 9 '18 at 6:03
2
For people using Android Studio find your installation folder and addexport QT_SCALE_FACTOR=1to yourstudio.shsomewhere in the beginning. Note that in KDE that factor must be1 / <display scale>. E.g0.5when you scaled your display by 2.
– Machisuji
Sep 17 '18 at 22:01
add a comment |
I am running Archlinux and I had exactly the same problem because I have $QT_SCALE_FACTOR set to 2 by default. Setting it back to 1 for the emulator fixed the problem:
env QT_SCALE_FACTOR=1 Android/Sdk/emulator/emulator -avd api25
answered May 27 '18 at 6:30
dvimdvim
1,39811016
Changing this settings works, but for me correct value was 0.667. So better way would be playing with it to check which value is good for your environment.
– Konstantin Labun
Jul 9 '18 at 6:03
2
For people using Android Studio find your installation folder and addexport QT_SCALE_FACTOR=1to yourstudio.shsomewhere in the beginning. Note that in KDE that factor must be1 / <display scale>. E.g0.5when you scaled your display by 2.
– Machisuji
Sep 17 '18 at 22:01
add a comment |
I am running Archlinux and I had exactly the same problem because I have $QT_SCALE_FACTOR set to 2 by default. Setting it back to 1 for the emulator fixed the problem:
env QT_SCALE_FACTOR=1 Android/Sdk/emulator/emulator -avd api25
answered May 27 '18 at 6:30
dvimdvim
1,39811016
I am running Archlinux and I had exactly the same problem because I have $QT_SCALE_FACTOR set to 2 by default. Setting it back to 1 for the emulator fixed the problem:
env QT_SCALE_FACTOR=1 Android/Sdk/emulator/emulator -avd api25
answered May 27 '18 at 6:30
dvimdvim
1,39811016
answered May 27 '18 at 6:30
dvimdvim
1,39811016
answered May 27 '18 at 6:30
dvimdvim
1,39811016
answered May 27 '18 at 6:30
dvimdvim
1,39811016
1,39811016
Changing this settings works, but for me correct value was 0.667. So better way would be playing with it to check which value is good for your environment.
– Konstantin Labun
Jul 9 '18 at 6:03
2
For people using Android Studio find your installation folder and addexport QT_SCALE_FACTOR=1to yourstudio.shsomewhere in the beginning. Note that in KDE that factor must be1 / <display scale>. E.g0.5when you scaled your display by 2.
– Machisuji
Sep 17 '18 at 22:01
add a comment |
Changing this settings works, but for me correct value was 0.667. So better way would be playing with it to check which value is good for your environment.
– Konstantin Labun
Jul 9 '18 at 6:03
2
For people using Android Studio find your installation folder and addexport QT_SCALE_FACTOR=1to yourstudio.shsomewhere in the beginning. Note that in KDE that factor must be1 / <display scale>. E.g0.5when you scaled your display by 2.
– Machisuji
Sep 17 '18 at 22:01
Changing this settings works, but for me correct value was 0.667. So better way would be playing with it to check which value is good for your environment.
– Konstantin Labun
Jul 9 '18 at 6:03
Changing this settings works, but for me correct value was 0.667. So better way would be playing with it to check which value is good for your environment.
– Konstantin Labun
Jul 9 '18 at 6:03
2
2
For people using Android Studio find your installation folder and add
export QT_SCALE_FACTOR=1 to your studio.sh somewhere in the beginning. Note that in KDE that factor must be 1 / <display scale>. E.g 0.5 when you scaled your display by 2.– Machisuji
Sep 17 '18 at 22:01
For people using Android Studio find your installation folder and add
export QT_SCALE_FACTOR=1 to your studio.sh somewhere in the beginning. Note that in KDE that factor must be 1 / <display scale>. E.g 0.5 when you scaled your display by 2.– Machisuji
Sep 17 '18 at 22:01
add a comment |
Try this and hopefully it works for you -
Go to
Toolsin Android Studio and openAVD ManagerIt will open all your virtual devices. Click on the Virtual device you want to edit and click the Pencil icon which will enable you to edit the device.
Click on
Changewhere it lists the device name. For example, for me my device name is Nexus 5X and lists the resolution of the device.In the Select a Device screen, click on
New Hardware Profileand change the resolution to 1080 x 1920 px.- Save the changes and run it again. If it still doesn't work, change the skin of the device.
- If still doesn't work, then make a new hardware profile with a new device.
answered Aug 3 '17 at 15:40
Ankit SharmaAnkit Sharma
409414
If you look at the question, I had asked it 2 days back and since then I have tried all these basic stuff which everyone knows ..! So , Unluckily , I have tried all those so called "still" from your answer . and you know what it "still" does not work.. Believe me, bounty awarded to the question (by me) is worth it.
– eRaisedToX
Aug 3 '17 at 17:14
add a comment |
Try this and hopefully it works for you -
Go to
Toolsin Android Studio and openAVD ManagerIt will open all your virtual devices. Click on the Virtual device you want to edit and click the Pencil icon which will enable you to edit the device.
Click on
Changewhere it lists the device name. For example, for me my device name is Nexus 5X and lists the resolution of the device.In the Select a Device screen, click on
New Hardware Profileand change the resolution to 1080 x 1920 px.- Save the changes and run it again. If it still doesn't work, change the skin of the device.
- If still doesn't work, then make a new hardware profile with a new device.
answered Aug 3 '17 at 15:40
Ankit SharmaAnkit Sharma
409414
If you look at the question, I had asked it 2 days back and since then I have tried all these basic stuff which everyone knows ..! So , Unluckily , I have tried all those so called "still" from your answer . and you know what it "still" does not work.. Believe me, bounty awarded to the question (by me) is worth it.
– eRaisedToX
Aug 3 '17 at 17:14
add a comment |
Try this and hopefully it works for you -
Go to
Toolsin Android Studio and openAVD ManagerIt will open all your virtual devices. Click on the Virtual device you want to edit and click the Pencil icon which will enable you to edit the device.
Click on
Changewhere it lists the device name. For example, for me my device name is Nexus 5X and lists the resolution of the device.In the Select a Device screen, click on
New Hardware Profileand change the resolution to 1080 x 1920 px.- Save the changes and run it again. If it still doesn't work, change the skin of the device.
- If still doesn't work, then make a new hardware profile with a new device.
answered Aug 3 '17 at 15:40
Ankit SharmaAnkit Sharma
409414
Try this and hopefully it works for you -
Go to
Toolsin Android Studio and openAVD ManagerIt will open all your virtual devices. Click on the Virtual device you want to edit and click the Pencil icon which will enable you to edit the device.
Click on
Changewhere it lists the device name. For example, for me my device name is Nexus 5X and lists the resolution of the device.In the Select a Device screen, click on
New Hardware Profileand change the resolution to 1080 x 1920 px.- Save the changes and run it again. If it still doesn't work, change the skin of the device.
- If still doesn't work, then make a new hardware profile with a new device.
answered Aug 3 '17 at 15:40
Ankit SharmaAnkit Sharma
409414
answered Aug 3 '17 at 15:40
Ankit SharmaAnkit Sharma
409414
answered Aug 3 '17 at 15:40
Ankit SharmaAnkit Sharma
409414
answered Aug 3 '17 at 15:40
Ankit SharmaAnkit Sharma
409414
409414
If you look at the question, I had asked it 2 days back and since then I have tried all these basic stuff which everyone knows ..! So , Unluckily , I have tried all those so called "still" from your answer . and you know what it "still" does not work.. Believe me, bounty awarded to the question (by me) is worth it.
– eRaisedToX
Aug 3 '17 at 17:14
add a comment |
If you look at the question, I had asked it 2 days back and since then I have tried all these basic stuff which everyone knows ..! So , Unluckily , I have tried all those so called "still" from your answer . and you know what it "still" does not work.. Believe me, bounty awarded to the question (by me) is worth it.
– eRaisedToX
Aug 3 '17 at 17:14
If you look at the question, I had asked it 2 days back and since then I have tried all these basic stuff which everyone knows ..! So , Unluckily , I have tried all those so called "still" from your answer . and you know what it "still" does not work.. Believe me, bounty awarded to the question (by me) is worth it.
– eRaisedToX
Aug 3 '17 at 17:14
If you look at the question, I had asked it 2 days back and since then I have tried all these basic stuff which everyone knows ..! So , Unluckily , I have tried all those so called "still" from your answer . and you know what it "still" does not work.. Believe me, bounty awarded to the question (by me) is worth it.
– eRaisedToX
Aug 3 '17 at 17:14
add a comment |
I have this similar issue. It happened after using an external monitor that has lower resolution (1440 x 900) than my laptop (2160 x 1440) has. There are couple of ways you can fix it until Google fix the issue.
- if you match your PC's resolution to your external monitor's resolution. Then you can return back to your PC's resolution.
- If you lower the scaling of your PC ( mine was 150% > 125% or 100%) from Display Settings. Run the emulator. Again, you can return back to your original scaling, emulator screen won't change. This is the one I prefer.
Note: this is not a permanent solution. You may need to change scaling/resolution again if you change your scaling or resolution to the one you had issue with. I have tested this only on Windows 10 Pro, but this approach might work on Mac as well.
answered Nov 10 '17 at 22:35
BenazirBenazir
314
Worked for me! but it's still a hack, hopefully we find a real solution for this..
– Gamal Mohamed
Apr 21 '18 at 12:50
add a comment |
I have this similar issue. It happened after using an external monitor that has lower resolution (1440 x 900) than my laptop (2160 x 1440) has. There are couple of ways you can fix it until Google fix the issue.
- if you match your PC's resolution to your external monitor's resolution. Then you can return back to your PC's resolution.
- If you lower the scaling of your PC ( mine was 150% > 125% or 100%) from Display Settings. Run the emulator. Again, you can return back to your original scaling, emulator screen won't change. This is the one I prefer.
Note: this is not a permanent solution. You may need to change scaling/resolution again if you change your scaling or resolution to the one you had issue with. I have tested this only on Windows 10 Pro, but this approach might work on Mac as well.
answered Nov 10 '17 at 22:35
BenazirBenazir
314
Worked for me! but it's still a hack, hopefully we find a real solution for this..
– Gamal Mohamed
Apr 21 '18 at 12:50
add a comment |
I have this similar issue. It happened after using an external monitor that has lower resolution (1440 x 900) than my laptop (2160 x 1440) has. There are couple of ways you can fix it until Google fix the issue.
- if you match your PC's resolution to your external monitor's resolution. Then you can return back to your PC's resolution.
- If you lower the scaling of your PC ( mine was 150% > 125% or 100%) from Display Settings. Run the emulator. Again, you can return back to your original scaling, emulator screen won't change. This is the one I prefer.
Note: this is not a permanent solution. You may need to change scaling/resolution again if you change your scaling or resolution to the one you had issue with. I have tested this only on Windows 10 Pro, but this approach might work on Mac as well.
answered Nov 10 '17 at 22:35
BenazirBenazir
314
I have this similar issue. It happened after using an external monitor that has lower resolution (1440 x 900) than my laptop (2160 x 1440) has. There are couple of ways you can fix it until Google fix the issue.
- if you match your PC's resolution to your external monitor's resolution. Then you can return back to your PC's resolution.
- If you lower the scaling of your PC ( mine was 150% > 125% or 100%) from Display Settings. Run the emulator. Again, you can return back to your original scaling, emulator screen won't change. This is the one I prefer.
Note: this is not a permanent solution. You may need to change scaling/resolution again if you change your scaling or resolution to the one you had issue with. I have tested this only on Windows 10 Pro, but this approach might work on Mac as well.
answered Nov 10 '17 at 22:35
BenazirBenazir
314
edited Nov 10 '17 at 22:46
answered Nov 10 '17 at 22:35
BenazirBenazir
314
answered Nov 10 '17 at 22:35
BenazirBenazir
314
answered Nov 10 '17 at 22:35
BenazirBenazir
314
314
Worked for me! but it's still a hack, hopefully we find a real solution for this..
– Gamal Mohamed
Apr 21 '18 at 12:50
add a comment |
Worked for me! but it's still a hack, hopefully we find a real solution for this..
– Gamal Mohamed
Apr 21 '18 at 12:50
Worked for me! but it's still a hack, hopefully we find a real solution for this..
– Gamal Mohamed
Apr 21 '18 at 12:50
Worked for me! but it's still a hack, hopefully we find a real solution for this..
– Gamal Mohamed
Apr 21 '18 at 12:50
add a comment |
Open the Emulator and press Ctrl+Up_Key to increase the scale and Ctrl+Down_Key to scale down. (Cmd+KUp / Cmd+KDown if you are on mac)
answered Aug 3 '17 at 11:24
aaron0207aaron0207
1,2851516
I dont know what do you mean by "Right Click the Project Folder"... What I have tried is --- Run ->Edit Configuration->target select as emulator,,, but then there is NO option for scale and all.. can you post some screen shots
– eRaisedToX
Aug 3 '17 at 13:52
Try my updated answer
– aaron0207
Aug 4 '17 at 6:35
yeah bro..I tried...all those..that increases the size of device plus the screen but ratio remains same (screen covering only 30% of device)No clue what's wrong...!
– eRaisedToX
Aug 4 '17 at 7:53
Worked for me for Nexus 4 simulator, on 15.6 inch mac.
– Martin Berger
2 days ago
add a comment |
Open the Emulator and press Ctrl+Up_Key to increase the scale and Ctrl+Down_Key to scale down. (Cmd+KUp / Cmd+KDown if you are on mac)
answered Aug 3 '17 at 11:24
aaron0207aaron0207
1,2851516
I dont know what do you mean by "Right Click the Project Folder"... What I have tried is --- Run ->Edit Configuration->target select as emulator,,, but then there is NO option for scale and all.. can you post some screen shots
– eRaisedToX
Aug 3 '17 at 13:52
Try my updated answer
– aaron0207
Aug 4 '17 at 6:35
yeah bro..I tried...all those..that increases the size of device plus the screen but ratio remains same (screen covering only 30% of device)No clue what's wrong...!
– eRaisedToX
Aug 4 '17 at 7:53
Worked for me for Nexus 4 simulator, on 15.6 inch mac.
– Martin Berger
2 days ago
add a comment |
Open the Emulator and press Ctrl+Up_Key to increase the scale and Ctrl+Down_Key to scale down. (Cmd+KUp / Cmd+KDown if you are on mac)
answered Aug 3 '17 at 11:24
aaron0207aaron0207
1,2851516
Open the Emulator and press Ctrl+Up_Key to increase the scale and Ctrl+Down_Key to scale down. (Cmd+KUp / Cmd+KDown if you are on mac)
answered Aug 3 '17 at 11:24
aaron0207aaron0207
1,2851516
edited Aug 4 '17 at 6:35
answered Aug 3 '17 at 11:24
aaron0207aaron0207
1,2851516
answered Aug 3 '17 at 11:24
aaron0207aaron0207
1,2851516
answered Aug 3 '17 at 11:24
aaron0207aaron0207
1,2851516
1,2851516
I dont know what do you mean by "Right Click the Project Folder"... What I have tried is --- Run ->Edit Configuration->target select as emulator,,, but then there is NO option for scale and all.. can you post some screen shots
– eRaisedToX
Aug 3 '17 at 13:52
Try my updated answer
– aaron0207
Aug 4 '17 at 6:35
yeah bro..I tried...all those..that increases the size of device plus the screen but ratio remains same (screen covering only 30% of device)No clue what's wrong...!
– eRaisedToX
Aug 4 '17 at 7:53
Worked for me for Nexus 4 simulator, on 15.6 inch mac.
– Martin Berger
2 days ago
add a comment |
I dont know what do you mean by "Right Click the Project Folder"... What I have tried is --- Run ->Edit Configuration->target select as emulator,,, but then there is NO option for scale and all.. can you post some screen shots
– eRaisedToX
Aug 3 '17 at 13:52
Try my updated answer
– aaron0207
Aug 4 '17 at 6:35
yeah bro..I tried...all those..that increases the size of device plus the screen but ratio remains same (screen covering only 30% of device)No clue what's wrong...!
– eRaisedToX
Aug 4 '17 at 7:53
Worked for me for Nexus 4 simulator, on 15.6 inch mac.
– Martin Berger
2 days ago
I dont know what do you mean by "Right Click the Project Folder"... What I have tried is --- Run ->Edit Configuration->target select as emulator,,, but then there is NO option for scale and all.. can you post some screen shots
– eRaisedToX
Aug 3 '17 at 13:52
I dont know what do you mean by "Right Click the Project Folder"... What I have tried is --- Run ->Edit Configuration->target select as emulator,,, but then there is NO option for scale and all.. can you post some screen shots
– eRaisedToX
Aug 3 '17 at 13:52
Try my updated answer
– aaron0207
Aug 4 '17 at 6:35
Try my updated answer
– aaron0207
Aug 4 '17 at 6:35
yeah bro..I tried...all those..that increases the size of device plus the screen but ratio remains same (screen covering only 30% of device)No clue what's wrong...!
– eRaisedToX
Aug 4 '17 at 7:53
yeah bro..I tried...all those..that increases the size of device plus the screen but ratio remains same (screen covering only 30% of device)No clue what's wrong...!
– eRaisedToX
Aug 4 '17 at 7:53
Worked for me for Nexus 4 simulator, on 15.6 inch mac.
– Martin Berger
2 days ago
Worked for me for Nexus 4 simulator, on 15.6 inch mac.
– Martin Berger
2 days ago
add a comment |
Have you already tried other emulator? I suggest Try bluestacks
go the tab Emulator (next to the General tab), and in Additional command line options, write
-scale 100.X
Press alt + space + M
Pls. see landscape also and revert back to portrait
answered Aug 10 '17 at 6:49
user8256287user8256287
14111
1
Which Emulator Tab you are talking about , If I go to Run -> Edit Configuration I see some tabs , but no emulator tab .. pls post screen shot if you can.
– eRaisedToX
Aug 10 '17 at 8:48
add a comment |
Have you already tried other emulator? I suggest Try bluestacks
go the tab Emulator (next to the General tab), and in Additional command line options, write
-scale 100.X
Press alt + space + M
Pls. see landscape also and revert back to portrait
answered Aug 10 '17 at 6:49
user8256287user8256287
14111
1
Which Emulator Tab you are talking about , If I go to Run -> Edit Configuration I see some tabs , but no emulator tab .. pls post screen shot if you can.
– eRaisedToX
Aug 10 '17 at 8:48
add a comment |
Have you already tried other emulator? I suggest Try bluestacks
go the tab Emulator (next to the General tab), and in Additional command line options, write
-scale 100.X
Press alt + space + M
Pls. see landscape also and revert back to portrait
answered Aug 10 '17 at 6:49
user8256287user8256287
14111
Have you already tried other emulator? I suggest Try bluestacks
go the tab Emulator (next to the General tab), and in Additional command line options, write
-scale 100.X
Press alt + space + M
Pls. see landscape also and revert back to portrait
answered Aug 10 '17 at 6:49
user8256287user8256287
14111
answered Aug 10 '17 at 6:49
user8256287user8256287
14111
answered Aug 10 '17 at 6:49
user8256287user8256287
14111
answered Aug 10 '17 at 6:49
user8256287user8256287
14111
14111
1
Which Emulator Tab you are talking about , If I go to Run -> Edit Configuration I see some tabs , but no emulator tab .. pls post screen shot if you can.
– eRaisedToX
Aug 10 '17 at 8:48
add a comment |
1
Which Emulator Tab you are talking about , If I go to Run -> Edit Configuration I see some tabs , but no emulator tab .. pls post screen shot if you can.
– eRaisedToX
Aug 10 '17 at 8:48
1
1
Which Emulator Tab you are talking about , If I go to Run -> Edit Configuration I see some tabs , but no emulator tab .. pls post screen shot if you can.
– eRaisedToX
Aug 10 '17 at 8:48
Which Emulator Tab you are talking about , If I go to Run -> Edit Configuration I see some tabs , but no emulator tab .. pls post screen shot if you can.
– eRaisedToX
Aug 10 '17 at 8:48
add a comment |
This looks like an incompatibility with windows scaling.
Try setting scale to 100% in display settings of Windows (right click on desktop).
answered Aug 10 '17 at 11:57
Rishabh KohliRishabh Kohli
737
Worked for me! but it's still a hack, hopefully we find a real solution for this..
– Gamal Mohamed
Apr 21 '18 at 12:49
add a comment |
This looks like an incompatibility with windows scaling.
Try setting scale to 100% in display settings of Windows (right click on desktop).
answered Aug 10 '17 at 11:57
Rishabh KohliRishabh Kohli
737
Worked for me! but it's still a hack, hopefully we find a real solution for this..
– Gamal Mohamed
Apr 21 '18 at 12:49
add a comment |
This looks like an incompatibility with windows scaling.
Try setting scale to 100% in display settings of Windows (right click on desktop).
answered Aug 10 '17 at 11:57
Rishabh KohliRishabh Kohli
737
This looks like an incompatibility with windows scaling.
Try setting scale to 100% in display settings of Windows (right click on desktop).
answered Aug 10 '17 at 11:57
Rishabh KohliRishabh Kohli
737
answered Aug 10 '17 at 11:57
Rishabh KohliRishabh Kohli
737
answered Aug 10 '17 at 11:57
Rishabh KohliRishabh Kohli
737
answered Aug 10 '17 at 11:57
Rishabh KohliRishabh Kohli
737
737
Worked for me! but it's still a hack, hopefully we find a real solution for this..
– Gamal Mohamed
Apr 21 '18 at 12:49
add a comment |
Worked for me! but it's still a hack, hopefully we find a real solution for this..
– Gamal Mohamed
Apr 21 '18 at 12:49
Worked for me! but it's still a hack, hopefully we find a real solution for this..
– Gamal Mohamed
Apr 21 '18 at 12:49
Worked for me! but it's still a hack, hopefully we find a real solution for this..
– Gamal Mohamed
Apr 21 '18 at 12:49
add a comment |
*Software rendering is very slow to be usable
Better Fix
You can fix the scaling issue when using the Hardware rendering by simply making windows override the scaling setting. How?, it's very easy.
Simply locate the .exe file for the emulator that you are using, (e.g. "qemu-system-armel.exe" for ARM and "qemu-system-x86_64.exe" for x86).
To make sure which .exe file, just run the emulator then use task manager to locate the .exe file is running, see the screenshot.
locate the .exe file using task manager
In my case it was in this location:
"C:Users[Username]AppDataLocalAndroidSdkemulatorqemuwindows-x86_64qemu-system-x86_64.exe"
Now just right click on the file then click on properties then choose the "Compatibility" tab. Under "Settings" at the bottom, click on "Change high DPI settings".
A new window will open. Tick the last checkbox "Override high DPI scaling behavior." under "High DPI scaling override".
Then select from the drop down below it "System" (this is very important or it will not make any difference!), see the screenshot below. Now just hit OK and OK. And that's it, problem solved :)
override scaling settings for the .exe file
answered Jun 25 '18 at 18:50
WaelWael
111
Thanks! This worked for me, required restarting android studio
– grantka
Jul 8 '18 at 17:40
add a comment |
*Software rendering is very slow to be usable
Better Fix
You can fix the scaling issue when using the Hardware rendering by simply making windows override the scaling setting. How?, it's very easy.
Simply locate the .exe file for the emulator that you are using, (e.g. "qemu-system-armel.exe" for ARM and "qemu-system-x86_64.exe" for x86).
To make sure which .exe file, just run the emulator then use task manager to locate the .exe file is running, see the screenshot.
locate the .exe file using task manager
In my case it was in this location:
"C:Users[Username]AppDataLocalAndroidSdkemulatorqemuwindows-x86_64qemu-system-x86_64.exe"
Now just right click on the file then click on properties then choose the "Compatibility" tab. Under "Settings" at the bottom, click on "Change high DPI settings".
A new window will open. Tick the last checkbox "Override high DPI scaling behavior." under "High DPI scaling override".
Then select from the drop down below it "System" (this is very important or it will not make any difference!), see the screenshot below. Now just hit OK and OK. And that's it, problem solved :)
override scaling settings for the .exe file
answered Jun 25 '18 at 18:50
WaelWael
111
Thanks! This worked for me, required restarting android studio
– grantka
Jul 8 '18 at 17:40
add a comment |
*Software rendering is very slow to be usable
Better Fix
You can fix the scaling issue when using the Hardware rendering by simply making windows override the scaling setting. How?, it's very easy.
Simply locate the .exe file for the emulator that you are using, (e.g. "qemu-system-armel.exe" for ARM and "qemu-system-x86_64.exe" for x86).
To make sure which .exe file, just run the emulator then use task manager to locate the .exe file is running, see the screenshot.
locate the .exe file using task manager
In my case it was in this location:
"C:Users[Username]AppDataLocalAndroidSdkemulatorqemuwindows-x86_64qemu-system-x86_64.exe"
Now just right click on the file then click on properties then choose the "Compatibility" tab. Under "Settings" at the bottom, click on "Change high DPI settings".
A new window will open. Tick the last checkbox "Override high DPI scaling behavior." under "High DPI scaling override".
Then select from the drop down below it "System" (this is very important or it will not make any difference!), see the screenshot below. Now just hit OK and OK. And that's it, problem solved :)
override scaling settings for the .exe file
answered Jun 25 '18 at 18:50
WaelWael
111
*Software rendering is very slow to be usable
Better Fix
You can fix the scaling issue when using the Hardware rendering by simply making windows override the scaling setting. How?, it's very easy.
Simply locate the .exe file for the emulator that you are using, (e.g. "qemu-system-armel.exe" for ARM and "qemu-system-x86_64.exe" for x86).
To make sure which .exe file, just run the emulator then use task manager to locate the .exe file is running, see the screenshot.
locate the .exe file using task manager
In my case it was in this location:
"C:Users[Username]AppDataLocalAndroidSdkemulatorqemuwindows-x86_64qemu-system-x86_64.exe"
Now just right click on the file then click on properties then choose the "Compatibility" tab. Under "Settings" at the bottom, click on "Change high DPI settings".
A new window will open. Tick the last checkbox "Override high DPI scaling behavior." under "High DPI scaling override".
Then select from the drop down below it "System" (this is very important or it will not make any difference!), see the screenshot below. Now just hit OK and OK. And that's it, problem solved :)
override scaling settings for the .exe file
answered Jun 25 '18 at 18:50
WaelWael
111
answered Jun 25 '18 at 18:50
WaelWael
111
answered Jun 25 '18 at 18:50
WaelWael
111
answered Jun 25 '18 at 18:50
WaelWael
111
111
Thanks! This worked for me, required restarting android studio
– grantka
Jul 8 '18 at 17:40
add a comment |
Thanks! This worked for me, required restarting android studio
– grantka
Jul 8 '18 at 17:40
Thanks! This worked for me, required restarting android studio
– grantka
Jul 8 '18 at 17:40
Thanks! This worked for me, required restarting android studio
– grantka
Jul 8 '18 at 17:40
add a comment |
I ran into this issue a while ago and have been struggling for it until now.
Solution seems to be:
Go to C:UsersYourUserAppDataLocalAndroidSdkemulator
Here, right click on emulator.exe, click Properties and go to Compatibility. Here, check: "Override high DPI scaling behavior. Scaling performed by: APPLICATION".
This should fix the issue on any Windows 10 machine with display scaling activated.
answered Apr 30 '18 at 10:58
akseliakseli
249110
add a comment |
I ran into this issue a while ago and have been struggling for it until now.
Solution seems to be:
Go to C:UsersYourUserAppDataLocalAndroidSdkemulator
Here, right click on emulator.exe, click Properties and go to Compatibility. Here, check: "Override high DPI scaling behavior. Scaling performed by: APPLICATION".
This should fix the issue on any Windows 10 machine with display scaling activated.
answered Apr 30 '18 at 10:58
akseliakseli
249110
add a comment |
I ran into this issue a while ago and have been struggling for it until now.
Solution seems to be:
Go to C:UsersYourUserAppDataLocalAndroidSdkemulator
Here, right click on emulator.exe, click Properties and go to Compatibility. Here, check: "Override high DPI scaling behavior. Scaling performed by: APPLICATION".
This should fix the issue on any Windows 10 machine with display scaling activated.
answered Apr 30 '18 at 10:58
akseliakseli
249110
I ran into this issue a while ago and have been struggling for it until now.
Solution seems to be:
Go to C:UsersYourUserAppDataLocalAndroidSdkemulator
Here, right click on emulator.exe, click Properties and go to Compatibility. Here, check: "Override high DPI scaling behavior. Scaling performed by: APPLICATION".
This should fix the issue on any Windows 10 machine with display scaling activated.
answered Apr 30 '18 at 10:58
akseliakseli
249110
answered Apr 30 '18 at 10:58
akseliakseli
249110
answered Apr 30 '18 at 10:58
akseliakseli
249110
answered Apr 30 '18 at 10:58
akseliakseli
249110
249110
add a comment |
add a comment |
In case someone ran into this issue on Linux, here is a fix:
QT_AUTO_SCREEN_SCALE_FACTOR=0 emulator -avd <Name of your virtual device>
answered Aug 29 '18 at 11:09
qedqed
9,7491266116
add a comment |
In case someone ran into this issue on Linux, here is a fix:
QT_AUTO_SCREEN_SCALE_FACTOR=0 emulator -avd <Name of your virtual device>
answered Aug 29 '18 at 11:09
qedqed
9,7491266116
add a comment |
In case someone ran into this issue on Linux, here is a fix:
QT_AUTO_SCREEN_SCALE_FACTOR=0 emulator -avd <Name of your virtual device>
answered Aug 29 '18 at 11:09
qedqed
9,7491266116
In case someone ran into this issue on Linux, here is a fix:
QT_AUTO_SCREEN_SCALE_FACTOR=0 emulator -avd <Name of your virtual device>
answered Aug 29 '18 at 11:09
qedqed
9,7491266116
answered Aug 29 '18 at 11:09
qedqed
9,7491266116
answered Aug 29 '18 at 11:09
qedqed
9,7491266116
answered Aug 29 '18 at 11:09
qedqed
9,7491266116
9,7491266116
add a comment |
add a comment |
Just go to display setting and change it to 100%.this normally happens if you have a fourteen inch laptop and below
answered Nov 11 '18 at 13:11
tarustarus
11
add a comment |
Just go to display setting and change it to 100%.this normally happens if you have a fourteen inch laptop and below
answered Nov 11 '18 at 13:11
tarustarus
11
add a comment |
Just go to display setting and change it to 100%.this normally happens if you have a fourteen inch laptop and below
answered Nov 11 '18 at 13:11
tarustarus
11
Just go to display setting and change it to 100%.this normally happens if you have a fourteen inch laptop and below
answered Nov 11 '18 at 13:11
tarustarus
11
answered Nov 11 '18 at 13:11
tarustarus
11
answered Nov 11 '18 at 13:11
tarustarus
11
answered Nov 11 '18 at 13:11
tarustarus
11
11
add a comment |
add a comment |
On Windows with high resolution screens I have to change the "high DPI setting" from application to system.
- Close Android Studio If it's open
- Right Click Android studio icon on desktop
- Select properties--> Compatibility
- Click "Change high DPI setting"
- Under "High DPI scaling override" section from the drop down list select System
- Click OK on both screens.
However, if you want to just run the emulator using PowerShell on windows by running "emulator '@your_device_name'" command, you would still have the same issue. to fix this issue you basically need to Right click the emulator you want to run and follow the steps from 3 to 6.
The default path for the emulators on windows is:
C:UsersREPLACE_IT_WITH_YOURSAppDataLocalAndroidsdkemulatorqemuwindows-x86_64
Alternatively to open the emulator's properties:
1. Run android studio
2. Select Tools and then AVD Manager
3. Run the emulator you want to use
4. Right click emulator on the task bar
5. Right click *.exe and choose properties
6. Follow the steps from 3 to 6 to change "high DPI setting"
answered Nov 2 '18 at 0:23
Alireza BayatAlireza Bayat
11
add a comment |
On Windows with high resolution screens I have to change the "high DPI setting" from application to system.
- Close Android Studio If it's open
- Right Click Android studio icon on desktop
- Select properties--> Compatibility
- Click "Change high DPI setting"
- Under "High DPI scaling override" section from the drop down list select System
- Click OK on both screens.
However, if you want to just run the emulator using PowerShell on windows by running "emulator '@your_device_name'" command, you would still have the same issue. to fix this issue you basically need to Right click the emulator you want to run and follow the steps from 3 to 6.
The default path for the emulators on windows is:
C:UsersREPLACE_IT_WITH_YOURSAppDataLocalAndroidsdkemulatorqemuwindows-x86_64
Alternatively to open the emulator's properties:
1. Run android studio
2. Select Tools and then AVD Manager
3. Run the emulator you want to use
4. Right click emulator on the task bar
5. Right click *.exe and choose properties
6. Follow the steps from 3 to 6 to change "high DPI setting"
answered Nov 2 '18 at 0:23
Alireza BayatAlireza Bayat
11
add a comment |
On Windows with high resolution screens I have to change the "high DPI setting" from application to system.
- Close Android Studio If it's open
- Right Click Android studio icon on desktop
- Select properties--> Compatibility
- Click "Change high DPI setting"
- Under "High DPI scaling override" section from the drop down list select System
- Click OK on both screens.
However, if you want to just run the emulator using PowerShell on windows by running "emulator '@your_device_name'" command, you would still have the same issue. to fix this issue you basically need to Right click the emulator you want to run and follow the steps from 3 to 6.
The default path for the emulators on windows is:
C:UsersREPLACE_IT_WITH_YOURSAppDataLocalAndroidsdkemulatorqemuwindows-x86_64
Alternatively to open the emulator's properties:
1. Run android studio
2. Select Tools and then AVD Manager
3. Run the emulator you want to use
4. Right click emulator on the task bar
5. Right click *.exe and choose properties
6. Follow the steps from 3 to 6 to change "high DPI setting"
answered Nov 2 '18 at 0:23
Alireza BayatAlireza Bayat
11
On Windows with high resolution screens I have to change the "high DPI setting" from application to system.
- Close Android Studio If it's open
- Right Click Android studio icon on desktop
- Select properties--> Compatibility
- Click "Change high DPI setting"
- Under "High DPI scaling override" section from the drop down list select System
- Click OK on both screens.
However, if you want to just run the emulator using PowerShell on windows by running "emulator '@your_device_name'" command, you would still have the same issue. to fix this issue you basically need to Right click the emulator you want to run and follow the steps from 3 to 6.
The default path for the emulators on windows is:
C:UsersREPLACE_IT_WITH_YOURSAppDataLocalAndroidsdkemulatorqemuwindows-x86_64
Alternatively to open the emulator's properties:
1. Run android studio
2. Select Tools and then AVD Manager
3. Run the emulator you want to use
4. Right click emulator on the task bar
5. Right click *.exe and choose properties
6. Follow the steps from 3 to 6 to change "high DPI setting"
answered Nov 2 '18 at 0:23
Alireza BayatAlireza Bayat
11
edited Nov 21 '18 at 5:45
answered Nov 2 '18 at 0:23
Alireza BayatAlireza Bayat
11
answered Nov 2 '18 at 0:23
Alireza BayatAlireza Bayat
11
answered Nov 2 '18 at 0:23
Alireza BayatAlireza Bayat
11
11
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f45435272%2fandroid-emulator-screen-fills-up-only-some-fraction-part-of-actual-android-emula%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
check this stackoverflow.com/questions/29737499/…
– Salman500
Aug 1 '17 at 10:29
I saw that...didn't help , I don't see any emulator tab in run->edit configuration
– eRaisedToX
Aug 1 '17 at 10:30
rotate screen from given rotation function in menu bar .
– Kevan Aghera
Aug 3 '17 at 11:21
@kevanaghera , "rotate" ???? No man !! that has nothing to do with it. I had tried all basic stuff.
– eRaisedToX
Aug 3 '17 at 13:33
It happen a few times to me and closing and re-opening the emulator fixed the problem. It usually happend when I closed my laptop lid without putting it to sleep first. I know that restarting it didn't fixed your problem, but maybe you can find a similar pattern.
– Iulian Popescu
Aug 11 '17 at 11:09