I Do Not Recommend Google Hardware | Hacker News Reader

I Do Not Recommend Google Hardware

xn--gckvb8fzb.com

18 pointsingve11 comments

If you’re a tech power-user, however, maybe consider Linux on mobile as a more radical alternative. I’ve been eyeing postmarketOS on the Fairphone 6 for a while, as it appears to be making meaningful progress, but it is not yet a daily-driver experience and probably won’t be for another year or two.

Hmmm, if you do not want to use Pixel for hardware issues, Fairphone is probably not going to be your best replacement. The Fairphone 6 has suffered from an issue where they die during charging, even on brand-new devices. People also encountered issues like the volume buttons breaking after just a few weeks/months (for which they don't sell replacements). Replacement of a FP6 under warranty often takes 1-2 months. And you cannot repair it yourself if they don't sell the parts that most commonly break (logic board and volume buttons).

I wish Samsung made an S-variant (or A5x) that passed all the GrapheneOS requirements. It's really stellar hardware (if conservative). I know it will never happen, but one can dream I guess.

I'm writing this on a Pixel 8 and it's the worst phone I have ever used. The wireless chip is basically dead. And the battery can't make it to 3pm. Annoys the hell out of me that so many reviewers I thought I could trust speak so highly of this phone.

It is surprising that many Android review sites always rave about Pixels. I have one because I love and run GrapheneOS, but outside the camera, the hardware is pretty mediocre. The 9 and 10 is a lot better than previous iterations because they moved to a newer Exynos modem, but real-life battery life is still bad compared to even Samsung [1]. Tensor is still an ok mid-range chip, but nowhere near Snapdragon 8 Elite Gen 5 or even Exynos 2600.

After release, Pixels are really overpriced for what they are. It gets much better after ~6 months, when they are typically discounted ~250 Euro. But then you have similar discounts on Samsung S-series after only a few months.

I am happy that Motorola is being added to the GrapheneOS mix, there will be more interesting hardware to choose from.

[1] I am taking Samsung as an example, because many Chinese vendors have even much larger capacity batteries.

Is there even an option in the Android space that isn't entirely filled with Bloatware? I've always hated the Samsung Android skin so I've mostly written off the rest of the market

Nothing Phone comes probably the closest to bare bones at least what I have come across.

They started pushing lock screen ads. The retracted this on some models after huge community outcry, but typically there is no way back once a company goes down that route.

If you are considering Nothing, you might as well go for Samsung and uninstall all the bloat from the user profile with adb/UAD. It will at least have a separate secure processor (Knox Vault, IIRC even recent mid-range A5x) and not a TEE that runs on the main CPU and is vulnerable to side-channel attacks. And the SoC (at least if Exynos and I believe the latest Snapdragon 8 Elite) supports MTE, which Samsung is rolling out support for in OneUI 9, etc.

Going from a Pixel to a Nothing Phone is like going from a modern iPhone to an iPhone before the 5s in many ways security-wise (the first iPhone with a secure enclave).

But yeah, despite the hardware issues, Pixel with GrapheneOS is still your best bet for a vanilla, secure Android.

Graphene on a pixel is the most lightweight ROM

I think the Nexus 4 is still my favourite phone I've ever owned. Maybe it represents a period of techno-optimism I had, and how my relationship with phones have changed over the years. Now I despise my phone but am required to own it for my digital ID to pay taxes, receive work messages, etc.

Sounds like I've been very lucky with my Pixel 4 and 7 that I haven't had any hardware issues while running GrapheneOS.

The Nexus 4 back glass was so awesome.

https://commons.wikimedia.org/wiki/File:LG_Nexus_4_back_glas...

Another reason I'm so incensed that Google bought Fitbit. Every Fitbit I had prior to the Google acquisition worked extremely well and had battery life in the 5-7-day range. My favorite was the Sense which was basically a full (but svelte) smartwatch + full fitness tracker.

Now: just overpriced crappy Google hardware that lasts 12 hours because of AI and who knows what else they shoved on there.

And nobody else makes anything close to what Fitbit made...

Garmin smart watches are great. They last for days or weeks depending on the model. E.g. my Fenix 8 AMOLED lasts 7 days with the always-on-display on or 14 days with raise-to-wake for the screen. The MIP solar versions can last 3-4 weeks with their screen always on (depending on how much sunshine).

The more expensive models have map support. And the maps are not Google/Apple Maps, which are crappy for hiking/cycling, but they are full offline openstreetmap-based topo maps. And the best thing is you can install your own maps and there is a large community making custom maps for mountainbiking, horseback riding, cycling, hiking, etc. For instance, on my Fenix I use Garmin's TopoActive maps, along with a community overlay that adds the Dutch cycling network.

Also, if you care about privacy and do not want to use Garmin's apps to sync with your phone, you can either connect the watch and copy the data to your computer, or you can use GadgetBridge to sync with your phone (GadgetBridge is open source).

Another really cool feature is that you can control almost all models fully with buttons (except models like Venu X1), which is extremely handy when you are e.g. cycling. Or when it is cold or raining.

Reply on news.ycombinator.com