Live data from Hacker News

Android 10

android.com

311–320 of 518 posts

Re: Android 10

#311
post #167

Earlier quoted context omitted.

Indeed. But it does look nicer/work better for what black themes are actually good at: Using at night. So while the additional battery savings between "true black" and grey are within the margin of error, the battery benefits remain for both and the non-battery benefits remain for our eyes.

True black looks nicer in the same way that oversaturated TVs look "nicer" in the showroom: it's great for grabbing your attention, but a pretty crap experience in the long run. White on True black UI has way too much contrast and is much more fatiguing than white on dark gray.

Eh, I don't agree at all. Maybe that's the case if you don't use adaptive brightness and your whites are max intensity. I prefer a dark theme I can use all day and let the brightness setting modulate the contrast. That way, direct sunlight kicks in the high contrast capability to make the theme usable during the day (which destroys these gray "dark" themes), while dropping the overall contrast ratio to something similar to these gray themes and emitting less light overall at night.

Pure black doesn't feel like I'm looking at a box light and makes transitions between text and media much more consistent. I end up futzing with the brightness for mixed media (like embedded videos or images) far more when using a gray dark theme, since the true brightness will be much more intense for "media white" than "text white", and the perceived brightness between them will be even higher than that.

Dark themes used to be about practicality and health. Current gray dark themes seem to be born from poor contrast ratio LCD limitations and justification for the aesthetics around the old Holo theme. As someone that has religiously converted their most common sites to dark themes with custom CSS (a few hundred as of now), gray on gray themes feel foggy and I only use light-but-still-dark gray backgrounds on sites that change frequently so I can see if there's a new text element that needs to be styled.

