Lollipop - Wasser Firmware for Beelink R89

[BTR11]

could you please recheck if this issue appears in 3.0.4a. It's very important to know if it' a regression. One thing you should try in 3.0.5 again: please enable "Settings-Display->HDMI chechking" and reboot again.

Thanks

Hi Wasser, the "HDMI checking" it´s selected by default in 3.0.5 and I had left in that way in my test; I had not experienced any of the described issues with HDMI Mode on v3.0.4a; in v3.0.4a the problems were with the poor quality image on TV-out and screen scale bug on TV-out mode.
I had been reading some about this strange message of "1080p 10 bit" and this can be the root of the problems; apparently v3.0.5 is pushing the output HDMI signal to 10 bit color depth whilst in 1080p; accordlng to the specs of the most 1080p TV (mine is 3 years old, manufactured on the Q1 - 2013) all of them so far are 8-bit color depth, & as well HDMI 1.4 port is not 10 bit color depth capable; this can be done so far only through HDMI 2.0 ports; in my 4K TV I have to connect the device to the HDMI 2.0 port and activate in the TV menu the 10-bit color depth to can obtain this, that is when the 4K - 50Mhz & 4K-60 Mhz mode appear listed in HDMI mode; so, even the 4K TV being 10 bit color depth capable, the default configuration is 4K-8-bit color depth, which give a maximum resolution of 4K- 30 Mhz on HDMI 1.4 & 2.0 ports.
This problem had appear only with this v3.0.5, so if there is a new kernel vs v3.0.4a this can be a regression on the v3.0.5 kernel.

I came accross this statement on the web http://www.trustedreviews.com/opinions/hdmi-2-0-vs-1-4 :

"Just as important as the higher frame rates for Ultra HD/4K HDMI 2.0 enables, the extra bandwidth also means HDMI is able to transport 4K video at 10-bit and 12-bit colour depths. With HDMI 1.4 it was limited to 8-bit."

[wasser]

For respect to your work I had decided to test it right now.

I had tested on Sony TV Full HD; I had reflashed the R89 to start clean, now I had used RKbatchtool ("restore" option), anyway I can confirm with this method the problems are the same; and then immediately flash the kernel with the Android Tool v2.35; this new kernel is dated 28th april instead of 24th of the original, just to be sure that I had done the task.
Well unfortunately the problems reported still are there, no sound when start on 1080p60Mhz; when I had been into recovery the first time went Ok, but when I had try a new reboot and I had tested again reboot to recovery or to the bootloader the problem of incompatible signal had appeared. So the conclusion is with this new kernel dated on 28th of april still the problems are the same.

I want to remark that for first time on my Sony TV HDMI 1.4b port I had seen the label when starting after a reboot of "1080p 10 bit", I didn´t know that this is possible on a 1080p, I believe that this was reserved for 4K resolution on HDMI 2.0 Port; it´s like the R-89 it´s forcing this mode on 1080p60Mhz; The normal label on the TV all the times before had been 1080p. That label shown of "1080p 10 bit" had ocurred only one time, I had not seen it again so far. Hopefully this is of help of you wasser. I have to say good night from my side now; I´m willing to continue testing other fixes you can implement for this problem, later. Thanks.

could you please recheck if this issue appears in 3.0.4a. It's very important to know if it' a regression. One thing you should try in 3.0.5 again: please enable "Settings-Display->HDMI chechking" and reboot again.

Thanks

[BTR11]

i uploaded the new kernel which should fix the issue hdmi mode. Could you please give a try and let me know the result. Thanks!

http://www.freak-tab.de/wasser/kerne...9-lollipop.img

For respect to your work I had decided to test it right now.

I had tested on Sony TV Full HD; I had reflashed the R89 to start clean, now I had used RKbatchtool ("restore" option), anyway I can confirm with this method the problems are the same; and then immediately flash the kernel with the Android Tool v2.35; this new kernel is dated 28th april instead of 24th of the original, just to be sure that I had done the task.
Well unfortunately the problems reported still are there, no sound when start on 1080p60Mhz; when I had been into recovery the first time went Ok, but when I had try a new reboot and I had tested again reboot to recovery or to the bootloader the problem of incompatible signal had appeared. So the conclusion is with this new kernel dated on 28th of april still the problems are the same.

I want to remark that for first time on my Sony TV HDMI 1.4b port I had seen the label when starting after a reboot of "1080p 10 bit", I didn´t know that this is possible on a 1080p, I believe that this was reserved for 4K resolution on HDMI 2.0 Port; it´s like the R-89 it´s forcing this mode on 1080p60Mhz; The normal label on the TV all the times before had been 1080p. That label shown of "1080p 10 bit" had ocurred only one time, I had not seen it again so far. Hopefully this is of help of you wasser. I have to say good night from my side now; I´m willing to continue testing other fixes you can implement for this problem, later. Thanks.

[bloodgnome]

i uploaded the new kernel which should fix the issue hdmi mode. Could you please give a try and let me know the result. Thanks!

http://www.freak-tab.de/wasser/kerne...9-lollipop.img

I will test this also maybe it fixes my TV-Out Issue

[BTR11]

i uploaded the new kernel which should fix the issue hdmi mode. Could you please give a try and let me know the result. Thanks!

http://www.freak-tab.de/wasser/kerne...9-lollipop.img

Yes, I will do it and report back; please let me some time for the feedback, it´s late for me today. Thanks for your work.

[wasser]

@wasser,

