this post was submitted on 08 Feb 2024
95 points (85.7% liked)

Android

17414 readers
159 users here now

The new home of /r/Android on Lemmy and the Fediverse!

Android news, reviews, tips, and discussions about rooting, tutorials, and apps.

πŸ”—Universal Link: [email protected]


πŸ’‘Content Philosophy:

Content which benefits the community (news, rumours, and discussions) is generally allowed and is valued over content which benefits only the individual (technical questions, help buying/selling, rants, self-promotion, etc.) which will be removed if it's in violation of the rules.


Support, technical, or app related questions belong in: [email protected]

For fresh communities, lemmy apps, and instance updates: [email protected]

πŸ’¬Matrix Chat

πŸ’¬Telegram channels / chats

πŸ“°Our communities below


Rules

  1. Stay on topic: All posts should be related to the Android OS or ecosystem.

  2. No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to [email protected].

  3. Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to [email protected].

  4. No self-promotion spam: Active community members can post their apps if they answer any questions in the comments. Please do not post links to your own website, YouTube, blog content, or communities.

  5. No reposts or rehosted content: Share only the original source of an article, unless it's not available in English or requires logging in (like Twitter). Avoid reposting the same topic from other sources.

  6. No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.

  7. No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.

  8. No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.

  9. No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!

  10. No affiliate links: Posting affiliate links is not allowed.

Quick Links

Our Communities

Lemmy App List

Chat and More


founded 1 year ago
MODERATORS
 

We typically like Pixel phones a lot, but we have some reservations about Google's quality control

top 50 comments
sorted by: hot top controversial new old
[–] [email protected] 3 points 7 months ago* (last edited 7 months ago) (2 children)

Google Pixels suck.

The 4a did everything right. Plastic cover? Yeah you use a protective case anyways.

The 6a that I now have is worse. I sent back a 7pro because it was so horrible. I dont want a tablet, I want a phone.

the camera

is worse! I cant believe that but I compared pictures. At least the selfie Camera is absolute garbage.

size, shape, materials

  • the phone is huge
  • its rectangle size is worse to hold in the hand
  • the 6a had some kind of plastic which is durable. The 7pro I had has a glass back? Wtf why?

fingerprint sensor

is so much worse. Why put it behind a display? I actually replaced one, so that is not the problem. But you cant unlock directly, they are waaay less reliable and you often need to create duplicate scans. Compare that to the damn 4a (and all other fingerprint sensors of that time) that just worked instantly.

No headphone jack

This is such a pain as an audiophile. I have awesome headphones and of course they are on a cable.

Bluetooth is factiually worse.

  • It takes forever to connect (apple devices alway connect first for example).
  • the controls for pause etc. take like a second to work
  • you always broadcast your Bluetooth ID around
  • you are attackable, like the iPhone DDOS attack
  • you need more tiny battery powered devices for nothing
  • headphones are always more expensive and often have worse audio quality

If you want to use normal headphones, the only good DACs are by Google and Samsung, and at least german electronic markets (!) dont have them.

And if you use a DAC, this works over USB. If you need to allow random USB devices all the time, this means you are also attackable through a cable.


My Pixel 4a is a bit slow, but the battery still lasts over a week in idle. I use it as an alarm clock now as its insecure.

I have not tested a Pixel 8, and the hardware for sure sounds appealing. But if Google continues this shitty path of useless "inventions" like the Fingerprint sensor behind the Glass, unnecessary huge and fragile phones, and purposeful decrease in security by needing Bluetooth all the time, while actively contributing to E-Waste, I will never recommend them.

[–] [email protected] 2 points 7 months ago (1 children)

This post strikes me as a little hyperbolic but I definitely agree that they've gone downhill in a lot of ways. I have a 3a and that genuinely feels better made than the more expensive 7a I tested recently. They had a good thing going with the size and feel of their older devices and they totally fucked it.

[–] [email protected] 1 points 7 months ago

In that case, its not hyperbolic :D

I has a 7pro and it was so damn huge. Sent it back again.

[–] [email protected] 1 points 7 months ago (1 children)

What's your next phone gonna be?

[–] [email protected] 2 points 7 months ago* (last edited 7 months ago) (1 children)

Pixel 8(a), until there is an alternative that meets GrapheneOS requirements. Poorly.

[–] [email protected] 1 points 7 months ago* (last edited 7 months ago) (1 children)

Does the Fairphone meet gOS' requirements?

