10
submitted 3 months ago* (last edited 3 months ago) by Varyk@sh.itjust.works to c/googlepixel

for anyone with the same problem, I add a border until the photo is larger than 1600x2650, at which point you can see the entire photo on the screen, as shown here:

This is one of the dumbest things I deal with on the pixel, although there are a lot of dumb things with this phone.

OP below:

ever since I got the pixel, one of the most frustrating non-Functionalities has been that I have to manually screenshot any picture that I want to make into a wallpaper background because my Google pixel 6 enlarges by about 3x any photo, I choose to make my wallpaper background and cannot make the picture smaller by pinching it smaller.

but now even if I save a screenshot, it blows it up more than 3x and I have to manually add a giant border around the picture in an external app so that the picture itself is much smaller if I want to see the entire picture on my phone wallpaper.

is this just some shitty thing with my phone or do all pixels do this?

you are viewing a single comment's thread
view the rest of the comments
[-] BearOfaTime@lemm.ee 1 points 3 months ago* (last edited 3 months ago)

Try doing it from the gallery, pick your image, then 3-dot menu, Set As, choose Wallpaper, it gives you a cropping box. Works perfectly for me, so far.

Edit: On some phones the cropping box isn't obvious - you grab the image and drag it around within the preview space.

[-] Varyk@sh.itjust.works 1 points 3 months ago* (last edited 3 months ago)

That second photo in the previous comment is the preview pane and cropping tool you're taking about, unfortunately.

however i enter the wallpaper app, either through three dots, use as, wallpaper, or through the home screen long tap process i described, the preview pane pops up with a massively oversized picture that I'm allowed to crop but not resize.

Looks like my pixel had something wrong with its wallpaper app.

at least the border trick works.

i did ask about this on reddit a couple years ago and had a few people respond with the same issue, so it seems like some crappo software some of us are stuck with.

I don't want to factory reset the phone over this glitch, given how many other pixel bugs probably won't be fixed anyway even after the hassle of a reset.

it's bizarre, but I'm glad that it isn't affecting you or others.

this post was submitted on 11 Aug 2024
10 points (100.0% liked)

Google Pixel

1426 readers
2 users here now

The home of /r/GooglePixel on Lemmy and the Fediverse!

The place for everything related to Google Pixel devices, including news, reviews, tips, tutorials, rooting, and app discussions.

!googlepixel@lemdro.id

Rules

  1. Stay on topic: all posts should be related to Google Pixel devices.
  2. No offensive/low-effort content: avoid posting offensive or low-effort content that does not contribute positively to the community.
  3. No self-promotional spam: active community members are welcome to post their apps but should also participate in comments and discussions. Please do not post links to your own website, YouTube channel, or blog.
  4. No reposts/rehosted content: whenever possible, submit original sources. If the original source is not available in English, you may provide a translation. Reposts of the same content are not allowed.
  5. No editorializing titles: when submitting articles, do not change the titles. You may add the author's name if it is relevant.
  6. No piracy: sharing or discussing pirated content is strictly prohibited.
  7. No unauthorized polls/bots/giveaways: please do not create unauthorized polls, use bots, or organize giveaways without proper authorization.
  8. No affiliate links: posting affiliate links is not allowed.

founded 1 year ago
MODERATORS