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

Android 8.0 Oreo, thoroughly reviewed

arstechnica.com

Post reply on HN
Print view View original

31–40 of 130 posts

Re: Android 8.0 Oreo, thoroughly reviewed

#31

Post by kuschku »

kinlan wrote: post #21
lukepothier wrote: post #11

If it's true that Chrome on Oreo genuinely prevents picture-in-picture for YouTube specifically , that's a troubling precedent to set. Why not allow all websites to enable/disable PiP (maybe via a meta tag, in the way that tab theme colours already work)? If I query https://m.youtube.com while emulating a Nexus 5X, the response contains: Is that what is preventing PiP on YouTube or is it some sort of underhanded inte…

Shared below too. Just as a quick point and I will drop it in the article comments too. I'm the lead for our Chrome Developer Relations team. Chrome doesn't disable picture in picture for Youtube, Youtube disable it in Chrome. They listen to resize events iirc and then exit fullscreen mode (the only way to currently get to pip mode in Chrome).

Then Chrome should have an option to stop the resize handler from firing when entering PiP mode. The user should always have the right to override what the website is doing.

Re: Android 8.0 Oreo, thoroughly reviewed

#33

Post by AndrewDucker »

I knew Project Treble was exciting, but this is really interesting:

>Treble promises to change everything. Malchev says that Treble standardizes Android hardware support to such a degree that generic Android builds compiled from AOSP can boot and run on every Treble device. In fact, these "raw AOSP" builds are what will be used for some of the CTS testing Google requires all Android OEMs to pass in order to license the Google apps—it's not just that they should work, they are required to work.

Ron paints a rosy future here:

>Custom ROMs shouldn't need to be painstakingly hand-crafted for individual devices anymore—a single build should be able to cover multiple Treble devices from multiple manufacturers. Imagine the next time a major new version of Android is released—on Day One of the AOSP code drop, a single build (or a small handful of builds) could cover every Treble device with an unlocked bootloader, with a "download Android 9.0 here" link on XDA or some other technical website.

If this comes to fruition, the ROM community is going to go nuts. This is enormously exciting and Oreo will turn out to be a real turning point for Android.

One thing that is interesting though is the implication that Android updates will get more iOS-y in the future. By that I mean certain features will be missing from updated phones because the HAL layer doesn't support it.

(Copied over from previous discussion here: https://news.ycombinator.com/item?id=15167138)

Re: Android 8.0 Oreo, thoroughly reviewed

#34

Post by kinlan »

kuschku wrote: post #31
kinlan wrote: post #21

Earlier quoted context omitted.

Shared below too. Just as a quick point and I will drop it in the article comments too. I'm the lead for our Chrome Developer Relations team. Chrome doesn't disable picture in picture for Youtube, Youtube disable it in Chrome. They listen to resize events iirc and then exit fullscreen mode (the only way to currently get to pip mode in Chrome).

Then Chrome should have an option to stop the resize handler from firing when entering PiP mode. The user should always have the right to override what the website is doing.

So you would like us to not tell the page what the render is doing? I'm not sure how that would play out for any number of API's that exist on the web. Developer's have consistently had the means to override the default actions of the browser (think drag and drop) but I don't think hiding side-effects or user actions helps anyone.

Re: Android 8.0 Oreo, thoroughly reviewed

#35

Post by dinnouti »

lukepothier wrote: post #11

If it's true that Chrome on Oreo genuinely prevents picture-in-picture for YouTube specifically , that's a troubling precedent to set. Why not allow all websites to enable/disable PiP (maybe via a meta tag, in the way that tab theme colours already work)? If I query https://m.youtube.com while emulating a Nexus 5X, the response contains: Is that what is preventing PiP on YouTube or is it some sort of underhanded inte…

Wondering if relate to YouTube Red sales.

Re: Android 8.0 Oreo, thoroughly reviewed

#36

Post by grepthisab »

Jedd wrote: post #20

After my Pixel updated recently to Oreo, being frustrated by a constant notification for Twilight (a red-tinting background app) and starting to search on google for a solution -- I discovered quite a lot of people have been asking 'how to suppress notifications on oreo' recently. FWIW you can control the notification snooze timeout, but you're going to need Tasker [1] (or similar). Interestingly I evidently bought t…

In the middle of updating my Pixel XL, use Twilight daily. Will it still work after the update?

Re: Android 8.0 Oreo, thoroughly reviewed

#38

Post by TheAceOfHearts »

How many people build their own ROMs? When I bought my Pixel I tried my hand at building my own ROM, but I kept stumbling and eventually gave up. Admittedly, I was running a newer version of Ubuntu than the one they suggested in the docs, but I didn't expect it would break everything. Am I right in guessing that using a VM would be the easiest path to success?

I've been a bit frustrated with android's sparse docs and unreliable build tool. Whenever I try searching for additional information, all I find are questionable tutorials and xda-developer threads. I don't have anything against the forum itself, but I find it a bit questionable to see so many people happily propagating and flashing random binaries. Is xda-developers still the main place to go when looking for help, or have any other communities started to overthrow them?

Now with 8.0 out, it seems like a good chance to retry building my own ROM. I'm thinking of forking CopperheadOS [0], and applying some minor patches on top. Is anyone here running their own ROM, or Copperhead in particular? I'd love to hear about your experience, along with any pros and cons. F-Droid seems to be capable of handling all of my requirements. My only big remaining concern would be with Project Fi; I'm uncertain if the service will work if Google Apps aren't installed.

[0] https://copperhead.co/android/

Re: Android 8.0 Oreo, thoroughly reviewed

#39

Post by avaer »

kinlan wrote: post #34
kuschku wrote: post #31

Earlier quoted context omitted.

Then Chrome should have an option to stop the resize handler from firing when entering PiP mode. The user should always have the right to override what the website is doing.

So you would like us to not tell the page what the render is doing? I'm not sure how that would play out for any number of API's that exist on the web. Developer's have consistently had the means to override the default actions of the browser (think drag and drop) but I don't think hiding side-effects or user actions helps anyone.

I'd like to be able to tell my browser what it should tell the pages it's loading, especially if pages are leveraging it to do things against my will.

That applies to blocking Google ads, as well as fixing Youtube malfeatures.

Of course, it's understandable you won't see this from a browser paid for by Google. But you can't paint in broad brush strokes like "I don't think hiding side-effects or user actions helps anyone."

Re: Android 8.0 Oreo, thoroughly reviewed

#40

Post by Mindwipe »

vanderZwan wrote: post #8
mtgx wrote: post #3

Keeping my fingers crossed that Project Treble is the real deal and would actually make it possible for a "generic AOSP image" to be installed on virtually any mobile device that came with Android. That's the dream, isn't it? But I think we've been burned too many times by Google's promises to "make it easier" for OEMs to update devices and other such promises, or at least these projects always sounded much better th…

Is Project Treble "backwards compatible" with old models? If so I hope it will work out for Fairphone users, especially the first model which is doesn't receive as much support as the Fairphone 2

No. In theory you could backport it to older phones, and OEMs allegedly might, but I wouldn't expect that to be the norm and it's not mandatory from Google in order to get Oreo.
Post reply on HN