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

Introducing Android 9 Pie

android-developers.googleblog.com

Post reply on HN
Print view View original

241–250 of 367 posts

Re: Introducing Android 9 Pie

#241

Post by dmitrygr »

puzzle wrote: post #189
DennisAleynikov wrote: post #45

Earlier quoted context omitted.

No sorry, you might have gotten lucky. But a few major YouTubers have reported this slowdown and I really have no data to back this up. I'm glad the Pixel 2 XL works for you! I just have a personal grudge against the pixel line of phones are they compete with OEM's directly without bringing good hardware to the table (except that god tier camera of course)

Funny that you mention the camera. The Pixel 2 has the same sensor (Sony IMX 362) as a bunch of Motorola phones, like the G5+ and the X4. There is the custom Pixel Visual Core, sure, but that's used only by third-party applications that call the Camera API. Google's Camera app does all the processing on the CPU, presumably with highly tuned Halide code.

There is more to photos than CPU and sensor. There are also lenses and their layout as well as per-device and per-model tuning. This is why even if you side-load google camera app and all the libs it needs unto another phone, even with IMX362 sensor, the photos do not come out as good.

Re: Introducing Android 9 Pie

#242

Post by sjwright »

adrian_mrd wrote: post #135

Does anyone know if Final Cut Pro X or Premiere Pro (or other popular video editing tools) yet support encoding to the "HDR VP9 Profile 2" ? (HDR VP9 Profile 2 is isted as a new feature, as per "Android 9 adds built-in support for HDR VP9 Profile 2, so you can now deliver HDR-enabled movies to your users on HDR-capable devices." yet I wonder if this is effectively a telco-friendly video codec not widely used by media…

I don't think publishing to a single specific profile is an appropriate use of a desktop video editing application. It's like typesetting a paperback book by pressing "print" from Microsoft Word.

You should be exporting a "master" file from your editor and getting your delivery platform (or at minimum a dedicated transcoding app) to output to the various profiles.

Also, exporting HDR content isn't as simple as changing your export setting. HDR changes the way you handle content from the earliest moments of data capture; the real question is how you choose to crush the high dynamic range down to a standard dynamic range for everyone else.

Re: Introducing Android 9 Pie

#243

Post by Paraesthetic »

EpicBlackCrayon wrote: post #30

Did anyone see these privacy changes? https://developer.android.com/about/versions/p/android-9.0-c... * Limited access to sensors in background * Restricted access to call logs * Restricted access to phone numbers * Restricted access to Wi-Fi location and connection information * Information removed from Wi-Fi service methods * Telephony information now relies on device location setting

Thats great and all, but really isn't Google the problem for having that information. I trust scammy looking Chinese apps over Google.

Re: Introducing Android 9 Pie

#244

Post by Paraesthetic »

wyldfire wrote: post #35
EpicBlackCrayon wrote: post #30

Did anyone see these privacy changes? https://developer.android.com/about/versions/p/android-9.0-c... * Limited access to sensors in background * Restricted access to call logs * Restricted access to phone numbers * Restricted access to Wi-Fi location and connection information * Information removed from Wi-Fi service methods * Telephony information now relies on device location setting

These are awesome. Android is slowly catching up with iOS in this regard.

They are slowly catching the year dead Windows Phone

Re: Introducing Android 9 Pie

#245

Post by userbinator »

kcmp wrote: post #128
Sir_Cmpwn wrote: post #75

Surprised not to see mention of the cutout stuff yet. It seems pretty dumb to me that Google is jumping on board with this ridiculous feature. Maybe this'll be one of those Dropbox-style HN comments which in hindsight looks misled, but I honestly can't find any redeeming factors to the cutout idea.

People loved it when Apple did it which gave everyone else the okay to go ahead and do it themselves. It allows phone manafacturers to advertise higher screen to body ratios and is really just a step in the progression towards bezelless phones. There's definitely a loud group of people who strongly dislike it but I think most people are okay with it

the progression towards bezelless phones

I hope not. The bezel has a very real purpose: a place to hold it without your fingers interfering with the screen, whether by activating a touch or just plain blocking the view. I have an older Android with ~5mm of bezel on all the sides and ~8mm of thickness, and trying to get a good grip while not activating or blocking the screen is hard enough. I remember being handed an iPhone 6, and trying not to drop it was the most difficult part. Holding something that thin is just not comfortable, as is trying to pick it up off a flat surface.

Re: Introducing Android 9 Pie

#246

Post by amluto »

EpicBlackCrayon wrote: post #30

Did anyone see these privacy changes? https://developer.android.com/about/versions/p/android-9.0-c... * Limited access to sensors in background * Restricted access to call logs * Restricted access to phone numbers * Restricted access to Wi-Fi location and connection information * Information removed from Wi-Fi service methods * Telephony information now relies on device location setting

> Limited access to sensors in background

I'm amazed this took so long. There have been papers coming out for years demonstrating how to extract all kinds of sensitive information from the vibration sensor.

Re: Introducing Android 9 Pie

#247

Post by on_and_off »

Latteland wrote: post #192
maxxxxx wrote: post #127

Earlier quoted context omitted.

I hope that the permissions are better to understand and control than the current ones. Right now they seem to be designed to give the appearance of giving users control but the implementation is pretty bad and user unfriendly.

And the other problem is you install an app all the time and the permissions aren't clearly laid out. I want: 1. tell me I install an app that wants "some list of permissions". 2. let me disable this permission for all apps installed now and in the future.

1) it is not really realistic in practice:

- Permissions are requested incrementally at runtime. For large apps, a LOT of these permissions depend on corner cases BUT you still declare all the permissions you might ask for.

So maybe I will declare that I might ask to see the content of your screen .. because there is an help menu where I take a video of your screen to send to support after asking you for the permission.

Same for camera .. we might use Google Pay for most cases, but in one of the countries where we have the app, a local player has a very popular solution that scans your credit card. So we declare that we might need Camera because of this sdk.

Etc.

This is one of the reasons why the previous model where you asked the permissions at install time did not work very well in practice.

Re: Introducing Android 9 Pie

#249

Post by on_and_off »

mmastrac wrote: post #4

One of the quieter features of Android 9 is that they are reducing the API surface of Android by explicitly black-listing and white-listing various APIs and fields that previously required reflection to access. None of these APIs were documented, but none of them were explicitly "off limits" before Android P. That suggests that the life of Java as Android's primary language might be really coming to an end, even thou…

I don't see how you come to this conclusion.

This change is only made because devs used the openness of java in order to access private APIs.

It is ok in some cases, but in others private means private.

Like you would have 'smart' devs manipulating the system resource cache .. even though it is not supposed to be a public API and they can mess up their app very easily if they touch it.

Nothing to do with moving away from Java.

Post reply on HN