[ROM] Mecool M8S Pro L TVStock Nexus ROM (Android TV 7.1)

[Intrinsic]

Using keyboard shortcuts its possible to get near full chrome behaviour. CTRL+right click on any link will open it in a new tab. after highlighting text using classic keyboard short cuts for copy and paste works the same. You won't see anything saying you have copied the highlighted text but you have. It will be available for pasting when you want it. You can either long click to bring up the paste context option or CTRL+V.

Downloading the Gboard and using that to replace the leanback keyboard will allow you have an Enter button so at least you can confirm selections after typing and space out your paragrapghs. It can also be hidden when the physical keyboard is being used but it can't be used with a remote control. When it's hidden you again lose your Enter button though. Annoying.......

[Intrinsic]

Ok. Need some help.

I fixed the keyboard issue, well at least sort of.

Using Is file explorer I went into the system/user/keylayout folder. Opening the files I saw that under the generic.kl file key 28 (which should be enter in a physical keyboard) was set to centre click. Basically the OK button on the remote. This is why we don't have an "enter" button within Android TV. But looks and behold there another file called querty.kl, whose key 28 was listed as "eneter".

I swapped names of files. changed the generic.kl to generic.kl.temp and then changed the name of the querty.kl to generic.

And now the enter key works as it's supposed to be in text feilds. but that's it.... the remote control pretty much doesn't work any barring the direction and volume keys.

I'm at my limits here so I need someone with more knowledge about stuff like this to help out, but at least now I know it's all about key mapping.

I have set everything back and everything is working again (have to restart after every change). Now I understand that the device looks at the generic.kl file for it's inputs, and what should be the ENTER key is instead the "ok/centre d-pad" key. What I need help doing is finding some sort of key combination of say Ctrl+enter, alt+enter...etc and whatever it's designation is with a .kl file and maybe it's possible to change that selection to represent ENTER.

So anyone that can help it will be greatly appreciated.

[supermal]

Ok. Need some help.

I fixed the keyboard issue, well at least sort of.

Using Is file explorer I went into the system/user/keylayout folder. Opening the files I saw that under the generic.kl file key 28 (which should be enter in a physical keyboard) was set to centre click. Basically the OK button on the remote. This is why we don't have an "enter" button within Android TV. But looks and behold there another file called querty.kl, whose key 28 was listed as "eneter".

I swapped names of files. changed the generic.kl to generic.kl.temp and then changed the name of the querty.kl to generic.

And now the enter key works as it's supposed to be in text feilds. but that's it.... the remote control pretty much doesn't work any barring the direction and volume keys.

I'm at my limits here so I need someone with more knowledge about stuff like this to help out, but at least now I know it's all about key mapping.

I have set everything back and everything is working again (have to restart after every change). Now I understand that the device looks at the generic.kl file for it's inputs, and what should be the ENTER key is instead the "ok/centre d-pad" key. What I need help doing is finding some sort of key combination of say Ctrl+enter, alt+enter...etc and whatever it's designation is with a .kl file and maybe it's possible to change that selection to represent ENTER.

So anyone that can help it will be greatly appreciated.

https://play.google.com/store/apps/d...edefiner&hl=en this any help?

[Intrinsic]

https://play.google.com/store/apps/d...edefiner&hl=en this any help?

I have sorted it out... it ended up being a little more complicated than I thought it would be but it worked at the end of the day. Here is what I did.

First off the issue was that in the M8s pro L if using an external keyboard of any sort you will not have an ENTER button. This means that you can't use the option within the ROM or any app to hide the keyboard cause if you do you won't be able to confirm anything. You type something in a search box and cant hit "GO" cause its not on your screen and the enter key on your keyboard thinks its an "OK" key.

The problem is that the ROM doesn't have a .kl file to match your keyboard so its defaulting to its generic.kl file which supports most keyboards along with the devices custom keys on the remote control. That means you can't modify this "generic.kl" file because if you do your remote control won't work right.

The solution.

You have to create your own .kl file. And it has to have a vendor ID that matches the device you are trying to use. So I used an app called "Gamepad tester" which gave me the full device ID of my keyboard. was something like Vendor_045e_Product_800. Armed with that info, I went back to the system/user/keylayout folder and made a copy of the generic.kl that the ROM defaults to. Changed the name of the copy to my vendors name, went within the .kl file (all using ES file explorer) and changed the key 28 function from D_PAD_CENTRE (or something like that) to ENTER. Set root permissions on the file rw_r_r......

Reboot and then profit.

