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

Well, the user interface is running in FHD (1900 x 1080), and on UHD (4K) the TV hardware is scaling. However, for video playback some apps can take advantage of codecs that drive higher resolutions. Those may hit bandwidth limitations from the video server or HDMI cable/controllers, though.

[zenix]

@Magendaz.
I use your nano rom and i have a 4k tv.
The settings are configured for the best screen resolution and this is 4k/60hz. It is also confirmed by the lg tv. But when i use some apps like antutu, kodi and many others apps like them, they say there is a fhd resolution. I wonder what is the true. For an example the main screen is 4k or fhd? If the above apps say the true then why the mecool does not change the resolution to 4k as it is asked by me?
Thank you.

Whatever it shows in About->Build is the OEM firmware build date, which the foundation upon which the Nexus custom ROM is built. The date in the filename of my ROM releases are the release dates, which are by necessity at least a few days following the OEM build. Sometimes I refresh in between OEM releases, in which case the build date won't change, but my release date will. In the release notes, I'll indicated what OEM firmware has been used for the foundation and provide a link to it, should you want to revert back to stock OEM firmware.

For ROM flashing, I use Windows 10 and USB Burning Tool. Unfortunately, that tool doesn't exist for Ubuntu or Mac, so you're forced to use OTA updates if you don't have a Windows box. In theory, you could use Burn Card Maker to flash burn packages, but I've found that very temperamental and it won't help you recover in Mask ROM mode if you corrupt the bootloader.

Yes, you could use a mini PC like the X5 or Z83 to flash these burn packages, and they're pretty cheap. If you're going to use it for anything else, though, I'd considering bumping up to the Apollo Lake boxes (e.g. AP42, AP34) which generally have at least 64GB eMMC that's about 3x the speed of the Cherry Trail storage. I started with the Z83 and Z83 II and have phased them all out for the AP42 and AP34 now, giving the old boxes away or making them headless servers running Ubuntu.

[ClarkKent]

Clarifying for me pls...
11/09 shows as my build... Even though I've updated to most recent 11/16.
Build date doesn't change with updates, 0nly when rom is...? What, fully rebuilt?

For Burn flashing, is a laptop with Win10 the minimum HW?
I've had great pita trying to get Dell tab 8.1 to work. Never happened.
Is the alfawise x5 (win10), or z83 Ubuntu platform a viable / desirable option to use for Android atv/ nexus ROM operations?

Well, parts of the firmware are open source, such as the AOSP bits, but not the bootloader, kernel or framework. That constrains us greatly.

Fortunately, the Khadas folks have been posting VIM source here: http://docs.khadas.com/develop/Downl...oidSourceCode/

That won't give us the ODM and OEM customizations, but it's a good snapshot of the Amlogic SDK 7.1.

[ClarkKent]

Your funny too, an excellent attribute @ the statehouse, I'm sure.
I just meant it is a simple substitute fix in phone ui. Nothing available here though? Correct me... Its closed source code, and cannot be tweaked, or features deleted. I'm cross-eye searched out.
Yes, schematics identification is what I wanted. I bruised my q201 board when the hood was open. Looking for a opinion if repairable, or fatality. Oops, grrr!

Sorry, I'm afraid I'm not aware of most of the phone hacks. As for hardware pro, I'm at a loss there too. I have an electrical engineering degree, but have squandered it on software development since leaving the Navy. It's been awhile since I got my hands dirty working with PCBs and solder.

[ClarkKent]

Guest who is the hardware pro around these parts? What a component is and does?
Side note: Goog's search bar recently expanded to cover entire top of screen l to r (1x5 format), which is new to me!?
Any hack to replace with microphone widget, as in phone u.i. It's obtuse, and useless

[Lolos21]

OK. Thank you for the answer my friend. I just asked because I want to flash these roms in the future.

I wasn't aware that Ethernet ever stopped working on these M8S Pro custom ROMs. The only scenario that caused that was if you installed one based on the Shiningworth All-in-One ROM, which is currently only released for the Beelink GT1, Alfawise S92, Vorke Z6 and Tanix TX92. These are based on VideoStrong's OEM firmware, and have had the correct values set in the device tree for this Ethernet hardware.

[Lolos21]

Thank you for the answer. Is it working with stock nexus rom also?

[zenix]

Hello, is the ethernet working with these roms?

It is working with nano rom!

[Lolos21]

Hello, is the ethernet working with these roms?

[rreiner3]

Yes, I have that turned on -- it has no effect, the box still goes to sleep after 10-15 minutes.

Well, the underlying bug on wake from sleep is going to have to be fixed by VideoStrong. As for preventing sleep, I set the Stay On While Plugged In setting by default, which seems to do the trick for me on the TVStock variant, which is what I use in my living room. I hadn't realized it wasn't working on the non-ATV variants.

Could you confirm by enabling Developer Options (click 7 times on Settings->About->Build) and checking the "Stay Awake" setting there?