Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

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

Collapse
This is a sticky topic.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • clementio
    replied
    Ok, so I will use the leanback keyboard.

    Thank you for all your work.

    For the brightness issue, I use the bootvideo tweak and all is ok.

    Leave a comment:


  • Guest
    Guest replied
    Originally posted by clementio View Post
    But since the 20170523 update on my Mini M8S II, the Gboard app crashes when I want to open the keyboard settings and I can't put the focus on the keyboard. The Leanback keyboard works fine. On the 20170422 version, the keyboard focus is OK. Any idea?
    Well, I can't reproduce the crash, but the Google keyboard (Gboard) just isn't as remote control friendly as the Leanback keyboard. The old 20170422 build didn't actually use the Google keyboard, but used a version of AOSP keyboard that Amlogic had hacked with DroidLogic to make work.

    I'm still trying to figure out if we can tweak the Gboard settings or remove some DroidLogic code to get it more remote control friendly. For now, I'd just use the Leanback keyboard.

    Leave a comment:


  • clementio
    replied
    Hello,

    First, very, very good job Magendanz!!!

    But since the 20170523 update on my Mini M8S II, the Gboard app crashes when I want to open the keyboard settings and I can't put the focus on the keyboard. The Leanback keyboard works fine.

    On the 20170422 version, the keyboard focus is OK.

    Any idea?

    Leave a comment:


  • Downunder 35m
    replied
    The BTUSB for sure for support of USB stick, the rest doesn't really ring a bell here, sorry.

    Leave a comment:


  • Guest
    Guest replied
    So, the ODROID-C2 has a bunch of driver modules that they've include in their Android 6.0.1 firmware and I'm thinking that I might borrow a few:
    • 8192cu.ko
    • 8812au.ko
    • btusb.ko
    • ch341.ko
    • cifs.ko
    • cp210x.ko
    • ftdi_sio.ko
    • md4.ko
    • nls_utf8.ko
    • pl2303.ko
    • pwm-ctrl.ko
    • pwm-meson.ko
    • spi-bitbang.ko
    • spi-gpio.ko
    • spidev.ko
    • w1-gpio.ko
    • w1_therm.ko
    • wire.ko
    Anything here grab you?

    Leave a comment:


  • Downunder 35m
    replied
    That is a good question that I tried to answer since I got my box
    In some roms is the "basic" BT support in terms of a few libraries and required settings section once a BT device is connected.
    But, so far I only found drivers in roms for boards with the dual Wifi/BT combo chip.
    Got 4 different BT dongles here, ll with different chipsets inside if I trust Windows but none gives any response at all when I plug it into the box.

    Was trying to do some more research on sticks with chipsets that are supported by several mobile phones/tablets but only found one - and that one is not available down here.
    Including postage from the US it would cost me more than what I paid for the box LOL
    If I would order 10+ of the little circuit boards used in the S912's for dual WiFi and BT than each one would cost less than 5 bucks, but without a decent reflow station I won't even attempt to change them.
    Also not 100% sure if Android would actually be able to check what type of BT dongle is plugged in unless already defined somewhere.
    It's not like Androd is famous for plug and play with automatic driver updates....
    Need more time to learn about the kernel stuff and how to properly modify one to my needs.

    Leave a comment:


  • Guest
    Guest replied
    Originally posted by Downunder 35m View Post
    USB BT sticks would be great to get working
    But don't all the p212 boards pretty much have Bluetooth support already?

    Leave a comment:


  • Downunder 35m
    replied
    USB BT sticks would be great to get working

    Leave a comment:


  • Guest
    Guest replied
    Sorry about the delay, but I ran into some issues with SELinux security contexts that were causing Ethernet to stop working. Took some time to track down the cause. Anyway, I want to extend a special thanks to tillaz87 for all the work he did diffing framework resources, and I think the result shows a level of UI polish that was missing before. (Now, if we can just figure out a way to allow screen casting from our phones and tablets, I'll consider this project pretty much complete.)

    Here's a quick summary of the changes. As always, please let me know right away if you spot any issues.

    Changelog (20170523):
    • New Nexus logo splash.
    • Added Leanback UI sounds.
    • Modified build.prop to spoof the Xiaomi Mi Box, which should circumvent some device checks.
    • Modified build.prop to enable 4K output in YouTube for Android TV.
    • Modified several UI settings (inc. animations & themes) in the framework to match those on the Xiaomi Mi Box and Nexus Player.
    • Added FrameworkPackageStubs.apk, which are present on Xiaomi Mi Box and Nexus Player.
    • Removed GlobalKeyInterceptor.apk, GamepadPairingService.apk and FuguPairingTutorial.apk, which are specific to Nexus Bluetooth remotes.
    • Added kernel modules (device drivers) for Sony PS3 and Dragonrise USB HID game controllers.
    • Updated for latest Open GApps build (20170523).
    • Updated to TWRP Recovery 3.1.1-0.
    • Resolved issues with Google Keyboard and Google Leanback Keyboard, and so both are now available to set as default IME.
    • Added SELinux security contexts during sparse file system creation.
    • Fixed keyboard focus issue on first screen of Setup Wizard (SetupWraith).

    One last request: I've now got a much better understanding of how to pre-load kernel modules so that drivers are present for any devices you might attach via USB. Other than game controllers, what devices of this type would you like to see supported?

    Leave a comment:


  • Guest
    Guest replied
    Originally posted by newkind View Post
    One question - my app drawer doesn't contain OTA Update package - should it be there or TWRP is the only way to install updates?
    Yeah, you don't want to install an OEM OTA update over a custom ROM, so I remove it. If we ever host our own OTA update server, I might put it back. Alternatively, I might install something that does local updates, but for now that's just TWRP.

    Leave a comment:


  • newkind
    replied
    I installed latest update package via TWRP and all went fine, Netflix (non AndroidTV) works great - thank you! One question - my app drawer doesn't contain OTA Update package - should it be there or TWRP is the only way to install updates?

    Leave a comment:


  • Guest
    Guest replied
    Originally posted by Cinquieme View Post
    I was talking about the MiniM8SII (V109) And if you have the full flash image instead of the update i would be delighted :-)
    Sorry, that was just a copy/paste error. Here's the URL that I intended.

    Leave a comment:


  • Cinquieme
    replied
    Originally posted by Magendanz View Post
    Here you go, Cinquieme. That was the last version to be based on the stock Mini M8S II firmware, but if you install the AP6255 wireless update, you'll be getting not only the drivers, but also the Mini M8S II kernel as well. This old codebase hasn't been maintained, and it won't get the major update that I'm about to post.
    Thank you Magendanz, sorry if i didin't make it clear.
    I was talking about the MiniM8SII (V109)
    And if you have the full flash image instead of the update i would be delighted (need testing on Nexboxes&Tanix modeels)

    For my other boxes, i'm eager to test your next update :-)

    Leave a comment:


  • keijun
    replied
    When I install Google Korean Keyboard from Play store and launching keyboard, it crashes itself.
    Any solution for this issue? I want to input Korean for searching youtube.
    Also, when I use 'Cast' function on my Android, I can not youtube cast or mira cast.

    Leave a comment:


  • Guest
    Guest replied
    Originally posted by Cinquieme View Post
    Hey i'd need the 109 firmware for MiniM8SII. Magendanz, it's not avaliable on your onedrive anymore. Can you give a link?
    Here you go, Cinquieme. That was the last version to be based on the stock Mini M8S II firmware, but if you install the AP6255 wireless update, you'll be getting not only the drivers, but also the Mini M8S II kernel as well. This old codebase hasn't been maintained, and it won't get the major update that I'm about to post.

    Leave a comment:

Working...
X