3 ms·
Perhaps I'm mistaken, but it was my understanding that if a device manufacturer wanted to license GApps for any of their devices then they had to use an officia
by Reelin 8y ago
Perhaps I'm mistaken, but it was my understanding that if a device manufacturer wanted to license GApps for any of their devices then they had to use an official Android version on all of their devices. In other words, the proprietary license was tied to their (non) use of the AOSP.
- ajross 8y agoThat's exactly correct. At no point was a manufacturer prevented from using AOSP. They were denied a license to the Google apps. So spinning this as "Google says you can't use AOSP" is just wrong. Users of open source software are fine. Proprietary licensees have to negotiate for their licenses and abide by restrictions the IP owner has put on the use. And, yeah, there's an arguable point that at some point those restrictions can run afoul of antitrust statutes. And that's an argument worth having, and my personal opinions are, as I said, mixed on this case. But none of that has anything to do with being able to use Android.
- Reelin 8y agoAhh yes, how could I have been so dense? Google wasn't saying they couldn't use AOSP, just that if they did then they wouldn't be allowed to use GApps. Of course, if you want to be profitable then you have to sell devices. And if you want to actually sell any devices, then you're either going to need to bundle GApps or role your own competitive alternative. And of course rolling a competitive alternative is going to (of necessity) include duplicating the entire Play Store ecosystem. Yeah, totally doable, go right ahead and use AOSP. It's kind of like the Mafia. We're not saying you can't compete with us, we're just saying that if you do compete with us then Tony over here will break both your legs. But of course, you're more than welcome to compete with us if that's what you want to do! I do so love having the freedom to make choices under duress. /s
- ajross 8y ago> Yeah, totally doable, It works for Amazon and the various Chinese clones. Alternatively: why are you mad at Google and not Apple? Apple doesn't let anyone sell a clone device! You're saying that Google needs to be forced to sell the app suite to everyone on even terms, basically. That's not the way business works. There's no "fairness" requirement in contract law, and if you think hard about it you don't really want there to be one. The finding by the EC was based on antitrust arguments, which have nothing to do with fairness and are intended to protect consumers and the market from exploitative monopolies. And for the third ?@!#! time, my feelings there are mixed, and complicated. But your sarcasm doesn't really argue well here.
- Reelin 8y ago> It works for Amazon and the various Chinese clones. It didn't seem to work so well for Amazon from what I could tell. They use AOSP on their devices, yes, but they aren't what I'd call competitive in the smartphone market. The Chinese ones are inapplicable because Google can't (yet) do business in China. If licensing GApps isn't an option in a given market, then everyone is on an even footing regarding its use. > Alternatively: why are you mad at Google and not Apple? I'm not fond of Apple and their walled garden, but I don't pretend to know how you could force them to open things up without being overly heavy handed. That being said, I also don't think they're relevant to this case because there's very clearly competition to them - there are (obviously) very feasible alternatives to buying an iPhone as evidenced by the sales figures. So far you've managed to list three examples as supposed counterpoints, but I don't think any of them are relevant with respect to Google abusing their market position to force the hands of others. On the whole, I don't know of any major vendor of Android devices that does business primarily in the west (EU, US, CA, AUS, ...) and doesn't choose to license GApps. I'd tend to view the complete lack of meaningful GApps competitors in such a large market as clear evidence that it's simply not feasible to compete with them under the dichotomy they force on you. > You're saying that Google needs to be forced to sell the app suite to everyone on even terms, basically. That's not the way business works. There's no "fairness" requirement in contract law, and if you think hard about it you don't really want there to be one. Your statement about fairness (general case) doesn't follow from your statement about Google (specific case). In general, yes, I am well aware that there is no requirement of fairness in the general case; you seem to be making an awful lot of assumptions about what I know and think. Google is very clearly not the general case, and I do think that they need to be forced to license the app suite to everyone on non-abusive terms at minimum. Apparently the EC agrees with me. > The finding by the EC was based on antitrust arguments, which have nothing to do with fairness and are intended to protect consumers and the market from exploitative monopolies. You keep bringing up fairness as though in response to me. I never said anything about fairness. > But your sarcasm doesn't really argue well here. On the contrary, I think it does. My sarcasm was in direct response to your earlier statements such as: * "This is spun terminology." * "So spinning this as "Google says you can't use AOSP" is just wrong." * "But none of that has anything to do with being able to use Android." These all seem comically out of touch to me. Google very much does say that you can't use AOSP so long as you wish to use GApps. As far as I can tell, this is roughly equivalent to saying that you can't use AOSP if you wish to be a reasonably competitive supplier of Android based devices in the west. I see no reason to sugarcoat those terms as anything other than Google very directly saying that smartphone manufacturers can't use AOSP.
- Nomentatus 8y agoExcept that AOSP leaves out the Java Virtual Machine (or equivalent) and most to the actual OS, that's built on it.