Edit: Apparently not, unfortunately. I'm probably gonna keep getting whatever Google comes up with next.

[–] [email protected] 2 points 7 months ago* (last edited 7 months ago) (1 children)

No, by far not.

https://discuss.grapheneos.org/?q=fairphone%205

Basically:

  • they are extremely late on Updates, like months behind
  • they claim to have an update timespan they cannot have because certain parts will not be updated anymore and firmware vulnerabilities are a thing
  • their hardware is not secure enough
  • they dont meet the minimum requirements

https://grapheneos.org/faq#future-devices

[–] [email protected] 1 points 7 months ago

That's really unfortunate. Can't have it all, it seems.

[–] [email protected] 1 points 7 months ago

I have a moto g7 power. No complains here

[–] [email protected] 16 points 7 months ago* (last edited 7 months ago) (4 children)

All I know that really surprised me is I'd been disgusted with nothing phone 1 constantly rebooting for no reason since an update (still does it).

When I complained on a reddit sub about it I got a ton of replies saying it's normal and not as bad as the pixel phones.

I've nowhere to go with that people are defending a completely unstable buggy phone and I've owned half a dozen androids before that and never seen any of them just randomly restarting.

[–] [email protected] 2 points 7 months ago (1 children)
[–] [email protected] 2 points 7 months ago* (last edited 7 months ago)

I wouldn't buy the phone 1 again anyway put it that way.

It was actually great until phone 2 released then they updated it to be very unstable and the cameras also got noticeably worse from updates.

On the plus side I've read the custom roms for it are pretty good, I haven't went that far yet but I know I will eventually.

[–] [email protected] 1 points 7 months ago

I used to have that issue on my midrange samsung when i set the ramplus(virtual ram in samsung) to max and did medium to heavy multi-tasking. It was mitigated in a future update but did happen once a while. The slow storage speeds combined with heavy usage of virtual ram were the main reason for that.

[–] [email protected] 7 points 7 months ago (1 children)

I've had pixel phones for at least 5 years now. I've probably had less than 10 random restarts, most of those would have been from apps crashing.

Sometimes the device gets slow and I restart it. But that happens maybe 3 times per year. Otherwise the phone only gets restarted when an update is installed.

[–] [email protected] 1 points 7 months ago* (last edited 7 months ago)

Yeah I'm skeptical of those claims as well, I've never owned a phone that did it a lot until this one and I'm pretty sure it's Nothing who introduced the vast majority of problems.

Their just too concerned with things like clothing lines and pr stunts to actually fix anything they break

[–] [email protected] 3 points 7 months ago

I have a 5 year old phone and it does in fact not randomly reboot.

[–] [email protected] 12 points 7 months ago (2 children)

Largely exaggerating bugs. If it happens to you that sucks, but I've never actually met anyone in the real world running into these bugs. This is "your holding it wrong" writing designed to rile up nerds.

[–] [email protected] 9 points 7 months ago* (last edited 7 months ago)

You shouldn't discount these reports just because you haven't seen them yourself. I mean, how many people do you talk to in the real world about their Pixel phones? If it's less than hundreds, it doesn't really say much β€” that's well within chance since, as the article states, the problem is inconsistency. If 1% of users experience a given problem, that's actually a pretty big deal. If 10% experience it, it's pitchfork time.

Pixel phones are notorious for poor quality control, and Google is notorious for poor customer support. That's a bad combination. Lots of people have perfectly good experiences, but there are still a lot of problems that aren't just flukes.

I read the article and I think it's pretty fair. I've used a couple different Pixel models and followed their respective subreddits for years. It's always something. Green tint, or poor signal, or overheating, or a barely-functional fingerprint reader, for example. None of these things affect everyone, but they're real problems. Probably the fingerprint reader is the most widespread. At least that's improved (for me) over time.

[–] [email protected] 4 points 7 months ago (1 children)

I have an 8 Pro that has had bugs since it was released.

They're mostly frustrating inconveniences that make using it annoying. Graphical glitches, phone calls hanging up unexpectedly, being able to type even after going into open apps view, not being able to switch apps because it just disappears from the open apps view, the fingerprint sensor just not working at all sometimes, and more.

Nothing that breaks the phone, but it's real annoying more often that it should be.

[–] [email protected] 2 points 7 months ago

IDK, nobody gets any real numbers so it's hard to say. I just know 9 pixel 6-8s and nobody has run into anything major.

