Slashdot Mirror


Google Fights Back Against Android Fragmentation

bonch writes "Google is tightening its control over Android in an attempt to standardize the platform. Licensees must agree to a 'non-fragmentation clause' that gives Google final approval over operating system changes, allegedly sparking complaints to the Justice Department. This follows Google's recent decision to withhold the source to Honeycomb from non-privileged partners, a move that has drawn criticism from openness advocates. Google says that Honeycomb will be open sourced when it's ready for other devices."

33 of 373 comments (clear)

  1. Good thing it is open by Anonymous Coward · · Score: 4, Insightful

    Well, mostly open. Except when it isn't.

    1. Re:Good thing it is open by maxwell+demon · · Score: 2

      About not releasing before it's ready: They are doing closed development. That's actually the mode the FSF has traditionally worked in (note that this was one of the reasons for the egcs fork of gcc), therefore it quite obviously doesn't make the code less open source (or even less free software), although it makes for a less open development model.

      However the restrictions to approved modifications might indeed make the code less open source, however it depends on how they are doing it. If they say "OK, you can get the code early, but then you may not make arbitrary modifications" then AFAICT the phone makers don't get open source (because they get it with restrictions which are incompatible with open source). However if the restriction is "if you make any unapproved changes, the next time we will not give you the code early" it certainly doesn't interfere with the code being open source (because they can change anything they want for the code they get), despite the net effect being almost the same.

      There are many aspects of open, and open source is only one of them.

      --
      The Tao of math: The numbers you can count are not the real numbers.
    2. Re:Good thing it is open by Tacvek · · Score: 2

      Any device that uses uses a (modifed) version of Android Operating system May claim to be running Android. If they meet the requirements of the Computability Definition Document for Android X.Y, they are permitted to claim that they are Android X.Y compatible. This has not changed and will not change.

      If you want early access to the latest versions of the OS, or if you want to include the official Google Apps or the Android Market, then you have additional rules. Google has simply tightened these rules. If you want to go crazy and create something weird you still can. You simply must wait for the source release, or base your changes on the previous version.

      --
      Stylish sheet to fix many problems in Slashdot's D3: https://gist.github.com/801524
    3. Re:Good thing it is open by rtb61 · · Score: 2

      Google is making a mistake. It simply needs to show a little patience. Companies that stray to far off the reservation, the android comparability reservation will soon find themselves punished by their customers and that punishment will likely doom their products for quite a long time.

      Rather than tightening up and enforcing those rules, it simply needs to evaluate the comparability of products and publicly declare any problems with them. Google needs to make better use of the Android brand and the whole concept of 'android digital fusion' and for example bringing more end users to the android web site as part of that digital fusion.

      --
      Chaos - everything, everywhere, everywhen
  2. The Case for Google's Control: Atrix by paulsnx2 · · Score: 4, Informative

    Motorola's "enhancements" to Android make the Atrix nearly unusable. My wife moved from the iPhone to the Atrix, and it is only because Android does allow customization that I was able to download enough skins and fixes to make the phone usable.

    AT&T wants to push their useless buggy navigation to the Atrix, despite the fact that Google's navigation works just fine.

    All in all, the fresh and clean Android I have on my Nexus One is almost completely corrupted by Motorola and AT&T on the Atrix, and this isn't done because it is in the interest of the customer. This a push of crapware onto the customer serving interests at Motorola and AT&T

  3. The ultimate irony by webrunner · · Score: 4, Interesting

    Google wants to close android in order to keep the manufacturers from closing android further.
    Openness advocates are fighting to protect the rights of the manufacturers (that of closing Android)

    I'm not sure who to root for here, so I'll just say GO LOCAL SPORTS TEAM

    --
    ADVENTURERS! - ANTIHERO FOR HIRE - CARDMASTER CONFLICT
    1. Re:The ultimate irony by ceoyoyo · · Score: 3, Insightful

      "Google wants a kind of openness which is good for everyone, especially including Google."

      Right. Google wants what is good for Google. That is, they want Android on lots of devices so they can sell lots of ads.

      Google thought making Android open source would be the best way to accomplish that, and it's worked pretty well so far. Except for this little bobble with fragmentation. Google couldn't care less whether you can upgrade the OS on your phone, or customize it as you wish. Actually, they probably prefer you can't, because hardware upgrades keep the manufacturers happy (more of them will use Android, more ads for Google) and no end user modifications prevent you from blocking their ads.

      Notice how Google ISN'T making an issue out of carriers and manufacturers locking down Android phones.

    2. Re:The ultimate irony by GooberToo · · Score: 2

      Actually, its to Google's own advantage to encourage devices to become upgradable. They've already suffered as a result of manufacturers and carriers dragging their feet. It hurts Google, it hurts developers, it hurts the the platform, and ultimately their revenue by falling behind in competition. Having said that, pragmatically, they do not make up the entire ecosystem. That means fighting the good fight but picking your battles. You can't alienate your jockeys on an unproven horse, right out of the gate. Assuming that's even possible is silly.

      Like it or not, Google must make concessions, especially right out of the gate, to allow for the platform's adoption; especially early on when it was completely unproven. Exactly what the tug-of-war will look like tomorrow, while I suspect Google has plans, I seriously doubt even they know. Regardless, it is shaking up the market to varying degrees for everyone's benefit.

      The only way Google can change the market is to work within the market. And doing so means working with the established players (carriers). Attempting to change the market from within doesn't automatically make them the enemy. I wish people would stop being so narrow minded and turn off their black and white vision and understand, the world is complex and they are very much attempting to change the status quo from very anti-competitive and entrenched players. In what way are these concessions and struggles not all but demanded?

    3. Re:The ultimate irony by fermion · · Score: 2
      Android is becoming closed because Google want to make sure it continues to serve the Google doctrine, that is the ability to run Google branded content and present said Google branded content continuously to users.

      With carrier level innovation, the real and present danger is that carrier will include equal or superior applications, will not liscense equal or inferior application from Google, and the Google brand will suffer. We see this best with Honeycomb. This is a new platform which could provide a rich development environment for developers everywhere, but Google is so scared that someone might create a better base that does not run Google, they keep it closed.

      --
      "She's a scientist and a lesbian. She's not going to let it slide." Orphan Black
    4. Re:The ultimate irony by GooberToo · · Score: 3, Informative

      Its a straw man because you're full of shit.

      Android 3.0 is not closed source. Android 3.0+, just as with all previous versions of Android, is part of a closed development process. Those are two entirely different things. Google has made it clear once they finish with their targeted 3.x features, it will be released from their closed development model.

      Closed development is in no way the same as closed source. To suggest they are one in the same is to validate one as either an idiot or a troll; whereby they are not mutually exclusive possibilities.

      So yes, absolutely, your statement is a straw-man because your statement means ALL versions of Android are closed source and factually we know your assertion to be full of shit.

    5. Re:The ultimate irony by wrook · · Score: 2

      But they released a binary. I can buy a Motorola Xoom and I can't get the source code. Thus it isn't open source.

      Of course we all believe it will become open source in the future. That's not the point. They have released it and refuse to give their customers the source code. Their customers can't inspect it for problems, learn from it, modify it, fix bugs, adapt it for their purpose or redistribute it. Even though they have bought a device containing the binary. Kudos that they intend to open source it in the future, but it is not open sourced now, by anyone's definition.

    6. Re:The ultimate irony by Daengbo · · Score: 2

      They gave Motorola the source code. It's open source there (only customers who receive binaries are required to receive the source under OSS rules). Did Motorola give it to you? Since the Apache 2.0 license is permissive, Motorola can choose to close it or not. Apparently, they did. Welcome to permissive licenses. This is why I prefer GPL, but many people disagree with me and I respect their opinions.

  4. Well they have a point by trollertron3000 · · Score: 3

    As much as I love Open Source I can see their point and I can't counter it. If we continue this fragmentation is it really going to benefit android or will it cause harm? If the goal is usage, which it is, then this is one way to enforce some standards and drive that goal. If the goal was software freedom it would be another story. But we knew this going in, it was never the goal.

    --
    Tiger Blooded Bi-Winning Machine
    1. Re:Well they have a point by bryan1945 · · Score: 2

      I am interested how people will respond to your point. Apple locks down their iPhone/iPad/whatever for this reason, and /. freaks out. How will /. respond to Google starting to do the same? I have no pony in this race, as I have a mere dumbphone and no pad/tablet of any type.

      --
      Vote monkeys into Congress. They are cheaper and more trustworthy.
  5. Easy solution by MDillenbeck · · Score: 5, Insightful

    Allow the manufacturer to customize the hell out of it, but write into the license agreement that all functionality must work a vanilla install that is made available OTA. That way a user can go into the update menu and select "update to latest Google version of Android supported by your phone's hardware WARNING: ALL MANUFACTURER CUSTOMIZATION WILL BE LOST". When on vanilla, make the latest manufacturer switchover available. If they did this, how many of us would still be on 2.1 or 2.2? That would be the best of both the worlds.

    1. Re:Easy solution by scragz · · Score: 2

      Allow the manufacturer to customize the hell out of it, but write into the license agreement that all functionality must work a vanilla install that is made available OTA. That way a user can go into the update menu and select "update to latest Google version of Android supported by your phone's hardware WARNING: ALL MANUFACTURER CUSTOMIZATION WILL BE LOST". When on vanilla, make the latest manufacturer switchover available. If they did this, how many of us would still be on 2.1 or 2.2? That would be the best of both the worlds.

      It could be YEARS before Vanilla is released. They're only on Gingerbread!

  6. Re:The Case for Google's Control: Atrix by ceoyoyo · · Score: 4, Insightful

    So? Isn't the point of open source that other people can take it and modify it to try out ideas?

  7. Re:The Case for Google's Control: Atrix by tepples · · Score: 5, Insightful

    The problem comes when all three carriers force bad ideas on their customers.

  8. im curious to know by nimbius · · Score: 2

    could GPLv3 have perhaps prevented in some way this "fragmentation" problem?

    --
    Good people go to bed earlier.
    1. Re:im curious to know by ceoyoyo · · Score: 2

      Why would Google want to prevent locked phones? That would piss off the carriers and manufacturers making Android phones and they might decide to use some other OS instead. Then Google couldn't sell as many ads.

    2. Re:im curious to know by Rich0 · · Score: 2

      He could require GPL v2+ on all new patches, so that at least the 2+-compatible codebase grows over time - thus fixing itself eventually once v2-only code is phased out, or becomes small enough to be replaceable or get a few author approvals here and there.

  9. Re:The Case for Google's Control: Atrix by TheCRAIGGERS · · Score: 3, Informative

    That would be a good point if I could take my phone and modify it. Motorola also has a pretty firm stance on locking down the system so I can't get at it.

  10. Good by rwa2 · · Score: 2

    The manufacturers were really getting out of line. With every Android device I've purchased so far, the first thing I've had to do was replace them with a custom ROM that was closer to Google's core release. The manufacturer's junk (HTC Sense, Viewsonic TnT, etc.) was really getting in the way.

    TFA points out that the non-fragmentation clause was always there, Google is just trying harder to enforce it nowadays.

  11. Powered by Android (TM) by mojotoad · · Score: 2

    Why not do something like THX used to do for theater sound systems? Trademark the 'official' powered-by-android phrase, run a certification program, let the vendors customize all they want -- they get to use the OS but not necessarily the 'brand'.

  12. Allow fragmentation, but without the trademark by Midnight+Thunder · · Score: 5, Interesting

    Google could reserve the Android trademark for non-fragmented distributions. This would make handset manufactures make the choice between keeping the brand recognition of the Android OS or going it on their own and losing that right and any support that may go with it. The attitude could hurt Google, but it would probably hurt handset manufacturers more as people decide they want the security of a platform with less surprises.

    Technically no one can really stop Android from being forked, but at the same time there is nothing stopping Google preventing you from being able to use their trademark.

    --
    Jumpstart the tartan drive.
  13. So... there is fragmentation after all. by DerekLyons · · Score: 2

    So, after all the statements from Google and comments here on Slashdot insisting there was no fragmentation - now Google wants to prevent what isn't happening from happening.

    How 1984 of you Google.

    1. Re:So... there is fragmentation after all. by Americano · · Score: 2

      Then you haven't been reading Slashdot much. Every time someone makes a comment about Android being fragmented, they get jumped on by a half a dozen True Believers who loudly and crudely remind us that "Android isn't fragmented, that's just bullshit FUD being spread by Apple fanbois who are scared that Android is beating their pet product."

      Call it by whatever name you want, the tone here on Slashdot has been:
      1) There is no fragmentation, that's just FUD;
      OR
      2) It's not fragmentation, it's diversity & variety, and that makes for a healthy ecosystem!

      But now that Google is trying to "control fragmentation", the tone seems to have changed to "Oh what a great thing, this will really prevent many problems for Android developers and users." Google is addressing a "problem" that, according to the Android fans, either did not exist or was not a problem, but was, in fact, the hallmark of a healthy device ecosystem.

      Either way, reading the reversal of opinion here is rather breathtaking.

  14. Re:The Case for Google's Control: Atrix by PopeRatzo · · Score: 2

    with android the carriers make money on the accessories, ad revenue sharing, the crap ware and the monthly insurance that some people buy

    Excuse me, but I thought that the "carriers" made money from carrying calls and data.

    This is a very clear example of why we need Net Neutrality laws and why "carriers" should not be allowed to become content providers, advertising companies, insurance companies, or software developers.

    Here's a novel concept: The Justice Department needs to do its job and start busting up these "carriers" that now want to become media companies, advertising agencies, insurance companies and software developers. There are laws against such anti-consumer behavior by these enormous corporations. And while we're at it, how about we make them pay their tax bills?

    --
    You are welcome on my lawn.
  15. Re:The Case for Google's Control: Atrix by Rich0 · · Score: 2

    I'd say dozens of distros is the reason linux is as successful as it is. Imagine of slackware were your only choice, and things like RHEL, Arch, Debian, Gentoo, or Ubuntu were legally forbidden?

    The issue with android isn't that it is fragmenting, but rather that carriers make forks and then prevent customers from having a choice. What Android really needs is GPLv3.

  16. Re:The Case for Google's Control: Atrix by LoganDzwon · · Score: 3, Insightful

    unless you can't, since the openness applies to the manufacture, and they choose if they pass that onto you, or sign the firmware and lock the boot loader.

  17. This is total bullshit by DrJimbo · · Score: 3, Interesting

    I smell Microsoft.

    Go here to download the Android source code. Then read the license here:

    The preferred license for the Android Open Source Project is the Apache Software License, 2.0 ("Apache 2.0"), and the majority of the Android software is licensed with Apache 2.0. While the project will strive to adhere to the preferred license, there may be exceptions which will be handled on a case-by-case basis. For example, the Linux kernel patches are under the GPLv2 license with system exceptions, which can be found on kernel.org.

    As others have already suggested, the FSF friendly way to "gain control of and final say over customization" is through the trademark, not the software license. There is no evidence in this article that this is not the path Google is taking, yet we got a plethora of posts saying "On noes! Google has become evil!".

    You know the funny thing? This is yet another example when Google does something very good (standing against software patents in this case) and then gets slamed with make-believe charges that they are doing something evil. It is clear, to me at least, that is is just another foray in Microsoft's attacks on Google because they know they can't complete technically. It's like this decade's version of what was reported in the Halloween documents

    --
    We don't see the world as it is, we see it as we are.
    -- Anais Nin
  18. Re:The Case for Google's Control: Atrix by dafing · · Score: 4, Insightful

    See, I remember all the Android arguments, "ITS FREEEEEEE!1!1!" when I mentioned having an iPhone. I love my phone, its slick, built like a piece of jewellery, very fast, takes gorgeous photos, it works great.

    The supposed argument for "open" would be that "all the bad carriers will get kicked out, people will get fed up with their bullshit products, and go to another vendor. Consumer choice!"

    Erm, no. The US market is already among the worlds worst for carriers, seriously, here in New Zealand - basically any other developed nation - I take my Micro SIM out, flip in a new one from any of the three major carriers, and it Just Works. I bought my phone outright, but even "on contract" phones are sold "unlocked" in NZ.

    The reality is, "The Free Market" involves crooked deals among The Big Boys, ie Google giving out favours to Manufacturer X, so they get "The Best Phone", often with an exclusive new version of the OS, while the others - including other very big companies, some of which were the FORMER poster child - have to quietly whine, and wait for the new update, if it comes at all.

    Think about the number of "Android device makers", how many are actually worth shit? I'd think about five, max! HTC, Motorola, perhaps Samsung (very high end tech in some ways, utterly crap quality in others).... hell, off the top of my head I only got three that I'd consider decent. The rest seem to be "clone phone" makers, the same crap, competing on price, "gotta make if five dollars cheaper than the other guy".

    And they all come loaded with BS! Except for the "stock" phone, which is what I'd go for. Oh, but theres not currently a "stock" phone with the larger screen? With a dual core CPU? So, people might be lured away from The Righteous Path, into crapware oblivion.

    The majority of people seem to put up with the awful ads, the programs you cannot delete (without superpowers), they take it as a given.

    Its the new version of "intel inside", everyone wants their little medals to show up, to build brand recognition, to profit from the consumer.

    I'd rather have a "free market with rules", with a Google who sets limits, ie no trial apps that work for 15 days, then ask you for ten dollars, that will otherwise remain on your phone undelete-able for eternity.

    If you're an Android user, speak up about this! Send a polite complaint email to the manufacturer, I dont think they will care about "your phone is the sux coause the motorolas has the sweet as screen...", and lets get people INTERESTED about how their devices SHOULD work!

    --
    --- ...or a new slashdot signature. Dear aunt, let's set so double the killer delete select all
  19. trademark vs code by Kevin+Fishburne · · Score: 2

    They probably are only now allowing the use of "AndroidTM" when they've personally approved the chain of compilations to make a smartphone OS. Anyone may still use the code however they want, but to use the trade name they must comply with Google's requirements. Vendors would have to choose between releasing their Android phone without the name or a touch of compliance so they'd get to use the trademark. Sorta like Element, the distro.

    --
    Buy your next Linux PC at eightvirtues.com