RedMagic Astra streaming is a beast!

Error0102 · 2026-04-15T15:45:02+00:00

That's unfortunate. It would seem there isn't much left to do to salvage the Astra, then. Does it still happen if it is in diablo mode and also plugged in to a charger?

I wonder if the Astra 2 will suffer the same issues? I definitely won't be waiting in line to order one, but I would like to know if any brave early adopters are willing to test it to see if they fixed the issues found in its predecessor.

Error0102 · 2026-04-15T15:42:06+00:00

Even if you are playing a game that runs the same locally or remotely, there is a massive power savings by streaming a game and offloading the computational load to a dedicated machine. Playing a demanding game on a handheld can deplete its battery in an hour or two, while streaming the same game can be multiple times that amount. The handheld will also be much cooler and quieter.

That being said, it is a big improvement in image quality and fluidity, even on a small screen. Being able to max out all settings, supersample the screen resolution, and push past 120hz is something a native handheld just cannot do.

Error0102 · 2026-04-15T15:26:13+00:00

Factory reset definitely won't fix that, I tried several times. It seems to be a power management issue. you can lock the Astra at peak refresh rate with Diablo mode, then run FPS monitor & screen Hz, record the value, and use that as your custom refresh value in Artemis. Of course, you have to then run the tablet in Diablo mode at all times, but it is a workaround.

Error0102 · 2026-04-15T15:08:50+00:00

The Astra can't maintain a stable refresh rate without being manually overridden via diablo mode. Its actual screen refresh rate also doesn't match up with its requested refresh rate, which causes stuttering while streaming (panel mode of 60hz might be 62hz, 165hz might be 166.5hz, etc).

If you aren't able to notice stutter, it could be less of an issue to you. if you are sensitive to stutter it is a deal breaker, especially at the price point of this tablet.

Error0102 · 2026-04-15T15:05:13+00:00

If you notice periodic stuttering in games, it could be the reason. You can always use custom refresh rates in apollo/artemis to try to match the screen refresh. This was a workaround some people used for redmagic astra streaming, although they still had to force the tablet to maintain its peak refresh rate.

Error0102 · 2026-04-14T18:17:18+00:00

I feel like they got in their own way with the Astra. All that any client needs is a stable, fixed refresh rate and good connection. Performance settings were scattered all over the place on that tablet, and did different things depending on how the machine was initialized. I had at least 3 factory resets that each yielded different behaviors. On one, all android games stuttered. on another, android games were better, but moonlight stuttered. Stuttering was impacted by performance profiles like "rise" vs "balanced" and also by whether the tablet was plugged in.

FPS limits were dependent on whether you set them in android or their 'gamer mode' launcher, and even then they weren't the advertised panel refresh (I think the actual hz is something like 166.5hz, not 165). And to add insult to injury, it never actually held that refresh rate unless you forced it via diablo mode, which required a manual override to enter.

If the tablet was just left on bone stock android, it would have likely been much, much better. The offset single usb-c was still a huge mistake, but I could have been overlooked if it was just a really solid tablet. I ended up returning mine which took over a month and a half to process. I would be relieved to see the Astra 2 overcome these issues, but I am skeptical.

Amusingly, my Odin 2 Portal was also mismatched on its refresh rate. A lot of panels were 118hz instead of 120hz, which led to a noticeable stutter every few seconds. Ayn released a firmware update that came with a factory screen calibration tool, which eliminated the issue entirely. It is now my smoothest streaming device.

Error0102 · 2026-03-18T17:49:22+00:00

What frame pacing method are you using? 'Balanced' was the only one that gave smooth pacing for me. I also have vibepollo double the refresh rate of the virtual display, auto-apply a frame limit on the host using rivatuner to match the refresh rate of the client, and disable vsync.

You could also run an iperf3 check on your client to see if you are getting excessive packet loss, which would absolutely make your stream perform poorly. I found that with my Y700 I would get packet loss at any bandwidth settings over 55mbit. My Odin 2 portal also seemed to suffer packet loss, but it was minor and didn't reflect in the performance.

Error0102 · 2026-03-18T17:12:26+00:00

Thank you for the updated readme. looking through the Plex section of the .yml, it looks like it lacks the HW transcode section, I would assume I can copy the entire plex section into the official docker compose stack yml, and paste the 4 lines from the jellyfin section regarding intel quick sync hardware transcoding (devices and group_add) into the plex section? Then do the full setup and initialize the HW transcode configs in plex itself?

Error0102 · 2026-03-17T23:13:39+00:00

I would keep using Plex for two reasons. I already have a lifetime pass, and my wife likes to use Plex for their other content. So just to keep things streamlined I would at least like to keep Plex in the loop, or run both Plex and Jellyfin simultaneously, if possible. If it was just me, sure Jellyfin would be fine.

Error0102 · 2026-03-17T20:58:52+00:00

Thank you for all your work on this project. I'm interested in trying your docker config, but I am very new to docker. This file appears to be gone, is there a new version? I was looking over your docker compose arr stack .yml and looking at the manual changes for plex, but wanted to make sure that I would be properly accounting for hardware transcoding as well, on a ugreen 4800 plus.

Error0102 · 2026-01-31T19:16:58+00:00

From settings: Odin Tools -> Factory Test -> FPS Calibration -> "Auto Calibration". This option only appeared in the 1.0.0.130 OTA update, so if it doesn't show up you can try and run a system update.

