this post was submitted on 27 Feb 2024
698 points (97.0% liked)
Firefox
17301 readers
132 users here now
A place to discuss the news and latest developments on the open-source browser Firefox
founded 4 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
And this is why I'm getting a Pixel for my next phone, it's the only phone line GrapheneOS works on, and it has a nice long support cycle.
I wish it was available on more phones though. I know there are other projects, but they don't seem as well run as GrapheneOS.
Been using pixel phones for that reason, since... Pixel XL, and six pixel phones since then. Used several different AOSP based OS-es, most recently CalyxOS on Pixel 4a, and then GrapheneOS on Pixel 6a and now the 8 Pro.
Everything works, and you can choose how much of Google you invite back in. The best part is that the Google stuff doesn't get any special treatment. Which means that the Pixel Camera app and Google Photos isn't allowed access to Internet, because why should it?
The only thing that is still fundamentally flawed, are remote push notifications. And I don't mean that it's flawed for GeapheneOS, they work fine. It's flawed in the sense that information goes through Google or Apple. The privacy concerns there are significant. It's not end-to-end encrypted. You cannot avoid the problem either by disabling them on your phone. Each application, be that a Ring Camera, or backend messaging system, etc, that sends the stuff to Google through notification apis, will do so regardless of how much you sandbox or disable those services on the phone-receiving end. Conveniently, there is no effort by Apple or Google to make this core functionality any less tied to Apple or Google. The "asynchronous" nature makes it a problem that needs to be solved for each and every backend service system, for remote notifications. Some privacy conscious apps/services might let you limit what is sent to Google so you only get "New message from Hubbie" instead of also "Hubbie: remember to buy the paint for the baby-room! I'm so excited".
Anyways... Not sure why I went on such a long tangent. I was done pooping a while ago.
CalyxOS on a Pixel is as great as it currently gets. But stuff can get better.
Do you like the Pixel 8 Pro? I'm waiting to see what the Pixel 8a looks like. I don't expect a lot from my phone so I don't need a flagship, but I do value long term security updates and the 8 series has 7 years of updates.
I think the 8a, if it's similar to the 8, might be a better size. But, I'm also fairly sure be fine with any of them.
My current phone is about the 8 Pro size, and I think it's a bit too big. The 8 might be good enough, but yeah, I'd like to see what the 8a looks like before deciding.
Pixel is garbage hardware though. I'm on pixel 7 pro now and it is the worst phone I've ever had. Shit battery life, shit reception, shit processor that lags constantly, absolute shit Bluetooth chip that randomly disconnects in crucial moments when I'm on important calls or REALLY need android auto. This phone is only good at taking pictures and the fact that I get exclusive spam filtering features. We badly need another alternative.
Also fuck Google.
Really? What are you comparing it to?
The problem is that options are very limited for privacy-respecting ROMs. I honestly don't care about the camera, but I very much want to avoid both Google and Apple software nonsense, and Bluetooth is also pretty important to me.
My current phone (Moto G Power) is a piece of crap, but it's reasonably consistent in most regards. I'm interested in the Google Pixel 8a (assuming they release one), and I only want it to get GrapheneOS and a few years of security updates. I don't expect a ton from my phone (I don't play games, or use any intense apps), but Bluetooth, battery life, and privacy are very important. Unfortunately, Linux phones aren't reliable at all, otherwise I'd just go that route.
I'm running GrapheneOS on a 7 pro. Battery isn't great, but I've not had any major issues... At 44% with about 2 hours screen time and 16 hours since last charge. Downloaded a bunch of updates including a system update / reboot / optimize. Listened to a few hours of music over Bluetooth. Also forgot to shutoff location services after using the GPS last night. Bluetooth connected Garmin watch. Dual e-sim (Fi and JMP).
I normally end the day around 60%.
You might checkout DivestOS. Last I heard they had e-sim support without needing to install any of Google's software. GrapheneOS didn't have this feature when I got this phone. If its not on GrapheneOS when I upgrade next I plan to try and get the e-sim on with it before installing GrapheneOS.
add e-sim directly on GOS I actually think it is working now, think I saw something about it. worth checking out at least.
Oh that's awesome. Appreciate the heads up!
My previous phone was OnePlus 8 pro and 5t before that. Both still work more reliably than this pixel.
I did hear that Pixel 8 pro is a better phone but I don't think Tensor will ever be as good as Qualcomm's offerings.
I'm not one of the people willing to sacrifice convenience for privacy. I really like Android auto and Google pay so imnho Android phone is useless without Google services, but I agree that there are simply no good alternatives at the moment, so I'll probably get another pixel when I smash this one against the wall from frustration.
Your issues is about stock OS not hardware. And yea shit works without that or gapps.
Android auto works on GOS with sandboxed playservice.
So your "convenience" is just laziness to actually look it up.
For those who don't want the huge inconvenience of no gpay and have to use their cards. Any ROM like lineage for example with gapps on it.
I do love how you dismissed my "inconvenience" and then immediately said that one of the two things I listed is a
Looks like AA is a fairly recent addition to apps that work on GrapheneOS and GPay will never work.
I wonder if I set up GPay on my watch and then switch to GrapheneOS if it'll still work?
Yea AA works as I said. For GPay "huge inconvenience /s" Just get a case with room for your cards , issue resolved. I said it was lazy ,pointing out one small thing like that is just trying to find something to blame, imho.
But if you really want Gpay, get a ROM and flash gapps on it . Mileage may vary so check your phone and roms.
Never used watches but yea I assume it might work. Seems so, https://support.google.com/wearos/thread/215767/can-i-use-google-pay-on-a-wear-os-watch-if-my-phone-is-not-nearby?hl=en
I never used stock OS on pixels but of what I read it is a world of difference with something better on them.
I never had any issues on GOS , basically everything works even without sandboxed Google. For the few things that don't I keep it in a separate profile. (Which really is separate in contrast to stock)