Posts by dipswitch

Well, this has become a nice mess; after upgrading to latest stable, my mce remote generates at least double keystrokes with every key pressed. Also the remote from my pana tv suddenly seems to work, although no hdmi cec devices are listed as input devices, so nothing to disable there.

My setup: htpc (1st gen i5 w. gt1030) on pda-v100hd with 42" pana ips. hdmi -> spdif splitter between htpc and pda-v100hd.

As an extra treat, dts passtrough isnt working anymore. I was always able to have the hdmi output for normal and passtrough use. Now on passtrough only ac-3 works, no dts. Could this have something to do with the gt1030 being all that new?

I would stay away from them cheap atom boxes. These are the so called "cherry trail" intel cpu's, and have given me a fair amount of headache. These are often shipped with 32bit uefi firmware. So altough the cpu has nice specs and has native 64bit support, because of the 32bit uefi, you will never likely to be able to boot 64bit LE , or other software. There are various attempts made, but nothing really ever was there to stay. I got rid of all 32bit uefi hardware; in the end wasnt worth the misery. These boxes normally run 32bit windows (10).

Hurray! Got me a "working" gt1030 setup, with the LE "extended" beta version. Needed to force the nvidia driver as mentioned before, system boot time is also as mentioned pretty long, but the system runs. Even gpu temps are shown. "normal" h.264 live tv playback is fine. no hevc hardware decoding.

For those like me, who just tought the 1030 card would work out of the blue, and to find out it doesnt, this solution is enough to bridge to gap until stable LE builds with stable nvidia drivers are released.

And yes i know, i should have read and search the forum first before buying the gt1030

I am unable to find the LibreELEC-Generic.x86_64-8.0-devel-20170216 build; i just got the gt1030 in now am unable to use it. Where would one download this beta release? Seems LE has no archive to browse through. Can anyone help me get this build?

Quote from gujal

dipswitch

If you had configured the box with network and enabled ssh before upgrading to 8.0.2, then you should try ssh to the box. There was an issue when going from OE6 or LE7 to LE8 where the display goes blank, basically Kodi 17 hangs.

The solution for that was to ssh to the box and move .kodi to .kodi.old and reboot

Thanks, going to give that a try.

Quote from kszaq

I used to do this but people mix issues in threads. There is a sticky post with a request to create a new thread for every issue but most people don't care to read and/or apply the request.

This is not true. From the very first build I put the information about missing fbdev driver for S912 in the first post. Before I published my first build (after LOTS of experimenting and work) there was a thread that explained again and again why there was no build for S912: thread-1653.html

Please remember that developers are also people with daytime jobs and families, they also commit their time to development.

I have to agree that the search engine is not very friendly, let's hope it changes when the forum software is upgraded this weekend.

We will see. It the mean time i tried to flash 8.0.2 with .nocompat . My s802 box now wont boot anymore. It shows the bootlogo and after that the hdmi port wont output any signal. Now i have to reinvent how to unbrick the box; it was a long time ago when i did it (from android to LE). Seems i needed some amlogic bootfiles on usb/sd along with a zip file.... Maybe when i get the time to do this i can write it down and make a thread for it, so that others can read it, somekind of "first flash / unbrick" tutorial.... Or does this also already exist and i'm really that ignorant

Quote from Demetris

Thats why in every forum i have been there is always a search button.

Στάλθηκε από το Moto G 2014 μου χρησιμοποιώντας Tapatalk

This is true, unfortunately searching forum with it's built in engine is hardly an option, because of the terrible search engine of forum software. When a forum is opened to google and one can use googles engine , there is some relief. But for forums that are closed to google, this becomes unworkable.

Update: the forum search engine didn't find the nocompat issue. When reading for half an hour and didnt find the issue, i turned to google. luckily google search engine did. It was described 14 pages back.

Quote from Demetris

I wont bother keep helping users that stubbornly don't read the solutions on this thread.
Community is to read understand execute we don't offer a free support service here.
Regards

That's not a really nice reply. This thread now holds 50+ pages; the s905 thread more then 200 pages! You can't expect one to spend three days reading an entire thread in search for a solution. When searching threads, often the answer isnt found simply because the topic isnt spelled or formulated correctly. And lots of people have daytime responsibilities and simply dont have the time to go through hunderds of forum pages.

Maybe it's a good idea to open a new thread for each release, and in the first post list the problems users encounter (brief) accompanied with the solution. This would make the forum much more professional looking and user friendly. Now everyting is "thrown" in one big thread, making it impossible to create any sort of structure and therefore people constantly asking the same questions over and over again.

