Posts by RayW

Quote from AuXBoX

The Nexbox is s905x, and i have the 1gig RAM version.

I'm using gxl_p212_1g.dtb device tree.

Hey Auxbox good to see you here and trust you are well mate. With your known technical knowledge of compiling Linux based builds I am certain you can be a great help here in this forum my friend.

Yes that is the correct .dtb device tree file for S905X boxes though not all makes and models will be fully compatible. I am not 100% but have3 a freind on here who you will know of old who uses a NExbox with LE8 but I believe it is an S905 box not the newer S905X version that you have.

Personally I use the very nneat and fast and compatible Beelinkg MXIII II S905X box and other than having to installtointernal twice it is excellent and works brilliantly wiht both the MM and Nougat kernal LE8 builds but note I do not have a UHD TV so can only test up to 1080 res of course.

Quote from bubblegum57

Is there a command the equivalent of ""installtoexternal" ?

The reason I ask is that I keep a microsd card with the last version, but I don't keep it up to date, & if the NAND gets corrupted, I have an old backup.

I have tried the backup kodi addon, but it seems to take ages & when I have had to use it, it fails.

Not that I am aware of and would not really have a use for such a command personally to be honest.

Best to just simply update your sd card with your latest suite of addons and setting you want to use with new boxes, To save you reinstalling it all manually from scratch to your sd card you can back it all up from your current working from NAND box and restore it to your bootable SD card. I would first use a cache and package clean up utility on your working nand installed LE box, for which there are many such utilities out there that I maybe should not name here. That will helpfully reduce the size of your LE backup. Then with your up to date working internally installed LE box carry out a backup using the inbuilt LibreELEC backup utility, saving the back up .tar file to a USB stick. Do not use an SD card for this backup as you wont be able to restore that backup to your bootable SD card running new box, as these devices only usually have one SD card slot of course.

Now boot up a new box using your LE SD card in the usual way and once booted insert your USB stick with the back up on it and go to the LibreELEC backup utility and then restore from the USB stick. You will then have a bootable LE SD card with all your suite of addons and settings on it too which you can keep up to date easily too. Check it all works okay and if necessary update it to a newer LE version too if a suitable new version is available. Now using ssh you can installtointernal on your new virginal Android boxes as required and say yes when it asks if you want to copy across your userdata too. It will then copy it all across from your LE SD card of course and voila you have a "fully loaded" working box and this saves a lot of time and effort thereafter.

Hope that helps

Quote from Skripo

That means I still have to install libre welcome first. I want a copy of the NAND that I can boot from a USB and then do copy to NAND.

Well I simply have my boot up LE8 SD card and set that up with the latest LE version I want to use and have it all set up with the add-ons I need and configuration settings (like international, display settings etc.). Once I am happy with it I installtointernal via ssh and then remove the SD card. Then for another box, assuming it is the same or compatible, I simply boot it up from the SD card and usign ssh installtointernal and say yes for copying across all the userdata too. I now only use Beelink MXIII II S905X boxes nowadays, though they need to installtointernal twice to set up memory allocation.

This works brilliantly and is easy to do. If I want to make changes in future before installtointernal cloning to another box, then I update the settings and/or LE version on the SD card first so my SD card is kept up to date all the time. Easy and no problem with any welcome screens etc. and box is ready to use as a clone or an updated clone of the last box. Secret is to keep the bootable SD card up to date with any needed changes of addons and settings whenever they may be needed.

Thanks so much Kszaq for the latest 8.0.1l version. Still to install it and of course will let you knwo if any problems arise. Anyway thanks for everything you do for us all and for all the great LE builds you compile Massive appreciation to you.

Main reason I post this is to let you know that at last new stocks of coffee have arrived so I have now been able to send you a well deserved cup. Enjoy !!!

Quote from RayW

Thanks Kostaman for this suggestion about changing the P Size option to Screen Fit as it works well, but alas I found that the screen soon switched back to 16:9 default and having already reset the calibration to default (0,0) top left and bottom right, this left me back with the overscanning and loss of the screen edges all round. Meant I was having to contunually change the P Mode on my remote back to Screen Fit. BUT I found th eanswer as it appears that you can only change the screen size setting and other Advanced Display settings, so they stick, in Standard and Movie modes and I have always used Dynamic mode.

Further to my post above I soon found that the edited settings on my Samsung TV still did not save and after about 30 minutes, or when you switch the TV off and back on, the edited screen settings are lost and all returns back to default in Dynamic mode. A bit of research and I found that even after the 5 years I have had the set it has always been in Store Demo mode ... duh. That was why it kept returning my screen settings back to default. Now switched off Demo mode and all is working as it should.

