Posts by awiouy

Quote from nickr

I am having trouble making this as an addon. So far I have (omitting the copyright message:

Code

PKG_NAME="xdotool"
PKG_VERSION="2.20110530.1"
PKG_REV="1"
PKG_ARCH=""
PKG_LICENSE="GPL"
PKG_SITE="http://www.semicomplete.com/projects/xdotool/"
PKG_URL="http://semicomplete.googlecode.com/files/${PKG_NAME}-${PKG_VERSION}.tar.gz"
PKG_DEPENDS_TARGET="toolchain libXtst libXinerama"
PKG_PRIORITY="optional"
PKG_SECTION="x11/app"
PKG_SHORTDESC="This tool lets you simulate keyboard input and mouse activity, move and resize windows, etc.."
PKG_LONGDESC="This tool lets you simulate keyboard input and mouse activity, move and resize windows, etc.."


PKG_IS_ADDON="yes"
PKG_AUTORECONF="no"


PKG_MAINTAINER="vpeter4 ([email protected])"


make_target() {
  make xdotool.static
  mv xdotool.static xdotool
}


makeinstall_target() {
  : # nothing to do here
}


addon() {
  mkdir -p $ADDON_BUILD/$PKG_ADDON_ID/bin
  cp -P $PKG_BUILD/usr/bin/xdotool $ADDON_BUILD/$PKG_ADDON_ID/bin/
}

Display More

I have cribbed this from the existing vpeter/oe github referred to above, plus a bit of what I have gathered from looking up othr addons (both OE and LE). I also have a freshly compiled OE7 tree.

However it doesn't compile. Using

Code

PROJECT=Generic ARCH=x86_64 ./scripts/create_addon xdotool

it eventually ends up with

Code

/home/nick/Downloads/LibreELEC.tv/build.LibreELEC-Generic.x86_64-7.0-devel/toolchain/bin/x86_64-libreelec-linux-gnu-gcc -o xdotool.static xdotool.o xdo.o xdo_search.o cmd_click.o cmd_mousemove.o cmd_mousemove_relative.o cmd_mousedown.o cmd_mouseup.o cmd_getmouselocation.o cmd_type.o cmd_key.o cmd_windowmove.o cmd_windowactivate.o cmd_windowfocus.o cmd_windowraise.o cmd_windowsize.o cmd_set_window.o cmd_search.o cmd_getwindowfocus.o cmd_getwindowpid.o cmd_getactivewindow.o cmd_windowmap.o cmd_windowunmap.o cmd_windowreparent.o cmd_set_num_desktops.o cmd_get_num_desktops.o cmd_set_desktop.o cmd_get_desktop.o cmd_set_desktop_for_window.o cmd_get_desktop_for_window.o cmd_get_desktop_viewport.o cmd_set_desktop_viewport.o cmd_windowkill.o cmd_behave.o cmd_window_select.o cmd_getwindowname.o cmd_behave_screen_edge.o cmd_windowminimize.o cmd_exec.o cmd_getwindowgeometry.o cmd_sleep.o cmd_get_display_geometry.o -march=x86-64 -m64 -Wl,--as-needed -fuse-ld=gold -fuse-linker-plugin -flto  -lm -lrt -lX11 -lXtst -lXinerama
/tmp/ccKzXLSz.ltrans0.ltrans.o:<artificial>:function _xdo_mousebutton.lto_priv.49: error: undefined reference to 'XMissingExtension'
/tmp/ccKzXLSz.ltrans2.ltrans.o:<artificial>:function cmd_mousemove_relative: error: undefined reference to 'XMissingExtension'
/tmp/ccKzXLSz.ltrans8.ltrans.o:<artificial>:function find_display.lto_priv.19: error: undefined reference to 'XextFindDisplay'
/tmp/ccKzXLSz.ltrans8.ltrans.o:<artificial>:function find_display.lto_priv.19: error: undefined reference to 'XextCreateExtension'
/tmp/ccKzXLSz.ltrans8.ltrans.o:<artificial>:function cmd_get_display_geometry: error: undefined reference to 'XMissingExtension'
/tmp/ccKzXLSz.ltrans8.ltrans.o:<artificial>:function find_display.lto_priv.18: error: undefined reference to 'XextFindDisplay'
/tmp/ccKzXLSz.ltrans8.ltrans.o:<artificial>:function find_display.lto_priv.18: error: undefined reference to 'XextAddDisplay'
/tmp/ccKzXLSz.ltrans8.ltrans.o:<artificial>:function find_display.lto_priv.18: error: undefined reference to 'XextCreateExtension'
/tmp/ccKzXLSz.ltrans8.ltrans.o:<artificial>:function XTestFakeKeyEvent.constprop.7: error: undefined reference to 'XMissingExtension'
/tmp/ccKzXLSz.ltrans8.ltrans.o:<artificial>:function close_display.lto_priv.17: error: undefined reference to 'XextRemoveDisplay'
/tmp/ccKzXLSz.ltrans8.ltrans.o:<artificial>:function close_display.lto_priv.16: error: undefined reference to 'XextRemoveDisplay'
/tmp/ccKzXLSz.ltrans8.ltrans.o:<artificial>:function find_display.lto_priv.19: error: undefined reference to 'XextAddDisplay'
collect2: error: ld returned 1 exit status
Makefile:65: recipe for target 'xdotool.static' failed
make: *** [xdotool.static] Error 1

Display More

Now time to cook dinner. Solutions on a postcard etc etc. Thanks guys.

Hello nickr,

If xdottool is only used in combination with chromium, it is maybe easier to ship it with chromium, see eg the PR to add unclutter.

I will have time to assist tonight

Quote from DomJ4ck

Hi. Many thanks for this addon! Works like a charme.

The Spotify-Connect-Web Script has a -bitrate option to specify a custom bitrate.

Is it possible to set the bitrate somewhere in the addon-python files?
Sadly, the addon settings are not providing this option.

Code

./spotify-connect-web.sh --username 12345678 --password xyz123 --bitrate 320

spotify-connect-web/README.md at master · Fornoth/spotify-connect-web · GitHub

Thanks in advance and keep up the great work!
Dom

Display More

Hello DomJ4ck,

Thank you for the feedback. I will add the bitrate option. I will also add an option to select the playback route (auto, HDMI or jack).

I am however away from my computer, so you will have to wait a bit.

Thank you for your patience.

Quote from nickr

How do I convert it to an addon?

Is it as simple as changing this line?

Code

PKG_IS_ADDON="no"

You also need to populate the addon, ie, addon() function, source directory, etc

If you provide me some details about the purpose of xdotool and how it works, I am willing to create an addon, or to add it to the chromium addon.

Quote from Complex_Username

Hi all,

I've just switched from a Raspberry Pi B+ to a ODROID-C2. Prior to that I was running Kodi on a desktop computer as a HTPC. Just setting up my new to me LibreELEC and there's a few things I can't figure out and Google (and this forum) return nothing which is mostly how I configure system settigns such as SSH port, setting up SSH keys and a few other tweaks when / is mounted as read-only please.

I can't find anything relating to this in the wiki either unelss I'm looking for the wrong subject. As a side note anyone have problems posting in Chrome? I've had to blow off the dust and fire-up Firefox just to post this. In Chrome this text entry box appears greyed out.

Thanks

Hello Complex_Username,

According to the code, you can pass parameters to sshd of LibreELEC with the SSH_ARGS variable of /storage/.cache/services/sshd.conf, which is writeable. Eg, to have sshd listen on port 789, set SSH_ARGS="-p 789" in /storage/.cache/services/sshd.conf, and then restart sshd (with systemctl restart sshd, or with reboot).

I never used this option, so I cannot confirm that it actually works, but it might be worth a try.

Please let me know if it makes or breaks.

Quote from PKOneTwo

Still maintaining the stable 7.0 branch.
Is a 7.03 coming?

Different question: would it be possible to make nightly builds (just for latest stable branch and for master branch if changes happen at all)?

v

A1: Maybe. Apart from addons there are not many differences between current head of libreelec-7.0 and release 7.0.2, yet.

A2: It is indeed possible, but no one has done it, yet.

I hope these answers fit the ones you expect

Hello PKOneTwo,

Why don't you roll your own?

git clone https://github.com/LibreELEC/LibreELEC.tv.git
cd LibreELEC.tv
git remote add upstream https://github.com/LibreELEC/LibreELEC.tv.git
git fetch upstream
git checkout upstream/libreelec-7.0
PROJECT=your_project ARCH=your_arch make image

Quote from TonyMac32

Hello Everyone,

Before I start beating my head against the wall, is there a quick and easy reason Emby would refuse or fail to stream video to any player? Using the web quick setup, it gets stuck at the FFMPEG section, not seeming to like any of the options.

Thanks for all the hard work!

In order to help you, I need more information, eg what LibreELEC project (Generic, RPi, RPi2, etc) you are running on, and a log.

Incidentally, hardware transcoding on Rasperry Pi is not implemented, yet. It is work in progress, nevertheless.

I have taken the liberty to wrap the spotify-connect-web project into addons, that I have proposed to LibreELEC.

I am looking for volunteers to test drive these addons.

Unfortunately, the spotify-connect-web project only runs on Raspberry 2 and 3 devices, and overcoming this limitation lies with the spotify-connect-web project. As a consequence thereof, the addons only run on Raspberry 2 and 3 devices.

The addons are available from the LibreELEC repository.

Operation:
1. Install the addon
2. Get your spotify_appkey.key from here
3. Place the spotify_appkey.key in the addon home folder, ie smb://libreelec.local/userdata/addon_data/service.spotify-connect-web
4. Configure Spotify username and password via the addon settings
5. Redirect Spotify streams from your Spotify app to LibreELEC
6. Enjoy!

Further reading:
spotify-connect-web README.md
Spotify Connect forum thread

New with release 91:
- added bit rate to the addon settings
- added playback route to the addon settings
- removed spotify_appkey.key from the addon settings: spotify_appkey.key must be located in the addon home folder
- cosmetic changes

I managed to make it work:
- remove/rename libasound.so.2 from the spotify-connect-web directory
- run ./spotify-connect-web -o hw:0,1 -u username -p password
- no need to create /storage/.config/asound.conf
- do not forget to add your spotify_appkey.key

I guess this can be improved, since the output of amixer hints at mono output.

A addon is on the way, nevertheless!

Until then, please be so kind to share your feedback/requests on this thread.

Enjoy!

I got spotify-connect-web to run, by creating /storage/.config/asound.conf, which was missing.
The content of the file I use is:

pcm.!default {
        type hw
        card 0
}


ctl.!default {
        type hw
        card 0
}

I will keep you posted if I manage to play music.
Enjoy!

Quote from ernisse

I know this is a stupid question, but how do you use the mono addon properly? I have several short mono apps that work fine in other linux distros but I have not for the life of me figured out how to use it properly in Libreelec. Even a small hint would be appreciated.

Hello ernisse,

Upload your app to LE, ssh to LE, type mono app name at the command line.

If you provide me with an app, I will gladly provide you with more detailed explanations.

I hope this answers your question.

Hi,
I tried this, unsucessfully, similar to what c0rrre reported above.
I have opened an issue at Fornoth/spotify-connect-web.
If I can make it work, I'll wrap it in an addon.

Great initiative, especially for the architectures/projects which support Docker.
You can count on my help on this

Team LibreELEC is happy to announce that WebGrab+Plus is available as a LibreELEC addon.

Addon Home Folder:
- via Kodi: Files, Profile directory, addon_data, service.webgrabplus
- via smb: smb://libreelec.local//userdata/addon_data/service.webgrabplus
- via ssh: /storage/.kodi/userdata/addon_data/service.webgrabplus

Operation:
The service produces files guide.xml and mediaportal.xml in the addon home folder.

Configuration:
Simply add desired channels in WebGrab++.config.xml in the addon home folder.
Available channels may be found in the siteini.pack folder in the addon home folder.
Optionally, edit chans2correct.xml to control xmltv_time_correct.
Do not edit file names in the configuration files, as this is likely to break service operation.

To restart the service (aka run now):
- via Kodi: disable and enable the addon

To inspect operation:
- via smb: smb://libreelec.local/userdata/addon_data/service.webgrabplus/WebGrab++.log.txt
- via ssh: systemctl status service.webgrabplus, or journalctl -u service.webgrabplus

One shot manual operation via ssh:
- webgrabplus.run

Please share your feedback on this thread.

Enjoy!

Quote from MikeKL

awiouy

Removed (renamed) my existing userdata -> addon_data -> service.webgrabplus folder then updated addon and tried out latest release and can confirm everything working well and as expected.

I understand better changes you have incoperated in service.webgrabplus-*.0.92 release for LibreELEC.

Really enjoying simplicty of webgrab++ set-up now with LibreELEC running as a service, where all typical user needs to do is access userdata -> addon_data-> service.webgrabplus -> siteini.pack -> [Country(s) of user Channel (to obtain EPG information) Interest]

Enter and then select channels strings required from user selected .channels.xml (with favourite text editor)
add text strings to userdata -> addon_data -> service.webgrabplus -> WebGrab++.config.xml (with favourite text editor)
Save changes in WebGrab++.config.xml

Then run via ssh, webgrabplus.start (which has benefit of providing running job information on the ssh'd screen as the webgrabplus job is being run on the LibreELEC device )

Display More

Thank you for your feedback.
I was waiting for it to request merging the pull request.
The official addon should hopefully be availabe soon.

Quote from mello

Hi guys, everything worked just as expected.

I'm in Brasil running a RPi2 with minisatip as backend and IPTV Simple Client as frontend, the receiver I'm using is a DiBcom 8000 ISDB-T. If any one have a similar setup and need some help or have any question please let me know.

Thank you for your work.

Thank you for your feedback!

Quote from donbrew

I must be denser than you think.
I typed "smb://libreelec.local/userdata/addon_data/service.webgrabplus/guide.xml" into to Add Sources in Kodi on the Windows machine and got "can't retrieve directory information".

Earlier I added a source "smb:// 192.168.1.211//storage" I thought that was working, but it only shows the directories, not the files.

For some reason the sources don't have a problem RPi to Windows. iVue on the RPi can use the guide.xml on the windows machine.

I know it is something I don't understand.

Are you trying to access guide.xml on LibreELEC from Kodi on Windows?
If this is the case:
- first, add the corresponding source (ie, a folder, not a file) on Kodi on Windows (files, add source, browse, add network location, etc to add smb://libreelec.local/userdata/addon_data/service.webgrabplus - do not add the file in the source)
- then, use this source to access files (eg, config.xml) from the addon on Kodi on Windows.
I hope this answers your question

Quote from MikeKL

awiouy, Please can you clarify....We can install and/or update addon in our existing LibreELEC installation by downloading and then accessing provided .zip in normal way to install an addon.

If we have already previously setup our webgrab+ configuration files and wish to view new examples from latest zip, we delete our userdata _> addon_data -> servicewebgrabplus folders. Otherwise we can just install from .zip and only underlying installation files are updated, with user configuration items in userdata _> addon_data -> servicewebgrabplus unchanged?

Thanks for the update

The update changes the paths of most of the output files, some of which are used by webgrabplus.start
it is therefore preferable to delete the service.webgrabplus folder.
If you have added many channels to WebGrab++.config.xml, it may be a good idea to save them someplace, to be able to put them in the new WebGrab++.config.xml.
I hope I have answered your question.
[hr]
[hr]

Quote from donbrew

How can I make WebGrab write guide.xml to smb:// Windows10machine /EPG/guide.xml ?

That is the address I can use to get iVue on the RPi to use the guide.xml that I moved there from the RPi. I put that address into the <filename> in WebGrab++.config.xml, but it insists on looking for it in /storage/.kodi/userdata/addon_data/service.webgrabplus/smb:// Windows10machine/EPG/guide.xml.

When I redirected the guide.xml to /storage/guide.xml it worked fine.

I am linux dumb, what have I done wrong?

Why don't you do it the other way around, ie access guide.xml from windows10machine via smb://libreelec.local/userdata/addon_data/service.webgrabplus/guide.xml?