I am using Windows and Kioware to start my Intel Stick computer in kioks mode. The kiosk is showing a webpage and everything looks fine, until a white screen randomly appears and there is no change to interact with the webpage.
I use Kioware lite for Windows that runs the kiosk using Chromium.
I use a Samsung Touch Screen TV with HDMI connected to an Intel stick (Windows 10).
Can anyone tell me the possible causes for this to happen?
Related
Please apart from the 7" LCD touch screen, which other lcd screen can work with raspberry pi using windows iot core operating system
It is recommended to use the screen device which is listed in the Hardware compatibility list. As mentioned in the document, this list is not exhaustive. There are many other peripherals not listed on this page that are compatible with Windows 10 IoT Core. You may try with other screen, maybe it is also compatible. If you just want to use a display screen without touch input, in general the screen with HDMI interface is usable.
Apple iMac & MacBook lineup uses high-resolution display branded as "Retina Display" which by default, macOS will set the screen resolution below the native screen resolution. For example on the 13-inch Retina MacBook Pro, which comes with native resolution of 2560-by-1600, macOS will set the default resolution to 1280-by-800 with option to scaled to other screen resolution (1024-by-640, 1440-by-900, and 1680-by-1050) on Settings app.
However, on Windows (including the latest version) screen resolution are by default, set to the native screen resolution with "Scaling" function to increases the elements sizing. For example on a 15-inch laptop, which comes with a Full HD display, Windows will set the default resolution to the 1920-by-1080 with scaling set to 100% but recommended to 125%. Setting a higher scaling in turns result in certain elements displayed blurry.
Hence, why is this case?
An operating system can work without screens. You could for example start your computer (either running Windows, or MacOSX, or Linux), and run some application app (or app.exe on Windows) on that command line.
Now, imagine you type app (without the ENTER key) in some command window, unplug your screen, and type the ENTER key. You app has still started (and perhaps detected that no screen is available, only if that app is a GUI application opening a window by using some widget toolkit). If your app is not a GUI application but a command line one (eg cp which copy files) it can successfully execute.
In practice, your screen is today used by some display server. And your application don't show directly pixels on the screen: it interacts with your display server which generally is the only process accessing the screen (more precisely, your graphics card).
So you need to learn how to tune or configure your display server. And that of course is operating system and display server specific. On MacOSX and and Windows and on Linux they are very different (and Linux even has several ones, e.g. Xorg or Wayland). On MacOSX it is Quartz.
I can't get to work my code or even the examples provided on http://aframe.io/examples/ on HTC Vive and Firefox 59.0.2 (Windows 10 on a MSI laptop computer with GTX 1060, Geforce drivers 3.13.1.30). Tried also with Firefox Nightly.
The scene loads and the controllers are visible. The headset is not tracked and does not change the scene. Then SteamVR starts and shows a "firefox.exe unresponsive" message. From this point, if I enter VR mode, the headset is not tracked.
Go to NVIDIA Control Panel and set Firefox to use with High Performance Mode. The laptop is probably falling back to integrated graphics.
If you use a VR browser like Supermedium, this is automatically handled for you.
I'm trying to use Microsoft's Remote Display Control (version 2.03, copyright 2000) to view my Windows CE device on the desktop (not only is it nice for my "regular" handheld device, because it makes the display easier to see, especially in zoom mode, but it is even more important for the other devices I have to test, whose screen is too dim for me to make out exactly what's on the screen (it's like the vision test from h311) - which is necessary for debugging, of course) but for some reason I am not able to enter key strokes on the device while it's connected to the desktop. I can enter them neither on the desktop/in RDC nor on the handheld device itself while connected via RDC.
This, of course, is untenable (no pun intended).
The .exe is created in XP Mode, copied to a "holding tank" in Windows Explorer on the Windows 7 machine, then copied from there to the handheld device.
Then I connect from the handheld device by selecting Start > Programs > cerdisp > selecting OK in the "Remote Display Control" dialog, then Connect, then OK (and I do connect), then run the app on the desktop in the "WindowsCE" window that RDC supplies. It allows me to select menu items, but the keyboard is broken/mute...???
Is this a known bug? Is there a workaround? The desktop is a Windows 7 machine.
Doing a "cold boot" of the handheld device caused it to come back to responsiveness, keyboard-wise. These devices are betimes more peckish than a put-upon puddle of Platypi.
I am developing apps for window phone 7 using phonegap. I am facing the problem when launching the apps in emulator. I can see the splashscreen but not the index page. I just see the white blank screen after splashscreen. While running on emulator I got message "this computer do not have required graphics processing unit configuration."
I test with other in built apps with visual studio for window phone. It work fine.
What is the problem? With my graphics or something else.
Did you set up your app to launch index.html. If you have change the tree it's not a problem. You can change it in CordovaLib, CordovaView.xaml, CordovaView.xaml.cs. In this one, you will find StartpageUri. Be sure that is pointing on your file