[ROM] Beelink GT1 / Alfawise S92 TVStock Nexus ROM (Android TV 7.1)

[ZIOLele1980]

Well, yes...if you're glutton for punishment. In Nougat, the dtb's are in their own partition, and you'll need this tool to split and then rejoin them after extracting the partition from the .img file with Amlogic's Customization Tool. Once you have the individual dtb files, you'll need to convert those to dts, edit them in a text editor, and then repack them using the dtc command in Linux.

well the remote hasn't enough buttons to map all functions i need,.. plus i kinda feel like i wanna play a bit.... i've read in another thread that it's possible to use also rc scan codes is that true? if so, do you know how to switch mode ?

[mrdigit420]

well the remote hasn't enough buttons to map all functions i need,.. plus i kinda feel like i wanna play a bit.... i've read in another thread that it's possible to use also rc scan codes is that true? if so, do you know how to switch mode ?

You can used xposedaddition app that is usable with xposed framework. I have been using it for a while, this app supports external devices. I use with mx3 air mouse with custom shortcuts with keyboard and other buttons. It also supports ir remote

[Alex06]

I'm not as technically skilled as you are, to be honest, which means that I don't know how to do what you mentioned at the end. Is it fairly easy?

Hi, I have the same problem when I try to install Magisk 13.3 from zip in TWRP. It stop at this message:

************************
* Magisk v13.3 Installer
************************
- Mounting /system, /vendor, /cache, /data
- Device platform: arm
! Unable to detect boot image
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/Download/Magisk-v13.3.zip'
Updating partition details...
...done

I am debugging the installer. Open the script META-INF\com\google\android\update-binary
Line 82 and 83 you'll find this:

find_boot_image
[ -z $BOOTIMAGE ] && abort "! Unable to detect boot image"

If you comment the line 83
find_boot_image
#[ -z $BOOTIMAGE ] && abort "! Unable to detect boot image"[/CODE]

The installer will skip the ending condition, and script will continue but it don't solve the problem because some lines after (line 151):

ui_print "- Found Boot Image: $BOOTIMAGE"

But at your screen you'll see this message:
- Found Boot Image:

The variable $BOOTIMAGE show nothing! It mean it's not set...
If you check the util_functions.sh script you'll find this:

