Not related but does Google have to pay Oreo money for using its name/image?
Android Oreo
501–510 of 658 posts
Re: Android Oreo
#502Earlier quoted context omitted.
Exactly. I need to customize, so I'll go to Apple, the most user-infantilizing software company on the face of the planet, world-renowned for their repeated refusal to let users tweak the user experience of their $1000 phones on the grounds that some people in a board room in Cupertino know what's best for you better than you do.
They usually know better. I've been iPhone user for 6 years and I've never wanted to customize something. Android, on the other hand, would need a complete customization, redesign and rewrite which I don't have time to do.
Might be a familiarity thing. Been on Android similarly long, and last few years I just stopped customizing because I was happy enough with stock.
Give me an iPhone though and I'd go insane. "would need a complete customization, redesign and rewrite" perfectly describes the iOS experience for me.
Re: Android Oreo
#503Earlier quoted context omitted.
At least they are bringing back PIP. This was such a great regression in N for Samsung users.
PIP somewhat exists already. Some apps, like tinycam already do it.
That's an overlay, rather than using windowing features. And they don't scale quite the same way into full-screen apps. This ought to be easier to implement for most apps since Android itself handles most of the window management and since rendering shouldn't change too much.
Re: Android Oreo
#504Earlier quoted context omitted.
Or even if just gets the chip manufacturers out of the equation, that alone fixes most of the problems. The OEM side is usually pretty easy / trivial in comparison. And there are a number of OEMs who would happily push updates but can't, because they can't get hardware packages from Qualcomm / Amlogic / Freescale / etc. That, more than anything else, holds back new Android releases on lots of hardware.
Supposedly the carriers are real pains as well. I've heard horror stories of months-long approvals processes on Verizon and AT&T ROMs. It's a game I wish they'd get out of entirely. There's no such thing as a useful carrier overlay.
The carriers are not the problem. They may be an additional problem but even when they aren't involved (i.e. outside America) Android updates still suck.
Re: Android Oreo
#505Earlier quoted context omitted.
Apart from what Ironlink said below, there's also the fact that Google and Apple support mean different things. For Apple, updates often mean some subset of the full operating system updates, or a crippled version. Whereas Google updates tend to be all of nothing - meaning if your phone does get the update, it gets all of the features of that particular version. This seems to have changed somewhat with moving a lot o…
No, Apple updates include the full operating system update. The only time features are disabled is when they require hardware that doesn't exist (e.g. you have no finger print reader so you can't use your finger print reader) or they are too intensive for the phones CPU/GPU. That's it. Apple's propensity for hardware accelerators may make this seem like it's crippling (Eg: there is a voice recognition hardware accele…
I think they do. The original iPhone never got MMS support for alleged hardware reasons that were bunk. Siri was originally on the AppStore but once bought by Apple suddenly couldn't run on anything less than an iPhone 4S. There are probably other examples but those are the two I remember.
Re: Android Oreo
#506Earlier quoted context omitted.
Functional planned obsolescence. Hardware vendors will find a way to break hardware abstraction layers... so they can sell more hardware. Its the business model.
I bought a series of Nexus phones. The Nexus 5 no longer works. The Nexus 4 still works, but its battery is puffing out. The Nexus S has no hardware problems at all, but it's too underpowered to run modern software. The model "phone vendors nefariously build products with short lifespans, regardless of what people want to buy, so that they can sell more hardware" has trouble explaining why the longest-lived phones ar…
My phone did died too (Nexus 6P). This doesn't mean all Nexus phones will die within opening the box.
Re: Android Oreo
#507Earlier quoted context omitted.
I remember many years ago when a few carrier and chipset execs stood up on Google I/O stage and announced a new program to ensure Android devices get updated quicker. Nothing came out of that. The proof here will be when they ship. Thankfully, 'Google Play Services' and distributing more and more services through the Play Store is a step in the right direction.
> Thankfully, 'Google Play Services' and distributing more and more services through the Play Store is a step in the right direction. A move towards replacing an open OS with an entirely proprietary solution full of tracking by a single vendor is "a step in the right direction"? There's thousands of solutions for how you can update core OS components, none of them require what Google's doing to open source.
>There's thousands of solutions
Yes, but only if you declare the business models of everyone involved a non-goal.
Re: Android Oreo
#508Earlier quoted context omitted.
Carriers generally have deals with other companies for preinstalled apps which may or may not still be active by the time it comes around for an update. Also they have to test the devices, but considering the sheer number of Android devices they probably prioritize new high end devices first. This problem is made worse on Verizon and Sprint which use CDMA 3G networks, as opposed to the worldwide GSM standard. Also th…
> Also they have to test the devices Why? The whole point of GSM is that carrier and phone can (and should) be entirely disconnected, decoupled and only connected through the means of whatever SIM the user puts in his phone. The notion that a carrier needs to be involved in the making of a phone makes about as much sense as if my ISP needed to test and "approve" what Ethernet hardware I use at home. It's frankly none…
Pretty much any argument for network/device tie-in is fallacious on its face for the simple reason that there are many countries out there which don't have that arrangement. And yet the phones there work fine, and so do the networks.
Re: Android Oreo
#509Earlier quoted context omitted.
Except, of course, getting your hands on a phone that has Oreo. For instance, the Galaxy S8 is the hottest new thing on the market right now, and it launched with Nougat. It will probably be six months to a year before Samsung pushes an Oreo update to it, if at all.
LineageOS is the cure to all ills.
It doesn't help with things like firmware vulnerabilities (without some extensive reverse engineering). I can get LineageOS on my Nexus 5 just fine, but it doesn't have broadpwn fixed.
(note that I wasn't able to actually replicate broadpwn on Nexus 5, if anyone was, some info would be appreciated)
Re: Android Oreo
#510Earlier quoted context omitted.
I would really like to see Google take Oreo as an opportunity to set an example and push the pixel 2 with something like 10 years of support. I am not holding my breath though
That's a pretty unreasonable desire. Technology changes so much in 10 years that it wouldn't be feasible to support a generation of phones for that long. 10 years ago was the original iPhone. How much of a money sink would it have been for Apple to support the original iPhone until now?
And yet, most PCs built 10 years ago can still run most modern software that is written for modern PCs.