(But, I'm probably in the minority. I also drop font sizes to reasonable levels, delete rounded corners on elements, and remove the miles of whitespace from sites unwilling to accept that a two paragraph "story" isn't worthy of the engagement metrics they get by wasting the reader's time scrolling.)

Re: Android 10

#312

I recently bought a Nokia 2.2, which in in the Android One program. Two main reasons: a removable battery and OS updates for two years and security for 3. At this point, there's very little difference between the hardware of flagships and commodity, especially considering the real-world use of smartphones. I mean, is anyone compiling programs on these things or doing anything particularly intensive? Not really. So gi…

> a removable battery and OS updates for two years This provokes me. Are we supposed to be happy with two years ? The environmental impact of e-waste and the production of electronics should not be understated. I have a Nexus 5 as a backup phone. It works just as well as my main handset. I know how to duck the G-surveillance and I'm able to keep it alive because I have the knowledge to install roms. Not everyone does…

> Are we supposed to be happy with two years? The environmental impact of e-waste and the production of electronics should not be understated.

Can you elaborate on this? Because I'm thinking of the amount of garbage I put in the bin over a period of two whole years, and the size of my phone, its packaging, chargers, cables, and manuals all together is just not even comparable. Even if you add in the environmental cost of the manufacturing I can't imagine it's even a drop in the bucket compared to other waste.

I'm sure it is a good idea to optimize for waste in some respect, but cell phones seem like they must contribute such a minuscule relative amount so as to be safely ignored for now.

Re: Android 10

#313

I recently bought a Nokia 2.2, which in in the Android One program. Two main reasons: a removable battery and OS updates for two years and security for 3. At this point, there's very little difference between the hardware of flagships and commodity, especially considering the real-world use of smartphones. I mean, is anyone compiling programs on these things or doing anything particularly intensive? Not really. So gi…

I bought a Nokia 3.1 as a lower end test device, which also belongs to the Android One program. The device is so slow to respond to input in every way that it's become the device I use to test our apps absolute worst case performance on. Even knowing it was meant to be a lower end device it routinely gets frustrating to use for even the most simple tasks, such as Chrome tab switching, keyboard response and even just…

I bought a few cheap (under $100) Nokia Lumias back when Nokia was Windows Phone's last, best hope, and it always annoyed me how a cheap Lumia with Windows Phone was in so many ways nicer to use than a mid-range Android phone -- much more responsive to input, less lag, etc.

Re: Android 10

#314

Earlier quoted context omitted.

> Are we supposed to be happy with two years? The environmental impact of e-waste should not be understated. Note it's 2 years of feature updates not 2 years and it turns into a brick. Everything will still work and you'll still get new apps and app updates for far longer than 2 years. Security updates go for longer, too.

Given that Apple are still managing to roll out operating system updates to iPhones that are 5 years old, a potent question is why Google and Android device manufacturers are either unable or unwilling to attempt to do the same. Planned obsolescence isn't just an attack on your customers, it's also environmentally irresponsible.

Apple does also cut features when they roll out those updates though. Not all iOS versions are equal.

It is a shame Android's update story is bad, but realistically it also doesn't matter much. Non-enthusiasts tend to not even want major updates in the first place (it's a chore - especially if anything changed on them).

It sucks for app developers a lot more than it matters to the majority consumer.

Re: Android 10

#315
post #260
post #211

Earlier quoted context omitted.

FYI, chrome on iOS's core is just Safari's

I know, if anything that makes it more embarrassing for Android - Google controls that whole system and they're still not beating WKWebview on their flagship device. Going between Android and iOS, that's one of the hardest aspects that I think gets overlooked - the browser is just slower and its noticeable. I pointed out the flagship device in this case, but its no better on the lower end devices.

Holy shit I’m not crazy. I switched to iOS almost entirely for Safari. I’d been an Android user for so long I just thought that Chrome was just how the web was until someone handed me their iPhone.

Re: Android 10

#316

Earlier quoted context omitted.

> Are we supposed to be happy with two years? The environmental impact of e-waste should not be understated. Note it's 2 years of feature updates not 2 years and it turns into a brick. Everything will still work and you'll still get new apps and app updates for far longer than 2 years. Security updates go for longer, too.

Given that Apple are still managing to roll out operating system updates to iPhones that are 5 years old, a potent question is why Google and Android device manufacturers are either unable or unwilling to attempt to do the same. Planned obsolescence isn't just an attack on your customers, it's also environmentally irresponsible.

It's because of how updates work. A good overview is here [0]

Basically for an android phone to get an update, Google, the Carrier, the Manufacturer, etc. all have to update the OS for that specific model, of which there are hundreds/thousands of models of phones.

Apple doesn't let the carriers configure the OS, and is also the manufacturer. They also have only like a dozen models. So they basically get to skip all of the parts that slow down updating your IOS version.

[0] https://www.xda-developers.com/wp-content/uploads/2013/12/HT...

Re: Android 10

#317

The website assets are optimized in a rather strange way. The total page weight of ~20MB is huge for mobile. The images are heavily compressed using WebP lossy with quite noticeable blockiness and washed out textures and fine details, but squeezed into 1MB, yet the videos are only lightly compressed, and make up most of the page weight. Had they been compressed with libx264 at good quality, the page weight would be m…

The images are awful (at least in Firefox). They are compressed even worse than Google Developer Insight usually recommends. The text in screenshots is barely readable. The dark theme is uncomfortable for my eyes (ok, maybe it's fault of my poor quality TN matrix, but anyway I don't want to see it). I doubt anyone wants to read white text on a black background. The letters are gigantic and are optimized for hi-resolu…

> still haven't solved the problem of apps and Google itself siphoning all available data from the phone.

New apps are required to request privileges like contact list access and location before using them. You can deny them. What other issues do you want to solve?

> Why does the messenger takes a work of a package manager I cannot understand.

It doesn't. You want to use hangouts. In this case GPS is effectively a library hangouts uses to auth/connect to servers. Since it's the critical building block, it updates itself.

Re: Android 10

#318

I recently bought a Nokia 2.2, which in in the Android One program. Two main reasons: a removable battery and OS updates for two years and security for 3. At this point, there's very little difference between the hardware of flagships and commodity, especially considering the real-world use of smartphones. I mean, is anyone compiling programs on these things or doing anything particularly intensive? Not really. So gi…

Apps are going to use whatever CPU and memory is available. It's the same reason a chat app can use hundreds of MB of memory on a desktop. Why optimize that lower when laptops ship with 16+ GB these days?

In my experience that $140 phone actually does end up being laggier and less responsive which can be super annoying when scrolling and tapping with your fingers. I'm not a hardware engineer, but somehow this seems to hold true even if the memory is sized the same and the CPUs seem comparable. There must be something deeper in the specs involved that leads to UI slowness.

Re: Android 10

#319

> So, if a friend asks you out to dinner, your phone will suggest you text "". Then, it’ll also pull up directions right in Google Maps. "Smart reply" sounds like a privacy nightmare. Now just opening a text causes unsolicited connections to made to Google's servers and other websites containing the contents of your messages. I hope this is something you can easily disable.

It's completely on-device [0]. The prediction models have been shrunk [1] so no connections are made (Google has enabled lots of shrunken on-device models with TF Lite [2]) . I'm not sure why this page doesn't call that out considering how privacy-focused the other features are.

0. https://www.androidauthority.com/smart-reply-android-q-98364...

1. https://www.tensorflow.org/lite/models/smart_reply/overview

2. https://arxiv.org/pdf/1708.00630.pdf, https://www.tensorflow.org/lite/guide

Re: Android 10

#320
post #238

> Now, you can share your Wi-Fi details with guests via a QR code while keeping your password secure. This is terribly misleading. The format used does contain the password so your password is still being shared: * https://en.wikipedia.org/wiki/QR_code#WiFi_network_login * https://github.com/zxing/zxing/wiki/Barcode-Contents#wi-fi-n... I'm saying misleading because there is an interpretation of that sentence that is…

Security is and always has been a sliding scale, despite always referred colloquially as being either present or absent. "Keeping your password secure" in English really means, "improving the security of your password".
Post reply on HN