I know that this question is not only related to Matlab, but I'm asking how to implement a specific workaround in Matlab.
I'm running Matlab (2019a, Update 3, but this also happend in 2018b) on a Lenovo P52 with SuSE Leap 15.0. It has two graphic cards, an onboard Intel card and a Nvidia card:
$> lspci -nnk |grep -EA 3 "VGA"
00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e9b]
Subsystem: Lenovo Device [17aa:225f]
Kernel driver in use: i915
Kernel modules: i915
--
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:1cba] (rev ff)
Kernel modules: nouveau, nvidia_drm, nvidia
70:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader [10ec:525a] (rev 01)
Subsystem: Lenovo Device [17aa:225f]
As you can see, I'm using the Intel card.
Matlab runs fine with this setup, until I'm running appdesigner or the Add-On Explorer (or any of the components from the Apps-Tab in the main window). The contents of the appdesigner-window only appear if I change the window's size, and any changes are only displayed after a resize (there might be other possibilities to force the contents to show up, but I haven't figured them out).
I guess all these components internally use the chrome browser. The native (that is, not shipped with Matlab) chrome browser shows (nearly) the same behaviour on my system. However, it throws an error when started:
$> chromium
[32273:32273:0703/095509.613762:ERROR:buffer_manager.cc(488)] [.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error from previous GL command
Obviously, this problem is not related to Matlab. However, if I start chrome with the --disable-gpu flag, it works as expected.
The Malab-related question is: Is there any way to tell Matlab to call its internal chrome with this flag?
Many rendering issues I've had, if they couldn't be helped by updating drivers and such, could usually be fixed by adjusting the opengl settings. Assuming it has defaulted to hardware, you could try setting it to either software or hardwarebasic (a stripped-down set of graphics features) and see if that helps.
...and don't forget you may need to save the new settings for future sessions:
opengl('save', 'hardwarebasic');
Related
I've browsed through many topic and answers related to the emulator crashing issue. Yet, I still have no clue how to resolve this issue.
My setup:
Windows 10 x64 laptop - 16GB RAM - Intel Core i7-6820HQ CPU # 2.7Ghz
Android Studio 2.3.3
Java JDK jdk-8u141-windows-x64
HAXM installed and activated
When I open Android Studio, I can start the emulator without any issues.
(see picture here)
But when I try the same from the commandline, the emulator does not startup properly and stops. (see picture here)
I've tried:
HAXM 6.0.6 and HAMX 6.1.3
Graphics: Software GLES 2.0 (instead of auto)
RAM: lowered to 512 (instead of the default 1536) as mentioned in many posts
Try a emulator with lower resulution (like Galaxy S 800x600) as also mentioned in many posts
Use arm image to trigger arm emulator
Add MB behind certain values in the ini file
Set the width/height value to 0 in the ini file
Turn off the camera (front and back) emulation
Disable multi-core CPU (since it mentioned behind it that it's experimantal)
I tried the emulator in the tools folder and the emulator folder
What am I doing wrong here?
What else can I try?
Did I forget a combination of the above mentioned items?
My end goal:
I want to make this emulator part of my CI cycle and for that I need to run a command line (or powershell) script on a Hyper-V machine (in Azure), to start this emulator, so I can hook it up to my selenium-grid (via Appium).
I had the same problem, I fix it by updating my windows (windows 10) to the latest version (windows 10 version 1903 build 18362) and take the optional update (KB4512508)
in the windows update setting..
I'm using:
- Windows 10 Enterprise.
- AMD A10-4600M APU withe Radeon HD graphics.
- ram 512.
Try this solution it worked for me.
to run the emulator in the new Android Develop Studio, I need to turn on the virtualization support (VT-x) on my guest windows 7 running in KVM, which in turn is on RHEL6.
Google shows we need vmx & vme in the guest processor definition, which I have them as 'require' from dumpxml. But in Android Develop Studio in my guest win7, it still complains about missing virtualization support.
Cannot launch AVD in emulator.
Output:
emulator: ERROR: x86 emulation currently requires hardware acceleration!
Please ensure Intel HAXM is properly installed and usable.
CPU acceleration status: HAX kernel module is not installed!
I then download 'haxm-windows_r05' and run 'intelhaxm.exe' to install it, with error:
VT not supported
This computer does not support Intel Virtualization Technology (VT-x). HAXM cannot be installed.
Please refer to the Intel HAXM documentation for more information.
In summary, my guest (windows 7) on KVM (running on RHEL 6) can not turn on Intel Virtualization Technology (VT-x).
Thanks for any help
Andy
Unfortunately, RHEL6 lacks support for Nested Virtualization. RHEL7 does but it's still very premature and new changes keep getting added. Your best bet is to install the current upstream kernel. To enable Nested Virtualization, load kvm_intel with "modprobe kvm_intel nested=1".
And ofcourse, you need to advertise vmx in your cpu definition.
I was trying to play with several tiny operating systems in an emulator but got stuck with Contiki in QEMU. Ideally the compiled executable should be run as a kernel in QEMU. For all OS's I was playing with I used this simple command to run executables in QEMU:
qemu-system-platform -nographic -kernel compiled_executable
In the case of Contiki, QEMU freezes regardless of any target platform the executables are compiled for, even for target platform "native", which according to the documentation, is built with "x86 gcc".
I also tried ARM-based platforms with the same freezing issues. If I specify a correct CPU model (e.g. cortex-m3 for cc2538dk), I received a segmentation fault instead.
I am wondering if I was missing any steps to cause the QEMU to freeze. Does it mean that the compiled executable cannot be treated as kernels (yet), unless I provide some QEMU-specific codes to initialize QEMU as a "board" for Contiki?
The native platform is used to build a "natively" (i.e. on Linux or other OS) executable image of Contiki - an userland app, rather than an OS kernel.
I have HD7690M XT (an overclocked version of 6770M) and Android emulator (sdk tool rev.20) for ICS failed to start hardware OpenGL ES emulation with the following error message:
emulator: ERROR: Could not load OpenGLES emulation library: Could not load DLL!
emulator: WARNING: Could not initialize OpenglES emulation, using software renderer.
and with software renderer I got really bad color resolution (please see the attached screenshots). I suspect that this is due to the software renderer (no such problem in emulating earlier versions of Android). Have someone who can run hardware emulation seen this problem?
What graphic cards can hardware GPU emulation run on? (You can see detailed debug messages by executing $ emulator -avd your_avd_name -verbose)
I had the same problem on my Windows 7 (64-bit) machine. The reason was that the libOpenglRender.DLL could not be located. I added C:\Program Files (x86)\Android\android-sdk\tools\lib to the PATH variable and can start the emulator now without error message. However, I don't see a difference in quality of the graphics compared to your screenshot.
Copy the file below from SDK\tools\lib to SDK\tools.
libEGL_translator.dll
libGLES_CM_translator.dll
libGLES_V2_translator.dll
libOpenglRender.dll
Copy all the dll files from tools\lib to tools.
Add toos\lib to PATH works, the only thing you need to remember is to add it in the HEAD of the PATH, not the end.
Check this post:
https://code.google.com/p/android/issues/detail?id=33336
I am using EclipseMe on Ubuntu. I want an emulator that can emulate mouse movements on screen.
Is there an s60 emulator for linux?
Edit:
Does net beans has an in built emulator that can emulate mouse movement on device screen?
Netbeans uses the Sun Wireless Toolkit.
The JavaME emulator it contains can me made into a touchscreen emulator. Read the accompanying documentation, it should be as simple as setting a variable inside a configuration file before stating the emulator.
You can find the specification for MIDP (the top layer of the JavaME platform you're probably targetting) at http://jcp.org/en/jsr/detail?id=118
Look at the javax.microedition.lcdui.Canvas class, you will find several methods used to deal with "pointer". While they are more often used to handle touchscreen event, they also map to mouse/joystick clicks on emulators.
You can definitely get the MIDP pointerDragged events when running the emulator on Linux.
This is basic MIDP, no need for fancy JSR-226 (e-swt) support.
The Windows only Symbian Emulator (EPOC) is being scrapped for a QEMU based emulator that will run on all platforms. This will likely be available within 6 months or so.
At the moment, I run Windows XP inside VirtualBox on my Mac for Symbian development. It works fine, but is of course not the ideal solution.
The full symbian OS emulator with application interfaces for Java and Symbian C is windows based unfortunately.
I usually get a MS Windows Vista install disk and install that into a VM like VirtualBox and than install the symbian SDks on top of that..
Works best on those 4 core desktop 64-bit computers now on sale for $687 as you get access to full 8 gig ram and close to 1 terabyte hard drive..