Some Pixel owners can't unlock their phones after the latest update

11 days ago by schizoidman to c/android

Reports have surfaced from users of the Pixel 10 Pro XL, Pixel 8a and Pixel 8 Pro, along with other models in Google's Pixel lineup. The mix...
load all comments
queeradjacent 62 points 11 days ago

Will be a good excuse to get off my ass and switch to Graphene

path: 0 26142562, hotness: undefined, score: 62, children: 41
orbituary 35 points 11 days ago

Good news. You can switch from your couch.

path: 0 26142562 26142925, hotness: undefined, score: 35, children: 9
mushroommunk 17 points 10 days ago

I dunno about them but my phone is only at 22% battery and I can't reach the cable from where I'm sitting.

path: 0 26142562 26142925 26143473, hotness: undefined, score: 17, children: 1
queeradjacent 3 points 10 days ago

It's been a minute since I flashed a rom but I feel like I'm gonna need a cable and a laptop?

path: 0 26142562 26142925 26151403, hotness: undefined, score: 3, children: 6
tigerhawkvok 13 points 10 days ago

It's tap to pay (or use the public transit) that's keeping me back.

path: 0 26142562 26155507, hotness: undefined, score: 13, children: 17
joat_mon 17 points 10 days ago

Check out WALT

It's still in development but is being built specifically with GrapheneOS in mind. Hopefully we should have a privacy focused tap-to-pay within a year.

path: 0 26142562 26155507 26156807, hotness: undefined, score: 17, children: 1
Grabthar 7 points 10 days ago

Put your card in your phone case.

path: 0 26142562 26155507 26156587, hotness: undefined, score: 7, children: 9
HereIAm 4 points 10 days ago

You can still use Google wallet if you're happy to accept Google services in full*. Also, Curve has touchless payment that doesn't require Google's stuff. You do obviously trade Google for another company to slurp up your data, so it's not a perfect solution.

* I'm bad and a big fat liar, Google Pay does indeed not work on 3rd party OSes. Curve Pay does though, as that's what I'm using.

path: 0 26142562 26155507 26156317, hotness: undefined, score: 4, children: 3
OpenPassageways 1 point 9 days ago

Tap-to-pay is an obstacle for GrapheneOS adoption for sure. It seems like some Garmin watches have tap-to-pay support which doesn't just utilize your phone like other smart watches. I'm going to be heading in that direction soon. I've found some reports that the Vivoactiv series actually loads the card onto the watch so I'd use the Garmin app in a secondary profile to set it up but then largely leave the Garmin watch disconnected from my phone but should still be able to use the watch for tap-to-pay.

path: 0 26142562 26155507 26173022, hotness: undefined, score: 1, children: 0
theparadox 12 points 10 days ago

I did recently and its been better than I expected. The only real issue was RCS. After 2 years of me not having a Facebook account, my friends finally switched from Facebook's system to a group text... which broke utterly without RCS.

I had to install Google's Messages app and fiddle with the native app and Google's RCS settings and eventually it start working again. I am pretty competent but the support for this seemed to be digging through forum posts and trying a bunch of different solutions unsuccessfully and then having it suddenly work and not knowing why. I hope they manage to get a solution working in the native app.

Otherwise a great experience!

path: 0 26142562 26144760, hotness: undefined, score: 12, children: 10
queeradjacent 7 points 10 days ago

Good thought. Luckily all my critical folks are on Signal.

path: 0 26142562 26144760 26151388, hotness: undefined, score: 7, children: 1
Unreliable 3 points 10 days ago

It's actually really easy nowadays. There's specific setting in the sandboxed Google play for ICC identification (needed for RCS) and activation/it getting it to work is trivial as long as you use Google messages.

The native RCS app is something they want to do but is far out.

path: 0 26142562 26144760 26145651, hotness: undefined, score: 3, children: 1
OpenPassageways 3 points 10 days ago

I was able to get RCS to work on Google Messages easily on GrapheneOS. The issue I had was trying to NOT use RCS. My messages have never been encrypted with iPhone users so I'm using Molly for people that matter anyways, and I was hoping to be able to recieve group texts even though I wasn't using Google Messages anymore. Nope, could never get it to work. I tried deregistering from RCS on Google's page, I tried contacting TMobile support, etc. Those group text just disappeared into the ether. So I'm back to Google Messages until Grapheme Messages adds RCS.

path: 0 26142562 26144760 26146470, hotness: undefined, score: 3, children: 5
frongt 4 points 10 days ago

I think graphene inherited this issue. It certainly inherited the memory bug in the latest update.

path: 0 26142562 26145170, hotness: undefined, score: 4, children: 0
dontfeedthemouse 4 points 9 days ago

This is what I did and do not regret a thing. It takes a few weeks to get used to (especially when coming from iOS), but once you find good open source replacements for daily apps, there's no going back. The only thing I miss is Apple Pay, but using regular card again is not a huge deal.

path: 0 26142562 26171208, hotness: undefined, score: 4, children: 0
android
android

@lemdro.id

login for more options
22216
4394
1644

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

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

🔗Universal Link: !android@lemdro.id


💡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: !askandroid@lemdro.id

For fresh communities, lemmy apps, and instance updates: !lemdroid@lemdro.id

💬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 !askandroid@lemdro.id.

  3. Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to !androidmemes@lemdro.id.

  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

go to feed...