I had wake up from suspend with CEC issues and also wanted more options than the tv remote could offer, so I bought the Harmony Companion with Bluetooth Hub, right from the start I had a very hard time connecting N2 with Hub/bluetooth, finally it paired and worked perfect quick and snappy just like a keyboard.
The issue is you really don’t know when it will work or not it can work for 2 days and suddenly after suspend or reboot it will not connect what so ever I have spend hours on this issue and really need help fixing this, @jbrisbin have similar problem here BT Keyboard Fails to connect H96 Pro + CE 9.0.1 [WORKAROUND FOUND]
Please let me know what logs is needed to look in to this, thanks…
EDIT: one of the errors I seen when trying to connect is “Input/Output error”
On the other hand, I do not know if it is me who kidding, but I have the impression that the fast forward is much more reactive. Very good! On the other hand, there are artifacts that sometimes appear when you make a quick advance on Billy Lynn (4K HDR 60 i/s).
And that was already on the GT1 @ S912 a few months ago, before the update “Automatic color space / color depth switching”. But maybe it’s something else …?
The picture on N2 looks better, and you need to re-calibrate with test pictures running on N2.
Hue, Saturation and Black level differ on these two boxes.
Edit: I use 3 Amlogic boxes, S905X, S912 and S922. To get best picture I have 3 different calibration settings, one for each.
I guess the S912 is ok because I have the same result on platinum Bluray and internal player of the TV.
I think I can not explain myself well. I’m not talking about colorimetry, I’m talking about the color gradient. Look in the sky, with the N2, we see a banding effect. https://en.wikipedia.org/wiki/Colour_banding
It is obviously much more obvious in “real”, than in photo.
OK this is different then What build are you using?
I heard reports of color banding. I need a sample. It’s probably another post processing Bullshit from Amlogic like the sharpening that lead to cartoon effect.
Yeah it was captured with it-keytble so will try UART route as need to try and understand what is happening with the Bluetooth Hotack_RC as it is also not functioning correctly within CoreELEC also.
Been using the aboxwireless.evmap as that is for Hotack_RC but the button mapping is a bit off and the ok/enter button does not register anything, I say anything it has worked perfectly twice but after reboot back to not picking up ok/enter which makes it non usable. As /etc is no writable so will maybe have to clone and mess around with the maps or edit the filesystem prior to flashing.
I have a few nodemcu lying around that look flashable for UART so just need to dig some female to female jumpers and have a look at getting that going to start with