For example: it took a VERY long time before the missing framedriver issue with s912 soc's was explained in a decent way . Now it finally got it's own thread. Even when the alpha s912 firmware was release, there still wasnt any explanation and people where thinking the framebuffer driver was found. Only after some time it was added to the first post that this wasnt the case and a brief explanation was added to this first post. Now finally things are clear for most users.

It is not my goal to be judgemental or critical, but only to offer some "reflection" on how the forum is experienced for average users.

I have the MXIII 1g/8g (with red 4k print), with 8.0.1 on it. When i try to install 8.0.2 it gives me the error of incompatibility for my box. Then it cleans up and resumes booting. I tried both .tar files.

Quote from Soli

I built grub-efi. Just extract this to /EFI/BOOT on LE installation media: MEGA
Extract all files to /EFI/BOOT/ on install media.
After install: copy grub-postinstall.cfg as grub.cfg and bootia32.efi to where /dev/sda1 is mounted, probably /flash/EFI/BOOT/ (you can boot LE live and ctrl-alt-f3 to do this) After this LE will be able to boot from HDD. I only wasted time on this so that I have a way to boot the install media with my 1. gen Mac minis in the future:) These 1.Gen machines don't support legacy USB boot, only EFI USB BOOT.

You're a genius. Don't know why i missed this post. Will be testing soon. Thanks again!

Quote from DaVu

It might not be called "overscan" directly. Just check the zoom options from your TV and play with them.

Could you please tell me which exact TV model it is?

This is true, some tv's have it as an option in the zoom modes "16:9 , 4:3 , true , wide etc", my panasonic has it as an option far away in a sub menu. There are also tv's that can only disable the overscan on specific inputs; older tv's with dvi input sometimes have extra settings to make. But i never encountered a tv which was unable to disable overscan. Normally there's always an option.
[hr]
I found this (crappy) video which shows how to enablen the service menu (at your own risk!):

There also seem to be software updates available for this tv (als at own risk!).

I gave up on 32bit efi. I began with the spo comm device (as mentioned in my other thread), which resulted in nothing. After that, i discovered that an Pipo x7 which i purchased also only could boot from 32bit efi. This gave me the same problems (there is a beta cherry trail build, but nothing official). The pipo x7 also has the nice feature of overheating and becoming totaly unusuable after some "wrong" bios settings (no clear cmos available, piece of cr*p).

Now i'm running LE on "normal" machines with bios or 64bit efi support, no more weird hardware that only costs money and, in the end, doesnt work.

For anyone who's reading this, if you want to avoid a lot of headaches and frustration, avoid all the cheap "quadcore" boxes as sold with intel cherry trail cpu's, or other devices that have this 32it efi limitation. this included the intel compute stick, Pipo X7 (x7s) , basically everything "to good to be true" (from aliexpress, ebay, dealextreme, etc).

If you want a cheap device with proper LE support, look at the supported hardware list, or if you just want to buy something guaranteed to work (and is cheap), buy a raspberry

In the perfect world, you want 1:1 pixel mapping. This means that each pixel outputted from the source is displayed on the screen without being remapped or altered in any way. What appears to be your problem is something called "overscan". This is a relic from ancient time, still present in a lot of tv's these days. it does, as the name suggests, overscan the image and chops of the edges. In the past (thirty years ago ) , this was done to lose crap which was transmitted along with frames, such as tv text among others, and distortion in the analog broadcast.

What you want to do is search in the settings of your tv, for a setting which disables the overscan function. Recalibrating the screen in kodi is something you want to avoid. With this option, you'll still have the tv overscanning each frame, and then kodi displays it's image in a cropped fashion. You'll effectively lose resolution and add distortion.

Quote from Daz

I completely agree with Poida, its definitely not unreadable.

You really cant expect people to read 156 pages??
[hr]

Quote from sentry23

I had this issue with 2 boxes before, and in both cases running installtointernal twice did nothing.
Flashing another older generic MXQ Pro android firmware solved it on one box (install other Android, boot from SD/USB, installtointernal), but the other one just flat out refuses to run from internal.
(first one was generic no-brand MXQ PRO 4k, the one with issues is an Acemax MXQ PRO 4k)

Are you able to send me your generic mxq pro firmware which did the job for you?

With 156 pages , this thread becomes unreadable.

I have the MXQ PRo 1gb s905. Everything works fine running LE from usb. Even the installtointernal gives no errors. Only problem when i installtointernal and reboot, the screen stays black, nothing happens. When in insert the usb stick + toothpick it runs LE again. I can also reflash to android with amlogic tool. So only running (booting) from internal doesnt seem to work. Any advice?

flashed the latest firmware. stock remote is working , mce remote still isn't (worked before).

Quote from nikosgrgr

I have MXIII 2G to....put it on confing folder..... remote.conf - Google Drive

That worked, thanks! Now the stock remote works again. Only mce remote still isnt (ir receiver light is blinking)