[ROM] Mini M8S / MX3 Nano and TVStock (Android TV) Nexus ROMs

Can I use this image for my beelink mini MX iii (s905 - 2/16)

Yes, and my Beelink Mini MX III didn't even require a wireless driver update. (If you have a Qualcomm QCA9377 chipset, however, the Android 5.1 updater is available here.)

UPDATE: Sorry, I forgot that was using the Mini M8S remote. (I've got WAY to many of these boxes cluttering my office.) To use the original Mini MXIII IR remote, see below. Alternatively, you can use a Bluetooth universal remote, which is what I recommend.

[Agronur]

Thanks for your effort. Can I use this image for my beelink mini MX iii (s905 - 2/16)

[manal_vedder]

Changelog (20170607):

• 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 on TVStock.
• Resolved blocking issue with WiFi setup in SetupWraith that wouldn't allow progress past language selection.
• Removed several libraries that are no longer required.
• Updated for latest Open GApps build (20170607).

EXCELLENT, UPDATE ON ARRIVING HOME

Changelog (20170607):

• 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 on TVStock.
• Resolved blocking issue with WiFi setup in SetupWraith that wouldn't allow progress past language selection.
• Removed several libraries that are no longer required.
• Updated for latest Open GApps build (20170607).

[demonpt]

first boot takes a little but all ok !

[demonpt]

top job tested both roms outstanding !

[HiBoU974]

Is it possible to replace some files in the M8S update to fit with the mini MX3 ? If it's possible could you please say me which files i have to replace

[hellfire_my]

Okay, I was finally able to reproduce it on my end...but only when I had no connectivity. Plugging in Ethernet allows it to proceed past the language selection, and wireless setup is available once you make it to the Settings or TvSettings apps. I'll look into this over the weekend, as it seems to have something specifically to do with WiFi configuration in SetupWraith.

That is strange, I plug in my Ethernet it doesn't able to get past the language selection.

Okay, I was finally able to reproduce it on my end...but only when I had no connectivity. Plugging in Ethernet allows it to proceed past the language selection, and wireless setup is available once you make it to the Settings or TvSettings apps. I'll look into this over the weekend, as it seems to have something specifically to do with WiFi configuration in SetupWraith.

[hellfire_my]

I had tested successfully flash the rom yesterday, however was stuck at choosing language wizard. Once selected a language, it just keep showing the same language selection page. I had tried to plug in LAN network still the same

my Android TV box is a Mini M8S with S905 and 2G/8G. i think the problem is not on WIFI but SetupWraith have some bug.

Odd that I can't reproduce it on my end then. Is anyone else seeing this?

[Jonh_Dimagio]

Yes, I've confirmed that both have the same wireless drivers. In fact, other than a few files specific to Android TV, the kernel, framework, binaries and libraries are identical. They're built on the same stock firmware, and it's really only the APKs that have changed.

my Android TV box is a Mini M8S with S905 and 2G/8G.
i think the problem is not on WIFI but SetupWraith have some bug.

can you check if both ROMs have same wireless drivers ?

Yes, I've confirmed that both have the same wireless drivers. In fact, other than a few files specific to Android TV, the kernel, framework, binaries and libraries are identical. They're built on the same stock firmware, and it's really only the APKs that have changed.

[Jonh_Dimagio]

Both include the same stock wireless drivers. I was under the impression that you'd installed a wifi driver patch or were running on hardware other than the target Mini M8S. Is that not the case?

As for the different behavior, that's not unexpected. The Nano variant includes SetupWizard and the TVStock uses SetupWraith, which are both from Google but could handle failures to establish a network connection differently.

no, i am not using a wifi driver patch.
can you check if both ROMs have same wireless drivers ?

...if you say that is a WIFI driver problem, why you have different WIFI drivers at 2 ROMs?

Both include the same stock wireless drivers. I was under the impression that you'd installed a wifi driver patch or were running on hardware other than the target Mini M8S. Is that not the case?

As for the different behavior, that's not unexpected. The Nano variant includes SetupWizard and the TVStock uses SetupWraith, which are both from Google but could handle failures to establish a network connection differently.