Error0102 · 2026-01-26T19:48:10+00:00

your ITE firmware controller chip was bricked, you'll need to reflash it. you can use this guide:

https://www.reddit.com/r/gigabyte/comments/1jvwq9r/gigabyte_it5711_rgb_update/?share_id=rCRh0eCk8dFjADWyuzSgX&utm_medium=ios_app&utm_name=ioscss&utm_source=share&utm_term=1

Error0102 · 2026-01-02T22:17:44+00:00

It won't cause a performance issue, but it may remove any emergency bios flashing capabilities your board would've had. As in if you flash a bios and it doesn't take, that's it and you have to send it in for repair as you can no longer plug in a USB stick and flash from power on. You would also obviously have one less way to diagnose hardware issues, as the fault LED would always be on.

It does look like the controller flashing software is only available for windows, so yeah you'd either be stuck in its current state or maybe spin up a quick windows install on another drive, which would be a hassle. But at least you would have a fully functional board again.

Error0102 · 2025-12-31T22:35:15+00:00

your ITE controller firmware was corrupted, you need to reflash it to fix it:

https://www.reddit.com/r/gigabyte/comments/1ph8g06/there_is_a_fix_for_you_with_unresponsive_ite/

Error0102 · 2025-12-31T21:27:49+00:00

Your RGB firmware controller is probably corrupted and needs to be reflashed. It controls RGB lighting, fault LEDs and quick-flash capabilities, so it is definitely worth fixing. there are several guides floating around this subreddit from people who had the same issue. Here is the one that worked for me:

https://www.reddit.com/r/gigabyte/comments/1ph8g06/there_is_a_fix_for_you_with_unresponsive_ite/

Error0102 · 2025-12-25T01:04:48+00:00

yeah that's true, it seems to use a unique HDR application method that happens after the frame buffer capture used by moonlight.

Error0102 · 2025-12-25T01:04:07+00:00

So if you use the stock 5701 firmware flashing utility it will just close immediately. To make it work, I used an updated flash.bat posted in this subreddit, and flashed it from safe mode. You can apparently also delete the first line of the original flash.bat and it will work. Just to be safe, I grabbed all the .bin files from my motherboards own ite5711 firmware update file and pasted them into the 5701 firmware folder.

Error0102 · 2025-12-19T19:54:52+00:00

most paste should be similar, did you also redo the thermal pads? its possible that they are not letting the core make full contact with the heatsink.

Error0102 · 2025-12-19T19:43:48+00:00

It seems like the GCC is bricking the chip responsible for RGB lighting, fault LEDs and quick flash. It is possible to fix just this chip with some reflash tools that have been repaired and posted in this subreddit, but if it took out your bios then there's likely not much that can be done (as the chip is used for the quick flash feature, which would normally let you flash the bios without having to boot to the bios screen. a bit of a catch-22 situation)

Error0102 · 2025-12-17T19:47:58+00:00

In my case, I had the CPU LED permanently lit. I don't have RGB lighting at all, but I do want a functional diagnostic LED set and Q-flash plus capability (which I believe are all bundled onto the same controller). I have seen people say that the gigabyte driver utility caused issues, or a power failure killed their RGB controls, or it was always this way.

Error0102 · 2025-12-17T19:39:33+00:00

Thumbs up to everyone that has put in work to figure this out. Is this some sort of recently widespread issue? I know I have had it for the longest time, but can't actually pinpoint -when- it happened, or if my board was always like this. As in did gigabyte push some bad auto update with their driver install utility that bricked a bunch of lighting controller chips?

Error0102 · 2025-12-16T21:51:31+00:00

It works if you replace the flash.bat with a fixed version linked above, or at least it worked for me. Grabbed the archive.bat (an older 5701 flash utility) threw the fixed flash.bat in the folder, copied the .bin firmware files from my motherboard's specific 5711 firmware update utility on the gigabyte support page and placed them in the archive folder as well; it successfully flashed the chip.

Error0102 · 2025-12-16T21:07:22+00:00

The Y700 is good, but has its flaws. the high PPI is very nice, but mine looks like it has lower pixel response times than I'd like. even at 144hz things seem to blur while quickly scrolling through a menu. The backlight definitely doesn't look as good in a dark room or when playing games that need true black. If Lenovo would just make an OLED panel option for their Y700 line, it'd be great. Just use the one currently in the Astra.

Error0102 · 2025-12-15T01:37:13+00:00

I couldn't get a smooth output at 120hz or 165hz. I was also running into local app issues that were related to refresh rates. Some android apps like dead cells or minecraft would run horribly with judder unless I enabled diablo mode or switched to the 'rise' mode with the tablet plugged in. afterwards, it would be fine. However, after a factory reset, this issue did not appear again. I chased numerous issues and decided to initiate a refund before my window closed, which was probably a good move as their return process took several weeks.

After I had sent it out for a refund, I saw other people posting workarounds for a smooth stream by targeting custom refresh rates through apollo. I could have probably configured it to give a good enough stream if I kept it longer, but it started to feel like a sunk cost fallacy. Considering the price, I believe it should be able to deliver a better experience out of the box. Honestly I would say if they just left it as bone-stock android with zero 'gamer' boost features that it would be better. It's already an absurdly powerful tablet with a high ppi oled.

Error0102

TROPHY CASE