Live data from Hacker News

Google Pixel 6 and Pixel 6 Pro

store.google.com

751–760 of 851 posts

Re: Google Pixel 6 and Pixel 6 Pro

#751

I think normally I'd look for the Pixel or the iPhone but my next purchase will be supporting FairPhone. When I think about how powerful I need my phone to be I don't need the best. I want something I can fix and update myself; something that's supported for more than a couple of years; something that is a little "better" for the planet. Does anybody use all of the new power of these incredible devices?

the camera app alone takes a lot of power. Carmack discusses it a bit in this article[0], but essentially Google uses a ton of software to overcome the often mediocre hardware, and the camera app is a great example of that.

[0] https://arstechnica.com/gadgets/2021/10/the-google-silicon-t...

Re: Google Pixel 6 and Pixel 6 Pro

#752
post #631

Earlier quoted context omitted.

There’s an example of it on HN front page right now, where a terminal application without privileges can trigger a kernel bug.

for those times when I run that terminal application on my phone. which is already rooted, so it's doesn't need the kernel bug to get root. it can just run.

Your phone might be already rooted, but that's not true in general, and doesn't mean that the kernel doesn't have an attack surface on phones.

Re: Google Pixel 6 and Pixel 6 Pro

#753
post #744

Earlier quoted context omitted.

Google had announced that all phones shipping with Android 11 with snapdragon chipset will be eligible for up to 4 Android OS versions (launch release + 3 OS updates) and 4 years of security updates as the result of project treble and getting Qualcomm on line. Which is more or less is inline with 5 years software support guarantee of FP.

That’s a lot of handwaving you need to do to get a tiny company to support phones beyond their suppliers intents - especially the SD660 equipped Fairphone 3. This is stuff given as the reason that Google moved away from Qualcomm for. Given the rest of their software, I don’t really trust them to deliver. I’ll happily be convinced otherwise though.

Fairphone has nothing to do with the latest announcement, It's Google's project treble and it smacking Qualcomm.

Re: Google Pixel 6 and Pixel 6 Pro

#754
post #718
post #274

Google seems to have for some reason requested a very/overly broad embargo from reviewers which does not let them show any photos taken with the device or software features for now. MKBHD mentions this (and shows nothing from the phone really) @ https://youtu.be/roWxo6jWoYw?t=140 And Mrwhosetheboss said he refused to cover these phones due to the embargo. The Tech Chap mentions he can't show anything apart from the h…

Interesting. Wasn't it the same for the last pixel? And also, MKBHD still made a video about them, why? Wouldn't it hurt Google more if he would just not cover them? Also, he regularly has Apple devices that he also has similar embargoes for and is not allowed to release stuff until the products are on the street or shortly before that - as for this Pixel. Does he always call it a red flag there too?

I think there is a difference between a general embargo not to show anything and an embargo that allows to show a few very specific things. The latter being a "show it but not really" vibe. Did Apple do that in the past? Or is it rather nothing and then everything?

Don't think he has an interest in hurting Google. But he has an interest to have some level of transparency.

Re: Google Pixel 6 and Pixel 6 Pro

#755
Ordered a Pixel 6 Pro for both my wife and I to replace a Pixel 4 and Pixel 3. Looks like a nice upgrade, very interested to see how the Tensor CPU performs compared to other flagship SOCs. The price was a pleasant surprise. Trying to order the phone was an act of frustration - that's for sure. I refuse to believe that Google, who handles more traffic than anyone else on the internet, can't create a store that can handle a bunch of people trying to pre-order this device. I ended up having to order from Best Buy after continually erroring-out during checkout on the Google Store and then finally having my items removed from my cart because they were out of stock. I also can't understand why Google limits the storage options of certain colors.

It's hard not to compare Google's event with the iPhone 13 launch event a month ago, and the wildly different strategies the companies are using to try and market their devices. Apple (rightfully so) is very proud of the performance of their SoCs and definitely emphasized that aspect - using tons of numbers and data throughout the presentation. This was also seen in the new Macbook event last week. Meanwhile, google hardly mentioned a single hardware detail and focused more on the software and user experience. I have to admit the google event felt more "hand wave-y." They may have avoided talking about hardware details in the event though since they basically revealed the phones months ago.

Re: Google Pixel 6 and Pixel 6 Pro

#756
post #741

Earlier quoted context omitted.

It is different for phones made by the people who also make Android. Google. Which is why I was specifically talking about the pixel and the nexus phones sold by google. For example, kernel version 4.9.3 - the latest one (yes, originally released in november of 2017) supports up to the latest Android. In fact, since 4.1 supports the latest Android, and will till June 2024 according to google. I'm going to go on a lim…

> So, Nexus6 released in 2014 will be able to run the latest android, fully security patched including kernel (which is not that important), till about 2026. This is getting to borderline misinformation here. Sorry to have made you dig in to this position, but please don’t call this fully patched. Qualcomm abandoned the Snapdragon 805 in the Nexus 6 in 2017 (maybe even 2016), and no updates to that platform's kernel…

[deleted]

Re: Google Pixel 6 and Pixel 6 Pro

#757
post #535

Earlier quoted context omitted.