Useful info for those with Samsung TVs trying to get their screen calibration correct to their LE and KODi boxes and maybe getting this problem with their TV display returning to default settings all the time. A bit off topic so sorry for that but it is very much related of course.

Quote from kostaman

Did you try turning off overscan on the TV. Menu -> Picture -> Screen adjustment -> Picture Size, then change from “16:9” to “Screen Fit”.
or maybe . “Picture Mode” / “Aspect ratio” change “16:9” to “Just scan”.
I had a friend with these issues on older Samsung or LG and i remember the Overscan was somewhere in the settings above.

Thanks Kostaman for this suggestion about changing the P Size option to Screen Fit as it works well, but alas I found that the screen soon switched back to 16:9 default and having already reset the calibration to default (0,0) top left and bottom right, this left me back with the overscanning and loss of the screen edges all round. Meant I was having to contunually change the P Mode on my remote back to Screen Fit. BUT I found th eanswer as it appears that you can only change the screen size setting and other Advanced Display settings, so they stick, in Standard and Movie modes and I have always used Dynamic mode.

So I went to Standard mode, which you CAN edit and set it to Screen Fit. Then adjusted the picture settings so it is not quite so wishy washy as it is in Standard mode by default, and now with my final settings looks actually even better than Dynamic mode. Dynamic mode was great but tends to be a bit too contrasty and a tad too cool in tone. So now very happy as all my devices will now work in default screen settings without screen calibration. Certainly only see the picture improvements with the change from Dynamic mode to my new carefully edited Standard mode. Certainly the overscanning problem being fixed in KODI display calibration did not noticeably degrade or distort my picture, but this is now more convenient and is probably technically a better way.

So now happy and renamed the HDMI 1 source back as AV Receiver as the other suggestion to change the name to DVI PC did nothing at all as I suspected being surely only a name label for each HDMI source. My TV BTW is a 5 year old 46" Samsung Series 7 so the above info might not apply with other makes and/or models of TV, but hope it may be of help ot many others with similar TVs and using LE8.

Must say I am very impressed with 8.0.1k so far and have no problems with it I have found. Runs smooth as silk on my Beelink S905X box.

Quote from Ftelf

I had an impression that screen-size calibration is only last resort fix because it will distort the image in the worst possible way (crop-resize). He obviously have problem with overscan, which is a TV problem not a S905 nor LE. All he have to do is to made TV works in 1:1 pixel mode. Ie. on my Samsung UE46F6650SB I had to change HDMI label to PC, problem fixed.

Don't think it causes any distortions as is a standard normal settings adjustment when installing a new box to your display. That is of course as long as you calibrate all 4 settings carefully and accurately, and that means do not skip the last stage usually with only a small adjustment to get the image perfectly square. Correct me if I am wrong here if anyone knows better of course.

All my KODI boxes past adn present overscan to my older Samsung TV, but I have noticed on friends leter Samsungs, less than about two years old, then the default calibration is spot on (default settings for top left/bottom right stay at 0,0). So I always calibrate my boxes to my TV and have a superb picture certainly not seeing any distortion or degradation at all. Also now with the fractional frame rates available it is well worth simply calibrating each display rate to your screen, and no minimow it really is not very time consumming as it takes me less than 5 minutes.

You can always switch off the option to set the display rate to the video option of course as most of us used before in KODI 16, but then you are losign a lot of the better and smoother potential display benefits brought in with KODI 17. Although a technical guy beign a now long retired senior comms and electronics engineer, I am no expert on these display issues so anyone who is more in the know please correct me, but I have been playing around with these KODI boxes and the display settings for many years now.

Quote from minimoe

I too saw this when I moved my box from my new-ish Panasonic TV to an old LG: I run the OSD at 50hz and set the screen borders for that refresh rate. When I play 50Hz videos, everything is displayed properly but when I play something with frame rate other than 50Hz, half the OSD buttons are not visible.

Simple as your LE setup is obviously configured to set display rate the same as the video frame rate (recommended setting). Easy to rectify and a one off operatioon. Just go through all the refresh rates for your chosen resolution and calibrate your box to the TV screen for each and every refresh rate. There are several of them with KODI 17 as we now have all the fractional rates too. I of course also had that problem y ou mention but of course now it is fixed. If you decide to use a different resolution liek changing from 1080i to 1080p then you will need to do the same again as I understand it but I just stick to 1080p on my FHD 5 year old Samsung Series 7.