Problem solved. Now I can use my external keyboard and remote and have them both behave like they are and not have to have the onscreen keyboard pop up everytime you are trying to type.

Nw onto the next issue... the dpi thingy.

[supermal]

I have sorted it out... it ended up being a little more complicated than I thought it would be but it worked at the end of the day. Here is what I did.

First off the issue was that in the M8s pro L if using an external keyboard of any sort you will not have an ENTER button. This means that you can't use the option within the ROM or any app to hide the keyboard cause if you do you won't be able to confirm anything. You type something in a search box and cant hit "GO" cause its not on your screen and the enter key on your keyboard thinks its an "OK" key.

The problem is that the ROM doesn't have a .kl file to match your keyboard so its defaulting to its generic.kl file which supports most keyboards along with the devices custom keys on the remote control. That means you can't modify this "generic.kl" file because if you do your remote control won't work right.

The solution.

You have to create your own .kl file. And it has to have a vendor ID that matches the device you are trying to use. So I used an app called "Gamepad tester" which gave me the full device ID of my keyboard. was something like Vendor_045e_Product_800. Armed with that info, I went back to the system/user/keylayout folder and made a copy of the generic.kl that the ROM defaults to. Changed the name of the copy to my vendors name, went within the .kl file (all using ES file explorer) and changed the key 28 function from D_PAD_CENTRE (or something like that) to ENTER. Set root permissions on the file rw_r_r......

Reboot and then profit.

Problem solved. Now I can use my external keyboard and remote and have them both behave like they are and not have to have the onscreen keyboard pop up everytime you are trying to type.

Nw onto the next issue... the dpi thingy.

Well done!I use k400 keyboard with mouse pad.sometimes I have to swap to remote to enter something.this would resolve the issue.respect for your efforts!

[Intrinsic]

Well done!I use k400 keyboard with mouse pad.sometimes I have to swap to remote to enter something.this would resolve the issue.respect for your efforts!

Yup, this should have you sorted. Now only if I can sort the DPI issue. I fear that one is going to be a lot more complicated.

[Intrinsic]

Sorted the DPi issues too....

[DreamSeason]

Sorted the DPi issues too....

Wow. Can't wait to see your sharing.
I'm using the same Box with a FHD(1080P) TV. I did see the viewport reading of 1920*1080*2. I thought it was kind of strange at that time. Because 2 stands for scaling. I learned that from my MacBook Pro. But I can not find any related settings down in the box.

[natzen]

this rom work on alfawise h96 pro plus 3-32 green pcb?

[Intrinsic]

Wow. Can't wait to see your sharing.
I'm using the same Box with a FHD(1080P) TV. I did see the viewport reading of 1920*1080*2. I thought it was kind of strange at that time. Because 2 stands for scaling. I learned that from my MacBook Pro. But I can not find any related settings down in the box.

I think Mecool is playing a fast one. The box is capable of outputing at 4k, but I believe internally everything is rendered natively at 1080p then upscaled and sent out as a 4k signal. This would explain why 4k displays see it as a 4k input device.

I have my rez set at 2560x1440p now, up from the 1920x1080p that it was running at before. My TV still sees it as a 4k device and within the display settings in the stock ROM its still set to output 4k.

Setting the rez (via the app DPI switcher) to 4k (3840x2160) breaks the system UI. Things still run, some things stutter but the system UI behaves and looks weird. So 1440p is the best middle ground for this box so far. My DPI is set to 300 (down from the default 320) so this way I can get the tabbed view of chrome and generally see more stuff on my screen than before. You may want to increase the font size in settings though as things get smaller. But I am on a 55" 4kTV so with a smaller TV it may be better to have a higher DPI setting. The higher the DPI the bigger everything is on screen.

Doing all that would generally break the system UI with regards to the recents menu. Long press "Home" to pull up recenst would no longer work. To fix that I used an app called Button Mapper. And customized the home button within the app to do excatly what it was designed to do anyways. gave it a long press for recents function and now the recents menu still works regardless of whatever rez/DPI you set.

With all this things look even sharper than they did before because now the box is rendering at a higher internal rez. Previously it acted like some of those 1440p smartphones that would render at 1080p natively to save battery life.

Switched back to 1080p but dropped my DPI to like 240 or something. Found out that regardless of whatever rez you set the system UI and apps that render based on its settings are tied to 1080p. But apps that play videos and stuff can play their videos at 4k regardless of your UI running at 1080p.

[DreamSeason]

