[ROM] Beelink Mini MX3 II / M8S II TVStock Nexus ROM (Android TV)

[XuanLee]

I was asked to remove these by other users, and agreed because they're not in the Nexus Player, ADT-1 or NVIDIA Shield. (In fact, I swapped in the SystemUI.apk from the Nexus Player.) If you want to put it back, just swap back the SystemUI.apk from the Nano or Stock variants using CMFileManager.

Guest Navigation bar is OK,but Statusbar allway show,it's not auto hide

I still get system ui errors. Does that mean I have to re-flash the rom?

Yes, usually that's a sign that your initial flash was done with the OTA update (.zip file), which is designed for incremental updates. You could try a factory reset, but the safer bet is to flash from the burn package (.img file).

[XuanLee]

I was asked to remove these by other users, and agreed because they're not in the Nexus Player, ADT-1 or NVIDIA Shield. (In fact, I swapped in the SystemUI.apk from the Nexus Player.) If you want to put it back, just swap back the SystemUI.apk from the Nano or Stock variants using CMFileManager.

Oh very thanks! Navigationbar & statusbar are auto show/hide? And a some other app is work? ( not FC )

[Gregoire]

I still get system ui errors. Does that mean I have to re-flash the rom?

Guest How to add navigationbar & statusbar on AndroidTV ROM?

I was asked to remove these by other users, and agreed because they're not in the Nexus Player, ADT-1 or NVIDIA Shield. (In fact, I swapped in the SystemUI.apk from the Nexus Player.) If you want to put it back, just swap back the SystemUI.apk from the Nano or Stock variants using CMFileManager.

[XuanLee]

Guest How to add navigationbar & statusbar on AndroidTV ROM? Thanks
p/s: I try add framework & systemUI other and navigationbar & statusbar are OK,but some other app FC on AndroidTV Rom this.

Okay, the AMPAK update for the Mini M8S II and other TV boxes with wireless chipsets from that manufacturer has been updated with new OEM kernel and drivers from the rv112 release. I've done a quick smoke test on my box, but please let me know if you experience any problems. No need to do a factory reset or wipe the data or cache partitions.

Well, there's no codec fix in rv112, just the usual bootvideo workaround. The MEGABOX splash and boot video are nice, but there's no end loop and so the first time I powered up the box I thought it had hung. Turns out it just ran out of video.

There are a bunch of new bundled apps in PreInstallApp.tar, and some updates to the VideoPlayer and Camera apps. In my system/framework diffs, I see only changes to framework.jar and services.jar in the PhoneWindowManager and camera CaptureRequest classes, respectively, that seem to be coming from Netxeon (who already contributes to the Beelink firmware). In /system/lib, the wireless drivers seem to have substantial changes. As for the system apps in /system/priv-app, there were just some behavioral changes to the nav bar in SystemUI and the RGB fix added to TvSettings.apk (which I already have).

So, my conclusion is that I need to update my AMPAK updater to get the new wireless drivers, but that nothing else here would drive a major update for any variants of this custom ROM.

[minixfreak]

Yea I'm hopeful too

Okay actually the firmware is rv112 not rv111 ... could u post chnagelog

Funny that the box didn't offer it up as an OTA update, but I found the burn package on China Gadget Reviews and am downloading now. (ETA 3 hrs) I'm still hopeful that some day one of these will include an actual brightness fix for the Amlogic codec.

[minixfreak]

Okay actually the firmware is rv112 not rv111 ... could u post chnagelog

[scooter2014]

Mistakenly its more like they finally fixed thongs long time fixed in this rom.... Get change log youll undersrand.

[minixfreak]

They have released mini m8s ii firmware rv111 in the last 24 hours ... no change log yet but they probably fixed a lot of bugs on this and possibly rebuild ur android tv to this new firmware

Would it be possible to add it into the shutdown menu? So if I make a long press on the "Power Off" button on the context menu which appears there should be a "Reboot" option.

I agree that adding Restart (plus Sleep and Recovery?) to the Global Actions menu on long press is pretty ideal from a usability perspective, especially if the short-press behavior is configurable in Settings. The only problem with that is that many users forego their IR remote for a Bluetooth remote or the Android TV Remote app, and neither of these have a power button.

[Fenderman]

Eventually I'll add a Restart command to the Settings->About section, just like they did in the PureNexus build for ADT-1. However, with Terminal Emulator a reboot is as easy as launching and typing "reboot" or "reboot bootloader". That's almost as fast.

Would it be possible to add it into the shutdown menu?
So if I make a long press on the "Power Off" button on the context menu which appears there should be a "Reboot" option.
That would be great!