Posts by Jeffers

Quote from Mr.Brown

Its called "HD and up", not "HD only". Unfortunately "HD and up" means "720p and higher resolution".

The thing is, when hardware acceleration is used for 720p content, its using the upscaling built into the ARM SoC. That means its a shitty upscaling quality.

The optimal setting would be "1080p and up", so that everything below 1080p would be decoded and upscaled by the CPU! Some ARM SoCs have strong CPUs and ideally all content that is not native 1080p, should be decoded by software and also upscaled by software, like Lancszos 3.

1080p doesnt need to be upscaled (on a 1080p TV), thats why the optimal setting here would be to use hardware acceleration starting with 1080p.

What Im saying is, there should be more options to "HD and up". Like "Full HD and up" and also "4K and up".

Let me use the Nvidia Shield as an example with SPMC. It has a powerful CPU, that can decode 1080p content easily by software. Or decode 720p with software and upscale with Software it, f. e. as Lanczos 3.

What would be ideal here is to have "Full HD and up" hardware acceleration, which would mean that all 1080p content would be decoded by the hardware. And all resolutions below, would then be decoded by software plus upscaled by software.

that "HD and up" is very unoptimal, because it uses hardware acceleration for 720p content with shitty upscaling quality. It needs more settings, f. e.:

Always

Never

"HD and up"

"Full HD and up"

"4K and up"

Right now with Shield and SPMC- If I want to decode 720p material by software and upscale it by software (lanczos 3), I have to DISABLE the hardware acceleration COMPLETELY. Why? Because the setting "HD and up" begins using hardware acceleration with 720p resolution, which is dumb.

I DONT want to disable hardware acceleration comepletely. I only want to use hardware acceleration with 1080p content or higher resolution than 1080p. And everything below 1080p to use software decoding + upscaling.

I dont know, if you still dont get it after this post, just forget it alltogether.. It seems like understanding basic things is sometimes hard.

Display More

I thought it was best to let your TV do the upscaling?

Quote from frequenzy

on two of my cheap android boxes, the default remote.conf from android doesn't work with LE. hence need to modify manually.

That's what happened to mine

I didn't realise it was copied automatically [8.2.0.1] LibreELEC 8.2 for S912, thanks for infor Pelican, I will have to look more closely at my SDCard, maybe I can modify the one copied automatically

Quote from jtsarnas76

On android its located in /etc folder. Copy that to the configuration folder in libreelec. Job done!

Just curious

If it's that easy why would someone generate a remote.comf from scratch?

Quote from blindhai

Why would you care for Android? What are the advantages?

Android apps, UK TV Catchup, utilities etc...

Quote from Shonk

i use this to save me picking my fat ass up

details?id=me.thomastv.rebootupdate&hl=en_GB

Looks good, all we need now is a reboot to nand app

I have used CPU Z to determine what processors I have in my two older android boxes.

CPU Z reported one as a Cortex-A5 (MXQ 1GB/8GB) and the other as a Cortex-A9 (MXlll 2GB/8GB).

How do I convert these CPU references into SXXX references in order to determine which LibreELEC I should be trying to use?

If it's possible?

Quote from ky41083

Yes, it was recommended at some point to not rename the dtb in the .update folder. Don't remember by whom.

It sounds like this may no longer matter though, given above feedback.

Is your statement correct given:- [8.1.10] LibreELEC 8.2 for S905/S905X

Quote from funabashi

Ok USB works fine now.

But another issue , my remote control doesnt work..

You should find a remote.conf here:- remote.conf repository

Or, build your own:- Create remote.conf from scratch

Quote from estimadarocha

i also received a bad one.... but flashed it to emmc before i read the warnings.... until now everything it's working

Now I am also based on this [8.1.10] LibreELEC 8.2 for S905/S905X warning your box should be bricked?

Maybe not the whole batch of eMMCs were bad?

Quote from wrxtasy

Yes agreed.

I forgot to upload the correct dtb.img file into the MECOOL directory for the M8S Pro+

I've now since uploaded the correct dtb.img file and yes the rear USB2 port now works along with the tested Analog Audio and the IR remote:

Index of /MECOOL/

WiFi is never going to work due to no Linux WiFi drivers available, but my v4.0 CSR Bluetooth USB dongle does work.

Also be aware there is a bad batch of M8S Pro+ boxes being sold with faulty eMMC storage, that when flashed with new Android Firmware brick themselves.

I suppose that is what happens with very little quality control or testing at the ultra budget end of the media player market.

Display More

I have received a 'bad' M8S Pro+

Will I be able to run LibreELEC by booting from SDCard without bricking it?

Quote from delz

H96 PRO Plus KODI 17.3 Android 7.1 Amlogic S912 TV BOX 4K 3GB/32GB 802.11AC WIFI 1000M LAN

33 quid. Isn't this extremely cheap for the H96 Pro+ ? 32 GB and 3 GB ram. Geekbuying charges $60 or so. Is this for real? And have anyone tried to install the H96 Pro Plus to internal? I can't use SD.

MOD EDIT: Product Link deleted. Please read forum Rules Above

That offers ended, usually about £65, so I would say very cheap at £33

Quote from hillz

Is there a way to add an option in the shutdown menu ? I installed LibreELEC to my SD Card and I want to add "reboot to internal storage" in the shutdown menu to boot to android automatically without unplugging the sd card. I'm using amber skin

See this post from bubblegum [8.1.10-rc1] LibreELEC 8.2 for S912

It worked for me using Aeon Nox 5 skin

Quote from ChimeyJimmey

Would anyone be able to help me with the H96 Pro+ (S912, 3/16) not powering on from its remote, when shut down?

Android (7.1.2) is working fine, so there must be some esoteric setting for LE... Ideas where to look further?

Thanks in advance!

Create remote.conf from scratch

Quote from r2d3

I upgraded my mini m8s II, but think i forgot the device tree or selected the wrong image (tar not the.img.gz). I'm not sure. But now my player boots and gets stuck on a google tv screen (boot screen).

Any idea how to fix it?
Tried making a new bootable usb with the image and correct device tree, but won't work. Won't boot using the usb (tried both usb-ports, used the toothpick and then powered the device).
Didn't try to make a new sd-card (will try this this afternoon).

Any other ideas? Is my device bricked?

See section:- If you forgot to use a new device tree or used wrong one and your device doesn't boot in first post

Quote from Shonk

I have a H96 pro+ if you give me the dtb your using i will test it on mine

I used this one and worked OK for me gxm_q200_3g.dtb

Quote from kodiuser1

No I didnt want android anyway. I tried using the guide already posted but could not get it to work.

I had no luck with it either

Quote from kodiuser1

Yes both wifi 5g and 2.4g and LAN work. Only issues are no boot logo at startup and no power on from remote. Another thing missing that would be great is suspend. This was an option in OE 6.0.1 but missing here.

Do you have a link to instructions that would allow me to install from SDCard and keep Android on Nand, if it is possible?

Quote from bubblegum57

usb port, right hand side rear. Haven't tried others.

good news, it boots from sd card, added gxm_q200_2g device tree

bad news, my sd card is now stuck in the holder, the socket has been dodgy from when I got it.

Luckily, it still boots from the usb

Any good guides on how to dismantle the H96 pro?