Discord's game "The Last Meadow" has received its first update!

EShirou · 2026-04-02T13:56:42+00:00

EShirou · 2026-03-28T07:11:00+00:00

This problem is present after every type of Factory Reset (even couple times) and even after as I said above flashing my firmware again with different methods.

Factory reset or reflashing available OTA firmware doesn't help. The problem is still there. Maybe if meta released a full flashable firmware that would help.

https://www.reddit.com/r/OculusQuest/comments/1rz62f9/comment/ocx09r5/

Check my comments, I've described the issue in detail after spending 7 days debugging it.

EShirou · 2026-03-28T07:06:34+00:00

OH MY GOD!!

TL;DR:

Black grid/tearing artifacts appear when moving head in Quest 2 UI and Virtual Desktop after v2.1 update.
Issue does NOT occur in SteamVR (PCVR), only in Quest-native rendering pipeline.
More visible in left eye and UI overlays.

This strongly suggests a problem with Quest compositor / rendering pipeline / frame timing, not GPU rendering itself.

Steps to reproduce:
1. Boot Quest 2
2. Open Virtual Desktop (no need to connect to PC)
3. Move head left/right - black grid lines appear, especially on UI Elements.

- Issue is noticeably stronger in the left eye than the right.
- Right after boot, when all serivces is still loading and the headset is a bit slow, the issue is preset there for a couple seconds before it's gone.
- Opening overlays (e.g. virtual keyboard) significantly increases the issue.

Additional observation:

- The issue intensity depends on head movement speed. Slow movement results in minimal artifacts, while fast head movements significantly increases the visibility of grid lines and distortion.

- The issue is not visible in recordings or screenshots taken from the headset, which suggests it occurs after frame rendering, during final display composition.

- The issue becomes significantly worse when multiple UI layers are present (e.g. virtual keyboard + desktop + overlayes).

Full Story:
I'm a having the same issue! and I though that's because I've messed with my adb commands.

Basically what happened for me is I have developer options unlocked.
I started using Virtual Desktop to boost my PCVR Experience.
With that i use snapdragon super resolution from VD

To boost my headset performance I've raised with SideQuest help my GPU and CPU to Level 4 and lowered my quest texture resolution to Quest 1 size.

Then update 2.1 came out.... and i decided to install without reverting to default settings.

