Posts by chewitt

Ozone isn't new, it's been around for some years already and nobody took the bait, so I wouldn't hold breath.

It often takes a few weeks for all the Skins to be updated for the final release. Looks like this is one of them. You'll probably find an update ormore status info in the Eminence add-on support thread in the Kodi forum.

It's possible to disable UART output in (u-boot) software even if the hardware is correctly wired. It's a little unusual to see that done, but some vendors do more customisation than others. Those chips don't run hot so I wouldn't be too afraid of pulling the heatsink off for a look.

There are issues in the codec drivers that cause memory (buffer) starvation. Repeated plays using the same codec eventually hit the problem. Swapping between codecs seems to cause them faster. It's nothing specific to S912 and impacts all chips.

I'm told LibreComputer plan further work on the codecs (resuming where last years effort/funding stopped) but that all depends on sales revenues to provide funding, info from Amlogic, and availability of commercial developer resources. It's a large piece of work to line up, so no breath holding.

EDID capture fakes the presence of the TV so LE/Kodi boots and sees an HDMI connection when the TV is turned off. It does nothing more. It is not a magic cure for old TVs with weird resolutions. Ignore those guides/articles.

Start over with a clean LE12b2 install (newer kernel/drivers and RPi firmware than LE11).

If needed you can force the initial boot splash to 16:9 using "video=HDMI-A-1:1280x720M@60" in cmdline.txt but once Kodi runs it auto-switches based on available resolutions (determined from EDID data) so this does not force Kodi to a specific resolution.

<?xml version="1.0" encoding="utf-8" ?>                                                   
<settings version="1">                                                                                                                                       
  <section id="system">                                                                   
    <category id="display">                                                               
      <group id="1">                                                                      
        <setting id="videoscreen.screenmode">                                             
          <visible>true</visible>                                                         
          <default>0128000720060.00000pstd</default>                                      
        </setting>                                                                                                                                                
        <setting id="videoscreen.limitguisize">                                           
          <visible>true</visible>                                                         
          <default>3</default>                                                            
        </setting>                                                                        
      </group>                                                                            
    </category>                                                                           
  </section>                                                                                                                                 
</settings>

Creating /storage/.kodi/userdata/advancedsettings.xml with that ^ content may work to force the initial resolution. If the resolution is not available in the EDID data, it won't work. Start with standard 1280x720 resolution. If the 1360x768 resolution is 1080i it will not work as Kodi only outputs progressive and thus filters/ignores all interlaced modes.

Quote from docsuess84

The IP address makes sense, since that’s the address for the device, but I wasn’t sure how the 445 came into play. How does that need to be formatted if you’re trying to mount it using the sudo mount -t cifs command?

You only need to specify port details when a non-standard port for the protocol is used. LE shares SMB/CIFS on default ports so nothing is needed.

The answer lies under the silver heatsink, but if the 512MB RAM sticker is correct we won't support the board even if it can boot something. All recent LE images need 1GB to run Kodi properly.

garbear ^

I shipped mine to HiassofT some time ago so I'm out of the Slice game.

Quote from Reddirt

Just out of curiosity would it have to be Chrome? Possibly a light weight plain jane browser?

It has to run under GBM, and so far the only one I heard of is Ozone, which is Chrome derived.

This experimental change was added: https://github.com/chewitt/linux/…ebdc0f2c772d153 and there's a fix for VP9 @ 59.94 (already merged upstream) but otherwise no changes. What kind of media are you playing?

Direct to Plane should be used always.

Even if we identify a problem in LE11 the fix will put into LE12 so the first thing to do is update to LE12b2 and test again.

It would be useful to see the system log, so use "pastekodi" not manual copy/paste to pastebin.

Then you need to calibrate Kodi as described (twice) previously

Quote from Reddirt

Are there any plans in the future to replace X11 with a more up to date window system?

Wayland is the only choice out there, but since it doesn't support dynamic refresh rate switching it's not an option. Hence we already moved towards GBM with no Windowing environment. It should be possible to compile the Ozone (Chromium on GBM) browser for LE, but it's probably a large work.

The pi devs are currently looking into an issue related to loss of HDMI sync. It's not specifically about 4K60, but you never know, it might be related

Quote from airflow

2024-04-26 23:20:02.187 T:1340 info <general>: CAESinkALSA::InitializeHW - Your hardware does not support AE_FMT_FLOAT, trying other formats

^ This is harmless and will be seen on all LE installs because almost nothing supports that audio (not video) output format.

First update to LE12b (newer kernels and everything). I would also "mv /storage/.kodi/userdata/guisettings.xml /storage/" and reboot to see if a default Kodi config solves anything? (resolutions are stored in a few places).

The update process does not touch the bootloader or partitioning/filesystems so for an LE11 > LE12 update to fail something would have to go wrong during kernel boot; which is normally visible on-screen (the kernel outputs something).

If not, reinstall LE11 then make /flash read-write with "mount -o remount,rw /flash" and then edit /flash/syslinux.cfg to remove "quiet" from params, then save/exit and reboot. You should now see the system log on-screen during boot. Next redo the LE12 update and take a video using a smartphone in slow-motion mode to see errors (or the point boot stops) on screen. Upload/share the video somewhere so we can review it.

Yes, delete the patch for this test. Just be aware that later tests may require you to reinstate (checkout) the patch again.

NB: "PROJECT=Generic ARCH=x86_64 scripts/unpack bluez" will only unpack/patch the package and "scripts/build bluez" will build the package without requiring the full "walk the tree" process of the buildsystem. It might help speed up the initial "get the patches right" process. If all is good the "make image" command will then package everything into an image.