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."

373 comments

  1. Fragmented Android by Anonymous Coward · · Score: 1

    The last fragmented android I saw was on Dagobah.

    1. Re:Fragmented Android by DurendalMac · · Score: 1

      I think you mean the Cloud City on Bespin, you charlatan!

    2. Re:Fragmented Android by FauxPasIII · · Score: 1

      Feh, that was a LONG time ago. There was one much more recently in the Kolaran system.

      --
      25% Funny, 25% Insightful, 25% Informative, 25% Troll
    3. Re:Fragmented Android by h00manist · · Score: 1

      The last fragmented android I saw was on Dagobah.

      I thought it got fixed in the POSIX repair shop. Then by the LSB mechanics. And finally it was fixed by the Java traders on Tatooine. It's still not fixed? Why is the GoogooPlex Star irate?

      --
      Build your own energy sources from scratch. http://otherpower.com/
    4. Re:Fragmented Android by An+ominous+Cow+art · · Score: 1

      My first thought upon reading the phrase "Android fragmentation" was of Chewbacca carrying a sack full o' protocol droid parts. I'm glad I'm not the only one. :-)

  2. 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 FatdogHaiku · · Score: 1

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

      I had a wife like that...

      --
      You have the right to remain sentient. If you give up the right to remain sentient, you will be elected to public office
    3. Re:Good thing it is open by AvitarX · · Score: 1

      Most likely they say:
      No Google Apps (not open at all), and no Android name (probably a trademark).

      --
      Wow, sent an e-mail as suggested when clicking on "use classic" banner, and got a fast response that addressed my msg
    4. Re:Good thing it is open by rolfwind · · Score: 1

      They're probably doing this via copyright, "If you make changes we don't approve, you won't get to stamp it with android nor use any android copyrighted artwork in your derivative OS." Or something like that.

    5. Re:Good thing it is open by VulpesFoxnik · · Score: 1

      Exactly what Mozilla did to Debian actually.

      --
      RES PUBLICA NON DOMINETUR
    6. Re:Good thing it is open by Hognoxious · · Score: 1

      Momma always said, "Open is as open does. Like a box of chocolates that's been opened."

      Man, she was a silly old cow.

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    7. Re:Good thing it is open by PReDiToR · · Score: 1

      So as Firefox is to Ice Weasel, Android will be to Cyborg?

      Cyborg because it's Android with a human element, not a corporate one.

      --

      Do not meddle in the affairs of geeks for they are subtle and quick to anger
    8. Re:Good thing it is open by IB4Student · · Score: 1

      Mozilla is fixing their ****. MPL 2 is going to be GPL compatible.

    9. Re:Good thing it is open by Moryath · · Score: 1

      Ok, here's part of the problem:

      for every "android" app, there are a hundred or two hundred devices that developers have to hope it works on. I've had a few that didn't work on my phone already.

      Not only that, but some companies are pulling shitty tactics on the consumer. Want to have tethering on your Android phone through Sprint? They want an extra $30 per month. Or you can just temp-root it and use free tethering software. Oh yeah, and Sprint's sales reps are actually bringing up the rooting option because so many customers have been pissed off about the extra "tethering subscription" ass-hattery that they have given up on trying to sell it.

    10. 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
    11. Re:Good thing it is open by larry+bagina · · Score: 1

      Mozilla's code has been tri-licensed as GPL, LGPL, or MPL for a while. "Mozilla Firefox" and the logo are trademarks. Debian doesn't have a problem distributing copies of the GPL text, which is not under a FREE license.

      --
      Do you even lift?

      These aren't the 'roids you're looking for.

    12. Re:Good thing it is open by dragonturtle69 · · Score: 1

      Yep, the Android OS needs to get stable, and the hardware underneath it, or does it?. Google Platform Versions shows 2.2/API8 as the largest group, but that will change, again. Linux Devices has a more complete summary article. I say "does it" as the diversity of hardware did not hurt Microsoft. If anything it hurt Linux users trying to migrate off cheaper Windows hardware (Winmodems are first in mind).

      Off Topic: My phones get a 60 day warranty bake in before being rooted (it is my hardware, don't lock it). Having the backup modem for the laptops is just a plus. The CDMA Nexus S may change that thought on rooting, but then I would have to pay the extra $30. That $30 may cost Sprint a sale on a Nexus S and a Evo 3D. For my 1-2GB per month with only limited backup modem usage, $30 is too much.

      OTOH, I know two small business owners who thought that the EVO would make a nice WAP, as in drop business DSL and use their phone for the office laptops. I guess the suits at Sprint chose charging extra to have the tethering feature easily available over capping or tiered usage plans.

      --
      "What luck for the rulers that men do not think." - Adolph Hitler
    13. Re:Good thing it is open by Daniel+Phillips · · Score: 1

      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.

      Absolutely wrong. Your EGCS example directly refutes your argument: the open fork won in features, efficiency, stability and pace of development. Likewise xorg won over xfree. Degree of openness does matter, and Google is heading in the wrong direction, both for them and us.

      --
      Have you got your LWN subscription yet?
    14. 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
    15. Re:Good thing it is open by dargaud · · Score: 1

      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.

      I wish it was that easy. I got 2 android phone: the 1st one is stock android and it's great. 2 years later it's still receiving regular system updates. The other one was modified by the carrier and it's pure garbage (can't change homepage in browser, no bookmarks, no tethering, can't disable data, no updates ever...). I wish there was a large simple sticker on the box that said: "pure android" vs "rendered useless by the carrier".

      --
      Non-Linux Penguins ?
    16. Re:Good thing it is open by Clsid · · Score: 1

      I respectfully disagree. Fragmentation is becoming an issue and it's being reflected on the complaints of many programmers. They pretty much point out that developing for iOS is a lot easier than developing for the myriad of Android versions. That and the fact that the Apple's App Store sells more really doesn't leave too much room for Google to make it harder for everybody else.

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

      Absolutely wrong. Your EGCS example directly refutes your argument: the open fork won in features, efficiency, stability and pace of development.

      Which, while true, is completely unrelated to the question of being open source. The original gcc was open source, despite of its closed development model (otherwise egcs would not have been possible).

      Degree of openness does matter

      Yes, an open development model is better than a closed development model. But that's orthogonal to being open source.
      Also, following open standards is generally better than not following them (unless those open standards are genuinely bad). But yet you can write open source software which doesn't follow any standard, and closed source software which follows the standard religiously. And of course you can write software following open standards using a closed development model and vice versa.

      As I wrote, there are many aspects of open, and open source is just one of them.

      --
      The Tao of math: The numbers you can count are not the real numbers.
    18. Re:Good thing it is open by Daniel+Phillips · · Score: 1

      If you want to define "open source" strictly according to the Open Source Definition then you are correct, and I need to be careful about using that term because in that sense it is very narrow. Up till now, by "open source" I have meant not the letter of the OSD definition, but the development model. While Google does use open source licenses, it very much does not like or use the open source development model. And in that Google causes a great deal of harm to both itself and the community.

      In my opinion, the license is just one part of what the world commonly understands to be "open source". However I will be careful in future to be specific about whether I mean a kind of license, a community, or a development approach.

      --
      Have you got your LWN subscription yet?
    19. Re:Good thing it is open by jsvendsen · · Score: 1

      I say "does it" as the diversity of hardware did not hurt Microsoft.

      This diversity of hardware is nothing like what Microsoft had to deal with. Microsoft had to deal with a multitude of vendors providing devices that resulted in, more or less, some combination consisting of a processing unit, graphics hardware, a screen, a keyboard, a mouse and a sound card. Android is supporting a multitude of devices that may or may not provide one or more of the following: a screen, a capacitive touchscreen, a resistive touchscreen, gsm hardware, gps hardware, 3g connectivity, wlan connectivity, ethernet connectivity, a physical keyboard, no physical buttons at all, any number of physical buttons offering any random functionality, sound hardware capable of reliable voice input, a useless simplistic microphone, lots of internal memory, little internal memory, limited internal memory with optional extension. I could go on.

      The point is that if someone tried to put Windows on something, it was a PC. If someone tries to put android on something, it could be anything from a toaster/washing machine/fridge through a headless server through a laptop through any imaginable kind of phone through a tablet pc. Creating a system that performs reasonably well in all those use cases involves more than just writing plenty of drivers for a lot of different hardware.

    20. Re:Good thing it is open by node+3 · · Score: 1

      About not releasing before it's ready: They are doing closed development.

      We're not talking about a closed development process, but a closed distribution process.

      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.

      No, that's exactly what it makes it. The FSF does not distribute closed source software. Android 3.0 is closed source.

      However the restrictions to approved modifications might indeed make the code less open source, however it depends on how they are doing it.

      No, the fact that you can't get the source makes it less open source.

  3. 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

  4. 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 AnotherScratchMonkey · · Score: 1

      If Android closes, I lose my incentive to avoid Apple's iOS. Google and the manufacturers need to understand that openness is the only real distinction they have over their competition, and that closing the platform loses their differentiation.

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

      That's an easy one. You want to root for Google. Google wants a kind of openness which is good for everyone, especially including Google. The manufacturers want an openness which is only good for them and bad for everyone else; basically attempting to reshape Android back into the status quo.

      With Google's solution, everyone wins to some degree except the manufacturers. With the manufacturers, only the manufacturers win and everyone else loses.

    3. Re:The ultimate irony by bemymonkey · · Score: 1

      It's easy - which team wants to keep Android open for you as the end user?

      Which team wants to lock everything down so they can continue to charge 20 cents for 140 characters of text?

      I'll take the "closed" Google version of Android, thanks :)

    4. Re:The ultimate irony by Local+ID10T · · Score: 1

      If Android closes, I lose my incentive to avoid Apple's iOS. Google and the manufacturers need to understand that openness is the only real distinction they have over their competition, and that closing the platform loses their differentiation.

      You are missing the point. Google's license will restrict the vendors ability to customize the OS, not the end-users. You can still root your phone and modify it as you please.

      --
      "You want to know how to help your kids? Leave them the fuck alone." -George Carlin
    5. Re:The ultimate irony by ceoyoyo · · Score: 1

      Except when they don't bother releasing the code at all.

    6. Re:The ultimate irony by Local+ID10T · · Score: 1, Funny

      Nice straw man...

      --
      "You want to know how to help your kids? Leave them the fuck alone." -George Carlin
    7. 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.

    8. Re:The ultimate irony by jewelises · · Score: 1

      I imagine that google is just going to restrict the use of the android trademark, not source code. This seems like a sensible solution, and won't restrict the rights of the manufacturers.

    9. Re:The ultimate irony by twistedsymphony · · Score: 1

      do you honestly believe that 95% of the people buying Android phones give 2 shits about Openess? Most of them probably don't know what that is... Heck I'm the biggest open-source advocate I know and that didn't even factor one iota into my decision to buy an Android phone.

    10. Re:The ultimate irony by ceoyoyo · · Score: 1

      Oh, someone said "straw man." That must mean an insightful post... oh right.

      Honeycomb, and it's withholding, was mentioned in the SUMMARY.

    11. Re:The ultimate irony by the+linux+geek · · Score: 1

      How? Android 3.0 is closed-source. Where's the straw man?

    12. Re:The ultimate irony by AnotherScratchMonkey · · Score: 1

      So why'd you buy an Android phone, then?

    13. Re:The ultimate irony by maxwell+demon · · Score: 1

      Well, if the goal is only keeping the manufacturers from closing it further, then a "non-closing" clause would be sufficient (e.g. demand that every phone running Android-derived code must give the option to change to an unmodified version of Android without voiding the warranty).

      --
      The Tao of math: The numbers you can count are not the real numbers.
    14. Re:The ultimate irony by Anonymous Coward · · Score: 0

      "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.

      How dare Google make their product more open just so their customers will like it!

      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.

      Except that being customizable is what separates Android from its biggest competitor, and it's a large portion of what keeps Google's legion of fans on their side.

    15. Re:The ultimate irony by bemymonkey · · Score: 1

      If anything, this move should make you want to switch to Android even more, as it will free you (the end user) from the customizations foisted upon you by manufacturers and carriers...

    16. Re:The ultimate irony by Anonymous Coward · · Score: 0

      Why? So you can be forced to watch an ad before you see your 140 characters of text that still cost you $.20?

    17. 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?

    18. Re:The ultimate irony by ifrag · · Score: 1

      do you honestly believe that 95% of the people buying Android phones give 2 shits about Openess?

      Obviously the general public does not care about that. What the public DOES care about is the phone doing what they need / want it to do. When people see certain apps / features work on another android phone but not theirs then that is when people will give a shit. Only problem being if the vendors are all shipping crippled phones that contrast becomes much more subtle.

      --
      Fear is the mind killer.
    19. 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
    20. Re:The ultimate irony by amRadioHed · · Score: 1

      I bought mine because it's a good phone.

      --
      We hope your rules and wisdom choke you / Now we are one in everlasting peace
    21. Re:The ultimate irony by Anonymous Coward · · Score: 0

      Yeah, the author of that Ars Technica piece, Ryan Paul, is such an Open Software advocate that he recently switched from Linux to OS X.

      Nothing but FUD and opinion pieces from Ars when it comes to Android.

    22. Re:The ultimate irony by alex67500 · · Score: 1

      Well... I know most people will tell me to geek-up and do it myself, but I'm waiting for the HTC-customised version of Gingerbread to hit my Desire Z(*), and it's been a while now. Maybe if it wasn't so much customised it would already be available. So hell yes, go Google on that one!

      (* yes, I really wanted that keyboard, and it's a good thing some manufacturer thought about making one. about time too)

    23. Re:The ultimate irony by amRadioHed · · Score: 1

      If Google prefers that you can't update or customize your phone, why are the phones with Google's name on them the ones that are the most frequently updated and easiest to customize.

      --
      We hope your rules and wisdom choke you / Now we are one in everlasting peace
    24. Re:The ultimate irony by Anonymous Coward · · Score: 0

      Except that being customizable is what separates Android from its biggest competitor, and it's a large portion of what keeps Google's legion of fans on their side.

      Right, that's what most consumers care about. Not that their phone just works and has the same apps as their friends.

    25. Re:The ultimate irony by uniquename72 · · Score: 1

      So why'd you buy an Android phone, then?

      At the time I got the EVO: cheaper than iPhone, faster than iPhone, better coverage than iPhone, free turn-by-tun navigation.

    26. Re:The ultimate irony by Inner_Child · · Score: 1

      Oh, someone said "straw man." That must mean an insightful post... oh right.

      Honeycomb, and it's withholding, was mentioned in the SUMMARY.

      So was the statement that it WILL be released. So yes, straw man, since GGP didn't bother mentioning that last rather important bit of information.

      --
      Today is red jello day - all workers must eat all of their red jello. Failure to comply will result in five demerits.
    27. Re:The ultimate irony by amRadioHed · · Score: 1

      Way to troll. Android and the standard apps it ships with don't display any ads. If you choose to install a free app that displays ads instead of buying the ad-free version that is your choice.

      --
      We hope your rules and wisdom choke you / Now we are one in everlasting peace
    28. Re:The ultimate irony by Anonymous Coward · · Score: 0

      Google wants to close android in order to keep the manufacturers from closing android further.

      Riiight. In reality Google is withholding source code to Android and license to use Google services from android apps to prevent competition.

      Fragmentation is just a code-word for Google losing control over Android once it has enough features that it doesn't need constant refreshes. Before manufacturers were kept in-line by the rapid development of Android (they can't compete with thousands of really smart coders working for 'free' paid by monopoly money). But now Android is a capable phone and tablet OS and doesn't need massive new features, so Google would lose control of the OS to manufacturers unless they lock them down using anti-competitive agreements that restrain trade.

      There's also no excuse for bundling, like Google not allowing license to use their services from apps if the manufacturer uses Bing for search. That's as restraint of trade as 90s Microsoft dictating what icons can appear on the desktop and what software can be installed with Windows. There's no difference, and a corporate motto is not a free pass to illegally copy books, restrain trade, etc.

      Regardless of what message Google's marketing genius are trying to get out, these agreements are by definition restraint of trade and will eventually be struck down by courts once they eventually declare Google a monopoly.

    29. Re:The ultimate irony by ByOhTek · · Score: 1

      Not the GP, but my logic

      1) Hardware keyboard (no iPhone)
      2) Large software library (no WinMo)

      That left Blackberry and Android. Revisiting #2, Android wins out for my uses.

      --
      Self proclaimed typo king, and inventor of the bear destroying coffee table (patent not pending).
    30. 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.

    31. Re:The ultimate irony by RobbieCrash · · Score: 1

      As MANY have pointed out, keeping development versions of code closed, and then open sourcing the final product is not closing the software, and has in fact been the preferred version of deploying code used by many organizations.

      --
      Keep on knockin'
      https://robbiecrash.me
    32. Re:The ultimate irony by cos(0) · · Score: 1

      This is the irony that permeates the GPL vs. BSD camp. Both can make a good argument why their license is freeer than the other.

      BSD gives companies the freedom to keep their changes private.
      GPL takes away the freedom from companies to keep their changes private in order to give consumers the freedom to tinker with those changes.

    33. Re:The ultimate irony by gad_zuki! · · Score: 1

      Better base? The garbage that HTC and Sumsung are pulling is not better, not by a long shot.

      Lets see, my Vibrant has random 5 second lag because of some boneheaded decision to make a custom filesystem that sucks. The gallery app freezes randomly. It does this weird super loud beep when the battery is fully charged that wakes me almost every night.

      My old EVO had similar issues and they both are behind the latest version of android for months because of these custom crap enhancements.

      Of course, when I play with a G2, it has none of these problems. Yes, the UI is a little uglier, but its rock-solid and the google developed apps are light years ahead of the nonsense Samsung and HTC and the rest are doing.

      More control is fine with me. I won't be buying modified android anymore anyway. Nesus S or better from now on. I feel sorry for Android users in the Android ghetto. All AT&T phones, most Samsung phones, most HTC phones, etc all have significant problems brought on by either the carrier or phone manufacturer.

      Google is also running scared from the potential of Win7 mobile. MS is controling the platform just like Apple does with the iphone. Google is the only one with little to no control and it must be heartwrenching to watch other companies fuck up their product.

    34. Re:The ultimate irony by Buelldozer · · Score: 1

      Tell you what, you keep my name handy and IF any U.S. carrier EVER releases ANY application that is generally considered to be better than Google's and I'll send $50 USD.

      I feel pretty confident that the carriers aren't capable of creating such a thing or aren't capable of releasing it if they DO create it.

      tl;dr I consider your argument that Google is scared of carrier innovation in the software space to be nonsense.

    35. Re:The ultimate irony by DMFNR · · Score: 1

      Most people probably buy it because of the pretty commercials.

    36. Re:The ultimate irony by Merk42 · · Score: 1

      So Verizon phones will continue to use the "Droid" trademark and this wouldn't affect them at all

    37. Re:The ultimate irony by JesseMcDonald · · Score: 1

      We're not talking about "development versions" here. Devices have already been released to end-users (e.g. Motorola Xoom) running Android 3.0 binaries, without any source code in sight. Still want to argue that Android 3.0 isn't closed-source right now, whatever their future intentions might be?

      --
      "The state is that great fiction by which everyone tries to live at the expense of everyone else." - Bastiat
    38. Re:The ultimate irony by Anonymous Coward · · Score: 0

      Android 3.0 is not closed source.

      Until it's opened, it's closed.

    39. Re:The ultimate irony by GooberToo · · Score: 1

      Android 3.0 is not closed source.

      Until it's opened, it's closed.

      Until Google says its closed, or refuses to release at some point down the road, its open. That's reality. Again, you're purposely conflating closed development with closed source. They are two completely different things. The fact you're purposely attempting to conflate validates you're an idiot.

    40. Re:The ultimate irony by Drakino · · Score: 1

      If it's not finished, why are Google and Motorola trying to get $800 out of people for the Xoom?

      I'm mad about Google because they haven't been up front about any of this. They bash others for calling out their Open claims, spout off about being Open to avoid a dark and closed future at their keynotes, then change the procedures.

      At least with people like Carmack, they state up front it will only be open later, after the main licensees have moved onto the next engine version.

    41. Re:The ultimate irony by awyeah · · Score: 1

      I bought mine because it's a good phone.

      You might have to explain that one further, because 98% of the users reading that believe that "good" and "open" must be synonymous.

      --
      Why, no, I haven't meta-moderated lately. Thanks for asking!
    42. Re:The ultimate irony by the+linux+geek · · Score: 1

      So Google, Motorola, and Samsung are selling an unfinished operating system?

    43. Re:The ultimate irony by Anonymous Coward · · Score: 0

      Hint: Honeycomb isn't a phone's operating system. Never can be, never will be. We're talking about phones; you may as well be talking about Windows by mentioning Honeycomb.

    44. Re:The ultimate irony by dannys42 · · Score: 1

      Source code is useless if you're locked from installing your custom OS on the device.

    45. Re:The ultimate irony by Anonymous Coward · · Score: 0

      But now Android is a capable phone and tablet OS

      No, it's not. We have _two_ divergent Android platforms, only they're called by the same name, but they actually aren't the same. You may as well label the Honeycomb OS 'Bubbles' because it's completely fucking different.

      What does Android mean to most users? It means the fucking phone operating system. The Android 'phone' operating system is still open source, developed in parallel, and it's planned to remain open source for all future releases. Honeycomb is completely fucking irrelevant when discussing the Android phone.

      The only thing Google has "withheld source code" from is a tablet-specific fork which only a small percentage of the current Android userbase is actually interested in.

    46. Re:The ultimate irony by AnotherScratchMonkey · · Score: 1

      I got my Droid for geek appeal. Otherwise I'd just carry a minimal phone for emergencies and a notebook for the functions I use my Droid for. (I hate phones.) Closing the platform will just put me in the market for a dumb phone and a notebook.

    47. Re:The ultimate irony by amRadioHed · · Score: 1

      Well, if that's their reason for liking Android that's fine. My reasons were more to do with the apps and the overall functionality. The iPhone is okay, but I don't prefer it and the iTunes requirement is a big turn off for me.

      --
      We hope your rules and wisdom choke you / Now we are one in everlasting peace
    48. Re:The ultimate irony by zuperduperman · · Score: 1

      Google has clearly been too ambitious with their schedule, that much is clear and pretty much accepted by everyone including Google who are quite open about it. If you want to be angry, sure, be angry about that. But don't try and twist that into some dark evil plot wherein Google is somehow intending to turn Android into a proprietary closed ecosystem.

      It's amazing how you have every other player happily distributing their fully closed, never to be opened phones and there's hardly even discussion of it and Google who has faithfully open sourced every release of Android so far under one of the most permissible licenses available just delays release of source by a month or so and everyone screams as if it's the end of the world and Google is the borg.

    49. Re:The ultimate irony by zuperduperman · · Score: 1

      Google said as much. It's not great, but it's pretty clearly the case. Nonetheless, Honeycomb is clearly the most powerful, flexible and open of any tablet OS out there and most certainly what I'll be getting (if I ever get a tablet, which is another question).

    50. Re:The ultimate irony by zuperduperman · · Score: 1

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

      They seem to be making an issue out of it for the devices they have anything to do with. Every Nexus and every "flagship" device (eg: Xoom) has been unlocked regardless of the carrier / manufacturer's general policy for locking the devices. I think this is where they've drawn the line: they will do the minimum to ensure that there is always at least one good quality unlocked phone that can run the latest Android. Others can do what they want, but Google will set a baseline there. It's not much, but it's something.

    51. Re:The ultimate irony by jonbryce · · Score: 1

      You can still install Apps from alternative app stores, or copy them in via an SD card; and the fact you can put an SD card in the phone is a good reason in itself.

    52. Re:The ultimate irony by jonbryce · · Score: 1

      Yes. Google have only finished the tablet bit of it, and it doesn't work well on 3"-4" screen phones.

    53. Re:The ultimate irony by Bruj0 · · Score: 1

      They can sell all the ads they want, but a few lines in my phone's /etc/hosts file and they are gone for good.
      And thats the beauty of Android OS.

      --
      http://securityportal.com.ar
    54. Re:The ultimate irony by Drakino · · Score: 1

      Everyone else who is closed is up front about it. They never set an expectation, so people aren't pissed. Google may be admitting they were too ambitious with the schedule, but they haven't had Motorola recall the Xoom. So either Honeycomb is done, or Google is admitting to using the public as beta testers with an $800 device and an unfinished OS.

      Google yaps about how open they are, and then aren't. Other companies have sprung up around this openness, and depend on it. Archos for example is probably mildly irritated about the Honeycomb delay, as they won't be able to ship a non "Google experience" Honeycomb device until much later. This isn't the first incident either. The Skyhook situation has both Motorola and Samsung slightly irritated at Google already, for initially certifying phones with a new location API, then later issuing stop ship orders.

      Microsoft pulled similar stunts in the OEM market, and it pissed off vendors to no end. The only difference here is that Android is not the only licensed smartphone OS, so vendors do have a choice to go elsewhere. Google needs to be more professional about how they handle licensing their "open" OS and how they meet commitments, or OEMs may choose to go elsewhere.

    55. Re:The ultimate irony by pckl300 · · Score: 1

      No, Google wants to control Android to prevent the stupid corporations from fucking it up any further.

      --
      In the beginning, there was null.
    56. Re:The ultimate irony by DRJlaw · · Score: 1

      Until Google says its closed, or refuses to release at some point down the road, its open. That's reality. Again, you're purposely conflating closed development with closed source. They are two completely different things. The fact you're purposely attempting to conflate validates you're an idiot.

      Once object code is being distributed to end users who are not developers, and source code is not being distributed to those same end users, then it is closed source.

      Nobody is purposefully conflating closed development with closed source. You are purposefully saying that development may continue until whatever arbitrary point Google declares to be the 'end' of development, and we are saying, despite Google's propensity for perpetual betas, that Motorola Xoom purchasers are neither developers nor beta users, ergo the development stage is complete. Google's choice to further develop the software does not alter that fact.

    57. Re:The ultimate irony by Anonymous Coward · · Score: 0

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

      Root root for the home team!!!

      I don't know about everyone else but my phone is paid for by the company and I really couldn't care if I void their service agreement.

    58. 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.

    59. Re:The ultimate irony by Daengbo · · Score: 1

      Honeycomb isn't ready for phones. It's ready for tablets. Google said that it doesn't believe that H on phone will be a good idea or that phone makers will listen to Google's advice. Based on modders already trying to put H on phones, I'd guess that Google is right. They say they'll release when phones work.

    60. 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.

    61. Re:The ultimate irony by Anonymous Coward · · Score: 0

      Google wants to close android in order to keep the manufacturers from closing android further.

      Google could have picked the GPLv3 for that. But they appear to want "just" compatibility, and likely so for market share reasons.

      Openness advocates are fighting to protect the rights of the manufacturers (that of closing Android)

      I think that's not how one would typically define "openness" advocates. Surely they can be defined as "open source" (as a free resource for any purpose) advocates in the sense of the MIT/BSD crowd - but not as "openness" advocates. An actual "openness" advocate surely can't stop caring whether something is still open just because it has arrived one organization/person further down the line...

    62. Re:The ultimate irony by Daengbo · · Score: 1

      Google is withholding H because it wants it to work on phones. G and H are to be merged in I. Finally, the Chrome OS and I are to be merged, probably for J. In short, you're entirely wrong, from start to finish. You talk a good game, but you haven't read anything about Android since before Honeycomb was released, I guess.

    63. Re:The ultimate irony by Stuarticus · · Score: 1

      HAHAHAHA! Carrier level innovation, that's brilliant....

      --
      If you think someone isn't free to have a different definition of "freedom" you may be a tyrant.
    64. Re:The ultimate irony by Anonymous Coward · · Score: 0

      So? That means Ice Cream is the next big phone revision -- and Honeycomb is still the tablet edition. None of what you said invalidated the GP post.

      If Ice Cream's source code is withheld then you would have a right to complain about 'real' Android. Right now, you can only legitimately bitch about Android tablets.

    65. Re:The ultimate irony by GooberToo · · Score: 1

      Once object code is being distributed to end users who are not developers, and source code is not being distributed to those same end users, then it is closed source.

      Sorry, stupidity alert.

      Please bother to go learn something about reality before you post ignorant stupidity again. Please go learn the difference between a development process and a licensing model.

      Unless you have proof Google has completely changed the licensing model and source code policies, for what they are developing behind closed doors, you are, in fact, a complete fucking idiot spewing lies and baseless propaganda.

    66. Re:The ultimate irony by awyeah · · Score: 1

      There you go ;) I think overall functionality is probably the key for most people. Just not slashdot users. I hear you on the iTunes requirement. I live with it though.

      --
      Why, no, I haven't meta-moderated lately. Thanks for asking!
    67. Re:The ultimate irony by Daengbo · · Score: 1

      "Divergent" means having a tendency to develop in different directions. G and H aren't doing that: in fact, they're convergent.

    68. Re:The ultimate irony by Anonymous Coward · · Score: 0

      Ice Cream is pure speculation at this point. We don't know how or if it'll actually pull the theoretical merger off. In fact, 2.4 is expected to be here before it's even being tested.

      I guess you're right in what you're saying, if you read 'divergent' to imply divergent in eventual development. Right now the Android platform is split firmly down the middle, and it'll be a while before/if that changes.

  5. Community distributions and less fragmentation by asnelt · · Score: 1

    I guess the Cyanogenmod community is not a licensee. So as long as it doesn't affect these open distributions we can have diversity (by community distributions) and less fragmentation for typical consumers. That's a good thing.

  6. 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 MadeInUSA · · Score: 1

      Do they have a point? Google's point is no different than Microsoft's, Oracle's, Apple's etc point when they want to protect their technologies to maximize profit. I don't think profit maximization is evil, but let's be clear here: if any other, older company was doing the same, bullets would fly from people screaming that company X, Y and Z are against software freedom. I think Google is doing the right thing for its shareholders, but the goal was NEVER software freedom: google is a profit making being. Adopting free software was part of the profit making strategy, and making the platform more closed now that it enjoys a substantial market share is just the obvious consequence of that.

    2. 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.
    3. Re:Well they have a point by Anonymous Coward · · Score: 1

      I think there's a difference between walled garden and stopping each vendor from tainting the user experience with their shoveled bloatware.

    4. Re:Well they have a point by tgd · · Score: 1

      The surprising thing is that anyone thought Google *wouldn't* do that.

      The OS is only of value to Google if they control the platform. They could play the open game for penetration, but at some point they had to start locking it down. Android is only as valuable as its brand, and the tie in to Google's services. If you let things be too open, you lose both.

    5. Re:Well they have a point by SeNtM · · Score: 1

      Google's point is no different than Microsoft's, Oracle's, Apple's etc

      Well, it is a bit different. Motorola and others is/are locking their devices and eliminating the "openness" of the platform. This forces users to use vendor specific versions of the software which are not open. IMO, it is these vendors trying to maximize profit by exploiting a free technology and thus the users of that product. Google is in the right here by withholding until the vendors agree to stop exploiting the consumers.

      Now, I don't know Linus, but I would bet that he would allow the source to be withheld on that basis...so long as it was done in good faith and only a temporary measure.

      --
      "There ought to be limits to freedom." -George W. Bush
    6. Re:Well they have a point by penguinchris · · Score: 1

      I don't think anyone who has looked at Android phones can deny that the iPhone's locked down, Apple-specified (rather than carrier) nature has been a huge advantage. Most Android phones are loaded with garbage.

      Even at the most benign level of carrier/manufacturer customization - skins and visualization stuff - they fuck it up. Different skins and whatever is fine, and there are some nice community-made options, but it's clear that the carriers and manufacturers make things different just to be different, not to improve anything - because the base Android version is almost always superior.

      I love my unlocked, rooted Nexus One. I use a custom ROM, but the base ROM that Google pushes out is perfectly fine and very nice to use. I read about what other Android phones are like, and I'm sometimes shocked - it would not be a phone experience that I would enjoy. It's often radically different from the base Android experience, and not for the better (not that there couldn't be improvements with base Android, as there certainly could be - same with iOS, though).

      So I am glad that Google has recognized the problem and is doing something about it. It's not like Android phones are anywhere near great examples of open-source philosophy, since most of it isn't even open, so it's hard to object on those grounds. If they attempted to restrict the ability to customize things, that'd be one thing, but that's not what they're doing. They're dictating to the carriers and manufacturers that they don't want Android phones messed up with their shitty customizations, because to the general public that gives all of Android a bad name, not just the specific phone.

    7. Re:Well they have a point by Midnight+Thunder · · Score: 1

      Using a GPL code base there isn't much Google can legally do to prevent how the code is used. On the other hand there is nothing stopping Google putting limitations how the Android trademark is used and what gets to use their market place.

      --
      Jumpstart the tartan drive.
    8. Re:Well they have a point by similar_name · · Score: 1

      As much as I love Open Source I can see their point and I can't counter it.

      That's because the marketplace for telecommunications is broken in this country. Phones and service should not be allowed to be tied together. Fix that fundamental problem and open source will be just fine on your phone. For that matter most other proprietary software would be better too as it would have to compete for the consumer's approval as opposed to the carrier's.

    9. Re:Well they have a point by GooberToo · · Score: 1

      First you need to establish how they are "locking down" the platform? You are free to branch the available source any time you want. How is that even remotely close to Apple's platform where the source isn't even available? One is open with a closed door development model plus tiny proprietary components (device drivers) while the other is completely closed and proprietary. They are as different as night and day. One is open sourced while the later absolutely is not.

      I have no idea why so many seem to get off telling half truths in an attempt to disenfranchise android developers and would-be users, but time and time again, that's all these stories are - lame attempts with half truths without a legitimate complaint.

      I mean, holy shit, how stupid do many of these slashdotters have to be? Google is well on record announcing Honeycomb was a forced march to create a tablet competitor at manufacturer demand and that it was only ever half a solution for a very targeted niche. Why would they want to damage the community and ecosystem just so people can play and damage the ecosystem. The complaint is completely illogical and squarely rooted in selfishness.

      Its always been pretty obvious to anyone who wants to read between Google's lines that once 3.x and 2.x are merged again, the result will be made public. Seriously, people take a step back and stop being so closed minded and selfish. How is it to the advantage of anyone to further a platform which is incompatible with the majority of devices, which will further alienate users and most importantly, developers? Its not. Basically the whining is coming from people who are too stupid to realize they've been done a favor. Either that, or they are coming from the Apple camp and are looking to capitalize on the ignorance of the masses to the benefit of their championed platform.

    10. Re:Well they have a point by hackstraw · · Score: 1

      On the other hand there is nothing stopping Google putting limitations how the Android trademark is used and what gets to use their market place.

      That is what they do. The Android name and robot logos are trademarked and your hardware and use of software must meet some criteria from Google to use the Android trademarks.

      Maybe I should read the FTA (ducks), but to me it would seem as though this trademark limitations would to some degree limit the fragmentation of the Android market. I guess that the trademarks could not limit things like replacing and adding apps on the phone. I have an Android phone. A Samsung Fascinate. And I would trade it for an iPhone in a heartbeat.

      It simply reminds me too much of the Windows and Linux user experience. My phone was preloaded with crapware (like most OEM Windows installations). The version of Android is 2.1/Eclair which is old (like most "Enterprise" Linux installations). Using the USB data on the phone broke in January due to a forced software update. There has been another update and still USB does not work. I can't root the phone anymore due to USB issues. The calendar does not work correctly. This is a "known issue" and the fix is to wipe and load the phone and repurchase all of my purchased apps. The software is frequently sluggish and does not respond quickly, which causes frustration and incorrect input from me.

      I mean, on the iPhone there was a bug in the alarm clock, and a few people overslept one morning. I'd take that level of dissatisfaction any day.

    11. Re:Well they have a point by Anonymous Coward · · Score: 0

      I think the problem people have with iOS is the fact that it's closed platform - not that iOS is open-source or not.

    12. Re:Well they have a point by trollertron3000 · · Score: 1

      That just covers the Linux kernel, the majority of Android is actually Apache-licensed, and that limits them even further.

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

      This could work particularly well if we had app markets that vetted their software thoroughly, thereby adding some value to the community.

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

      Not true. The "GPL code base" actually isn't. I have no idea why you believe that factually incorrect statement.. The code base is BSD and/or Apache based. Largely, only the kernel is GPLed. So good luck taking just a Linux kernel and recreating the Android platform. Google is literally entirely free to lock down the entire platform tomorrow. Of course, I doubt they'll do that, but the option is always on the table.

    15. Re:Well they have a point by dara · · Score: 1

      I agree with similiar_name that carriers are the fundamental problem (in the US). Manufacturers are being a pain too, but if we fixed the carriers, there would be more competition in the manufactuering side, and I think the worst (Motorola) and others would clean up a bit as well as opening it up for new smaller companies which will cater to user subsets (e.g. geeks) much better.

      Simply put, we (in the US) must demand of our regulators that they force cell phone companies to offer all plans to users who come with their own phone if they have compatible hardware (GSM vs CDMA, etc.). All plans shall be month to month (or pre-paid fixed number of minutes) - no multi-year contracts available. I don't mind if carriers want to try their hand at the phone rental business as well, but no tie ins (discounts if you get a plan and a rental).

      Unfortunately, I don't see that happening, and now with T-mobile going away, I'm not sure what a decent nationwide option is for those who want to buy a phone outright is anymore.

      Another poster asked HTC if they would start a line of vanilla Andoid phones. I'm not sure if that would work in the US if none of the carriers offer to subsidize it. I'm aware of Geeksphone, but until the Two comes out (if it does), the hardware isn't very interesting to me. But if I could get really good open hardware, I guess I'd forgo the $20 month subsidy on the typical plans in the US (i.e. I'd pay the same rate as someone who is getting their phone for cheap).

      In the meantime, more power to Google, I'll take whatever incremental improvement to the very real fragmentation problem that I can get. I sure as hell am not getting an Atrix.

    16. Re:Well they have a point by david_thornley · · Score: 1

      In the US, you have five choices on how you're going to be screwed with your cell phone. You can pick Verizon, Sprint, AT&T, T-Mobile, or Apple. There used to be only four choices.

      Apple is the one phone maker with enough clout to impose some of its will on the carriers. That's worth something.

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
    17. Re:Well they have a point by metamatic · · Score: 1

      This is a "known issue" and the fix is to wipe and load the phone and repurchase all of my purchased apps.

      Your purchased apps are associated with your Google ID. You don't need to repurchase them. I wiped my phone and installed a completely different ROM image, and all my purchased apps came right back when I ran the Market app.

      --
      GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
    18. Re:Well they have a point by snadrus · · Score: 1

      Carrier's barrier to entry is too high for market forces to cause Open Source to win here, and the oligopoly isn't trying to undercut each other with better phones. Pushing it to the users would be my preference by requiring a "reset to latest stock Android" app shortcut.

      That way fragmentation that doesn't improve will be easily replaced and market forces prevail by users avoiding the junk. The carriers know this & won't bloat their phones with junk.

      --
      Science & open-source build trust from peer review. Learn systems you can trust.
    19. Re:Well they have a point by Anonymous Coward · · Score: 0

      The question is based on whether you are somebody who wants to improve the system by fragmenting it trying out new ideas, or you just want to harvest benefit.

      On the software sector, second mindset does not make a lot of sense, since you offer your customers software only, targeting any hardware. a browser with built in ads built on top of chromium will not find it's way to the broad customer spectrum, because you can use the original.

      On the hardware sector however, fragmentation is lethal, since it destroys compatibility, forcing you to use the local flavour.
      Extending drivers and APIs for your device makes sense, however you want to have support for the software market, so you would want to contribute it to your upstream. Otherwise your hardware device gets less attractive.

      Google might change it's mindset if the whole thing does not work out anyway. They do listen to the voice of community.

      Don't panic.

    20. Re:Well they have a point by swb · · Score: 1

      Carriers' marketing and sales departments have total control over the handsets and know just enough to want to "BRAND" them without any idea of what this does to usability.

    21. Re:Well they have a point by awyeah · · Score: 1

      skins and visualization stuff - they fuck it up

      I'm not so sure about that. I had two people show me the animated backgrounds on the home screens of their Android phones and the little windshield wiper on the weather screen - I think those are specific to HTC's custom interface? They were raving about how awesome they think that stuff is. They used that to prove that their brand new 4G phones are better than my almost-two-year-old iPhone.

      Not the bigger, higher-res screens, or the faster CPUs, the fast LTE network... no. The animated wallpaper is what puts their Android devices ahead of my iPhone 3GS. I like a nice black background. Whatever. Oh, and I work at a software company, a place where you'd think people wouldn't care about that stuff.

      I guess my point is - don't be so fast to dismiss the eye candy. You and I may never understand *why* people care so much about that. But for whatever reason, they really do.

      --
      Why, no, I haven't meta-moderated lately. Thanks for asking!
    22. Re:Well they have a point by Matheus · · Score: 1

      I see this as two different things. Apple's clear intent is to lock down their phones so that no one can do anything they want on the phone that isn't specifically approved by the Apple overlords. Google is trying to get past the current issue of every OEM shipping a much modified 'version' of the OS causing incompatibility issues and fragmenting the market doing harm to the viral spreadability of the platform.

      Although some of the hardware manufacturers are doing so (read Motorola) Google has said and done nothing to prevent you from taking that (now hopefully more) standardized Device/OS you got from your TELCO and hacking the crap out of it. They are saying "When you sell a phone and say it has Android vX.X on it that means something much more consistent."

      Now... if I could just get Motorola to stop being so evil with their devices I'll be a truly happy camper (cause dammit... I really like their hardware!)

    23. Re:Well they have a point by Anonymous Coward · · Score: 0

      One is open with a closed door development model plus tiny proprietary components (device drivers)

      You got this switched around. Android drivers are completely open (kudos to GPL) minus the tivoization. It's the apps on top of Android that are closed.

      Also, Android isn't exactly closed development - anyone can contribute (even you) but you won't necessarily be accepted or have access to the internal branch.

    24. Re:Well they have a point by trollertron3000 · · Score: 1

      That's actually a brilliant idea, if it could be required to license it. I can't even load a stock ROM onto mine right now, even using the SDK I'm having issues.

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

      Er, nice rant at me. The article was about Google tightening control over their platform. I never said "locking down." I never said they would lock it down. Obviously, I hit quite the nerve with you. I thank you for calling me stupid; now I have an excuse for my wife when I do something wrong.

      "Its always been pretty obvious to anyone who wants to read between Google's lines that once 3.x and 2.x are merged again, the result will be made public."
      Know something we don't, Carnac?

      By the way, did you even read the article? Or just forgot to drink your coffee today or somesuch? I'd be annoyed if I wasn't laughing so hard right now.

      --
      Vote monkeys into Congress. They are cheaper and more trustworthy.
    26. Re:Well they have a point by Anonymous Coward · · Score: 0

      The biggest block to separating carriers and phones is that the carriers each use different technology, different frequencies (sometimes required, sometimes not) and have different radio and protocol requirements. This means that is absolutely certain that a phone which works on Verizon will not work on AT&T's network. It also leads to Verizon having a rather complicated validation and approval process for phones to make sure they work. AT&T has the same thing I am sure. But because Verizon is using one set of frequencies and AT&T a different set plus different protocols plus different radio requirements the phones are in fact quite a bit different.

      With that you cannot separate the carrier from the phone. The only alternative would be a government mandate of a single technology and protocol which would allow all phones to work for all carriers. Only problem with that is in the US the only way to get that done really is to have one and only one carrier. Unlike some other countries, the only reason we had one and only one POTS connection standard was because the phone company was a single entity and you were either compatible or you weren't. There were countries where the wired phone systems weren't compatible with each other - even at the wiring level.

      Today the only way you are going to get handset compatibility is by government mandate and probably by the government selecting one "winner" and making them a monopoly. Just like the Bell System was in 1950.

    27. Re:Well they have a point by Anonymous Coward · · Score: 0

      Trying to compare an OS with a phone is tricky. Apple doesn't produce software they produce phones. They take open source software rip off the GUI layer and ruin it. The difference between Apple's phone and Google's OS is huge. Apple locks everything down. Google isn't a phone manufacturer. As far as lock downs go they aren't locking it up. They have simply delayed the release of the code. This isn't necessarily acceptable although assuming that they have released it to those they have distributed the OS (phone manufacturers) then it may be acceptable. Now if the phone manufacturers fail to release it that is a problem. Regardless Google IS going to release the source code and has no intention of violating the spirit of software freedom. Google isn't perfect and I'm not defending Google in all regards. They could do a allot better in regards to free products they release. Such as Picasa amongst others.

    28. Re:Well they have a point by similar_name · · Score: 1

      The biggest block to separating carriers and phones is that the carriers each use different technology, different frequencies (sometimes required, sometimes not) and have different radio and protocol requirements.

      Just because Windows and Mac use different technologies does not mean the only place you can get software for Windows and MacOS are Microsoft and Apple (there are only artificial barriers when it comes to the iPhone).

      If cell providers could not take part in selling (on crazy payment plans that no one would agree to if they were separate) the phone they would have less incentive to make their systems so proprietary. At the very least your cell phone usage should be charged separately from your cell phone loan.

    29. Re:Well they have a point by similar_name · · Score: 1

      no multi-year contracts available.

      The only reason they exists now is to hide the terms of the two year $500 loan people get to pay for their phone. It strikes me as crazy that someone who wouldn't pay $500 for their phone will gladly take a loan (with hidden terms/interest rate) for one.

    30. Re:Well they have a point by similar_name · · Score: 1

      In the US, you have five choices on how you're going to be screwed with your cell phone. You can pick Verizon, Sprint, AT&T, T-Mobile, or Apple.

      One of those is not like the others. One of those is not a carrier. Also, AT&T bought T-mobile so that would leave 3 choices for the largest economy in the world.

    31. Re:Well they have a point by Anonymous Coward · · Score: 0

      -1 AT&T + T-Mobile merger announced.

    32. Re:Well they have a point by Anonymous Coward · · Score: 0

      The solution to this problem should be different: the customer's interests are being hurt, and this is exactly where the FTC should step in.

    33. Re:Well they have a point by Anonymous Coward · · Score: 0

      It seems to me that people's major problem with apple is how they restrict the app store. As long as Google doesn't start rejecting apps on some random whim (like apple), I don't think the majority of people will care how much they lock down the android source.

      Besides, nothing good has come out of the crap Verizon and Motorola have tried to force on me. I use just about 0 of their bloat apps and widgets

    34. Re:Well they have a point by bryan1945 · · Score: 1

      I see this as two different things. Apple's clear intent is to lock down their phones so that no one can do anything they want on the phone that isn't specifically approved by the Apple overlords. Google is trying to get past the current issue of every OEM shipping a much modified 'version' of the OS causing incompatibility issues and fragmenting the market doing harm to the viral spreadability of the platform.

      Respectfully, those don't seem very different to me. Yes, I do see the slight differences, but the practical effect is mostly the same. Apple locks down to keep a unified platform (the experience), Google is now realizing that letting everything going viral may be a problem (such as Windows + various OEMs), and so wants some lockdown (the experience).

      A difference, but a small difference as I see it.

      --
      Vote monkeys into Congress. They are cheaper and more trustworthy.
  7. This sucks by Anonymous Coward · · Score: 0

    Not the decision, I actually understand it, but the fact that it's necessary.

    This is really the open, anyone can do whatever vs closed, controlled user experience debate. I really wanted to see open work, but it just seems like it's not.

    Then again this is a relatively new approach, there are bound to be bumps. Hopefully we end up with the right mixture of open and sanity. I can see android slowly morph into the iphone mentality out of necessarily, and I don't like it.

    1. Re:This sucks by EraserMouseMan · · Score: 1

      What I want is the ability to toggle between stock Android (aka NexusOne) and the manufacturer's interface (if I happen to prefer it). This way it can stay just as open as before but allow users the easy choice to go the clean stock route too. One more requirement I'd like is a requirement that manufacturers support and push out the latest OS update as soon Google releases it.

  8. 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 Attila+Dimedici · · Score: 1

      The best part about your solution is that it sounds like it might be compatible with the licensing that the software Android is based on comes with. Which I do not believe that Google's solution is.

      --
      The truth is that all men having power ought to be mistrusted. James Madison
    2. Re:Easy solution by Anonymous Coward · · Score: 0

      The only Android devices I would ever spend actual money on are running plain vanilla Android, with no locks to upgrade any time I want. Your plan may work as a nice compromise.

    3. Re:Easy solution by jarich · · Score: 1

      That's brilliant. Let Sprint put their crap Nascar apps and everything else on my EVO, but require them to have a button for an over the air plain vanilla latest Android install. Add tons of warnings, etc, but provide that button. I love it.

      That would highly motivate carriers to ~add value~ instead of taking dollars from partners to shove crap on phones.

    4. Re:Easy solution by Anonymous Coward · · Score: 0

      Mod parent up. If the problem is manufacturer customizations, then make sure the user has a solid, supported way of getting rid of them. I root every Android device I buy *specifically* to get back to something resembling vanilla Android.

    5. Re:Easy solution by amiskell · · Score: 1

      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.

      The only problem I see with this is, who supports the vanilla android install? The carriers, the manufacturer, or the google themselves? Carriers most likely will not want to touch it because it increases their support costs to maintain two or more images and in some cases, ie Moto phones, the junk isn't even theirs to control. The manufacturer would be the most likely source, as they have the vanilla image installed then customize from there. I could see HTC providing default Android builds for their phones without the HTC software installed, but I highly doubt you'd see someone like Motorola doing that. And then you get into fights with the carriers because you can load unauthorized builds on the phones which carriers never really like for you to do. Google most likely wouldn't want to mess with it because now they have to provide images for other manufacturers phone and maintain them.

    6. Re:Easy solution by Anonymous Coward · · Score: 0

      I like it, but it's never going to happen.

      One word. Tethering.

    7. Re:Easy solution by tycoex · · Score: 1

      This is a great idea.

    8. 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!

    9. Re:Easy solution by Anonymous Coward · · Score: 0

      Someone get this idea to Google, ASAP!!!

      I always try to remove as much bloat as I can, this would be an excellent idea.

    10. Re:Easy solution by Anonymous Coward · · Score: 0

      Your theory falls apart because it makes sense, no one would ever adopt it.

    11. Re:Easy solution by Anonymous Coward · · Score: 0

      That's what we want. Not what the carriers (and thus manufacturers) want. It takes both, really.

    12. Re:Easy solution by Anonymous Coward · · Score: 0

      I wonder if you realize that all phones have different hardware. A vanilla 2.2 build for phone A wouldn't work on phone B. So who is going to create the vanilla build for your phone? It's not in the manufacturer's interest, and Google can't maintain hundreds of builds.

    13. Re:Easy solution by Anonymous Coward · · Score: 0

      Highly convoluted is this language. Following the path to the dark side of stack-based writing, you must cease, or lisp-isms too many your speech shall inherit! Only then your true potential will you realize.

    14. Re:Easy solution by Anonymous Coward · · Score: 0

      In theory it is a sound plan; however, carriers require strict testing of a software revision before they will release it on their network... with reason!

      Imagine a scenario where the driver released by, say Sony Ericsson, for the wireless chip works well with android 2.3.1, but on 2.3.3 they change how they are calling the driver and this causes the device to flood the network with information requests due to an error in the driver. Now if only a couple of crazy hax0rs that frequent the xda forums run this version with that driver, no biggie, the network can handle it. If %80 of Sony Ericsson users are in this mode, suddenly there is a big issue.

      Carriers won't go for it, and since the vast majority of handset sales go through carriers, you won't see it happen.

    15. Re:Easy solution by Scowler · · Score: 1
      ... and watch as the number of manufacturers who care about Android wilt.

      No manufacturer wants to get caught in a price war on Android devices, where the only distinguishing items are hardware feature set (marginal selling point) and price. Their margins will sink like a rock.

      It is imperative for these manufacturers to be able to differentiate on software as well, for the long term health of the Android marketplace.

    16. Re:Easy solution by mdielmann · · Score: 1

      And yet, somehow, Windows was able to solve this problem.

      Yes, that's too simplistic a response, but if the hardware specs are mandated, and the specific configurations fall within those specs, half the battle is over. Add drivers for specific hardware elements, and you're there. And if you put in as part of the agreement that OTA download of vanilla Android is required, it isn't much more to require compatible drivers for included hardware, as well.

      --
      Sure I'm paranoid, but am I paranoid enough?
    17. Re:Easy solution by SiChemist · · Score: 1

      That's complete and utter crap. Most of my friends have Android phones and I don't know of a single one of them that picked the phone based on manufacturers software customizations. In every case it has been about 1) the carrier and 2) the phone hardware. Big, bright screens sell smartphones. Touchwiz does not.

    18. Re:Easy solution by MDillenbeck · · Score: 1

      Precisely what I was thinking of. Manufacturers maintain drivers and the burden would be on Google to design the interface to those drivers (and thus maintain a repository of them for going to plain vanilla). I thought this was how linux worked also (like most modern OSes), and so it shouldn't be a problem. I think this would have the added benefit of standardizing some hardware and thus causing economies of scale to decrease the cost of the phones for the manufacturers. Then we are basically allowing users to get rid of the customized interfaces (Blur, Touchwiz, Sense, etc) in order to allow phones to stay current with the latest Android release - that should have no bearing on the underlying drivers needed by the OS to run the hardware in the phone.

    19. Re:Easy solution by Sarten-X · · Score: 1

      How long until that's subverted, though?

      "Enter authorization code to upgrade:"

      "To enter the maintenance control panel, follow these 57 easy steps:"

      "Simply hold down the 'firmware unlock' button, located on the back of the display circuit board, throughout the entire upgrade process. You may need to remove your phone's case and some internal parts to do this, which may make your device inoperable. Proceed at your own risk."

      Per the terms of the agreement, the vanilla-update option would be there, and the user can access it. That they need to jump through ridiculous hoops first is a separate issue.

      --
      You do not have a moral or legal right to do absolutely anything you want.
    20. Re:Easy solution by GrumpySteen · · Score: 1

      It's a great idea, but cell phone companies don't want you to be able to re-enable tethering and the local wifi hotspot capabilities if they're disabled and the manufacturers will always bow to will of the phone companies that act as their primary sales channel.

    21. Re:Easy solution by Anonymous Coward · · Score: 0

      There is an even bigger problem - hardware specific customizations (drivers) and things like power optimizations and of course testing of all this.Google has no incentive nor access to pre-release hardware to do this expensive work. Most people wouldn't upgrade to the latest OS if it meant that they can't use the camera anymore or the phone will only last 4hrs in standby. It's similar to installing "vanilla linux" on a laptop - it kinda works, maybe 75% of peripherals but has half the battery life of the pre-loaded OS and the non-standard buttons (like volume control) don't work at all. Mobile world is orders of magnitude less standardized than the PC world, so this "Vanilla Android" would be even worse, if at all possible.

  9. 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?

  10. 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.

  11. Same sin by Kakao · · Score: 1

    They don't want the same they did to Java to happen to them

    --
    2011. The year Gnome decided Linux will never be on the desktop.
    1. Re:Same sin by Midnight+Thunder · · Score: 1

      They don't want the same they did to Java to happen to them

      That would be an irony. A better example of fragmentation is Smalltalk where no VM was really compatible with each other.

      --
      Jumpstart the tartan drive.
    2. Re:Same sin by Anonymous Coward · · Score: 0

      Did to Java? What exactly did Google 'do' to Java?

      The net effect of Android appears to be the very first case of a really widespread client side application of Java (that isn't a development tool.) Poor Java? There are thousands of developers that would never have touched Java but for Android.

      In order to make Java viable for battery powered portable platforms Google had to address the performance problems inherent in the Sun JRE and its inefficient stack-based virtual machine model that people have been disparaging since the late 90s. Someone finally listened. How awful.

  12. 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 Anonymous Coward · · Score: 0

      Yes, as GPLv3 would have banned bootloader locks on phones. Too bad Google specifically excised all GPLv3 software, and Linus doesn't give a shit about the GPLv3 (in fact, with the amount of proprietary crap in your average Linux kernel, it might as well be BSD-licensed).

    2. Re:im curious to know by Anonymous Coward · · Score: 0

      It's not that Linus doesn't care, it's that the kernel is license is GPL2, not "GPL2 or later" and Linus doesn't require copyright assignment for contributions to the kernel, so in order to change the license they'd need to get the consent of all contributors.

    3. 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.

    4. Re:im curious to know by GameboyRMH · · Score: 1

      This. This is why I support GPLv3. Yes it can cause some problem for businesses, but you know what, if they're doing something that causes a problem with the GPLv3 then too bad. If you stick to the GPLv2 and let businesses tivoize everything to make it practically closed, then what's the point?

      --
      "When information is power, privacy is freedom" - Jah-Wren Ryel
    5. 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.

    6. Re:im curious to know by Anthony+Mouse · · Score: 1

      Because locked phones piss off customers and they might decide to use some other OS instead.

      The thing with Android at this point is that as long as there is customer demand for it, the carriers and manufacturers will supply it, because if they don't their competitors will. At least until AT&T finishes buying T-Mobile so that Verizon can buy Sprint and then AT&T-Mobile can merge with Sprizon and stop worrying about that whole competition thing.

    7. Re:im curious to know by Anonymous Coward · · Score: 0

      Yes.

      By not having anything to fragment.

    8. Re:im curious to know by Anonymous Coward · · Score: 0

      It would have prevented manufacturers from locking down the phones, which would allow users to install vanilla versions of Android without the effort of 'jailbreaking'.

  13. Re:First by amicusNYCL · · Score: 1

    No, it matters to no one that you failed to get a first post. In fact, I wonder why people even bother trying to do that.

    --
    "Our two-party system is like a bowl of shit looking at itself in a mirror." - Lewis Black
  14. Re:The Case for Google's Control: Atrix by GooberToo · · Score: 1

    Yes, but the failing isn't with Google, rather its the fact a failed idea has been used to punish a user by preventing them from then moving to something which actually works.

  15. 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.

  16. Re:The Case for Google's Control: Atrix by ackthpt · · Score: 1

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

    It's also so the code is completely transparent - you know what it's doing. Many eyes make for better code.

    What AT&T is trying to do is lock customers into AT&T as their sole source of support and products. More money for them, right?

    --

    A feeling of having made the same mistake before: Deja Foobar
  17. No Market by tepples · · Score: 1

    As far as I can tell, non-licensees can't legally offer the ability to buy apps from Android Market. The CyanogenMod community got cease-and-desisted for distributing the Google applications that people expect to be on an Android phone, such as Android Market. See this article.

    1. Re:No Market by GooberToo · · Score: 1

      Ya, but the solution was easy and trivial. Simply re-install the originally provided and licensed applications to those who install Cyanogen. Installs copy the originally applications, install, and then copy back those same applications. Basically, its not even worth mentioning so long as your device was originally licensed to run such applications; which is the vast, vast majority of devices.

    2. Re:No Market by tepples · · Score: 1

      so long as your device was originally licensed to run such applications; which is the vast, vast majority of devices

      Are there any such OHA Android-powered devices sold in the United States that aren't phones? I don't have 70 USD per month for a typical monthly voice and data plan, and the Archos PDAs and tablets have AOSP Android (no Market), not OHA Android (with market).

    3. Re:No Market by GooberToo · · Score: 1

      Not that I'm directly aware of. I've heard rumblings of cheap Chinese knockoffs but that's its own ecosystem with problems.

      I seem to recall hearing some place that post-Honeycomb, that is to say, whatever the 2.x+3.x merge becomes, there will finally be an OHA (with market a gapps) tablet/pda, non-phone series available but its been a while since I've read that and I no longer remember the source. As such, I don't remember if that was unofficial-official talk (much of what is learned about Android before releases), general rumor and speculation, or some guy talking from his ass.

    4. Re:No Market by Sancho · · Score: 1

      Which is why the Amazon market is a Good Thing for Android.

  18. Re:The Case for Google's Control: Atrix by the_humeister · · Score: 1

    Root your phone and load Cyanogenmod or some other OS. That's really the way to go.

  19. Re:The Case for Google's Control: Atrix by alen · · Score: 1

    that's the business model difference between iphone and android. apple makes money on the hardware, accessories and applecare. with android the carriers make money on the accessories, ad revenue sharing, the crap ware and the monthly insurance that some people buy

  20. 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.

    1. Re:Good by Anonymous Coward · · Score: 0

      The manufacturers were really getting out of line.

      This is an open-source, GPL operating system. How could manufacturers be "out of line" except by violating the GPL? The only way this possibly makes sense is if Google made an open-source operating system, but doesn't really want it to be open after all; being able to make any changes you want is the entire point of open source.

      Apple could use BSD license and make closed software because they have tons of in-house BSD experience and have filled in the weak points already (like graphics, audio latency, etc). What if Android being GPL was just an unfortunate side-effect of having tons of linux experience, almost no BSD developers, and needing to get something out ASAP because they were behind everybody else? That perfectly explains why a "non-fragmentation" aka non-compete clause would be in contracts from the beginning.

      The only reasonable interpretation is that Google never intended Android to be open, but intended from the start for it to be a way to monopolize the smartphone OS market. Open source is just a bait-and-switch tool for Google.

    2. Re:Good by rwa2 · · Score: 1

      Meh, everything that Google does could be spun into them being evil or incompetent. I think this is just another instance of the latter. Sure, there are lots of smart people there, but I suspect most of the time they're just victims of their own idealism.

      Google wanted a GPL'd OS so there would be some kind of commodity thing out there. But, all of the manufacturers wanted to distinguish their version somehow, so they customized it as much as they could. They don't have to violate anything to be dicks. Forking is fine if there's a good reason for it, but mostly the reason was to lock people into their own version of the product (and forced obsolescence when they refuse to release updates for "old" products that still run on half-decent hardware). It's gotten so bad that the only way to have a good experience on an Android device is to root it and flash it back to something closer to Google's releases. That's just sad. It's fine for me (I wouldn't buy an Android device that wasn't supported by CyanogenMOD), but I would have trouble recommending one to a grandparent saying "hey, it's actually pretty nice if you root it!" I do want to see Google doing more to, um, encourage manufacturers to track the upstream releases more closely and not waste their time on pointless GUI customizations and wicked DRM ROM locking.

      There are evil things that Google is doing wrong in this fight... for example, I don't like how they lock out my G-Tablet as an "incompatible" device with most of the apps on their app market (even though it's probably among the high end of Android devices available). But at least there are plenty of ways around that inconvenience.

  21. Re:The Case for Google's Control: Atrix by Zeek40 · · Score: 1

    Taking it and modifying it to try out new ideas generally voids your warranty, which most people aren't willing to do to a several hundred dollar piece of equipment.

  22. Re:The Case for Google's Control: Atrix by Albanach · · Score: 1

    The trouble is that, for most folk, there's no ability to customize their phone. The only group benefiting are the handset manufacturers and network operators.

    If they were not making phones with locked or difficult to upgrade firmware it might be different, but in actual fact they're trying to foist their changes upon users and are certainly not making it easy to revert to a vanilla Android install in the sense that you could reinstall your PC with Linux or Windows as soon as you get it home.

  23. Re:Is it just me? by Anonymous Coward · · Score: 0

    I have mod points, but there is no -1 Stupid, so I will just insult you as an AC and then mod -1 Overrated.

  24. Re:The Case for Google's Control: Atrix by Anonymous Coward · · Score: 0

    Personally, I don't mind Motorola crapping all over the OS as much as I mind the tivoization that prevents you from running a stock OS with a stock kernel on their newer devices.

  25. Thank goodness Android is open by Anonymous Coward · · Score: 0

    I've been looking for an open phone that I can modify the software on, like Android. Oh, wait....

  26. hypocrite much? by waddgodd · · Score: 0

    Google's under fire for fragmenting Java and for relicensing GPL code. Sounds like they're fragmenting two codebases to make the bloody thing, so my response to them is:"karma's a bitch."

    --
    Just because you're paranoid doesn't mean they aren't out to get you
  27. Re:Is it just me? by Anonymous Coward · · Score: 0

    It's just you. Samsung, Motorolla, Sony and HTC are the culprits for forcing their proprietary "overlays" on their customers, not Google for preventing them (at this moment) from doing the same crap with Honeycomb.

  28. Re:Is it just me? by DeVilla · · Score: 1

    They are attempting to get medieval on the manufactures who have been more than just a little evil.

  29. Re:The Case for Google's Control: Atrix by AdamThor · · Score: 1

    Mod parent up. To paraphrase the Matrix: What good is the source code, if you are unable to compile and install it?

    The solution of choice for users would not be Google holding more control back for itself, but passing control to users rather than carriers. Not that this is necessarily viable in either a technical or economic sense.

    --
    -- "Oh. This guy again."
  30. Re:The Case for Google's Control: Atrix by HateBreeder · · Score: 1

    Since when is apple a carrier?

    Last time I checked, Carriers make money through call tariffs - barely from accessories or ad revenue etc.
    Apple makes their money from selling the hardware. Motorola, Samsung, HTC etc make their money also from selling hardware.

    Some carrier see greater value in Android as they can fill it up with their rubbish content and try making even more money - beyond the call charges.

    Thankfully, Android is open and you can just rip away all the garbage some carriers push into it.

    --
    Sigs are for the weak.
  31. Not quite by Anonymous Coward · · Score: 0

    Isn't the point of open source that other mobile carriers can take it and modify it to force subscribers to bend over?

    FTFY

  32. Re:The Case for Google's Control: Atrix by ceoyoyo · · Score: 1

    When Android was first announced I said that an open source phone OS wasn't worth much without good hardware and a good network to run it on.

  33. Smart move by elrous0 · · Score: 1

    Open source and Linux fans may hate to hear it, but fragmentation doesn't produce better product. It just makes everything a giant, confusing pain in the ass, especially for developers who have to develop for the platform. With Android, you not only have to design for specific versions of the OS, you also have test it out on specific phones because HTC and others have taken it upon themselves to throw their own flavor of the OS on top of everything else. It's confusing to consumers and often embarrassing to Google. And it puts Android at a huge disadvantage over Apple, with their relative consistency and quality control.

    --
    SJW: Someone who has run out of real oppression, and has to fake it.
    1. Re:Smart move by F.Ultra · · Score: 1

      Agreed, but let's face it. Everyone running their own version of Android is a fragmentation that can be handled vs everyone running their own closed phone OS. Now think of the joy of developing software in that kind of future with HTC-OS, Samsung-OS, Motorola-OS etc.

    2. Re:Smart move by Anonymous Coward · · Score: 0

      Why not just test on stock Android phones and redirect all "doesn't work on my phone" support complaints to the folks that deviated from your test platform?

  34. enforce licensing its terms while breaking others? by dndk82 · · Score: 1

    in order to make others respect Google's licensing terms, Google must first obey the open source license that applies to Android: don't delay releasing their Honeycomb source code

  35. Re:The Case for Google's Control: Atrix by elrous0 · · Score: 1

    The point of Android is to sell phones. It's not a social experiment. If you want to see how commercially successful it is to let anyone fork their own version, take a hard look at how far it got Linux. Dozens of distros and not a one of them ever even came close to mainstream success.

    --
    SJW: Someone who has run out of real oppression, and has to fake it.
  36. Re:The Case for Google's Control: Atrix by bemymonkey · · Score: 1

    Unfortunately an option on any of the current Motorola lineup, and that lineup seems to be the go-to choice for regular Joes...

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

    Google tried making phones and nobody wanted them. So now they're going to slowly stop sharing their OS, hey?

    There's a company that's been doing that for a while now... oh yeah, Apple.

  38. Re:The Case for Google's Control: Atrix by ceoyoyo · · Score: 1

    So what you're saying is that open source is not viable for commercial products?

  39. 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'.

    1. Re:Powered by Android (TM) by ebs16 · · Score: 1

      If Google does as THX did, they would give the "powered by Android" brand to phones running Symbian, Windows Mobile, and other sub-par operating systems.

  40. Re:First by clang_jangle · · Score: 1

    Pretty sure it's an attention-seeking behavior. It's probably two or three 12-year-olds who are responsible for every FP on the internet.

    --
    Caveat Utilitor
  41. Wrong problem by rickb928 · · Score: 1

    Most fragermentation up to now has been due to hardware. My G1 (and the MT3G) won't run Gingerbread, no matter what. The OS finally outgrrew the old hardware.

    Now, my G1 does run Froyo, CM 6 something, but that is a struggle.

    And the memory constraints weren't limited to those phones. A few Moto phones also lack memory.

    The next big problem is melding the UI some makers have into a new release. Blame openness.

    --
    deleting the extra space after periods so i can stay relevant, yeah.
    1. Re:Wrong problem by Anonymous Coward · · Score: 0

      That's the funny thing though.

      Launcher Pro and the like all run on top of Android 1.6 all the way to 2.3 without any problems and is removable by the user. The same app. Why can manufacturers do the same?

      Toss it in an obscure place for all anyone cares -- just give us the option.

    2. Re:Wrong problem by LanMan04 · · Score: 1

      I use Gingerbread as my daily driver on my MT3G (original). Works fine, seems just as fast as CM6/Froyo. A little swap and overclocking goes a long way, as does the new (well, months ago new) radio that frees up about 10MB of RAM.

      http://forum.xda-developers.com/showthread.php?t=932118

      I'm running RC6.1 as we speak.

      --
      With the first link, the chain is forged.
    3. Re:Wrong problem by rickb928 · · Score: 1

      I'm thinking of SenseUI etc. Launcher Pro isn't a Samsung or Motorola product, is it?

      Asking "Why can (sic) manufacturers do the same?" misses the point entirely. The manufacturers use their own skins to add perceived value, differentiation, and revenue (ads, paid placements, etc.).

      Just accept that manufacturers will keep adding skins no matter, and that problem will delay them delivering new releases. And remember when you bought a phone, and whatever it was on the day you bought it, that's all it ever was. Android is a big leap past that, even with frags.

      --
      deleting the extra space after periods so i can stay relevant, yeah.
    4. Re:Wrong problem by rickb928 · · Score: 1

      I can't quickly get a straight answer if Yoshi will run on my 32B witrh radio 2.22.23.02 (DangerSPL) and HBOOT 1.33.2005 (2k5 kernel hack). It SAYS radio 2.22.28.25 or 27.08, no kernel notes, but I suspect I get a new kernel with the ROM. And I will need a new SPL, 1.33.0013 or 1.33.0013d apparently, something of a downgrade I think, so I'll lose some RAM, like 15MB off the top maybe... They say 013d solves that, at least it's Danger-compatible.

      I had enough trouble with CM, I'll try Yoshi when I've got a weekend to flash/wipe/restore/wip/restore/flash/wipe/restore/reinstall. I've had my G1 bricked so bad it needed to be JTAG'd, and I need to actually use it, so I'll wait until I get my other G1 back in the new casing...

      --
      deleting the extra space after periods so i can stay relevant, yeah.
  42. Re:The Case for Google's Control: Atrix by everett · · Score: 1

    I think you're trying to say that this is not an option on Motorola devices to which I reply interesting.

    Posted from my Droid running Cyanogen Mod 7.0 RC 4.

    --
    Sig withheld to protect the innocent.
  43. Re:The Case for Google's Control: Atrix by GameboyRMH · · Score: 1

    Yeah and the point of an e-Fuse is to prevent you from doing that.

    If HTC were to release some open phones that the user could choose to install Android or MeeGo on, they'd at least become the go-to phone manufacturer for geeks, and probably take a big bite out of the mainstream Android market.

    --
    "When information is power, privacy is freedom" - Jah-Wren Ryel
  44. Hopefully this will temper some of the Apple hate by Anonymous Coward · · Score: 0, Insightful

    Disclaimer: I'm an iPhone user.

    I think this is a necessary move by Google, in the face of the carriers' crapware (and it was naive of Google to think that they would do anything otherwise). To be truly competitive with the iPhone, there needs to be a strong association of a consistent, positive experience with terms "Android" and "Google Phone." Random crapware on phones hurts their brand. Carriers need to be hit over the head with legalese, as the only means of accomplishing this. Google recognizes this and is taking steps to ensure they continue to gain market share and don't erode the brand.

    So we can see that a fully open model doesn't work well in the mobile phone space. Decision to postpone the release of Honeycomb source, amongst other things, is an admission that "too open" hurts business in this space.

    Most reasonable people are happy that Google is making this move. I am happy, because for me, this makes Android a more viable option in the future (and we all, as geeks, love to have options).

    Most reasonable people will also understand that Apple's "uniform experience" position is not merely a stubborn act of greed, but is a conscious engineering design decision, rooted in reality of the carriers. Apple doesn't let AT&T preload crapware on the iPhone because they know it will damage the brand. Apple also knows that if given the opportunity to do so, AT&T WILL preload that crapware, without fail.

    TL:DR version: Apple haters, how's that "Android is open" pie tasting now.

  45. 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.
    1. Re:Allow fragmentation, but without the trademark by Anonymous Coward · · Score: 0

      I wish I had mod point.

      This is what oss has been all about. No need to fuss over it let alone an article on Wlashdot! OSS is funny when you think about it : When you change the platform (in this case, from pc to phone) they all jump in the same hoops , making the same mistake along the way. Google should have known better.

    2. Re:Allow fragmentation, but without the trademark by Anonymous Coward · · Score: 0

      This was called a "Google Experience" device. The original Droid was a Google Experience device, and very little else ever was. The manufacturers decided to rely on their crappy skins instead of hardware (what we all really want) as a differentiation factor, and as a result, today there's little to no Google Experience devices available. If it wasn't for the fact that Honeycomb is such a significant change, even the Xoom would have been disfunctionally blurred.

      Originally, for the Google name to be marked on the phone the device had to be "Google Experience", coming with stock Android and the Google applications. This is the main reason the original Droid ended up getting all of the latest software updates months before anything else (except the Nexus One of course), and ironically is quite a bit better software wise than all of this bloated sense/blur/touchwiz crap. I think that since nobody jumped on board with the Google Experience idea, they dropped the requirements in order to get Android going in the marketplace. Perhaps it's time to bring it back..

      The sad thing is, I like the Droid, and would be happy with one with current hardware specifications, but now I cannot buy a Motorola device because it'll come screwed to hell with blur, almost never get an update because of it, and then be further crippled to hell by Verizon. The worst part of it is that while there's hundreds of handsets, almost nothing offers a keyboard with current hardware and STOCK android. Rooting or running a custom ROM on any phone is a poor decision from a security and stability standpoint. Google needs to get with the program and drop a Nexus device with a keyboard (touch screens are horrible, and putting up with it shouldn't be a requirement).

    3. Re:Allow fragmentation, but without the trademark by Twinbee · · Score: 1

      I agree with other replier.

      Modders, please mod parent up.

      --
      Why OpalCalc is the best Windows calc
    4. Re:Allow fragmentation, but without the trademark by imlepid · · Score: 1

      Restricting use of trademark is one good solution. (That's how Red Hat does it.)

      Another is to have a "Google Approved" set of Android phones. Such approval could vary from extensive testing of the phone to Google dictating certain specs such as screen resolution. Apple made the "retina display" twice as big (480x320 -> 960x640) on the vertical and horizontal scale compared to the older 3GS version to make old apps still work with no lost space (unlike running iphone apps on ipads). There are good advantages to the end user when a manufacturer controls those details, but it does slow innovation. Having a set of approved phones with tight control by Google could help the Android area sharpen up its lineup.

      (Anecdote: I have a friend who has a Galaxy phone and he's constantly complaining that it crashes. This is probably in part due to lack of testing of software on Samsung's part, but I couldn't say for sure.)

    5. Re:Allow fragmentation, but without the trademark by Matheus · · Score: 1

      Mod parent above 5 please ;-)

      This is exactly what Google should be doing. Open Source gives the end user a lot of Freedom but Google has the right to do certain things for the benefit and success of their "product".

  46. Re:Hopefully this will temper some of the Apple ha by Uksi · · Score: 1

    Oops, accidental A/C post

  47. Do No Evil by dmomo · · Score: 0

    Easy. Redefine Evil. That's innovation!

  48. 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 LodCrappo · · Score: 1

      I never saw anyone say there was no fragmentation in the Android world. I heard lots of people say that fragmentation wasn't a problem, and I'd tend to agree with them. Before the anti-Android crowd made up this "fragmentation" thing, we used to use terms like "variety", "diversity" and so on.

      --
      -Lod
    2. 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.

    3. Re:So... there is fragmentation after all. by LodCrappo · · Score: 1

      I supposed we tend to see what we're looking for. Seems to me it isn't a world of such "all or nothing" extremes. IMHO the diversity found in the Android world hasn't caused any significant problems and has lead to a great deal of variety in innovative devices from many companies. Now Google is trying to put some additional standards in place so that we don't run into problems down the road, probably in response to lessons learned over the past couple years. This isn't a massive change. They aren't locking down the platform or reducing the marketplace to a single model from a single manufacturer, so I still see Android as a superior platform to some of the competition. Are they "less superior" for making these changes? Time will tell.

      --
      -Lod
    4. Re:So... there is fragmentation after all. by O(+inf) · · Score: 1

      Most of the talk (and FUD) about Android fragmentation is from developer's perspective. This initiative does nothing about it - it is purely about fragmentation of UI from user perspective, which is a different and real issue. Samsung Android phones look different from HTC phones which look different from stock Android.

    5. Re:So... there is fragmentation after all. by tooyoung · · Score: 1

      Before the anti-Android crowd made up this "fragmentation" thing, we used to use terms like "variety", "diversity" and so on.

      So what do you think about google clamping down on "variety" and "diversity"?

    6. Re:So... there is fragmentation after all. by LodCrappo · · Score: 1

      I'm not sure yet. In a perfect world, manufacturers would make good choices that added value to the Android platform, without any need for rules or supervision. It seems that Google has some reason to believe they will not be perfect. I don't know whether this is an appropriate way to make Android better, or if it even will make Android better, but Google seems to think it will and I've got to assume they know more about what is going on than I do. That doesn't mean I blindly support their actions here, but I can't condemn they either.

      --
      -Lod
    7. Re:So... there is fragmentation after all. by LordLucless · · Score: 1

      There is no fragmentation - not in the sense that was being discussed. People just seem to chuck "fragmentation" into any story about Android. Previous criticisms over fragmentation were generally that there were too many hardware variants for developers to support. This, as far as I can see, is a complaint that shoddy proprietary interfaces screw up the customer's experience and ruin Android's rep. There's really nothing fragmentary about it.

      --
      Just because you're paranoid doesn't mean there isn't an invisible demon about to eat your face
  49. Re:The Case for Google's Control: Atrix by rtaylor · · Score: 1

    I think he's saying open source does not make a commercial product immediately viable.

    Very few people run out and buy something just because it is open.

    --
    Rod Taylor
  50. Re:The Case for Google's Control: Atrix by ceoyoyo · · Score: 1

    Google isn't, and hasn't, objected to e-Fuses or other locking mechanisms.

  51. Trademarking as a less draconion solution? by IAmAI · · Score: 1

    Would a more FOSS friendly approach be for Google to use Trademark law, by only allowing mobile phone carries to advertise their phone as using Android if it uses a derivative that meets Google's standards? I presume this would still allow anyone to freely use the source code for Android and manufacturers to freely produce phones with an Android based OS and lock it down however they want. However, for end-users who are concerned over the implications of Android fragmentation can avoid phones that are not advertised as 'Android, as approved by Google'. Is this feasible? Is this fair?

  52. Lucky for you... by Rob+Y. · · Score: 1

    Lucky for you, Google's model for maximizing profit depends on a free and open internet based on freely implemented standards. And they do that so they can keep making a bundle providing the best internet search tool around (with the least obtrusive advertising model). That means Google makes money by making Android exactly what you want it to be. A pretty good deal all around. No wonder nobody's screaming that they're against software freedom - they're not.

    --
    Posted from my Android phone. Oh, I can change this? There, that's better...
    1. Re:Lucky for you... by MadeInUSA · · Score: 1

      Lucky for you, Google's model for maximizing profit depends on a free and open internet based on freely implemented standards. And they do that so they can keep making a bundle providing the best internet search tool around (with the least obtrusive advertising model). That means Google makes money by making Android exactly what you want it to be. A pretty good deal all around. No wonder nobody's screaming that they're against software freedom - they're not.

      Nobody? RTFA! This post is exactly about how Google is beginning to restrict software freedom.

  53. 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.
  54. A passing thought by Ensign_Expendable · · Score: 1

    I'm no expert in open source use conditions, so I won't mind being *ahem* corrected if I display my ignorance here. I totally understand Google wanting to exercise control over the Android OS to avoid some of the nightmares that are happening with carrier customizations, etc. But if they wanted to manage Android that way, shouldn't they have developed (or purchased) their own OS, and not used open source?

  55. Probably would have saved the GTab... by modi123 · · Score: 1

    Well I am torn. See I recently picked up a Viewsonic G-Tablet. A nifty little bugger (odd viewing angles, but hey - I don't care that some schmuck next to me on an airplane can watch my Angry Bird Marathon in full crisp color) and all sorts of snappy hardware. The problem is Viewsonic's OS flavor is poop. A giant pile of poop. Their half-assed "market place" is crippled and broken. Lacking 99% of everything. Why?! why smear good hardware with da poo-poo? Thankfully I educated myself a head of time, found a nice group of folk who have rooted the bastard device and developed their own ROMs (think OS). I had to root mine just so I had access to Android Market Place. While dinking with it I did soft-brick it for about an hour until I found out what combination of ROMS were going to work. Fun fun for three hundred bones, right?

    Personally I have no problem if these manufactures want to 'theme' their devices or add specific apps to it, but for god sakes most are not in the "OS making business" and there's a reason for that!

    1. Re:Probably would have saved the GTab... by Gruuk · · Score: 1

      I also recently bought the g-Tablet, a splendid tablet once flashed with another ROM (aside from the screen, which isn't as bad as I had feared based on all the reviews I read). Viewsonic completely dropped the ball on their customization of Android, making a tablet superb hardware specs (same CPU as the Xoom) slow and unstable. It's sad that there are multiple hacker developed ROMs that completely crush the stock version performance- and stability-wise.

      Google's announcements do mean that Honeycomb ROMs are still many months away, which is unfortunate. Still, XDA developers have done a fine job with Froyo; with gingerbread ROMs in the works, I don't feel bad about having to wait a bit more for Honeycomb.

      --
      De gustibus et coloribus non est disputandum
    2. Re:Probably would have saved the GTab... by pulski · · Score: 1

      XDA to the rescue. :)

      Not only is the built in rendition of Android a giant pile of poop, it is a Jurassic Park, sick Triceratops, pile of poop. In fact, before I ran the OTA update, it would crash and Force Close programs *constantly*. The G Tablet lasted all of 24 hours in my possession before it had been rooted and flashed with VEGAn-Tab.

  56. Re:The Case for Google's Control: Atrix by ZenDragon · · Score: 1

    Except that Google didnt try to make anything, HTC made the phones. Google just wanted to control their own distribution channel. And who said nobody wanted them? They pulled back the N1 due to hardware issues and realized that they didnt want to get involved in the handset market. Apple on the other hand wants control over every step of the process.

  57. Legal by metrix007 · · Score: 1

    If I have a device running honeycomb and request the source, don't google have to release it to me immediately? Not 1 year from now or when they decide it's ok?

    --
    If you ignore ACs because they are anonymous - you're an idiot.
    1. Re:Legal by maxwell+demon · · Score: 1

      AFAIU at the time the hardware is on sale, Google will also allow access to honeycomb. Before that time, you'll not be able to get a device running honeycomb.
      Of course, the manufacturers should in principle be allowed to already distribute the code they got. However, I don't think it's in their best interest to do so, because they would lose their early-access advantage.

      --
      The Tao of math: The numbers you can count are not the real numbers.
    2. Re:Legal by iburrell · · Score: 1

      The Android user-space isn't GPL licensed but mostly licensed under ASL2.0. They don't have to make the source available on request. But people are allowed to distribute the binaries and to distribute the source if they have it. The Android Linux kernel is GPLv2 licensed and the source, including Honeycomb, is available at http://android.git.kernel.org/.

    3. Re:Legal by VGPowerlord · · Score: 1

      AFAIU at the time the hardware is on sale, Google will also allow access to honeycomb. Before that time, you'll not be able to get a device running honeycomb.
      Of course, the manufacturers should in principle be allowed to already distribute the code they got. However, I don't think it's in their best interest to do so, because they would lose their early-access advantage.

      *checks online stores*
      *spots Motorola Xoom, which runs Honeycomb, currently for sale on NewEgg*
      *Notes that Honeycomb source is not currently published*

      TL;DR: You understand incorrectly. Honeycomb tablets are in stores now, but the source hasn't been published.

      --
      GLaDOS for President 2016! "Well here we are again. It's always such a pleasure." -- GLaDOS, 2011
  58. Re:The Case for Google's Control: Atrix by bemymonkey · · Score: 1

    Correct, my statement was missing a "not".

    Your objection is duly noted - however, your Droid is not part of the current Motorola Android lineup (it was replaced by the Droid 2), and was the only mid-high end Moto device to have a non-signed bootloader.

    RC4 rocks, btw... running it right now myself :)

  59. Re:The Case for Google's Control: Atrix by Rich0 · · Score: 1

    Well, it probably doesn't legally void the warranty, but it will take you a few years in court to settle that one...

  60. Re:The Case for Google's Control: Atrix by Anonymous Coward · · Score: 0

    WHY does everyone complain about Motorola? I don't find anything wrong with the software on my Motorola Android phone. Motorblur is somewhat useful. It is not hard to remove unneeded software from your Android device. If you don't like AT&T Navigator, then don't use it. Or remove it like I did.

  61. 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.

  62. Standards by theygoto11 · · Score: 0

    "The nice thing about standards is that there are so many to chose from." -Andrew S. Tanenbaum

  63. Microsoft Approach by Anonymous Coward · · Score: 0

    Any reason Google could not take Microsoft's approach to Windows? Manufacturers can put whatever they want just like they do on say Windows laptops but user can always put a Google "retail" copy of Android on the SD Card that'll download the device specific drivers and software just like how Windows does it.

    It requires more resources on part of Google and also requires manufacturers to submit their device drivers and required customizations but that can only be good.

  64. Google is a publicly traded company by captaindomon · · Score: 1

    I don't think people have realized yet the incredible impact it has on a company to have an IPO and become publicly traded. Going forward, Google is going to start operating a lot more like any other publicly traded company, because the investors are now in charge, in the long run. Their purpose now is to increase the value of their shareholders, that's just the way it works if the public owns your company.

    --
    Just because I can hook a shark from a boat, I do no offer to wrestle it in the water.
  65. Re:Is it just me? by Anthony+Mouse · · Score: 1

    It's kind of ironic how the problem seems to have been created by Google (and really, Android before them) choosing the Apache license rather than the GPL. The manufacturers keep installing all of their crapware because they think it makes their devices distinct so that they can compete on something other than price. Or at least get some money from spammers for putting their spam on your phone. If they had to distribute their modifications then they wouldn't have the incentive to fork for the sake of forking, and the community would have a spam-free version of any positive modifications running in about 30 seconds.

  66. Fragmantation is even worse for open source. by Anonymous Coward · · Score: 0

    Look at the results, the Linux kernel is almost 20 years old and yet it has only 0.7% market share. Steve Jobs and Steve Balmers iron fists control 6% and 90% respectively. Ubuntu is even worse. It started of with a version of gnome and added propreitary drivers and plugins to make it more usable, but then used its realitive to other linux distros market share to impose its own vision of a GUI (Unity), screwing GNOME (3.0 didn't help either) and the other *buntus as well. Firefox fragmented itself over the awesomebar and status bar and soon the "social plugins". So did OpenOffice.org with Oracle's messups. Because they rested on their laurels allowing Chrome and LibreOffice to catch up, and they will be surpassed in the future by other newer and "hipper" software.

    Android is yet another example of too many cooks and too many wannabe Steves. Put android in a titanium straightjacket and slim him down from all those fattening desserts and release a version based on healthy food.

  67. Re:The Case for Google's Control: Atrix by Anonymous Coward · · Score: 0

    ...and if they did, you'd be bitching about how they're not "open."

  68. API standards and a user app to test them. by bobs666 · · Score: 1


    IMHO, rather then lawyering up with licensees, let the prospective buyer of hardware download a test sweet that checks the API. If this check fails customer then knows that the phone is not an Android.

  69. Re:The Case for Google's Control: Atrix by rolfwind · · Score: 1

    This has been the bane of Windows for years. I never understood why Acer sells computers with bloatware as that shit just hogs the hell out of the CPU and HDD and must have just given them a bad name more than anything.

    This lack of stupid shit is what makes Apple's more pleasant to use out of the box and a strong argument to retain control of the environment -- the fact that Google is now doing this is basically a submission that Apple was correct in this regard.

    (P.S. I'm just speaking of this specific aspect of OEM crapware and don't approve all of Apple's practice's across the board.)

  70. Re:The Case for Google's Control: Atrix by Anonymous Coward · · Score: 0

    ... so don't buy a crap phone from a crap carrier? You can always buy a Nexus series phone with plain android: http://www.google.com/nexus/

  71. Re:The Case for Google's Control: Atrix by rolfwind · · Score: 1

    I have never seen mass licensed OEM manufacturers add much in value to the software of the hardware they're selling. Mostly the exact opposite. Whether it be computers or phones. Most pre-Smartphone phone software imo sucks, as does most of the hardware interface.

    Manufactures don't make good designers imo.

  72. Re:Hopefully this will temper some of the Apple ha by maxwell+demon · · Score: 1

    Random crapware on phones hurts their brand.

    As someone else suggested, they could tightly control the trademark instead. Just deny the phone makers calling their OS Android, or using the terms Android or Google in their advertising, if the derived code doesn't have Google's blessing. That way phone makers have the choice whether they sell an "Android phone" and comply with Google, or if they just use the code, but don't mention Android in their advertising.

    That would help Google, because it would make sure that everything sold as Android phone follows their guidelines, but it would still allow phone makers to make any change they want - they just cannot call the result an Android phone. And since the modified phones cannot draw popularity from the Android name, they cannot simply add crap, because no one would buy that. If they cannot sell it through the Android name, they have to sell it via an improvement for the user.

    --
    The Tao of math: The numbers you can count are not the real numbers.
  73. Re:enforce licensing its terms while breaking othe by Anthony+Mouse · · Score: 1

    Haven't we been over this? Parts of Android are licensed under the GPL (mostly the Linux kernel) but most is under the Apache license. They've released the modifications to the GPL bits as required and the Apache license doesn't require them to release the rest.

    Of course, what they really ought to do is just release the whole thing under the GPL in the meantime. Then the open source people are happy but it keeps the manufacturers from making immature devices because they don't want to distribute their modified versions and in so doing be required to publish the source to the changes, so they'll want for the "official, final" release under the Apache license.

  74. 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.

  75. theming by alienzed · · Score: 1

    seems to be the real goal of the people who want to modify the software, why doesn't Google close the source but invest in a powerful theming architecture? In fact, Apple should do the same and then no one would prefer Android. The world is all about micro customizations these days, but only aesthetically, because functional principles are either good or bad, they aren't decisions the user should make.

    --
    Never say never. Ah!! I did it again!
    1. Re:theming by rogerdugans · · Score: 1

      Theming is a part of what people do, but only a part. And most- if not all- of that CAN be done now.

      Most Android phones are customized with applications that cannot be removed or easily kept from mucking up the phone one way or another.
      Some users DO like them. Some users despise them for the negative affect on functionality.

      Most people just don't know anything can BE done or if they do are not willing to take the risks involved with rooting and installing a custom rom on their phone.
      It is the functional principles you speak of being either good or bad that the carrier/manufacturer agreements and products make and screw up phones with.

      And I think it likely that THIS is what Google aims to fix.
      Hopefully....

      --
      Linux computers, watercooled, photography
  76. Re:The Case for Google's Control: Atrix by gbjbaanb · · Score: 1

    If that's the case, and its not a problem, then why are these carriers/manufacturers locking the device down so much. You'd think they'd be happy to sell you a new phone.

    Can a factory reset not fix it anyway, or would you need to blow a new rom onto it? If so, couldn't the manufacturer put a copy of the original roms in there too ready to copy over the new one - like my motherboard has.

  77. Good for google...the upgrad gravy train might end by grapeape · · Score: 1

    I realize that many of the phone manufacturers might be upset with this but in the long run its going to help solidify Android as a viable platform. The upgrade game that many of them are playing now is downright scammish. I have a phone I spend nearly $600 on less than 8 months ago that has not been offered any sort of upgrade...instead the manufacturer offered up a new version of the phone, it wasn't a hardware issue, the new one is virtually identical internally, it appears the issue was simply...hey if we dont offer an upgrade we can sell them the new one. I felt burned enough by it that I switched to an iphone, i would have rather stayed with android but as the saying goes...screw me once shame on you...I wasn't setting myself up to get screwed again. The customized interfaces on vendor devices and lack of vendor support on upgrades is what has caused all the fragmentation, rooting and custom kernels to start with. In the end I guess it will hurt some manufacturers since the only real differences between devices will end up being the hardware itself but that also is good for consumers, it means they will have to up their game to compete and stay relevant.

  78. 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
    1. Re:This is total bullshit by Anonymous Coward · · Score: 0

      Yes except if Google picked the right fucking license in the first place none of this would be happening.

      ps, i'm not just another suddenly "Oh noes! Google has become evil!" fucktard. Google has been the scum of the internet for nearly a decade.

      How can you trust the most trusted (not most trustworthy) company on the planet?

    2. Re:This is total bullshit by Anonymous Coward · · Score: 0

      > ps, i'm not just another suddenly "Oh noes! Google has become evil!" fucktard. Google has been the scum of the internet for nearly a decade.

      Oh, ok. So you're a more complete kind of fucktard.

    3. Re:This is total bullshit by JabberWokky · · Score: 1

      It seems if I get the actual story correct that it is the same terms (that you not call it under the name of the original author's project if you make changes to it) that were the reason a bunch of people and groups (like debian) rejected ion3 and argued with the author until he washed his hands of the whole thing and quit open source?

      Sure, the code is open. The project identity is another thing entirely. Some of the larger groups (KDE, for instance) have run into this and split the project identity and actual codebase (or for KDE, codebases) into distinct categories. What is Android? It's code, sure, but I (and apparently Google) would say it is also an expectation of certain conventions and available tools.

      --
      "$30 for the One True Ring. $10 each additional ring!" -- JRR "Bob" Tolkien
    4. Re:This is total bullshit by Anonymous Coward · · Score: 0

      Are you kidding? You're a lunatic. How the hell is this modded insightful?

      Yes it's microsofts fault that Google has incredible fragmentation and are finally doing something about it. Nobody does anything and nothing happens to anyone without the sinister hand of Microsoft behind it. They used your junk OS and gosh, ran into the same fragmentation problems Linux has. What a shock.

      Does apple have a hand in it too? With their sinister iTunes monopoly?

  79. Re:The Case for Google's Control: Atrix by Anonymous Coward · · Score: 0

    What hardware issues? My one is working fine.

  80. Just use TM by Raccroc · · Score: 1

    Going about it the wrong way...what they should be doing is taking a page out of the Red Hat playbook and just protect the Google TM within Android. Then they could just set forth specific rules which must be strictly followed in order to say this is an Android device and to use any of Google's TM within.

    For example:
        Create a directory structure for 3rd party (non-ASOP) drivers, libs, and config scripts which must be used and prevent manufacturers/providers from altering or removing other files/folders.
        Force manufacturers/providers to allow users to use default Android applications in place of 3rd party apps through some standard means.
        Weigh in with yes/no on things like encrypted boot loaders, rooting, preventing side loading of apps, etc.
        [Add whatever rules which are causing fragmentation problems or allowing such monstrosities as Viewsonic's Tap'nTap here!]

    What this should do, is allow manufacturers/providers who do not care about being labled as Android to do as they please (the B&N NOOK, for example, may not care at all if they get to put a little robot sticker on the box or not since it is such a specific device). Manufacturers/Providers who DO care, would be forced to follow the rules if they want to take advantage of Google's advertising, marketing, and reputation.

    As a side benefit of going this route, they could also do things like strike back at MS forcing Bing on everyone within WM7 by specifically banning it from Android(TM).

  81. Re:First by neo8750 · · Score: 1

    are we going by mental or physical age?

  82. Android != GPL by itsdapead · · Score: 1

    If I have a device running honeycomb and request the source, don't google have to release it to me immediately? Not 1 year from now or when they decide it's ok?

    Only the parts which are covered by the GPL - such as the Linux kernel.

    Most of Android is covered by the Apache license which doesn't oblige you to provide source to users.

    Plus, Google can do what the hell it likes with their own code, provided its not a derivative work of other people's GPL code. (see any GPL FAQ for the rules)

    --
    In a survey of 100 programmers, 111111 thought that duck-typing was a good idea.
  83. Re:The Case for Google's Control: Atrix by Dishevel · · Score: 1

    But you can.
    Gain root on your device and you can make all kinds of changes.

    --
    Why is it so hard to only have politicians for a few years, then have them go away?
  84. Re:The Case for Google's Control: Atrix by Anonymous Coward · · Score: 0

    Because Motorola done the following:

    1: Explicitly told the modder community to go elsewhere.

    2: Encrypt bootloaders. So far, the Droid is the only Motorola handset that one can truly flash a custom ROM on. Yes, other devices have ROMs, but they all do kexec() functionality, executing on top of a signed kernel.

    3: Motoblur cannot be removed. In fact, newer phones will soft-brick until you reflash it.

    There are other modder friendly devices. HTC phones have always been up to snuff in this department, if one doesn't buy a dev phone or one of Google's devices that can be easily unlocked from fastboot.

  85. Won't work because of drivers by Nimey · · Score: 1

    Your vanilla Android is just that - no drivers for vendor-specific hardware. I'd rather keep the crappy vendor Android if it means I can still use the accelerometer and camera, and power management works.

    --
    Hail Eris, full of mischief...

    E pluribus sanguinem
    1. Re:Won't work because of drivers by jarich · · Score: 1

      Drivers can be dropped into standard spots on standard Android releases and the same concept still holds. The various vendors are already testing this, they just load a ton of crap on top after they do the testing.

  86. Re:The Case for Google's Control: Atrix by Anonymous Coward · · Score: 0

    Mod parent up. To paraphrase the Matrix: What good is the source code, if you are unable to compile and install it?

    The source code can be educational. There is more than one way to use source code. One is to compile, install, and run it. Another is to read it and get ideas for design and implementation.

  87. Re:The Case for Google's Control: Atrix by HateBreeder · · Score: 1

    You get the choice of buying android from a different carrier/manufacturer.

    With apple, you're stuck with iTunes... no other choice or option.

    --
    Sigs are for the weak.
  88. Re:First by BlackSnake112 · · Score: 1

    Mental of course. For one may be physically 12 years of age only for 1 year. However, one can be mentally 12 forever!

  89. openness by jDeepbeep · · Score: 1

    Thankfully, Android is open and you can just rip away all the garbage some carriers push into it.

    Real openness would be me being able to
    make install
    without rooting the device.

    --
    Reply to That ||
  90. Re:The Case for Google's Control: Atrix by Anonymous Coward · · Score: 0

    businesses should modify on behalf of customers.

    trying out new ideas is not equal to trying out how to get people pay even more money for something, they already paid for.

    not being able to use a device with the original source is not the intention of open source. nobody hinders the customizers to use the open source version and adapt it when the next version is coming out or invest in the technology they are using by applying to rules.

    this however, turns out to be the real problem we encounter. so it depends on the customer to select compatible devices, those who refuse might fragment and die or survive and be dealt on its own.

  91. Re:The Case for Google's Control: Atrix by PReDiToR · · Score: 1

    The point of Android is to sell phones

    No, I disagree. The point of Android is to get people relying on Google and their services.
    No matter which version of Android you're using, they have your info. They know what apps you run, where you are, what networks you connect to, they have the ability to use your phone like they were holding it in their hands, they keep the keys to your credit chip in the next version.
    Who cares who makes the phones or how many they sell? That isn't Google's problem. Being able to backport the latest version of Android, or its features is a non-issue for Google.

    The problem comes when Canonical, IBM, Novell, Microsoft, Sony or Cisco decide that they can run their own servers to let users who replace Android with a GNU/Linux phone distro connect to and sync with.
    This is what Google fears. Linux on phones without Dalvik and without them having the keys to your world run through their servers every few minutes.

    And if I sound a little paranoid just drink this Kool Aid:
    They only want to use all that information to serve you the right adverts in a form you won't block and which are relevant to you.

    --

    Do not meddle in the affairs of geeks for they are subtle and quick to anger
  92. Re:Hopefully this will temper some of the Apple ha by metamatic · · Score: 1

    So we can see that a fully open model doesn't work well in the mobile phone space.

    I don't think anyone on Slashdot ever thought it was good that Android was open to the carriers. We care about whether it's open to the end user.

    If I have to choose between a phone that's open to the carriers and one that's closed to me, I'll still take the former.

    --
    GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
  93. Re:The Case for Google's Control: Atrix by xouumalperxe · · Score: 1

    You're absolutely right. Having the code is great in and of itself. Unfortunately, you're also absolutely missing the point. When people here compare android phones and iphones, the "Android is free/open source" argument keeps coming up. Unfortunately, that openness argument goes right out the window when carriers and/or manufacturers lock down the hardware so that you can't compile really overwrite the firmware without a jailbreak. Past that point, the biggest difference between iOS and Android in terms of openness is the app store, not the operating system itself. And that is what's being discussed here.

  94. It all makes sense now by Anonymous Coward · · Score: 0

    I finally get it. By delaying the open source release by one release cycle and only allowing code access to privileged partners, those partners get a head start at releasing the latest version of android on their devices. That means that these privileged partners can use this head start to have upgrades available within weeks after the xda custom rom crowd (who must wait for the open source release) puts out an unofficial upgrade for the same device. Anyone who's afraid of rooting their phone may be tempted to just wait a few extra weeks for the "official" version, and thus there's "less fragmentation" among android devices. Brilliant.

  95. Fixed that for you by Anonymous Coward · · Score: 0

    Lucky for you, Google's model for maximizing profit depends on selling your personal information to advertisers. And they do that so by providing the best internet search tool around. That means Google makes money by making Android exactly what you want it to be as long as you have no privacy. A pretty good deal all around. No wonder nobody's screaming that they're against software freedom - they're not.

  96. Re:First by BronsCon · · Score: 1

    And what is this?

    --
    APK quotes people (including myself) without context and should not be trusted. Just thought you should know.
  97. Re:The Case for Google's Control: Atrix by icebike · · Score: 1

    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.

    So skins are what makes Android usable or unusable? Is that what you are saying?

    And Atrix is unusable because you can't get your favorite skin on it? Wow. There are sure a lot of Atrix phones sitting un-used then because the vast majority of users never hack their phones.

    And Google Maps and Navigation appear on the Atrix, and you can even set them ad default and never worry about AT&T navigation ever again. Where's the problem here?

    The real problem is that Google designed Android WRONG, and those phone makers and carriers who want to add features and customization can't do so cleanly without rebuilding Android to hang in their desired changes.

    What if every point release of Windows or Linux kernel had to wait for every package, every desktop (KDE, Gnome, XFCE) to be updated before you could slip it in? What if Dell or Acer or HP couldn't ship any laptops just because they couldn't get their bloatware to run until they hacked the next minor release of windows?

    When Google figures this out, and repackages Android so that you can slip in OS updates without destroying carrier specific layers then the fragmentation will stop.

    In the mean time, its pretty much a tempest in a tea pot, since somewhere approaching 90 percent of all Android installs are in two versions of Android, 2.1 and 2.2. See http://www.androidcentral.com/sites/androidcentral.com/files/articleimage/684/2011/04/android-versions-4-2.jpg
    Fragmentation is largely a figment of the past rapid development cycles.

    --
    Sig Battery depleted. Reverting to safe mode.
  98. 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
  99. Re:The Case for Google's Control: Atrix by tepples · · Score: 1

    You get the choice of buying android from a different carrier/manufacturer.

    When all three carriers lock down the phones designed for their respective networks in undesirable ways, I have the Hobson's choice of doing without.

  100. Re:The Case for Google's Control: Atrix by bonch · · Score: 0

    Well, the spirit of openness is that any ideas are allowed if someone wants to fork and implement them. Besides, nobody's forced to use a smartphone.

  101. Having to move to get a Nexus phone by tepples · · Score: 1

    The Nexus phones are on T-Mobile USA, the most geek-friendly carrier at the moment. But notoriously geek-hostile carrier AT&T will soon gobble up T-Mobile USA. Then Nexus will move to Sprint, if the page you linked is any indication. But one might have to move to a different city or state in order to be in a "good" carrier's coverage zone. There are plenty of states with no coverage other than roaming, and plans aren't offered to people who live or work in a roaming area.

    1. Re:Having to move to get a Nexus phone by Anonymous Coward · · Score: 0

      The problem is that geeks are notoriously the worst possible customer to have, as they will suck your resources dry, try to avoid paying for anything, and bitch incessantly with or without cause, then put forth arguments about how they deserve to be coddled because they were born.

      I avoid serving geeks myself. You all suck. I'm not in business to donate to you fuckers.

  102. Re:The Case for Google's Control: Atrix by tepples · · Score: 1

    Well, the spirit of openness is that any ideas are allowed if someone wants to fork and implement them.

    The technologies behind the phone networks themselves are patented, and the spectrum on which they operate is exclusively licensed to four, soon to be three nationwide companies. With no patent license and no spectrum, how does one "fork and implement them"?

    Besides, nobody's forced to use a smartphone.

    So what should I use instead of a smartphone to accomplish the use cases commonly associated with smartphones?

    "It looks like you're playing the Hobson's choice card. Would you like help?" I don't see "don't use a smartphone at all" as germane in a discussion about which smartphone to use. It's almost like recommending that a Slashdot user give up telecommunication and join the Amish.

  103. Re:The Case for Google's Control: Atrix by Anonymous Coward · · Score: 0

    Yes, their employees have written about how they believe Android shouldn't be locked down. Sadly, Google hasn't contractually objected to it.

  104. Amazon by DrXym · · Score: 1
    I think it's fairly obvious who Google are trying to stop here. They don't want Amazon producing a Kindle running Android 3.0 with its own app store, videos, books etc and directing people away from the equivalent Google apps. They don't want other manufacturers being poached into some competing services platform run by Amazon. Amazon are clearly working something up since their app store makes no sense in any other context.

    So the nocompete clause is likely to stop that happening. I expect if the parties can find a way to amicably split the business (e.g. apps to Google, vids / music to Amazon, books shared) everything will blow over, but if it doesn't, expect fireworks.

    I was actually thinking of signing up to the Amazon app store as a developer and then I saw they want $99 annually (waived the first year). What the fuck? You don't compete with the defacto store by charging devs more money for the privilege.

    1. Re:Amazon by Funnnny · · Score: 1

      What ? Clearly Amazon have their right to get Google approved, just because the standard is public.

    2. Re:Amazon by DrXym · · Score: 1
      Amazon can do anything they like with Android 2.x because the source is out there. They can roll out a device which is certified as a compatible device and get the Android Marketplace app, or they could just ignore compatibility entirely and ship their own apps. They could do this right now. I suspect if they did release that they wouldn't bother with certification at all. They have their own app store and services for books, videos & music too. Maybe they'd even partner up with Bing to augment their system with apps equivalent to those that Google denied them such as Hotmail, search, maps etc.

      I think Google realises they can't stop this happening with 2.x but they can stop it with 3.x. So they're withholding source and using it as a stick to get some concessions out of Amazon. Clearly Amazon would like to be running the latest and greatest OS because its purpose built for tablets. Clearly Google want their apps and marketplace on the device because that's how they make money. Perhaps some bargain can be struck to mostly satisfy both parties. If not, there is going to be war.

      I think it's clear that this all coming to a head and soon.

  105. Did you hear that? by Anonymous Coward · · Score: 0

    It was the sound of thousands of Google advocates saying Apples walled garden is a terrible terrible thing..... Suddenly wondering if anyone saw them being complete hypocrites.Its open its free information wants to be free ummm except when it doesn't. I think their heads may explode from the paradox, bring a umbrella just in case.

  106. Re:The Case for Google's Control: Atrix by Anonymous Coward · · Score: 0

    Um, you normally don't need kernel or bootloader flash access to replace the system software. Motoblur is easily removable on most Motorola phones by simply gaining root. You can run AOSP on those devices if you want to, as long as the kernel version is compatible (which usually means being forever stuck on Android 2.1 or 2.2).

  107. Re:The Case for Google's Control: Atrix by Anonymous Coward · · Score: 0

    They pulled back the N1 due to hardware issues and realized that they didnt want to get involved in the handset market.

    With the Nexus S, they're every bit as involved in the handset market as they were before.

  108. Re:The Case for Google's Control: Atrix by Anonymous Coward · · Score: 0

    With apple, you're stuck with iTunes... no other choice or option.

    Yeah, that Cydia thing is just a made up store for alternative iPhone apps.

  109. Re:The Case for Google's Control: Atrix by bloodhawk · · Score: 1

    That isn't a problem, that is a strength. If you can't try ideas be they good or bad we go back to the stagnate mess we were in a few years ago.

  110. Good or bad? by cyberfin · · Score: 1

    So Google created something good which others are making bad and now Google wants to prevent the goodness from becoming badness.

    Mmm...good?

    --
    "I'm taking this loop off." - Jack O'Neill
    1. Re:Good or bad? by joshtheitguy · · Score: 1

      Given Samsung's TouchWiz UI or Motorla's Motoblur I am 100% in support of Google making some terms for these companies to quit ruining the Android OS. It seems most of the hold ups on the newer generation hardware is due to these terrible UI modifications (see Samsung Galaxy S line or any Motorola phone that wasn't the Droid, Droid 2 or Droid Global) or their releasing two year outdated hardware as a new phone now.

    2. Re:Good or bad? by rogerdugans · · Score: 1

      Being the owner of a Droid 2 Global (needed global sim capability, wanted Android, Verizon best carrier in my normal area) I can heartily agree with this.
      MotoBLUR made the D2G slower, buggier and harder to use than the Original Droid I have still.

      Fortunately there IS a custom ROM for it (only one that works with the sim though, sadly) and with Fission on it the D2G is a damn good phone.
      But if Verizon/Motorola hadn't screwed up:
      1) the Android operating system in the first place it would have been a good phone in the first place
      2) the bootloader to try and force users into using their crappy software then there would be far more options to choose from as far as ROMs for the phone.

      It has really become a simple thing:
      You don't need to make it impossible to install a custom ROM, just make it so that it can ONLY be done intentionally. Once a user makes the decision require a digital signature of some sort that also absolves the carrier and manufacturer of the responsibility to provide support. Easy.

      While I have never believed that ANY company has MY best interests in mind, I don't believe Google is wrong to hold onto the source code for Honeycomb until it is done.
      Manufacturers who have released devices with an operating system which is not yet done.... yeah, I don't see that as such a good idea.

      The way Android has moved into the smart phone market so far is pretty incredible but it HAS led to deviations from AOSP that continue to increase. If this continues it will eventually lead to Android being junk. I see no valid reason to complain that Google is taking steps to keep Android healthy.

      Last of all- my Nook Color (which is about as un-brickable a device as I have seen!) runs great as a tablet with Gingerbread and some Tablet Tweaks (under development) on it.
      Personally I am not even INTERESTED in Honeycomb.

      --
      Linux computers, watercooled, photography
  111. Re:The Case for Google's Control: Atrix by Anonymous Coward · · Score: 0

    So skins are what makes Android usable or unusable? Is that what you are saying?

    No. No, that isn't what he was saying. Not at all.

    And Google Maps and Navigation appear on the Atrix, and you can even set them ad default and never worry about AT&T navigation ever again. Where's the problem here?

    I can't speak for AT&T devices, but Verizon's bloat likes to run at startup for no reason and not go away if you try to force close it. It really has a negative impact on performance, especially on lower-end devices.

  112. Re:The Case for Google's Control: Atrix by kikito · · Score: 1

    You should see the Samsung Galaxy. It even comes with a propietary (and underperformant) file system. Which in turn lags the rest of the system, and makes some apps simply not work.

  113. Re:The Case for Google's Control: Atrix by dannys42 · · Score: 1

    This is the traditional way cellphone companies have dealt with their phones. This exactly why the "openness" of Android would be it's own down-fall in this market.

    Despite what anyone says, Apple's "walled garden" is one of the greatest innovations in cell phone operating systems in that they actually managed to prevent the carriers from having the control to be stupid.

  114. Re:The Case for Google's Control: Atrix by tepples · · Score: 1

    If you can't try ideas be they good or bad we go back to the stagnate mess we were in a few years ago.

    So where does an end user turn if all carriers are trying a bad idea?

  115. Re:The Case for Google's Control: Atrix by Redbluefire · · Score: 1

    I'm behind Google on the general principle, but did you actually use her Atrix at all, or instantly jump on it an customize it assuming MOTOBLUR was bad? I've had my Atrix for a month now, and the only downside I've had with MOTOBLUR was that it has limited customizability. It runs smooth as butter, and I feel does a great job at tying together the android experience in Motorola's own way.

    God forbid a manufacturer customize anything.

  116. Easy fix for all Android Users by Anonymous Coward · · Score: 0

    Get a iPhone.

  117. Re:The Case for Google's Control: Atrix by Anonymous Coward · · Score: 0

    The problem isn't the modifications. The problem is that people expect a good user experience and drastic modifications to the user experience should require a new differentiating name.

  118. Re:The Case for Google's Control: Atrix by bonch · · Score: 0

    The technologies behind the phone networks themselves are patented, and the spectrum on which they operate is exclusively licensed to four, soon to be three nationwide companies. With no patent license and no spectrum, how does one "fork and implement them"?

    The topic is Android, an open source operating system that can be forked, not the cell phone networks.

    So what should I use instead of a smartphone to accomplish the use cases commonly associated with smartphones?

    A laptop, a tablet, or simply don't do the things you'd accomplish with a smartphone. You're acting as if a smartphone is a necessity like food and water.

    "It looks like you're playing the Hobson's choice card. Would you like help?"

    What you're thinking of is actually a Morton's fork.

    I don't see "don't use a smartphone at all" as germane in a discussion about which smartphone to use. It's almost like recommending that a Slashdot user give up telecommunication and join the Amish.

    The discussion wasn't about which smartphone to use; it was about the existence of bad ideas and how people are free to implement bad ideas in an open system. You said bad ideas were "forced" onto consumers, without explanation. No consumer is forced to purchase a smartphone. A smartphone is a technological luxury.

  119. Re:The Case for Google's Control: Atrix by Anonymous Coward · · Score: 0

    Provided that the people they pass it on to have the same freedom. Unfortunately, most consumer-owned smartphones are locked down.

  120. Re:The Case for Google's Control: Atrix by daid303 · · Score: 1

    Funny, as HTCs enhancement (except for the locking it down) make the phone more usable.

  121. Re:The Case for Google's Control: Atrix by zuperduperman · · Score: 1

    What happens if you just buy and unlocked GSM phone and stick your SIM card from AT&T in it? (genuine question).

    I understand if you insist on sucking on the credit teat of your carrier to get a phone on contract you're stuck with what they let you have and the conditions they put on it. But can't you just buy any international phone and start using it?

  122. Re:The Case for Google's Control: Atrix by jonbryce · · Score: 1

    Depends which market you look at. It certainly isn't mainstream in the desktop market, that is for sure, but in the embedded market, such as TVs, wifi routers, network hard drives and so on, linux has quite a high market share. Also in the server market, apart from the niche sectors occupied by Small Business Server, Exchange and Sharepoint, linux is pretty strong. In the high performance computing market, there is very little else apart from linux.

  123. Re:The Case for Google's Control: Atrix by scot4875 · · Score: 1

    Unfortunately, that openness argument goes right out the window when carriers and/or manufacturers lock down the hardware so that you can't compile really overwrite the firmware without a jailbreak.

    Actually, it doesn't. You can jailbreak an iPhone, sure, but good luck finding alternatives to iOS to run on it. But because modders have access to the Android source, there are a ton of other ROMs you can install on your phone with new and improved features. Admittedly, I haven't played with an iPhone or tried to do any modding, but a search for "iPhone ROMs" pretty much gives you a list of how to play old NES/SNES ROMs on your iPhone. Oh, and it looks like you can run a stripped down Linux install on it. Woo. A search for Android ROMs gives you tons of options for alternative Android versions to play with.

    --Jeremy

    --
    Jesus was a liberal
  124. Re:The Case for Google's Control: Atrix by jonbryce · · Score: 1

    I think this is a problem with the ARM architecture rather than with Android. To update the OS, you need to flash the ROM, and you need to flash the entire ROM in one go, not just replace a few files on the hard drive like you do on intel based machines.

  125. Re:The Case for Google's Control: Atrix by icebike · · Score: 1

    I don't believe this is the case. It might be for iPhones, but not for android.

    Android frequently send out small updates to various phones to fix minor issues.

    --
    Sig Battery depleted. Reverting to safe mode.
  126. Don't anger the geeks by tepples · · Score: 1

    Geeks are the ones who create the applications. Applications are what allow you as a carrier to sell smartphones with a marked-up data plan rather than dumbphones with the cheapest prepaid plan. And early-adopting geeks recommend carriers to their friends and family.

  127. Re:The Case for Google's Control: Atrix by DJRumpy · · Score: 1

    Yes and No. Apple refused to allow AT&T to modify iOS from the get go. No ads, shovelware, or AT&T bloat which the cell providers always thing is a great idea and the consumer can't wash themselves of fast enough. I wish Google had used a heavier hand earlier on in this area.

  128. Re:The Case for Google's Control: Atrix by HateBreeder · · Score: 1

    I think google did the right thing - get the critical mass - then use the leverage.

    see:

    http://www.engadget.com/2011/03/31/google-tightening-control-of-android-insisting-licensees-abide/

    --
    Sigs are for the weak.
  129. Buying an unlocked phone and paying for service by tepples · · Score: 1

    What happens if you just buy and unlocked GSM phone

    Where can I walk in, try, and buy an unlocked GSM phone in my home town in the United States? Or what online store do you recommend that has a good return policy if I find the unlocked GSM phone that I bought to be unusably unergonomic?

    and stick your SIM card from AT&T in it?

    For one thing, I'm stuck on EDGE and its ISDN-like speed if no unlocked phone supports the frequency band that AT&T uses for UMTS. For another, AT&T includes the price of a "free" phone in the price of voice and data service even if I don't take a phone from AT&T. T-Mobile USA used to offer plans designed specifically for those who bring their own phone, but AT&T is buying T-Mobile USA.

    1. Re:Buying an unlocked phone and paying for service by zuperduperman · · Score: 1

      Well, I sort of have to read between the lines in your answer but it sounds like you are confirming that you can just stick a SIM into any unlocked phone. You then piled a whole bunch of conditions onto the circumstances under which you would purchase such a thing (only in your home town, only if you can try it hands on, only with a return policy that meets your criteria of "good" ...). I suspect whatever I suggest you will trump up a reason why it wouldn't be acceptable to you, but just to show how easy it is here's a nice unlocked phone that you can buy today if you want.

      AT&T uses the same standard UMTS bands as many regions in the world (most of europe), you can easily find phones that will give you 3G. You certainly don't have be stuck on EDGE (although you do have to be stuck on AT&T, which people might argue is similar :-) ).

  130. GPLv3 by DrYak · · Score: 1

    Why would Google want to prevent locked phones?

    Note: Locked in terms of software. Not in terms of sim-lock

    This will help user install upgrade, even is the manufacturer and the carrier are too lazy to provide their own upgrade.
    More upgrade = more phones running the latest version = less fragmentation.

    This will also force the manufacturer to publish their customisations - thus making it easier to make upgrade including the customisation.
    So the upgrade won't look ass ugly because they miss some of the customisation. And so the upgrade works, even when the device uses a strange mix of exotic hardware which requires customized drivers.
    More upgrade = more phones running the latest version = less fragmentation.

    Also openness of the customisation help motivated 3rd parties to fix the customisations when they break compatibility with mainstream android.

    --
    "Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
  131. Re:The Case for Google's Control: Atrix by pckl300 · · Score: 1

    Since when is apple a carrier?

    Doesn't good old Steve get a cut of the monthly payments from the carriers? They've at least blurred the line.

    --
    In the beginning, there was null.
  132. Um, NO by Anonymous Coward · · Score: 0

    Google. No. Put it down. Go back to the playground. No. You don't get a say in this.

  133. Re:The Case for Google's Control: Atrix by Anonymous Coward · · Score: 0

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

    Yes that is the point. Google did an admirable job of sucking everyone in and hen changing the rules. There are a lot of developers that can rightfully feel betrayed. I wish the Linux community would stand up and tell Google to quit calling it Linux. It is in no way Linux - even though it uses an earlier model of the kernel. They have cut off all access to the system via a terminal emulator. I bought a Xoom as my first exposure to Android. I paid $599 for it and sold it this morning for $500 to get it out of my house! I'm busy deleting accounts on Google now. I don't need anything they are offering because I am running Linux - the real open source Linux.

  134. Re:The Case for Google's Control: Atrix by Anonymous Coward · · Score: 0

    You should really learn HTML, especially the and/or tags.

  135. Re:The Case for Google's Control: Atrix by Anonymous Coward · · Score: 0

    I assure you, after rooting the device, you have the same system-level filesystem access you would have on a Linux PC box after logging in as root.

    The only things you can't necessarily do are write to the boot, recovery, or kernel partitions.

  136. Re:The Case for Google's Control: Atrix by sjames · · Score: 1

    The problem is the carriers making a hash of it and then preventing their customers from being equally free to make changes (such as putting it back the way it was). That is starting to give the entire platform a bad name.

    This crap probably won't change until the cell carriers are forced to allow any device on their network with a sim card and they're forced to unbundle the "free" phone's cost from the monthly bill for those who bring their own.

    Don't bother telling me T-mobile lets you do that now, AT&T is about to swallow them whole and change all that.

  137. Protecting their brand? by Anonymous Coward · · Score: 0

    They obviously just want to protect their brand, why not just say you can't call it Android if your fork it and be done with it?

  138. Re:The Case for Google's Control: Atrix by Daengbo · · Score: 1

    You're conflating an argument about the openness of a product with one for the openness of a market. The US market is sick and needs to be healed. I don't really know what the solution is, but I suspect that both the mobile phone industry and the ISP industry can be fixed the same way: consider the pipes to be infrastructure handled by the government, and allow free access at wholesale prices to every company that wishes. That would take away the carriers' de facto lock-in by putting out a single platform.

    I'm not an economist, though. My opinion isn't worth shit.

  139. "open"... by smash · · Score: 1

    So why are the fanboys still crapping on about how open android is, when the honeycomb source is not released? Its a scam. But oh no, Google "do no evil".

    At least apple are up front about iOS being a closed-source platform.

    --
    I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
  140. Re:The Case for Google's Control: Atrix by Billly+Gates · · Score: 1

    With AT&T's network they install the AT&T map apps. How they make money is if you click on it it will tell you that your phone can't do maps or GPS. BUt do not worry AT&T can fix that for $10/month to your phone bill for 2 years. Most people click on it not knowing about the Google apps and AT&T makes $240 from it. WOW

  141. Re:The Case for Google's Control: Atrix by Billly+Gates · · Score: 1

    A better example would be Unix.

    Sure Sun made some money for a little while. Meanwhile in the end Microsoft and Linux killed it. Meego might be Linux.

    When greed of mega telecoms and phone makers get in they will kill the whole market for a bigger slice of the pie and end up destroying the pie all together.

  142. Re:The Case for Google's Control: Atrix by dargaud · · Score: 1
    I'll just take ombrage to this:

    takes gorgeous photos

    Do you need apple tinted glasses to see them as gorgeous ?!? Because the iPhone pics I receive from friends and family suck ass worse than a 30 year old 5$ el-cheapo throw away camera. Sure it's better than most other phone cameras but it's like claiming your webcam makes great movies !

    --
    Non-Linux Penguins ?
  143. Re:The Case for Google's Control: Atrix by dafing · · Score: 1
    Hi dargaud,

    Have you seen photos from an iPhone 4? Its widely regarded as having the best "shooter" of all smartphones, the Nokia N8 takes technically more accurate images (ie more detail), with photos from the iPhone being more "vivid", artificially richer greens, reds, more pleasing to the eye.

    Let's first take a look at the higher-res main camera. At his WWDC keynote, Jobs said that getting great looking images wasn't just about upping the camera's megapixels, but had more to do with grabbing more photons. Increase the photon count, let more light in, and your images will look better, the thought goes. So Apple's using a newer backside-illuminated sensor that's more sensitive to light in addition to upping those megapixels -- and we must say, pictures on the iPhone 4 look stunning. Our shots looked good right out of the gate, with few problems when it came to focusing or low light. With the flash on, we managed decent if somewhat blown out results (fairly common with smaller LED flashes) though impressively, the iPhone 4 was usually able to take completely useable and even handsome photos in fairly low light without the flash. It seems like that photon situation is definitely in play, because even shots taken in fairly dark lighting came out looking good. Autofocus worked well in most situations, and we were actually able to get some impressive looking macro shots (see the flowers and Penny below). In general, we'd have no trouble using the iPhone 4's camera as a stand-in for a dedicated camera.

    Engadget Review

    I genuinely prefer using my iPhone to my "prosumer level" Sony digital camera from a few years ago, they both shoot at 5MP, which "isnt great" by todays standards, however, the resolution is more than enough for little old me :-)

    It's always with me, its very, very thin, beautiful, and takes lovely photos, wait, I said GORGEOUS photos ;-)

    Could it do with Optical Zoom? Sure, and my Sony has "Night Vision" mode via IR photography. Big whoop, I'd rather use my iPhone than carry a seperate camera with me, even if the other camera was as slim...and if it could also upload images over 3G or wifi, directly onto Facebook, Flickr, videos to YouTube, have GPS...

    Next up, using your phone as a calender, as a clock, and as a navigation unit :-)

    I would also say the 30 FPS 720 HD video off my iPhone makes for GREAT movies too, although there is off course the "wobbly sensor" action common to such video cameras.

    Heres a compressed video, YouTube does take a lot of the quality out, still looks great.

    http://coexistingwithnonhumananimals.blogspot.com/2011/03/chicken-friend-salad-video.html

    Best wishes :-)

    --
    --- ...or a new slashdot signature. Dear aunt, let's set so double the killer delete select all
  144. Re:The Case for Google's Control: Atrix by cavebison · · Score: 1

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

    Yes but only if the end user has a *choice* of what to use. That's open and democratic. On the other hand, just look how Democracy itself turned out. :)

  145. Services services services by cavebison · · Score: 1

    I think Google is worried about not being able to lock people into their services. Just look at Apple's iOS, it goes hand in hand with the App Store, which is itself proving to be a minor revolution in delivering software. Apple may even (speculation here) licence iOS out to other device makers, simply to gain more share for its services. These days it seems device penetration isn't as important as service penetration. I'd say the device is secondary. The iPhone & iPad are "new and cool", but they're just delivery mechanisms for Apple services.

    So I'd say Google is wanting to expand their services, and having an Android which can be customised to, say, exclude the Google App Store, or any other of their services, wouldn't be good.

    This is a services war, methinks.

  146. 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
  147. I do not understand! by tanveer1979 · · Score: 1

    In India we have rarely got subsidised phones. Its primarily a GSM market. Only CDMA carriers were selling subsidised phones, as well as un subsidised phones.
    So I guess you cannot buy an unlocked GSM phone there. Why? Is this against the law? If not, and still you cannot buy, that means there is not enough demand in the market to buy unsubsidized phones.
    I guess if there is enough demand in the market to buy unsubsidised phones, somebody will sell them.

    Now a LG optimus one costs 300$(max) in India, totally unclocked. Similar mid range android phones cost 250-350$

    I guess in USA, you will get such a phone for 50$ if you sell your soul for a year right? Thats where lies the problem. People will not buy the same phone for 300$

    Few geeks will but it does not make sense to import phones unless there is a large market.
    So its a case of no demand?

    --
    My Aurora : http://www.youtube.com/watch?v=o91ZsGwJYyg
    FB : https://www.facebook.com/TanveersPhotography
  148. Re:The Case for Google's Control: Atrix by Builder · · Score: 1

    Maybe they've blurred the line on who profits, but Apple does not maintain any communications infrastructure. Nor do they own any spectrum. So they're _clearly_ not a carrier.

  149. Re:The Case for Google's Control: Atrix by Builder · · Score: 1

    Get better family and friends. There are some really stunning photos out there taken with an iPhone 4. Just check flickr.

  150. Re:The Case for Google's Control: Atrix by Yvanhoe · · Score: 1

    And the solution is in labellings. Google should control "Android" or "Android phone" as a trademark and only deliver it to the people who accept some compatibility specifications, and sue the people who call their phones "android phones" or their OS "android" without implementing those specs.

    Preferring to close the sources indicates some more malevolent ideas.

    --
    The Wise adapts himself to the world. The Fool adapts the world to himself. Therefore, all progress depends on the Fool.
  151. No SIM-only plans on AT&T by tepples · · Score: 1

    it sounds like you are confirming that you can just stick a SIM into any unlocked phone.

    This is true. The rest of my post explained why it might not be cost-effective to "just stick a SIM into any unlocked phone."

    You then piled a whole bunch of conditions onto the circumstances under which you would purchase such a thing (only in your home town, only if you can try it hands on, only with a return policy that meets your criteria of "good" ...)

    I want to be able to actually use what I buy. Return shipping and the restocking fee can add up to 25% of the selling price of a returned product. What way do you recommend to ensure that I won't buy a phone whose display and input I will end up finding unusably unergonomic? Or should one just suck it up and be prepared to pay two or three restocking fees until finally ending up with a usable phone?

    But thank you for linking to a product sold by FGS Trading, which indeed provides a satisfaction guarantee according to its Amazon seller page.

    although you do have to be stuck on AT&T

    Ordinarily, when a subscriber starts a contract with AT&T, this includes a "free" phone or a discount on a high-end phone. I asked an AT&T sales representative whether I could qualify for a discount for bringing my own phone, and he sounded surprised that a carrier would even offer such a SIM-only plan. So if I were to sign up for service on AT&T, I'd be buying two phones: the phone I will be using and the "free" phone that the carrier gives me no matter what. This $300+ discount on a phone is how the carriers strongly push subscribers into accepting carriers' branded firmware.

    1. Re:No SIM-only plans on AT&T by bingoUV · · Score: 1

      So, back on topic, there definitely are Android open phones. Due to carrier prejudice, this openness is expensive, but that is besides the point. Why then, do you say

      "When all three carriers lock down the phones designed for their respective networks in undesirable ways, I have the Hobson's choice of doing without." ?

      You can "buy" openness if it is worth any money to you. You can buy cheap locked down phones, if that is worth openness to you. Why is it a Hobson's choice? That is like saying you have a Hobson's choice between buying food and staying hungry.

      --
      Bingo Dictionary - Pragmatist, n. A myopic idealist.
    2. Re:No SIM-only plans on AT&T by tepples · · Score: 1

      You can "buy" openness if it is worth any money to you.

      This is true, but it doesn't diminish the fact that the carrier's tying, or not making product A (voice and data service) available except with the purchase of unwanted product B (a locked-down phone), may violate competition laws.

    3. Re:No SIM-only plans on AT&T by bingoUV · · Score: 1

      Yeah, but I guess you have changed the argument. Your original statement was to someone comparing iPhone's openness and Android'd openness. Your statement could only be taken as denying Android's openness. Now you change tack and allege something illegal is going on (which is true in a way, but besides the point here).

      iPhone's openness, whatever it is, is by virtue of one unfair advantage (of Apple over AT&T and other carriers) winning over another unfair advantage (of US carriers over US customers). So the openness itself is not open. It could be a temporary victory of one tyrant over another. Android's openness is inherent in product design and license terms. US law enforcement being screwed up, this openness comes at a cost. But in any sensible market environment, it is clearly superior. Even for the US, you would not deny that a sensible market environment is the right way forward rather than a battle of tyrants providing occasional comfort to customers?

      --
      Bingo Dictionary - Pragmatist, n. A myopic idealist.
  152. Re:The Case for Google's Control: Atrix by tepples · · Score: 1

    And the solution is in labellings.

    That didn't turn out so well for copy-protected discs partially compatible with Compact Disc Digital Audio players. A lot of customers saw the shape of the jewel case and didn't care that the product wasn't a real CD and didn't have the "COMPACT disc DIGITAL AUDIO" logo.

  153. Re:The Case for Google's Control: Atrix by Anonymous Coward · · Score: 0

    Why would Google want to sell phones?

    The point of Android is to sell advertising.

    Carriers see this and think - Why aren't we getting that income? If we are customising the OS for our hardware, how can we make money from this opportunity?
    When carriers can change the OS to increase their income they will.
    So, who "owns" open source code? Who controls it?
    The original developer? The company that deploys it on their hardware? The owner of said hardware?
    It's an interesting test for open source.

  154. Re:The Case for Google's Control: Atrix by Raenex · · Score: 1

    The reality is, "The Free Market" involves crooked deals among The Big Boys, ie Google giving out favours to Manufacturer X

    ...

    I'd rather have a "free market with rules", with a Google who sets limits

    So you want the same company that warps the market with crooked deals setting the limits?

    What I want is a market like the PC market. One where the device is a commodity and you are free to install any software you want on it, and as long as it talks the standard protocol, it works. Fuck the Apple walled garden. Fuck Google-controlled, faux openness.

  155. Re:The Case for Google's Control: Atrix by Anonymous Coward · · Score: 0

    Apple never shared their OS they are as closed as possible can be and a bit more.

  156. Re:The Case for Google's Control: Atrix by ceoyoyo · · Score: 1

    Apple STILL shares their OS. It's called Darwin. They don't share some of the pretty Aqua stuff that runs on top of it, but they share the core OS. Google doesn't share some of the pretty stuff in Android either. They even had a little dispute with Cyanogen about it.

  157. Re:The Case for Google's Control: Atrix by Hognoxious · · Score: 1

    Its widely regarded as having the best "shooter" of all smartphones, the Nokia N8 takes technically more accurate images (ie more detail), with photos from the iPhone being more "vivid", artificially richer greens, reds, more pleasing to the eye.

    I'd take accuracy any day. It's generally easier to manipulate an image that starts out accurate than to fix one that's already got "artistic interpretation" built in.

    Having said that, I own a Nokia E71 and the camera is total plop.

    --
    Confucius say, "Find worm in apple - bad. Find half a worm - worse."
  158. Re:The Case for Google's Control: Atrix by dafing · · Score: 1

    Again, thats a matter of "plugging in the phone by USB, transferring to computer, opening in Photoshop/what have you, dragging the colour levels about...resaving it....

    Its not something that can be done on the phone itself, it might actually be quite possible on an iOS (or Android device) with some of the new photo editing tools, not sure.

    I'm sure most would rather have a camera that takes GREAT photos, be they a little bright, than have technical accuracy, with two bits of gravel more visible in some background shadow on the terrible Nokia's photo, compared to the fantastic iPhone's.

    How many people have the "vivid" mode turned on their television? If they saw the "natural" picture, they'd say "hey, who turned down the colour?!?"

    --
    --- ...or a new slashdot signature. Dear aunt, let's set so double the killer delete select all
  159. Re:The Case for Google's Control: Atrix by dafing · · Score: 1

    "The PC Market"? Like who? CERTAINLY NOT WINDOWS! Talk about "warping the market"... christ!

    So then you're meaning like, some Linux distro? Well, the closest you would have is that Maemo thing Nokia is trying to cook up, you know, the thing that will most likely NEVER come out? And when it does, its stuck on that wooooooonderful, cutting edge Nokia hardware? :-)

    Nokia are moving to Windows Phone 7, ugh! "Moving", no no no, even this "most open of operating systems" company had their price, they were bought off, with "billions of dollars" thrown their way.

    Theres a lot of talk about "extremely open" devices, but who buys them? NOBODY! And the ones that are closest on the market, like the N900, people HERE have them, but the thing got terrible reviews, felt years out of date, and was in no way comparable to a modern iOS or Android device.

    Even gun nuts generally dont mind the government "taking away our rights" to Nuclear bombs. If Google say "the CPU must be at least this, the screen res..." to run their OS, then thats a GOOD thing. If anything, otherwise you end up with another Nokia, this big, POS, caught with their pants down, and utterly unable to compete.

    --
    --- ...or a new slashdot signature. Dear aunt, let's set so double the killer delete select all
  160. Re:The Case for Google's Control: Atrix by Raenex · · Score: 1

    "The PC Market"? Like who? CERTAINLY NOT WINDOWS! Talk about "warping the market"... christ!

    So then you're meaning like, some Linux distro?

    You're confusing the PC hardware with the software that runs on it. I can buy a PC from any vendor, and there are some vendors that ship them barebones without an OS at all. I happen to be typing this comment on a PC with Linux, but the point is it could be anything, from FreeBSD to any operating system that you can dream up.

    Well, the closest you would have is that Maemo thing Nokia is trying to cook up, you know, the thing that will most likely NEVER come out?

    I never trusted Nokia any more than any other company when it comes to openness.

    Theres a lot of talk about "extremely open" devices, but who buys them? NOBODY!

    Yes, that's the way it is. I can tell you what I want, but it doesn't mean it will happen. Still, it doesn't mean it won't. The original PC was a proprietary platform by IBM that was blown wide open by clones. Who knows if some clone or free device will arise?

    If Google say "the CPU must be at least this, the screen res..." to run their OS, then thats a GOOD thing.

    Fuck that. Here I am typing this comment on a widescreen monitor of my choosing, on an operating system of my choosing, on a web browser of my choosing, with installed software of my choosing. I don't need or want any mother-Google dictating the terms.

    It's best to hang on to your ideals instead of embracing the wolf in friendly clothing.

  161. Re:The Case for Google's Control: Atrix by dafing · · Score: 1

    What are the connectors you are using? A standard HDD I see, not something you wire wrapped yourself? :-)

    Again, so Linux On The Desktop was soooo successful, right? Its ALWAYS the year of "Linux in the home" :-)

    What do you *realistically* want in a phone? I mean, we cant expect a bag of parts to be in the box, "assemble however you want!" :-) Nor assembled phones that ask "please insert an SD card with Operating System ISO of your choice :-)" upon the first boot.

    I would think having devices that you can legally hack is the best of both worlds. I had a "jailbroken" Original iPhone, because it wasnt sold in my country. I supported financially those who "free us from the shackles...", and still do, with Geohot.

    It has to be realistic, something that can actually happen. I'm 23, in my lifetime there have been AT LEAST five "open" mobile devices I can remember, openmoko and all that, Android was breathlessly described as "open", until it got too big, and now those same Stallman types are freaking out and bitching about.

    I think hacking your Android or iOS device, and not being sent to Gitmo for it is the best of both worlds. A beautiful, REAL device, running whatever the heck you want to cook up in your basement :-)

    --
    --- ...or a new slashdot signature. Dear aunt, let's set so double the killer delete select all
  162. Re:The Case for Google's Control: Atrix by Raenex · · Score: 1

    What are the connectors you are using? A standard HDD I see, not something you wire wrapped yourself? :-)

    I don't even know what HDD is supposed to stand for. There's no connectors with that label, and HDD could refer to a hard drive or a high-definition display. Either way, I don't really care. Many companies make these commodity components. I don't want or need to wire my own. Of course, I could if I want. The protocols aren't secret.

    Again, so Linux On The Desktop was soooo successful, right?

    I'm happy running Linux. If it hasn't gone mainstream that still doesn't stop me from running tons of software and accessing the Internet.

    What do you *realistically* want in a phone? I mean, we cant expect a bag of parts to be in the box, "assemble however you want!" :-) Nor assembled phones that ask "please insert an SD card with Operating System ISO of your choice :-)" upon the first boot.

    Look again to the PC. It can come pre-installed with software, or I can wipe it out and install my own.

    I would think having devices that you can legally hack is the best of both worlds.

    No, it sucks. I don't want to have "hack" my hardware just to install the software I want on it.

    It has to be realistic, something that can actually happen. [...] I think hacking your Android or iOS device, and not being sent to Gitmo for it is the best of both worlds.

    That's all fine and dandy until the company bans you from their network because you hacked their device, or invalidates your warranty for the same reason. Or until the hacks become harder and harder to pull off.

    I'm not embracing Google and their illusionary open garden.

  163. Re:The Case for Google's Control: Atrix by node+3 · · Score: 1

    More people run Unix on their desktops than run Linux on their desktops. Mac OS X is Unix.

  164. Re:The Case for Google's Control: Atrix by cibyr · · Score: 1

    By that logic, the iPhone is open because you can jailbreak it and then "make all kinds of changes".

    --
    It's not exactly rocket surgery.
  165. Tying makes openness less relevant by tepples · · Score: 1

    Yeah, but I guess you have changed the argument. Your original statement was to someone comparing iPhone's openness and Android'd openness. Your statement could only be taken as denying Android's openness. Now you change tack and allege something illegal is going on (which is true in a way, but besides the point here).

    Then allow me to rephrase: The tying practiced by all three carriers makes Android's openness less relevant, as taking advantage of it is cost prohibitive.

    Even for the US, you would not deny that a sensible market environment is the right way forward

    I agree. So what can I, as an end user, do to make this start happening?