[–] [email protected] 6 points 7 months ago (1 children)

It's interesting, it's because of such articles and comments about the various issues (mostly battery life, and sometimes connectivity) that I didn't consider Pixel for my new phone.

It's sad because they are supposed to be the Android top devices. Motorola seems decent nowadays, Asus Zenfone got a lot of backlash recently about the locked bootloader, but at least their phones are compact and have audio jacks. Even Xiaomi I could consider with DNS blocking to stop the trackers, their quality-price ratio is quite good, especially second hand.

[–] [email protected] 3 points 7 months ago (1 children)

Unfortunately, the next Zenfone is looking to be quite a lot larger. I've been using Nexus and Pixel for years, and while my uses have always been rather simple, I've never had any serious issues aside from the LG bootloop on my Nexus 5x. Motorola phones get practically no updates, and unfortunately Xiaomi is a non-starter for those of us in the US.

That said, I've also been using Graphene, because I no longer tolerate the tracking and other productization of me. That's not just a Google thing, nor limited to their phones, but they're certainly one of the worst offenders. It's ironic that their own phones offer some of the most freedom to remove them from our lives.

[–] [email protected] 2 points 7 months ago

Unfortunately, the next Zenfone is looking to be quite a lot larger.

Crap, that's sad to hear.

[–] [email protected] 19 points 7 months ago (2 children)

My pixel 7 Pro's vector motion sensor is broken. How the hell does that even happen? I've never even heard of it and there's like nothing online about it.

I can't do anything that requires tracking how the phone is moved- no compass calibration, no Map's guidance arrow, etc.

[–] [email protected] 1 points 7 months ago

Have you considered getting it checked at a service center? There's a possibility it's a hardware issue.

[–] [email protected] 9 points 7 months ago

My old phone did that. Anyone looking at my maps data must have thought I walked like a crab everywhere.

[–] [email protected] 12 points 7 months ago (1 children)

My Pixel 7a's battery life was so terrible I just gave up on the phone. I was literally charging it 2 times a day from sub-10% to 100% with light use (no games, no intense apps, under 2h SoT for the full day). I lost 7%+ per hour idle. Days when I actually needed to use my phone, I'd need to bring my charger for a third mid-day top up to 100%.

I bought a Sony Xperia 10 V to replace it. It's not perfect (it doesn't support all the NA carrier bands so signal is a bit spotty in big stores), but the battery life is amazing. Same usage patterns and I only go from 80% to 50% most days. I only 100% charge once/month for battery health. I frequently go 1Β½-2 days without charging. I don't know how well it plays games, but with 8GB RAM, it's snappy with app multitasking. Oh, and I can plug it into my car (3.5mm). And it's a 68mm wide, so quite easy to use one-handed.

I had been buying Google phones exclusively since the early Nexus days, but I'm unlikely to buy one again. At least for the foreseeable future.

I hope Google can figure their shit out. It's bad for everyone when Apple and Samsung capture increasingly large marketshare, and Google's fuck ups are turning people off smaller vendors.

[–] [email protected] 4 points 7 months ago (3 children)

Were you using Firefox? On my phone, FF browser takes ~5% battery per hour, even if I force close it, there is some background task eating battery. I uninstall it and bam! No more 40% drain during the night but only 2-3% drain in 8 hours.

[–] [email protected] 2 points 7 months ago* (last edited 7 months ago)

I am using Mull (on a Pixel 6a) and it took 3% with 40min screen time. Thats great.

I have no idea what is causing that for you.

I am also using

  • ublock origin
  • noscript
  • dark background light text (saves a ton of screen energy)
[–] [email protected] 3 points 7 months ago* (last edited 7 months ago)

Were you using Firefox? On my phone, FF browser takes ~5% battery per hour,

Mine drains about 6% per hour, it's absolutely unsustainable. Just uninstalled firefox, let's see. I regret getting it so much (pixel 7) lol.

edit. wasnt it, what a piece of shit this phone is.

[–] [email protected] 2 points 7 months ago

Might have been Firefox. My phone reported it was Amazon Photos, so I uninstalled it, but then it was another app instead, which I uninstalled, then it was a third one (which I think was Firefox?). At that point I gave up, assuming it was a problem with the G2 Tensor chip not cycling down while idle, not a specific app. Even if 3 apps that I've never had a problem with on other phones all have problems on the Pixel 7a, that's just not good enough.

load more comments
view more: next β€Ί