Posts by Da Flex

Buy one, which will be connected to the DSI port:

• official Raspberry Pi Foundation touchscreen: 7 inch.
• Pimoroni touchscreen: 7 inch.
  

I don't have one of those, but internet research says, they work fine with LE.

Your first log has a CEC adapter error, so I would disable CEC.

I would stay with 9.0.2 until 9.2 is final, because it's the most stable release for all RPi lower than version 4B.

Thanks for testing! Then I'm running out of ideas, because using the same image / config leads to different results on RPi 2 / 3.

PS: Be sure to have the jack completely plugged in at your RPi 2.

Can you test composite while HDMI is active? Maybe composite only works when HDMI is connected.

PS: Do you have the composite issue at your RPi 3, too?

At /usr/share/kodi/system/setting/settings.xml the GUI definitions and default values are stored. They are read-only by concept.

Unfortunately <maximum> is part of the GUI definitions, and not editable by overwriting it at /storage/.kodi/userdata/guisettings.xml.

PS: It should be possible to write a slideshow as a Python script. Then you can set the pause as long as you want.

Just for even more inspiration: Foxbiker did a nice passive cooling RPi 4B case here.

Read here about using composite A/V.

Quote from ninjafuchs

I uploaded the logs via the suggested options in that mode here: http://ix.io/1xhr

You are using LE 9.0.2 on RPi. This combo is known to run very stable.

2019-10-05 20:35:11.438 T:1936855056   ERROR: CProfileManager: error loading special://masterprofile/profiles.xml, Line 0
                                            Failed to open file
2019-10-05 20:35:11.438 T:1936855056  NOTICE: special://profile/ is mapped to: special://masterprofile/
2019-10-05 20:35:11.438 T:1936855056   FATAL: unable to load profile

My bet is a broken microSD card. Follow my above advice to check or repair the card.

Nice to hear you made it!

Interesting for me is that no i2c configuration was necessary, because both devices are using that bus.

Have you been soldered the the RTC module on top of the DAC board?

razmafaz :

We got a showcase about the power button, I'm using an additional status LED, reset is easy, too.

You just have to know where the button / LED contacts of your case are, and connect them right.

If you post those connections to the GPIO, then I can post the script.

Quote from JeffR

ERROR: ffmpeg[E2E2C380]: [AVBSFContext] Channel mapping 2 is only specified for channel counts which can be written as (n + 1)^2 or (n + 1)^2 + 2 for nonnegative integer n

Changing the amount of audio channels at the LE audio settings doesn't help?

Since the latest libwidevine update yesterday, the buffering issue is gone. I can't tell whether ISA or libwidevine has been the cause of the issue, because both are needed to decode the DAZN streams.

Have a look at "Settings -> System -> Input -> Enable mouse and touch screen support". Maybe you have to disable this option to set a resource free for your project.

It works on Armbian, so Kodi itself could be the cause for some low data priority, which eventually leads to data loss.

Especially there could be a tricky tr@de-off when input and output device is the same. I stay with my theory, leaving USB can make it safer.

PS: I found a censored word again: tr@de.

Hey JeffR , what's up?

If you want to read more about LE touchscreen experience, click the last link of vpeter 's signature.

Quote

Interesting note about USB reliability vs. GPIO. Unfortunately I have 22 of these type of cheap touchpanels, and I can't change at this point. (This is for interactive displays at a charity haunted house)

Maybe you can reverse-engineer those panels, and use the connectivity before the USB controller.

Quote from vpeter

Really? Can you clarify more? Any links maybe?

This guy wanted to make RS232 work over USB, but it only worked sometimes:

CH340/CH341 USB to RS232 not working

Of course, if you use standard hardware like a memory stick, then USB works fine.

If you use non-standard hardware with unusual protocols, then stay away from USB, and use a GPIO protocol.

PS: I'm not a kernel hacker, but I think we have to split USB in two levels: USB transmission standard, and the protocols, which are using it. At the protocol level, it seems like some protocols have low priority, so data can get lost, even if the kernel driver is present.

Using USB connection is unsafe. Find a touchscreen, which uses a GPIO protocol, like i2c. The RPi has the same issue, that's why I know.

Use hifiberry-dacplus.dtbo and i2c-rtc.dtbo. According to this both modules have no GPIO conflict.