831–840 of 851 posts
I hate the trend that the "pro" versions of all these flagship phones need to be an XL Phablet monstrosity. Human hands haven't gotten any bigger. I have owned most of the Nexus & Pixel phones throughout the years. After having the Nexus 6 as my daily driver for 2 years, I have always opted for the smaller option ever since. I would totally pay flagship prices for a regular ~5.5-6" phone with flagship specs, and I'm…
I hate the trend that the "pro" versions of all these flagship phones need to be an XL Phablet monstrosity. Human hands haven't gotten any bigger. I have owned most of the Nexus & Pixel phones throughout the years. After having the Nexus 6 as my daily driver for 2 years, I have always opted for the smaller option ever since. I would totally pay flagship prices for a regular ~5.5-6" phone with flagship specs, and I'm…
Earlier quoted context omitted.
> 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 fli…
There is still a local CSAM database and still a method somewhere that returns a probability that an image is in the database, isn't there? The safety voucher logic is layered on top.
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...
Earlier quoted context omitted.
Accurate, but note that intent as OP referred to is not the same as implementation. Fucking up doesn't mean you intended to fuck up. 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.
That's the narrative that Apple's marketing department is selling, but I'm not buying it. The fact is that Apple devices slurp up more data to Apple that you cannot turn off without making your phone essentially useless than Google devices slurp up to Google.
Want to update Google maps home/work addresses? Too bad, requires web/app tracking enabled.
Earlier quoted context omitted.
I bought a Fairphone 3+ 10 weeks ago, and just got a refund because they cannot build any units. I really wanted this, I guess I will continue to wait for the librem5
I was curious and just checked into the librem5. I am NOT spending $900 on a phone.
Earlier quoted context omitted.
https://forum.xda-developers.com/t/kernel-7-x-i9300-hybrid.3... 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…
Given that the kernel still identifies as 3.0.101, my guess is that they just backported some features from 4.x and applied them to the ancient kernel ;-) I am not so sure that qualifies as a 4.1 in terms of Android support. 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 manufac…
Earlier quoted context omitted.
Recently spent a long time agonizing over getting a new phone. This is the only phone that checked all my boxes (small, decent ram, storage and camera, headphone jack...) but it doesn't work on Verizon :( Went with the Pixel 4a, we'll see how it goes
4a is a great choice. I think you'll be happy with it. The Samsung 10e is another similarly priced device. I think the Google photos integration is really nice. Even though the Google photos app drives me nuts sometimes.
Earlier quoted context omitted.
Btw, I just came across this: https://www.engadget.com/google-assistant-call-hold-18123642...
“It understands the difference between a recorded message and an actual representative on the line.” If it can really understand that hold music stopped to play a periodic voice recording of “your call is important to us” is still a recording (and not have the urge to smash phone at the wall) I’m completely sold!
Earlier quoted context omitted.
What are these good apps? I'd like to check some out.
I don't know if it's worth changing phones over, but Overcast is a really nice podcast player (smart speed works very, very well). Apollo is nice for reddit.
Earlier quoted context omitted.
Given that the kernel still identifies as 3.0.101, my guess is that they just backported some features from 4.x and applied them to the ancient kernel ;-) I am not so sure that qualifies as a 4.1 in terms of Android support. 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 manufac…
And how does the kernel affect you in any way. Most of the internet runs on old kernels because servers user long term stable kernels anyway. If they ux is good the kernel shouldn't be a problem to you
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.