Posts by Da Flex

Quote from rpistutters

Bump as the sample link will only remain active for another 7 days.

It's better to create a new thread, instead of permanently kidnapping and updating a solved one.

All your questions have been answered here.

Crazy.

Theory 2: Your add-on starts a server application, which needs some time to come up.

So try this autostart.sh:

#!/bin/sh

(
sleep 3
/usr/bin/sh /storage/tvmosaic/start2.sh
) &

If this works, you can play around with sleep time (sleep 2 for two seconds, sleep 1 for a second).

I had my moments with old hardware and Windows versions. It feels like a big waste of former lifetime, and still is a waste of time.

Theory: /etc/profile initializes environment variables for add-on's, but will only get executed when starting a shell session.

To include this process into your script, try:

#!/bin/sh

. /etc/profile
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:${TVM_ROOT_DIR}/lib
export TVMOSAIC_ROOT_CONFIG_DIR=${TVM_ROOT_DIR}
${TVM_ROOT_DIR}/tvmosaic_server

Quote from John_T

Thanks for all the answers. Is there any possible (other) way except using an USB extension cable to a wireless operation of my RPI 4 at a 6 feet distance?

Get a Bluetooth adapter with an antenna and a Bluetooth keyboard. This should provide best signal range.

Unfortunately they are both USB-dongle-based, so you can't do anything to increase signal range.

My research says that your new WiFi adapter needs an RTL8812AU Linux driver, and milhouse currently includes that driver into LE.

Chances are, the driver hasn't been included into LE's major release, yet, but maybe it's already available as test build. Activate test builds (a.k.a. milhouse builds) this way:

1. go to Settings -> LibreELEC -> Updates
2. click Show Custom Channels
3. click - Custom Channel 1
4. insert http://milhouse.libreelec.tv/builds/master/RPi4 and click OK
5. click Update Channel
6. click Milhouse-9.80
7. click Available Versions
   
8. click the first entry at the list of test builds (not the highest number)
9. confirm the update

Hopefully this update will make your driver available, and the WiFi adapter should work without any further configuration.

Good luck!

1. remove the second line . $(dirname $0)/incl
2. replace the third line by export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:${TVM_ROOT_DIR}/lib
3. find the value of variable TVM_ROOT_DIR by: echo $TVM_ROOT_DIR
4. create the line export TVM_ROOT_DIR=/YOUR_TVM_ROOT_DIR

Result should be like (/YOUR_TVM_ROOT_DIR replaced by the result you found at point 3):

#!/bin/sh

export TVM_ROOT_DIR=/YOUR_TVM_ROOT_DIR
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:${TVM_ROOT_DIR}/lib
export TVMOSAIC_ROOT_CONFIG_DIR=${TVM_ROOT_DIR}
${TVM_ROOT_DIR}/tvmosaic_server

Yes, by using a tvservice command line option inside an autostart.sh script. However, I'm sure you want to turn the display on again, but that's a problem. My tests gave me a Kodi error when trying to turn the display on by tvservice command.

Maybe it's just a script challenge to stop and start Kodi at the right time (before and after turning the display off/on). But without Kodi running, there probably must be found a different way to get an event for display wake-up.

Then post the start2.sh script please. When it's a large script, use a link to Pastebin for publishing.

Start another simple shell script (test file creation etc.) from autostart.sh to be sure that shell-script-to-shell-script works.

Cool. Using a smart phone app might be easier than the IR approach. Your choice.

If it has been working before, better HDMI cables might help. Maybe volume change increases data rate, and one or both of your HDMI cables can't handle that data rate. HDMI 2.0 or 2.1 standard cables work fine for RPi 4.

At config.txt you can try hdmi_safe=1 for maximum compatibility among devices.

Other users do RPi -> AVR -> TV without problems, so I think your AVR interrupts HDMI connection. Try RPi -> TV -> AVR instead.

Quote from bluelionpiper

For kicks and grins I created the file and copied it over like I did with advancesettings but I'm not sure I dropped in the right country code as IEEE doesn't have a code for the USA but does for my region (Eastern US), which is a 2. Now I don't see the 5GHz SSID at all.

Country ID's are for countries, not for regions inside countries. That means LE's default country US already fits for you, and there is no need to create that file.

So you're using the right WiFi configuration, but it looks like the WiFi signal isn't strong enough. You have to buy a WiFi adapter with an antenna for your WiFi surrounding, like the one I mentioned above. That will improve signal strength.

Quote from bluelionpiper

I'm running LE 9.2.1. is there such an interface for this version or do I need to create the config and push it over?

You already learned how to use the nano editor, right? If the file doesn't exists, then you have to create it. It's the same procedure like on your advancedsettings.xml problem:

nano /storage/.config/modprobe.d/cfg80211.conf

Then add this line, but replace US by your country ID (IEEE standard):

options cfg80211 ieee80211_regdom=US

Thanks for testing. Remove the (...) &, which makes the call a background process. Make sure both scripts have executable permissions (chmod +x).