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

[Guest]

Bluetooth Xiaomi Mi Box remotes can be purchased cheaply on aliexpress. I was wondering if it would be possible to turn on/off these units using a xiaomi bluetooth remote. If not, would it be possible to support this functionality?

Yes, and I ordered one myself last week.

[professeur83]

Changelog (20170606):

• Enabled multi-user support.
• Added kernel module for many USB Bluetooth dongles (btusb.ko).
• Reverted to AOSP keyboard, since Gboard just doesn't have the necessary D-pad navigation support. Leanback keyboard is still also available.
• Switched from spoofing the Xiaomi Mi Box to the Nexus Player.
• Removed several libraries that are no longer required.
• Updated for latest Beelink firmware OTA update (112M0) and Open GApps build (20170606).

IMPORTANT NOTE: This custom ROM is still based on the Beelink Mini MXIII II, but it's the version that contains the AMPAK wireless chipset drivers. These support most AMPAK chipsets, but not the Qualcomm QCA9377. An update for that will be forthcoming...basically as soon as Beelink posts the 112M0 update for QCA9377.

On the bright side, this means that the ROM will work AS IS on the Mini M8S II, which uses the AMPAK AP6255.

Hello and thank you ! You are a killer this firmware is on top

[seikt]

Yes, and I ordered one myself last week.

Sweet.

[EagleEyeXZ]

Magendanz do you also start with android 7.1.1 sdk? SuperCeleron said he does not have time now to start with it but what i read nougat can have a lot new features for the s905x chipset like HD audio

[Guest]

Magendanz do you also start with android 7.1.1 sdk? SuperCeleron said he does not have time now to start with it but what i read nougat can have a lot new features for the s905x chipset like HD audio

Not on this hardware, but I've started a custom Nougat build on the M8S Pro...right now blocked because I'm lacking a functional TWRP build for that box. I could potentially also do it for the GT1, but they've only got a beta release at this point which is still pretty rough around the edges.

Surprisingly, I've gotten the farthest on the Z28, which uses a Rockchip RK3328. That chipset, however, has problems in that it seems to be natively running in 720p vs. 1080p.

[EagleEyeXZ]

Oh damm... maybe later?

[sweetnonso]

Changelog (20170606):

• Enabled multi-user support.
• Added kernel module for many USB Bluetooth dongles (btusb.ko).
• Reverted to AOSP keyboard, since Gboard just doesn't have the necessary D-pad navigation support. Leanback keyboard is still also available.
• Switched from spoofing the Xiaomi Mi Box to the Nexus Player.
• Removed several libraries that are no longer required.
• Updated for latest Beelink firmware OTA update (112M0) and Open GApps build (20170606).

IMPORTANT NOTE: This custom ROM is still based on the Beelink Mini MXIII II, but it's the version that contains the AMPAK wireless chipset drivers. These support most AMPAK chipsets, but not the Qualcomm QCA9377. An update for that will be forthcoming...basically as soon as Beelink posts the 112M0 update for QCA9377.

On the bright side, this means that the ROM will work AS IS on the Mini M8S II, which uses the AMPAK AP6255.

Nice update, thanks for your work as always. Still waiting for the VPN fix please.

[Guest]

Still waiting for the VPN fix please.

From what I can tell, this VPN problem is just a generic issue with the app bar (a.k.a. action bar) running on Android TV. Several apps (including Settings and Terminal Emulator) are missing their toolbar icons on the right and the Up (<) button on the left isn't working.

[Guest]

BTW, a Qualcomm QCA9377 updater is now available here. It's based on the 111M0 kernel, but seems to work fine. I'll update it when Beelink eventually posts the 112M0 update for the QCA9377.

[sweetnonso]

From what I can tell, this VPN problem is just a generic issue with the app bar (a.k.a. action bar) running on Android TV. Several apps (including Settings and Terminal Emulator) are missing their toolbar icons on the right and the Up (<) button on the left isn't working.

In your opinion, is that fixable?

[Guest]

In your opinion, is that fixable?

I don't know yet, but I'm actively looking into the issue.

[sweetnonso]

I don't know yet, but I'm actively looking into the issue.

Ok many thanks, patience is the key

[Stamp75]

Changelog (20170606):

• Enabled multi-user support.
• Added kernel module for many USB Bluetooth dongles (btusb.ko).
• Reverted to AOSP keyboard, since Gboard just doesn't have the necessary D-pad navigation support. Leanback keyboard is still also available.
• Switched from spoofing the Xiaomi Mi Box to the Nexus Player.
• Removed several libraries that are no longer required.
• Updated for latest Beelink firmware OTA update (112M0) and Open GApps build (20170606).

IMPORTANT NOTE: This custom ROM is still based on the Beelink Mini MXIII II, but it's the version that contains the AMPAK wireless chipset drivers. These support most AMPAK chipsets, but not the Qualcomm QCA9377. An update for that will be forthcoming...basically as soon as Beelink posts the 112M0 update for QCA9377.

On the bright side, this means that the ROM will work AS IS on the Mini M8S II, which uses the AMPAK AP6255.

Great Update: works fine. !!!!
Thanks a lot Magendanz !!!!
____
Box: Mini M8S II S905x
Location; France

[Guest]

Hello Magendanz!

I need a little help...

I own a Beelink GT1 and a Beelink Mini MXIII-II, both with QCA9377-chipset.

Now I just need the right TWRP.img-files for both boxes to make first of all a Nandroid-Backup of my existing Stock Roms before installing your custom roms. Which ones are the right ones to install?

Thank you in advance!

[tanzhuoning]

After apply the latest 20170606 update, my mini mx3 ii can't connect to wifi. I can't turn on the wifi.

Please help, or give me some advise.