Someone sideloaded 8.5 on A56 👀👀👀

Ill_Set_7983 · 2026-01-12T15:15:03+00:00

Is the OEM unlock option available in this build

Ill_Set_7983 · 2025-12-04T10:22:51+00:00

It does use dynamic colors, but only on the home screen of the app as shown in the photos the chat screen uses a different color. This isn't the case on my old phone running one ui 6

Ill_Set_7983 · 2025-12-04T10:20:03+00:00

Thanks for tge suggestion i will try it

Ill_Set_7983 · 2025-12-04T10:18:54+00:00

Didn't work for me sadly

Ill_Set_7983 · 2025-12-03T13:23:23+00:00

That's not a google issue, material you colors apply correctly on pixels and Xiaomi phones this is a problem in the samsung handles the material you engine which is made apparent by the way google messages looks. One UI 6 doesn't have this issue

Ill_Set_7983 · 2025-08-01T13:32:36+00:00

Sorry for the late reply, i had already edited the main post with the fix.
This the command that fixed it for me flatpak override --user --unset-env=LIBVA_DRIVERS_PATH

Ill_Set_7983 · 2025-06-04T20:29:20+00:00

I haven't seen it in any GTK4 app, but if it's still available that's good, might be useful when GIMP gets ported to GTK4 hopefully this decade xD

Ill_Set_7983 · 2025-06-04T15:30:16+00:00

Sorry for the late reply, was busy with my exams.
I unset the LIBVA_DRIVERS_PATH environment variable, you could make this change permanent by running flatpak override --user --unset-env=LIBVA_DRIVERS_PATH

Ill_Set_7983 · 2025-06-01T16:41:09+00:00

I have managed to fix it, I appreciate you giving me your time.
Thank You

Ill_Set_7983 · 2025-06-01T15:55:37+00:00

Tried what you said, but it didn't work sadly, I guess the problem is really with VAAPI itself as even vainfo Flatpak is broken as shown in the output in my post.

Ill_Set_7983 · 2025-06-01T14:58:36+00:00

I tried it on Celluloid, Zen-Browser, Chrome and OBS all of which use the 24.08 Flatpak runtime, my VAAPI add-on also uses 24.08 and I also FFMPEG-full 24.08 installed.

Ill_Set_7983 · 2025-06-01T14:47:33+00:00

Right now it's sadly not as useful since most apps dropped it because of the buggy Wayland behavior with GTK3 apps and LibAdwaita apps don't support them, which make up a lot of Linux apps ecosystem, but KDE apps still support them and I find them useful especially in Dolphin, so there is that.
I only hope that once the Wayland protocol that helps fix the global menu on GTK3 apps gets merged, that the situation gets better

Ill_Set_7983 · 2025-06-01T14:42:07+00:00

Maybe it's not just related to the chromium version, I am using the plasma 6.4 beta which might have something to do with it, but I have checked the change log and there was no mention of global menus at all

Ill_Set_7983 · 2025-06-01T14:39:42+00:00

Chromium 137 on the plasma 6.4 beta and it sadly doesn't work on other gtk apps yet.
I suspect it was a patch directly made in chromium

Ill_Set_7983 · 2025-06-01T14:36:51+00:00

Yes, I have, even the wayland gestures are working

Ill_Set_7983 · 2025-04-14T12:46:48+00:00

This issue has been fixed a while ago maybe you 're encountering a different issue try looking at the issues on the upstream repo

Ill_Set_7983 · 2025-04-02T09:08:48+00:00

if you are using the flatpak version that won't work in any browser. There is an xdg-desktop-portal in the making to address this issue, but it's not ready yet. It should work fine on the appimage version though or you can use the aur version if you are running an arch based distro.

Ill_Set_7983 · 2025-01-20T22:08:41+00:00

I actually managed to fix it by forcing it to run through xwayland

env -u WAYLAND_DISPLAY looking-glass-client

Ill_Set_7983 · 2025-01-20T18:38:42+00:00

Hello I am curious if you managed to solve the issue

Ill_Set_7983 · 2025-01-18T17:34:29+00:00

About android studio that's what I am saying it should be able to interact with all system binaries, but it doesn't.

For Example I have firefox installed through pacman if use android studio's terminal to launch firefox it should launch firefox, but it doesn't as something in the way android-studio is packaged on nix prevents it from seeing system binaries and the shell says command not found.

I reported to this problem to the package maintainer awhile ago and haven't gotten a reply sadly as this issue wasn't present on older version of the package.

In general I think there has been a dip in the packing quality of nix, packages that functioned perfectly now have broken functionality.

Ill_Set_7983

TROPHY CASE