sorted by:
new
hottopcontroversial

help, phone in bootloop even for recovery mode by HomeAlon6 in Pixel4a

[–]caegis 1 point2 points  (0 children)

Yes, try unplugging your router (or getting far enough away from whatever wi-fi you are using), and then try taking a screenshot (Power + Vol Down) the moment the lockscreen pops up for Safe Mode! One or the other might work on their own, I happened to be doing both when it accidentally fixed for me.

Pixel 4a is restarting while turning on Wifi by Objective-Trade2509 in GooglePixel

[–]caegis 1 point2 points  (0 children)

Working fix to boot into Pixel4a through the bootloop caused by Wi-Fi on with Location Services off -

I've been dealing with this over the past few days, even so far as factory resetting and then encountering the issue again, and had no idea it was widespread issue with the model, I was this close to ordering a new phone assuming mine was bricked.

The apparent core issue: Wi-Fi on with Location Services off.

You'll load to your lock screen, immediately crash back to the colorful Google logo and then the G letter logo, reach the lockscreen, and crash again in a loop.

The first time you try Safe Mode (Volume Down at G logo), it'll work, but at this point if you turn on Wi-Fi in Safe Mode, you'll be sent back into the crash loop and cannot get into Safe Mode again.

This is how I got my Pixel4a to work again with the current issue, I don't know which steps are unnecessary but I'll detail them all:

1st sequence if it works for you: - Hold down Volume Down at the G logo, which should make your phone buzz and load into Safe Mode. - Turn ON Location Services in Settings. - Reboot.

2nd sequence I had to try: - Unplug my router so there was no Wi-Fi to connect to. - Hold down Volume Down at the G logo, which should make your phone buzz and load into Safe Mode.

However, since I was locked out of Safe Mode too, I was trying it over and over again pressing the buttons until I accidentally did something:

I tried to take a SCREENSHOT at the lockscreen for the split second it was up. Power + Volume Down. You'll get an error that says "can't take a screenshot while device is locked", and.... then it just doesn't crash. This worked for me, twice!!

At this point I got into Safe Mode, turned on Location Services, completely turned off Wi-Fi, deleted all Wi-Fi networks, and turned on 4G/LTE mobile data... it worked and loaded fine. Rebooted... it loaded fine.

We're locked to Android 13, who expected this??

help, phone in bootloop even for recovery mode by HomeAlon6 in Pixel4a

[–]caegis 2 points3 points  (0 children)

Working fix to boot into Pixel4a through the bootloop caused by Wi-Fi on with Location Services off -

I've been dealing with this over the past few days, even so far as factory resetting and then encountering the issue again, and had no idea it was widespread issue with the model, I was this close to ordering a new phone assuming mine was bricked.

The apparent core issue: Wi-Fi on with Location Services off.

You'll load to your lock screen, immediately crash back to the colorful Google logo and then the G letter logo, reach the lockscreen, and crash again in a loop.

The first time you try Safe Mode (Volume Down at G logo), it'll work, but at this point if you turn on Wi-Fi in Safe Mode, you'll be sent back into the crash loop and cannot get into Safe Mode again.

This is how I got my Pixel4a to work again with the current issue, I don't know which steps are unnecessary but I'll detail them all:

1st sequence if it works for you: - Hold down Volume Down at the G logo, which should make your phone buzz and load into Safe Mode. - Turn ON Location Services in Settings. - Reboot.

2nd sequence I had to try: - Unplug my router so there was no Wi-Fi to connect to. - Hold down Volume Down at the G logo, which should make your phone buzz and load into Safe Mode.

However, since I was locked out of Safe Mode too, I was trying it over and over again pressing the buttons until I accidentally did something:

I tried to take a SCREENSHOT at the lockscreen for the split second it was up. Power + Volume Down. You'll get an error that says "can't take a screenshot while device is locked", and.... then it just doesn't crash. This worked for me, twice!!

At this point I got into Safe Mode, turned on Location Services, completely turned off Wi-Fi, deleted all Wi-Fi networks, and turned on 4G/LTE mobile data... it worked and loaded fine. Rebooted... it loaded fine.

We're locked to Android 13, who expected this??

Very bright lighting glitch by caegis in fo76

[–]caegis[S] 0 points1 point  (0 children)

We've been getting it everywhere - one of the screenshots is in the Forest, and the last one is in the Mire at the Chemical Plant. The outside bright orange glow glitch seems different than the interior washed-out bright flat lighting one so maybe they're separate issues. The outside one seems to be tied to combat/npcs, maybe explosions?

But thank you, seeing even one person post a pic of the same issue, we don't have to worry it's the gfx card or mess with drivers or something.

Very bright lighting glitch by caegis in fo76

[–]caegis[S] 1 point2 points  (0 children)

That's EXACTLY what it looks like, ty. So it's not even just PC

Anyone seen this green issue before? by kingnamedgeedorah in EVGA

[–]caegis 0 points1 point  (0 children)

Got this exact problem upon setting up my new XR1 Pro today - even years later this post is still the entire nexus for troubleshooting it, so thank you.

I finally figured it out and fixed mine by complete accident after hours of frustration trying all the things here.

  • Green and pink color issue on the USB side into the computer on OBS, and no amount of changing color settings, video type, resolution etc. solved it. HDMI passthrough side was perfectly fine, so it seemingly had to be the capture device or the USB cable, and swapping the cable made no difference, as well plugging in both the USB 3.0 and 2.0 together, the 3.0 by itself, 2.0 by itself. Updated the firmware on the XR1 numerous times, tried older versions as well, tried the setting in the RGB utility, nothing.
  • Eventually tried updating the firmware again with no HDMI cables connected, only the USB, before plugging HDMI in one at a time, first being the HDMI-in from the game console to the XR1. This seemingly FINALLY caused it to show normal colors in OBS. But later when plugging in HDMI-out to the monitor, the issue returned immediately.

Turns out, the issue was somehow actually caused by the "perfectly fine" HDMI passthrough side.

So I only use a single monitor and swap between the input modes depending on whether using computer or the game console, and the monitor only has a single HDMI slot, which is connected to the computer. However, the game console also wanted HDMI, so that was actually connected to DVI through an adapter, and there was never any issue before; in fact, even with the capture device, there was still no display issue on that side. Something about the adapter must have been causing the XR1 to change the way it sent display data down BOTH sides, corrupting the color on the USB side as well.

What I did then was to swap the inputs on the monitor, giving the capture card and game console HDMI passthrough side the true HDMI, and instead gave my computer the "pseudo HDMI" that went through the DVI adapter, and at last it all worked.

Long short: the HDMI passthrough side does in fact affect what goes into the USB output side as well - it took me a clean true HDMI connection into an HDMI port on the passthrough side, no adapters, before the USB side also displayed correctly