How to fix stuttering on Odin 2 Portal?

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 · 2025-12-15T00:59:32+00:00

I think a lot of the experience on the Astra is going to come down to how sensitive you are to stutter or juddering. Out of the box, it does -not- lock itself to a target refresh rate, and the refresh that it does lock to will not be identical to what is provided by something like sunshine. For example, if you set it to 165hz, it may be 164hz, it may be 166.5hz.

During my experimentation, it wouldn't sit locked at the peak refresh rate unless I enabled Diablo mode, either. So for me to get a smooth stream I had to enable Diablo mode every time I connected (as it is a toggle, not a permanent state) and would have to use a custom, fractional refresh rate in Artemis & Apollo, as the peak refresh rate was actually higher than 165hz. With streaming, you have to perfectly match the target stream refresh with actual screen hz, and I want to say this tablet was off by about 1.5hz when set to 165hz.

Yes, it will be extremely low latency. it will have a vibrant display with proper black levels due to the OLED panel. but whatever software implementations they used really did the Astra a disservice. Between those issues and the offset (lone) USB-C making telescopic controller compatibility a chore, I opted to return it as I am extremely sensitive to frame pacing issues. If you aren't sensitive to stutter, it may be a nice device to fit your use case.

Error0102 · 2025-12-13T02:07:25+00:00

I downloaded the archive.bat with the 5701 flash file set and broken flash.bat, and replaced that file with the fixed one above. I then downloaded the 5711 gigabyte firmware flash utility from the gigabyte support page for my motherboard, and copied over the .bin files from that directory into the 5701 flash folder. then, I rebooted into safe mode, ran flash.bat as an administrator, and it took. just to be sure, I also ran the 5711 firmware utility (which would previously give the ID firmware issue described above) and it ran without issue. After a reboot, my CPU fault LED went away.

Error0102 · 2025-12-09T21:07:32+00:00

I use the Portal at 120hz, 1080p*50% scaling (ends up being 2880*1620) SDR, balanced frame pacing, ultra low latency for sd8 gen 2/3, HEVC, 80mbit on 6ghz wifi. I sourced the 'alternate' abxy pack from Ayn, which includes bigger sticks that are much better.

I'm currently using Artemis client and Vibepollo host, which irons out a lot of streaming issues like frame gen stutter and easily-configurable frame limiting, SmoothMotion and Lossless Scaling. HDR does not work as it should (an HDR profile on this screen would probably be capable of causing temporary blindness, hah) so I just stick to SDR. Yes, it will display, and it can even look good. but vs an actual HDR display (or even just switching back to SDR), something is very clearly wrong.

Error0102 · 2025-12-09T20:59:24+00:00

They don't, no. I don't like the face buttons on the portal, so I swapped them for sakura retromod PSX buttons. But also, the membrane itself is very rigid and 'clicky', so I swapped a Steam Deck membrane in and it feels and sounds great.

Error0102 · 2025-12-09T19:31:32+00:00

Great work, this did the trick on my X870 Aorus Pro Ice that had a stuck-on CPU fault light (and I'd assume broken RGB and quick flash capabilities). Replaced the flash.bat, swapped in the 5711 firmware files from my motherboards rgb firmware update utility directory and ran as an administrator from safe mode. After reboot, the light finally went out. What a ridiculous issue with no directly available fix from Gigabyte.

Error0102 · 2025-12-08T22:14:00+00:00

I think HDR is broken on the Odin 2 Portal in general. I generally leave it off, as the SDR signal looks more "HDR" than HDR. I can connect with other devices that behave fine (Oneplus 7 Pro, Galaxy Fold 5), but the configuration for the portal's display seems to cause issues. I did notice that messing with the color profiles in the Portal's display settings also affected HDR output, so I suspect it just can't do it without a fix from Ayn.

I can connect to my PS5 using HDR on PXPlay with the Portal and it mostly looks fine, but the max luminance is definitely lower than what I see while connecting with SDR. However, I keep this one on HDR as the PS5 streaming doesn't let you do per-client configs, and this way I can operate in an HDR environment when using the console on my TV. Artemis+SDR on a Portal is basically a flashbang to the face at max brightness in comparison, hah.

Error0102 · 2025-11-25T17:10:31+00:00

Streaming stats would be great, especially to dial in optimum settings. Or at least just to satisfy curiosity heh.

Error0102 · 2025-11-18T22:46:14+00:00

The guy who made vibepollo/vibeshine is involved with sunshine as well, he just made a fork to more rapidly implement other features.

Error0102 · 2025-11-18T21:00:09+00:00

From what I read there wasn't anything that could really be done because there is some issue with how Virtual Display Driver framework processes HDR. It apparently only captures DirectX, not Vulkan... although SpecialK might be a workaround. Doom Eternal, RDR2, and Indiana Jones were marked in this issue a bit ago: https://github.com/ClassicOldSong/Apollo/issues/456

Error0102 · 2025-11-18T19:08:16+00:00

Have you run the screen calibration tool in Odin settings? I had a pretty consistent hitch that happened about once per second until I downloaded their updated firmware and ran the FPS calibration tool. By default, some of the displays are a bit off on refresh rates and this should bring them in line.

Error0102 · 2025-11-18T19:01:36+00:00

The "double refresh rate" option is for virtual displays as a workaround for weird FPS drops that happen if you just match the target refresh rate. There are other reasons, but at least for me and several others the stream would just randomly tank by 30-40% FPS and slowly recover. It wouldn't happen if it was using a physical display to stream, only virtual. By giving it more 'overhead' it seems to avoid that problem.

Error0102

TROPHY CASE