This happens all the time. Happens when I go to the app switcher and resets when I go back home. But as soon as I hear back into the app switcher, it moves to the side.

Here it is as I write this post:

  • LCP@lemmy.world
    link
    fedilink
    English
    arrow-up
    5
    ·
    edit-2
    7 months ago

    Pixel by any chance?

    I run into this bug every other day on my Pixel 6a. Also causes “swipe down on pill to use one-handed mode” to break. Have to reboot every time to fix it.

    • RGB3x3@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      5
      ·
      7 months ago

      Yeah, Pixel 8. I feel like the software is so full of bugs, at times it becomes unusable.

  • jacktherippah@lemmy.world
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    7 months ago

    It was a bug a while back. It went away, now it came back. It’s been here again for what? 1,2 months now? Actually, now that I think about it, it’s been an on and off bug ever since Android gained gesture navigation and the gesture bar LMAO.

    • RGB3x3@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      10
      arrow-down
      1
      ·
      edit-2
      7 months ago

      It’s the line on the right side. I’m in portrait mode, so it should be at the bottom.

        • Codilingus
          link
          fedilink
          English
          arrow-up
          1
          ·
          7 months ago

          Lmao, I thought the same thing. IIRC for Android 15, one of the features I read about, was better portrait & landscape support.

  • Ironfacebuster@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    7 months ago

    I had this happen all the time, although I’m using a beta version of Android (pixel 7 pro)

    Seeing this post made me realize that I haven’t seen this happen in a while, even though I’m still using the beta, maybe they fixed it? Good luck trying to report it as a bug by the way, I reported a notification shade rendering bug and they labeled it as a duplicate of a completely unrelated lock screen bug!