UPDATE - Marschmallow - Wasser Firmware for Beelink R89

[wasser]

Hi wasser!

Do you have plans to deal with an interlacing in Marshmallow build?

Can you make "Connect to PC" enabled by default on the first start? It can help to configure a box while it is still connected to a computer after flashing and allow to configure it right there.
For example, 2.0.9a is perfect in this. Need just to wait until a box will boot.

1. the interlacing issue is caused from the binary libffmpeg. I don't think i can fix that without having source code.
2. "Connect to PC" enabled by default on the first start in 4.0.8

[wasser]

Thanks for this new MM rom. I had jumped on my first R89 from KK rom to this 4.0.7; everything went fine flashing the box with Android Tool, first "Eraseflash" and then "upgrade".

There is a major bug for me; Wifi 5G does not connect, the box can see the signal when the router is set on channels from 36 to 140 but does not connect, after a couple times trying appear "wifi connection failure"; when router is set to any channel above 149 the box simply can not see the signal at all. My AC router is set to VHT(80+80) width channel. The other R89 running with your LP rom 3.0.5 connect without a problem to wifi 5G.

wifi 2.4G and ethernet work fine.

Regarding to xbmc, I had tried RKMC but there are a lot of problems with sound; many times I had video without sound. I'm using spmc 16.4 working fine, but i remark that I do not use any PT equipment.

Youtube 1080p - 60 fps has the best performance ever for me.

wifi issue is fixed in 4.0.8. I added menu to specify the wifi region code for wifi. You should set the correct region code.

[amclean123]

Thanks bluesmanuk! The reboot helped. HDMI audio passthrough works but the video is not as smooth as when I used SPDIF audio.

[bluesmanuk]

are you using the custom libffmeg for mxplayer by testing?
does Passthrough using HDMI and SPDIF still working MX Player if you only use the stock libffmpeg?

I'm using libffmpeg.mx.so.neon.1.7.32

I'll give it a test without the custom option and report back.

Update: Re-installed 1.7.40 without custom codec and passthrough does work with HDMI and SPDIF

I also tried 1.8.3 and passthrough works with HDMI and SPDIF too without the need for a custom codec libffmpeg.mx.so.neon.1.8.0

So if I am guessing correctly, you have integrated the custom libffmpeg into the ROM?

If so, could this potentially be what is preventing KODI/RKMC etc from utilising the passthrough?

[andreyh]

1. the interlacing issue is caused from the binary libffmpeg. I don't think i can fix that without having source code.
2. "Connect to PC" enabled by default on the first start in 4.0.8

