I have been searching this over the web for 2 days now and I am still unable to get my hands on something helpful. I have to run my windows 8.1 app on large device (i-e 80 inches) having 4k(3840 X 2160) resolution. The max resolution I have on the windows simulator is 2560 x 1440 (i-e 27 inches). Is there any way that I can add custom screen size/resolution to windows simulator? or is there any other option available where I can test my app on 4k resolution?
PS: I don't have a 4k device with me right now, that's why I want to test it on some simulator.
Thanks in anticipation.
The simulator doesn't support custom resolutions.
If you design your UI to be flexible and test it at a variety of resolutions and DPI levels you should be able to get a pretty good idea of how it will work. Running at 1920x1080 will give the same ratio as 3840x2160, just scaled by half in each direction.
You can request feature updates for the Windows Dev Platform at http://wpdev.uservoice.com
Related
I have an issue all of a sudden where I am getting a weird black flickering at the bottom of the screen (as shown in the video below). I had no problem earlier also this happened after I removed android emulator and rechecked it (Reinstalled it ) under the setting “Tools” ->” SDK Manager” -> “SDK Tools” tab.
Video Link - https://vimeo.com/manage/videos/739329236
Computer Specs -
I7 - 10750h,
Nvidia 1650 Ti - 4GB,
16 GB Ram,
1 TB SSD (443 GB free)
Also, I have noticed the screen goes most of the part blank when I am not touching the screen.
I had the same problem recently after create a emulator with API level 33,
Then I've tried to used API level 31 and emulator works normally.
I tried giving more memory to my emulator and the issue disappeared.
https://i.stack.imgur.com/QHSIK.png
It seems there is a problem with the x86_64 images. If Software GLESS is turned on then the flicker goes away but the graphics are little laggy.
x86 images works well smooth but out-dated.
I just installed Android Studio first time for a while and noticed the flickering problem right away. I have NVIDIA GPU which most likely contributes into this problem. In the AVD options inside the Android Studio device manager I tried switching the Graphics setting from automatic to "Software GLES 2.0" and it fixed the flickering. No way using software acceleration is optimal in any way but it could be a workaround until the root cause is fixed.
EDIT: found the issue posted about this behavior confirming it is a GPU driver related issue https://issuetracker.google.com/issues/246917660
I had a same issue in my new laptop. I have fixed it by changing one parameter in the emulator's config file.
Go to C:\Users\USER_NAME.android\avd\Pixel_5_API_31.avd
Edit the config.ini file.
Find the "hw.gpu.mode = auto" and change it to the "hw.gpu.mode = guest" and save the changes.
Restart the emulator.
Same here. After one of the latest Emulator (in SDK tools) updates virtual device with API level 31 or above show same issues. Devices with API level 30 or below work fine.
Tried to completely clean and re-install Studio and Video drivers. No effect.
So since it started right after update i believe it's Emulator component issue.
I just switched to a Pixel 5 with API 33 and it seems to have resolved my flickering problem..
I'm trying to capture the desktop screen using Windows Magnification APIs based on code sample given in https://www.codeproject.com/Articles/607288/Screenshot-using-the-Magnification-library?msg=5570528#xx5570528xx.
The program (32bit executable) works pretty good on Windows8 and Windows10 but fails on Windows7 OS. I compiled the program into 64bit and the behavior is same even for the sample program mentioned in the above codeproject thread.
After debugging I figured out that the MagImageScalingCallback function returns image width and height as 4*4 instead of my monitor's size and that causes the program to crash or capture a blank screen on Windows7 machines (reference: https://learn.microsoft.com/en-us/windows/desktop/api/magnification/ns-magnification-tagmagimageheader).
All the API calls (MagInitialize, CreateWindow, MagSetWindowFilterList & MagSetWindowSource) are successful. There are no API call failures or mistakes in the code flow in terms of Initializing creating, setting desktop area & assigning filter list.
DWM (Aero theme) is turned off (as per reference: https://learn.microsoft.com/en-us/windows/desktop/api/magnification/nf-magnification-magsetimagescalingcallback)
I couldn't find any resources related to this topic even after researching for about 3 days. I have to use Magnification APIs because I have the need to capture windows that stays behind other windows on the desktop.
Any help would be appreciated.
Update 1:
I figured out that the application is able to capture the screen only when Aero theme is enabled and that contradicts with the statement in https://learn.microsoft.com/en-us/windows/desktop/api/magnification/nf-magnification-magsetimagescalingcallback.
I'm not sure how could I make it work on Operating systems with Aero theme disabled or not available by default.
I'm trying to run my app on Android x86 in VirtualBox, and I've hit a small but annoying problem. I've not had this problem before, when I had the VM at the tablet resolution I was mimicking. However, I'm now running the VM at and writing the app for a smaller (phone) resolution. The problem is that the layout looks fine in eclipse and on the actual phone, but everything is shifted in the VM. The resolution and pixel density are supposed to be the same in all three cases, so I'm not sure what to do. The app still functions, but I would prefer the various views to be where they should and look correctly placed, instead of being shifted left and up. It's almost as if everything is drawn correctly in a subset of the screen. Thanks in advance for any help!
I've searched every place I could think of, but nobody seems to have had this issue or didn't bother asking about it.
I just installed Ubuntu 11.10 freshly with the gnome fallback shell. Everything works perfectly fine, except for one thing.
My WINE applications start on the wrong screen, this isn't really a big issue, but when I drag the window to my main screen, the mouse doesn't work on the application anymore. The app doesn't freeze, and is fully responsive to keyboard input, I just can't click on anything anymore.
My specs (relevant):
- NVidia Geforce 540M
- 1 laptop screen 1366x768
- 1 Samsung Syncmaster SA550 27" - 1920x1080
Thanks in advance!
Did you create the application on a resolution smaller then the current on your pc?
If so, do the following (I have a laptop with 1366x768 on the internal monitor and 1920x1080 on the external monitor):
Open winecfg
Check the Virtual Desktop checkbox and set the size to the largest resolution you are going to use
Start the app and check if it's working properly now (You can check that with the battlenet launcher :))
Start winecfg again and uncheck the Virtual Desktop box
What can be the cause of my Windows CE 6.0 installation to turn to black screen after initial loading ? I built the Win CE 6.0 myself. After initial screen displaying Win CE 6.0 logo with progress bar reaching 100% the screen turns black.
Is there any way to debug, test or emulate the run time image before deploying.
I have not a real hardware in my development environment to test it.
I just built the image and sent to the client for testing.
I based the Win CE image on Board Support Package from the ICOP company. The target touch panel is ICOP with Vortex86DX chipset.
Every possible, permutation, combination results in black screen. I disabled all debuging techniques (KITL, ... ) without progress.
Please, give mi some advice where and how to find the problem.
Thanks in advance.
For all those who have similar problems as mine I will give the solution that worked for me.
In the Project properties\Building Options must be unchecked everything and specially KITL and all debugging options. In addition the project must be built in Release mode.