find_boot_image() {
  if [ -z "$BOOTIMAGE" ]; then
    for BLOCK in boot_a BOOT_A kern-a KERN-A android_boot ANDROID_BOOT kernel KERNEL boot BOOT lnx LNX; do
      BOOTIMAGE=`ls /dev/block/by-name/$BLOCK || ls /dev/block/platform/*/by-name/$BLOCK || ls /dev/block/platform/*/*/by-name/$BLOCK` 2>/dev/null
      [ ! -z $BOOTIMAGE ] && break
    done
  fi
  # Recovery fallback
  if [ -z "$BOOTIMAGE" ]; then
    for FSTAB in /etc/*fstab*; do
      BOOTIMAGE=`grep -E '\b/boot\b' $FSTAB | grep -v "#" | grep -oE '/dev/[a-zA-Z0-9_./-]*'`
      [ ! -z $BOOTIMAGE ] && break
    done
  fi
  [ -L "$BOOTIMAGE" ] && BOOTIMAGE=`readlink $BOOTIMAGE`
}

If the $BOOTIMAGE is empty, it mean this function don't work on the device. Magendanz, the bootimage file is somewhere isn't it? We must define the bootimage variable without using the function, like BOOTIMAGE=xxxxx
Can you tell me what is the name of this file?

Yeah, the problem is that some kernel command lines for Nougat are including "androidboot.slot_suffix=_a" which is confusing install scripts like OpenGApps and Magisk into detecting an A/B partition layout, which they're not using. I've notified VideoStrong of the problem, but need to let Netxeon know too.

To check the kernel command line on a box, just type "cat /proc/cmdline" in the terminal emulator.

Oh, and the boot partition on Amlogic devices is just //dev/block/boot.

[GNex5]

You can used xposedaddition app that is usable with xposed framework. I have been using it for a while, this app supports external devices. I use with mx3 air mouse with custom shortcuts with keyboard and other buttons. It also supports ir remote

Xposed Framework is not yet (officially) compatible with Android 7.x Nougat. Here are rovo89's comments on the unofficial Xposed port for Nougat that made news recently.

https://github.com/rovo89/Xposed/iss...ment-316085447

"As you already mentioned, your changes could only work for ROMs compiled from scratch with Xposed already active, so people should understand that this won't work (at least not reliably) on their stock or otherwise pre-compiled ROMs."

https://github.com/rovo89/Xposed/iss...ment-316623920

"Their code is abforce's port, with all the limitations I listed above. It doesn't make sense at all to publish flashable ZIPs with this, as the port is only intended for recompiling a ROM from scratch. And as I feared, there is not a single warning that this is an incomplete port that will often fail to fulfill the API contract. That's bad for developers and users, they should at least know it's incomplete so they can decide whether they want to support/use it. I would never dare to do something like that without a big fat warning. Actually, as I'm rather perfectionist, I wouldn't publish an incomplete version at all, reliablity is very important for me."

It's unlikely that Magendanz would release a custom ROM with Xposed Framework built in. Doing so would go against his statement in the first post.

"The goal is to keep true to Google's vision and use the bare minimum of OEM or third-party apps or add-ons, which can be added à la carte by the user as needed, just as I've done with the Stock and Nano variants."

[testphase]

Is auto frame switch works with kodi?

[mrdigit420]

Xposed Framework is not yet (officially) compatible with Android 7.x Nougat. Here are rovo89's comments on the unofficial Xposed port for Nougat that made news recently.

https://github.com/rovo89/Xposed/iss...ment-316085447

"As you already mentioned, your changes could only work for ROMs compiled from scratch with Xposed already active, so people should understand that this won't work (at least not reliably) on their stock or otherwise pre-compiled ROMs."

https://github.com/rovo89/Xposed/iss...ment-316623920

"Their code is abforce's port, with all the limitations I listed above. It doesn't make sense at all to publish flashable ZIPs with this, as the port is only intended for recompiling a ROM from scratch. And as I feared, there is not a single warning that this is an incomplete port that will often fail to fulfill the API contract. That's bad for developers and users, they should at least know it's incomplete so they can decide whether they want to support/use it. I would never dare to do something like that without a big fat warning. Actually, as I'm rather perfectionist, I wouldn't publish an incomplete version at all, reliablity is very important for me."

It's unlikely that Magendanz would release a custom ROM with Xposed Framework built in. Doing so would go against his statement in the first post.

"The goal is to keep true to Google's vision and use the bare minimum of OEM or third-party apps or add-ons, which can be added à la carte by the user as needed, just as I've done with the Stock and Nano variants."

It works fine for me, it might not work for you or anyone else.
Also if anyone interested in alternate or shortcut to Leanback launcher, check this https://github.com/itvlab/tvapprepo/releases

[ZIOLele1980]

well the remote hasn't enough buttons to map all functions i need,.. plus i kinda feel like i wanna play a bit.... i've read in another thread that it's possible to use also rc scan codes is that true? if so, do you know how to switch mode ?

ok... i've tried that... adding missing scancodes, i mean, and i'm definitely missing something. Because it doesn't work. so, have you some advice, or better, can you point me to the docs to read to understand where i'm doing it wrong? i really don't have a clue where to search.

Thanks,

Well, there appears to be no documentation on this other than what's in the Amlogic SDK 7.1, but unfortunately we don't have access to that. I did find this: http://www.cnx-software.com/2017/03/...st-quick-look/

[Appdata]

I have the rom, just waiting on the AMPAK flashable .zip for my odd-ball 6330. (I may install it soon anyway and hook it up to ethernet.)

[Guest]

I'm afraid that I've got some bad news to report on the Mouse Mode bug. I've spent the last 12 hours working on a fix, and I'm still at an impasse. In the old remote.conf files that were used in Marshmallow and earlier for mapping remote scan codes, you just set "fn_key_scancode" to the scan code for the Mouse Mode button and were done with it. And while the remote keymaps have moved to the device tree in Nougat, there's no documentation on where the equivalent of "fn_key_scancode" is now stored. Looking through the device tree, nothing obvious stands out.

Setting the keymap entry for the scan code so that it produces the same key code as the old remote has no effect, so it appears they're pulling the setting from somewhere else. It's not clear where, and so at this point I'm referring the problem to someone with more inside knowledge of the Amlogic SDK 7.1. We could be waiting a while.

[joelkolb]

Guest I'm curious about how you were able to package this ROM. Was a new Amlogic customization tool for Nougat finally released. I've search all over but I haven't been able to find anything.

The Amlogic Customization Tool can still pack Level 1 Nougat images fine. I just do all the actual image manipulation (make_ext4fs, simg2img, sdat2img, etc) in Ubuntu now.

[Alex06]

Hi, I have the same problem when I try to install Magisk 13.3 from zip in TWRP. It stop at this message:

************************
* Magisk v13.3 Installer
************************
- Mounting /system, /vendor, /cache, /data
- Device platform: arm
! Unable to detect boot image
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/Download/Magisk-v13.3.zip'
Updating partition details...
...done

I am debugging the installer. Open the script META-INF\com\google\android\update-binary
Line 82 and 83 you'll find this:

find_boot_image
[ -z $BOOTIMAGE ] && abort "! Unable to detect boot image"

If you comment the line 83
find_boot_image
#[ -z $BOOTIMAGE ] && abort "! Unable to detect boot image"[/CODE]

The installer will skip the ending condition, and script will continue but it don't solve the problem because some lines after (line 151):

ui_print "- Found Boot Image: $BOOTIMAGE"

But at your screen you'll see this message:
- Found Boot Image:

The variable $BOOTIMAGE show nothing! It mean it's not set...
If you check the util_functions.sh script you'll find this:

find_boot_image() {
if [ -z "$BOOTIMAGE" ]; then
for BLOCK in boot_a BOOT_A kern-a KERN-A android_boot ANDROID_BOOT kernel KERNEL boot BOOT lnx LNX; do
BOOTIMAGE=`ls /dev/block/by-name/$BLOCK || ls /dev/block/platform/*/by-name/$BLOCK || ls /dev/block/platform/*/*/by-name/$BLOCK` 2>/dev/null
[ ! -z $BOOTIMAGE ] && break
done
fi
# Recovery fallback
if [ -z "$BOOTIMAGE" ]; then
for FSTAB in /etc/*fstab*; do
BOOTIMAGE=`grep -E '\b/boot\b' $FSTAB | grep -v "#" | grep -oE '/dev/[a-zA-Z0-9_./-]*'`
[ ! -z $BOOTIMAGE ] && break
done
fi
[ -L "$BOOTIMAGE" ] && BOOTIMAGE=`readlink $BOOTIMAGE`
}

If the $BOOTIMAGE is empty, it mean this function don't work on the device. Magendanz, the bootimage file is somewhere isn't it? We must define the bootimage variable without using the function, like BOOTIMAGE=xxxxx
Can you tell me what is the name of this file?

For all those who want to install Magisk on this Android TV 7.1 ROMS you only have to modify the script "util_functions.sh" script at line 56
replace this:

      BOOTIMAGE=`ls /dev/block/by-name/$BLOCK || ls /dev/block/platform/*/by-name/$BLOCK || ls /dev/block/platform/*/*/by-name/$BLOCK` 2>/dev/null

by this:

      BOOTIMAGE=`ls /dev/block/$BLOCK || ls /dev/block/platform/*/by-name/$BLOCK || ls /dev/block/platform/*/*/by-name/$BLOCK` 2>/dev/null

As Magendanz said, the "/dev/block/boot" path is the good one for the $BOOTIMAGE variable, by default the path is /dev/block/by-name/$BLOCK while in real the "by-name" folder doesn't exist.

[Alex06]

I found an other bug, maybe known? With HDMI-CEC activated, at first boot or sleep exit the TV remote is not detected by the TV Box, you have to switch to TV then HDMI to make the TV remote operate again.

[smrtprjcts]

I found an other bug, maybe known? With HDMI-CEC activated, at first boot or sleep exit the TV remote is not detected by the TV Box, you have to switch to TV then HDMI to make the TV remote operate again.

Try this android app, maybe it can keep the cec alive.

[AFQuintans]

Hi Magendanz,
Can you confirm that rom is the same as Mini M8S Pro?
Since I tested on the Ultimate GT1 and it is ok to me, both on GT1 (QCA9377) and GT ultimate (QCA9377) and since the MIni MXIII 2 shares the same Rom with the Mini M8S on the S912 chip will it be the same?
Best Regards

Yes, the Beelink GT1, Alfawise S92 and Mini M8S Pro are all very similar hardware based on the Amlogic q201 reference board, but you might see some differences in wireless chipset. (They have identical device trees.)

[AFQuintans]

This rom Nexus Android TV 7.1 date smoothly on the M8S Pro 3GB RAM (wi-fi 9377). A friend is undecided among the M8S Pro and Ultimate, I only see difference in price practically ...
Best Regards