[ROM] Beelink GT1 / Alfawise S92 Stock & Nano Nexus ROMs (Android 7.1)

The Qualcomm drivers have not been well maintained, and they still rely on the kernel compatibility layer (compat.ko).

[Vineet]

Yup, a good ROM finally in the making! Except for the age old wifi connectivity problem. I have seen this wifi problem on many android tv boxes with similar SoCs. My MX9 Pro also has this problem.

Any idea why exactly the wifi continuously disconnects on these boxes? I have been unable to figure out so far

Cool. Remember that you can change the behavior of the power button in Settings->Powerkey definition.

Ultimately, I'd like to get a proper fix for the BT audio stutter, but that will require updating the Shiningworth runtime check to use libbt-vendor-qcom.so for the LTM8830. Given that the check is probably occurring in a binary file, changing that without source could be very difficult.

[Vineet]

I'm so sorry, here's a quick update, bluetooth stutter issue resolved. Required a power recycle.Now, connecting and working well. Also, the issue with power off got fixed as well.

Only one major issue left...wifi connectivity. Rest all positive

Many thanks.

[Vineet]

So, there are 2 problems.

1. The power buttpn doesn't actually turn the box off, it reboots it.
2. After deleting and renaming to Libbt-vendor.so, Bluetooth doesn't connect with any of the bluetooth devices. It does pair, but never connects. Error: unable to communicate with xyz..device.

Hope this helps. Also, the wifi problem still persists.

Rgds

[Vineet]

I think I've got a workaround for the Bluetooth audio stutter on the Longsys LTM8830.

It seems the Shiningworth All-in-One firmware does a runtime check to determine the wireless chipset, then loads a Broadcom (libbt-vendor.so) or Qualcomm (libbt-vendor-qcom.so) Bluetooth vendor library depending on the results. Currently, it's getting the match wrong for the Longsys LTM8830, which is a Qualcomm QCA9377 clone.

To correct this on an affected device:

1. Reboot into TWRP Recovery and mount the System partition.
2. Open TWRP File Manager and delete /system/vendor/lib/libbt-vendor.so.
3. Rename libbt-vendor-qcom.so to libbt-vendor.so.
4. Reboot to System

You shouldn't need to wipe data or cache, and there are no new files needed. It should just load the Qualcomm vendor library from that point on and the audio stutter should be gone.

Hi Magendanz,

Many thanks for keeping the beelink hopes alive Just flashed this ROM (the latest changelog). All working well, most issues resolved but one.

Still not able to get a stable wifi connection. I have flashed almost all ROMs available out there, but none has provided stable wifi connection.

Bluetooth stutter observed, trying to fix as per your post above, will report back soon.

Please help get the wifi issue fixed. I've tried almost all techniques, removed/reset wpa config file, reconfigured my modem to wpa-tkip which appears to be a little more stable but at the cost of bandwidth. Assigned static IP, but everything in vain so far

This wifi issue is freaking me out. Help me if there is a fix out there.

I think I've got a workaround for the Bluetooth audio stutter on the Longsys LTM8830.

It seems the Shiningworth All-in-One firmware does a runtime check to determine the wireless chipset, then loads a Broadcom (libbt-vendor.so) or Qualcomm (libbt-vendor-qcom.so) Bluetooth vendor library depending on the results. Currently, it's getting the match wrong for the Longsys LTM8830, which is a Qualcomm QCA9377 clone.

To correct this on an affected device:

1. Reboot into TWRP Recovery and mount the System partition.
2. Open TWRP File Manager and delete /system/vendor/lib/libbt-vendor.so.
3. Rename libbt-vendor-qcom.so to libbt-vendor.so.
4. Reboot to System

You shouldn't need to wipe data or cache, and there are no new files needed. It should just load the Qualcomm vendor library from that point on and the audio stutter should be gone.

UPDATE: tillaz87 made a patch here that can be applied in Settings->About-System Update or TWRP recovery.

[shwabo]

Hello Magendanz,

could you please tell me how easy and\or complicated it would be to flash between ROMS? In other words, I would like to try the Stock Android TV variant, and if not suitable, then flash to stock android variant, and if that is not suitable, flash back to stock beelink FW. I have all the FW's and would be flashing via USB. Is this doable?

Anything special I would need to know or do to flash between?

Thanks for your help, and for everyone's efforts in providing these ROM's. I for one greatly appreciate it!!

[snakeb]

Hi just read this rom is working with the gt1 ultimate, but I will lose 1GB of ram, is that correct? All other functions working well? Any fix or plans to be able to use all 3gb ram?

[UserPepe]

OK Send me a fix .I have 9377 chip on GT1 s/n S912xx so it should work fine.

That's already documented as a known issue. I have a fix for LTM8830/QCA9377, but it breaks all Bluetooth on AP6255.

[UserPepe]

In this rom bluetooth does't work correctly - audio via bluetooth has hik

[Philbra]

Hi Magendanz,
Honestly, I did not took care to tick any other options then the standard ones in the RoM burner. I will take care the next time even if I would prefer to have only OTA and so prevent me from a new full reinstallation
I found a way to reboot remotly finally when both android VNC and Linux CHroot VNC are frozen:
as long as ssh of Linux deploy is working, I just typed unchroot then I was in the GT1 busybox and from there the command reboot works
nevertheless a good watchdog would be fine as I use a lot those boxes remotly

regards
philippe

Did you wipe user data when you installed the custom ROM? Some OEMs preinstall apps that run in the background, including bitcoin mining apps. Best to do a clean install the first time.

[Philbra]

Hi magendanz
I found the reason and the fix.
the application is more than 100 Mb. So it needs the download of the application and an OBB file
i downloaded manually this file and installed it manually in the /SDCARD and it works now ( even if it seems that the Bluetooth is quite deaf and needs real proximity to work )
it seems that the stock beelink Rom takes care alone to download and install the whole package while your ROM does not.
see solution in the following link https://apkplz.com/android-apps/parr...r-apk-download
definitively not a major issue but interesting ....
for your information, your last ROM is installed on my two GT1 ultimate ( I assume I lost 1 M RAM ) with a lot of application that run in the background + Linux Deploy in which again many applications run in the background including some under mono
a 2 To HDD is also linked on it and i must recognise it is far quicker than my Raspberry
the only issue is that I cannot rely on a proper stability over weeks and that very often, either it is crashed or the Linux part is still working but the VNC acces is broken for unknown reason.
it could be interesting to have some kind of watchdog that reboots the whole box when something is broken.
From the Linux part, it is not possible because it works in CHROOT and when the VNC is frozen, there is no remote way to restart.

good exercice ...
regards
philippe