Slashdot Mirror


With Cyanogen Dead, Google's Control Over Android Is Tighter Than Ever (greenbot.com)

Last week, Cyanogen Inc announced it is shutting down all its services. A day later, CyanogenMod announced that it is going away too. Regardless of how you found Cyanogen's commercial operating system or open source fork CyanogenMod, the demise has bigger implications. From a report on GreenBot: Cyanogen might never have seriously threatened to take control of Android, but the upstart's shutdown still represents a major victory for Google. As Google showed with the launch of the Pixel, the company is taking steps to ensure no one ever gets close to stealing Android's soul ever again. [...] In many ways, Cyanogen encapsulated more of the spirit of Google's mobile OS project than Android itself ever did. As an early offshoot of the mainstream project designed and supported by habitual modders, Cyanogen was in many ways more aligned with the iOS jailbreaking community than Android proper, bringing customization and features far beyond those available in the stock OS. But almost as quickly as Android took off, Google began reining it in. By implementing stricter rules for manufacturers to prevent further fragmentation -- including licensing of its apps and mandatory inclusion of its search bar widget -- Google actively worked to keep deviant versions of Android on the fringes. Nonetheless, CyanogenMod persisted, surviving cease-and-desist orders, takeover rumors and general Google-led consternation. And now it's all over. Google won, not by waging war with Cyanogen but by doubling down on its own vision, forging partnerships with manufacturers, and working to ensure that Google's Android remained the world's Android.

