Posts by awiouy

    Hi dead!

    Look here:
    Raspberry Pi • View topic - Netflix on Pi 2

    External Content gist.github.com
    Content embedded from external sources will not be displayed without your consent.
    Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.

    Plenty of ideas for improvement!

    Hi infinity85,

    I have no plan to implement the feature you request (neither time, nor skills). Improvements are however welcome, especially as github pull requests.

    Odroid C2 is aarch64, and the addon only runs on armhf, eg RPi2.

    Enjoy!


    When the time that it is running webgrab corresponds to a time I am using a TV Guide, it stops the TV Guide loading.

    Are you referring to guide.xml or another guide_*.xml file?
    guide.xml is only updated once, by a cp at the end of processing, which should be quite short.


    Thanks.

    As far as I can see the .timer has to start a service called the same name .service in the same folder.
    If I can't call it .service because it gets started automatically by LE, do you know what I should call it?
    systemd.timer

    I can see why people get frustrated by system.d now. ;)


    Call the service/timer anything you like, eg webgrabplus.service/timer, as long as it is not service.webgrabplus.service.

    Try it manually first ;)


    awiouy I've had a go at adding a configurable system.d Timer to the service but have got stuck. Please help.

    I can't work out how LibreELEC is triggering the system.d services. I tried to start the timer in the default.py file but it doesn't work.
    On reboot it runs the .service file even though it should start the .timer file.

    I added a user setting for the system.d timer's OnCalendar field to make it as flexible as possible and a random delay to be nice to the servers.

    The code so far is here:
    GitHub - primaeval/service.webgrabplus


    Hi primaeval!

    LE automatically:
    a) enables/starts service.webgrabplus.service at system startup
    b) runs default.py at Kodi startup

    Modify one or the other to enable your timer. In any case, the service called by the timer should not be named service.webgrabplus.service.

    To enable a service/timer:
    systemctl enable path-to-the-service-unit/service-unit

    I hope this will help you. Keep me posted.


    Uploading a new version of the "chromium-elec". Pretty sure now it is working. :)
    It even has an cec input, but it is slow.

    Build the Dockerfile in the docker folder using:

    Code
    docker build -t chrome .

    Config.txt

    Code
    dtparam=audio=on
    disable_overscan=1

    Then just execute the run.sh

    It is using the mmal to accelerate the h264 decoding but unfortunately it doesn't work really well. (tested in a raspberry pi 2).

    Hello dead!

    First, thank you for your efforts, they look promising.

    Then, I tried to follow your instructions, but run.sh fails with
    /bin/sh: 1: /tmp/run.sh: Permission denied
    I am running LE 7.90.006 for RPi2 on a RPi3.

    Finally, if I can make it work, I would like to wrap it in a addon.
    Do you intend to host the image on Docker Hub?

    Thank you for your help


    after.sh is a shell script, not a python script :D
    Copy that script to after.py, and call it from after.sh with python after.py ;)


    Thank you for your quick reply,

    I saw the config with the "after.sh" at the end, have the after.sh in the folder. The after.sh is doing the job started on its own. It has 777 attrib. Still not running... or at least I don't see the result.
    The log is only telling me that that the job finished succesfully. Is there another log to see what exactly is happening with after.sh.

    Thank you,
    Gabriel

    We could help you, if we knew your script ;)

    Eben Upton quote from Eben Upton talks Raspberry Pi 3 - The MagPi MagazineThe MagPi Magazine

    “Although it is a 64‑bit core, we’re using it as just a faster 32-bit core,” he reveals aboutthe Pi 3’s central processing unit. “I can imagine there’d be some real benefits [to 64-bit code]. The downside is that you do really create a separate world. To access that benefit, you’d have to have two operating systems. I’m hoping that someone will come and demonstrate to me that this is a good idea. But there are some really compelling advantages to still being basically ARMv6, and because it’s [Cortex-]A53 it’s a really good 32‑bit processor.”


    Hey there,

    very nice addon.
    Is there a way to use it with a phatDAC on my Raspberry Pi 2 ? It uses the same device-tree-overlay as the hifiberry-dac and the configuration wizard recognizes the card as 'sndrpihifiberry'.
    Kodi detects the card and uses it for sound output with no problem. The addon however fails.
    If you need special error-messages or log-files, let me know!

    fuenfzigccm

    Hello 50ccm,

    I am not sure that Kodi and the addon can share the phatDAC.
    A log would be useful
    [hr]


    Hi this has probably been brought up before but I simply don't have time to read up on the forum. So apologies in advance if I upset anyone.

    In the addon settings, changing "initial volume" does not accurately set the volume in ASAP itself.

    Changing the settings to 90% actually changes the volume to 65% in alsa as seen in the image below

    Hello Loggio,

    This issue appears to lie with spotify-connect-web and/or the hardware, see here and here.
    [hr]

    Hello Robert,

    console_callbacks.py lives somewhere in the /storage/.kodi/addons/service.spotify-connect-web/ folder.
    You can update it there, and restart the addon to pick up your changes
    [hr]

    Thanks for the update. Unfortunately, it breakes :(

    1) Kodi needs to use other audio in order to hear anything through the add-on
    2) Sound still scratches
    3) Port 4000 just shows "Loading..." (OK, that is not really an issue but still worth mentioning)

    Do you need any logfiles or something?

    Thank you for your feedback.
    I am having a look at the web server issue.
    Assessing WeTeK issues without WeTek hardware will be very complicated for me :(