• General

  • Stretched and low resolution wallpaper

Hi, however I try to setup wallpaper for my pixel 7, it's always a cutoff low resolution pic.
It only shows perfectly before applying.

    I also got tired trying to apply a nice wallpaper to my phone and stopped since I had the exact same issue with the op. Is there any solution?

    EconomicSachs
    Everyone has wallpaper working in GOS? That's really strange.
    I tried different profiles, home launchers, wallpaper apps, all have this same issues.

      zzz Thank you for the answer. For unknown reasons I saw 0 reply to this thread and was wondering why.

        zzz I tried changing to the width of 1344, resizing to the exact screen ratio of 20:9 (pixel 7), using photophase which can't even launch properly due to android version compatibility issue.
        So I have not found a working solution.
        Is this bug happening to certain devices or? Do you guys just get by with the broken wallpaper? I'm not into fancy UIs but having a custom background paper seems to be basic and useful..

          4 months later

          Same here.
          No solution seems to work.

          I thought this would have been an easy fix, but seen that the GitHub Issue has been there for over 1 year I don't think we can expect a fix for this anywhere soon.

          For now I'm just going to stick with a black wallpaper, even if sad.

          Maybe @GrapheneOS could help us all? I would love to set a cool background on my secondary profiles.

            bael these kinds of issues are not usually fixed by the GrapheneOS project members because they're usually too busy with other things. As you've pointed out, there's already an issue in the tracker for this, so pretty much the only thing we can do is wait for it to be fixed upstream or for a community member who knows what they're doing to fix it.

              10 days later

              I found ways to get it work by using other wallpaper app. You can downloaded the wallpaper changer app from Aurora (link on play store: https://play.google.com/store/apps/details?id=de.j4velin.wallpaperChanger), and set it as your live wallpaper. It works absolutely fine without internet permission. After you added your wallpaper, go to the settings in the app, go to image size and choose display, that fix all the issues. I currently have 133 high resolution wallpaper and have them randomly switch every 5 minutes or whenever I unlock the screen or double-click the homescreen, it looks very nice. If you encounter issue where GOS switched back to the system wallpaper, make sure you set the battery to unrestricted, and turn on "Auto-rescan" inside the app. I set it to rescan every 3 hours, which I believe would help the app keep running in the background.

                3 months later

                Asparagus thank you for the recommendation of this app, it was exactly what I was looking for.

                    spiral You're welcome, I'm glad that it helped you! Thank you for responding, I thought no one is looking at this issue anymore since no one reply.
                    Extra tips, if you encounter the wallpaper being killed, you might have too many stuff in the background or switch between profiles too frequently. Mine was killed all the time because I don't have that much ram and I switch between profiles. Now that I only use one profile it hasn't get killed for months.

                      a month later

                      I have just now switched to 7a from 5 and the bug is present only in 7a for me, even with a new install on both.
                      I can use a huge image on 7a, which then the phone scrolls through.
                      Another bug I am getting is that scrolling through screens on the desktop is has an eye-hurting frame-rate now. It is perfectly smooth on the pixel 5, and on 7a, the option smooth display does not seem to have a noticeable effect.

                      a month later

                      I've had issues with this to, I just cutting the wallpaper to fit my screen height (in pixels) before setting it as my wallpaper and I've never had any issues while doing it this way.

                      6 months later

                      Still an issue on the Pixel 9 Pro years later. I've seen this blamed / passed off to AOSP, but I have not had this issue on Lineage, so other projects have found a way to fix this.

                      As a privacy focused OS, and profile use being a cornerstone to privacy-minded daily driving, fixing this bug should be a higher priority. A fundamental part of the advocated UI experience is broken and lightly steering users away from best practices.

                      For me, mostly after picking the phone up from a hiatus and unlocking, the wallpaper is primary signal to easily tell which profile I am currently in. Having to jump through hoops to get that wallpaper to look normal is frustrating. For this bug to be known and ignored for years, when your user base is probably some of the most active users of profiles (vast majority of regular Android users don't use profiles), is confusing... [removed]

                        spiderman44

                        Why do they hate their users? Are you actually serious?

                        You do realize that for every "I'm sad about my wallpaper" request we make, actual security features don't get built? It's a zero sum game.

                        Why are you demanding they fix code they didn't write, when you can solve your own problem by installing a 3rd party launcher and be done with it? Ridiculous.

                          spiderman44 As a privacy focused OS, and profile use being a cornerstone to privacy-minded daily driving, fixing this bug should be a higher priority.

                          On the contrary. Privacy focused here implies that issues with custom wallpapers should be very low priority, because non-default wallpapers are bad for privacy in the first place.

                            spiderman44 I have not had this issue on Lineage, so other projects have found a way to fix this.

                            spiderman44 For this bug to be known and ignored for years, when your user base is probably some of the most active users of profiles (vast majority of regular Android users don't use profiles), is confusing...

                            You're assuming that their fix is actually done well. It's very possible their fix is hacky and not up to GrapheneOS's standards. LineageOS has a very hard time keeping up with upstream changes so their OS is always lagging very far behind. It's terrible for security. They also make changes that reduce security as well. It's my understanding that one of the main reasons they lag behind on updates is because it's very difficult for them to maintain all of their invasive changes to the OS, making big updates a much bigger job for them.

                            GrapheneOS always ships updates very quickly. If fixing the wallpaper stretching bug is easy, cool. However, if they have to make a lot of changes to make it work, then that would mean developers would have to spend a lot of time maintaining the fix until it's fixed by AOSP, which at this rate may be a while. This isn't counting all the time it would take for a developer to research the issue, dig through the code to find the source of the bug, test fixes, etc.

                            spiderman44 Why do you hate your users?

                            GrapheneOS doesn't hate its users. The priorities of the project are very clear. They would like to fix these bugs, but it's not always possible since they're always busy with higher priority tasks. If the project could hire more developers, some of these bugs may be fixed. Also, GrapheneOS is an open source project. A community member can do the work themself and submit a PR to fix the issue.

                            Considering all that they have accomplished, suggesting that the project hates its users because of one bug is, if you ask me personally, insulting, so I have edited your post to remove that one sentence.