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

Android 10

android.com

Post reply on HN
Print view View original

261–270 of 518 posts

Re: Android 10

#261

Post by eco »

frittig wrote: post #76
mfontani wrote: post #5

> Android’s new Dark theme uses true black to keep your battery alive longer. None of the screenshots around the caption seem to use "true black", though!

I wonder if any of the Google apps will support a dark mode. Maps / Gmail are harder to use with all of the white

Many Google apps already do. It was weird during the Android 10 Beta because Google was releasing apps with partial support for Dark mode which made them hard to use. You'd sometimes get dark grey text on black background, for instance.

Re: Android 10

#262

Post by eco »

mfontani wrote: post #5

> Android’s new Dark theme uses true black to keep your battery alive longer. None of the screenshots around the caption seem to use "true black", though!

They aren't on those particular screenshots for some reason but are on the actual phone. I just took my own screenshot and it is indeed #000000.

Re: Android 10

#263

Post by Roritharr »

pranau wrote: post #37

I wonder how many of the features advertised here will make it onto the Android 10 release of other OEMs. In Android 9 for example, the ability to select text via OCR in the recent apps screen was limited to only the Pixel devices for some strange reason even though all Android devices had access to that feature prior to the release of Google Assistant via the Google app. In a similar vein, Digital Wellbeing was offi…

Sadly the crazy useful feature of OCR selection was removed from my Pixel 2 XL which really unnerved me.

Re: Android 10

#264

Post by inlined »

pgeorgi wrote: post #17
MrMetlHed wrote: post #3

How will Google avoid being sued (like Amazon / Audible is being sued https://www.reuters.com/article/us-amazon-com-lawsuit/top-u-... ) for the "Live Caption" feature?

For example by making it a feature that isn't exclusively used for books? I suspect it's implemented using the new Playback Capture API ( https://developer.android.com/preview/features/playback-capt... ) which provides an opt-out, too.

Seems dangerous to opt out of what is arguably an accessibility feature.

Re: Android 10

#265

Post by on_and_off »

distances wrote: post #242
alistproducer2 wrote: post #206

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 wouldn't mind the lower power that much, but camera is one of my main use cases for phone. Pixel is just so damn good at taking pictures. The cheap phones do have considerably worse cameras, no way around that.

At some point cameras are going to be commoditized as well though, partly thanks to all the investment in computerized photography.

I bought a mid range phone for my parents, they find its camera amazing.

It does not hold a candle to a pixel, but it is adequate. For users that don't feel the need for the best in class phone camera, it is already enough.

I wonder what will be the distinguishing factor in 5 years.

Re: Android 10

#266

Post by applecrazy »

vladdanilov wrote: post #138

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…

Actually, if you stay on the page for a while and scroll up and down, it loads the light/dark alternates for all media on the page, bringing the total weight of the page to about 41MB. Yikes.

Re: Android 10

#267

Post by andrepd »

alistproducer2 wrote: post #206

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 agree that performance is good enough on 100$ phones, but there are other things, namely camera, battery, screen.

By the way, have you considered the fairphone 3?

Re: Android 10

#268

Post by ivankolev »

nunodonato wrote: post #223
alistproducer2 wrote: post #206

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…

Samsung DeX (or similar) is a very interesting use case for more powerful hardware. But if that's not something you'd use, then I fully agree with you.

I am setting myself up on DeX as a full blown Intellij IDEA multi language environment but their locked down Linux distro makes me very uneasy...

Re: Android 10

#269

Post by Eridrus »

alistproducer2 wrote: post #206

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 recently started playing some games on my phone that require 3d rendering. Pretty sure it would struggle on an older phone. The 4GB of RAM I have feels slightly insufficient since the game gets closed by the OS if I switch to another resource intensive enough app.

I'm not going to say you should pay $1000 for a phone, but just because you have no issues with a $120 phone doesn't mean no-one does.

Re: Android 10

#270

Post by jcknight »

alistproducer2 wrote: post #206

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 plain navigation.

We have had similar, buy not as bad, reactions to other low end device we use for testing.

I genuinely feel sorry for people who use these devices as their primary phones.

Post reply on HN