Switched back to 1080p but dropped my DPI to like 240 or something. Found out that regardless of whatever rez you set the system UI and apps that render based on its settings are tied to 1080p. But apps that play videos and stuff can play their videos at 4k regardless of your UI running at 1080p.

That's interesting. What's your stats for nerd in youtube after you made those changes? Any changes for view port readings? BTW, are you still using the youtube app out of the box? The youtube updates seem problematic for this device.

[Intrinsic]

That's interesting. What's your stats for nerd in youtube after you made those changes? Any changes for view port readings? BTW, are you still using the youtube app out of the box? The youtube updates seem problematic for this device.

So say you switch the rez to 2560x1440/3840x2160, the view port in stats for nerds changes accordingly. Switching back to 1080p the view port in stats for nerds shows up as 1920x1080*2. I reverted to the 1080p setting cause I figured out (and was also told) that android TV renders its system UI and all app elements render their UI at 1080p in android TV. Its like the GUI of everything is tied to a 1080p rez, but anything that has to do with video (codecs) can then play at 4k.

The youtube app out of the box gave me issues too like apparently everyone else. Its on 2.03.04 or something like that and can't play for 30 seonds without it freezing. So I installed another Youtube app from aptoid store (1.3.10 or something like that) its an official youtube app and disabled the stock app (since for some reason whenever I try and uninstall it my system reboots). Works perfectly and is even faster than the stock youtube app and has full support for android TV too. Only downside so far is that it doesn't seem to support 4k videos; not too big an issue for me since I stream my vids at 1080p max.

[Intrinsic]

Last issue I am having, this has to do with the fact that for some crazy reason android sees right click o a mouse or trackpad as a back button!! Wtf??

This is doubly bad since the long click to bring up context menu doesn't seem to work on android TV or at least with all the browsers I have tried. So if anyone has any ideas it would be appreciated. I dn't really care for the rightclick thing but it would be great to get the long click to enable context menu back.

You know? how you can long click on a link or image and a menu comes up asking to open in new tab....etc? Yeah that.

[DreamSeason]

So say you switch the rez to 2560x1440/3840x2160, the view port in stats for nerds changes accordingly. Switching back to 1080p the view port in stats for nerds shows up as 1920x1080*2. I reverted to the 1080p setting cause I figured out (and was also told) that android TV renders its system UI and all app elements render their UI at 1080p in android TV. Its like the GUI of everything is tied to a 1080p rez, but anything that has to do with video (codecs) can then play at 4k.

The youtube app out of the box gave me issues too like apparently everyone else. Its on 2.03.04 or something like that and can't play for 30 seonds without it freezing. So I installed another Youtube app from aptoid store (1.3.10 or something like that) its an official youtube app and disabled the stock app (since for some reason whenever I try and uninstall it my system reboots). Works perfectly and is even faster than the stock youtube app and has full support for android TV too. Only downside so far is that it doesn't seem to support 4k videos; not too big an issue for me since I stream my vids at 1080p max.

Yeah. Version 2.03.04 seems to be latest one which came out probably a week earlier. Quite surprised to see Mecool update it in the stock rom. What's the alternative that you're using? I'm using Smart YouTube myself. Only 1080p for your 4K TV. It's starving for more pixels.

Last issue I am having, this has to do with the fact that for some crazy reason android sees right click o a mouse or trackpad as a back button!! Wtf??

This is doubly bad since the long click to bring up context menu doesn't seem to work on android TV or at least with all the browsers I have tried. So if anyone has any ideas it would be appreciated. I dn't really care for the rightclick thing but it would be great to get the long click to enable context menu back.

You know? how you can long click on a link or image and a menu comes up asking to open in new tab....etc? Yeah that.

Yeah. Right button for back. That's how I use my mini keyboard mice combo. Other than that, there does not seems to be another option.

[Intrinsic]

Yeah. Version 2.03.04 seems to be latest one which came out probably a week earlier. Quite surprised to see Mecool update it in the stock rom. What's the alternative that you're using? I'm using Smart YouTube myself. Only 1080p for your 4K TV. It's starving for more pixels.



Yeah. Right button for back. That's how I use my mini keyboard mice combo. Other than that, there does not seems to be another option.

I use this version of youtube https://google-inc-youtube.en.aptoide.com . Its about 2yrs old from what aptoid says but it works perfectly. I tried Smart youtube also but didn't like it, too many starts and stops. Like while watching a video you can't be scrolling through other suggested videos.

Not having 4k sucks but what can I do lol. I will just wait until the stock youtube app gets updated, then try it again, hopefully its fixed.

The lack of a right click and/or long press to open context menu within browsers is annoying though.