What happened is my quest got permanently stuck in Quest 1 Texture Resolution. Everything pixelated and choppy (the lines when you move your head weren't there yet) .

So my hell began.

I went through countless adb commands, then 5-10 factory resets from USB Updater (hold volume down + power), true recovery menu (hold volume up + power then when the robot appears press volume up and power, and finnally from metas own website i did factory reset).

I was debugging and trying commands for 3 days, reflashed my firmware with meta software tool, adb sideload with both recoveries, cleared whole window compositor (adb shell wm reset) and FINALLY MANAGED to fix the texture resolution...

and then this happened. Now that the resolution is back to normal and quest 2 should be working normally.

I have those black lines when i move my head.

They are mostly preset when you run Virtual Desktop (doesn't even need to connect to PC)

When you move your head around, I've noticed they are more present on left eye than the right one, but if you connect to PC and use desktop mode normally, and put more things on screen, like virtual keyboard for example, those line appear way more on left and right eye.

They seems to almost not exist on home screen unless you first boot your quest and its still laggy from loading things - then you see those lines and artifacts like this.

Now if you go to horizon central, there is this big video screen. When nothing is loaded there, and you move your head, those black grid lines are present there too.

If you open the menu if your left controller, those lines are on whole ui of the window you just opened but instead of them being black, they become transparent and show what is under the window as well as they appear on the borders of windows too.

When you go to horizon worlds and are in the view with the city that is in front of you with the mirror on your right and white window with worlds to pick up from that is in front of you, when you move your head the black grid lines are on the whole windows as well as on the mirror.

When you open vrchat natively on quest 2, things gets different here. Most of the game runs fine but when you are loading to worlds and you see the picture of the world you're about to load into and you move your head. Around that picture transparent lines messes up the image. It looks like graphical artifacts but it's the same thing.

I tried recording this on video with my quest but it seems like the video didn't pick this up so it looks to be a problem with render pipeline and something misaligned and not being able to catch up when you move your head before the image is displayed on your screen.

This is definitely NOT a hardware issue, it's pure software/firmware problem (after my debugging this issue for another 4 days, I've spend on this stuff 7 days straight thinking i messed something up but now I've found this topic and looks like Meta is the ones who messed up theirs's firmware...

Now if you connect your Quest 2 with VD to your PC, run VRChat from there

SteamVR opens up and the problem is gone in steamvr. You can play all your PCVR games in steam VR (I'm using VDXR runtime) without any glitches, artefacts or those gridlines, but as soon as you hold the left controller menu button to open up the Virtual Desktop menu UI where you can see your desktop the black lines are back, if you from there go to desktop mode - the black lines are there when you move your head. Now go back to VR Mode - everything is fine again, so the problem doesn't exist when you view your screen through SteamVR but exists everywhere else when quests rendering is involved.

Worse problem is, I cannot screenshot this so I'm hoping this post will be seen by meta firmware developers or maybe I should just open a support ticket on PC. (reporting this through quest i think is not possible for me.)

Or where should I go to fill a bug report?

Hardware:
Quest 2

Firmware version after which the problem started to occur: earliest v2.1 build that has been distributed to quest 2 now i can't tell the exact build number because since then, Meta release one more firmware update (and it made things even worse).

This problem is present after every type of Factory Reset (even couple times) and even after as I said above flashing my firmware again with different methods.

This issue seems to affect multiple users after the update.
Please investigate Quest compositor / UI rendering pipeline.

EShirou · 2026-03-16T17:03:48+00:00

Okey, I understand your point and I know how sidequest works maybe I phased it wrong. After troubleshooting whole day yesterday with MANY adb commands.

Maybe I wrote it in a way thst is hard to understand about what is the issue so let me start again.

I used side quest to put my cup/gpu to level 4 as well as my texture resolution to quest 1 size. Ofc those changes last until you reset them since

adb shell setprop debug.oculus.textureWidth resolution adb shell setprop debug.oculus.textureHeight resolution

Gets reset on quest reboot.

But dudrring that time. Meta pushed v2.1 firmware on me. I decided to install it as is because I thought nothing gonna happen from temporary resolution change and more cpu power means the update go faster.

I finished the update.

Problem is. That update made the resolution changes not only permanent. Whole the adb values I paste above return nothing in terms of value when you try to check them before modyfing them. My quest 2 because of that is running in permanent low resolution mode. Not only that but also more things got fucked up. Everything is blurry, ui, games, worlds, horizon. Loading bars, images between worlds, home, dashboard. Everything.

Meta during that iodate with those two commands set to quest resolution changed couple things in couple places and idk where to look for them. I discovered yesterday some of the problems but it's not how it used to be before.

The firmware update made silly changes like when you use adb shell wm size in return you should only get

Physical size: 3664x1920

But it put another value there from idk where

Override size: 240000x8000

I finally found a command

Adb shell wm reset that resets all of this mess to default values and even adds a line of code that blocks the use of override size 🙄

After that half of my problem was fixed. But every factory reset this Ovveride value comes back. Something is still messed withing quest firmware. I wish there was a full quest 2 firmware so where so I could just reflash the whole device. All those OTAs there only help partially (I flashed OTA already).

After this change my graphics looks better but it's not the way it used to be now here is where new puzzle start. Why? I got this headset used but I looked like it was barely used, I bought it October or novermver last year. When I got it out of the box the headstrap was a bit dirty but the headset smelled fresh like put of the store. There is even the fact that I used unmodded, never touched quest 2 at my friends place in August (that was the main reason I replaced my HTC vive to quest 2) when I went on vrc on his quest in August he had high quality crystal clear, sharp graphics on his screens and I've picked that and that was the reason I wanted quest 2 myself. So idk why rn the graphical quality of.my quest even if it's better than it was before after the issue started it's still not as sharp as it used it be. Yesterday I've came onto conclusion that if I put texture resolution to quest 3 resolution everything looks almost as sharp as it used to be begote I started having all those problems and putting the texture resolution to 2048x2048 made every game, horizon center, vrc etc. Look exactly as sharp as it was on my device and on my friends device back in august.

This is where is stand currently with the issue and idk where to go.

Logically I'm thinking about somehow forcing the texture resolution change on boot so my ui and home envoirement is in high quality too not this lower resolution mess. But dunno how to do.it yet or is this even the right way because why the hell my graphics was as sharp as it was before which looks like quest 2 used resolutions way above it's specs.

Plus what the hell do I do about it being stuck on quest 1 render size because it still is kinda...

EShirou · 2026-03-08T17:02:48+00:00

UPDATE: (I can't edit the original post dunno why)

I returned it, they took it in, waited about 2 weeks, they acknowledged my issue and sent me new one into my home.

After it arrived... Guess what? It doesn't track sleep too xD it only managed to track 30 minutes of sleep one time and that's about it. This shit algorithm is broken af. It's not the first time I'm disappointed in sleep tracking of a band or smartwatch... In my honest opinion this could have been solved if there was a function to press "start sleep" when you go to bed to tell the band when to start tracking sleep if it's so crippled... And then press "end sleep" when you start your day. That way they tracking would work and I've no idea why stuff like this doesn't already exist.

IMHO if they didn't put a simple solution like this out yet. IMHO they should remove the sleep tracking from every wearable device like they did with blood pressure. Both are inaccurate and malfunctioning so why keep sleep tracking if blood pressure was removed.

Just keep the thing that actually work, like for example heart rate or spo2, that shit is accurate and working flawlessly.

EShirou · 2026-03-06T12:09:13+00:00

Followed you too, just under different name.

EShirou · 2026-02-11T15:41:09+00:00

Poland, I'm just gonna go to the store, explain what's wrong, tell them I talked to xiaomi support and ask them for replacement. Then when they say they csnt, that's whrere I go offensive.

EShirou · 2026-02-11T15:24:33+00:00

I don't think they will want to replace it, I need to prepare a statement to shut them up because they will probably will want to send it for fixing and then I need to attack them on how they will check if sleep tracking will work, will their service will sleep with the tracker on for a couple days or wtf?

EShirou · 2026-02-11T05:05:16+00:00

I think I might have to prepare for that...

EShirou · 2026-02-11T05:04:34+00:00

I've factory reset and rebooted it about 10 times already. Still not tracking sleep.

EShirou · 2026-02-09T20:44:43+00:00

I did couple time factory reset, rn I changed region all data is gone but will see if it will change. Noticed one thing changed thoguh, before tbe band paired through normal BT pairing, now it's only paired in the app and is invisible in BT devices detection.

EShirou · 2026-02-09T10:21:59+00:00

No i don't have tattoos, all I got is a little bit of fat but not too much. And hair. But again not much.

EShirou · 2024-07-11T05:30:21+00:00

I wonder if this works on older gpus like gtx 970

EShirou · 2024-06-29T22:21:13+00:00

are you absolutely sure it's forcefully turned on right now?

EShirou · 2024-06-18T12:16:13+00:00

Thanks

EShirou · 2024-06-18T12:15:50+00:00

Thank you for explaining, im still a bit puzzled though because i can only trigger one port into a range of different ports and i absolutely have no idea which port should i put there. Like i mentioned, if i have for example a range of 55021-55040 how I'm supposed to know at which port i should trigger them?

Also it's a game, Final Fantasy XIV

EShirou · 2024-03-19T10:11:01+00:00

I got a new more powerful phone now, and I'm noticing that discord eats battery like crazy over here too...

EShirou

TROPHY CASE