I wan't to use the camera in my application but when I ran the emulator it shows this:
And this is my setting:
Try this:
Right-click on the Desktop and click Nvidia Control Panel. Click
Manage 3D settings. Click Program Settings. Select SketchUp from the
drop-down list. There are five settings that you need to configure:
Anisotropic Filtering set to Application Controlled.
Antialiasing FxAA set to On.
Antialiasing Gamma set to On.
Antialiasing Mode set to Application Controlled.
Open GL set to the name of the video card that you have.
This might remedy the situation where you have incorrect OpenGL settings. However if you have an old card with a small amount of VRAM you might unfortunately be unable to run the emulator of that system.
Related
I'm happily using x2go to connect to a remote Ubuntu Server 16.04 with XFCE installed from my local pc with a local resolution of 1920x1080 on a HiDPI screen (13''). If I run the x2go client from a virtualized Linux (Linux Mint 18.03 with XFCE), everything works well and I can see a really sharp image of the remote desktop. Problem is, when I try to connect directly from Windows 10 the image is blurred and the resolution is wrong. I tried to play around with the x2go client settings but no way, the image is always terrible. I also tried to use PyHoca and different X-servers but the result is the same.
Is it a well-known problem? Any suggestion on how to fix it?
Thanks in advance.
I had a very similar problem: A Dell laptop with an Nvidia graphics card, having a resolution of the built-in flat panel of 1280x800. I connected this to an external screen with HDMI with a resolution of 1920x1080. However, X2Go seemed to pick up the resolution of the built-in screen instead of the actual screen, making everything seem blurry (interpolating 1280x800 to 1920x1080).
This is what fixed it for me: Navigate to the C:\Program Files (x86)\X2GoClient\VcXSrv\ directory in Explorer. Select the vcxsrv.exe file and right-click it, choosing Properties from the popup menu. Go to the Compatibility tab, and in the Settings section there, select the option "Override high DPI scaling behavior. Scaling performed by:" and then select "Application" in the combo-box below.
Restart the X2Go Client to have its X server start with this new setting.
This fix also solved X2Go Windows Client crashes in my setup.
I have basically the same scenario: connecting from a high DPI Windows laptop to KDE on Debian, in my case for Desktop Sharing. The client would connect okay, but display only a portion of the remote host's screen.
Keyboard shortcuts would not scroll the client window.
Any attempt to show more (maximize, go full screen, click-and-drag client window border) would seem to work for a second, then crash.
The Compatibility scaling change fixed the instability - no more crashes, yay! - but did lead to slow repaints as noted by Algeboy.
Upgrading to a newer version of VcXsrv also did not resolve the crashes - Compatibility change still required, but screen repaints are quicker.
To upgrade, download and install the latest VcXsrv in its own directory. Using Explorer or whathaveyou, apply the HiDPI setting to vcxsrv,exe.
Start x2go client but don't start a session. Click Options, Settings, then X.Org Server settings tab. Select "use custom x server". Point to the newly installed vcxsrv.exe and click okay. Restart the x2go client.
This apparently takes the version from 1.20.6.0 supplied by x2go to 1.20.14.0 (2022-04).
Screen refreshes are quicker if I minimize all applications on the host, allowing it to repaint the desktop, then restore whatever I want to work on.
I've Installed the newest version of Android studio, including the newest version of HAXM, ndk, sdk and whatever other related dependencies it installs. Intel Virtualization bios setting thingy I can't remember the name of is enabled and I have no trouble in virtual box and such.
I created an empty activity and tried testing it on the phone, works perfectly. Then I tried it on the emulator and there is a problem when it is hardware accelerated. It just opens a white window. The android studio displays 0 errors and thinks it ran the app properly. The graphics card I have is a gtx 1060 6gb. When it is software accelerated it works but is so slow I would rather use a chisel on a rock to draw the application usage.
So if someone knows a fix it would be nice.
Thanks
Well I have discovered that in order to solve the issue you have to go to the sidebar menu click More>Settings>OpenGL ES Renderer and(in my case) set it to Angle(D3D11) or Angle(D3D9) or Swiftshader. After that you simply restart the emulator and the issue should be gone.
For me Desktop native OpenGL and Autodetect based on host(which probably sets it to the first thing) don't work and leave you with a white screen.
In case someone finds this useful, you can set software acceleration as below and this solved the issue for me on Mac OS. (OP also mentions it works with software acceleration)
Tools > AVD Manager
Select virtual device
Click on Edit (pencil icon for me)
Click "Show Advanced Settings"
Look for Emulated Performance - Graphics
Select "Software" option
Current version of the emulator (27.1.3) doesn't work for me. The emulator just shows a white screen. Even playing with the gpu in the .ini configuration didn't work.
Once I downgraded to 26.1.4 (https://dl.google.com/android/repository/emulator-darwin-4266726.zip) the emulator started working again.
It seems that the Android Emulator is somehow conflicting with the NVidia Web driver on Mac OS. I had the latest NVidia Web driver (378.05.05.25f04) installed and I was having this same problem - the white screen whenever I used Desktop Native rendering (or left it at the automatic default which selects that as well).
I tried the Swift Shader as well, it works but the performance is abysmal!
On a hunch, I switched back to the OS X Default Graphic Driver from the Nvidia Pref Pane in Apple menu settings, and the Desktop Native driver is now working great after the computer restart!
The same problem can happen to the lightning fast Microsoft Android Emulators utilizing Hyper-V that work on both Intel and AMD CPU based PCs. The solution is in the same line as the accepted answer. For those who use Microsoft Android Emulators and land here by searching "android emulator white screen", here is the screenshot showing how to solve the problem by changing the default hw.gpu.mode from the default "auto" to "mesa":
So sorry
Check your onCreate method in your MainActivity.java, it should have setContextView(R.layout.activity_main)
I wanted to develop my own watchface for my Gear S2. I found some good documentation on downloading and using the Tizen IDE. All is well, but I'm finding the tweak css/html5-run/upload-switch faces-view-wash-rinse-repeat to be very tedious and time-consuming.
I know I can point my browser (Chrome) to my development workspace and load the index.html up and I surmise that I could tweak what I have, which came from the template to work in the browser if I made the sizes in the css static vs dynamic (absolute vs percentages). But is there a better way? Scouring the Internets Googles have yielded nothing too helpful yet.
moderators: this might be OT for this particular SO. If that's the case, I apologize. A nudge in the right direction would be greatly appreciated, if so.
So, I was able to make a little progress on this myself. I am using Chrome in developer mode, which almost works perfectly when using the developer device emulator. To toggle the device emulator, open developer mode (windows: ctrl+shift+I, OS X: cmd+option+i) and when the tool window opens up, look for the little device button next to the element button in the upper left corner of the developer tools window. When the device emulator open, switch the resolution to 320x320 (top of the window next to "screen").
Now, open your index.html file for your project in Chrome, and you can at least muck around with your css styling.
Now to get around the whole issue of reloading your clock with the default clock in the Java emulator for Tizen, I was able to get my changes to automatically assert when running the new code. The way I did it, though I'm not sure if all of these steps were necessary was:
In the emulated watch:
1. set the screen timeout to 15 mins.
2. set the watch face to your development watch face
In the IDE:
1. when ready, use the button for smart launch (it's the blue button just to the left of the bug button in the tizen web IDE). This is in the Tizen SDK version 2.3.1 build 20150721-1440.
At the time of running your code -- making sure both your emulated watch is running too:
1. In the IDE, click the smart launch button
2. Click over to your emulated watch and make sure it's in focus.
It should update the watch face with your latest changes in realtime. This worked for me, so YMMV, but at least I didn't have to reload the watch face after asserting the latest version.
After migrate Xamarin iOS project to Unified API, the app shows black screen only.
Apparently all resources are not loaded at all.
Not only all images including icon, splash are not loaded, but also all XIBs are not loaded.
Now only default black window screen is shown.
Any advice to solve this?
In some cases XI 8.6.0 new msbuild-based build system can forget to copy some files into the app bundle.
This is fixed in the service release (8.6.1) which is in the alpha channel (right now). You might want to try it to see if this is the issue (if not then please file a bug report so it can be investigated).
I know about firebug and the developer tools for the major modern desktop browsers, but I can't find any way of debugging JavaScript code on mobile browsers.
What are some high level techniques I can use to debug code on mobile browsers?
Android devices can be put into developer mode by going through settings>Phone status then tapping on "Build number" 7 times. This allows you to do a bunch of things (see step 5) including USB debugging. (Some devices might have Build number under Software Info)
To activate USB debugging, look in Settings for the newly appeared "{ } Developer Options", open this and switch on USB debugging. Connect your device using a direct USB connection.
In Chrome on your desktop, in the usual developer tools panel used for debugging, look in the menu for more tools>remote devices. With Discover USB devices selected, you should now see your mobile device on the side.
Select it to see a list of all the chrome tabs you have open and the ability to enter URLs directly.
Selecting one of the links will open up a new window with a mirror of your device screen on the left and all the familiar chrome debug tools on the right. You can still control your device directly or use the mouse on the mirrored screen. It even rotates.
full details on remote debugging from google and how to enable developer mode (link as above) from askvg.com
Android provides a tool set for these purposes:
https://developers.google.com/web/tools/chrome-devtools/remote-debugging/?utm_source=dcc&utm_medium=redirect&utm_campaign=2016q3
Apple does it a similar way:
https://developer.apple.com/safari/tools/
Tutorial: https://css-tricks.com/using-chrome-devtools-to-debug-javascript-in-any-browser-with-ghostlab-2/
You can debug on Safari Mobile with any iPhone/iPad. In Developer menu you can find your device and you can then debug your code with inspector.
If you have an Android Device instead, you can debug on Chrome Desktop (remember to active the debug mode) with chrome://inspect
On the IPhone you can go into settings>Safari>advanced and turn web inspector on
Sometimes I get bugs reported by customers that are not reproducible every time or in our testing. For such cases I recommend Lucky Orange. It records the user activity and also has the option to record console messages.
PS - I'm not an affiliate, I use them for my own projects and like it.
Another solution for basic debugging (which many times is all is needed), is having a console polyfill on mobile without the need to plug into USB on desktop.
mobileConsole is such a console polyfill.
Hope it helps someone, I found it useful.