81–90 of 130 posts
Earlier quoted context omitted.
Were you aware that Android has built-in tinting capability? It's under Display > Night Light. There's a quick tile for it too.
That is only available on the Pixels, not even on the Nexus 5X (which has similar hardware for that). Since 8.0, it is impossible to get any kind of night light on the Nexus 5X without a custom rom.
Perhaps slightly off-topic, but what are the best hardware/carrier options in USA currently if you want vanilla Oreo that updates reliably instead of a custom ROM (w/ no carrier or third-party overlays and skins)?
Perhaps slightly off-topic, but what are the best hardware/carrier options in USA currently if you want vanilla Oreo that updates reliably instead of a custom ROM (w/ no carrier or third-party overlays and skins)?
I prefer T-Mobile.
Earlier quoted context omitted.
What if I want to present an X button that the user can click to exit fullscreen? How would I do that without a programmable API?
That should be a browser option. (Show exit full-screen button or not.) Also, especially for video, the browser should be able to play it full screen without any distractions. Of course, there are optional enhancements (subtitles, or different audio tracks) driven via JS. And for those the controls have to go somewhere. Ideally, if there were a standard for those, the browser could handle it. (But then we're at the p…
I think you're overreacting to one bad-actor. Inevitably your suggestion here leads to good-actor pages having much less power to present good UI to its users. The browser has to think of all use-cases and have options for that, rather than defining lower-level hooks that pages can do what they want with.
Would it make you feel better that there already many other ways that pages can do user-hostile things? Have you ever visited a page that blocks right-click? Would you want to forbid Mouse Events because of this?
Earlier quoted context omitted.
Thank you for staying level-headed here. This is indeed a gray area question, and it's worth having a debate over. No one is clearly in the right.
Well, the legal answer clearly places one side in the right (the user has the right to modify websites that are shown on their system however they wish to, and the right to circumvent all measures on that site, as in the countless ABP vs. ... cases has been ruled). The historical answer does the same, as browsers were explicitly designated User Agents, as their whole purpose is to act in the name of the user, and ful…
> The historical answer does the same, as browsers were explicitly designated User Agents, as their whole purpose is to act in the name of the user, and fulfill whatever the user wishes to, which also clearly places the will of the user over everything a website may wish to.
The browser is a User Agent, I agree. This doesn't mean they can predict all user hostile behavior and fix it before it ever happens. Browsers often fix bad behaving websites over time. Recently there's been a lot of effort to fix pages that cause scrolling jank when they load ads in the background.
Earlier quoted context omitted.
That would be an excellent way to force Google to switch distribution of all content via YouTube to HTML5 EME with Widevine DRM, given it's pretty clear their music agreements prohibit permitting this.
Most of YouTube content isn't music though. Why are they so user hostile - e.g. why can't I listen to talks/podcasters in the background while browsing the internet?
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…
I've been able to successfully build Android on Arch Linux. Depending on which particular ROM you're building, much of the required build environment is packaged with the source. I just needed repo's dependencies and to rebuild the prebuilt Bison with the included source.
> I've been a bit frustrated with android's sparse docs and unreliable build tool.
The guide at https://source.android.com/source/ should result in a working AOSP build. I've followed it before without problems. My guess is you're trying to do something weird that makes sense to you that isn't really supported.
> Is xda-developers still the main place to go when looking for help, or have any other communities started to overthrow them?
XDA is still the primary place ROM development is carried out, yes. Finding a ROM's IRC channel can be helpful too.
> Is anyone here running their own ROM, or Copperhead in particular?
I built Copperhead for my Pixel but unfortunately it resulted in a bootloop so I gave up on it. I'm running PureNexus right now and might try Copperhead later.
> My only big remaining concern would be with Project Fi; I'm uncertain if the service will work if Google Apps aren't installed.
I don't think it'll work totally bereft of Google services but you might be able to manage it with MicroG: https://microg.org/
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…
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…