That’s all great - but don’t lure people too much into a false sense of security. While your Nexus 6 may run a shiny new version of Android, underneath it runs a crusty old 2017 kernel full of holes of different sizes. The community is great, but vendor support remains important. LineageOS and other projects can’t fix things in kernels they can’t compile - they can only provide security updates for open source compon…

Alright - I'll bite. This is a smartphone, not a windows PC with a bunch of services. There is Zero listening on any port. There is no attack surface for any kernel - the only thing there would be a bug in mms. Please share your source for kernel attacks, on any android version, that's not an attack on an app - but on the kernel. No, this is not a google play attack, or an attack on an outdated app - which are update…

I'm not sure I'm the one confused here. Not really willing to get combative on what security priorities one should have, but I'll stick to mine.

> I had my nexus6 on kernel 4.9.3.

I find this very hard to believe, as no evidence of Nexus 6 kernels that are not Google's original 3.10 shipped exists that I can find. Even PostmarketOS that looks to update kernels links to LineageOS fork of the 3.10 kernel on their page for shamu/Nexus 6.

Unless you mean a custom kernel from "some guy on XDA" that names itself 4.9.3 like this one - which is just kernel 3.10 with some branding on it. It says so right in its description: https://forum.xda-developers.com/t/kernel-sm-4-9-3-o3-graphi... . Kernel 4.9.3 is a weirdly specific point release to be on in modern times anyway - there's kernel 4.9.0 all the way up to 4.9.287 - so it'd definitely be oddly specific if that's what you had.

Outside of valiant community efforts like Replicant and PostmarketOS, who have an extremely hard time getting working or feature complete kernels running, Android devices getting new kernels is almost unheard of. Even with vendor support. Community ROMs have to stick with what the vendor gave them to have a functional device.

Re: Google Pixel 6 and Pixel 6 Pro

#758

Earlier quoted context omitted.

Bit larger yes, just under 1oz heavier... not too significant. And headphone jack, no notch (dealbreaker in 2021), no CSAM.

A notch just makes the screen slightly smaller. Why is that a dealbreaker when you're already asking for a smaller phone?

Apple dragging out the notch removal as long as possible. When they finally do (next year?), notch devices will look/feel like old trash.

Re: Google Pixel 6 and Pixel 6 Pro

#759
post #525

Earlier quoted context omitted.

There's one thing that's handy about having it on the front, which is that the phone doesn't have to be picked up to unlock it. It's quite nice being able to read a message on my phone without picking it up from my desk. But on the other hand, it is definitely more comfortable unlocking it from the back while holding it. Maybe phones should have both!

Would be neat if there was a way to set the phone to stay unlocked for as long as it is stationary.

Hmm...I thought that was an option...but nope...longest screen timeout I can set on my Pixel 3 is 30 minutes.

Re: Google Pixel 6 and Pixel 6 Pro

#760
post #576

Earlier quoted context omitted.

It was an obvious generic tangent into an obvious flamewar topic. I realize that details like that can be activating, but in this case it was a clear swerve into offtopicness. This is not a borderline call! Offtopic swerves can be fine when they're interesting and unpredictable, but classic flamewar swerves are the opposite of that.

It wasn't. He was simply stating what he saw and why that made him uncomfortable. It wasn't even remotely off-topic. This is a RELEASE banner/promo website for the product. He discusses that. It seems just like censorship, and that's cool. I understand the requirements to keep narratives flowing. But we'll all end up in an echo chamber, unable to admit when we feel like something feels wrong. You keep using words lik…

We don't care about "narratives" - we're just trying to have an internet forum that doesn't destroy itself in the obvious internet ways, and the principles of how we try to do that are well-established. As I said, this wasn't a borderline call.

If you familiarize yourself with the rules (https://news.ycombinator.com/newsguidelines.html) and the moderation practices here (https://news.ycombinator.com/threads?id=dang), you'll soon see that they're applied pretty consistently and don't favor any narrative nor any particular issue position. It's common for people to feel like the mods are biased against their view when they see a comment that they happen to agree with getting moderated (https://hn.algolia.com/?dateRange=all&page=0&prefix=true&sor...), but this is just a cognitive bias—a form of sample bias, in fact, because those cases always stand out more (https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...).

The problem with changing the subject from the original topic (the new phone) to a generic flamewar topic (race grievances) is that the latter tend to quickly take over a thread and to quickly lower comment quality. In that respect, they are like flames—they spread quickly and consume everything—so "flamebait" and "flamewar" are good words for this.

> I realise you are now attempting to delete his comments

I haven't deleted anything. If you're referring to https://news.ycombinator.com/item?id=28921996 being marked [flagged] and [dead], that's because users flagged it.

It's really easy to jump to conclusions about this kind of thing, which means it's best to hesitate and sift through what you've actually observed vs. what it seems-like-it-absolutely-must-be, because the latter is usually a misinterpretation. This applies to all the moderation practices here. For example, if you see a post getting moderated and conclude that we must be opposed to the views expressed in the post, that's a big non sequitur. We moderate posts with the opposite views just the same way, when they break the site guidelines.

You can disagree with the guidelines and/or refer to moderation as censorship if you like—people differ about such things. Nonetheless the HN guidelines are the rules by which this site operates (we're not trying to impose them anywhere else!) and, agree or disagree, users here need to abide by them.

Post reply on HN