And they work great on Kodi, so why not as standalone for us as well?

I already use code from that branchmeveric wrote:Looks really good.. you should check if the shadertoy visualizer works that is used for Kodi, that thing is amazing and good looking.
https://github.com/notspiff/visualization.shadertoy
Yes they are, i really love that site there is so much online which you can use with this Display, the only thing was missing was to capture the audio data from somewhere, but this turned out to berooted wrote:Most of those came from the same site he's already using, https://www.shadertoy.commeveric wrote:Looks really good.. you should check if the shadertoy visualizer works that is used for Kodi, that thing is amazing and good looking.
https://github.com/notspiff/visualization.shadertoy
i would contact HK for a replacement !butch2k wrote:Got mine today but it seems there is an issue with the screen, it was a bit loose almost unglued from the board when i opened the package and after setting it up i was greeted by an ugly white band on the left side
There is no console-kit-daemon processlephro wrote:So what does the console-kit-daemon process do?
No one besides you is calling it a daemon.lephro wrote:If there is no daemon, why is this thing called daemon
There is one script that calls mplayer and passes a video/picture to be displayed on the LCD.lephro wrote:And its not a shellscript btw
/usr/local/bin all files with -xbmc in the name are the scripts that are used to start the emulators.lephro wrote:So can you give me any clue where i can take a look in these start commands?
Retroarch has nothing to do with this.lephro wrote:I guess somewhere at retroarch?
I use the same launcher for all frontends. The image was started in 2014 back then EmulationStation was not very good, and Kodi was still called xbmc, therefore the name, but the scripts are versatile enough to run for every frontend, therefore they are used on ROM Collection Browser (Kodi), EmulationStation, and Attract Mode alike.lephro wrote:I guess the xbmc scripts are for handling the launch from kodi. How is the launch from EmulationStation handled?
Yes that is a common issue. Although it might sound fun having every single game in existence in a library for a system, there's no way you gonna play every single game. So I'd highly suggest limiting yourself to the games you really like.lephro wrote:I couldnt get the Kodi version running, since my libary contains too many roms (the scraper would take about a week... i dont have that patience / time).
That's part of the OS and has nothing to do with the OGST console kit. It's a daemon for keyboard and mouse input:lephro wrote:Regarding the "console-kit-daemon":
I got a binary process (not a script.. dunno how you call it in the linux world... i would call it programm^^) that always starts with my OGST that is called / named "console-kit-daemon" which is located in /usr/sbin/. I have no clue what it does or where it came from. I thought thats the thing responseable for the video playing. Does anyone have a clue?
Code: Select all
Shader2LCD shaders/digitalclock.f.glsl
Code: Select all
#!/bin/bash
#
Shader2LCD shaders/digitalclock.f.glsl
Code: Select all
Available Renderers: opengles2 opengles software
Vendor : ARM
Renderer : Mali-T628
Version : OpenGL ES 3.1 v1.r14p0-01rel0.0fe2d25ca074016740f8ab3fb451b151
Extensions : GL_ARM_rgba8 GL_ARM_mali_shader_binary GL_OES_depth24 GL_OES_depth_texture GL_OES_depth_texture_cube_map GL_OES_packed_depth_stencil GL_OES_rgb8_rgba8 GL_EXT_read_format_bgra GL_OES_compressed_paletted_texture GL_OES_compressed_ETC1_RGB8_texture GL_OES_standard_derivatives GL_OES_EGL_image GL_OES_EGL_image_external GL_OES_EGL_image_external_essl3 GL_OES_EGL_sync GL_OES_texture_npot GL_OES_vertex_half_float GL_OES_required_internalformat GL_OES_vertex_array_object GL_OES_mapbuffer GL_EXT_texture_format_BGRA8888 GL_EXT_texture_rg GL_EXT_texture_type_2_10_10_10_REV GL_OES_fbo_render_mipmap GL_OES_element_index_uint GL_EXT_shadow_samplers GL_OES_texture_compression_astc GL_KHR_texture_compression_astc_ldr GL_KHR_texture_compression_astc_hdr GL_KHR_texture_compression_astc_sliced_3d GL_KHR_debug GL_EXT_occlusion_query_boolean GL_EXT_disjoint_timer_query GL_EXT_blend_minmax GL_EXT_discard_framebuffer GL_OES_get_program_binary GL_OES_texture_3D GL_EXT_texture_storage GL_EXT_multisampled_render_to_texture GL_OES_surfaceless_context GL_OES_texture_stencil8 GL_EXT_shader_pixel_local_storage GL_ARM_shader_framebuffer_fetch GL_ARM_shader_framebuffer_fetch_depth_stencil GL_ARM_mali_program_binary GL_EXT_sRGB GL_EXT_sRGB_write_control GL_EXT_texture_sRGB_decode GL_KHR_blend_equation_advanced GL_KHR_blend_equation_advanced_coherent GL_OES_texture_storage_multisample_2d_array GL_OES_shader_image_atomic GL_EXT_robustness GL_EXT_texture_border_clamp GL_OES_texture_border_clamp GL_EXT_texture_cube_map_array GL_OES_texture_cube_map_array GL_OES_sample_variables GL_OES_sample_shading GL_OES_shader_multisample_interpolation GL_EXT_shader_io_blocks GL_OES_shader_io_blocks GL_EXT_gpu_shader5 GL_OES_gpu_shader5 GL_EXT_texture_buffer GL_OES_texture_buffer GL_EXT_copy_image GL_OES_copy_image
Error opening shaders/triangle.v.glsl: No such file or directory
You don't the case is not thermal efficient, using the plastic case and the XU4Q model will always cause the board to overheat.crazyquark wrote:Maybe a silly question but how do you keep an odroid-xu4q cool inside that case?
The fan comes in different qualities, some are very quiet while others are noisy (AF).crazyquark wrote:From the pictures there doesn't seem to be enough clearance inside that case to put a fan in there unless you get the noisy regular odroid-xu4(yes, I am that fan hater from the forums)
It should be possible to redirect other output to the LCD using it as a "second" monitor, but with the 320x240 resolution the information on the screen is very limited, and applications like htop for example don't really show much cause of this.
If I remember correctly mainly due to order problems. systemd loads the modules "too fast" which causes the system not to work properly.
Code: Select all
modprobe spi_s3c64xx force32b=1
modprobe fbtft_device name=hktft9340 busnum=1 rotate=270
Users browsing this forum: No registered users and 1 guest