Max2Play Home Forums Search Search Results for 'kodi update'

Viewing 30 results - 151 through 180 (of 217 total)
  • Author
    Search Results
  • #19167

    Teetertank premium
    Participant

    I tried again a few tines to install Kodi and still no joy.

    I downloaded a fresh Max2Play image again from the website (Verson 2.22)
    I downloaded Win32DiskImager from the link Heiner kindly supplied above.
    I reformated eMMC moddule (to FAT32) just to be sure.
    Used Win32Disk Imager to burn a new image to eMMc module.
    Max2Play booted fine – I the expanded the file system and confirmed.
    I updated to version 2.27 (I also tried te latest beta version too with same results)
    Then I tried installing Kodi from the ‚Start Kodi‘ button on M2P Kodi tab.
    I still get no video output even for sandard Max2play interface – screen is just blank
    I get a similar error message when trying to start Kodi (as shown below)
    …says: „unable to resolve host OdroidXU4“ ….is that something to do with the problem?
    Error message pasted below:

    Trying to launch … NOT successful Click here to show detailed information
    sudo: unable to resolve host OdroidXU4
    Use Interface eth0 with -m 00:1e:06:31:13:96
    Stopping Squeezelite
    Stopping Shairport
    pulseaudio: no process found
    sudo: unable to resolve host OdroidXU4
    sudo: no tty present and no askpass program specified
    /usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:57: GtkWarning: could not open display
    warnings.warn(str(e), _gtk.Warning)
    xdpyinfo: unable to open display „:0“.
    Traceback (most recent call last):
    File „/usr/local/share/kodi/FEH.py“, line 174, in
    if (1 == 1 and badColorDepth()):
    File „/usr/local/share/kodi/FEH.py“, line 153, in badColorDepth
    return bitDepth
    UnboundLocalError: local variable ‚bitDepth‘ referenced before assignment

    #19151

    In reply to: Jessie-based image

    News:

    • most apps are working with the RPi 3 and the current Beta (make sure to update to latest Max2Play-beta)
    • WPS is currently not working with Raspberry Pi 3 integrated WiFi (thanks Bort for investigating) – I think there are some driver issues that need to be solved. External USB-Wi-Fi sticks are working with WPS.
    • I built a bluetooth addon that wants to be tested – if you like you can get it from http://shop.max2play.com/media/downloadable/beta/bluetooth.tar – this will let you connect to bluetooth speakers and let kodi / squeezelite and other players use it as audio output

    If you want to upgrade to the latest packages, you should call „apt-get update && apt-get upgrade“. This can also be done at the bottom of the web interface on the Raspberry PI Settings Addon.

    I am still testing and preparing to build the final version of Max2Play 2.28. If you experience any problems in the Beta with Kodi 15.2 or other Addons, this is the place to post them 🙂

    All the best
    Stefan

    #19003

    In reply to: Kodi 16?


    Bort premium
    Participant

    Hi,

    Logitech media server (sorry I’m not have running it on a pi):
    http://wiki.slimdevices.com/index.php/What_To_Backup%3F
    Look where the LMS installation on your pi stores all relevant data, create a smb share to the folder and copy all to your PC. Backward same procedure…

    Kodi: As far as I know, the default user for kodi on m2p ist pi himself.
    So create a smb share to /home/pi/.kodi/ (otherwise it would be /home/kodi/.kodi/) and copy the content to your backup location… in the new image copy it back, start Kodi 15.2 once and then update to Jarvis…

    • This reply was modified 9 years, 1 month ago by Bort.
    #18963

    In reply to: Kodi 16?


    Bort premium
    Participant

    With the apt-get update and dist-upgrade process the preinstalled m2p version of kodi will be completely replaced by the jarvis version from the repository.
    The kodi integration in the m2p web interface works for me (it shows the recent version correct (16.0-2jessie)).

    The jessie image has already (marked as beta) arrived in the dowlnoad area.
    There is an manual update path from wheezy to jessie: https://www.max2play.com/forums/topic/update-auf-debian-jessie/

    But after the official release has arrived I would prefer the start with a fresh image and restore the old settings.

    #18960

    In reply to: Kodi 16?


    asplundj premium
    Participant

    If I add that repo and do an update packages will thar replace the kodi package shipped with m2p or do I need to install a new package and remove the m2p one? Will kodi be integrated into the m2p Web interface?

    When can we expect the jessie-verson of m2p and does it require a fresh install?

    #18853

    flysurfer
    Keymaster

    If you are experiencing trouble with the Youtube Addon in Kodi – this will help you:

    The Youtube-Addon that is listed in the Kodi-Addons won’t work anymore because Google changed the authentication for Youtube-Users.

    With Max2Play (Beta Version or from Version 2.28) all you got to do is:
    – on the Max2Play Web interface Kodi page choose „Update/Install Youtube Addon to fix Unknown Error“ from the Addon Installer
    – restart Kodi
    – open Youtube Addon and click „sign in“
    – you will get two codes that you must connect with your Youtube account to get access. This can be done with any browser by pointing it to „http://www.youtube.com/activate“

    That’s it!

    #18600

    m.max2play
    Participant

    That doesn’t work. Audio outputs are separate and I hear Kodi sounds via HDMI, but even now, when Kodi runs, Audioplayer/Squeezelite stops though Squeezelite is using DAC+.

    Kodi also renders on 7″, not HDMI though sound is on HDMI for Kodi. Jivelite (and Squeezelite) pause whilst Kodi is running.

    Is there a way for Jivelite/Squeezelite to run simultaneously with Kodi? Ideally for both audio and video, though even the audio is not working at the moment. I want Kodi to render using HDMI and Jivelite to render on 7″.

    [UPDATE] Okay, works, kind-of, if I select USB-DAC checkbox. I shouldn’t be selecting that however, because DAC+ is not USB DAC. However, now I cannot connect to Squeezelite using Squeezer app (because there is a port conflict on port 9090 between this and Kodi. Note that I’m not talking about port 8080 control of Kodi, that’s separate and works, this is about port 9090). Also, the problem that Kodi still renders on 7″ still remains (so Jivelite UI is not seen which coupled with the fact I cannot use Squeezer to connect any more if I autostart Kodi, means I cannot now control Squeezelite if I start Kodi, so cannot play audio via it for example if I start Kodi – this problem would be solved if either of Kodi or Squeezelite uses a port other than 9090 (how?) – at least, I would be able to use Squeezer (or other app) to control Squeezelite whilst Kodi is occuyping the 7″ display.

    So two problems after both Squeezelite and Kodi have now started running simultaneously after selecting the USB-DAC checkbox:
    * Both Kodi and Jivelite want to use 7″. I want Kodi to use HDMI, but video output device is not selectable inside Kodi and I do not know how to get it to render on HDMI and Jivelite on 7″ simultaneously. I do not know if I can use a parameter like --display 6 to start Kodi on the non-default screen (from https://www.raspberrypi.org/blog/the-eagerly-awaited-raspberry-pi-display/ – search for Dual display usage). If it is possible, it would be great to have this parameter available on the max2play web interface.

    On a side note, this might be useful for those who want to run Kodi on demand (upon HDMI plug-in), especially if it can then use the parameter mentioned above to start Kodi on the non-default display (for most users, TV/monitor as opposed to the 7″ LCD): https://www.max2play.com/forums/topic/start-stop-kodi-based-on-hdmi-monitor-status/

    * Both Kodi and Squeezelite want to use port 9090. I do not know how to make one of them listen on a different port.
    [UPDATE] I’m guessing the issue for the port conflict can be addressed by setting a different port for Kodi jsonrpc, http://kodi.wiki/view/Advancedsettings.xml. It would be great if max2play did this automatically if the user chooses to autostart both Squeezelite and Kodi.

    <jsonrpc>
        <compactoutput>true</compactoutput>
        <tcpport>9999</tcpport>
    </jsonrpc>

    So, until this thing is fixed properly (a.k.a. in a newbie friendly way), my workaround is to:
    * Set Squeezelite to DAC+ in Advanced settings
    * Set Squeezelite to autostart
    * Set Kodi audio output device to HDMI (assuming DAC+ can’t be used in Kodi and Squeezelite both simultaneously)
    * Set Kodi jsonrpc to a port other than 9090 (e.g., 9999)
    * Set Kodi to autostart
    * Set HDMI as default video device using display_default_lcd=0 in config.txt file (from https://www.raspberrypi.org/blog/the-eagerly-awaited-raspberry-pi-display/)
    * Forget about using Jivelite interface unless Kodi is exited, but use the Squeezer (or similar) app on my smartphone to control Squeezelite

    But once it all falls into place for noobs like me (prameters provided on max2play web-interface, automatically configured as needed, dual display works properly), I’ll no longer default display to HDMI and will use dual display to show Jivelite UI on LCD and Kodi on HDMI connected display (TV/monitor), running all the time.

    For those desiring to use DAC for all audio output, who do not have a use-case for playing music and Kodi on different speakers but at the same time, perhaps running Kodi with XSqueeze plugin is a better option?

    • This reply was modified 9 years, 2 months ago by m.max2play.
    #18491

    In reply to: Accesspoint issues


    Alex
    Participant

    Hi Simon

    I put this together for a friend just after I got mine working (and to remind me how we did it), I hope you can follow it, but it’s Noop who deserves full credit for this, I was just following his instructions.

    Here goes and good luck hope it works for you

    How I installed Max2play.

    Installation Preparation (read this first before installation, and the **** below to get a feel of whats needed before you start, it just helps to understand the procedure)

    Please note, this was to resolve my accesspoint issues which I had MAJOR problems with.

    Problems were, not all dongles work as an access point, and when I did get one that should have worked it was faulty, so you just have to be aware and lastly Noop also found there was a bug in M2P accesspoint plugin module too.

    But Not everyone had problems with that particular dongle, very odd, I did !
    YOU might have no issues at all, hopefully not

    Anyhow a great little programme to use is Putty. Install this before you start, it’s very useful as it allows you to run the commands later on in this set up on your Pi.
    With putty, you can also cut and past between windows, This means you don’t have to type any of the commands into the command prompt, just cut and paste using Ctrl V each time for cutting and pasting

    You can find Putty here http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html

    When you are ready to start your installation Load and run Putty.exe.

    Once loaded ensure your Pi (M2P) is hard-wired (at this point) into your Lan, switched on and running.

    When Putty is loaded, you will be presented with a DOS type screen, this is what I call the command prompt, at this point, put in your IP address of your SWITCHED ON Pi 192.168.1.XX
    Then when asked, enter your user and passwords (Pi then Raspberry) to get into your Pi. Once in, leave this screen open as this is where all commands will be entered and run (just shrink the screen for now).

    It may also be a good idea at this point to register your M2P account before you start your installation, you need to register for a premier account, this gives you access to your accesspoint plug in and other plug-in modules

    Its also worth noting if all works, the least you need to do are actions 1 – 8 to get is working in its basic form. Actions 9 -11 just offer a way to check your connection/set up so far.

    If all is good at this point and all is working, jump to No 13, 14, 15. If not, then run No 12 and then 13, 14, 15

    Remember you need to know your ip address of your Pi so you can get to M2P via your browser once switched on

    Please note:

    After each module is installed, you will be asked to reboot, make sure you do otherwise the plugin’s may not be installed properly, EVEN if you are not prompted to do this DO IT !!

    The Plugin’s will/should be sat across the top of the GUI page on switch on except for the Raspberry and Access point plug-in’s

    Installation (at this point only your lan and power supply should be connected)

    1. Burn a new image (min 8gb SD card), plug it into your Pi and switch on and navigate to your PI’s IP address using your browser, this will present you with the main Max2play Gui page, from here you will do all setting up
    2. Expand your new image in (Settings/Reboot plug-in )
    3. Update M2P in (Settings/Reboot plug-in)
    4. Increase the USB current via the Raspberry Settings plug in. To do this you can either install the pi plug in by going to the
    squeezebox server module where you can enter your registered email account, (after this the Raspberry Pi module should be in view at the top of the page you opened). Another way is go to the Pi command prompt and enter
    at the prompt, max_usb_current=1 (remember if you want to do this via the command prompt, just open Putty and enter it there (Cut & Paste), then shrink Putty again)
    I opened a M2P account previously and did this part via the Raspberry Plug.

    Once done continue with the installation

    5. Plug in the wifi dongle**.
    6. install wifi.
    7. install access-point*.(then reboot)
    8. remove power and then apply power.
    9. On your IOS device***, set-up -> wifi (after a few minutes) should show an available network with SSID “max2play” (or whatever you set it to)
    10. Try to connect to this network, if you get an error, “forget” the network, and re-try (you will prompted for password in this case).
    11. If connected, on the IOS device use safari or chrome and browse the PI at: http://192.168.189.1/ , you should see the max2play page, so it should be working at this point
    ONLY if there is a problem with the wifi, do the following

    12. login to the PI command by opening Putty and execute these commands: (remember you can cut and paste)

    cd /tmp
    wget https://www.dropbox.com/s/we0d928vfddovia/interfaces.192.168.1.0
    sudo cp /etc/network/interfaces /etc/network/interfaces.orig
    sudo cp interfaces.192.168.1.0 /etc/network/interfaces
    sudo chown root:root /etc/network/interfaces
    sudo chmod 666 /etc/network/interfaces

    After installing this, check the following as you did previously as below 12a – 12c

    12a. On your IOS device, set-up -> wifi should show an available network with SSID “max2play” (or whatever you set it to)
    12b. Try to connect to this network, if you get an error, “forget” the network, and re-try (you will prompted for password in this case).
    12c. If connected, on the IOS device use safari or chrome and browse the PI at: http://192.168.189.1/ , you should see the max2play page.

    If successful carry on installing the rest of the plug-in’s in this order

    13. Install Squeezebox Server (click on show available versions, click 7.9 nightly, click install)
    14. Install Audio Player (and plug in the USB DAC or other before installing the audio player)
    15. Plug in your ext hard drive and scan contents via Squeezebox Server plug-in (go to webadministration tab)

    It takes time for your m2p to scan your data, so leave it running for as long as it takes, mine took overnight.

    Now it should all be working correctly

    If you have photos/films/music on your M2P HD, and need to access them via kodi on your tablet, run the M2P kodi plug-in and follow these instructions

    http://www.instructables.com/id/Raspberry-Pi-Mobile-Media-Center-with-Smartphone-C/?ALLSTEPS
    (please note, I have not done this at the time of writing this, it was from memory before Christmas, but I’m sure it’s the right procedure) I just wanted to put this down while I remembered

    If you try and connect via LMS, you may need to enter the password for max2play

    The user is user and passwords is root (I think, lower case)

    NB
    **My wifi dongle was and RT5370. You need one that works in access mode, this does. £4.89 from Ebay
    http://www.ebay.co.uk/itm/RT5370-150Mbps-USB2-0-Wireless-Network-Card-WiFi-LAN-Adapter-Antenna-Warranty-/400801704684?hash=item5d51a4aaec:g:ttYAAOSwzOxUWyVY

    ***When have set up your your wifi in settings, and you connect, it may prompt you with the home screen of Max2Play. It may ask for a password but will not offer anywhere to put it. If so, Press cancel, top right. It should come up with another screen, use internet connection Yes or NO, pick NO. I don’t have a clue what would happen if you say yes. Maybe it will hook into the local wifi and you access it that way..

    * to install accesspoint, go to the bottom of the settings/reboot page (a demo can be seen here)

    http://demo.max2play.com:81/plugins/max2play_settings/controller/Basic.php

    click on the „list of Max2Play extensions“ and find accesspoint plugin and follow the instructions and install it

    #18482

    asplundj premium
    Participant

    I have two questions regarding this.

    (1) what should I do to get this working before it’s implemented into max2play?

    (2) tvservice -n still reports that my asus monitor is plugged in when I turn off or unplug the monitor. Is there a way to update the tvservice status. As a workaround i think I just reboot the rpi to reset tvservice -n and thereby turn off kodi (once I understand how to do with the script). However, it would be much better if the status could be updated some how. Turning off and hdmi with tvservice -o and -p flags doesn’t help.

    Any suggestions?

    #18450

    Heiner premium
    Keymaster

    Hi Teetertank,
    Thanks for your feedback. I just tested a new image, 2.26 and update to 2.27. Both versions were able to display the usual desktop via HDMI and when I clicked on start Kodi, the program started in the screen both times.
    Have you expanded the filesystem?

    #18274

    Maximilian premium
    Participant

    Hi Murat,

    thank you for your post. Are you still having trouble with your U3 and the latest Kodi version?

    You could try out the following solutions:

    Solution 1:
    Do a beta update and reinstall Kodi (the package hosted on our website)

    Solution 2:
    Log into the console (with SSH) and enter the following command:
    rm -R /usr/lib/arm-linux-gnueabihf/mesa-egl/

    Unfortunately, it is not possible for us to check every USB-DAC available and we don’t have tested the Hardkernel USB-DAC so far. If the audio output is still unstable, it could be related to compatibility issues.

    Maximilian from Max2Play

    #18252

    Das stimmt natürlich…
    mein Updatevorgang war nicht so erfolgreich:
    – Squeezebox Server lief zwar, aber die Weboberfläche auf Port 9000 war nicht erreichbar
    – Kodi ließ sich nicht starten

    Ich hab jetzt erstmal wieder mein Backup eingespielt und besorge mir eine zusätzliche Micro SD Karte.
    Dann habe ich mehr Zeit und kann mit der Kopie spielen.

    Schade

    #18234

    bilbo6209
    Participant

    I gave up on installing Ampache and I am now only using MPD and YMPD… I have loaded/installedthe following

    set Audioplayer to HiFiBerry Digi/Digi+ ( I have a digi+)
    installed and configured Access point
    set Raspberry setting to full power USB
    removed Spueezebox server and Kodi/xbmc
    mapped the USB drive path

    I have updated the data base in MPD YMPD and I can select songs (MP3 and FLAC), I have the HiFiBerry Digi+ hooked up via optical to soundbar, I start a song and it does not produce any sound, I attempt to adjust the volume slider on the top right corner of the YPD screen and it jumps back down to 0% and puts up a message of „Problems setting volume“ I searched on the web and found some references to this issue and they all include linux code, I am not familiar with Linux so I am not able to fix the issue. Does anyone have any steps for fixing this issue that work on Max2Play?

    #18182

    Bort premium
    Participant

    Hallo,

    das wäre in der Tat schön – allerdings ist es auch relativ unproblematisch, das selbst zu machen…
    Ich habe nahezu alle meine Installationen mittlerweile auf Jessie hochgezogen. Zum einen ist das Rechtehandling für wiringpi praktischer (nutze ich für das Schalten der Verstärker über fhem) und zum anderen gibt es für aktuelle KODI-Versionen einfach mehr Repositories für Jessie (z.B. Pipplware – für wheezy ist ja schon 15.2 kaum zu bekommen).

    Vorbereitung:
    1.) Die apache2.conf ist inkompatibel mit der neuen Version
    Es muss die LockFile-Zeile auskommentiert werden.

    #
    # The accept serialization lock file MUST BE STORED ON A LOCAL DISK.
    #
    #LockFile ${APACHE_LOCK_DIR}/accept.lock

    Zusätzlich habe ich die includes für externe snippets ganz am Ende der Datei auskommentiert.

    2.) Upgrade:
    System auf aktuellen Stand ziehen:

    sudo apt-get update
    sudo apt-get upgrade
    sudo apt-get dist-upgrade

    In den Source-Listen alles von wheezy auf jessie ändern:

    sudo sed -i /deb/s/wheezy/jessie/g /etc/apt/sources.list
    sudo sed -i /deb/s/wheezy/jessie/g /etc/apt/sources.list.d/*.list

    Und auf jessie updaten:

    sudo apt-get update
    sudo apt-get upgrade
    sudo apt-get dist-upgrade

    Die Fragen nach der zu installierenden Version der jeweiligen Dienste-config habe ich eigentlich mit Ausnahme von Apache2 immer mit „bestehende Version behalten“ beantwortet.

    Am Ende saubermachen:

    sudo apt-get autoremove
    sudo apt-get autoclean

    Bislang hatte ich keinerlei Probleme mit den so hochgezogenen Systemen – eher Vorteile… es läuft alles (jivelite inkl. Hintergrundbeleuchtungsmod für das 7″ Display, iqAudioAmp+ clone, ir, kodi 15.2 ;-), fhem…..)
    Vorher Backup machen sollte man – einen gescheiterten Versuch hatte ich allerdings nie.

    Einziger Nachteil bisher: insbesondere bei jivelite sind die fertigen binaries halt gegen wheezy kompiliert – dass heißt man musst die lange Variante wählen und die sources runterladen und kompilieren lassen. (Mache ich aber bei jivelite sowieso lieber, da ich da mittlweile auch anderweitig dran rum gefummelt habe…)

    Hoffe das hilft Dir ein wenig – und vielleicht auch dem Team: jessie läuft stressfrei mit Eurem tollen Produkt 😉

    #18179

    bilbo6209 premium
    Participant

    OK I tried doing the resize first following these steps and it failed again 🙁
    First here are my specs, Raspberry pi 2, hifiberry digi+, on an 8gb Samsung class 10 SD card

    loaded m2p_hifiberry_226_wps.img
    expanded file system (USB drive unplugged)
    reboot
    added hifiberry digi/digi+ ( I have the digi+)
    rebooted
    updated info IE my email addy to register, set time zone to america/chicago
    updated via the update button
    rebooted
    removed Kodi
    removed Squeezebox server
    added music player MPD
    added access point
    saved
    installed Access point
    set access point settings
    reboot
    ampache installed
    failed same issue

    as I said I got it working one time without without enabling the higher power for the usb ports… This last time I didnt have the usb drive hooked up and without enabling the full power usb.

    Is my SD card goofed up, what am I doing wrong?

    #18147

    bilbo6209 premium
    Participant

    Well
    attempt 2
    loaded m2p_hifiberry_226_wps.img
    added hifiberry digi/digi+ ( I have the digi+)
    rebooted
    updated info IE my email addy to register, set time zone to america/chicago
    updated via the update button
    rebooted
    removed Kodi
    removed Squeezebox server
    added music player MPD
    added access point
    saved
    installed Access point
    set access point settings
    reboot
    expanded file system (USB drive unplugged)
    reboot
    ampache installed
    failed with same issue


    bilbo6209
    Participant

    Hello,

    I am having trouble with getting max2play on a Raspberry Pi 2 with a Hifiberry Digi+
    here is what I do and the issue I run into
    Steps to reproduce

    loaded m2p_hifiberry_226_wps.img
    added hifiberry digi/digi+ ( I have the digi+)
    rebooted
    updated info IE my email addy to register, set time zone to america/chicago
    updated via the update button
    rebooted
    removed Kodi
    removed Squeezebox server
    added music player MPD
    added access point
    saved
    installed Access point
    set access point settings
    reboot
    set max usb current under raspberry settings
    reboot
    installed Ampache
    At this point Ampache show it was complete
    I hit the link to refresh the page (or click on any other page) and any page is unavailable. I have polled the power and at this point nothing works, if I hook up a monitor to the r-pi at this point I see a failure
    [ ok ] Starting Samba deamon mbd smbd
    [….] Starting webserver: apache2warning; document root [/var/www/ampache] does not exist
    apache2:could not reliably determine the server’s fully qualified domain name, using 192.168.189.1 for servername
    action ’start‘ failed
    the apache error log man have more information

    FAILED!
    [ ok ] starting periodic command scheduler: cron.

    I have tried a couple time formatting the SD card and reloading teh image each time.

    I know NOTHING about Linux so if you want me to do something to correct this in Linux please be kind and walk me through it step by step 🙂

    I had it working one time but my USB drive wouldn’t mount, assuming that filesystem mount was corrupted I formatted and reloaded the image again and have had this issue since (I realized I didn’t set Max USB current on the one that was working but not mounting)

    I am wondering if this has something to do with either not expanding storage, or if it is the combo of some setting and Max USB current.

    I will try again without setting max usb current to see if this is the issue, if not I will attempt to add in the step to expand the storage.

    Any thought or ideas would be greatly appreciated.

    Bill

    #18107

    In reply to: updating kodi


    sandman60
    Participant

    Hi,

    it seems that the current M2P version 2.27 has problems to install KODI 15.1 also on a fresh and expanded OS on a RPI1.
    The only chance I had to solve it was to install/update it manually by removing/solving a dependency problem with
    „apt-get update“
    „apt-get install kodi“
    „apt-get -f install“
    „apt-get autoremove“
    After this KODI (15.2) started successfully.

    Maybe this information can be used to fix the current setup.

    Cheers,
    Sandman60

    #18099

    Nojelc
    Participant

    Well I have tried, but without success.
    I entered the command
    rm -R /usr/lib/arm-linux-gnueabihf/mesa-egl/
    I assume it did something, but there was no response.
    I then tried to run Kodi – nothing. This did not suprise me as my previous attempt to update it resulted in the existing implementation being deleted, and the new one not being installed.

    Tried once again to install Kodi with the procedure at the top of the thread. Just the same result:

    Remove old version
    dpkg: warning: ignoring request to remove xbmc which isn’t installed
    dpkg: warning: ignoring request to remove kodi which isn’t installed
    –2016-01-22 17:37:27– http://steinerdatenbank.de/software/kodi-15-wheezy.tar.gz
    Resolving steinerdatenbank.de (steinerdatenbank.de)… 85.25.144.201
    Connecting to steinerdatenbank.de (steinerdatenbank.de)|85.25.144.201|:80… connected.
    HTTP request sent, awaiting response… 404 Not Found
    2016-01-22 17:37:28 ERROR 404: Not Found.

    dpkg-deb: error: `/opt/max2play/xbmc.deb‘ is not a debian format archive
    dpkg: error processing archive /opt/max2play/xbmc.deb (–install):
    subprocess dpkg-deb –control returned error exit status 2
    Errors were encountered while processing:
    /opt/max2play/xbmc.deb
    Installation abgeschlossen
    Click here to reload Page
    finished

    Installation abgeschlossen!

    So my max2play Kodi is still snafu. Have I misunderstood the instructions?

    #18076

    Maximilian premium
    Participant

    Hi Nojelc,

    Thank you for letting us know. There is an issue with Kodi 15.1 and U3, sorry for that. There are so many differenz systems and we don’t have the time to test every change with every single device. Therefore, your feedback is appreciated.

    The following solutions are available:

    Solution 1:
    Update Max2Play to the latest Beta Version and install Kodi once again (the link given in our interface)

    Solution 2:
    Log into the console with SSH and enter the following command:
    rm -R /usr/lib/arm-linux-gnueabihf/mesa-egl/

    Kodi should work now. Please report your progress! Thank you.

    Maximilian from Max2Play

    #17997

    In reply to: updating kodi


    asplundj premium
    Participant

    How do I update kodi to 15.2 on rpi with max2play?

    #17942

    Nojelc
    Participant

    Hi, trying to update Kodi on my ODROID. I have done the above but the install fails. Log below:

    Installationspaket: http://steinerdatenbank.de/software/kodi-15-wheezy.tar.gz
    Installation startet – This Messages refreshes every 3 seconds to show current status of installation. If finished this message disappears.
    Hit http://ports.ubuntu.com trusty/main Translation-de
    Hit http://ports.ubuntu.com trusty/restricted Translation-en
    Hit http://ports.ubuntu.com trusty/restricted Translation-en_AU
    Hit http://ports.ubuntu.com trusty/restricted Translation-de
    Hit http://ports.ubuntu.com trusty/universe Translation-en
    Hit http://ports.ubuntu.com trusty/universe Translation-en_AU
    Hit http://ports.ubuntu.com trusty/universe Translation-de
    Reading package lists…
    Remove old version
    dpkg: warning: ignoring request to remove xbmc which isn’t installed
    dpkg: warning: ignoring request to remove kodi which isn’t installed
    –2016-01-16 16:00:59– http://steinerdatenbank.de/software/kodi-15-wheezy.tar.gz
    Resolving steinerdatenbank.de (steinerdatenbank.de)… 85.25.144.201
    Connecting to steinerdatenbank.de (steinerdatenbank.de)|85.25.144.201|:80… connected.
    HTTP request sent, awaiting response… 404 Not Found
    2016-01-16 16:01:00 ERROR 404: Not Found.

    dpkg-deb: error: `/opt/max2play/xbmc.deb‘ is not a debian format archive
    dpkg: error processing archive /opt/max2play/xbmc.deb (–install):
    subprocess dpkg-deb –control returned error exit status 2
    Errors were encountered while processing:
    /opt/max2play/xbmc.deb
    Installation abgeschlossen
    Click here to reload Page
    finished

    Installation abgeschlossen!

    How do I sort this out please. I did have an earlier version of Kodi installed, it has been running fine for over a year. However I could not get the latest version of iPlayer working so decided to uopdate to the latest Kodi. Now it seems the old version is deleted and the new version has failed to install.

    Help please!


    noop
    Participant

    I get the following problem during updating kodi: Do you have any suggestions?

      Selection    Path              Priority   Status
    ------------------------------------------------------------
    * 0            /usr/bin/gcc-4.6   60        auto mode
      1            /usr/bin/gcc-4.6   60        manual mode
      2            /usr/bin/gcc-4.7   40        manual mode
    
    Press enter to keep the current choice[*], or type selection number: update-alternatives: using /usr/bin/gcc-4.7 to provide /usr/bin/gcc (gcc) in manual mode
    Cloning into 'platform'...
    remote: Counting objects: 449, done.
    remote: Total 449 (delta 0), reused 0 (delta 0), pack-reused 449
    Receiving objects: 100% (449/449), 157.68 KiB, done.
    Resolving deltas: 100% (256/256), done.
    -- The C compiler identification is GNU 4.7.2
    -- The CXX compiler identification is GNU 4.7.2
    -- Check for working C compiler: /usr/bin/gcc
    -- Check for working C compiler: /usr/bin/gcc -- works
    -- Detecting C compiler ABI info
    -- Detecting C compiler ABI info - done
    -- Check for working CXX compiler: /usr/bin/c++
    -- Check for working CXX compiler: /usr/bin/c++ -- works
    -- Detecting CXX compiler ABI info
    -- Detecting CXX compiler ABI info - done
    -- Looking for include file pthread.h
    -- Looking for include file pthread.h - not found.
    CMake Error at /usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:97 (MESSAGE):
      Could NOT find Threads (missing: Threads_FOUND)
    Call Stack (most recent call first):
      /usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:288 (_FPHSA_FAILURE_MESSAGE)
      /usr/share/cmake-2.8/Modules/FindThreads.cmake:166 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
      CMakeLists.txt:8 (find_package)
    
    -- Configuring incomplete, errors occurred!
    make: *** No targets specified and no makefile found.  Stop.
    
    #17459

    In reply to: updating kodi


    kremat premium
    Participant

    Hi,
    I know that both at the same time are not working and it is working like a charm with Wheezy (14.2)… squeezeplug is stopping, xmbc starts perfectly and after I stop it, squeezeplug starts playing music again.
    But Kodi/XBMC is not staring after the update to 15.1…
    apparently I’m the only one with this problem….I will leave it on 14.2 though.


    ad6922
    Participant

    I ran max2play for a month until I got a kernel panic (Kernel panic – not syncing : VFS: Unable to mount root fs on unknown-block)

    I started all over again.
    1. Formatted my sd-card with SDformatter in overwrite format
    2. Installed 2.22 version from m2p on the card
    3. Put card in rpi 2b
    4. Went to max2play site and updated to 2.25
    5. Then i went to kodi and tried to install http://steinerdatenbank.de/software/kodi-15.tar.gz

    That gave errors:

    Installationspaker: http://steinerdatenbank.de/software/kodi-15.tar.gz
    Installation startet – This message …. message disappears

    the following names:
    kodiConfig.cmake
    kodi-config.cmake

    Add the installation prefix of „kodi“ to CMAKE_PREFIX_PATH or see „Kodi_DIR“
    to a directory containing one of the above files. If „koi“ provides a separate development package or SDK,
    be sure it has been installed.

    — Configuring incomplete, errors occurred!
    make: ** No targets specified and no makefile found. Stop.
    Reset compiler to first version
    There are 2 choice for the alternative gcc (providing /usr/bin/gcc_

    Selection Path Priority Status
    0 /usr/bin/gcc-4.6 60 auto mode
    1 /usr/bin/gcc-4.6 60 manual mode
    * 2 / usr/bin/gcc-4.7 40 manual mode

    Press enter to keep the current choice(*), or type selection number: update-alternatives:
    using /usr/bin/gcc-4.6 to provide /usr/bin/gcc (gcc) in automode
    Click here to reload page.

    ===
    I reloaded the page and I wasn’t able to start Kodi.

    Don’t know what I need to do, please help

    #17308

    zero007cool premium
    Participant

    Nach dieser Anleitung: https://www.raspberrypi.org/forums/viewtopic.php?f=66&t=125879″&gt;
    habe ich es endlich geschafft Kodi 15.1 zu updaten.

    Anscheinend funktioniert es über die Weboberfläche nicht ordentlich.

    • This reply was modified 9 years, 4 months ago by zero007cool.

    boumacor
    Participant

    For the last week I’ve been trying to install the Max2Play image with the Kodi15 package on my Odroid U3. For some reason the max2Play image with or without all the updates works perfect. Every time it expands the filesystem, updates packages, updates the kernel etc etc.

    But as soon as I install Kodi15 thrue the webinterface (using http://steinerdatenbank.de/software/kodi-15.tar.gz or https://www.max2play.com/download/15362/) the multimedai player will not work anymore. Staring form the commandline results in ERROR: Unable to create GUI. Exiting or different errors.

    So I’m wondering : Am I foloing the right procedure and been trying to find something online, but cant. So here’s the question :

    „What is the right procedure to install Kodi15 on the U3 with the Max2Play image ?“

    #17305

    zero007cool
    Participant

    Hallo,

    das Update auf Kodi 15.1 funktioniert nicht. Der Status ändert sich nicht und bleibt ewig bei der Meldung:

    Installationspaket: http://steinerdatenbank.de/software/kodi-15.tar.gz
    Installation gestartet – Diese Meldung zeigt den aktuellen Status der Installation aller 3 Sekunden an. Wenn diese abgeschlossen ist verschwindet die Meldung und der Server läuft.
    …. haben schon mehrer Stunden so. Gibt es im System irgendwo einen fehler?

    Manuelles Update habe ich auch schon versucht aber ohne Erfolg.
    Das System ist up-to-date, Version 2.25.

    #17215

    Hi giacva,

    Please update to the latetest Max2Play Beta (on settings page) and Update Kodi again („Start installation“ on Kodi-Tab of web interface). Afterwards the PVR-Plugins from Max2Play Repository should work.

    Background: There was a recent update by the developers of kodi-platform (changed the name of a library) that is needed to run the PVR-Addons. Otherwise it will bring that DLL-Error (missing library libkodiplatform.so).

    Cheers,
    Stefan

    #17194

    In reply to: updating kodi


    kremat premium
    Participant

    update: When I tick the „Aktualisieren der HDMI-Ausgabe“, it still doesn’t work but then comes the login page for the Desktop.
    I tried to login with „Kodi“ (login:pi pass:raspberry) but it failed. Then I tried to login with „Defaut Xsession“ and that works.
    I can see Kodi under Menu/sound&video but it won’t start.
    (My Monitor is connected via HDMI/DVI adaptor and I can’t test with a pure HDMI connection but never had issues)

Viewing 30 results - 151 through 180 (of 217 total)