It sounds like a bug with the image proxy feature like you suggested.

What version of Android are you using?

Are you using a customized rom that replaces the WebView component?

On a vanilla pixel 6 running Android 16 it’s working for myself on Voyager and Boost.

For those that click in does this example work for you? What client and os are you using?

Edit: I noticed the colours are wrong on boost. This was fine in the past, curious.

They need to fire their entire upper management team and roll windows back to 7 and try again.

Arch recently moved legacy Nvidia support to the AUR. That might have left you with a broken install.

You would probably have an easier time with a mainstream distro like kubuntu LTS. They tend to be better suited for older equipment.

It can be challenging to fix the bootloader once it dumps you into this situation. On a UEFI secure boot installation the EFI shim is responsible for allowing the modules to load each time there’s a change.

If you have a legacy MBR installation the Nvidia modules might just need to be reinstalled. This was a common issue when updating the kernel.

Edit: switching it to the Nouveau drivers might get you back into the OS. Would need to tweak your environment from a working one with a live environment potentially.

This issue feels like a stack problem, peeling back the layers.

Most of the information I’m finding about this flavour of arch doesn’t reveal much about libreboot’s role in this issue. I’m not familiar with the device and online results are vague about what the specs are.

My main thought is If you’re using a Nvidia GPU or other proprietary software to run hardware, did you reinstall its software after changing the kernel? I’m not sure if your distro automatically does that for you.

Are you using shim for anything?

I’m wondering if something went funny with your mok enrolment or if it failed to use the key to sign the module? Could test by temporarily disabling secure boot. (But would continue to fail if not the problem; such as the modules are compiled against the wrong kernel)

My other thought was that I’m under the impression that endeavourOS uses pinned versions and swapping out the kernel puts you in an undefined state.

You might have some luck jailing it on an working os with the configuration you desire and regenerating the boot files. Same idea as using the rescue environment on a livecd. The last time I had this idea it was a big waste of effort. When I realized I could just roll back using a backup.

Edit: maybe the drive is dying try testing it?

Looks like the colour temp was changed in the monitor’s settings. (OSD menu)

Happy99!!

They should just rollback to windows xp and patch the security issues. It happily ran on 128MB of ram.

My buddy had success running it off a pi.

But he had to encode everything ahead of time as h264.

I love the syncplay feature i just wished it worked much better with large groups.

Heh, you know it’s bad when the OEMs are throwing shade.

I’m really hoping that the price of the vr headset meets or beats the Facebook models.

So just the easy part lmao

What a crazy looking url.

Did you get it working?

In my humble opinion that was probably the best windows of its era. Windows XP sp2 was the most important change with its own firewall.

Hidive is probably the last good one, unless something changed in recent times.

No, neither does M3. You can read more about this project here: https://asahilinux.org/docs/platform/feature-support/m4/ Even M2 and M1 support is still being worked on.

Wow, when I see a waifu come up on my comms system I’ll know we’re living in the future.

That’s likely caused by your DNS provider blocking it.

486 and first gen Pentiums are still supported, though I’d expect not for much longer.

It’s funny you mention that.

I’ve been loosely following development around maintaining support for those. (And seeing i686 become the x86 soft target)

It seems we’re entering the era where test units related to these legacy platforms are no longer blockers should they fail. We’re also seeing a mass exodus for support of the x86_64 v1 and v2 feature sets in some distributions and projects.

But that doesn’t mean no one is working on supporting legacy stuff.

https://www.phoronix.com/news/Linux-6.16-SoundBlaster-AWE32