[ROM] Mecool M8S Pro Stock & Nano Nexus ROMs (Android 7.1)

[Koowluh]

[*]Added support for all HID devices (e.g. remotes, gamepads, etc.) on latest Nougat firmware for Nexus Player, NVIDIA Shield TV & Xiamoi Mi Box

Hmm, I had hoped my Logitech Rumblepad 2 would work on this box now, but alas... On the Amlogic build of LibreElec the device seems to work, but any Android builds do not detect it. I'm quite new at this stuff so I was wondering if there was anything I could do to make it go. Suggestions are welcome!

[zenix]

I use latest magendaz nexus stock rom and the cursor of the airmouse is too small on my 43" 4k tv. Can i make it bigger?

[ClarkKent]

Build prop: DPI settings. Three digit number, approximately around 210.
edit and raise by twenty points. See how that looks to you.

I recommend you use one of these standard Android density values, as they're going to have better test coverage and performance optimizations: https://developer.android.com/refere...ayMetrics.html

[zenix]

Build prop: DPI settings. Three digit number, approximately around 210.
edit and raise by twenty points. See how that looks to you.

Thank you all. These dpi settings are for cursor only or will affect the whole system?

[teters01]

I use latest magendaz nexus stock rom and the cursor of the airmouse is too small on my 43" 4k tv. Can i make it bigger?

turn on disable h/w overlay. Your cursor will be bigger.

[zenix]

turn on disable h/w overlay. Your cursor will be bigger.

I did but then only audio in youtube and mx player, so i disabled again

[zenix]

Build prop: DPI settings. Three digit number, approximately around 210.
edit and raise by twenty points. See how that looks to you.

Cant find any line "dpi" in build.prop

Look for "ro.sf.lcd_density".

[ClarkKent]

Cant find any line "dpi" in build.prop

Last entry under build data.using b.prop Editor by j. Rummy Apks. Be sure to read link MAG listed for correct settings.

[zenix]

By mistake i must have deleted build.prop and box stucked in rebooting circles. Is there any way to fix it?

Flash the burn package using USB Burning Tool. (The updater won't work, since it will try to check environment using the current build.prop.)

[zenix]

Ok, i flashed again. All ok. Thank you
do you recomend any value in " ro.sf.lcd_density", cause i changed the value from 213 to 253 and still the cusrsor is small

Try enabling More Settings->Accessibility->Large Mouse Pointer

[zenix]

Thank you

[DrBlue]

Greetings all,

I have been attempting to install the file 'update_M8S_PRO-V0619_Stock-20171005' onto my M8S Pro using the Updater on the system (and installing from a USB stick). When I attempt to do so I get an error which reads something along the lines of 'This update is intended only for the M8S Pro'.

The machine I have is based around the Amlogic q20x board (according to DRM Info) and (supposedly) contains the Amlogic S912 rather than the S905 which rules out it being an M8S Pro +. Also the casing does not display an L which would indicate that it is the newer L model. However, widevine/security level in DRM Info is L1. I have read that some M8S Pro's have L1 rather than L3.

I'm curious as to why the update finds that this machine is not a Pro, could it be an L in a different case and could this be why the install did not work?

Any assistance would be greatly appreciated.

Edit: Attempted to install the earlier 'M8S_PRO-ota-20170707.094011.V0321-fixed' which appears to install fine but then hangs partway through a fancy Mecool intro sequence. It then reboots and reinstalls the original Mecool firmware.

Ah, crap! I just updated the script to identify by device name instead of reference board, and it seems there are two varieties of device name out there for the M8S Pro: "M8SPRO" and "M8S_PRO". I'll need to update this again. <sigh!>

[DrBlue]

No worries The upside is that while neither installed correctly (for me) they did root the device so I was able to install a semi decent launcher which should do for the time being.

Many thanks.

Okay, if you refresh your download now, the updater should work.

[Mindaugas]

Greetings,

Does anyone know, if there is alternative Shiningworth firmware for M8SPRO available? Maybe it would be more stable, than VS firmwares..

If I recall, you can actually install my latest Nexus GT1 custom ROMs on the M8S Pro, and they're based on the Shiningworth all-in-one ROM. I think you'll find that it has some issues of its own, though, particularly with regard to wireless performance and Bluetooth audio.

[Mindaugas]

Thanks, Magendanz, i will try it.