Fixed
Status Update
No update yet.
Comments
na...@gmail.com
guys this issue need a fix, lots of 4k display are out there and are used with 1080p notebook
sj...@gmail.com
I have a Lenovo P50 laptop with a 1920x1080 display and Windows 10, and I have two older monitors that I used with a dock. Every time I dock or undock my laptop Android Studio appears very blurry (see attached screenshot). To resolve this, I have to close all applications and sign out and sign back in to Windows, which is really annoying. It would be great if this could be implemented so I don't have to close everything out every time I dock/undock.
Here are the two user resources I found related to this on Windows 10:
*https://support.microsoft.com/en-us/help/3025083/windows-scaling-issues-for-high-dpi-devices
*https://msdn.microsoft.com/en-us/library/windows/desktop/dn280512(v=vs.85).aspx
Using Sysinternals Process Explorer you can confirm that Android Studio is "System Aware", not "Per-Monitor Aware".
Here are the two user resources I found related to this on Windows 10:
*
*
Using Sysinternals Process Explorer you can confirm that Android Studio is "System Aware", not "Per-Monitor Aware".
sj...@gmail.com
FWIW, it seems like this may be fixed in IntelliJ.
This issue:
https://youtrack.jetbrains.com/issue/IDEA-141456#comment=27-1847865
...says:
"IDEA-164566 (https://youtrack.jetbrains.com/issue/IDEA-164566 ) introduced support for per-monitor integral scale factors on Windows (IDEA 2017). To experience it, please make sure you have the following property set to true (in idea.properties):
sun.java2d.uiScale.enabled=true"
This issue:
...says:
"IDEA-164566 (
sun.java2d.uiScale.enabled=true"
rp...@google.com
#3: It is very likely Android Studio will at some point integrate the changes made to IntelliJ 2017. Note that (currently), IntelliJ solution is still limited to "*integral* scale factors on Windows".
What this means is that 200%, 300%, etc. are supported, but 125%, 150%, 250%, etc. are not supported.
By "not supported", I think this means that non-integral scaling factors are rounded to integral ones. This eliminates blurriness in all cases, but will result in UI looking smaller (or bigger) than expected.
What this means is that 200%, 300%, etc. are supported, but 125%, 150%, 250%, etc. are not supported.
By "not supported", I think this means that non-integral scaling factors are rounded to integral ones. This eliminates blurriness in all cases, but will result in UI looking smaller (or bigger) than expected.
se...@gmail.com
Android Studio 3.1
Windows 10
Laptop with an external monitor as a main display
What worked for me:
1. Display scale of the monitor = 100%
2. Android Studio > Help > Edit Custom Properties: sun.java2d.uiScale.enabled=true"
3. Restart Studio
4. Configure UI and Editor proper font sizes
Windows 10
Laptop with an external monitor as a main display
What worked for me:
1. Display scale of the monitor = 100%
2. Android Studio > Help > Edit Custom Properties: sun.java2d.uiScale.enabled=true"
3. Restart Studio
4. Configure UI and Editor proper font sizes
sa...@gmail.com
Phone is just fucked
rp...@google.com
Android Studio 3.2 implemented the same multi-monitor support as IJ 2018.1, meaning multi-monitor support with fractional scaling support.
fo...@gmail.com
Bug all
dv...@gmail.com
tr...@gmail.com
None
st...@gmail.com
I still have this problem in android studio 2021.2.1
pi...@gmail.com
Still had the problem in android studio Chipmunk (2021.2.1 Patch 2)
I found a work around that works for me on my dell g15 laptop, what you do is
Close Android studio
Go into your settings -> System -> Display settings
Select your main monitor -> Scale and layout -> change the scaling from your current to 100%
Open android studio
Change back your scaling to the original one
This should fix temporarily the dpi on android studio
I found a work around that works for me on my dell g15 laptop, what you do is
Close Android studio
Go into your settings -> System -> Display settings
Select your main monitor -> Scale and layout -> change the scaling from your current to 100%
Open android studio
Change back your scaling to the original one
This should fix temporarily the dpi on android studio
lu...@gmail.com
I am facing the same issue and have found the folowing fix on Windows 11:
1. Go to Android Studio shortcut and open properties
2. On Compatibility tab, click "Run compatibility troubleshooter"
3. Follow the troubleshooter suggestions and, if solved, save program config.
In my case, Windows set the program to run with in High DPI mode or something like that. It's working fine now, even with my main monitor at 125% scaling.
1. Go to Android Studio shortcut and open properties
2. On Compatibility tab, click "Run compatibility troubleshooter"
3. Follow the troubleshooter suggestions and, if solved, save program config.
In my case, Windows set the program to run with in High DPI mode or something like that. It's working fine now, even with my main monitor at 125% scaling.
ga...@gmail.com
- uses: actions/setup-dotnet@v3
id: stepid
with:
dotnet-version: 3.1.422
- run: echo '${{ steps.stepid.outputs.dotnet-version }}' # outputs 3.1.422
hk...@gmail.com Restricted
Restricted
Comment has been deleted.
at...@gmail.com
تنشط
Description
Long story short, to get the best possible experience, applications have to be coded specifically to support this new feature, otherwise blurriness will occur in certain scenarios, as Windows will scale automatically, "The effect is that the window and content size are appropriate for every display, but the scaling introduces blurriness.".
Official doc:
There is a good summary here:
This has 2 implications:
1) Applications need to support DPI setting per top-level window (as opposed to application wide) <= This is required because top level windows of a single application may appear on separate displays, each one with distinct DPI settings.
2) Applications need to be able to apply a new DPI setting to any top level window at run-time, without restarting <= This happens when a window is moved by the user from one display to another display with a different DPI setting.
Implementation notes:
* Supporting this feature means that every top level windows of Android Studio will have it's own DPI (and scaling factor), so relying on a global scaling factor is not an option anymore.
* This also means that the application needs to support dynamically (i.e. at run time) scaling to a different factor all components of a top level window in response to the WM_DPICHANGED message.
* The two points above make the approach currently implementated in the JBUI class obsolete.