Quote from yatoya

[SOLVED] thread-8253-post-49042.html#pid49042

One more question. How to change subtitle font?
According to tutorials fonts should be placed in /media/Fonts (one level below userdata).
There's no such directory and creating one makes no difference.
I tried creating Fonts in Samba shares by editing samba.conf. Tried also creating media/Fonts.
Then I tried to create Fonts folder to existing media folder in system with ssh but after restart all files in media are deleted.
I tried also creating folder in Userdata and nothing.
One hour later I discoverd that File Menager in Kodi shows there are folder like 'fonts' and 'media' so I though "that must be it!".
But no. It's not.
Not one of these locations work.
Anyone can help me with this?

Display More

No need to bother with messing around with ssh into box, just use File Manager but first ensure you are configured in KODI Settings so you can see and write/delete to hidden and system files. In KODI 17 default Estuary skin go to Settings/Media/General and enable the last two items which are disabled by default, cannot right now remember where you find thsoe settigns in the old Confluence skin which I no longer use. I prefer Estuary skin now at last I am familiar with it.

So with the font TTF file you want to use (I use Arialuni.ttf file by the way) on say a USB stick or SD card and in your box run up File Manager. In the A window find your font file on your memory stick. Next in the B window go to this path root/storage/.kodi/media and once there make a new folder called Fonts. Open your new Fonts folder and copy across your new TTF font fiile from your memory stick. Reboot and that is it. You can now select your new font in the subtitle settings.

I create a new source in File Manager called root which points to the the Root File System and the path just shows the / character. This is so useful as I can access all the folders in /root and then using File Manager copying across config files like remote.conf, font files etc and of course new LE update files into the storage/update folder. This is by far easier than running up Putty or whatever on your PC, getting your box's LAN IP address and having to log in via SSH trying to remember the various commands syntax.

Just put what you need to copy across onto say a USB stick. Or do what I do and create another File Manager source pointing directly to my NAS Drive (or any other local network storage location), where I have accessible folders with all of these needed KODI files stored and can easily find them and copy across what is needed simply using File Manage every time. I actually only use SSH for editing, or makingfrom scratch, a remote.conf file by finding all the required remote's key codes, plus of course for installing LE from SD card to internal, which I always do as see no point in keepign bloatware Android with LE being so much better, leaner and so much faster running properly from internal.

Hope that helps.

Have to confirm what Kszaq said, as subtitles for me work silky smooth too on my Beelink MXIII II box running LE8.0.1j and have had no problem with this with any of the LE8.0.1 builds. I use the standard KODI subtitles service and use the Subscene and Opensubtitles.org servers. I also run my subtitles in both English and Thai language for my Thai wife and family but have to use a special TTF font file that reproduces the sanscript characters correctly and still absolutely no problems with it in Thai language either and never have had a problem with any Linux builds going back over several years.

Quote from kszaq

It's not possible to "fix" it because of the way how bootloader determines partition sizes.

Thanks for the info Kszaq. I thought it was somethign to do with the boxes partition size and now I know that. Not a big problem anyway just thoguht it worth asking.

BTW the new "i" build its working very well on my Beelink MXIII II 2/16GB box and can confrim that the Suspend mode works fine, though when I bring the box back up it still has the Power Options screen with Suspend highlighted on the screen, which is easily removed of course with the Back button on the remote.
As always many thanks for all your superb work and only hope you enjoy those well deserved cups of coffee we send you Be more coming for sure just as soon as I get some new supply of coffee in

Thanks Kostaman, I missed that. Duh another senior moment hmm.

Thanks for the latest "i" build Kszaq. Weird though as I see others are testing this new build, but I just went to Page 1 of this thread to download it and it is not availabel there with the latest version still "h" whcih I have been running for the past week and all good on my Beelink MXIII II 2/16GB S905X.

Incidentally and as you probably know on first time installtointernal with these boxes I have to install to internal twice with this Beelink S905X model as it throws the well documented error after the first attemp. Is there anyway this can be fixed for these boxes that throw this initial installtointernal file system error? Okay sure it is only a minor annoyance I admit, so accept it would be a low priority of course.

Quote from bylderup

I can see more clearly now what the problem with my MiniX3 II is.
Made a factory Android reset and new Libreelec Installation on SDCard.

There are 2 Partitions, the 512 MB Partition with FAT32 called LIBREELEC
and the second Linux Partition generated from libreelec on first boot called LIBREELEC_DISK
The Android System can not access this Partition.

