Posts by Magnum

Quote from Poida

Magnum - You probably should remove the direct links to sellers in your post (breaching forum rules)

done...

kszaq

Could the H96 Plus S905 Quad Core 2GB DDRR3 work with LE?
I know that no one can ensure Le works 100% with this box...

Anyway I think it's a good starting point. What do you think about it?

Thanks

Magnum

Thanks guys.

For me it's important not to see the green screen after install LE.

I thought to buy the H96 Plus. It has 2.4GHz/5GHz Dual-band WiFi: 802.11 a/b/g/n/ac, 10/100/1000Mbps Ethernet and 2G RAM. Could it go well?

Or the NEXBOX A95X... but it hasn't WiFi ac, and I don't know if it has 10/100/1000Mbps Ethernet.

Both have the same price.

Magnum

Hi,

I bought a Mecool BB2 Pro Aml S912 device. Unfortunately, for the issue described in this post, there is no solution now.
So I thought to buy a S905 device and load, via SD card, LE as said here.

Could I have the same problems or LE can solve this?

Thanks to everyone could answer my question.

Magnum

Quote from mmpp

Your box uses an amlogic S912 SoC, while the fix we are discussing here is specific for S905(X) SoC. Also the fix is for Libreelec, not Android.

Currently the box maker is the only one who could help you.

Hi MMPP,

Thanks for reply.

I thought to buy a TV box with SoC 905. Then install LE.
Anything to solve my problem with green screens ... waiting Videostrong solve this problem on BB2 Pro. Or waiting a LE for 912.

I have read this thread: thread-1982.html

What do you think of the H96 Plus model? Also to minimize the expense.

It might be fine for LE?

As said from Kszaq... "My firmware is aimed to work on most S905/X devices. I have no list of boxes that work because except for officialy supported devices I own only 1 S905 and 1 S905X box."

I accept suggestions ...

Thanks in advance to all for possible replies.

Magnum

Hi guys,

the same problem for me.

I've just bought the MECOOL BB2 PRO Android 6.0 TV Box 3GB DDR4. The TV box is connected to my Philips 32PFL5604H. Tv Set is up to date (last update from Philips is 2010 dated).

BB2 Pro specifications:

Brand: MECOOL
Model: BB2 PRO
Type: TV Box
GPU: ARM Mali-T820MP3
System: Android 6.0
CPU: Amlogic S912
Core: Octa Core
RAM: 3GB
RAM Type: DDR4
ROM: 16G
Max. Extended Capacity: 32G

In the support forum of others Android Tv Box (this one too) it is suggested to turn on the RGB Option, if present.
Fortunately this option is present in BB2 Pro...(default disabled)... but If i active this option... it works for a while.

When I switch between TV Box options screen becomes green again (not always...but often). I switch again in the RGB option (active) and re-active the same option.
In this way the BB2 Pro turns to work good again. Sometimes... after the green screen, TV Box turns to work well without doing anything.

I changed the HDMI cable...set to 720p 60hz (from 1080p 50hz)...but nothing.

The screen turns green even while watching movies with Kodi. Today, for example, about 30 minutes after the start of movie. (1080p 50 hz).

Here some links to my problem.

WP_20161225.mp4 - Google Drive
WP_20161227.mp4 - Google Drive
WP_20161229.mp4 - Google Drive

In the Minixforum I found this:

Quote

"That issue has to do with the color space the HDMI driver uses for displaying video content. I've seen this before with my Open Hour Chameleon Android based media player and there it was only resolved after the developers gave us the option to select the color space to use. By default they were using YUV444 which isn't the preferred color space of my TV (which seems to use RGB). So when the color space information in the HDMI data stream is missed somehow during display (temporary hickup or timing mismatch) the TV picks the color space it prefers (in my case RGB) and displays the YUV444 stream as a RGB stream. Since the Y component (Luminance or brightness information) is mapped to Red and U and V (which normally encode the color components) are mapped to Green and Blue the picture starts looking like its rendered in Green and Purple shades.
The only solution for this issue (as de OHC devs discovered) is to give us the options to set the color space used by the HDMI driver. There are no other solutions for this problem for TV's/Displays that use RGB color space by default.
This issue was also a major problem for UPC's Horizon media boxes and TV's from all major manufacturers (Sony, Philips, Samsung etc) were hit by this until they did the same as the OHC devs."

Videostrong give me the last firmware available...but nothing change. I wrote several emails to Videostrong support, followed their advice, but nothing has worked.

A user in another forum says:

Quote

"Hi, I have the same problem on a Philips 42PFL8404H/12.
It seems to be an erroneous AMLogic HDCP 2.2 implementation that doesn't default to HDCP 1.x when HDCP 2.2 handshaking fails as it should for Widewine DRM purposes.
Hope the next firmware solve this problem."

How is it possible to resolve this issue?

Suggestions?

Thanks

Magnum