34 of 212 comments (clear)

  1. We are back to square one by Anonymous Coward · · Score: 2, Funny

    Only instead of the carriers telling us what we can do with our phones, it's Google and Apple.

    1. Re:We are back to square one by bondsbw · · Score: 2, Interesting

      I hesitate at the word "chance". A lot of damn hard work went into breaking the IE monopoly.

      New browsers such as Firefox and Chrome had to be built, which is quite difficult given the complexity of any web browser. But then they needed to gain traction, so the web standards problem had to be fixed... and the only player in the game, IE, refused to comply and seemed to even actively push against standards. But then to fix the web required a third-party browser to already exist that adhered to standards to gain marketshare, which came in the form of mobile Safari on the iPhone. But the iPhone wouldn't have been special without reinventing how people interacted with smartphone devices, and mobile Safari would have been useless if data still cost $30 for the first 20MB.

      Entire markets had to be reinvented just to break the IE monopoly. It was a huge undertaking, and might not have happened if IE, smart phones, or cellular providers were any more tolerable than they were at the time.

      --
      All my liberal friends think I'm a conservative, all my conservative friends think I'm a liberal.
    2. Re:We are back to square one by Kjella · · Score: 5, Insightful

      But then to fix the web required a third-party browser to already exist that adhered to standards to gain marketshare, which came in the form of mobile Safari on the iPhone.

      Stop licking Steve Jobs' butt, he did enough without making shit up. Peak IE was around 2004 with 95% market share. In mid-2007 when the first generation iPhone launched it was already down to around 80%, that is non-IE share had quadrupled and the monopoly was cracking all over. The market for $399+ smartphones was nothing compared to the many hundreds of millions of computers in use, the first sign of mobile browsing having any more than a token presence was in 2010 (went from 1.3% to 4.1% that year, according to StatCounter) when IE was down to 60%. The iPhone had absolutely nothing to do with the fall of IE.

      --
      Live today, because you never know what tomorrow brings
    3. Re:We are back to square one by Etcetera · · Score: 4, Interesting

      We survived the IE near-monopoly and ended up with a nearly-standardized web platform instead of the incompatible mess it was before

      Sure, but it took twenty years, and everything is organizing under Google's banner. Even Firefox is practically indistinguishable from Chrome these days, and will be entirely so once they discontinue support for legacy plugins/addons. So instead of having Microsoft dictate terms through outright monopolization of the market, we're allowing Google to dictate terms because...... why? We trust them?

      This is a matter of faith; we've traded monopoly for theology.

      This is exactly it. Only I fear that this time the technical populace somehow thinks this is a Good Thing. Control by information companies is not any better than control by software companies, and in fact is almost certainly far worse for a whole host of Orwellian reasons.

      We fought and fought and fought to remove IE's monopoly, but the biggest work overall was done by Apple. Remember when we wanted to break up Microsoft into an Office/Apps company and an OS company? It's hard to imagine that we shouldn't break Google up into an advertising company, a tech hosting company, a search company, a browser company, a mobile OS company, a cloud computing company, and half a dozen other distinct entities. But this time the Bay Area is fully behind unified, Umbrella Corp, control because "it's easier".

      Read a book, guys. Learn your history.

    4. Re:We are back to square one by PingSpike · · Score: 2

      I was under the impression that Firefox was what broke peak IE. It certainly coincides with your timeline. Its popular to hate on Firefox these days but I recall it being the hot new thing for a good long time. Chrome and iPhone/Safari probably accelerated the trend away from IE but they didn't start the trend since they didn't exist when the trend started.

    5. Re:We are back to square one by Etcetera · · Score: 2

      Yeah, that worked out so well for the phone companies. Oh wait, they've all merged back together again. Breaking up companies because you think they're too powerful are the thoughts of short sighted people.

      There's an argument to be made that physical high-capital network infrastructure creates a natural monopoly, which ultimately ends up regulated.

      But Google warehousing "all the world's information" and vertically integrating every aspect of this into myriad levels of myriad electronic devices is not the same thing. That's what MS was saying back in the '90s (private, in-house Windows API access by the Office and IE teams was a net benefit) and the industry wasn't having it.

    6. Re:We are back to square one by Etcetera · · Score: 2

      In your hypothetical breakup, only the advertising company stands a chance of surviving. Advertising is the only Google (sorry, Alphabet) company that actually makes money, and it subsidizes all of the others. Conversely, all the others slurp up user data to enhance the functionality of the advertising company. So post-breakup, the advertising company would be crippled, starved of the data that makes it valuable, and all the others will die from having zero funding to run them. So congratulations, you just killed Google.

      Well, yes. That's the point. One of the largest reasons for breaking up huge vertical monopolies is that the cost of entry for other participants is too high because the monopoly can subsidize one side of the business with the others. Can anyone else create a viable mapping, searching, or other business competing with them? No, not really. The only competitor they have in any of these is in Smartphone Mobile OS -- which is a duopoly with Apple.

      Google needs to be broken up, for the good of the tech industry and of the country as a whole.

  2. Goolge needs to ban carrier builds and let people by Joe_Dragon · · Score: 5, Insightful

    Goolge needs to ban carrier builds and let people update there os with out needing to wait for the carrier to do it.

  3. Crackpot by Luthair · · Score: 5, Insightful

    Despite the CEO of cyanogen claiming they were taking away Android from Google, they were always irrelevant. They may have had a few wins with minor players consumers had no relevance with consumers and were never going to replace Google services.

  4. Probable FUD by Anonymous Coward · · Score: 5, Informative

    Unless you want to be accused of contributing the the Google-FUD, be sure to make mention of this whenever Cyanogen/CyanogenMod is mentioned:

    https://github.com/LineageOS
    http://lineageos.org/

  5. Re:One Plus? by Desler · · Score: 2

    No, they run OxygenOS.

  6. Lineage OS by gti_guy · · Score: 4, Informative
  7. Re:Goolge needs to ban carrier builds and let peop by ooloorie · · Score: 2

    Goolge needs to ban carrier builds and let people update there os with out needing to wait for the carrier to do it.

    Why do they "need to"? You can buy a Pixel phone if you want an iPhone-like carrier free experience.

  8. LineageOS by lactose99 · · Score: 5, Informative

    So CyanogenMod is only closing-down due to trademark stuffs surrounding Cyanogen. The actual OS is going to live on as LineageOS, still organized by Steve Kondik.

    --
    Fully licensed blockchain psychiatrist
  9. No basis in reality by WaffleMonster · · Score: 2, Interesting

    The name is dead but the software itself isn't going anywhere. Ass kissing is only necessary to distribute Google Play Services (GPS)... a proprietary bundle of Google malware otherwise Android is open source and there isn't shit they can do about how you use it.

    The only real competition Google has ever had with respect to GPS was from Amazon who operates their own app store separate from Google.

    Personally I will never use an Android phone with Google Play Services installed. For me it isn't a choice between a custom mod and Google it is a choice between no GPS or nothing at all.

    1. Re: No basis in reality by BellyJelly · · Score: 3, Insightful

      Check out the F-Droid store. K9mail for email, OsmAnd~ for mapping/navigation, firefox, vlc, Face Slim if you really must use facebook. Not using google play store and the related services does wonders for your battery life. It's perfectly feasible to run a productively useful yet google-free android phone.

    2. Re:No basis in reality by Anonymous Coward · · Score: 3, Informative

      1) OSMand
      2) K9-Mail
      3) Yes, K9-Mail supports IMAP-IDLE
      4) The Youtube web site works in Firefox (in the background too, if you're into that)
      5) F-Droid
      6) Many apps are available with embedded ad libraries replaced by dummies.

    3. Re:No basis in reality by WaffleMonster · · Score: 2

      Without the Play Services, what do you actually use on the phone?

      I don't spend a lot of time with apps.. I use it mostly for communication and tethering the laptop on the go.

      Do you have a decent map application?

      Yes, internal maps for whole country completely offline with automatic rerouting, TTS. 0 data usage. Love it. Also have 3D google earth app.

      What email app?

      I normally don't do email on my phone. I've used k-mail in the past just screwing around and it worked fine. Don't find on screen keyboards and tiny displays acceptable for any purpose other than writing short text message. I would never write an email on my smartphone unless I absolutely had to. There are enough real computers with usable sized screens and keyboards readily available to me.

      Does it have push notifications?

      Don't remember.. I'm not sure if it forwarded notifications from IMAP or just polled periodically.

      I assume you don't use YouTube or any other streaming services either

      Have youtube 2.0 application which predates GPS integration. Quite old but still works fine.

      Do you huntdown and manually install all your apps?

      Yes either using a Google app store downloader or third party app stores. I don't have a lot of apps yet I do have everything I want. Searching for apps on desktop and sideloading is easier in my view than doing the same from a painfully tiny screen. All commercial apps such as mapping application I have were purchased directly from the publisher not via an app store.

      How many work without adsense or other google services?

      All of them. Local only apps I have firewalled via iptables so they can't communicate with the outside world if they tried. To the extent any of them have ever tried to call home or download ads or telemetry they fail silently.

      CyanogenMod was great, but without installing Gapps it seems a bit pointless to me. How many people honestly run a mobile device with no app store?

      I don't care about popularity contests. Everyone has different opinions and requirements. If you need Google apps that's fine. I personally find the concept of pervasive stalking of entire populations by massive advertising agencies offensive/harmful and refuse to participate regardless of any perceived benefit. I will say battery life and data consumption are amazing without GPS.

    4. Re:No basis in reality by sexconker · · Score: 5, Interesting

      Android is open source and there isn't shit they can do about how you use it

      Android is not open source. You have to be a major OEM (Samsung, HTC, etc.) and pay big, big money to get Android source code, as well as agree to bundle in (and pay separately for) other shit like Google's Play store and dozens of Google services and apps. If you want access to the latest and greatest <dessert name> version of Android you need to agree to launch a flagship product with it and advertise that version of Android as being the next coming of Christ Himself, etc.

      AOSP is open source, and it's fucking useless to 99.999% of people. You can't legally get any of the Google apps on it, and going forward that includes all the baked-in but needlessly-separate features Android phones will have. See the Pixel for examples - the Assistant, the Launcher, the customization UI, etc.

      Not only is AOSP bare and useless, it's often simply fucking broken. It gets lip service support from Google and "lol fuck you" support from hardware manufacturers. The only way to get a free and open and usable Android experience is to do so illegally - use AOSP and inject Google's apps and services, maybe grab some firmware or blobs for specific hardware so the damn thing charges properly or the WiFi actually works, hack some more shit to maybe get Android Pay working or get WiFi calling enabled, and illegally download and share the updated APKs whenever there's a security patch (often), then cry because you have to reformat your phone to flash a new ROM with the latest Android security updates every month because even when someone on XDA uploads an OTA differential patch for your phone it never works quite right.

      Android is fucked up in many, many ways and Google is making it worse every day. They're becoming the walled garden of iOS without the garden.

    5. Re:No basis in reality by desdinova+216 · · Score: 2

      what's the point of a navigation app without real time traffic?

    6. Re:No basis in reality by Miamicanes · · Score: 3, Interesting

      Yep. Most people don't realize that NOT EVEN NEXUS DEVICES have official buildscripts available to create a ROM with everything in the official factory ROM (including binary blobs that aren't open source). You can build and install generic AOSP, but generic AOSP is a subset of what's part of an official Nexus 6P ROM. AOSP on a Nexus 6P is no better than it was on the Galaxy S3 (IMHO, the S3 was the Golden Era of AOSP, and the closest we ever got to being able to flash a semi-device-nonspecific ROM the way you'd boot Debian or Ubuntu on a PC... almost everything since the S3 has been a slide downhill compared to what we had).

    7. Re:No basis in reality by almitydave · · Score: 2

      what's the point of a navigation app without real time traffic?

      The point is to navigate you from point A to B. Just like it was for every single GPS navigation device people had before we switched to using smart phones. Real-time traffic is a nice feature, but by no means a necessity.

      --
      my, your, his/her/its, our, your, their
      I'm, you're, he's/she's/it's, we're, you're, they're
  10. But remember, Google is not a monopolist. by alternative_right · · Score: 2

    Over time, every human venture goes to a bad place. Why?

    Because suddenly it has dependents, and those tend toward rent-seeking, and then that influences leadership to try to "keep the herd together" instead of admitting that it must cull the weak.

    So now Google is an abusive monopolist because its leaders look out there, and see all those smiling hopeful faces, and realize they have to keep growing in order to keep everyone happy, even though that means (1) worse things for the consumer and (2) eventual doom.

    They just can't stop themselves... ah well, it takes a tragedy for humans to learn, and even then, it only takes for awhile. If we filtered out the stupidity, we would be working 2-hour days and enjoying life, but why not suffer for the pretense of equality.

    1. Re:But remember, Google is not a monopolist. by leftover · · Score: 2

      Much more specifically: in the USA businesses become evil when they "go public". They become completely ensnared by Wall Street analysts rather than being responsive to customers or even to the actual stockholders. Nothing "public" about it.

      --
      Bent, folded, spindled, and mutilated.
  11. Re:Goolge needs to ban carrier builds and let peop by Solandri · · Score: 4, Insightful

    Then Android wouldn't be open source anymore. Which do you want? An OS which is open and that anyone can fork and modify if they don't like how the original author made it? Or an OS which is closed and proprietary so you have to take it the way the original author made it, no alterations?

    Way I see it, the carrier problem isn't Google's responsibility. It's a market problem - vertical integration causing lack of customer fluidity. The carriers own the towers, the service, and also sell the phones. GSM tackled the problem by requiring SIM cards, basically forcing all phones to be interchangeable between carriers. The U.S. doesn't have that so your phone is frequently tied to your carrier, giving them an unprecedented level of control over your phone.

  12. Re:Another Cyanogen ? by Archangel+Michael · · Score: 2
    --
    Agent K: A *person* is smart. People are dumb, stupid, panicky animals, and you know it.
  13. But will the OEMs still control security patching? by QuietLagoon · · Score: 4, Insightful

    So long as the OEMs continue to control whether or not, and when, security patches are installed, Google can claim all the control they want. But they do not have that control. Android customers are left in the lurch, subject to the whims of the OEMs and to security issues from unpatched vulnerabilities.

  14. Re:Goolge needs to ban carrier builds and let peop by ninthbit · · Score: 2

    The US is muddied with Sprint and Verizon's CDMA crap, but you can have universal US phones. The Nexus 6 is and example I still use. It works on any US carrier. You need a different model for good international support, but that's true for any radio device in the US vs the world. TV's just the same. It's a pain to near impossible to find a good cheap USB ASTC tuner for the US that supports Linux, but there seems to be swarms of DVB ones for the rest of the world. :(

  15. what if some big name players made their own OS by FudRucker · · Score: 4, Interesting

    companies like Samsung & etc.. and other hardware makers of Android phones made their own OS based on Linux. and it was a open source co-op method of development where everybody pitched in to develop the OS & apps so they can have something on their phones that was not controlled by another company

    --
    Politics is Treachery, Religion is Brainwashing
  16. Built to fail by Anonymous Coward · · Score: 2, Interesting

    Cyanogen Inc. had three paths to profit:

    * Two paths with low-hanging fruit, but requiring hard work to yield near certain success -

            Path A - Port CynogenMod to new platforms for pay
            * Lowest risk, uses the skills and the community they already have
            * Profitable from day one
            * Takes a few years to grow to a meaningful size - like CyanogenMod!

            Path B - Sell retail installation kits for "normal" mainstream people
            * Requires hiring the right channel manager, spending money on advertising etc.
            * An initial hit would make a pile of money, but future growth would require continuous innovation

    * One path with high-risk high-return:

            Path C - Sell CynogenMod Phones
            * Requires starting a business using completely different skill-sets from that used to produce CyanogenMod, such as, cell-phone carrier sales, hardware quality assurance, world-class product design, electronics supply channel management, electronics design, manufacturing, etc.
            * Piles of money to hire the right people, but with a return to justify the expense.
            * The Cyanogen advantage would be having the best software, obtained by having the best developers, IF AND ONLY IF, they do not alienate said developers.

    Cynogen went with Path C, without hiring the right people, and also ALIENED THE DEVELOPERS.

    Follow-up attempts, to reinvent itself, involved neither fixing the mistakes for Path C, nor switching to Path A or Path B.

  17. Who Wrote this? by jdkc4d · · Score: 3, Insightful

    I really just want to write "WRONG" as the entire content of this post and just leave it at that. The article seems to have some of the facts, but not all. Yes, Cyanogen the company has decided to shut down. And CyanogenMod, the open source version of the OS released by Cyanogen based on Android also decided to change their name because they don't want to get sued. But facts seem to end there. CM will continue on under another name. If you are running CM on any of your devices, rest assured, aside from a name change, the next build will be more of the same.
    Where I am getting frustrated with this article is the notion that this is a big win for Google. I have to disagree. Google or alphabet or whatever they want to call themselves may have created the android OS, but they release it in an open source format. They do this to get it out there on as many devices as they can. More importantly, they do this to get it into the hands of as many developers as they can. There are a number of things that I actually thought were part of android, that only later when reading stock android was adding certain features did I realize were actually only part of CM. That's really what open source is about, the ability for a wide variety of people to work to better something together. A lot of times things seem to make sense when one person is working on them, but later we come to find out that they don't make sense to others.
    If Google actually wanted to rein in android, they would simply retool with proprietary code, and release the next version of their OS closed source. The only thing they actually seem to be concerned with are phones that are still running old versions of the OS. This makes is hard not for them, but for application developers to support their applications in that ecosystem. We have seen Google take steps in the recent year or two to modularize some of the core components of Android so that those pieces can be updated even if the OS itself has not been.

  18. Re:What's wrong with Android uniformity? by Miamicanes · · Score: 3, Informative

    > I mean Android is just a use of an OS kernel and some standard services, including application security, and some UI conventions.

    And Google's very, very proprietary, non-opensource, and defacto-required (if you don't want your phone to be crippled) Google Play Services, which are required for installing apps from Google Play, using Google Maps, using Google-assisted location services, Google Pay, and plenty of other things. Over the past couple of years, Google has been systematically moving more and more of Android's core functionality into Google Play Services.

  19. Re:What's wrong with Android uniformity? by presidenteloco · · Score: 3, Insightful

    Ok but for the sake of argument, other than the following factors:

    1) Name recognition and reputation
    2) Resources and ability to write good quality software and maintain good databases with quality data (e.g. maps database, wifi IDs database)

    Is there anything stopping open organization SPQR from creating

    SPQR App Services for Android

    and offering equivalents to the Google-branded services?

    If resourceful, SPQR could convince phone makers to pre-load their phones with the SPQR app store and services.

    My devil's advocate question is: Is this just jealousy that Google out-innovated and out-standardized others, and out-"take my free stuff"-offered others, creating a de-facto monopoly?

    Is this just bitterness that the network effect (on adoption) is the network effect, and it's tough to compete with after a while?

    Seriously, if there is a strong will (including possibly distributed financial backing) to have a good quality open alternative to Google services on Android, couldn't that be done in theory? There's nothing license-wise or artificial-technical-barrier preventing it, is there?

    --

    Where are we going and why are we in a handbasket?
  20. Re:And the best part is... by farble1670 · · Score: 2

    Google won't do a damn thing to flex that muscle on something as simple as forcing the carriers to not stymie any updates.

    You profoundly misunderstand the relationship between Google and the carriers.

    Android exists as it does today so as to make the carriers feel safe. Safe that if Google screwed them in some way they'd have all the source to their OS and the expertise to carry on without Google. Google may have the $$$, but carriers own the wires, cables, poles, lines to your homes, cell towers and the agreements that allow them to exist, and the spectrums themselves. Android's entire business model was to be the anti-Apple. Worried about losing control of the devices on your network? We (Google) have a compromise! You own the software, you control the updates, and you decide what bloatware goes on the device. Carriers tell Google what to do, not the other way around. If Google tried to put the screws to the carriers, you'd start seeing Tizen / Baidu / Meemo / etc phones on their networks before you can blink an eye.

    Google's model is one of education not coercion. Nexus (and Pixel) exist to show carriers and OEMs that a model of open software and updates will sell more devices. Think of them as a "best practice" in phones. You can choose to support this, or you can keep buying locked down phones from Verizon. Up to you.