I experience several graphical issues with Vanadium at the moment. When navigating to a tab that have not been used for a few minutes, the page first blacks out, then it seems like it is loading the page, but instead it just shows a full white page. If I wait a minute, the page appears. I often refresh the page, and it appears like normalt, but it is a hassle if it's on a page I don't want to refresh... This happens on normal tabs and incognito-tabs. When going to home screen and opening Vanadium again, the white page disappeares, and it shows the web page like normal.

And, it has happened several times that I have removed the incognito-tabs, but the "Close all incognito tabs" button/option in the pull down notification area is still there. When clicking on it, it does nothing, it just removes the notification 🤷

I have noticed these behaviours on several versions.

Pixel 7 Pro
2025030900
versjon 134.0.6998.95.0

    Panda-na

    I experience similar problems with brave so it could be an upstream chromium issue.

        Panda-na
        user

        I experience several graphical issues with Vanadium at the moment. When navigating to a tab that have not been used for a few minutes, the page first blacks out, then it seems like it is loading the page, but instead it just shows a full white page. If I wait a minute, the page appears. I often refresh the page, and it appears like normalt, but it is a hassle if it's on a page I don't want to refresh...

        Same behavior here.

        It seems to be a known upstream bug:
        https://github.com/GrapheneOS/Vanadium/issues/726

            Panda-na I had this issue when using Brave on stock PixelOS a couple of weeks ago as well. Most definitely upstream. Not sure why Google can't get their stuff together. Did they fire their experienced QA testers and replace them with interns?

              It may be an OS GPU driver issue rather than a Chromium issue. Someone should test an older Brave release based on Chromium 133.

              Panda-na

              You're not alone.

              I've got similar got similar issues since Version 133 on a Pixel 9.

              https://discuss.grapheneos.org/d/19730-vanadium-version-13306943490-released

              Nonetheless, it genuinely seems to be some kind of upstream issue, most likely the GPU Driver, as GrapheneOS said.

              Sometime later I've noticed square shaped, white flashes when minimizing the Widget of the weather app that I'm using, or black screens when opening Gboard from the launcher. On the other hand, since updating to Vanadium 134 only the website content bug remained and since Android 15 QPR2 the Gboard Bug disappeared.

              Actually, I've had similar issues years ago with a completely different Android Device. In that case, only a factory reset fixed it.

                Panda-na I experience several graphical issues with Vanadium at the moment. When navigating to a tab that have not been used for a few minutes, the page first blacks out, then it seems like it is loading the page, but instead it just shows a full white page.

                I have found that switching away and back, such as switching to a different tab in the group and back, or switching to a different app and back, causes the paint to work.

                    de0u Yes, I tried that, and it is a workaround. But it's good to know I'm not the only one. I know that sometimes there can be hardware issues that only affect a specific device, and only fix is factory reset or buy a new one. Good to know it's not that.

                      I had the same problem and due to the hint with graphics driver I enabled 'Skia Graphite' options via brave/chrome://flags for Brave+Vanadium and it seems to help until now.

                      Panda-na this is not new. Been there since 133 for me. Hoping for a fix soon

                        It may be from Android 15 QPR2 rather than a Chromium issue. It hasn't been narrowed down if it's a Chromium or OS issue.

                          GrapheneOS I've also experienced this issue. According to my memory, it's highly likely to have occurred to me before the QPR2 update.