Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Android 16 is here

blog.google

Post reply on HN
Print view View original

261–270 of 360 posts

Re: Android 16 is here

#261

Post by gorbypark »

mrweasel wrote: post #4

The notification feature looks nice. I've pretty much exclusively used iOS, but honestly notifications is a weak point for iOS, in my opinion. I frequently have the 1 notification on my home screen, but once unlocked notifications are pretty much impossible to find again.

Yeah, I've not quite figured out what I'm doing wrong, but sometimes iOS notifications just disappear after clicking on them. I think it's when iOS decides my face isn't good enough (I have an iPhone 11 where the FaceID isn't as good as the newer phones), and then it tries three times and fails...then the notification is dismissed because I clicked on it but I haven't actually unlocked the phone? Then it's gone forever seemingly.

Re: Android 16 is here

#262

Post by [deleted] »

cenamus wrote: post #234
octo888 wrote: post #226

Earlier quoted context omitted.

Oh, they also had the issue that one of the leading devs got forcibly conscripted. Quickly scanning GrapheneOS's posts I couldn't find any detail about the technical challenges. They'll probably post about it in the coming months

I mean, conscription is per definition forced, isn't it?

[deleted]

Re: Android 16 is here

#263

Post by octo888 »

cenamus wrote: post #234
octo888 wrote: post #226

Earlier quoted context omitted.

Oh, they also had the issue that one of the leading devs got forcibly conscripted. Quickly scanning GrapheneOS's posts I couldn't find any detail about the technical challenges. They'll probably post about it in the coming months

I mean, conscription is per definition forced, isn't it?

Is such nitpicking necessary? It derails the conversation

Re: Android 16 is here

#264

Post by thyristan »

cenamus wrote: post #234
octo888 wrote: post #226

Earlier quoted context omitted.

Oh, they also had the issue that one of the leading devs got forcibly conscripted. Quickly scanning GrapheneOS's posts I couldn't find any detail about the technical challenges. They'll probably post about it in the coming months

I mean, conscription is per definition forced, isn't it?

Yes and no. In some countries and depending on peace or war times, you are forced into service, but you can choose to do military service or be a conscientious objector and work as a hospital aide.

Re: Android 16 is here

#265

Post by graemep »

nashashmi wrote: post #236
villedespommes wrote: post #41

I'm really excited about the Desktop mode, now I can finally break free of Samsung!

Is this something windows phone app can’t do?

Its irrelevant. Windows phone does not have the apps most people need.

Phones are a duopoly reinforced by networks effects. Only Google and Apple matter.

Re: Android 16 is here

#266

Post by TiredOfLife »

anticrymactic wrote: post #245
visarga wrote: post #202

Earlier quoted context omitted.

Maybe Apple thought they need to make a desperate move to deflect from their lack of AI?

Call me old, but I don't think users want AI. Apple summary's turned out barely helpful and that was the big, simple and easy AI application. Instead of a working voice assistant, what uses does AI (LLM) have on a smartphone?

> Apple summary's turned out barely helpful and that was the big, simple and easy AI application. Instead of a working voice assistant

That's the point. Apple is years behind on that stuff

Re: Android 16 is here

#267

Post by M95D »

derefr wrote: post #206
lmm wrote: post #177

Earlier quoted context omitted.

Bland and inoffensive is what I want from my OS. The stage manager should be facilitating the show, not trying out their own material on the crowd.

The OS is less the stage manager, and more the venue itself. Imagine if the Sydney Opera House or Carnegie Hall looked "inoffensive" rather than majestic.

A very good example!

Opera House had (possibly still have, I heard they did a redecoration [1]) very big issues with acoustics. It's bad functionality directly caused by aesthetics.

[1] https://thespaces.com/sydney-opera-house-emerges-with-a-whol...

Re: Android 16 is here

#268

Post by TiredOfLife »

esseph wrote: post #14
throw_m239339 wrote: post #12

I remember my first android device, it had like 512MO of RAM (and storage), and it was blazing fast, it could be used as a WIFI repeater too (which is why I still have it, although it 2.5G...). Fast forward 13 year later or so, if your android device doesn't have at least 8gig of RAM and 64gigs of storage, then it's pretty much useless given how bloated the OS (and the apps) have become... So basically, Android low e…

The same thing that happens to every OS, features and bloat. That said, Pixel devices all the way. No gross UI reskin, no having multiple copies of the same type of app (Samsung camera vs android camera, dialers, keyboards, etc.). Fast, stable, good features. If it's not a pixel device, you're probably going to have a "mid" experience.

> No gross UI reskin

Pixel experience is literally same thing as Samsung One UI - a gross UI reskin

> no having multiple copies of the same type of app (Samsung camera vs android camera, dialers, keyboards, etc

Google is the one that forces the multiple copies of same app thing

Re: Android 16 is here

#269

Post by fcpk »

spaqin wrote: post #214
fcpk wrote: post #130

One extremely disappointing thing that Android has been getting under the hood with Google images is ... Play integrity. This used to be a relatively simplistic system with three tiers: 0 - you are not certified for anything 1 - basic integrity, you need to have a genuine android device running google play services 2 - device integrity, you need to have a genuine android device with core requirements on play and no r…

> rooting should be allowed on a certified device i don't think this is enough - rooting should be allowed on any device that you own, rather than the device owning you.

I do agree, but I understand that we live in an imperfect world with people needing some level of reassurance even if it's pointless...

Re: Android 16 is here

#270

Post by fcpk »

charcircuit wrote: post #158
fcpk wrote: post #130

One extremely disappointing thing that Android has been getting under the hood with Google images is ... Play integrity. This used to be a relatively simplistic system with three tiers: 0 - you are not certified for anything 1 - basic integrity, you need to have a genuine android device running google play services 2 - device integrity, you need to have a genuine android device with core requirements on play and no r…

>rooting should be allowed on a certified device I don't think this should be allowed because rooting breaks the Android security model. Devices that don't follow at least Android's security model should not be allowed that way apps understand the security model of Android. >grapheneos should be given a way to pass all attestations There already is the Android attestation API that can be used to attest grapheneos. Bu…

I think it's a bit disingenuous to mix together the security model and the ability to do things on a device you own.

Should the default android be locked, with no root, play store verifying apps, etc, absolutely. This is great for the average user that desires nothing more than just running play store apps.

Should you have the ability to run what you want on your phone, and copy the data from the app that you installed, after accepting the risks? absolutely.

It is already non trivial to install root, and adb locked root for example makes things vastly more secure even in that case(that is, you can only adb su into your phone, you can't grant the permission to an app directly). Especially with locked adb having fingerprint verification.

On grapheneos you can get basic. You can't get device, which is now needed by a lot of applications. See another example at: https://discuss.grapheneos.org/d/18118-play-integrity-meets-...

Play integrity by locking everything to the Google/Main vendors is making it less and less possible to run non-primary images/oses. And it's not for users security, it's for apps security, so this is purely to reassure the industry, and yet it is just another security theater. Running with strong integrity on a rooted device is possible with semi-significant effort, and that's good. It means that we're not relying on security by obscurity, and we can look at what's running on the phones.

Post reply on HN