I can re-confirm now that after test v3.0.5, HDMI Mode 1080p60Mhz on:
1) Full HD Sony TV - 60 Mhz (this tv set it´s not compatible with 50 Mhz mode)
2) 4K-60 Mhz LG TV (this TV is as well compatible with 50 Mhz)
after each re-boot when appear a not supported mode or not compatible signal than can be cured unplugging HDMI cable and re-plug it again, the sound it´s lost; so changing the mode to a lower frequency make the sound comes back; and after that I can set again the mode to 1080p60Mhz.

If I leave the mode set to 1080p30Mhz and reboot the R-89 the sound is Ok after the reboot.

So I think this can be called a bug on v3.0.5 with the 1080p60Mhz and higher modes, because on 4K30Mhz and 4K60Mhz the sound it´s lost as well after each reboot.

I had tested as well the v3.0.5 TV Mode on a Rear Projection TV, Samsung (NTSC System) and in this is everything fine, not lost sound after rebot, not dropouts.

This v3.0.5 it´s a great rom, with xposed framework working, the air mouse ops very smooth - lag free, and Antutu v6.1.4 scoring 54K without any special overclock; there are just some "buffering" episodes playing through Youtube, but never it´s always sure that it´s fw related, may be it´s the youtube itself. Hopefully you can check what can be the problem added in this v3.0.5 rom to the HDMI mode that it was not present in v3.0.4a. Thanks.

i uploaded the new kernel which should fix the issue hdmi mode. Could you please give a try and let me know the result. Thanks!

http://www.freak-tab.de/wasser/kernel-rk3288-r89-lollipop.img

[BTR11]

@wasser,

I can re-confirm now that after test v3.0.5, HDMI Mode 1080p60Mhz on:
1) Full HD Sony TV - 60 Mhz (this tv set it´s not compatible with 50 Mhz mode)
2) 4K-60 Mhz LG TV (this TV is as well compatible with 50 Mhz)
after each re-boot when appear a not supported mode or not compatible signal than can be cured unplugging HDMI cable and re-plug it again, the sound it´s lost; so changing the mode to a lower frequency make the sound comes back; and after that I can set again the mode to 1080p60Mhz.

If I leave the mode set to 1080p30Mhz and reboot the R-89 the sound is Ok after the reboot.

So I think this can be called a bug on v3.0.5 with the 1080p60Mhz and higher modes, because on 4K30Mhz and 4K60Mhz the sound it´s lost as well after each reboot.

I had tested as well the v3.0.5 TV Mode on a Rear Projection TV, Samsung (NTSC System) and in this is everything fine, not lost sound after rebot, not dropouts.

This v3.0.5 it´s a great rom, with xposed framework working, the air mouse ops very smooth - lag free, and Antutu v6.1.4 scoring 54K without any special overclock; there are just some "buffering" episodes playing through Youtube, but never it´s always sure that it´s fw related, may be it´s the youtube itself. Hopefully you can check what can be the problem added in this v3.0.5 rom to the HDMI mode that it was not present in v3.0.4a. Thanks.

[BTR11]

Does anyone else encounter audio dropouts using HDMI PT with v3.0.5? This was not present in v3.0.4a.

I had dropouts during playback using ZDMC Superceleron, but my connection it´s the simple one, just HDMI cable to the TV, using the TV speakers, I don´t use PT at all. After a couple of test I had found that "default Sound" option on Sounds --> Sound Device Manager had produced that dropouts in my case. So I had set the sound output option to "HDMI Bitstream" and the dropouts are gone; I had understood before that this kind of option marked is for HDMI PT, but in the case of wasser v3.0.5 that is the option that work properly even in my case of simple set up without passthrough; there is some kind of mess with the "default sound" option.

[torbvea]

Thanks for the help! I will do a clean installation again. Hopefully the audio dropouts will be resolved.

[superceleron]

the difference of my RC3 and the final is only the name(removed the RC...) and the logo( they removed the RC).
So no need to update

[bluesmanuk]

Since it's working fine for you and bloodgnome it's probably something wrong on my front. The dropouts is happening occasionally when I use YouTube or Spotify with PCM2.0 audio. When i use SCMC with DD5.1 it's working more or less fine. Do you use 1080p60, Auto refresh rate, HDMI check and HDMI Bitstream in android settings? Did you upgrade to v3.0.5 from a clean 3.0.4a installation?

I do use 1080p60 as I found video playback issues with 1080p50.

Auto refresh rate is on in Android settings and off in SCMC.

I use HDMI Bitstream and not in front of the box right now to confirm HDMI check but I seem to remember playing around with it and leaving it off (I think).

Sync playback to off when using passthrough and on when not.

Managed to do an upgrade directly from 3.0.4a this time, using factory tool 1.33 rather than the usual android tool (although it shouldn't make any difference).

[bloodgnome]

Do you use 1080p60, Auto refresh rate, HDMI check and HDMI Bitstream in android settings? Did you upgrade to v3.0.5 from a clean 3.0.4a installation?

Yes
No (Auto Refresh Rate)
Yes
Yes

I updated from 3.0.3 to 3.0.5.

[torbvea]

I use HDMI PT but get no dropouts.

Since it's working fine for you and bloodgnome it's probably something wrong on my front. The dropouts is happening occasionally when I use YouTube or Spotify with PCM2.0 audio. When i use SCMC with DD5.1 it's working more or less fine. Do you use 1080p60, Auto refresh rate, HDMI check and HDMI Bitstream in android settings? Did you upgrade to v3.0.5 from a clean 3.0.4a installation?

[bloodgnome]

I use HDMI PT but get no dropouts.

Me neither.

bluesmanuk superceleron Since Kodi 16.1 Final is out since 24.04 can we expect a update to the awesome SuperCeleronMediaCenter

[bluesmanuk]

Does anyone else encounter audio dropouts using HDMI PT with v3.0.5? This was not present in v3.0.4a.

I use HDMI PT but get no dropouts.