I have only 1080p TV, can't test this.
If you want to test 2160p, please try setting it in Android and then reboot to LE.
I have only 1080p TV, can't test this.
If you want to test 2160p, please try setting it in Android and then reboot to LE.
I noticed that AMlogic released a new buildroot: http://openlinux.amlogic.com:8000/downlo...ilesystem/
Yeah but it's on Chinese servers, 5KB/s here.
Thank you Ken.
Unfortunately as long as we have to rely on libhybris these builds will stay experimental. I am still fighting with resolution switching, can't make it work properly.
OK, I've got the logs. There are some errors. My current config is set to passthrough for every available format since my AVR can decode everything up to Dolby Atmos (excluded). Sample is trying to play DTS-HD-MA audio stream.
It is quite odd that only I have this issue with 8d. Looks like I'm special
I need full LE log files to also see kernel log. I repeat, instructions are in sticky post: thread-981.html
[hr]
Greetings,Only this information, it did not appear on TVH.
Best regards...
Probably your tuner is not supported by the drivers although it should be by cx231xx kernel module.
You should start by reading sticky thread. Everything is explained. They are sticky for a reason.
beeasy79 You box is based on Rockchip RK3229, you can't run my builds on it.
I have a RUPA M8S Pro S905 box. I dowloaded this 8.0 software and a tree via Rufus to a SD Card. I then used Android Terminal to boot into recovery mode.
But after the box is powered on it takes around 10 minutes before the LibreElec logo shows up and its starts to boot. When it has started its works just fine but everytime i reboot the box it takes another 10 minutes for the Libre Elec to boot. Just a black screen before that. Really weird.
I tried to use a USB disk instead but with the same result.
I'm sorry, I don't know that box. The only way to debug it is to hook up a serial console. You may also want to seek for an updated firmware from manufacturer.
Dear Kszaq image I wrote on the 32GB SD card, I plugged it into WeTek Play 2 but it did not turn on the following errors.
Make sure that you used a proper device tree.
Karol, please post a full log so that I can see your config. Instructions are in sticky post. There were some changes in audio config, I may have done something wrong.
Tim_Taylor This is wrong! cfg80211 is a dependency for all WiFi kernel modules!
renzz Correct. Echoing 5 will get you 792MHz for S905 and 742MHz for S905X. It might increase smoothness for very heavy skins, although I can see no difference on Estuary which is already running smooth here at standard speed (500MHz).
The only difference between the new/old device tree is that the new one allows running Mali at 792Mhz but only when you set the driver parameter. Network and USB are working just fine on all my devices.
mmpp is 100% correct. In my opinion Jarvis builds are almost 100% working and I am backporting hardware-related fixes from time to time.
If you want a new box, get S905 or S905X. Do not buy S912. My S912 builds are a proof that it's possible, not something recommended to use.
Don't worry, I work closely with Sam (OSMC lead) on sharing both S805 and S905 platform improvements.
I cannot comment on installing OSMC on generic S905(X) boxes, I have never tried it.
Ok Thanks.
I think it was related to advancedsettings.xmlDo you advise change settings on advancedsettings.xml to?
The recommendation is to stay stock. If you want to adjust them, it's up to your setup/liking.
kszaq I was wondering which s912 box you are using for development. I couldn't locate that info it in your postings. Any chance you would be willing to post that info? My apologies if it is out there, but I am having trouble finding that info. I appreciate the work you have been doing and would like to assist in whatever way I can. If you need a box to test development on let me know and I'll see what I can do to help.
I am reluctant to say which box I am using because that would sound like a recommendation. I aim to support as many boxes as possible.
That said the only boxes that I can fully support are branded ones, i.e. WeTek and Minix because these are the only ones with consistent hardware and great support from vendors.
Thank you for your offering. Currently thanks to many coffee donations I have enough funds to buy a box in case it is needed but I think I am doing fine with the hardware I already have.
A kind reminder note:
S912 will be experimental as long as we have to use libhybris to render the UI.
[hr]
ps: is it hard to install jarvis 16.1 into this release....still like yarvis over krypton...maybe you (kszaq) can make a image with 16.1 kodi also?!
First I need to sort out a few bugs, then I will consider building Jarvis... Remember that Jarvis is no longer in development!
Amlogic supplies device trees with 100M Ethernet and there's a built-in 100M transciever. I provided them just in case.
improved Kodi buffering patchCan you explain better this feature please?