FairPhone 4 not only promises 5 years of android software updates but also has 5 years of warranty, There are more reasons to trust their words than any of the other phone manufacturers.
• They are not profit focused but rather towards sustainability, They have been delivering their promises consistently for 8 years and so it's not an idealistic vaporware.
• They produce the most repairable smartphone using components sourced from conflict free areas. Parts for repair are available directly on their site, Parts for FairPhone 1 are still available.
• Their factory workers get living wage bonus, Of course do not employ child labor while preaching humanity.
• They have first class support for alternate operating systems i.e. We are the owners of what we buy; So support from alternate OS like Linux, Sailfish or even android ROMs like LineageOS could exceed even the official 5 years support.
FairPhone4 hardware is competent enough for average daily use, Only drawback I see is that the phone is available only in Europe. Then again Google Pixel phones have been notorious for being available in only couple of countries.
The Pixel site sets the language based on geography and does not allow changing it without changing the region, which comes with a warning about delivery and currency conversion.
One of these makes me feel understood and accounted for as a potential customer, the other makes me want to CTRL+W and move on.
I am aware that this doesn't affect the majority of people. That doesn't make it less frustrating that Google keeps doubling down on this with many of the things they do.
To be fair, Google likely knows what you had for lunch and so it decides which is the best region for you; Trying to change it is an edge case /S.
What I don’t understand about Fairphone is how they will deliver these updates. Fairphone, like others, uses Qualcomm chips. Qualcomm supports their chips only for three years (four years for recent ones, but not the ones FP is using). This is what held Google back to ship reasonable security updates on Pixel devices so far. How can a small company like Fairphone convince Qualcomm to make more updates if Google couldn’t? Or will they just end up shipping incomplete security updates, like a community project?
Which is more or less is inline with 5 years software support guarantee of FP.
Given the rest of their software, I don’t really trust them to deliver. I’ll happily be convinced otherwise though.
Edit: Checked their shop and now says Out of Stock: https://shop.fairphone.com/en/fairphone-3-plus
You might have gotten unlucky on timing right at the end of orders.
I'm not mad, but it is obvious to me that they had no capability or intention to fulfil my order and were just hanging onto the €. They also sent me an email (before I cancelled) saying I could turn my current order into credit for a v4 preorder.
I am NOT spending $900 on a phone.
The camera is also a big draw of the Pixel phones. I think it might be a long while for open source and commodity hardware to match top smartphone cameras.
On the page it says on the 12th footnote, "Feature drops for at least 3 years from when the device first became available on the Google Store in the US. Your Pixel will receive feature drops during the applicable Android update and support periods for the phone. See g.co/pixel/updates for details."
On https://support.google.com/pixelphone/answer/4457705 it says, "Guaranteed Android version updates until at least: October 2024" and "Guaranteed security updates until at least: October 2026" for Pixel 6 and Pixel 6 Pro
So they hypothetically could extend it to more than 3 years of feature updates and 5 years of security updates with the nebulous "at least" wording.
Although, after 1-2 year, the features get a bit thinner because a lot of the newer features rely on new hardware that the older phones don't fully have. Sometimes they try to make it work, like how Astrophotography was available on older pixels but didn't work quite as well as on Pixel 4. But in general, they probably put the "at least" because it's hard to guarantee that a feature in 5 years will be backportable to Pixel 6.
With that said, open source ROMs don't take advantage of some features such as the Tensor SoC, and therefore the camera stops performing so good.
From their FAQ:
Why are older devices no longer supported?
GrapheneOS aims to provide reasonably private and secure devices. It cannot do that once device support code like firmware, kernel and vendor code is no longer actively maintained. Even if the community was prepared to take over maintenance of the open source code and to replace the rest, firmware would present a major issue
One can always switch to a different ROM I guess.
But also, it has a good hardware ISP that will also improve image quality by itself.
For more info: https://twitter.com/GrapheneOS/status/1450746282176303107
Both Android vendor and Apple hardware continue to work long after the software has become "outdated". That hardware does not die when the software becomes "obsolete". The vendor may choose to ignore this fact in the interest of sales but it does not mean that authors of applications must ignore it as well.
The third factor besides the vendor and the authors of applications are the operating system authors. With older PC-like hardware, I can run the latest versions of NetBSD. Forever. I update when and if I decide it is time. x86 has its benefits. It is sad that these pocket-sized computers called "smartphones" are so inflexible.
A non-HN reader recently told me that the "tech" industry has turned us all into "beta testers". The entire "updates" concept needs a serious examination. Updates are not a substitute for quality control.
With open source software for PC, in many cases we (users of open source OS) have the choice to install any version we want. Sometimes I need to I run older Linux programs with older versions of system libraries. We can download these older versions of libraries and programs from an FTP sites or websites that provide a simple directory listing, an "Index of" page.
With pocket-sized computers called "smartphones", instead we (users of open source OS) have to contend with "app stores". The author publishes a new version and all older versisons "disappear". This lack of choice may be suitable for some users, but may not be suitable for every user, i.e., "one size fits all".
- APKMirror: https://www.apkmirror.com
- Aptoide (requires app store download, stick with "trusted apps" for security): https://aptoide.com
Also, Aurora Store lets you download older versions from the Play Store through the "Manual download" menu option. You'll need the "version code" (different from version number) of the app version you want to download.
Failed to load the deno.land standard library docs just last night while I was watching TV.
Still not going to buy a new iPad though.
Yes I'm aware of WKWebView and how it's not the same as Safari. I'm using the classic meaning of browser skins, dating back to browsers like Maxthon which were wrappers over Trident in exactly the same way.
It's similar to complaining about other basic features of iOS IMO (like complaining there's a default settings app or that iOS just works a certain way).
Think of Safari as a skin that's unbundled from the engine. While Chrome or Firefox are reliant on Apple to update the engine, so is Safari, but neither are reliant on Apple for other functionality that they want to implement that users can take advantage of.
IMO it's modular enough.
It would be nice to have 8 years of security updates and 0 years of feature updates, instead. I always dreamed of having the option to only have security updates on my OSes...
1. Spam call screening is nonexistent on the iPhone, and T-Mobile's blocker still lets a ton of them through. In my prior experience Google did a much better job in this department. It would be nice to pick up the phone without a 90% chance of an annoying spam call.
2. Speech to text on iPhone makes a lot of mistakes and Google's latest update looks like they've widened the gap even more. I don't want to handle my phone to text while driving, and when the interpretation is wrong it requires extra keystrokes to try again, correct it, or type the message if urgent. This is unsafe.
3. I find FaceID annoying, and after replacing the iPhone screen because I cracked it, FaceID got noticeably worse. With a fingerprint I can have the phone unlocked before I even pull it out of my pocket, especially these days when we have masks on.
Plenty of other sexy features like camera and the customer service line feature are very nice to have, but in my opinion these are major benefits in terms of everyday usability. The overall integration across services is just smoother too, in terms of flows like email -> calendar -> google maps live traffic, or email -> boarding pass QR code. I am and will always be a PC user so I don't benefit from those integrations with Apple products.
Making the switch will require ditching Airpods and the Apple Watch, but I think it might be worth it for me.
But on the other hand, it is definitely more comfortable unlocking it from the back while holding it.
Maybe phones should have both!
I've been saddened that Google keeps the Spam filtration feature locked to the Pixel devices. It is a KILLER FEATURE.
And for STT - that "just works" 95% of my time that I use it with common vocabulary.
The hardware has failed me a couple of times - sudden battery failure, and battery cable tearing with a reasonable, slight fall - though so consider one of the warranty options.
Why would anybody share killer features with competition ?
I have the pixel 4 which has face id. I loved it for the 6 months that I had the phone before we all started wearing masks everywhere. Now it's a completely useless feature.
I always thought iOS had better, higher quality apps, and in some areas, that's true - Procreate for art, first-party games, etc. But I miss powerful, functional apps. I love the way Moon+ Reader tracks every single reading session, time spent and WPM. And nothing on iOS comes close to Smart Audiobook Player, although Bound is decent.
My iPhone is a great phone and a poor computer, whereas Android's MiXplorer and Termux empower me to, in a pinch, do whatever I need to do. iOS's best equivalent apps consistently fail to copy files over SMB or SCP (they get killed in the background or just fail), while Apple's Files app can't even write to my writable SMB share that works everywhere else.
In short, while my iPhone wins on battery life, speed, and support, the Pixel (and by extension Android) beat it in power and freedom. Perhaps this all proves that Android suits the needs of this power-user and tinkerer better.
More accurately put, their intent is to scan cloud photos for exact matches with known child pornography material (like every other cloud provider, including Google), and then have the case reviewed by a human only after multiple positives, and only then forwarding the case to law enforcement (based on photos you chose to upload to the cloud)
corrected: their intent is to scan all photos in your photo library, on your device, including images automatically pulled in from from various sources such as messages, if you have iCloud Photo enabled.
As far as I am aware, this is false and there is no mechanism on iOS by which images are "automatically pulled into" the photo library from anywhere, Messages or otherwise. Do you have a source or an example of how that could happen?
(edit: people are mentioning Whatsapp, which I guess has an option to auto-save received photos. Fair enough, but that's a third-party app and requires you to enable photos access anyway, so it's pretty clearly not what the parent meant).
> their intent is to scan all photos in your photo library, on your device ... if you have iCloud photos enabled
Yes, that's what I said. Enabling iCloud photos uploads your photo library to the cloud, so it's scanning your cloud photos.
Per Apple [0]
>Shared with You works across the system to find the (...) photos, and more that are shared in Messages conversations, and conveniently surfaces them in apps like Photos (...) making it easy to quickly access the information in context.
---
>Yes, that's what I said. Enabling iCloud photos uploads your photo library to the cloud, so it's scanning your cloud photos.
Being disingenuous about it is still a thing though. You stated
> More accurately put, their intent is to scan cloud photos (...) (like every other cloud provider, including Google)
which makes it appear that the photos are only scanned server side "like every other cloud provider". Client side scanning is something that no other provider does, in contrast to what you stated.
[0]: https://www.apple.com/newsroom/2021/06/ios-15-brings-powerfu....
I was not being disingenuous, frankly. I said that Apple is scanning your cloud photos, i.e. they are scanning photos that are uploaded to the cloud. Photos not being uploaded to the cloud are not scanned. I made no claims about where the scanning is happening, and I'm not particularly sure why it matters in any material sense.
Still: they scan photos locally - those are not cloud photos, those are local photos. And they have deployed the technical capability. You can bet that once capability exists, they will bend to government demands - there's ample precedent for that.
SO, yes, Apple, unlike all others, scans your photos locally. If they are going to be uploaded to cloud, or if they are forced to.
They are cloud photos. I say that because:
1. The photos are in the process of being uploaded to the cloud when they are scanned
2. The result of the scan is attached to the photo only when it is uploaded to the cloud. If the photo is deleted from the cloud, or the upload is canceled, the scan result is discarded
Practically, the system works precisely the same whether or not the scanning happens on device before the image reaches the cloud, or on the server after the image reaches the cloud.
The only well-intentioned argument about why on-device vs. on-server scanning matters is that "slippery slope" argument, which presupposes that:
1. Apple putting this scanning code in iOS not only somehow makes it easier/more tempting to use it for non-CSAM, but all but guarantees it will be used for non-CSAM.
2. Apple does not already have the ability to run whatever code they want, on any of your devices, without you ever knowing
3. Apple folds very easily to government demands, especially when it comes to privacy, their core differentiator
I don't think any of these are true. You might think they are, but then I'm not sure what point there is in discussing any more.
> or if they are forced to.
I'm not sure what this implies. If someone forces you to upload a photo to the cloud, surely that will get scanned regardless of whether the scanning is performed on-device or on-server?
Therefore, the scanning is local. There's really nothing more to it: The distinction is based on where the input is read from, in addition to where the input is processed. Both are happening inside the phone while you hold it in your hand.
It is scanning images locally.
This is totally unacceptable, and should never become acceptable.
This is what I don't understand about the whole argument about this CSAM debacle. I've read quite a bit of the discussion about this, as I'm someone who takes privacy fairly seriously, and it never really gets discussed. Could someone maybe point me in the direction of some literature about this? Is someone doing extensive load and packet analysis? Don't they(Apple) upload at least some E2E data?...
My iPhone already does an insane amount of "indexing", including image classification. This is all under the hood and I have no idea what else its doing, for all I know its mining Monero. Additionally all my iOS devices seem to send an inordinate amount of data to the cloud; I'm particularly sensitive to this because I don't have a strong internet connection, and frequently have to turn off WiFi on my phone or iPad when playing online games to stabilize my ping.
I'm also skeptical that you can really insure privacy from a 5 eyes country. Maybe I just read too many spy novels as a kid, but it doesn't take a lot of imagination for me to guess how any given decently large western company could be completely infiltrated by a multinational espionage coalition.
Idk, I tend to like that Apple is fighting against Ad-tech, as that power dynamic is at least believable. I do think that playing around with deGoogled Android is fun and in my experience is much more suited to dropping off the cellphone grid. I have an Android running Lineage and microG and with OSM and Kiwix(wikipedia is indispensable, IMO) as well as a handful of other apps, it serves the majority of the purposes of a cellphone without the need for data. I still daily drive my iPhone, mostly because the UX is a lot better than deGoogled Android.
Now if Apple developed a special update that they sent to only a few choice targets, that might be able to go under the radar.
You can wrap intrusions in form of 'think about the kids' (what is used here), think about security/terrorism and so on. This playbook has been used ad nausea, isn't it about time to learn?
That was my point: they get caught if/when they try.
If _Apple_ are forced to (e.g. by a judge), and they can't claim the ask is technically impossible.
But yes, I agree with the comment, there's no reason to hide between details: Apple plans to introduce the capability of scanning photos on your local device and comparing hashes against an opaque (non-reviewable) list of hashes that they (along with governments) control (details about how they plan to initially employ this capability are irrelevant).
What no one has done before and what I totally don't accept is someone scanning photos on my device, which is what Apple is doing.
The in the cloud vs. on your device aspect of this debate is the most important part and cannot be glossed over.
I really do think it's a weird aspect to fixate on, though.
So long as Apple is only scanning the photos that're being uploaded to its servers, it genuinely doesn't matter to me where that scanning happens. It's a scan that could have happened in either location, and the version where it's happening locally is arguably more private/secure-from-fishing-expeditions. If I don't like that the scanning occurs, I can disable the uploading.
The distinction would matter if the local-scan involved things that weren't being uploaded. But it doesn't, so from my perspective the only difference is an implementation detail.
You can already do that today (I do).
> But it doesn't
Maybe, maybe not. Even if I were to trust Apple 100% it's again a matter of principle (no local scanning).
Imagine the uproar if Microsoft Defender (which comes in-box enabled-by-default on all Windows 10/11 PCs) were to suddenly start scanning photos (it already scans executables and Office documents), hashing them against some opaque "database" and attaching tokens to suspicious ones that would be analyzed when uploaded to OneDrive (again, enabled by default for your Documents\Photos on Windows 10/11 if you use a MS Account).
Then on top of that, imagine Windows was a walled garden a-la iOS and you couldn't uninstall / disable / replace Defender with a different tool (which you totally can today).
I think there would be massive outrage in the press with MS being dragged through the mud for months, and droves of users switching to alternatives (like Linux) overnight. Yet (except for a few privacy / freedom organizations and a little press bleep) Apple gets to shake it off scot-free; I don't understand the dissonance.
If you want to "correct" the claim to say their intent is to scan every photo, citation needed.
Google, on the other hand, has been scanning the entire contents of your account for the past decade.
>a man [was] arrested on child pornography charges, after Google tipped off authorities about illegal images found in the Houston suspect’s Gmail account.
https://techcrunch.com/2014/08/06/why-the-gmail-scan-that-le...
However, Google is scanning everything in your account.
We recently had a thread from a historian whose entire account was suspended after Google scanned all the files in his Google Drive, and didn't like what they saw (files on the history of tanks).
https://support.google.com/accounts/thread/81988101/google-l...
If you want your photos to upload in the background, iCloud Photos is your only choice on iOS. Not so on Android. This makes backing up photos to a server privately on iOS essentially unusable.
This kind of crippling anti-privacy pro-Apple-profits design permeates iOS. You cannot even install an app on your device without giving Apple your billing details and letting them know you installed it, which is used for ads. You cannot get your location without also telling it to Apple. You cannot tell Apple not to track your WiFi SSID's location. You cannot uninstall Apple News, which is filled with user tracking for ads. On and on.
> We recently had a thread from a historian whose entire account was suspended after Google scanned all the files in his Google Drive,
You're comparing iOS to the wrong entity when you compare it to Google instead of Android, but even your comparison to Google is faulty. Your link is about Google suspending an account for files shared publicly, not about Google scanning all the files in that account. Section V.B. of https://www.apple.com/legal/internet-services/icloud/ says that sharing those types of images publicly is also a violation of the iCloud TOS, and Apple has the right to do the same thing. The difference is that Apple will probably handle the customer complaint better, but that is an issue of customer service, not privacy.
Nope. Background App Refresh has allowed any iOS app to update data between the server and client in the background for more than half a decade.
Apple has discussed scanning photos uploaded to the iCloud Photos portion of their cloud service in the future, but nothing is scanned now.
Google has been scanning everything in in their user's cloud accounts for the past decade.
Also, given Google's reluctance to pay human beings to supervise decisions made by their algorithms, I have zero doubt that Google is turning in users when they have a single false positive.
All the other privacy-invading criticisms remain, making iOS an awful choice for privacy.
I still don't know why you're comparing iOS to Google. As I've already explained, that is the wrong comparison. I can use my own services on Android. Apple is planning to scan photos in iCloud (and already does in mail) and only hasn't because their services are still so basic, so it is just as bad as Google in that respect but only temporarily better due to incompetence. My own server does not scan and review photos and never will.
I guess I could have said almost a decade ago.
So, again, Apple only discussed scanning the iCloud Photos portion of their cloud service some time in the future, but NOTHING is being scanned now.
Google, on the other hand, has been scanning everything in your account for the past decade.
Also, documents from the discovery phase of Google's various antitrust trials show that Google has literally pressured device makers to hide the privacy settings from users.
Google also buys a copy of everybody's credit/debit card transaction data so they can spy on your real world purchases as much as they spy on your online life.
A company with surveillance capitalism as it's business model, like Google, will always be motivated to violate user privacy as much as possible.
I don't know why you're still trying to pretend that Google's cloud service is separate from Android while Apple's cloud service is not separate from iOS?
I acknowledged that. The point is that they admitted this is an oversight because they are already scanning iCloud Mail. Their intentions are exactly the same as Google's. They are merely less competent. Apple is also a surveillance capitalist, as I explained in my previous post, giving several examples. iOS even splits the privacy settings of Apple's apps from the privacy settings of all other apps to make it harder for users to control what little Apple lets them control.
> Google also buys a copy of everybody's credit/debit card transaction data so they can spy on your real world purchases as much as they spy on your online life.
Apple gets the exact same information for transactions completed with Apple Pay. Users have to opt in for Google to see this information. Once again, exactly the same.
> I don't know why you're still trying to pretend that Google's cloud service is separate from Android while Apple's cloud service is not separate from iOS?
I already explained why. I don't have to use Google services on Android. iOS ties me to Apple's privacy nightmare. I listed several other examples of Apple data collection on iOS that are unavoidable. Android, even in builds provided by Google, has none of those problems.
Nope.
>Google has been able to track your location using Google Maps for a long time. Since 2014, it has used that information to provide advertisers with information on how often people visit their stores. But store visits aren’t purchases, so, as Google said in a blog post on its new service for marketers, it has partnered with “third parties” that give them access to 70 percent of all credit and debit card purchases.
https://www.technologyreview.com/2017/05/25/242717/google-no...
Buying a copy of everyone's credit card transaction data, no matter who they bank through, is not even close to the same.
>I don't have to use Google services on Android. iOS ties me to Apple's privacy nightmare.
Nope. Apple's cloud service is every bit as optional as Google's.
The difference is that Google has been scanning everything in Google accounts for the past decade.
Google and Facebook, as the pioneers of surveillance capitalism, are both privacy nightmares.
Yep.
> Buying a copy of everyone's credit card transaction data, no matter who they bank through, is not even close to the same.
As I already explained, the user has to opt in to share that data with Google. The purchase is a deal with the credit card companies to send data that users have opted in to share. https://support.google.com/googlepay/answer/10845853?hl=en
> Nope. Apple's cloud service is every bit as optional as Google's.
You completely ignored my post explaining why they are not. To repeat myself from https://news.ycombinator.com/item?id=28933939:
"You cannot even install an app on your device without giving Apple your billing details and letting them know you installed it, which is used for ads. You cannot get your location without also telling it to Apple. You cannot tell Apple not to track your WiFi SSID's location. You cannot uninstall Apple News, which is filled with user tracking for ads. On and on."
Apple, Google, and Facebook are all privacy nightmares. The difference is that iOS forces that privacy nightmare on its users, while Android does not. Your comparison of Apple to Google is as irrelevant as it is incorrect.
As I have already explained, this has nothing to do with Google Pay whatsoever.
It doesn't matter who issues your card. Google made deals directly with Visa and Mastercard to buy your transaction data.
>as Google said in a blog post on its new service for marketers, it has partnered with “third parties” that give them access to 70 percent of all credit and debit card purchases.
Google has gone from spying on everything you do online, to spying on your offline behavior as well.
As for the rest of your errors. I'm afraid that I'm not willing to take the time to correct them individually.
That is about aggregate purchases, which have no privacy implications at all, not about individual purchases, which need to be matched either by email or by users opting in to share their credit card transactions, which is exactly the same as Apple Pay.
> Also, how exactly do you use the Google Play Store without having a Google account?
You don't have to use Google Play to install apps on Android. Even if you use Google Pay, you don't have to completely de-anonymize yourself with billing details.
> I'm afraid that I'm not willing to take the time to correct them individually.
More like you're afraid that you cannot correct them because they are already correct. I have made those claims hundreds of times on this forum, and they have never been corrected.
You have simply fallen for Apple's marketing without critically thinking about what data Apple actually collects, and the embarrassment of overpaying for an ecosystem that is clearly worse has understandably caused you to become defensive. The takeaway is to not trust marketing and verify if what the marketing actually claims is true. None of these companies are looking out for you. If Apple can make more money by exploiting your privacy on top of getting you to pay more, they will do it, and they are doing it (why actually make a privacy-respecting product that ties Apple's hands when they can just have the marketing department claim that it's a privacy respecting product and have their cake and eat it too). The only reason Android has gotten away with less user exploitation is that Google is still not yet as top-down driven as Apple, so the hackers who work on Android can influence how the base system is made while just enabling the company's services teams to build what they want on top of that instead of directly into the base system, and the only reason Google still lets them get away with that is that Android initially had to be released as AOSP + vendor bits in order to bring other companies into the ecosystem, and it is now too expensive to change course.
Spying on everywhere you shop no matter which bank issues your card has no privacy implications at all?
Sorry, but at this point I can't take you seriously.
It's literally the headline of the article I've posted three times now.
Connecting purchases to your user profile has nothing to do with aggregate data and everything to do with spying on individual users for a profit.
I suppose it's also Apple's fault that Google pressured device makers to hide the Android privacy settings, and ignored users when they turned off the setting Google told them would stop Android from tracking their location?
It might be Apple's fault that you believe I said that. Try reading my comments on an Android phone, which gives you a choice of multiple working web browsers instead of just different skins of the same buggy browser engine.
> Google pressured device makers to hide the Android privacy settings.
That's funny. The privacy settings on Android are more easily accessible than the privacy settings on iOS, and they apply to all apps, not special-casing Apple apps like iOS does.
> ignored users when they turned off the setting Google told them would stop Android from tracking their location?
You're talking about two different settings in two different Google apps, not in Android. The really faulty thing is that there is no way to prevent iOS from sending your location to Apple at all unless you don't get your location on your iOS device at all.
You keep trying to compare iOS to Google and failing. The correct comparison is iOS to Android, where iOS fails badly.
Apple claims to not scan your pictures, but that's unrelated to whether they scan your pictures
You either believe their corporate communications on the subject or you do not.
In reality they probably have a "photoscanner.so / .dylib" that currently is only linked in by the iCloud uploader thing, but at any time could be called in by any other part of the system (or offer exploits new avenues for data exfiltration), which was actually spelled out in their initial announcement (there will be a system API for accessing it).
So they absolutely have the ability to scan photos on your phone; the fact that they don't intend to currently use it outside of the iCloud uploader is totally immaterial to this debate (the thing I don't want on my phone is photoscanner.so or any such capability).
That is completely false. They announced, a week after the initial announcement, that the on-device nudity-detection they planned on implementing in iMessage would also be open to Snapchat and other messaging apps. That doesn't report anything to the police, isn't hash-based, and is done on-device; it just pops up a bypassable warning to allow child users who are part of "iCloud Family Sharing" to avoid seeing things they don't want to see. It has nothing to do with CSAM detection.
I continue to be frustrated by the amount of misinformation on the anti-CSAM scanning side of the debate, including on HN (and it's orders of magnitude worse everywhere else).
Come on, now you're really going off the rails. What we're discussing here is the system Apple has said they have implemented and described. Anything beyond that is hearsay and accusation, for which some evidence would be appreciated. If you're just going to believe whatever you want to, and damn the evidence or what anyone says, go ahead. There's nothing much more to say.
Not exact matches. Hashes. Hashes that were quickly show to have collisions that the company brushed off.
On page 10 of the paper I linked though, they state that they assume a false collision probability of 1/million, which is more conservative than the 3 in 100 million false collisions they saw in their tests. The way they chose 30 as the threshold is based on the safeguarding assumption that everyone's photo library is larger than the actual largest library. This is safeguarding because the more photos you have, the more likely you are to have collisions. Copying from my previous comment, we can compute their photo library size assumption by solving for N in this equation: 1/trillion = 1 - sum_{k=0}^{29} of (N choose k) (1 - p)^k p^(N - k), where p is 1/million (the probability of a false collision).
With Google you can be absolutely sure that their intent is to eat all your personal information and data for short-term profit. With Apple it was "just" a stupid attempt at legal (over?) compliance.
Want to update Google maps home/work addresses? Too bad, requires web/app tracking enabled.
That "web and app tracking" applies to apps both on iOS and Android. The difference is that Android gives you more choice about what services you use.
Its not the law enforcement that's the main issue, but various greedy 3-letter agencies who are already well known to have ambition to have profile on every person in this world (not unlike Facebook but for different purposes).
This is not privacy anymore no matter how you bend it, it has been cancelled and Apple realizes this very well. And it still doesn't care. Literally the only serious selling point for many new buyers not invested in ecosystems, blowing it off with a nice double barreled shotgun shot.
I don't trust them not to jump to conclusions with a 256x256 (the exact quoted resolution escapes me at the moment) image at their disposal.
Full E2E encryption is going to trigger nightmare "I lost all my photos" customer-service stories when people forget their passwords... which is acceptable when you deliberately signed up for a service where security was the selling point, but not great for someone who bought a mass-market phone.
And you can either choose between (a) someone having to see your photos or (b) relying on an automated but imperfect process. You have to pick one.
Which includes them scanning your photos for CSAM.
Good, descent people, waking up screaming, cold shakes, permanently damaged from what they could not unsee.
You couldn't pay me enough to go through images of such sickness.
Outside of all the yes/no, on/off phone stuff, how are they going to hire, and keep staffed, a department of people having to look at this stuff.
How are they going to insure it?!
Try getting that behavior from Google, a company who's existence is dependent on surveillance advertising.
Also who is reviewing this known child pornography list? Hopefully nobody because it is Child pornography but also hopefully somebody because what if somebody slips something in there… Say a offensive political cartoon or a ethnic group symbol or a picture of Tiananmen Square. This list of “offensive images” needs to be auditable.
Also it is crossing a line in the sand because it is on your personal device not in their servers. All you can hope for is that they don’t alter the deal further.
Seconds after they scan it the files will be on their server, right?
For some definition. Russia's FSB might have a very different idea of what this is. Anti-Putin memes, for instance. Navalny support materials or brochures. You'll have to watch what you download, because your phone might upload it and incriminate you.
Or China's MSS. Winnie the Pooh, Tiananmen Square, Free HK, etc.
Or even the FBI. Financial or political leaks, Wikileaks, etc.
Once they know who you are and why they don't like you, they can incriminate you in other ways. This helps them find and flag you. They don't even need to monitor and decrypt traffic - they can just upload hashes of things they don't like and let Apple's dragnet do all the work.
Don't buy into "CSAM" scare. It's never the intent. The powers that be don't give a damn about children. It's about power.
This is the EXACT SAME database EVERY cloud provider has been using for about a decade. Look up Microsoft PhotoDNA.
The only difference is that the company doing it was Apple, who wanted to do the checks on-device BEFORE upload. And with multiple redundancies and human review.
Not like Microsoft, who have - for example - shut down the MS account of a German man for having photos of his own children on a beach. No human review, no way to complain. Everything gone from Outlook mail to Xbox account.
[0] https://en.wikipedia.org/wiki/National_Center_for_Missing_%2...
I'll eat my hat if this system doesn't hurt someone innocent.
Because if a government agency is involved they will be doing so server-side instead of client-side.
I hope you're right, but I don't think you will be.
One of these yummy nacho hats? https://www.google.com/search?q=nacho+hats&tbm=isch
Our defense of privacy should be paramount, and we shouldn't defend the fruit company for assailing it just because we like the pretty things they make.
Every word of Stallman's warnings about computing freedom was right. He was prescient. And just like his arguments, there are many people that view this move by Apple as a huge erosion of privacy. We all have a very legitimate fear that shouldn't be dismissed.
You can attack and trivialize my arguments, but mark my words, history will show we're making a huge mistake here.
If you turn the iCloud Photos feature off, no more scanning is happening.
This seems pretty simple to me.
Yet.
A few years later, [Insert gov agency here] will force Apple to scan all photos and compare hashes to material banned by the government.
This ability to scan photos on the device simply should not exist. If they only want to scan photos being uploaded, just scan them on the server itself. It really isn't that hard.
Apple has turned a steel barrier that's capability focused, into a policy barrier that can be changed by influencing people. That's simply much more insecure and much less privacy focused.
As a Fi and Fiber user, those services have actually been really solid and reasonably priced.
Android wise, Calyx maintains a nice de-googled one (https://calyxos.org/install/ ) and they will sell you an unlocked phone at a reasonable price if you are a member. We use one on Google Fi with no issues in any of about 10 countries so far.
Or you could be a T-Mobile subscriber and never "go over" on data, even when abroad. It just gets slower, but that's fine most of the time, at least for me. It's amazing to be able to use even slow internet in the butt crack of the world somewhere without paying an extra dime - that's the way it ought to be on all carriers.
If the EU agrees this will be very interesting for the smartphone market.
5 years of security updates is already great.
Why? Despite what Apple would have you believe, Pixel phones aren't "more complicated" than iPhones. They're just a little different. For example, I recently had to use an iPhone and the interface was difficult to use, coming from Android. Not because it was inherently confusing, but because I simply wasn't used to it. But I'm sure it would have only taken a few days to adjust.
In my case it's -1 year because I prefer to wait up to a year until I get a good deal, and then there's always the option to put LineageOS on the Pixel devices [2].
[1] https://support.google.com/pixelphone/answer/4457705?hl=en
I think the previous pixels were reasonably good in that regard (not compared to framework of course).
Improving that would be higher priority in my eyes. Software support can always come later: even once the official support is dropped the community can backport AOSP fixes etc.
I'll wait for the iFixit report on how difficult it is to replace the battery, before believing in a phone lasting that long. Also as usual for the pixels, there is no analog headphone jack. Still I can't believe I'm at least somewhat interested in a $600 phone since I'm not that much of a mobile user. I wonder if they will do a 6A version any time soon.
The main difference between the 6 and the 6 pro is the pro adds a telephoto camera, right?
Anandtech article is up: https://www.anandtech.com/show/16939/google-announces-pixel-...
I'm still somewhat leaning towards a 5a as my next phone, as it's already more than I want to spend.
I have a family member with an iphone se (2016 model) and it has needed a battery replacement. No big deal with the ifixit kit. But it seems to me, phones with wireless charging seem to have harder to replace batteries a lot of the time. The Pixel 2 is notoriously difficult. So I'll wait to see what happens with the 6. Of course I'm even more interested in a 6a, if they make one of those. I'm enough of a throwback to still want to use wired headphones.
I recognize Samsung as being well clear of the rest of the pack of Android vendors. Other Android vendors are outright negligent, whereas Samsung seems to generally try to fight their bad incentives and come up with some decency.
Where I think Samsung falls short is execution. Samsung is fundamentally a hardware company and their software has always been mediocre in my view, even to this day. In terms of security updates they promise less than Google, they promise fewer and slower updates than Google (quarterly software updates for some devices / late in the lifecycle still makes older devices an afterthought!), and I trust their promise to execute on their promise less than Google.
Finally, Samsung devices don't have nearly the same support for third party privacy friendly OSes than Pixel devices do - you're stuck with Samsung's (warning: personal opinion) rather tasteless take on what Android should be, and have no real other options.
[1]: https://news.samsung.com/global/samsung-takes-galaxy-securit...
I'm a huge fan of operating my phone with styluses in general, but I think Samsung is the only Android vendor (other than Apple with their pencil) that actually cares about the benefits of adding a stylus to a phone/tablet.
For instance, last week I discovered that you can annotate your calendar with the S-pen. Your annotations stick to your calendar like post-its would to a computer. At first I thought I was drawing on a _picture_ of the calendar application view, but I was writing inside of the app itself.
Samsung's Note os is full of these niche-but-useful-when-you-actually–need-or-want-them kind of features.
Taking macro photos of that little insect on a hard to reach life in the forest? You can point it right where you need it with your right hand while you snap pictures with your pen in the other. It's a neat little remote.
Use your phone for presentations? The pen is your clicker to go through your slides.
Like keeping a digital journal with handwriting? Samsung's (and Google's too) keyboard has great handwriting recognition built-in. Nobody except me seems to use it, but it's actually great!
Need to quickly quickly take a note to make sure you won't forget to do that one important thing? Take out your pen while phone is locked and you can write on your screen directly, this is saved instantly to your device.
Samsung has clearly put a lot of thought into this over the years. The integration is excellent and is available in places where you would never expect it.
TL;DR: I like my note, not only is the hardware great, the software is great too
I disagree. I really like Samsung's take on Android and appreciate features like Dex. With some first-party software from the company, they also make Android extremely customizable. The long tail of Android features that exist only on Samsung devices would probably surprise you. OneUI is a pretty clean take on Android styling.
> In terms of security updates they promise less than Google, they promise fewer and slower updates than Google
I'm getting monthly updates on my somewhat older devices. Not just security updates but full on Samsung software updates. I just got a bunch of new features on tablet this week including quicker multi-tasking, better window docking, etc.
We have different tastes in phones, which is okay. I wouldn't really normally respond to this, but I think this quote highlights _why_ our tastes differ.
"Having more features" is not a selling point to me, it's probably the opposite. I want a simple OS with a strong set of core features, with a small selection of apps relevant to me. Smartphones have been reasonably mature products for a lot of years at this point, I know what I want from them.
That's why Samsung is quite unappealing to me despite their best efforts - I have owned and used multiple Samsung devices in the past. They're trying to give you everything and the kitchen sink, wow you with a bunch of features. Don't bother me with that stuff, I just want something more basic - software wise, at least.
One small example, I've removed all the Android indicator icons on top of the screen that are always on/same for me (alarm, network, volume state, battery, NFC, Bluetooth, etc).
Admittedly I love features but I don't feel like having more features necessarily interferes with minimalism of day to day use. I've used certain features only once or twice but I was glad they were there at time.
Google says "Feature drops for at least three years from when the device first became available on the Google Store in the US." on the shop page footnotes.
Samsung says you get 3 major Android updates on your devices. Therefore, Samsung is a better deal for updates assuming Google doesn't release a new major Android version every year.
"We patched a few zero days" should be the norm, not something you mightily announce as something grand and Brave.
I'm utterly tired of Google's attitude and how little they really care about their customers. They have really cool tech and solutions, but their total neglectance of the individual but somewhat high attention of activists have made my view of a #1 company down the slope, I guess I would at one point have to try applying for some position to hopefully change my mind on that point.
I have a love/hate relationship regarding their Android ecosystem and lack of possibilites to keep an updated phone up to date more than 1-2 years.. so after many years listening to the Apple ambassadors among (okay, mostly non-tech) friends and finally went all-in on the Apple way of doing stuff, bought their "Pro"-version of wireless headset, their smart watch series 7 and their "Pro"-version smartphone series 12 (supplied from my work).
I feel totally claustrophobic about the lack of options and what Apple enforces. Chrome, Firefox, Opera, Safari, switching doesn't matter.. everything is Safari/Webkit engine, no firefox extensions.
Control volume of an app/media - no way, everything should have the same volume.. so my phone remains muted 24/7 and I hope important stuff vibrates on the watch (which is of course also muted as I cannot clearly select what notifications should sound or not).
If it weren't for my old android phone no longer receiveing updates I would switch back to my now three year old phone, at least that one let me unlock my screen with my fingers.. The Apple way is more.. if I, in the middle of the night, want to change track on my Bose Sleepbuds - I cannot do it unless I widely open my eyes and stare on the Apple camera so I am wide awake.
But an Android with 5 year lifespan.. then it starts getting interesting again.
I hope the hardware is solid too. After having 2 Google phones die just outside of warranty to bootlooping, I'm skeptical they'll be able to make them last.
What I like about the standard Google Photos/Dropbox/OneDrive approach is that it's no secret you upload your photos to their computers, where they process them. They process them for useful features, and they process them to catch child abuse. But I understand clearly I upload it from my device to another device, and that other device can process these photos. I'm not a Google Photos customer mind you (as stated, I prefer other services than Google's), but I understand the premise, value add and what they do with my stuff on their computers. It’s not my device incriminating me, it’s someone else’s device that does that, someone else’s device I chose to send my things to. I understand that relationship.
I will not accept a relationship with a device I own, situated on my desk or in my pocket, where it try to start a process to incriminate me. That's not processing a personal device should be engaging in, even if this starts out gated behind the heavily pushed iCloud Photos (it’s technically opt in), even if the solution is technically sophisticated (it is), and even if there exist definitions of "privacy friendly" where this approach is more privacy friendly (you can argue that all day long). I just don't want a personal device to do this. If Apple wants to draw the line somewhere else than I want to draw it, that means I probably should not support that.
I don't care what happens in the cloud. What bothers me is the precedent that Apple sets by shipping iOS with `scanPhotoForIllegalContent()` and `reportUserToPolice()` functions. This code is working against the user's interests. As of now, these functions only run on photos that have already been iCloud synced, and they only look for CSAM, but they could easily expand this later on by changing a few lines of code or adding to the hash database.
To be clear, I think CSAM is absolutely disgusting and I want those in possession of it to be prosecuted. But scanning local photos is crossing a line. (I'm sure they catch most pedos through server-side scanning already anyway.) Besides, the only reason Apple gets away with this is because iOS is closed source. If Google tried to pull this shit on a Pixel phone, you could just install a different ROM.
Using that they could add multiple redundancies and they wouldn't need to look at your stuff on the cloud at all before getting multiple positive matches. And even then the first level is a human checking if it's an actual match or a false positive.
This was somehow a huge invasion of privacy, when people were competing on who could misunderstand the very simple premise the most.
Fairly sure that most of the worry around that was because such a system could very easily be changed to do the same to any photo.
And people felt like their phone wasn't theirs and that it could snitch on you. We know that you truly do not own your phone, but most people do not view it that way.
Sure, it is technically better than doing that check on on a server, but the general public do not currently view it that way.
Personally do not like the system as you would be unable to escape it if it started scanning local photos (which I feel is only a matter of time), something you can with google drive and such, by not using them.
In this case, the steelman is that Apple has turned a capability barrier (if your scanning is on the cloud, you simply cannot scan local photos) into a policy barrier (now you can scan all photos, there's just a flag in the software which means you don't do so.)
This is not the case. People are guessing about how it works and getting it wrong. The device doesn’t know if there’s a match or not. The logic is not “if there’s a match, tell Apple”, the logic is “attach a safety voucher to every iCloud upload and let Apple figure it out on the server”. You can’t flip a switch and just run it against all photos on the device – the iCloud upload is a part of the design. If Apple wanted to scan all the photos on your device, they would have picked a different design for this. If Apple change their minds and want to do this in the future, they need to redesign how this works, it’s not just a policy decision.
Yes, but that method is on the server. The client doesn't know which images match, so it can’t scan all photos and decide to upload the ones that match. From Apple:
> On-Device PSI Protocol. Given a user image, the general idea in PSI is to apply the same set of transformations on the image NeuralHash as in the database setup above and do a simple lookup against the blinded known CSAM database. However, the blinding step using the server-side secret is not possible on device because it is unknown to the device. The goal is to run the final step on the server and finish the process on server. This ensures the device doesn’t know the result of the match, but it can encode the result of the on-device match process before uploading to the server.
– CSAM Detection Technical Summary: https://www.apple.com/child-safety/pdf/CSAM_Detection_Techni...
'scan -> encrypt -> upload' is in my opinion better than 'upload -> scan'
We don't need to have this discussion again. Please go research the hundreds of thousands of discussions and blog posts about how what apple is proposing to do is entirely different.
It's this kind of casual fearmongering which stops people from accurately understanding.
What makes you think Apple doesn't already have the functionality to scan for anything they want on your phone, given that they built a phone content scanner a decade ago for the iTunes Match service and a photo tagger and analyser which does run on the phone, and they control everything about the software?
What makes you think Google doesn't have the functionality to scan for anything they want on your phone, or couldn't add it if they wanted to? Have you the source code for the Google Play services? The internal chip firmwares? Have you studied Google's terms and conditions in enough detail to be certain they can't move any such checks client side without telling you? And they also do analyse photos on-device and tag their content for normal use.
Why do you trust that Google isn't doing anything snitchy or on behalf of the authorities, but when Apple announces that they won't and designs a system which makes it hard for them to do that, then you assume they will? Not even quietly cynically suspect that they might, but spreading as a fact that they definitely will.
There's no need for this tone. People will disagree, and that's what makes this place great.
When they scan it on my phone, they don't need to scan it in the cloud. They have one less reason to touch my stuff when it's on their servers. One step closer to full E2EE.
Every major cloud provider is already scanning every photo you put up and in most cases without any human review. Your photo gets flagged and it's good bye account. Next step: HN front page to maybe get a human to look at your case.
Well I wont. I will look for an accumulator replacement for my Pixel one.
700 USD every few years? Quite a bit of money.
Screensize? We had a joke in our (European) high school to tease someone: You shoe size develops like 10, 11, 12, coffin for children, coffin for adults, motorboat... Looks like the same thing is happening to cell phone screens.
I've got updates from both Huawei and Xiaomi many years after the phones stopped being sold. I've heard that OnePlus does the same.
You do realize that Google also scans your images for CP, and furthermore that Google's current business model is literally surveillance advertisement, right?
I am curious if the courts will agree given the evidence of Google secretly paying carriers not to open their own app stores.
If I buy one I will install LineageOS on it as soon as possible.
Yet you buy into the most intrusive of them all... an Android device.
I'm a tech guy though. had a nexus 6, now got a pixel2. all custom roms, completely degoogled. In addition to phone tasks, I use the phone for solitaire, basic web reading, and email. I charge once per week. Both phones are extremely easy to flash. No hacking or exploits required.
That makes Google’s promise here so key. 5 years of updates is 5 years of kernel level fixes. After that, it’s probably left up to the community.
I really don’t recommend people to go out and buy abandoned Android phones to flash software. LineageOS and other community projects are a blessing in many many ways, but they don’t make your phone completely up to date. And that’s something one should make an informed decision about (buying an iPhone, I decided against that).
> LineageOS and other projects can’t fix things in kernels they can’t compile
I think that you're wrong on this, that is unless you decided to use term "kernel" above too liberally, referring to all software running on a device. AFAIK, alternative Android images, such as LineageOS, include relevant - and quite up-to-date! - AOSP common kernels (aka Android common kernels or ACKs; https://source.android.com/devices/architecture/kernel/andro...), which are open source, plus some manufacturer-specific proprietary binary drivers and firmware (though there exist a related, but slowly-moving, project Replicant focused on creating and maintaining a fully open, i.e., kernel + drivers + firmware, Android distribution: https://replicant.us).
Some diligent LineageOS projects are known to incorporate some open source kernel fixes sometimes, or grab newer blobs from other phones from other devices. But there’s only so much to they can do. In general, it’s true to say that older devices with community Android support are not completely up to date - the kernels are old, and vendor drivers are not getting updated. Outside of making big usability concessions in projects like Replicant, the community can’t do much here.
AFAIK, the only way to run it with working drivers for all hardware components, are ROMs which use the rusty 3.0.101 Linux kernel from back in the day and I think that is what DCKing is referring to. If you want to create a new ROM, you either have to use the old kernel and have an upper Limit of Android 7.x (in this case) or you have to accept, that not all components are supported (e.g. no GPS).
I would be glad if the situation would be different. Maybe it is different for phones you buy today?
Having said that, I ran across the following post that describes successful installation of LineageOS 18.1 (Android 11) ROM on Samsung Galaxy S3 i9300: https://devsjournal.com/install-lineage-os-in-galaxy-s3-i930.... This is just FYI. So, if you understand relevant risks and feel adventurous, you can try to install it on your device. Disclaimer: I'm neither affiliated with the author of the post, nor responsible for any damage that might be associated with following the advice contained in the above-linked post.
https://youtu.be/K_i29pczfRA?t=10
So congratulations to the guy who made it possible to run Android 11 with that ancient Linux kernel, even when Android officially doesn't support it. And to illustrate what I mean by ancient: Linux 3.0 was released in 2011 and got support updates until 2013 [1]. So even when CyanogenMod/LineageOS supported the Samsung Galaxy S3 the included Linux kernels were old as crap. You can't blame them for it, as they had little choice given that a few crucial drivers are not open source and included in the upstream Linux kernel.
I just wonder if anything has changed for modern devices?
[1]: https://en.wikipedia.org/wiki/Linux_kernel_version_history
backported 4.2, which includes some of the 4.3 changes as well. supports lineage. 4.1 is a version google supports till 2024, so I'm assuming 4.2/4.3 is going to be even later. So, you got a phone from 2011 that's going to run a modern kernel and latest android till after 2024.
> And to illustrate what I mean by ancient
yes. I would love to see an iphone from 2011 that's going to be running the latest ios and apple kernel after 2024.
I think the discussion about which devices live longer is simple to answer: Apple (iPhone) and Google (Nexus/Pixel) do probably the best job of supporting their devices for a while from a manufacturers point of view (in comparison to Samsung, Xiaomi, LG, Huawei, Sony, etc.). However, if you want to spend some time and flash alternative ROMs yourself you are better off with Android due to the large modder community, but it also depends a bit on the device you bought.
My biggest issue on the other hand, is that if the manufacturers would also open source the drivers, they could be included in the Linux kernel and we would not have this discussions, because one could simply use an up-to-date kernel as you can with every PC.
1. UX: most of the time kernel updates don't affect the user experience. However, from time to time there are scheduler updates which can have positive effects.
2. Security: Being able to run the kernel with the latest security updates is evidently very important to have a system that is not vulnerable to newly discovered exploits.
3. Dependencies: As discussed already, some software components like the Android itself requires certain kernel features and therefore certain versions to let you run the latest versions of the software.
Btw. even LTS kernels are just supported for six years or so.
My biggest problem with the situation is, that 99% of the software is open source (Android incl. the Linux kernel) and just a few vendor-specific drivers make it very hard to upgrade the kernel and therefore the system.
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.
Now let's keep in mind that I replied to a guy who said how great it is that ios has more longevity.
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 drivers or other proprietary components exist. You can patch up open source pieces - those are important too - but that doesn’t count as “fully security patched”. Kernel drivers are a very important vector on any system, on Android especially so.
This is why e.g. CalyxOS has these EoL notices for Google devices much newer than the Nexus 6 here: https://calyxos.org/install/ They’re honest not everything can be updated!
If you choose to run your devices this way, more power to you. It's a legit way of extending a phone's life with some tradeoffs. But please inform others about the actual limitations.
> For example, kernel version 4.9.3 - the latest one (yes, originally released in november of 2017) supports up to the latest Android.
I couldn't find anything online about Nexus 6 kernels that are not some version of Linux 3.10, which despite being an LTS release was EoLed by the Linux kernel developers end of 2017. Would be curious to get any sources on the information that the Nexus 6 has modern-ish kernels available.
It's a rare feat that Android devices get a new major kernel version, _even with_ vendor support.
This is why CalyxOS now makes it clear what devices they support are still getting full security updates (kernel + firmware blobs) or just kernel updates. I believe the most recent CalyxOS patch added the ability for the user to see in settings the month and year of the last firmware security update for their device vs their current kernel security update.
In addition, I'm unsure why you think you can't update the kernel on a phone. In fact, updating the kernel is standard procedure for... pretty much all directions on flashing a custom ROM. I had my nexus6 on kernel 4.9.3. There are literally new phones, right now, selling with that kernel version and earlier, with android11.
This is like saying windows server 2016 has a kernel that's outdated, or that windows 10 which came out in 2015 is outdated.
I think you are extremely confused.
>I really don’t recommend
Which is a good thing, because you should not be recommending about things you do not understand on even a basic level.
>After that, it’s probably left up to the community.
right. the entire point of my post. you can load stuff from the community. which includes the community of things like lineage - a big official community that's an llc - a corporation like redhat.
A phone is not a server. It is not a security risk to run an outdated kernel. there are no services running a hacker can connect to. You don't connect to a kernel over the internet. A kernel which is by no means out of date, and is currently running in many datacenters.
The kernel also still plays a vital and security-meaningful role in processing calls from applications.
Running an out of date kernel could mean strangers ransoming your data, or could mean an attack becomes persistent and starts logging and uploading through reboots.
Running an out of date kernel often does not result in this, and that higher level security matters first.
However, the kernel does have an attack surface through those higher levels, and pwning the kernel still means something.
Those datacenters are running LTS kernels with minor versions updated, or have security patches backported, or have far more limited connections to the world than your phone — only one protocol, one port, one service, for example.
One example, since you asked: https://thehackernews.com/2019/10/android-kernel-vulnerabili...
> Smartphones aren’t servers, but they run tons of services that
> interact with the surrounding world. Bluetooth, WiFi, etc…
Sounds like a server to me. Maybe not a webserver, or an SMTP server, or database server, but it is a server running world-accessible services.The issue you note is only exploitable via a bug if you have an outdated version of the chrome browser. You don't need to update the kernel, in order to update an application.
Seriously, I feel like I'm talking to my wife here, who is not a tech person. Why are you and the other couple of people being purposely dense, and purposely ignoring the content of your own links that doesn't fit your viewpoint?
BTW, after you said smartphones aren't servers, you go on to talk about why an older kernel is bad on servers.
But since you asked, the latest 4.9.3 kernel running on that nexus6 from 2014, that's been compiled appears to be from the end of the year 2019.
If everyone around you is stupid, then maybe you don’t understand the topic at hand?
This is after one hasty search. https://source.android.com/security/bulletin/2016-10-01
There are various kernel level vulnerabilities listed. Some weakening privacy over tcp connections, others locally exploitable via a malicious app such as Pegasus.
I don't understand why you call him confused. Perhaps you can approach with curiosity instead.
In those five minutes of looking through your garbage dump, I found Zero vulnerabilities that do not need either you installing a virus, which then gets root (the vulnerability), or a bug in an application running as root that's out of date, which then of course gives the attacker of the application root. None of those are valid examples, and I'm now bored digging through random garbage.
Any hack, in Any application, will give the attacker root - we're running rooted phones (for the extra functionality).
If you want to make a point, note the actual bug listed that does not need a compromised application. You installing a virus then the virus getting root does not count. The thread is about a kernel bug giving a remote attacker control of your phone. Applications and drivers like your modem can be updated without you updating the kernel. The latest N6 kernel is 4.9.3, with updates from the end of 2019.
Also, regarding your previous post, modern Android and ios is lightyears ahead in security than any desktop os out there, for good reason (majority of people interact with their phones, and store much more sensitive data there)
yes. always have. same in windows where I also don't use antivirus. and this is what most tech people do for their personal equipment. because the one issue I had, in my 30+ years of using computers, and 20+ years of doing it professionally as a dev, sysadmin, and storage admin, I only once got a virus.
i'll tell you a little secret too. yes, it's wtf to people who don't know what they're doing and need the safeguard against when they screw up. I know enough to not screw up. now go pipe a bash script from a webpage to sh to install something, because that's what the installation manual for your game said to do.
Running anything under root is just insanely stupid.
> 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.
Your car has pieces that run linux too. Guess an attacker can make you crash.
> drivers
since this is about iphone and android comparison, guess what has those same driver blobs form those same exact manufacturers. apple doesn't make their own bluetooth chips. oh, btw, the drivers get updated just fine, since that's part of the kernel and os, which all get updated just fine.
google supports kernel 4.1 till 2024 for android 11. the nexus from 2014 runs 4.9. so probably 2026 kernel and android, fully patched - 12 years.
oh, sorry, did you forget this thread started with a guy claiming ios is great because you can put later versions of the OS on there? where's that iphone from 12 years ago running the latest version of ios, and still performing fast? because that's what this thread is about.
> Your car has pieces that run linux too. Guess an attacker can make you crash.
Actually, yes... https://www.wired.com/2015/07/hackers-remotely-kill-jeep-hig... http://www.autosec.org/pubs/cars-usenixsec2011.pdf
> the drivers get updated just fine, since that's part of the kernel and os, which all get updated just fine.
Just because the kernel is getting updated does not mean the drivers and firmware are also getting updated. Drivers are specific to hardware, and if a vendor stops shipping updates for some chip that is no longer used in newer phones, then you aren't going to get updates for that chip.
> since this is about iphone and android comparison
This isn't about iphone and android comparison, not for me. You made naive claims about kernels not having attack surface and unimportance of staying updated, and I am responding to those claims.
But iphones have amazing longevity. The iphone 5s you mentioned came out in 2013 - which is 8 years ago now. Back then Obama was still in his first term. Maybe it is way too slow to handle the most recent version of iOS, but I'd rather a phone vendor that releases operating system updates for 8 years than a vendor who releases updates for only 2 years (like you get with certain android vendors.)
Last year I replaced my iphone 6s with an iphone 12. The thing that astonishes me is that I didn't need to. After a battery replacement, my 5 year old iphone was still running fine. It still runs the latest OS, and it ran every app I threw at it with aplomb. I really only upgraded it as a personal indulgence. Its still in use by a friend.
I'm absolutely on board with complaints about apple's lock in. I'm disgusted by some of the documents that came out in the epic court case, and I wish you could easily root iphones. But it feels like a stretch to complain about their longevity.
Now as far as the iphone 6s being usable - that's my point. It is usable, on the old OS it was designed for. Because you can't load your own OS on it, it will never run the latest. While the Nexus does run the latest, and is completely usable. I do remember when my brother loaded some latest ios on his iphone 5S, and it literally became too slow to answer a phonecall.
Apple's lock-in is in my opinion a feature for its target market. That's why they get like $1200 from me every two years. Me, my concern was battery life. For that I needed to not have crap that keeps phoning home and waking up the phone. Imagine charging once per week. While not an issue now, I used to travel a lot. Country-hopping trips. Yes, you can charge at the airport, tied to a full charing pole for an hour. Yes you can charge while sleeping on the plane and have a usb cable hanging in six inches in front of your face getting in the way. Or... You can literally not worry about it for a week.
There are of course other things - I want to chromecast my screen or cast a movie from a pirate streaming site (not the youtube app). I want toggles on my lock screen and home screen to turn off data/wifi/bluetooth. I want to turn on the flashlight if I press both power buttons when the phone screen is off. I more importantly need a filesystem that I can store OVAs on that I can take to customer sites for demos - why would I carry a usb stick when my phone is always with me. I want a web server running on it and my laptop to dump a backup of itself onto the phone daily. This means the phone phone software needs to recognize that the phone hardware is a computer, not a toy for 5yo kids. My wife on the other hand needs it to be a toy, because if it wasn't, she'd do everything possible to get viruses, delete everything, and screw something up. So I got an android, she has an iphone.
Now, you think I'm complaining about longevity. Let's see the reality though.
The post I'm replying to touts the iphone's longevity compared to Android. I point out Android has much, much longer longevity and he has it backwards. You then declare I'm complaining about the iphone's longevity.
Now, normally I would normally unload on you with all kinds of funny (for me) things at this point, because you now fit into a certain category of people, but this isn't the place.
That's... An odd thing to say. I'm not sure what you're saying about your wife, but I've never had anyone, young or old, have a problem with an Android phone that would require anywhere near that amount of time.
My whole family has Android phones from different makes except 2 people with iPhones and they don't need hours of tech support. Your experience may be different, but I think most people using Android phones would agree that for the most part it just works.
For the battery life and the latest iOS, once you upgrade your iPhone to a later version, it is hard to go back, and you need hacker chops to do that if it is even possible. Later versions of iOS do often reduce performance and battery life.
On top of that, iPhones have smaller batteries so even with a tightly-integrated OS, what happens is that with active use, the battery level drops precipitously. Sure they last ages when not touched, but what's the point of that when a video call drops the battery by 50% because the battery itself is smaller?
Most people stuck to power banks these days are people using iPhones, especially the smaller iPhones. Androids have taken care of the battery issue by going with 4000 mAH+ batteries.
I highly, highly, highly doubt that.
Considering how static phones honestly are after initial setup, when you've installed the apps you need and configured the few things you need configuring, you never touch anything that's not an app.
Apple and Android ecosystems and user-bases are wildly different so a true apples-to-apples comparison (pun-intended!) is not trivially possible.
> Now as far as the iphone 6s being usable - that's my point. It is usable, on the old OS it was designed for.
That phone was running the latest OS when I gave it to my friend last year. I think it might have been running faster thanks to ios 13 (or whichever version improved performance). I believe you when you say your brother's iphone 5s became unusable with subsequent updates. But my 6s kept chugging along just fine, updates and all.
I'm delighted there's solutions for android phones like what you're talking about. This sort of thing is really important - I mean, they're fully fledged computers capable of way more than we're able to use today. Its crazy that people throw them out after a few years. My iphone 12 is faster than my 2016 macbook pro. And I still occasionally code on that laptop. If I could run OSX on my phone and use my laptop as a terminal for it, that would be really sweet. But I can't because Apple doesn't care, and I'm locked out of making changes like that on my own hardware. Using old phones as web / file servers would be fantastic.
Companies like Apple are actively incentivized by the market to make their old products feel worse over time. And for that reason I'm always impressed when occasionally they release an OS update that improves performance across the board.
I guess my take is, Android phones have an awful history of dropping official support for recent devices. I'm delighted the hacker community can and has stepped in to clean up android's mess. Its a shame they have to, but such is life.
I'm sad you can't do that on Apple devices, but one saving grace is that, the 5s aside, apple seems to do a much better job of official software longevity than android. I'm expecting my iphone 12 to last 5-10 years. I do wish the battery lasted all week though - that sounds phenomenal.
There is of course also a degree of investing time writing to the new hardware more than the old one, and just cutting down features that don't fit due to lack of processing power or just lack of underlying tech on older hardware, but it's not something that being able to throw a different OS on seems likely to fix?
I don't think they're trying to make their old products worse over time. But I also don't think companies generally care that much about making old products work better over time. One of the parent commenters noted how well modern android runs on really old nexus phones if you strip out the "modern" animations and useless features. There's nothing stopping google doing this. People would love it. So its notable that they don't. Apple got a lot of good will from me a few years ago when they focussed on performance in ios 13 (or was it 12?). That OS release made my phone feel new again. After that update I think it ran faster than it did when I bought it.
Another way to think about it is that when you buy a product, your incentives and the company's incentives are aligned. You want the best phone. The company wants your money, and knows they need to deliver a good product to get it. After you've bought a product, the company's motivations aren't as well aligned with yours.
Arguably a company sells more phones in the long run when they have a good reputation for delivering on quality, and supporting their products. Eg, a few years ago some of my friends would buy every single blizzard game simply off the back of their reputation.
But most companies don't take advantage of this, and mistakenly focus on short term sales even if it harms their reputation. And, in turn, their long term profits.
As someone much wiser than me said, service and support is a form of marketing to repeat customers.
But the discussion in this thread was specifically about the claim that iphones unlike android have a long life of updates. That's like saying "my dell from 2010 came with windows vista, windows vista is not supported, the computer has a short support life. Umm, no, you put Win10 or Linux on it, and can probably put win11 on it, and in 30 years still put the newest linux on it.
Graphene and Calyx only support the devices as long as google is putting out the security updates, so all the phones before the 6 will only get the ~2/3 years that Qualcomm limits updates to. I am not sure how lineage is able to support devices for so long after vendors stop supporting it themselves. They are a super dedicated community of volunteers, though. [Here](https://grapheneos.org/faq#legacy-devices) is where Graphene talks about why they drop support after vendors don't officially support the device anymore
Of these projects Calyx and Graphene are the easiest to install. Graphene you only need a chromium browser and to allow unlocking your bootloader in the developer part settings, and over webusb the whole wipe, install, and flashing of their key so you can re-lock it. Calyx has a script you download to do the same. Lineage is a hair more involved.
https://forum.xda-developers.com/c/samsung-galaxy-s10.8693/
I did a lot of research earlier, because I don't use a case, dropped my pixel 2xl, and the glass on the corner cracked. I ended up just putting a dab of epoxy on it instead though. I use the carbonOS ROM on the pixel, which os only for pixels I think. You do have to go through a lot of system services and turn off the unneeded ones though. Lots of useless stuff like "carrier services" and "sprint dm" and a bunch of other crap - just google them one by one. An app like Fibers is great too - I use it to do things like display percentages instead of icons, and when I need turn off half the screen pixels. You can do that in low brightness situations like reading this site in bed w/ the lights off, and you can't tell it's half the resolution. Adguard is great too - blocking ads at the DNS level saves quite a bit of battery when online.
Now here's the main thing - I do spend a couple of hours per day using it - either for email or reading sites. I get about 4 days from 90% to 25%. I never go below 25% or above 90% - my battery is like new 3+ years later. Another feature that an iphone can't have - an app having access to limit your max charge limit. I'm just guessing that 100%-0% is going to be about 7 days, so I can't fully promise that.
Also, a couple of banking apps don't work. The Uber app doesn't work either - you have to use the website versions.
I'd go for a Pixel 5, but... no 3.5mm jack is a dealbreaker.
So I guess the Pixel 4a is my only real choice.
https://www.phonearena.com/phones/size/Google-Nexus-5,Samsun...
The Pixel 5 is larger than the nexus 5, but it's almost in the range of reasonableness. The S10 is well past that size range -- there's no way I can reach the top of the screen.
Admittedly, it is nice that the S10 includes a headphone jack. But phone size is even more important than that to me. Guess I'll keep using my 2016 iPhone SE for a couple more years!
The problem was that they didn’t notify users, and after people in France winning a lawsuit, they now have it opt in I think? Nonetheless, it was a feature made in good faith.
I got the panda version. after 2 months in my side pocket, the white paint that for some reason the google geniuses decided should cover the also white plastic, started peeling off. From rubbing with my leather wallet. completely irrelevant to the functionality, which is the good part about it. searched it and everyone w/o a case is having the paint peeling issue. but... it's a much better issue than the entire phone, front and back being made of glass that breaks and costs $100+ to replace, and falls frequently because it's too slippery to hold in one hand.
I want as little to do with Google’s services as possible in my life, but they really deserve credits for making a modern usable smartphone that is reasonably open. There is just one single feature I will be buying this for - the 5 years of software updates. While good image processing is definitely a pro, all of these software you’re presenting features I really don’t give a damn about. Just give me a phone that is meant to last a little while - and allow me to run what I damn please. This looks to be like a continuation of the Pixel 5, which allows you run your own software like /e/OS and CalyxOS aside to just being a lot less of a walled garden on the stock ROM.
The Android market is completely dire, and no vendor can be trusted to provide openness, reasonable taste or security updates. They sell you a phone, and once you’ve clicked buy they’ve already stopped caring. So last year I switched to an iPhone 12. I needed to vote with my wallet to get a phone that lasts. But although I get what’s appealing about iPhones and the walled garden, I started feeling claustrophobic. Feeling claustrophobic about what I can tailor about my browser, how easily I can run Game Boy games, what ads I can block, and Apple’s stated intents to actively incriminate you by scanning your photos on a personal device. I will continue to recommend those phones for most people (pending what they’re going to do with trying to incriminate you), but it’s not for me.
Finally here’s a seemingly good Android phone with 5 years of support - from the only phone vendor outside of Apple who appears to give a damn about that aspect. Don’t get me wrong: 5 years is still too short in my view, and not as long as Apple provides support for on their stuff [1]. But the market needs change, and I’ll put money towards that.
[1]: The iPhone 5S has just hit 8 years of _kernel_ security updates last month with iOS 12.5.5. One can dream on the Android side, but I’ll take 5 years in the current market.