I can't speak for the LE build but it works fine on mine with the latest version from GitHub and the latest libwidevine.so, tested yesterday.
ok, I am going to bite. Where do I get this “ libwidevine.so“ thingy from😀
[8.90.1] CoreELEC for S905/S912 devices
-
-
-
See the post above...
I think part of my post got cut off. I have the Netflix Addon, but don’t know where to get that latest libwidevine.so.
-
-
"installtointernal" command changed?
I throwed the remote.conf file in .config folder, not working, any quick help?
Remote solved, the remote thread should be pinnned
-
"installtointernal" command changed?
I throwed the remote.conf file in .config folder, not working, any quick help?Install to internal has been dropped on latest releases, and is not going to come back.
There is extensive discussion in the forum, a quick search will do.
Regards
-
Install to internal has been dropped on latest releases, and is not going to come back.
There is extensive discussion in the forum, a quick search will do.
Regards
I'm pretty sure I read that GDPR-2 stated he brought back installtointernal on his development builds due to user requests.
::EDIT:: Here is the link that says installtointernal is back
-
I think part of my post got cut off. I have the Netflix Addon, but don’t know where to get that latest libwidevine.so.
To make things short:
1. install the Netflix-repo repository.netflix-1.0.1.zip
2. in Kodi install the Netflix-addon from this repo-zip
3. configure the Netflix-addon with your Netflix-login
3. ssh to your box
5. cd /tmp; wget getwidevine.sh
6. sh getwidevine.sh
-> now libwidevine will be installed to /storage/.kodi/cdm
7. invoke the Netflix-addon and you will see...
-
I upgraded (at least I tried) from 8.90.5 to 8.90.6
just copied the img.gz file to update folder than rebooted the box, sadly it booted to android recovery
I guess I should have copy the devicetree file too
just followd this method:
Code- If you forgot to use a new device tree or used wrong one and your device doesn't boot:
- if booting from internal:
- Boot this build from SD card or USB with correct device tree.
- Login over SSH and execute dd if=/dev/zero of=/dev/dtb bs=256k count=1 then dd if=/flash/dtb.img of=/dev/dtb bs=256k
- Power off, remove SD/USB, boot from internal.
Successfully booted from USB, than logged in over SSH and executed the two command, turned off the box, USB drive removed than started
but instead of Libreelec my box booted to android recovery again
Any idea how can I fix this?
-
Display MoreI upgraded (at least I tried) from 8.90.5 to 8.90.6
just copied the img.gz file to update folder than rebooted the box, sadly it booted to android recovery
I guess I should have copy the devicetree file too
just followd this method:
Code- If you forgot to use a new device tree or used wrong one and your device doesn't boot:
- if booting from internal:
- Boot this build from SD card or USB with correct device tree.
- Login over SSH and execute dd if=/dev/zero of=/dev/dtb bs=256k count=1 then dd if=/flash/dtb.img of=/dev/dtb bs=256k
- Power off, remove SD/USB, boot from internal.
Successfully booted from USB, than logged in over SSH and executed the two command, turned off the box, USB drive removed than started
but instead of Libreelec my box booted to android recovery again
Any idea how can I fix this?
I thought you were supposed to upgrade by putting the tar file in the update folder
-
"installtointernal" command changed?
I throwed the remote.conf file in .config folder, not working, any quick help?Wrong build, the copying of the remote config file changed after 8.90.4?
-
I thought you were supposed to upgrade by putting the tar file in the update folder
I always used the img.gz file (whitout dtb file) before without any problem, this is the first time I have this issue
-
S912 -> Better to wait the version [8.90.7]
-
S912 -> Better to wait the version [8.90.7]
The two S912 devel builds are not perfect but seem to be an improvement over the basic 8.90.6
They still show issues with smooth playback of PVR streams - but they are certainly getting better all the time. The 8.90.7 build will be a distillation of what works best from the devels. I would go ahead and install them.
Shoog
-
I always used the img.gz file (whitout dtb file) before without any problem, this is the first time I have this issue
Try using the tar file as per instructions in OP to upgrade
Choose .img.gz file for burning to a new usb drive or SD card and choose .tar if you are upgrading
just followd this method:
You didn't, because that method describes building a new install from the img.gz file on a SD/USB but you simply dropped it into the existing .update folder
Any idea how can I fix this?
Read previous posts, the sure fire fix is there.
-
Just a quick thanks GDPR-2 for the latest build w/colorspace options in settings.
Yes agreed, very nice to have the options through gui.
-
Try using the tar file as per instructions in OP to upgrade
You didn't, because that method describes building a new install from the img.gz file on a SD/USB but you simply dropped it into the existing .update folder
Read previous posts, the sure fire fix is there.
Wasn't one of the changes that LibreElec introduced over OpenElec that .img.gz could be used for upgrades, as well as .tar files, with an aim to eventually no longer needing .tar files to be used at all (as .img.gzs would serve both for original installs AND upgrades)?
Has this changed - or is this just a quirk of these builds?
-
Wasn't one of the changes that LibreElec introduced over OpenElec that .img.gz could be used for upgrades, as well as .tar files, with an aim to eventually no longer needing .tar files to be used at all (as .img.gzs would serve both for original installs AND upgrades)?
In a different thread, concerning builds by a different person and different kodi version, mods were introduced that indeed allowed an upgrade from img.gz files as well as tar files.
The OP of this thread, pertaining to the new, alpha builds we are testing here clearly state
Choose .img.gz file for burning to a new usb drive or SD card and choose .tar if you are upgrading
and in the FAQ that follows it
Q: How do I update?
A: Copy the tar file into the '.update' folder in /storage, DO NOT copy your DTB, this will be updated automatically, finally reboot.
Personally, I follow the most recent procedures given, even if they do differ to what I've been used to, I've found it leads to less issues overall
