SMB works for me as well (Debian host), but I can't see suspend option in Kodi anymore.
Suspend was removed a while ago due to it being unreliable, providing too great a risk of stuck devices.
SMB works for me as well (Debian host), but I can't see suspend option in Kodi anymore.
Suspend was removed a while ago due to it being unreliable, providing too great a risk of stuck devices.
Display MoreOk, here's what I have tried so far.
Installed the build with the correct device tree. The installed tvheadend 4.2 using zip install. SSH remote.conf to make the remote work.
On the Tvheadend web interface I enabled availink avl6862 tvb t device. Added a network using Australia Melbourne (tried generic as well)
Went back to devices and selected the network on the device. Force scanned the network which always returns a failed status for all mux.
Tried this entire procedure on 8.0 c , 8.0 e and now on 8.1 as well.
One observation is that while scanning the status on the device shows signal strength in 90%+ however SNA is always 0. Is that why the scans are always failing? Is there an issue with the firmware? Btw I have tried scanning channels on TV and on the android DTV app both work flawlessly so there are definitely no issues with the antenna signal.
Again, please, start a discussion for this in a different/new thread. This thread is not the place for it. You're busy with something that applies to any device, not just the S905, nor AMLogic for that matter. You'll get more and better help elsewhere, as well as that you're not polluting this thread, which is about just S905 related matters. You need to keep things separated to make it easier for yourself and others.
Ok.. I get the point.. no worries will try to find in on my own. Just though I could talk to someone who might have faced such issue. Guess none else did. Thanks for all your help.
Loads of people have, that's the point. There are plenty of resources already available to you to help you. You have to make an effort yourself first. We are happy to help if you have an actual problem, just as long as you keep the topics separated.
Thanks, just did that. Now which pvr backend and client testimonials do I need to use?
This thread is not the place to discuss those topics. Search in the forum for similar discussions and have a look at the PVR page in the Kodi wiki to get you started on that. You can always start a new thread if that is not sufficient.
Display MoreHi Guys,
Fairly new to this. I followed all instructions to download k1 plus device tree and LibreELEC-S905.arm-8.0-8.0.2e-C2.img.gz.
Used rufus to write to USB and it booted perfectly. However when I go to TV it says no addon installed.
I have a k1 plus with DVB S2/T2 suppost. Was the addon supposed to be installed or do need to install any addon?
Which addon has to be installed to see live TV?
I don't have tvheadend.
If you have a K1, you should not use the C2 image. Either start over with LibreELEC-S905.arm-8.0-8.0.2e.img.gz or get LibreELEC-S905.arm-8.0-8.0.2e.tar, put it in the update folder and reboot to update.
Is 8.2 stable??
The build had been labelled "testing", S912 has never received an official stable build (read first post) and LE has not even been released yet. Please apply some common sense.
EDIT: Lol, kszaq beat me to responding just a minute earlier with exactly the same thoughts.
Display MoreTry this.
My box is the S905 MXQ NEXBOX Pro 4 k '.
It took me a lot of time to the box flashing it. None of the mentioned possibilities on this forum worked in my case. The following steps brought luck.
- Copy the image to SD with rufes.exe.
- Copy the new dtb.img as prescribed. (gxbb_p200_1G_100M_RealtekWiFi.dtb)
- But then the trick. Zip the ' aml_autoscript ' file from the SD and copy it to the SD card. (Leave the existing aml_autoscript).
- Use the update app in andoid and update the zip file on the SD card.
Voila, it works! Then went flashing as expected.
(It boots first with the NEXBOX logo, the libreelec logo appears briefly after.)
That's still of no use to him. He simply hasn't got a chip which LE supports. His box is not a true S905 MXQ.
Procedures are described in detail by kszaq on the first page. You cant go wrong.
Let me help you out; just find the proper .dtb file from the location mentioned on the first page. Grab the proper one for your box (make sure memory and ethernet values match) and replace the file on your SDCard after burning the image. Boot. Done.
PS: Note that if you have a s905X box,or are using a existing device tree that works , replacing the device tree might not be needed. Just leave it.
Since it's about updating an existing running system it's a lot easier to just put the dtb file in the update folder, next to the update image/tar and reboot. No need to do anything manually with the SD card. ![]()
Testing johngalt's nougat kernel version with fractional frame rate fix.
LibreELEC-S912.arm-8.0-8.0.2-devel-201707041911-g834a470-I.img.gz
THX to vevs.
Thanks again!
For what it's worth: I've been using the last three nougat test builds without issues, in a simple setup for the moment (CEC, h264 1080p input, 1080p output, HDMI non-passthrough audio). All is playing fine.
I do have the impression that the last build does cause a bit more image distortion when quickly navigating though the collection, but this is all but objective and not a show-stopper.
Also, putting the first test build in the update folder and rebooting resulted in a failed update leaving me with nothing more than a black screen with TV input channel label (i.e. no signal at all). I had to manually restore the kernel and system files to get things up and running again.
This latest build did not show the same issue, but it does take an awfully long time with a black screen before the update is finished. Is displaying some sort of update progress not possible? I expect users aborting the process too soon without it, leaving them with broken systems (and more help requests here as a result of that).
If using Windows, use Putty.
Putty is for SSH, not Samba (i.e. Windows file sharing) ![]()
Test build with johngalt nougat kernel, but only 2K.
LibreELEC-S912.arm-8.0-8.0.2-devel-201706261237-ga422055-I.img.gz
Don't use it for install to internal NAND. There is nougat dbt.
Is there any other advantage to this build, in addition to the 10bit/HDR work that has been done, for the 1080p users?
Is it likely that the Kodi menu vsync for the 912 (say the nexbox A1) will get fixed at some stage, or is this a permanent issue due to lack of co-operation from chipset manufacturers regarding drivers?
Unlikely, due to the lack of fbdev Mali libraries released by AMLogic, as mentioned in the OP.
hi guys I've installed the latest build and everything works sweet bar audio,the selection is greyed out and stuck on default,Bluetooth.there's no option of HDMI, anyone know of a fix? Cheers lads
Device? Log?
Device tree is already included in SD image, you needn't replace it for KIII Pro.
Cheers. Strange thought. When I started using LibreELEC a few weeks back, 8.0.1k with a full clean install, I didn't have the tuners available in tvheadend until I replaced the device tree with the one in the third post manually. Maybe it was just an unlucky combo of other things then.
Update in #1.
Thank a million again for your work afl1 ![]()
Would it be possible to include a reference and link to the device tree in the first post? Makes it easier to locate for existing users and new users tend to skip this step because they don't read further than the first post.
You forgot note there is internal tuner support (Mecool KIII Pro).
Pls add dtb for KIII Pro KIII_Pro_dtb.zip.
I already tested your version and internal tuner is running.
Does this mean that there's no need for your separate KIII builds any longer?
he kszaq can you add this way in your builds?
...just two posts earlier...
Not in current shape. You also have to keep in mind that my builds are ongoing work in progress, not everybody wants to test. Custom update channel also doesn't provide support for device tree update in case it's needed - and it will be if "full Nougat" kernel makes it into regular builds.
Did you use the device tree from the third post in this thread?