Posts by PANiCnz

Working successfully for me now.

Another set of logs if it helps -> https://paste.libreelec.tv/unlost-alaya.log

This combination works LibreELEC-Generic.x86_64-13.0-nightly-20260714 + Flatpak 12.80.7.12 + VacuumTube 12.80.7.0

LibreELEC-Generic.x86_64-13.0-nightly-20260801 doesn't work, Flatpak & VacuumTube versions appear to be the same.

For what its worth ChatGPT blames the update of ibdisplay-info from version 0.3.0 to 0.4.0 on July 28.

Same issue here with Vacuumtube and the lastest nightly build.

Running a nightly from the last week on a rk3399 box and get a black screen when playing back h264 content? Is this a known issue? If not I'll grab some logs etc and do a separate post.

Loving VacuumTube! Interface is a bit sluggish on my ROCK 4C+ but great on my x86 box.

I've had it running in the past, but have since got rid of my compute stick. From memory there is a special build floating around on the forum you can use and then upgrade from there. There are definitely instructions out there on how to do it.

Is there a possibility we might see LE running on the Dragon Q6A?

Supposedly has mainline support

For a RK3399 board how do these images differ from the standard nightly's? More or less features? or much the same?

Either way will give it a go on a Rock 4C+.

For what it's worth there appears to be two versions of this board, the earlier v1.2 with the M2 slot, and a latter 1.41 without the M2 slot. Not sure if this impact compatibility etc.

Are any of these images likely to work with a Orange Pi Compute Module 4? I see there is an image for the SOQuartz, but the Orange Pi seems easier to source.

Quote from HarryH

Before I look deeper into the code, does this "touch /storage/.config/argon40_rc.lock" don't work for you?

Regarding the range. I have seen your post in Argon40 forum. I can only report from a buddy of me, who is owner of a Argon One V1 and has added the IR Receiver manually. He reported a bad response to the IR signal until he has made a slot/hole in the transluent red plastic cover. Before made such irreversible changes you should check without the bottom assembled.

Edit:
In a short test with my universal remote control, I got a distance of about 4m/13 feet when I pointed the remote control frontal to the argon case. The further you go away, it seems more important to keep the remote control at the same heights as the case/IR sensor.

Thanks "touch /storage/.config/argon40_rc.lock" sorted it.

Found my range issues are likely being caused by the remote rather than the sensor. Range on my SofaBaton U1 is terrible compared to my Flirc Skip 1s. Unfortunately, the range of devices supported by the Skip 1s is a big lack luster.

The reason Confluence doesnt work with Omega is there have been changes to the skinning API. Change the version number in the XML file bypasses the version check so Confluence will run. But given you haven't fixed the underlying incompatibility you shouldn't expect it to run perfectly.

I've installed version 0.0.10, and it looks to be performing as expected.

My remote is no longer working. Am using a SofaBaton, with the onboard IR receiver and a mecool_kii_pro keymap.

Edit: ignore that all sorted. Has anyone else found the range on the v3 IR receiver to be crap? I'm barely getting 6ft. Using a FLIRC as a temporary solution but would rather use the builtin receiver.

Can the addon be configured so it doesn't override /storage/.config/rc_maps.cfg on boot? I've changed it to support the remote I'm using but after a reboot its back to the argon40 remote.

Fan pulses seem to have stopped with 0.0.8, but i don't think the double press works. Will try the alternative settings in the config file shortly.

Quote from Da Flex

If the on/off frequency of the fan is pretty constant, then I would say it's expected behavior. My power LED (always-on expected) had random on/off cycles without that fix.

Yeah its constant. Kinda annoying but not too bad.

Quote from HarryH

PANiCnz ,

your are the second which reports this behavior with Argon One V3 in combination with 0.0.7. So there seems really to be an issue within the current code.
Currently I can't reproduce with my V2 case... it could takes longer to find the root cause.

As long the CPU temperatur is below the first threshold, the fan should be off. Pulsing is possible if the current temperature is around the threshold. 42c is far away from the 55c default value. I fear I have possibly insert this bug as I switched over to the Argon Register Helper methods, which has a mechanism included to differentiate the firmware versions.

From the testing with Argon V3 case exists a version 0.0.6d, but this version should only be used with Argon One V3 cases, because the commands were changed for the new firmware. I don't know if there are also V2 cases with this type of firmware in the wild.

You can give this a try, until I have isolate the bug. Please don't forget to reboot after you have uninstalled the current plugin version.

Display More

After about 30 seconds of testing this seems to solve the problem. Haven't tested any of the other features but the fan isnt pulsing at this stage.

Quote from HarryH

Add-On was update to version 0.0.7.

• make it work with LE12 nightly builds after 2023/11/16.
  Raspberry Pi Tools - GPIOZERO - LE12 Issues
• supports the new firmware version of the Argon One V3 (RPi5) case

Thanks for maintaining this addon its great.

Using a V3 case with an LE12 nightly and addon v0.0.7, the fan pulses every 20-30 seconds. Is this expected behavior? LE is reporting temps of about 42c and fan thresholds are the default.

From memory LE should run well with a discrete Intel card like Arc A380 if you want to retain your existing hardware. But I suspect a RPi5 would provide a comparable experience for far less power consumption.

I've got a RPi5 as a secondary setup and I can't notice any difference with my J4105 based HTPC in the lounge. I've got the RPi5 booting off a NVMe drive and it's a slick experience.

Should I expect deinterlacing to be working with a RPi5 with DRM Prime? Working as expected on a 12 nightly but not with 11.0.6.

Have gone back to 12 but can go back to 11 and dump the logs if it's expected to be working.