1. Which libffmpeg.so do you use? What a project is it from? (ffmpeg is open source, it is possible to compile it from scratch using Android SDK. Example: https://github.com/vecio/FFmpeg-Android,) Here is a compilation of sources: https://trac.ffmpeg.org/wiki/CompilationGuide/Android
2. That's great. Now it economies a lot of time.

Thanks.

[digitalriver]

On my ubox 8G (beelink R89(8GB rom)) the 4.0.7 and 4.0.8 firmware stops working(unprompted reboot and endless logo) after enabling bluetooth mouse. In previous firmware(4.0.6 and earlier) all was good. Wasser, help, please! If you can

[BTR11]

wifi issue is fixed in 4.0.8. I added menu to specify the wifi region code for wifi. You should set the correct region code.

BIg thanks wasser, this is great, as usual on Android Rom development you put the pace, you show the right way. Now after had been chosen "USA region" 5G Wifi it´s working fine with full power signal and full speed; at the beginning I had lost a couple of times the connection as if the "wifi region" chosen won´t be remain selected (just speculation), but then after some time of use the wifi connection had been stable, working very good now.

"version 4.0.8

• disabled initial lock screen --> Thanks, this it´s good.
• added menu to specify the region code for WIFI (Settings->Wifi->Advanced Wi-Fi->Wi-Fi region code) --> For these android devices this it´s revolutionary, looks like as a windows wifi controller driver menu
• fixed issue in HDMI Bitstream (i don't have the equipment to test this! please test yourself and give the feedbacks) --> I cannot test it neither because I don´t have as well this type of equipment
• improved nfs mount --> I´m not sure if this produce a strange name when an USB unit is connected, appear name with numbers and letters like A0DB-39FF but not usb1, usbstorage1 or so...?
• fixed issue in 4K 50/60HZ --> It´s better now, but still there are black screen / sound cut-off around every 30 seconds; and some not very frequent flickering on 4K 30Hz, 25 Hz and 24 Hz

Some more comments:
- AV - TV out works fine now however it´s not mentioned as a fix on the changelog
- In my test, MX player does not play the content when HW+ decoder it´s active; but plays fine with HW decoder
- Sopcast apk does not work, with acceleration active or disabled, it´s the same; not sure if this is application related or it´s something with the firmware
- xposed 3 alpha4 with frame v86 for SDK23 it´s working Ok.

Considering that Im doing the test on the R-89 that never can run properly nor stable the LP roms, this performance with MM it´s brilliant. Thanks Wasser, android 6 definitely made the R-89 a much better device that it was sold to us from Beelink; may be when the next android N be out you surprise us with a new flavor for the R-89.

I have a specific question for you wasser related to the I/O scheduler: you use by default "cfq"; before was told that "noop" and lately "deadline" in this particular device R-89 had produced some performance improvements and overcome some deficiencies; had you been able to checl by yourself about it?; I change always on R89 with "non frill CPU" the i/o scheduler to "deadline", but not sure if this it´s counter-productive; my perception it´s that it´s a good change.

[bluesmanuk]

The naming of USB devices I have found can depend upon the app. I have seen some identify a device by name and others with the number/letter combinations.

MX Player using HW by default is preferable to having to manually select HW+, so that should be fine.

Never used Sopcast but worth checking if it is one of those apps that can detect HDMI or requires an unrooted device, both of which can be altered within settings, so worth a check.

[bluesmanuk]

On my ubox 8G (beelink R89(8GB rom)) the 4.0.7 and 4.0.8 firmware stops working(unprompted reboot and endless logo) after enabling bluetooth mouse. In previous firmware(4.0.6 and earlier) all was good. Wasser, help, please! If you can

I don't have a bluetooth mouse but I can confirm that I was able to connect to other devices using bluetooth such as mobile phone, soundbar and speakers.

I know this won't help your specific case but it did remind me that I had forgotten to test BT.

[BTR11]

Thanks blues...

The naming of USB devices I have found can depend upon the app. I have seen some identify a device by name and others with the number/letter combinations

This is a different fact here on this 4.0.8 using ES explorer, something had changed; it´s a strange when you need to refer a location to save automatically a content form i.e recording app.

MX Player using HW by default is preferable to having to manually select HW+, so that should be fine.

Yes this it´s the right way to go here on v4.0.8 and works fine.

Never used Sopcast but worth checking if it is one of those apps that can detect HDMI or requires an unrooted device, both of which can be altered within settings, so worth a check.

On previous KK and LP rom sopcast works fine, not related to HDMI checking nor rooted or unrooted devices; so I will check again but I think it´s not related to those items; looks more related to playback issue into the rom or and app that needs be updated to MM...

[amclean123]

4.0.8 is really nice for HDMI video and audio passthrough! Thanks wasser It's probably just a coincidence but the new ES File Explorer may have corrupted my 8TB network drives.

[digitalriver]

I don't have a bluetooth mouse but I can confirm that I was able to connect to other devices using bluetooth such as mobile phone, soundbar and speakers.

I know this won't help your specific case but it did remind me that I had forgotten to test BT.

Thanks bluesmanuk. Possible, problem not with bluetooth, still alternatively problem with Titanium backup.

[gridlock]

regarding spdif passthrough via kodi?
just wondering bluesmanuk, in the long run, does the autoframe switch affect tvs? i mean after years of use...
thanks wasser for your extreme effort....

[bluesmanuk]

Thanks bluesmanuk. Possible, problem not with bluetooth, still alternatively problem with Titanium backup.

Is your Titanium problem anything to do with write access when backing up by any chance?

[bluesmanuk]

regarding spdif passthrough via kodi?
just wondering bluesmanuk, in the long run, does the autoframe switch affect tvs? i mean after years of use...
thanks wasser for your extreme effort....

I'm not a TV engineering expert and I did put that question somebody more in the know today and they said that in real terms, no it won't make a difference because whilst everything has a failure time, you might be much older and greyer before this happens.