Home Artists Posts Import Register

Downloads

Content

I didn't expect to see so many people show interest in the WiFi 5GHz & BT upgrade... just an hour after releasing the last build brookystech got in touch with me concerning a seemingly bad WiFi module.

Turns out some of the OEM re-brands of RTL8821CU dongles boot up in the wrong mode... and as such I had to add usb_modeswitch support into the operating system.

Long story short, more WiFi / BT dongles work now!

I also noticed that a new Magisk update has landed, so this one is included now as well alongside the previously removed 2.2/1.8GHz OC profile (for those that want or need it).

(But please... only use it with the fan set to medium / high or auto!)

How to install: Unpack the attached files using 7zip and follow the included instructions found inside README.txt.

Things to note when updating from a previous build: If you previously had Google Apps installed, please make sure you re-install them after the update to avoid crashes!

For those needing the Google Play Store: Reboot into TWRP and install the latest OpenGapps ARM64 9.0 Pico bundle! (I suggest you finish the first-time setup with WiFi disabled... things move so much faster if you do!)

For those needing root: Magisk is included out of box and only needs to be activated on first boot. A WiFi connection is required for the initial Magisk activation.

Changelog

  • The 2.2+1.8GHz OC profile is back
  • Magisk was updated to the latest version
  • More WiFi / BT dongles work now (usb_modeswitch support was added)

Files

Comments

Anonymous

Hello, thanks for your work. Coming from Beta 8.0, possible to upgrade with TWRP? Thanks

Michael Snipes

What is usb mode switch support: i done ordered the adapter RTL8821CU, did i get wrong one

Anonymous

great work. though I find that fans keep spinning even in sleep mode is this intentional?

Anonymous

Once again sir, thanks for the good work. I am especially impressed by your detailed tuto on how to improve wifi and bring BT capability to the 552. Now, I myself have been very happy with your second 9.0 release which allowed maximum OC. I have never encountered any perf/fan issues while gaming so far and am certainly not willing to give some of this OC back. If I am not interested in upgrading the wifi (too involved for me at this point I am afraid), can I safely stay on my current build without missing anything of importance?

Anonymous

Thanks for your kind answer

Anonymous

Some of these devices boot up like a USB CD-ROM so Windows users can load the drivers from them. usb_modeswitch helps Linux eject them so the kernel will see the real device and load the correct modules.

blackseraph

It is. Some people reported that their devices slowly overheated while stored in cases or pockets and such. Because of this the fan keeps spinning in its lowest possible setting during sleep as well.

blackseraph

Exactly what Fewtarius said. It's just another measure to increase dongle compatibility. I'm sure the dongle you ordered will be just fine.

blackseraph

You can skip updates if you like but there really is no reason to in your case because the latest beta let's you pick the exact same overclock you already have.

Anonymous

Beta8 was done with maskrom... Beta10 with Twrp. Seems to have access to 2208+1800 OC

blackseraph

Let me correct myself then: If you're coming from a beta build that didn't include the RAM overclock yet and you decide to upgrade via TWRP your unit's RAM won't run at the best possible clock rate.

Anonymous

Hi! Thank you for work!!! I have a question, is there an option to put the system in deep sleep...? Because my rg552 went from 63% to 30% of battery in a few hours in sleep mode.

blackseraph

Settings -> Display -> Sleep let's you set a display auto sleep timeout. It's set to infinite by default. But what you mean is a RK3399 issue more than anything, that SoC is very power hungry.

Anonymous

can I update from beta 8 to this or do I need to update to beta 9 first?

blackseraph

You can go straight to the latest build, always. Older builds are kept around for archival purposes and to give people the option to take a step back in case a newer build introduces a bug.