I’m hoping somebody can help. I recently installed Tizen Studio 3.7 with only the wearable Tizen 4.0 downloads. The emulators worked fine. I then upgraded my Galaxy Active 2 to TIzen 5.5 and also updated the Tizen Studio to also have the Tizen 5.5 development tools. I didn’t test the emulators after that. I then installed Visual Studio 2019 with a lot of C Sharp tools, the tizen framework; I hadn’t yet pointed VS 2019 to the Tizen SDK path.
Now, when I try to open the Wearable emulators, I get a message that it has stopped or the emulator stays on the ELF screen and never comes to the watch face.
I saw in another post that a community member asked for logs. “Open the emulator folder, inside that open logs folder you can find “emulator.klog, emulator.log, emulator-skin.log, emulator-skin.log.lck. Along with this emulator logs please provide (.log) file which is present in workspace inside .metadata folder”
I have gathered these logs and posted them in a zip file here. Additionally, since I had VS 2019 installed, I took a dump of the memory of the emulator and included the DMP file in the zip file. I hope this helps identify the problem.
Any questions, please ask and I’ll do my best to help.
UG hax_vcpu_hax_exec: handling INIT for 3
UG hax_vcpu_hax_exec: handling SIPI for 3
UG hax_vcpu_hax_exec: handling SIPI for 2
UG hax_vcpu_hax_exec: handling SIPI for 1
UG hax_vcpu_hax_exec: handling INIT for 1
UG hax_vcpu_hax_exec: handling SIPI for 1
UG hax_vcpu_hax_exec: handling SIPI for 1
UG hax_vcpu_hax_exec: handling INIT for 2
UG hax_vcpu_hax_exec: handling SIPI for 2
UG hax_vcpu_hax_exec: handling SIPI for 2
UG hax_vcpu_hax_exec: handling INIT for 3
UG hax_vcpu_hax_exec: handling SIPI for 3
UG hax_vcpu_hax_exec: handling SIPI for 3
12:28:58.540|16456|I| input| 283|virtio_touchscreen_device_reset
12:28:58.687|16456|I| input| 592|virtio_rotary_device_reset
12:28:58.891|16456|I| input| 510|virtio_hwkey_device_reset
12:28:59.096|16456|I| input| 430|virtio_keyboard_device_reset
12:28:59.197|16456|I| vmodem| 243|virtio_vmodem_reset.
12:29:00.698|16816|I|brightness| 119|current brightness level = 100
12:29:00.808|16816|I| sensor| 409|sensor device capabilty sending 7df
emulator.klog
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Initializing cgroup subsys cpuacct
[ 0.000000] Linux version 4.4.35 (root@e2027971d123) (gcc version 4.8.5 (Ubuntu 4.8.5-4ubuntu2) ) #1 SMP PREEMPT Thu Nov 29 12:31:11 IST 2018
[ 0.000000] Disabled fast string operations
[ 0.000000] x86/fpu: Legacy x87 FPU detected.
[ 0.000000] x86/fpu: Using ‘lazy’ FPU context switches.
Emulator crashes
Hello Community,
I’m hoping somebody can help. I recently installed Tizen Studio 3.7 with only the wearable Tizen 4.0 downloads. The emulators worked fine. I then upgraded my Galaxy Active 2 to TIzen 5.5 and also updated the Tizen Studio to also have the Tizen 5.5 development tools. I didn’t test the emulators after that. I then installed Visual Studio 2019 with a lot of C Sharp tools, the tizen framework; I hadn’t yet pointed VS 2019 to the Tizen SDK path.
Now, when I try to open the Wearable emulators, I get a message that it has stopped or the emulator stays on the ELF screen and never comes to the watch face.
I saw in another post that a community member asked for logs. “Open the emulator folder, inside that open logs folder you can find “emulator.klog, emulator.log, emulator-skin.log, emulator-skin.log.lck. Along with this emulator logs please provide (.log) file which is present in workspace inside .metadata folder”
I have gathered these logs and posted them in a zip file here. Additionally, since I had VS 2019 installed, I took a dump of the memory of the emulator and included the DMP file in the zip file. I hope this helps identify the problem.
Any questions, please ask and I’ll do my best to help.
Thanks very much
Christopher
.log
!SESSION 2020-10-19 00:41:48.306 ———————————————–
eclipse.buildId=3.7
java.version=1.8.0_242
java.vendor=Amazon.com Inc.
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en
Command-line arguments: -os win32 -ws win32 -arch x86_64
This is a continuation of log file C:\Users\cobrien\workspace\.metadata\.bak_0.log
Created Time: 2020-10-19 08:06:11.635
!ENTRY org.tizen.nativecore.csviewer.util.CrashReportUtil 4 0 2020-10-19 08:06:11.636
!MESSAGE [2020.10.19 08:06:11][ERROR] CrashReportUtil.java(73) – Failed to search a project: null
!ENTRY org.tizen.nativecore.csviewer.CrashReportServiceListener 4 0 2020-10-19 08:06:13.834
!MESSAGE [2020.10.19 08:06:13][ERROR] CrashReportServiceListener.java(62) – Failed to pull CrashReport file from /opt/usr/share/crash/dump/muse-server_2679_20201019142921.zip
!ENTRY org.tizen.nativecore.csviewer.CrashReportServiceListener 4 0 2020-10-19 08:06:15.471
!MESSAGE [2020.10.19 08:06:15][ERROR] CrashReportServiceListener.java(62) – Failed to pull CrashReport file from /opt/usr/share/crash/dump/muse-server_2679_20201019142921.info
emulator.log
12:28:30.618| 236|I| osutil| 396|Running with elevated integrity level. Try to respawn.
12:28:30.662| 236|I| osutil| 427|Respawning success. Waiting for child process.
12:28:30.796|17484|I| main| 345|Start emulator…
qemu args: =========================================
“C:\tizen-studio\platforms\tizen-4.0\common\emulator\bin\\emulator-x86_64” “-drive” “file=C:\tizen-studio-data\emulator\vms\W-4.0-circle-x86-preview\emulimg-W-4.0-circle-x86-preview.x86,if=none,index=0,cache.no-flush=on,id=drive” “-device” “virtio-blk-pci,drive=drive” “-drive” “file=C:\tizen-studio-data\emulator\vms\W-4.0-circle-x86-preview\swap-W-4.0-circle-x86-preview.img,if=none,index=1,id=swap” “-device” “virtio-blk-pci,drive=swap” “-enable-hax” “-device” “vigs,backend=gl,wsi=vigs_wsi” “-device” “yagl,wsi=vigs_wsi” “-smp” “4” “-m” “512” “-device” “virtio-maru-sensor-pci,sensors=accel&geo&gyro&light&proxi&haptic&uv&press&hrm&pedo” “-device” “maru-camera,index=0” “-netdev” “user,id=net0” “-device” “virtio-net-pci,netdev=net0” “-device” “virtio-maru-nfc-pci” “-chardev” “file,path=C:\tizen-studio-data\emulator\vms\W-4.0-circle-x86-preview\logs\emulator.klog,id=con0” “-device” “isa-serial,chardev=con0” “-device” “virtio-serial” “-L” “C:\tizen-studio\platforms\tizen-4.0\common\emulator\data\bios” “-kernel” “C:\tizen-studio\platforms\tizen-4.0\common\emulator\data\kernel\bzImage.x86” “-append” “vm_name=W-4.0-circle-x86-preview video=LVDS-1:360×360-32@60 dpi=301 clocksource=hpet consoleblank=0 host_ip=10.0.2.2 aod_color_type=None console=ttyS0 force_pat” “-device” “virtio-maru-touchscreen-pci,max_point=2” “-device” “virtio-maru-rotary-pci” “-device” “AC97” “-device” “virtio-maru-esm-pci” “-device” “virtio-maru-hwkey-pci” “-device” “virtio-maru-evdi-pci” “-device” “virtio-maru-keyboard-pci” “-device” “virtio-maru-vmodem-pci” “-device” “virtio-maru-power-pci” “-device” “codec-pci” “-device” “maru-brightness” “-nodefaults” “-rtc” “base=utc” “-M” “maru-x86-machine” “-usb” “-vga” “none” “-device” “virtio-maru-jack-pci,jacks=charger&usb” “-display” “maru_qt,rendering=onscreen,resolution=360×360,dpi=301”
====================================================
12:28:30.800|17484|I| main| 348|qemu main start…
12:28:30.804|17484|I|emul_state| 733|initial display resolution: 360×360
12:28:30.804|17484|I|qt5_consol| 171|display density: 301
12:28:30.921|17484|I|qt5_supple| 515|* Qt version (compile time): 5.6.0
12:28:30.922|17484|I|qt5_supple| 516|* Qt version (runtime): 5.6.0
12:28:30.922|17484|I|qt5_supple| 517|* working path: “C:/tizen-studio/platforms/tizen-4.0/common/emulator/bin”
12:28:30.922|17484|I|qt5_supple| 518|* binary path: “C:/tizen-studio/platforms/tizen-4.0/common/emulator/bin”
12:28:30.922|17484|I|qt5_supple| 519|* Qt plugin library path: (“C:/tizen-studio/platforms/tizen-4.0/common/emulator/bin”)
12:28:30.922|17484|I|qt5_consol| 153|Display Type: QT5 Onscreen
ram_size 0x20000000
device fd:00000000000003d8
12:28:30.950|17484|I| main| 157|* Board name : Maru
12:28:30.950|17484|I| main| 158|* Package Version: 2.8.0.24
12:28:30.950|17484|I| main| 159|*
12:28:30.950|17484|I| main| 160|* Git Head :
12:28:30.950|17484|I| main| 161|*
12:28:30.955|17484|I| main| 162|* User name : cobrien
12:28:30.955|17484|I| main| 163|* Host name : CO-W8LT
12:28:30.955|17484|I| main| 166|* Build date : 2019-05-07 15:17:07 IST
12:28:30.955|17484|I| main| 175|* Current time : 2020-10-19 12:28:30
12:28:30.955|17484|I| main| 179|* Host Qt version : 5.6.0
12:28:30.955|17484|I| main| 195|* Host SDL version : 2.0.4
12:28:30.955|17484|I| osutil| 165|* Windows
12:28:30.955|17484|I| osutil| 166|* LibPNG Version : 1.6.21
12:28:30.955|17484|I| osutil| 176|* MajorVersion : 6, MinorVersion : 2, BuildNumber : 9200, PlatformId : 2, CSDVersion :
12:28:30.955|17484|I| osutil| 194|* Total Ram : 6174248 kB, Free: 1020820 kB
12:28:30.959|17484|I|net_helper| 122|TCP port 26101 is aleady occupied12:28:30.960|17484|I|net_helper| 178|Emulator base port is 26110.
12:28:30.960|17484|I|net_helper| 662|start sdb noti server thread.
12:28:30.961|17484|I|net_helper| 687|success to bind port[127.0.0.1:26113/udp] for sdb noti server in host
12:28:30.961|17484|I| main| 239|kernel commandline : vm_name=W-4.0-circle-x86-preview video=LVDS-1:360×360-32@60 dpi=301 clocksource=hpet consoleblank=0 host_ip=10.0.2.2 aod_color_type=None console=ttyS0 force_pat sdb_port=26110, vm_resolution=360×360
12:28:33.703|17484|I| vigs| 246|vigs_gl_backend_wgl_check_gl_version:246 – Using OpenGL 3.1+ core
12:28:33.757|17484|I| vigs|2526|vigs_gl_backend_init:2526 – Current GL_VENDOR = Intel
12:28:33.757|17484|I| vigs|2528|vigs_gl_backend_init:2528 – Current GL_RENDERER = Intel(R) HD Graphics 4000
12:28:33.757|17484|I| vigs|2530|vigs_gl_backend_init:2530 – Current GL_VERSION = 3.2.0 – Build 10.18.10.4358
12:28:33.805|17484|I| vigs| 536|vigs_device_init:536 – VIGS initialized
12:28:33.830|17484|I| yagl|1102|[0/0] yagl_egl_wgl_init_ext:1102 – WGL extensions: WGL_EXT_depth_float WGL_ARB_buffer_region WGL_ARB_extensions_string WGL_ARB_make_current_read WGL_ARB_pixel_format WGL_ARB_pbuffer WGL_EXT_extensions_string WGL_EXT_swap_control WGL_EXT_swap_control_tear WGL_ARB_multisample WGL_ARB_pixel_format_float WGL_ARB_framebuffer_sRGB WGL_ARB_create_context WGL_ARB_create_context_profile WGL_EXT_pixel_format_packed_float WGL_EXT_create_context_es_profile WGL_EXT_create_context_es2_profile WGL_NV_DX_interop WGL_ARB_create_context_robustness
12:28:34.013|17484|I| yagl| 320|[0/0] yagl_egl_wgl_get_gl_version:320 – Skipping GL_ARB_ES3_compatibility check
12:28:34.024|17484|I| yagl| 348|[0/0] yagl_egl_wgl_get_gl_version:348 – GL_ARB_ES3_compatibility not supported, using OpenGL 3.2
12:28:39.660|17484|I| yagl| 688|[0/0] yagl_egl_wgl_config_enum:688 – WGL returned 13 configs, 13 are usable
12:28:39.691|17484|I| sensor| 741|initialize virtio-sensor device
12:28:39.692|17484|I| sensor| 768|initialized sensor type: accel&geo&gyro&light&proxi&haptic&uv&press&hrm&pedo
12:28:39.692|17484|I| sensor| 731|sensor device capabilty enabled with 7df
12:28:39.806|17484|I| camera|1786|Device name : USB2.0 HD UVC WebCam
12:28:39.902|17484|I| camera|1886|PixelFormat: YUY2, Frame size: 640×480
12:28:39.903|17484|I| camera|1886|PixelFormat: YUY2, Frame size: 160×120
12:28:39.903|17484|I| camera|1886|PixelFormat: YUY2, Frame size: 176×144
12:28:39.904|17484|I| camera|1886|PixelFormat: YUY2, Frame size: 320×240
12:28:39.904|17484|I| camera|1886|PixelFormat: YUY2, Frame size: 352×288
12:28:39.904|17484|I| camera|1886|PixelFormat: YUY2, Frame size: 1280×720
12:28:39.905|17484|I| camera|1886|PixelFormat: YUY2, Frame size: 640×480
12:28:39.905|17484|I| camera|1886|PixelFormat: MJPG, Frame size: 640×480
12:28:39.905|17484|I| camera|1886|PixelFormat: MJPG, Frame size: 160×120
12:28:39.906|17484|I| camera|1886|PixelFormat: MJPG, Frame size: 176×144
12:28:39.907|17484|I| camera|1886|PixelFormat: MJPG, Frame size: 320×240
12:28:39.908|17484|I| camera|1886|PixelFormat: MJPG, Frame size: 352×288
12:28:39.908|17484|I| camera|1886|PixelFormat: MJPG, Frame size: 1280×720
12:28:39.909|17484|I| camera|1886|PixelFormat: MJPG, Frame size: 640×480
12:28:39.913|17484|I| camera|1908|Elapsed time : 0.190830
12:28:39.913|17484|I| camera| 281|[cam0] Native Camera mode
12:28:39.913|17484|I| camera| 294|initialize the maru-camera0 device
12:28:39.942|17484|I| nfc| 270|initialize nfc device
12:28:39.963|17484|I| input| 267|virtio_touchscreen_device_realize: 2
12:28:39.964|17484|I| input| 576|virtio_rotary_device_realize
dsound: Registering endpoint notification callback succeeded.
dsound: (dsound_create_thread) Done
dsound: (dsound_audio_in_init) success
dsound: (dsound_audio_init) finished
12:28:40.395|17484|I| esm| 125|virtio_esm_device_realize
12:28:40.396|17484|I| input| 494|virtio_hwkey_device_realize
12:28:40.397|17484|I| evdi| 232|initialize evdi device
12:28:40.397|17484|I| pkgs| 78|ADDON PATH: C:\tizen-studio\platforms\tizen-4.0\common\emulator\bin\..\..\..\wearable\emulator-images\add-ons
12:28:40.399|17484|I| pkgs| 234|pkgs: cert, ca-certificates-tizen-ext-0.0.3-1.4.i686.rpm
12:28:40.411|17484|S| evdi| 87|virtio queue is not ready
12:28:40.412|17484|I| pkgs| 251|pkg_list: ca-certificates-tizen-ext-0.0.3-1.4.i686.rpm
12:28:40.412|17484|I| input| 412|virtio_keyboard_device_realize
12:28:40.414|17484|I| vmodem| 223|finish the vmodem device initialization.
12:28:40.416|17484|I| power| 209|initialize virtio-power device
12:28:40.417|17484|I|brillcodec| 267|device initialization.
12:28:40.417|17484|I|brillcodec| 268|version: 3.0.0
12:28:40.420|17484|I|brightness| 221|initialize maru-brightness device
12:28:40.422|17484|I| jack| 271|initialize virtio-jack device
12:28:40.423|17484|I| jack| 285|initialized jack type: charger&usb
12:28:40.423|17484|I| jack| 266|jack device capabilty enabled with 11
12:28:40.424|17484|I|emul_state| 390|VM name: W-4.0-circle-x86-preview
12:28:40.424|17484|I|emul_state| 586|VM data path: C:\tizen-studio-data\emulator\vms\W-4.0-circle-x86-preview
12:28:40.424|16600|I| ecs| 906|ecs starts initializing.
12:28:40.438|16600|I| ecs| 878|Listen fd is 1036
12:28:40.828|17484|W| | 0|libpng warning: iCCP: known incorrect sRGB profile
12:28:40.860|17484|W| | 0|libpng warning: iCCP: known incorrect sRGB profile
12:28:40.873|17484|W| | 0|libpng warning: iCCP: known incorrect sRGB profile
12:28:40.888|17484|W| | 0|libpng warning: iCCP: known incorrect sRGB profile
12:28:40.909|17484|W| | 0|libpng warning: iCCP: known incorrect sRGB profile
12:28:40.923|17484|W| | 0|libpng warning: iCCP: known incorrect sRGB profile
12:28:40.936|17484|W| | 0|libpng warning: iCCP: known incorrect sRGB profile
12:28:40.945|17484|W| | 0|libpng warning: iCCP: known incorrect sRGB profile
12:28:40.960|17484|W| | 0|libpng warning: iCCP: known incorrect sRGB profile
12:28:40.976|17484|W| | 0|libpng warning: iCCP: known incorrect sRGB profile
12:28:40.991|17484|W| | 0|libpng warning: iCCP: known incorrect sRGB profile
12:28:41.003|17484|W| | 0|libpng warning: iCCP: known incorrect sRGB profile
12:28:41.017|17484|W| | 0|libpng warning: iCCP: known incorrect sRGB profile
12:28:41.836|17484|I| ecs| 143|rotation 0 degree with setting: 100,980665,100
12:28:46.725|17484|I|mainwindow| 339|show main window
*********ReSet hax_vcpu->emulation_state
*********ReSet hax_vcpu->emulation_state
*********ReSet hax_vcpu->emulation_state
*********ReSet hax_vcpu->emulation_state
*********ReSet hax_vcpu->emulation_state
*********ReSet hax_vcpu->emulation_state
*********ReSet hax_vcpu->emulation_state
*********ReSet hax_vcpu->emulation_state
*********ReSet hax_vcpu->emulation_state
*********ReSet hax_vcpu->emulation_state
*********ReSet hax_vcpu->emulation_state
*********ReSet hax_vcpu->emulation_state
*********ReSet hax_vcpu->emulation_state
*********ReSet hax_vcpu->emulation_state
*********ReSet hax_vcpu->emulation_state
*********ReSet hax_vcpu->emulation_state
12:28:46.934|17484|I|brillcodec| 327|device reset
12:28:46.934|17484|I| vmodem| 243|virtio_vmodem_reset.
12:28:46.934|17484|I| input| 430|virtio_keyboard_device_reset
12:28:46.934|17484|I| input| 510|virtio_hwkey_device_reset
12:28:46.935|17484|I| input| 592|virtio_rotary_device_reset
12:28:46.935|17484|I| input| 283|virtio_touchscreen_device_reset
12:28:46.944|17484|I| camera|2030|Closed
12:28:46.945|17484|I| camera| 331|reset maru-camera0 device
12:28:46.945|17484|I| vigs| 574|vigs_device_reset:574 – VIGS reset
12:28:46.972|17484|I| evdi| 124|virtio queue is not ready
UG hax_vcpu_hax_exec: handling INIT for 1
UG hax_vcpu_hax_exec: handling INIT for 2
UG hax_vcpu_hax_exec: handling INIT for 3
UG hax_vcpu_hax_exec: handling SIPI for 3
UG hax_vcpu_hax_exec: handling SIPI for 2
UG hax_vcpu_hax_exec: handling SIPI for 1
UG hax_vcpu_hax_exec: handling INIT for 1
UG hax_vcpu_hax_exec: handling SIPI for 1
UG hax_vcpu_hax_exec: handling SIPI for 1
UG hax_vcpu_hax_exec: handling INIT for 2
UG hax_vcpu_hax_exec: handling SIPI for 2
UG hax_vcpu_hax_exec: handling SIPI for 2
UG hax_vcpu_hax_exec: handling INIT for 3
UG hax_vcpu_hax_exec: handling SIPI for 3
UG hax_vcpu_hax_exec: handling SIPI for 3
12:28:58.540|16456|I| input| 283|virtio_touchscreen_device_reset
12:28:58.687|16456|I| input| 592|virtio_rotary_device_reset
12:28:58.891|16456|I| input| 510|virtio_hwkey_device_reset
12:28:59.096|16456|I| input| 430|virtio_keyboard_device_reset
12:28:59.197|16456|I| vmodem| 243|virtio_vmodem_reset.
12:29:00.698|16816|I|brightness| 119|current brightness level = 100
12:29:00.808|16816|I| sensor| 409|sensor device capabilty sending 7df
emulator.klog
BY
16 Apr 2025
Tizen Studio
BY
04 Nov 2024
Tizen Studio
BY
02 Apr 2024
Tizen Studio