Everytime when "i boot from internal" this partition is marked as corrupted from Android System Memory

Is there a way so solve this ?

To be perfectly blunt get rid of the crappy Android, personally I see no use for it only a resource hog and a much inferior way of running KODI with the other Android apps not wanted and not needed AFAIC. This external card/disk access is always the same with Android being both klunky and more restricted as it has to make an Android folder on your SD card or USB stick to be able to read/write to it following a reboot with the card in the slot.

Personally I strip Android off of my boxes as soon as possible, once it is tested to LE8 from a bootable SD card and then I installtointernal straight away and bingo I then have the best KODI box you could ever wish to have IMHO.

Those two partitions on your bootable LE SD card are just as they should be for running LE from an SD card and then for installing it to internal an dgetting rid of the unwanted Android. Once LE is installed to internal remove that bootable SD card and you can freely put in a normally formatted SD card for whatever use you want without the crappy Android restrictions. I use my normal formatted SD card for LE backups and the occasional download that I rarely make (as can access almost all I want when I want via streaming I see no point in wasting time and effort on downloading media files, though useful to have some material locally sotred just in case the internet goes down). The boxes run so much better once LibreELEC is installed to internal of course as you would expect.

Quote from saltanar

Confused here as I certainly did not write that. Do not understand what must be your question saltanar. We are talking here LibreELEC V8.0.1f So nothing to do with LE 7 of course.

Just a quicky to confirm that after updating from 8.0.1e to 1f on my Beeling MINI MXIII II S905X box all is good. TH eprevious problem wiht 1e withthe video calibration not beign saved seems so far to now be fixed as my calibrations at various frame rates are now maintaitned as I set them even after a full poweroff/on cold reboot. Nobody so far has mentioned about this fix being okay now, which is strange as to me this was a very important annoyhing bug to fix and so good that it now all works as it should.

Thanks immensely Kszaq fo all these great builds. Just sent you some well earned coffee in appreciation

Cheers
RayW

Quote from Exp245

8.0.1e works great except video calibration settings, every time when i reboot device settings return to the default. Has someone fix?

Yes same here for me too with 8.0.1e All else seems fine to me but I have not got a UHD TV so cannot comment on the 4K video issues. Found that if I switch to 50Hz refresh rate instead of 60 Hz then it seems to boot up with my Samsung screen remaining properly calibrated but it does not at 60Hz. ????

Quote from csadoian

Using LibreELEC on a Nexbox A95X 2GB/8GB box.

I was testing 8.0.1d and noted some minor freezing when watching an OTA TV channel from my NextPVR setup. I have two Silicon Dust devices, one is the HDHomeRun Connect 2 tuner OTA, the other is a HDHomeRun Prime 3 tuner cable using Comcast. The freezing occurred only when using the Connect on OTA channels. Didn't see it when tuned to a cable station using the Prime.

So today I switched to 8.0.1e and I don't see any freezing, but the display is not acting correctly. I normally feed the Nexbox into a computer monitor at 1920x1080p, and I used the video calibration to move things around to make it look correct. In player settings I also set it to minimize black bars at 20%. This has always worked fine on my setup. However after I loaded up 8.0.1e and I switch to a TV channel the display momentarily blinks and then looses the custom calibration I had set (image is very large and shifted to the left). The video looks normal for a few seconds, then after the screen blinks it's obvious it's ignoring my custom settings. When I exit the TV channel the Kodi menu returns and everything looks fine.

The loss of custom calibration occurs regardless of the native resolution of the TV channel I am watching.

Ok, more info ... it's not just the TV, it's even doing it on Movies and TV shows I have stored and playback using Kodi. Must be something in the player that's causing the issue. In addition, when I switched to 720p resolution it does the same thing ... it goes to a large image shifted off to the left.

I will roll back to a previous version for the time being.

Edit: Ok, sorry, false alarm. For some reason in Settings/Player the option "Adjust display refresh Rate" needed to be turned off. It was set to "On Start/Stop" and that never made any difference in the past. It does now.

Thanks,

Chuck

Display More

If you have the Adjust Display Refresh Rate option set to Always or On Start/Stop then to ensure your screen stays correctly calibrated you would need to calibrate in KODI Settings/System each rersolution refresh rate screen and then of course when it switches display modes it should keep you with a calibrated correct screen. You will need to do that for all the resolutions and refresh rates that you find you need to do it for. Sure my Adjust Display Refresh Rate is happily switched off now in 8.0.1e as it seems to be not needed as it was in c and d.