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.

212 comments

  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 Anonymous Coward · · Score: 1

      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.

    3. Re:We are back to square one by SumDog · · Score: 0

      Firefox was built. Chrome was more stolen than built. They uses pieces of Webkit, pieces of Gecko and didn't release an open source version initially.

    4. 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
    5. 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.

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

    7. Re:We are back to square one by Anonymous Coward · · Score: 1

      You mean like Apple stole WebKit from KHTML?

    8. Re:We are back to square one by Anonymous Coward · · Score: 0

      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.

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

    10. Re:We are back to square one by Anonymous Coward · · Score: 0

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

      There's an argument that IS made by interfering liberals who think they can run your life better than you for regulating EVERYTHING.
      --
      roman_mir

    11. Re:We are back to square one by harperska · · Score: 1

      I am not clear on how forking a FOSS project counts as stealing. That goes for the GP comment as well (i.e. if forking a project isn't stealing, then neither is forking a fork).

    12. Re:We are back to square one by harperska · · Score: 1

      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.

    13. Re: We are back to square one by Anonymous Coward · · Score: 1

      Thanks for the congrats. It's exactly what we've been proudly aspiring for in our last tech monopoly. Why am I supposed to feel badly about this one?

    14. Re:We are back to square one by bondsbw · · Score: 0

      I was quite clear about not placing responsibility on any single item, but on a host of transformations across markets. The largest boosts in mobile web browsing most certainly occurred from Android devices. Indeed, Firefox had already won the hearts of power users and even quite a few consumers (though, that support was starting to level off).

      But let's be clear, Apple was a strong catalyst for the kinds of changes that impacted the IE monopoly at just a time when the web (and PCs) were becoming stagnate again. Apple seemingly negotiated tough with AT&T (which was Cingular months before) and so the iPhone required an unlimited data plan, but it was affordable. The iPhone was a (relatively) large screen in a small-phone world, making it more capable of browsing "the full web" (as Steve Jobs said) instead of WAP... so long as that web was compliant with HTML standards and didn't include Flash and other plugins that were pretty much required for any reasonable level of functionality in IE. It's easy to dismiss just how good pinch-to-zoom was, but it made so much difference. Sites were now rendered for the resolution at which they were designed--and that made the web useful in mobile.

      Primarily Apple set a trend, but I agree that the iPhone never truly commanded the market. I'm not an Apple fanboy, and I'm not even saying they invented anything specific. But ignoring the spark they brought to these industries is revisionist history.

      --
      All my liberal friends think I'm a conservative, all my conservative friends think I'm a liberal.
    15. 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.

    16. Re:We are back to square one by dryeo · · Score: 1

      The difference was that MS was actively working to make sure that no other OS or Browser could succeed, intentionally breaking stuff, "DOS ain't done until Lotus won't run", using contract law (Gate's family were lawyers and he got their monopoly through lawyering rather then having the best product) to stop manufacturers from carrying any other OS, using undocumented API to make sure their offerings worked way better then the competition and forcing IE down the throats of users as well as breaking standards left, right and centre.
      While Google has grown too big and since going public, are much more evil then they were, they're still easy to avoid. No paying Google every time you upgrade your hardware like I found myself doing with MS. Fairly easy to switch. My phone is easy to get the boot loader unlocked by going to the manufacturers website, clicking a bunch of warnings and getting the unlock code. I remember installing Win95 on a computer with OS/2 on it. Happily installed with no activation code and at the end informed you that all the stuff on your OS/2 partition was now gone along with your work, rather then saying to go to fdisk and make Bootmanager the active partition.
      It was due to MS putting so much effort into leveraging their desktop monopoly to monopolize the web that they deserved to be broken up. When Google starts the same shit, then they should be broken up. Right now I use them for some stuff because they have a better product, just like why I started using them in the beginning. I've tried Bing for search and it's crap for what I was searching.

      --
      https://en.wikipedia.org/wiki/Inverted_totalitarianism
    17. Re:We are back to square one by unixisc · · Score: 1

      Which is a good thing. When I had a Lumia Icon w/ Verizon, I just couldn't get updates to it b'cos Verizon (at the time) hadn't tested it completely. I much prefer it where it's in the control of the OS maker: like whenever Apple is ready w/ an update, I just have to install it, and not bother Verizon, whose personnel usually don't have a clue.

      Google controlling the Android updates is a good thing, and so is Microsoft getting hold of updates in Windows 10 Mobile. I'd rather not leave that w/ the carriers.

    18. Re:We are back to square one by Anonymous Coward · · Score: 0

      Nobody is saying anybody stole the code, but corporations are more than happy to steal credit from the open source community and each other. That's why we have these re-branding exercises, excuse me, I mean forks.

    19. Re:We are back to square one by AvitarX · · Score: 1

      I find Chrome way better than Safari.

      Webkit worked a lot better than KHTML for web browsing.

      True, neither built there's from the ground up, but they certainly added a lot.

      --
      Wow, sent an e-mail as suggested when clicking on "use classic" banner, and got a fast response that addressed my msg
    20. Re:We are back to square one by Anonymous Coward · · Score: 0

      The barrier to entry is high but not insurmountable. Open Street Map is just one example of viable alternatives.

    21. Re:We are back to square one by tentenone · · Score: 1

      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.

      So are you proposing a consumer pay-per search model, or a monthly subscription? Or is the search company supposed to be taking money from the sites who'll pay for higher rankings? Mapping probably only makes sense as a consumer subscription service.

    22. Re:We are back to square one by Etcetera · · Score: 1

      So are you proposing a consumer pay-per search model, or a monthly subscription? Or is the search company supposed to be taking money from the sites who'll pay for higher rankings? Mapping probably only makes sense as a consumer subscription service.

      Mapping companies could make money from advertising (cf. Mapquest) or subscription fees (other GPS navigation services). What they can't do is compete against Google Maps and Google Maps' backend, both of which are completely subsidized by Google's vertical monopoly but don't display ads on their own and couldn't survive *solely* through the apps they do display from AdWords independently. Using the market-dominant position in one industry (ads) to subsidize their position in another industry (online mapping), keeping prices (subscription and/or annoyance) artificially too low to make it worthwhile for anyone else to try to compete... is classic monopoly behavior.

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

    How many more instances of Google fucking you freetards over does it take before you stop sucking their dick?

    1. Re:Freetards by Anonymous Coward · · Score: 1

      Yeah! Let's all switch to Windows Phone!

    2. Re:Freetards by Anonymous Coward · · Score: 0

      At least Windows Phone people get updates on time.

    3. Re:Freetards by Anonymous Coward · · Score: 0

      > At least Windows Phone people get updates on time.

      How many Windows Mobile 6.5 users got updates ?
      How many Windows Phone 7 users got updates beyond 7.8 (that added a few more colours and a couple of icon sizes to 7.5) ?

    4. Re:Freetards by unixisc · · Score: 1

      To be fair, those were completely different OSs than Windows 8. Those OSs were based on Windows CE, while 8 and beyond was based on NT

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

  5. One Plus? by Anonymous Coward · · Score: 0

    What does this mean for the One Plus line of phones? They were running Cyanogen right?

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

      No, they run OxygenOS.

    2. Re:One Plus? by Archangel+Michael · · Score: 1

      They run both on OnePlus One.

      --
      Agent K: A *person* is smart. People are dumb, stupid, panicky animals, and you know it.
    3. Re:One Plus? by Qzukk · · Score: 1

      Which is really just stock android with a few nice tweaks that don't include permanently installed nascar, facebook and blockbuster apps or a long, obnoxiously loud boot video, all of which came on my previous Sprint phone.

      --
      If I have been able to see further than others, it is because I bought a pair of binoculars.
  6. And the best part is... by MikeRT · · Score: 1

    Google won't do a damn thing to flex that muscle on something as simple as forcing the carriers to not stymie any updates. I have an unlocked LG G5 and all of the carrier versions are getting updates rolled out. I contacted LG and asked the WTF is going on that my unlocked RS988 is not getting the update. Their response to when it'll be allowed? \_()_/

    1. Re:And the best part is... by Anonymous Coward · · Score: 0

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

      What muscle? Carriers hold the upper hand on Google. Google needs them far more than the other way around.

    2. Re:And the best part is... by Anonymous Coward · · Score: 1

      Similar situation with a LG G4 here. Ran hot as hell, glass was burning hot to the touch, it was unusable, and there were no carrier updates. Putting cyangenmod on it fixed the cooling issue and made the phone so much better I use it as my regular phone now. Damn shame they're gone.

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

    4. Re:And the best part is... by Anonymous Coward · · Score: 0

      And same issue with Nexus 4 (similar hardware as LG G4 IIRC). Google never fixed it and updates only introduced more bugs (Wi-Fi related bugs).
      The problem if these phones is poor thermal design. Only way to "fix" it is to modify kernel CPU thermal parameters.

    5. Re:And the best part is... by Anonymous Coward · · Score: 0

      See, the problem with this post, and the thinking behind it, is that it ignores the customers and their concerns. You've laid out a business model that Google adopted, what, 20 years ago? And now you just keep repeating how a business decision made 20 years ago must dictate the future. The past must be exactly like the future! Smart people with self-interest dictated that it must be so!

      What exactly does this do to solve the problems of today? Android has a very well-known problem with phones not getting security and version updates. Carrier specific versioning, and a broken support and revenue model are the reasons. And yet you, and Google, just keep blathering on about the business model and the Apple thing and the Windows Mobile thing. Are you deaf? Are you blind? Do you have eyes to see?

      Grow up! Most phone buyers do not buy smartphones to make a political statement. They do not make a structured decision based upon the principles of Open Source. They are not rooting for Google as a business titan in battle with Apple or Microsoft. And when something is wrong with their phone, they want help to fix it. So what do most phone buyers look at?

      1). Cash cost of the handset;
      2). Monthly cost of the contract;
      3). The amount of data included in that contract;
      4). The extent of cellular coverage that their carrier can provide;
      5). Features. Games. Bling. The shiny.

      All that other crap, that you keep using to justify a completely broken update model, is actually Google's internal business affairs. And if those business model choices interfere with customers and their needs, then the business model needs an update.

      You made me snort my drink out my nose with the comment that, "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." So what! Let them try!

      First of all, what market share do all those quoted smartphone OSes have? Tizen + Baidu + Maemo combined, have a market share of maybe 5%, and that's being generous. The history of smartphones has not been kind to any of the smaller players. Google has market power, and they are sitting pretty. The thought of Google running scared from the likes of Tizen is so unlikely you could make a comedy routine about it.

      Second, what if someone like a Tizen / Baidu / Maemo, actually made substantial market share gains? Because of superior features, marketing, or whatever? That benefits the customers. Google may not like it, but then maybe Google needs a kick in the pants to become more responsive to customer needs.

      Stop yakking about business model choices. The customers don't care. That's Google's business, not the customers.

    6. Re:And the best part is... by farble1670 · · Score: 1

      See, the problem with this post, and the thinking behind it, is that it ignores the customers and their concerns.

      Sigh. I'm only stating the way it is, not the way it should be. My name isn't Mr. Google, I don't work for Google, and believe it or not they don't turn to me for business strategy.

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

    1. Re:Probable FUD by Anonymous Coward · · Score: 0

      Thanks to whoever upvoted this (I might be OP), I was surprised to see this actually become visible. Salutations to my fellow 0/-1 browsers ;3 /

  8. Lineage OS by gti_guy · · Score: 4, Informative
    1. Re: Lineage OS by Anonymous Coward · · Score: 0

      Yep. Give em some time to get the infrastructure back up (and help and donations). Looking forward to new great releases! Keep up the good work!

    2. Re:Lineage OS by sobachatina · · Score: 1

      Thank you!

      You just saved my 1st gen Nexus 7 from a landfill!

    3. Re:Lineage OS by unixisc · · Score: 1

      So we will have Android distros from now on? Cool. Just hope there is a good way to upgrade my 2 Android toys to the Marshmallow version

    4. Re:Lineage OS by Anonymous Coward · · Score: 0

      You just saved my 1st gen Nexus 7 from a landfill!

      No offense but that device is utter garbage. I was so happy when I traded it in for BestBuy giftcard (recycling program).

    5. Re:Lineage OS by drinkypoo · · Score: 1

      So we will have Android distros from now on?

      We long have had. See XDA-developers. Some minor distributions support multiple devices. Then there's AOSP-based distributions which are much of a sameness, though with different launchers and baked-in apps. There used to be AOKP and SOKP, the Android Open Kang Project (and Sonic...) but they both seem to have gone away. Now there are many lesser AOSP derivatives. And then, of course, CyanogenMod, which is now going to be Lineage.

      I miss SOKP, it's what I was running on my Moto G 2016 (Titan) but then basketbuild asplode and then there was no more SOKP. So now I have the last nightly of CM14 on, and it's working well.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    6. Re:Lineage OS by samwichse · · Score: 1

      https://review.lineageos.org/#...

      That is heartening.

      Work indeed continues.

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

  10. Another Cyanogen ? by Pieroxy · · Score: 1

    I thought Cyanogen was open source? If there is so much traction, another player will pick up where Cyanogen left off and the whole thing will continue.

    1. Re:Another Cyanogen ? by Anonymous Coward · · Score: 0

      Until a new phone is introduced, or a new chip with a closed source graphics driver (see: Raspberry Pi), or the carriers decide to stop supporting your 4G phone.

    2. Re:Another Cyanogen ? by Archangel+Michael · · Score: 2
      --
      Agent K: A *person* is smart. People are dumb, stupid, panicky animals, and you know it.
    3. Re:Another Cyanogen ? by Anonymous Coward · · Score: 0

      The only open-source part is Linux Kernel and AOSP (Android base).
      Everything else is closed source (GPU drivers, Baseband, Google's shit apps, etc.)

    4. Re:Another Cyanogen ? by Anonymous Coward · · Score: 0

      The only open-source part? You do know that the kernel + AOSP is the entire OS, right?

      There are open source drivers for Mali, Adreno and Tegra GPUs. Baseband comes with phones and doesn't generally need to be reflashed for a new ROM. Google apps are unnecessary.

  11. 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
    1. Re:LineageOS by Anonymous Coward · · Score: 1

      Yup. Someone just created a clickbait headline and summary to pull traffic over to greenbot.
      Ah, if only there was a one strike system for clickbait submissions.

    2. Re:LineageOS by Anonymous Coward · · Score: 0

      Much the same with mysql,where's the fun in only being able to sellout open source contributors once when you can screw them over again and again. I hope that contributors withhold their rights this time around.

    3. Re:LineageOS by Anne+Thwacks · · Score: 1
      The actual OS is going to live on as LineageOS, still organized by Steve Kondik.

      Thats no reason to stop whining about Google selling our souls to the devil.

      --
      Sent from my ASR33 using ASCII
  12. Re:Goolge needs to ban carrier builds and let peop by Anonymous Coward · · Score: 0

    "their", raisin-nuts.

  13. 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 ninthbit · · Score: 1

      Without the Play Services, what do you actually use on the phone? Do you have a decent map application? What email app? Does it have push notifications? I assume you don't use YouTube or any other streaming services either. Is it really a "smart phone" without the apps.

      Do you huntdown and manually install all your apps? How many work without adsense or other google services?

      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?

    2. Re:No basis in reality by jabberw0k · · Score: 1, Flamebait

      How many people honestly run a mobile device with no app store?

      My flip-phone serves all the functions of a telephone (you can talk on it). Honestly, how can anyone who reads Slashdot use one of those locked-down user-hostile spy-computers that the gullible masses have been tricked into calling "smart" "telephones"? "Smart" is just a euphemism for "Treacherous." Stallman was right.

    3. Re:No basis in reality by nnull · · Score: 1

      There are plenty of offline map services on Android and they're pretty decent, especially where I can actually turn off traffic alerts (Have it track me online) or not. What bothers me is that Google pretty much can access my phone whenever they want. Ever try logging into your account? Yeah, what you can do there, they can do more.

      In the meantime, I'm sure we'll have alternatives. The end of Cyanogen is not the end of roms. XDA forums is still there and I'm pretty sure Cyanogen is already forked. Hell, actually, its already been forked with many other projects...

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

    5. Re:No basis in reality by Anonymous Coward · · Score: 0

      You can install apps from the apk files. And there are alternative app stores such as F-Droid (FOSS only) and Aptoide. There are also replacements for the Google Play Services APIs (e.g. for location) but I haven't tried them.

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

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

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

    9. Re:No basis in reality by Anonymous Coward · · Score: 1

      Don't trust flip phones. They can still be owned via the baseband, and location can be triangulated from cell towers. I used to use a tin can and string, but realized the string is vulnerable to MITM attacks, so now I use a pocketful of sand.

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

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

    11. Re:No basis in reality by drinkypoo · · Score: 1

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

      Play Services

      My phone came with Play Services, arguably I'm entitled to run them. Who cares where I got them? Google apparently doesn't care.

      Now, with that said:

      Do you have a decent map application?

      osmand

      What email app? Does it have push notifications?

      The default app works, although it does not have push notifications. Poll more.

      I assume you don't use YouTube or any other streaming services either. Is it really a "smart phone" without the apps.

      There are apps.

      Do you huntdown and manually install all your apps?

      You could do, or you could use getjar or f-droid...

      How many work without adsense or other google services?

      Lots don't. Many do. If you get them from one of the above, they won't.

      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?

      Cheap phone plus CM equals bitchin' feature phone.

      But seriously, installing gapps is not hard.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    12. Re:No basis in reality by lgw · · Score: 1

      Myphone also plays mp3s, audiobooks, and has an ebook reader. It might be useful to call an Uber. I find it sad that to get that minimal functionality, I have to get a smart phone, but it's an imperfect world.

      --
      Socialism: a lie told by totalitarians and believed by fools.
    13. 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).

    14. Re:No basis in reality by Rob+Y. · · Score: 1

      Considering that the Pixel is a new phenomenon, and the latest Nexus devices are still being supported like they always were, "making it worse every day" is overstating things a bit. And the Pixel is what it is due to the success of the midrange Android market, which removed some of the appeal of the Nexus line. Android is fragmented because it's open source. That's got all the good and bad aspects. A lot of innovation in Android came from various OEMs, and were eventually incorporated into the mainstream Android - as well as copied by Apple.

      The main problem with Android fragmentation is orphaned devices. Most Android versions will run most apps - and that's due to Googles 'lockdown' efforts as much as anything. But OEMs are still operating on a planned obsolescence model. OnePlus, Moto, and some others to varying extents (ZTE?) are (or were) trying to support the idea of allowing the ROM community to keep their devices alive longer than they're able (or willing) to do themselves. Hell, I had to turn to CyanogenMod to keep my Nexus 4 going longer that Google would too. Google never had a problem with CyanogenMod existing - and it made its gapps stuff available to load on top of it - if not bundled inside it. I'm sure they weren't happy about the "take Android away from Google" crap that the CM CEO was feeding to the press. But CM will live on as LineageOS - and very little will have changed.

      --
      Posted from my Android phone. Oh, I can change this? There, that's better...
    15. Re:No basis in reality by ninthbit · · Score: 1

      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.

      Great reply, with this and the list from above I may have to give a Google-less experience a try. Though, to be fair, anything using replaced ad libraries is surely a copyright violation in the US so is a bit moot against the original point; Android without Google Play Services isn't really commercially viable.

      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.

    16. 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
    17. Re:No basis in reality by thegarbz · · Score: 1

      Not providing open source support is not the same as a walled garden. You do the definition of walled garden a great disservice. You can make that claim when you are no longer able to side load apps Including another store, or use your phone without a Google account.

    18. Re:No basis in reality by jareth-0205 · · Score: 1

      How many people honestly run a mobile device with no app store?

      My flip-phone serves all the functions of a telephone (you can talk on it). Honestly, how can anyone who reads Slashdot use one of those locked-down user-hostile spy-computers that the gullible masses have been tricked into calling "smart" "telephones"? "Smart" is just a euphemism for "Treacherous." Stallman was right.

      Because people have different tradeoffs - maps / games / video outweigh thouse considerations, for me. And bear in mind that you have also made a tradeoff, you carry a phone that is locatable at all times, has a completely closed-source OS that could be doing all sorts of things you pin on Google Services - you don't know.

    19. Re:No basis in reality by Anonymous Coward · · Score: 0

      Like it or not, AOSP is still the best open source phone OS out there.

    20. Re:No basis in reality by Anonymous Coward · · Score: 0

      so now I use a pocketful of sand.

      Beautiful and surreal.

    21. Re:No basis in reality by brantondaveperson · · Score: 1

      The point is to be able to find your way around.

    22. Re:No basis in reality by farble1670 · · Score: 1

      Is the software on your flip phone open source?
      Oops.

    23. Re:No basis in reality by farble1670 · · Score: 1

      Arguably, I'm entitled to take your car for a joyride. Arguably.

    24. Re:No basis in reality by drinkypoo · · Score: 1

      Arguably, I'm entitled to take your car for a joyride. Arguably.

      On what basis? I have a license to run play services on Android on this phone. It came with the stock OS, which was Android with play services. On the other hand, I've never given you any kind of permission to drive my car, nor would I.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    25. Re:No basis in reality by farble1670 · · Score: 1

      Android is not open source.

      https://source.android.com/sou...
      Maybe what you meant was: the software running on my phone isn't 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.

      False. We were a company of ~10 people when we started building a product on Android (custom hardware), starting with AOSP. We now have 4 soon to be 5 hardware devices running Android. We're not "Google certified" nor do we license or run Google apps.

      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

      What you really meant was: "The only way to get the GOOGLE experience ...". Sort of like saying "The only way to get HBO with my free basic cable is to do so illegally."

      Not only is AOSP bare and useless

      Getting AOSP up on your hardware isn't hard*. It is however more than flashing some pre-built binary. It's a development task, not an end user task. You know Linux is open source as well, but does anyone provide a dist of it that runs on your phone? Who are you mad at about that?

      * Making it stable and performing is hard.

    26. Re:No basis in reality by farble1670 · · Score: 1

      On what basis?

      Pretty sure I can think of something. After all I just need to argue the point.

      I have a license to run play services on Android on this phone.

      Did you sign any agreement with or pay Google any money? You don't have a license for anything, your device's vendor has a license and the license has stipulations. Google licensed their apps to run on top of the stock OS that came on your phone. Google required the vendor to run a rigorous tests before it would allow them to run the Google apps.

    27. Re:No basis in reality by drinkypoo · · Score: 1

      Did you sign any agreement with or pay Google any money?

      Not directly.

      You don't have a license for anything, your device's vendor has a license and the license has stipulations.

      My vendor was granted the right to extend that license to me, and that's what they did.

      Google licensed their apps to run on top of the stock OS that came on your phone.

      And I've replaced that OS with a reasonable facsimile, based on code provided by... Google.

      Google required the vendor to run a rigorous tests before it would allow them to run the Google apps.

      Go on, pull the other one.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    28. Re:No basis in reality by Anonymous Coward · · Score: 0

      I used to use a tin can and string, but realized the string is vulnerable to MITM attacks

      Even when using full end-to-end enterprise level ROT13 encryption?

    29. Re:No basis in reality by farble1670 · · Score: 1

      My vendor was granted the right to extend that license to me, and that's what they did.

      Well that sounds interesting. I'm sure you'll provide that license.

      And I've replaced that OS with a reasonable facsimile, based on code provided by... Google.

      You can't change a contract after it's written and agreed upon. Regardless of how reasonable the modifications seem to you. That's a contract for you. If everyone got to muck around with the terms according to what they think makes sense a contract would be worth nothing.

    30. Re:No basis in reality by Anonymous Coward · · Score: 0

      The apps with the ad libraries replaced by a dummy library, is actually referring to apps in the F-Droid app repository. Apps included in F-Droid are all open-source, so there is no copyright issue with modifying them in such a manner. Maybe an ethical issue as you are potentially depriving the author of revenue, but as they were released under an open source license, the author is effectively allowing you to make that decision yourself.

    31. Re:No basis in reality by Anonymous Coward · · Score: 0

      My phone came with Play Services, arguably I'm entitled to run them. Who cares where I got them? Google apparently doesn't care.

      If Google was bothered with how they are currently being distributed, they would surely take legal action. They did take action in the past when they were included in CyanogenMod, Google wanted them distributed separately, I'm sure there were some more specifics to it, but basically making them a separate download was sufficient for Google.

    32. Re:No basis in reality by epyT-R · · Score: 1

      Finding your destination?

    33. Re:No basis in reality by drinkypoo · · Score: 1

      You can't change a contract after it's written and agreed upon. Regardless of how reasonable the modifications seem to you.

      Point to the part that says I can't update to a newer version of Android.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    34. Re:No basis in reality by farble1670 · · Score: 1

      Point to the part that says I can't update to a newer version of Android.

      I never said that did I? I said that Google requires vendors to pass a suite of tests before they license Google apps on their dist of Android running on their device. Ergo, if the build you are running hasn't passed those tests, it isn't licenses to run Google apps.

      If the dist you are running didn't come with a version of Google apps in the firmware, it isn't licensed to run them. That's not a rule of course, just pointing out the obvious that if someone went through the hassle of passing the tests and the cost of licensing Google apps, they'll surely have included them in the firmware. It's the reason why CM could never bundle Google apps and you always needed to go off and download the APK somewhere else.

      I'm not stating how it should be, only how it is.

    35. Re:No basis in reality by Shane_Optima · · Score: 1

      Bubububu... they told me that permissive licenses are the only way we can have real freedom!

      Meanwhile, consumers everywhere are still feeling the painful loss of freedom after Linksys/Cisco was forced to release their modifications to GPLed source code 14 years ago.

    36. Re:No basis in reality by Shane_Optima · · Score: 1

      It's semi-walled, with obvious kill switches[1] in case any third party project gets too popular. OP might have overstated the current status, but the concerns are valid. Particularly in light of Pixel.


      1. A focus on permissive licenses instead of GPL, plus the OEMs and phone carriers being generally hostile to user modding.

    37. Re:No basis in reality by michael_wojcik · · Score: 1

      Real-time traffic is a nice feature, but by no means a necessity.

      A nice feature for some users. I've never had any need for it.

      Of course, I still use paper maps more often than I use satnav, because they're quick and reliable. I only use navigation apps when I don't have a map with me, or need a more-precise location of my destination.

      I know it's hard for some to believe, but there was a time when we didn't have satnav with real-time traffic information, and somehow many of us survived. I used to commute around Boston - North Shore to Cambridge or Back Bay in the morning, then out to Framingham in the evening, then back to the North Shore at night; then later directly between the North Shore and Framingham morning and night. Yes, I often got stuck in traffic. It was annoying. It wasn't digging coal or subsistence agriculture.

    38. Re:No basis in reality by michael_wojcik · · Score: 1

      The only way to get a free and open and usable Android experience is to do so illegally

      For some values of "usable", perhaps.

      - use AOSP and inject Google's apps and services

      I can live without 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

      Maybe - but this doesn't seem to be a problem with many phone models. And if you obtained the hardware legally in the first place, and saved its firmware and OS before you started messing with it, you'll probably have legal copies of the hardware-specific blobs you need.

      hack some more shit to maybe get Android Pay working or get WiFi calling enabled

      I've never wanted WiFi calling, and the day I use Android Pay you'll be able to ice skate in Tartarus.

      and illegally download and share the updated APKs whenever there's a security patch (often)

      Oh, please. Vast numbers of Android phones never get security updates now. This is hardly an obstacle to a "usable" Android experience, as millions of users can testify. Sensible user hygiene goes a lot further toward securing Android.

      then cry because you have to reformat your phone to flash a new ROM with the latest Android security updates every month

      As above. I have never had an Android phone receive an OTA security update. Never.

      None of the things you mentioned would impede my current use of Android in the slightest. AOSP might not provide the Android "experience" you want, but many people don't need much more than a featurephone plus one or two apps they can find from someplace like F-Droid. No, it may not be easy for non-technical users, or even for techies who don't want the cognitive load and opportunity cost of acquiring Android-hacking expertise. But that doesn't mean it's impossible.

      "Usable" is defined by the user.

      Now, that doesn't mean that your broader point - that Google is doing what they can to control Android, while paying lip service to openness - is wrong. But as long as you exercise some care in your choice of phone model, it's not impossible to live without the non-open parts.

    39. Re:No basis in reality by sexconker · · Score: 1

      the latest Nexus devices are still being supported like they always were,

      They aren't. The day the Pixel was officially unveiled was the day Google officially shat on Nexus owners.

      They don't get the new features, as they are Pixel exclusive (and not because of a hardware limitation.
      They Nexus devices didn't even get the official builds of the latest (7.1) Android version in a timely manner. Usually, Google would post these builds and people could flash them as soon as the new Android version was available on whatever new device just launched. Some people would take those builds and create a fake OTA update for a given ROM that could be loaded up just like a real OTA update (no need to wipe, reroot, etc.). This time around, Google sat on their ass and didn't release the official builds for the 6P and 5X until much later.
      Google is also dragging their damned feet on the security updates too.

      So we have features being locked to Pixel for no reason, Android system (feature) updates being delayed for no reason, and Android security updates being delayed for no reason. Google's message is "Buy a Pixel or get fucked.".

    40. Re:No basis in reality by drinkypoo · · Score: 1

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

      If you were right, nobody would use google maps, because it fails so badly at actually alerting people of traffic problems before they run into them. I hear Waze actually works, but only for routes with a lot of users on them, and only if you have cellphone internet access. I don't have much of it, so it's irrelevant to me.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    41. Re:No basis in reality by sexconker · · Score: 1

      AOSP is NOT Android. If you don't understand the distinction, you don't know what you're talking about.

      ANYONE can take AOSP and mess with it and do whatever they want with it.

      Only people who sign their soul away to Google get the latest Android source. These are major OEMs (HTC, Samsung, LG, etc.) and if you want the latest and greatest, you must agree to launch a flagship device with it, advertise the device as coming with the new hot version of Android, bundle the Google apps in, etc. Last I heard, you can buy into access for 2 versions ahead. If Android is on 7.x, the top bidder can get exclusive access to the nascent Android 9.0 (or whatever they end up calling it if they end up merging it with Chrome OS), giving them time to get it up and running on their device in progress, skin it, create support documentation and training manuals and scripts for customer support dweebs, create promotional materials and distribute them to channel partners and carrier stores, etc.

    42. Re:No basis in reality by farble1670 · · Score: 1

      AOSP is NOT Android. If you don't understand the distinction, you don't know what you're talking about.

      I work for a company that took AOSP and built a custom dist of Android to run on very customized hardware. You could argue that what we are running isn't "Android". In the same way CM isn't "Android" nor is any other 3rd party dist you load onto your device. That distinction is moot however. Developers can still write Android apps using the Android SDK and they run on our devices.

      The fact that it isn't Android(tm) doesn't stop an AOSP-based dist from being extremely useful. It may be useless to you since you don't have the expertise to do anything with it, okay. For people that need an OS to run on their mobile or embedded devices, compared to having to build your own OS from scratch it's gold.

    43. Re:No basis in reality by Rob+Y. · · Score: 1

      That's not really unlike the way the situation has always been for older Nexus models. The new model comes out with the latest stuff, and that stuff rolls out to the older models over the next few months. They still generally get it ahead of practically all other OEM devices.

      --
      Posted from my Android phone. Oh, I can change this? There, that's better...
  14. Re:Goolge needs to ban carrier builds and let peop by known_coward_69 · · Score: 1

    except google won't do it because they are like the old Microsoft. no retail presence and they are content to let others sell and support their product as long as they control it

  15. 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.
  16. Stick a Fork in it... by TheFakeTimCook · · Score: 1

    Android's Done.

    And nothing of value was lost.

    1. Re:Stick a Fork in it... by Archangel+Michael · · Score: 1

      But ... has Netcraft Confirmed it?

      --
      Agent K: A *person* is smart. People are dumb, stupid, panicky animals, and you know it.
    2. Re:Stick a Fork in it... by Anonymous Coward · · Score: 0

      No, Minecraft did

    3. Re:Stick a Fork in it... by Anonymous Coward · · Score: 0

      The news of Android's death has been greatly exaggerated.

  17. Re:Goolge needs to ban carrier builds and let peop by TheFakeTimCook · · Score: 1

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

    I was told that Google couldn't do that, because Android was Open Sores.

  18. Given the reason Cyanogen is dead... by Anonymous Coward · · Score: 1

    Given the reason Cyanogen is dead (their major customers started maintaining their own Android forks), I'm not sure the conclusion in the summary is actually true.

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

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

  21. Re:Goolge needs to ban carrier builds and let peop by Anonymous Coward · · Score: 1

    "there" instead of "their" and "with out" instead of "without" - And you focus on the typo in Google?

  22. Google will kill itself by Anonymous Coward · · Score: 0

    Android security is falling apart and MediaTek actively subverts Google's attempts at security. The FTC investigation is still ongoing.

    Like Microsoft, Google is turning into a self-correcting problem.

    1. Re:Google will kill itself by Anonymous Coward · · Score: 0

      And yet iOS reports more CVE holes yearly than Android and is probably second only to that sieve called Windows.

    2. Re: Google will kill itself by Anonymous Coward · · Score: 0

      Where is swillden when you need him? Maybe he finally realized that working Android security required actual work rather than defending the castle on /.

    3. Re: Google will kill itself by Anonymous Coward · · Score: 0

      Wow, that link is pretty bad. It doesn't even get the dynamics of the parties in the Android ecosystem: between Google, the manufactures, the carriers, and how they operate with respect to each other. The fact that it pegs manufacturers as the culprit pretty much sums up that the author has absolutely 0 knowledge of the actual problem/situation. And you ate that shit up.

      I'll quote Trump on this one: "Sad!"

  23. Re:Goolge needs to ban carrier builds and let peop by gsnedders · · Score: 1

    If you live in Australia, Canada, Germany, United Kingdom, or United States, then yes, you can. If you don't, you can't, at least not easily.

    The number of countries the iPhone 7 was available to pre-order in five times the number of countries the Pixel is available in two months after release.

  24. Re:Goolge needs to ban carrier builds and let peop by MyFirstNameIsPaul · · Score: 1

    Is this correct for AT&T? When I have experimented with non-AT&T phones, AT&T will not allow access to their LTE service, so always end up stuck at HSPA+.

    --

    I once took an excursion to Reddit, and later HN. Unlimited up/down voting sucks when dealing with a hive-mind.

  25. One word by Anonymous Coward · · Score: 0

    FORK! U! Teh G!

  26. Re:Goolge needs to ban carrier builds and let peop by Anonymous Coward · · Score: 0

    I live in Spain. I can't get the Pixel unless I import it.

  27. Re: Goolge needs to ban carrier builds and let peo by Anonymous Coward · · Score: 0

    The US uses gsm, we've just figured out how to make it so that even gsm is carrier specific.

    Sure, you can use an at&t gsm phone on t-mobile, but the data uses a different frequency range, so you can only use the slowest speed data

    And open source so people can fork doesn't help. It doesn't matter if someone can fork the operating system if every phone and tablet comes with a locked bootloader. Do they not pull that crap in Europe?

  28. 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. :(

  29. Re:Goolge needs to ban carrier builds and let peop by Scoth · · Score: 1

    This varies by phone. Non-AT&T phones that support the proper frequencies should work just fine on AT&T with LTE. There can sometimes be some drama getting the APNs set up just right, but it's usually not hard. Also, some features like HD Voice or VoLTE may or may not work depending on the rom and software support - those usually need a stock AT&T or AT&T-derived rom, but it may be possible to install one on an unlocked device and make it work.

  30. Re:Goolge needs to ban carrier builds and let peop by ooloorie · · Score: 1

    I used to be an AT&T customer, and I never had problems with third party phones.

  31. 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
    1. Re:what if some big name players made their own OS by BlackSupra · · Score: 1
    2. Re:what if some big name players made their own OS by thegarbz · · Score: 1

      Why would they do that? High risk, lots of effort, design by committee, no market presence, lack of features that big names provide e.g Google apps which many customers actually care about. There is zero reason for them to do this. They have every reason to bake their own mini and tightly controlled OS and yet they aren't making any serious effort in that either.

      May as well wish for a unicorn.

    3. Re:what if some big name players made their own OS by drinkypoo · · Score: 1

      Moblin begat Meego begat Tizen, and all have been a joke because they've changed their plan over and over again instead of getting shit done. The only one which wasn't pug-ugly was Moblin, and they abandoned that interface almost as quickly as they developed it.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  32. Re:Goolge needs to ban carrier builds and let peop by Anonymous Coward · · Score: 0

    "w/ out" instead of "w/out"
    --
    FTFY - unixisc

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

  34. Re:Goolge needs to ban carrier builds and let peop by Anonymous Coward · · Score: 0

    Google is doing the typos!

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

    1. Re:Who Wrote this? by Anonymous Coward · · Score: 0

      The Enter/Return key is your friend. I want to read your +3 Insightful comet, but my eyes are bleeding.

  36. Re:Goolge needs to ban carrier builds and let peop by MyFirstNameIsPaul · · Score: 1

    Did the phone actually connect and state LTE? HSPA+ and lower work without issue, but LTE I have yet to see work, including a friend who has one of the OnePlus phones.

    --

    I once took an excursion to Reddit, and later HN. Unlimited up/down voting sucks when dealing with a hive-mind.

  37. Re:Goolge needs to ban carrier builds and let peop by Anonymous Coward · · Score: 0

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

    As a long time Android user about to go iPhone, I have to ask wasn't the customizability and user tweak ability the original selling point of Android? I am ready to trad that for compatibility with a larger array of devices.

  38. Android is worthless crap by Anonymous Coward · · Score: 0

    You can throw away your Android phone after six months, because of security issues and lack of upgrades. As long as Google and manufacturers allow this to happen, Android will remain a worthless pile of shit anyway. Yes, people buy it, yes there will probably be lawsuits against manufacturers and Google some time.

    1. Re:Android is worthless crap by epyT-R · · Score: 1

      Every OS today is full of holes. I suggest you plan accordingly when using them.

  39. Why Not Linux? by Anonymous Coward · · Score: 1

    Something like Maemo, Meego, WebOS, Tizen, DebianARM; but real Linux, with a real X11(not surfaceflinger) so the established base of programs will compile. I am using Cyanogen for now on one tablet, and sticking with Maemo on my still unreplaced N900. Cyanogen mostly works as long as you have F-Droid rather than G-Play, and with the sandboxing I can get apks for the services I really need on the tablet. But it is a pain to have to work with a system which uses all the wierd mutation of android, unfortunately Ubuntu touch falls into this mess too using an android kernel and surfaceflinger so it can access the android blob drivers.

  40. 'course, this isn't a "SQUIRREL!" for apple fans by Anonymous Coward · · Score: 0

    I mean, it's not like this is peanuts compared to a walled garden that Apple can use to retaliate against you if you want payment for patents (even if they're BS patents, this doesn't stop Apple demanding them too). Or if you don't agree to buy their patents, probably.

    No, this is a real bad thing, and therefore is EQUALLY bad as Apple's actions, therefore we just have to put up with What Apple Did, because at least Apple don't run a search engine we use...

  41. Microsoft Disease by StormReaver · · Score: 1

    Cyanogen died from a terminal disease it contracted when it got into bed with Microsoft.

  42. Re:Goolge needs to ban carrier builds and let peop by Anonymous Coward · · Score: 0

    just block them from using the trademark.

  43. What's wrong with Android uniformity? by presidenteloco · · Score: 1

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

    Everyone's free to write their own apps for it to make phones do whatever.
    And that's much easier to do (and get wide user adoption) because the apps can target Android standard services.

    If anything, there's too much diversity (not enough lockdown) due to carrier and/or phone maker mods of Android.
    So users can get befuddled when they get something different and thought they were getting Android.
    And developers have to target many different versions to reach a big market.
    That's all because of too MUCH freedom (about when to push OS updates etc), not too little.

    If you want to tinker with an alternative or forked OS, nothing is stopping you.
    And if you do it significantly better than the prevailing standard, and also have the organization and business network to make it grow and stick, then more power to you. The core is all FOSS so embrace and extend and modify to your heart's content. I don't see the problem here.

    The overwhelming number of users want something functional, regularly improved in the same way as their friends' phone, and something which supports the apps they and their friends want to use together. Are you people just cranky? What's the big problem with monolithic Android where the name means something singular and predictable?

    --

    Where are we going and why are we in a handbasket?
    1. 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.

    2. 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?
    3. Re:What's wrong with Android uniformity? by Anonymous Coward · · Score: 1

      Senatus populusque Romanus building an Android ecosystem. Is the Roman Empire back? There's a long list of people who will be pissed off, from animal welfare leagues to labour organizations to LGBT who reject the idea of social domination == sexual domination. Israel is gonna throw an even more epic tantrum but they're always crying wolf anyway.

    4. Re:What's wrong with Android uniformity? by Carcass666 · · Score: 1

      I think the problem people have is that there are various pieces of mobile OS functionality that have been moved out of the open Android Open Source space into the proprietary Google Play space (like location). Google Play services are not free (as in beer or freedom), it's another walled garden with commercial restrictions on usage. It's not just a matter of "replace Google search, maps and other services". The Android kernel itself is a decreasing amount of the software footprint required to build mobile apps.

    5. Re:What's wrong with Android uniformity? by swillden · · Score: 1

      Is there anything stopping open organization SPQR from creating

      SPQR App Services for Android

      and offering equivalents to the Google-branded services?

      s/SPQR/Amazon/g

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    6. Re:What's wrong with Android uniformity? by dffuller · · Score: 1

      %s/SPQR/Amazon/g

      There, FIFY.

    7. Re:What's wrong with Android uniformity? by swillden · · Score: 1

      %s/SPQR/Amazon/g

      There, FIFY.

      Ick, I'd never use vi. My expression was a sed command.

      For vi, yours has a redundant /g on the end.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    8. Re:What's wrong with Android uniformity? by swillden · · Score: 1

      Er, I meant a redundant "g". My fingers inserted the '/' without my permission.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    9. Re:What's wrong with Android uniformity? by Anonymous Coward · · Score: 0

      I heard that Google requires all its licencees to also agree not to develop their own non-Google AOSP OS for their phones.

    10. Re:What's wrong with Android uniformity? by wallsg · · Score: 1

      I thought you were modifying "$_".

    11. Re:What's wrong with Android uniformity? by Anonymous Coward · · Score: 0

      Samsung have been trying to. Do you think they have succeeded?

  44. back to square zero by nazsco · · Score: 1

    now, on top of carrier control, we have google and apple inc.

    just look at the new google phone that used to be sold by them. Pixel, the dumbed down Nexus, is now sold exclusively on Verizon.

    1. Re:back to square zero by farble1670 · · Score: 1

      Pixel, the dumbed down Nexus, is now sold exclusively on Verizon.

      It's sold unlocked for use on any carrier.

    2. Re:back to square zero by Anonymous Coward · · Score: 0

      there is a world outside the US. Heck, even in the US you can get the phone without Verizon

    3. Re: back to square zero by Anonymous Coward · · Score: 0

      For calling Pixel dumbed down, you sure missed the fact that Verizon is just the exclusive third party US carrier partner, but not the exclusive retailer of the phone. You can also get it on the Google store, the Google Fi store, and Best Buy. If you get it unlocked, you can also use it on any carrier's network in the US.

  45. Re:Goolge needs to ban carrier builds and let peop by nazsco · · Score: 1

    dear troll, user customizability is very different from carriers disabling stuff and adding bloat while denying you access to your own phone.

    everyone here probably rooted their phones and used it as the full featured computer it is.

  46. J2ME by LesserWeevil · · Score: 1

    Fragmentation killed J2ME like a cinderblock out of a 4th story window. Splat. Google obviously learned this and quite a few other lessons from Sun on how to create and nurture an ecosystem. The best lessons are those you learn from other's mistakes..

  47. Re:Goolge needs to ban carrier builds and let peop by Anonymous Coward · · Score: 0

    And yet Apple's market share continues to decline. Funny how that works out.

  48. Re:Goolge needs to ban carrier builds and let peop by Anonymous Coward · · Score: 0

    I was told Tim Cook had open sores.

  49. Wintards by Anonymous Coward · · Score: 0

    No it doesn't. Just look at all of the phones they osbourned and didn't update to windows 10 mobile. Besides, their toy OS is a POS anyway.

    1. Re:Wintards by unixisc · · Score: 1

      Actually, in Windows 8 and 8.1, Microsoft usually left that decision to the carriers. For the AT&T and T Mobiles, it wasn't an issue upgrading to the latest OS. In the case of Verizon, it was a pain - I couldn't even upgrade my Lumia from 8.0 to 8.1. In Windows 10 Mobile however, Microsoft has taken over full control of the upgrades, so it's no longer owned by the carriers. Only issue - Verizon still doesn't have the equivalents of a Lumia 550 or 950 or 640 - something they could use. But then again, if Microsoft is now looking at 'Surface Phones' which will emulate x86, there doesn't seem to be a compelling reason to either.

      As for the OS, I don't agree that it's a toy OS. Yeah, if you are into the latest games like Pokemon Go, it's not for you. And it does miss a lot of standard apps, such as Uber Partner or Lyft. But it's a very functional phone to use for work purposes - its best app being OneNote. Also, while Windows 8 may have had problems on the desktop, both Windows Phone 8 and Windows 10 Mobile are pretty good phones. I have a Lumia 550 - an unlocked one cost me $150, which I use as a travel phone outside the US. And recently, w/ WhatsApp introducing video calls into the app, Windows finally has a standard video and VOIP app, which it badly lacked.

      Regarding the updates on time, once a particular phone has managed to be upgraded to Windows 10 Mobile, updates on time will be automatic, since Microsoft maintains the same code base in both the desktop and mobile versions

    2. Re:Wintards by mcswell · · Score: 1

      I came to a Windows phone from an Android phone, and was a skeptic. But in fact I much prefer the Windows phone--easier to use, more reliable.

    3. Re:Wintards by Anonymous Coward · · Score: 0

      Windows Phone is definitely the best out of them. If only people actually developed their applications to run on it as well.

    4. Re:Wintards by Anonymous Coward · · Score: 0

      That's the way it has to be. How long is it going to be before, finally, iPhone and Microsoft Phone are controlled by Apple and Microsoft entirely (and the carriers relegated off to being a mere commody provider of data, like they should be?)

      Microsoft are slowly realising that the expeirence matters - and a user's experience is constrained to be no higher than the carrier, OEM, and original OS. A carrier that constrains the experience to what they like will result in Windows 10 getting a bad reputation -- not the carrier even if the carrier is at fault. They're realising it on laptops (signature edition of W10?) so eventually they'll realise it for phones and carriers will be put in their rightful, minor, place.

  50. Re:Goolge needs to ban carrier builds and let peop by ooloorie · · Score: 1

    Maybe you need a new SIM?

    https://www.reddit.com/r/Googl...

    I've had similar experiences: employees claiming falsely that the phone is blocked on their network when there actually is a simple technical problem (like a new SIM).

  51. google are anticompetive jew N I G G E R S by Anonymous Coward · · Score: 0

    fuck those greedy anticompetitive n i g g e r s at google.

    Filter error: Lameness filter encountered
    Filter error: Lameness filter encountered
    Filter error: Lameness filter encountered
    Filter error: Lameness filter encountered
    Filter error: Lameness filter encountered

    free speech wins again

    captcha- overjoy

    1. Re:google are anticompetive jew N I G G E R S by Anonymous Coward · · Score: 0

      DIE IN A FIRE YOU PIECE OF SHIT

      Would you look at that! No filter!

  52. OpenBSD Phone by 0100010001010011 · · Score: 1

    Time for an OpenBSD Phone?

    My favorite phone is still my Kyocera DuraPlus that I use on Ting. Battery lasts ~2 weeks. It does have Bluetooth and a bare bones browser for when I *need* to see something on the web. It would be nice to plug it into my laptop and use USB or bluetooth as a LTE modem, when I have the opportunity.

    I would absolutely pay for an OpenBSD phone in the same form factor that worked and was as secure as the Kyocera. You could also use the same software/hardware to make a secure IoT device. There are a lot of devices out there running cell modems attached to questionably secure Linux distros.

    1. Re:OpenBSD Phone by unixisc · · Score: 1

      How about something based on Minix, which would minimize the resource consumption, and then use OBSD security services on top of that to arm it?

    2. Re:OpenBSD Phone by Anonymous Coward · · Score: 0

      My favorite phone is still my Kyocera DuraPlus

      Looks totally boss!

  53. More and more, Google is badly managed. by Anonymous Coward · · Score: 0

    At a recent news conference in Hell, Satan, CEO of Hell praised Google for its progress in being Evil. However, Satan said that Google is still not as Evil as Microsoft.

  54. Re:Goolge needs to ban carrier builds and let peop by Anonymous Coward · · Score: 1

    Doesn't the GPL3 have a clause to forbid device lock-in? What if all the parties involved in making Android had chosen that license? It would have been better at least for the users.

  55. Ask Linus by Anonymous Coward · · Score: 0

    And a lot of other people who hate GPL3 because of RMS. And the BSD people too. They seem to feel that gpl3 is wrong because it's not limiting itself to merely copyrighted works, ergo won't sign up. Ergo won't get accepted into the Linux kernel as "GPL3 or later", so can't be in the Android set AND in the kernel at the same time without assessing two different licenses and not letting Google use the GPL2 version code (which the license doesn't allow).

  56. Knowing where to go. by Anonymous Coward · · Score: 0

    And,if you decide to avoid the traffic jam you can see ahead, drive away and, well, navigate via the map to beyond it. How did you think it was done before there were live updates on traffic news?

  57. Re:Goolge needs to ban carrier builds and let peop by Anonymous Coward · · Score: 1

    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?

    I want an OS with a license that mandates hardware openness, like the GPLv3: so that, if the carriers put their crapware on the phones, the end users can take it off.

    It's funny. I keep thinking that Stallman is ridiculous - like when he wrote GPLv3 in 2005 - only to find out, a decade or so later, that he was right on the money.

  58. Re:Goolge needs to ban carrier builds and let peop by swillden · · Score: 1

    you can have universal US phones. The Nexus 6 is and example I still use. It works on any US carrier.

    The same is true of the Nexus 5X, Nexus 6P, Pixel and Pixel XL, FWIW.

    --
    Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
  59. Re: Goolge needs to ban carrier builds and let peo by Anonymous Coward · · Score: 0

    Moto G purchased unlocked direct from Motorola happily using LTE to post this comment.

  60. Re:Goolge needs to ban carrier builds and let peop by Anonymous Coward · · Score: 0

    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.

    AFAIK Motorola sells phones that are near stock android. I'm replacing my worn out nexus 5 with a Motorola z play tomorrow. I'm still half betting I'll regret the 5.5" size as cumbersome, but verizon does have a good deal on them. (Free with contract.) That one can get a wireless charging mod pack, that I'm tempted to get for it. I was tempted to get the pixel, but it didn't have wireless charging, and would have been $10 dollars a month and I believe the sale is gone as well. I had previously looked at the S7 for $10 a month, but again the sale is gone.

    My best guess is that it is worthwhile to add a tempered glass screen protector, but not a bumper case. I'm not sure about the mod pack either. Fitting it in ones pocket is likely already difficult. The screen protector should give the screen some protection, without significantly increasing the phones size. Interestingly enough, some of the other Motorola Z phones I believe have more crack resistant screens.

    Of course, I'd like google to sell a stock android phone for say $200. It doesn't have to be state of the art. I just prefer one that actually gets updated. I know I didn't pay $600+ for my original nexus 5. The Huawai (sp?) honor 5 I bought and returned seemed a decent phone, save for bluetooth appeared unrealiable.

  61. Re:Goolge needs to ban carrier builds and let peop by unixisc · · Score: 1

    Not exactly, troll, I use w/o

  62. Re:Goolge needs to ban carrier builds by unixisc · · Score: 1

    I wouldn't mind carriers owning it if they were prompt about supporting every model w/ the latest version. I am w/ Verizon, and for a while, when I owned a Lumia Icon, I couldn't get it upgraded from 8.0 to 8.1. Both Verizon and Microsoft kept tossing the blame on each other. I know that Google too let the carriers own the version releases: I had an Ellipsis 7, which I could never upgrade to Lollypop or Marshmallow.

    I prefer the new scenario, where starting from Lollypop, Google makes it easier to upgrade to Marshmallow, and has a tighter control on the upgrade process. I actually don't see why that should be in the hands of a carrier, unless they change something about their network that requires them to rig the OSs of all their phones. In fact, not just Google, but even Microsoft in Windows 10 Mobile is now in complete control of the upgrade process, and can therefore enable end users to automatically upgrade just like they would their laptops.

  63. mux standards by unixisc · · Score: 1

    Actually, 2 of the 4 US carriers - AT&T and T Mobile - are GSM, while the other 2 - Verizon and Sprint - are CDMA. While that terminology is 2G and dated, since all 4G and beyond phones are OFDMA, the reason different chipsets are still needed is compatibility w/ older networks in places that have not been upgraded to 4G.

    AT&T and T Mo can be used w/ any unlocked phone that you bring in, so that the OS upgrade responsibilities rest w/ the manufacturer. Verizon and Sprint phones don't, so unless one uses an iPhone, a Pixel or a Windows 10 Mobile phone, one is SOL

  64. Re:Goolge needs to ban carrier builds and let peop by Rakarra · · Score: 1

    everyone here probably rooted their phones and used it as the full featured computer it is.

    Except when you do that, you're stuck on an old OS, because OS updates disable the phone rooting and close the security holes that allowed the root to happen in the first place.

  65. Re:Goolge needs to ban carrier builds and let peop by rtkluttz · · Score: 1

    I'll expand on this and say it should be made illegal to lock the owner out of their own devices. Root should be understood.

    --
    Digital is, by definition, imperfect. Analog is the way to go.
  66. Re:Goolge needs to ban carrier builds and let peop by Anonymous Coward · · Score: 0

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

    Let's wait and see how long that crap will get updates from Google before calling it iPhone-like experience.
    One year from now Google will abandon Pixel and come out with all-new Shnitzel phone.

  67. CyanogenMod is _not_ dead or "going away" by gweihir · · Score: 1

    What is it with the bad story editing? CyanogenMod is renaming itself, but that is it. It is not "going away".

    --
    Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
  68. LinuxFromScratch is more relevant. by Anonymous Coward · · Score: 0

    Android From Scratch is right around the corner.

  69. Fought against iPhone, but I guess they win by Anonymous Coward · · Score: 0

    With CyanogenMod dead, all we are left with is a Jailbroken iPhone and lets be honest. Google's OS sucks. They are handing Apple the win... Stupidity for Google seems to know no bounds...

  70. Re:Goolge needs to ban carrier builds and let peop by Anonymous Coward · · Score: 0

    How about banning *commercial* deviant builds and allowing any free build

  71. Re:But will the OEMs still control security patchi by Anonymous Coward · · Score: 0

    Without a unified kernel for ARM we won't be able to get away from the OEM controlled updates.

  72. so the by Anonymous Coward · · Score: 0

    So the Microsoft money is gone ?

  73. Google, only you would be so bold. by Anonymous Coward · · Score: 0

    The more you tighten your grip, the more operating systems will slip through your fingers.

    ~ OpenSource Leia.

  74. Re:Goolge needs to ban carrier builds and let peop by sad_ · · Score: 1

    A carrier/vendor build ban is too much, but each android phone should be flashable so that you can install at least a basic android as released by Google (and any OSS custom rom projects).

    --
    On a long enough timeline, the survival rate for everyone drops to zero.
  75. Re:Goolge needs to ban carrier builds and let peop by Anonymous Coward · · Score: 0

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

    I can update my Sony Xperia Z5 Compact directly from Sony through a vendor provided PC based tool (Xperia Companion), without having to wait for the carrier.

  76. Re: Goolge needs to ban carrier builds and let peo by Anonymous Coward · · Score: 0

    It's funny. I keep thinking that Stallman is ridiculous - like when he wrote GPLv3 in 2005 - only to find out, a decade or so later, that he was right on the money.

    I remember the criticism 10 years ago too. I've come to think that it may have been a coordinated assault by a party that had a lot to lose.

  77. "tighter than ever" by Anonymous Coward · · Score: 0

    Tighter than before Cyanogen existed?

  78. Re:Google needs to ban carrier builds and let peop by Shirley+Marquez · · Score: 1

    For a phone to work with LTE on AT&T, it has to support the correct bands. An LTE phone bought outside the US or intended for a non-US market is unlikely to work. (Notable exceptions: recent iPhone models and some Samsung and LG flagship phones.) A OnePlus phone that was sold directly to a US customer should be fine. Phones bought from Chinese resale sites like Banggood and AliExpress are pretty much guaranteed NOT to work. Phones from eBay and Amazon Marketplace may or may not work; check the for-sale posts carefully to make sure you're getting a phone that will work in North America. Phones sold directly by Amazon to people with US addresses are fine unless the offer specifically says they are not.

    Band 12 support on T-Mobile has an additional requirement. T-Mobile will not allow a phone to be used on band 12 unless it has VoLTE (voice over LTE) and e911 support. The reason is that T-Mobile has no non-LTE spectrum on the 700MHz and 850MHz bands. A phone without VoLTE support might work for data in some locations where it would be unable to make voice calls, and that would violate the emergency service mandate.

  79. Re:Goolge needs to ban carrier builds and let peop by Shirley+Marquez · · Score: 1

    Typos in the subject line are more visible than typos in the body. Thus the focus on that one.

  80. Re:Goolge needs to ban carrier builds and let peop by Anonymous Coward · · Score: 0

    Except unlike Apple, Google has no leverage over the carriers to enforce that. People switch carriers en masse for an iPhone, but no one does so for an Android phone.

    Um of course they do - they can just sue to pull their OS. though the bigger question is why they would do it - it means absorbing more bandwidth cost, supporting a larger pool of hardware configs (metro, boost, etc have a lot of models specifically sold to the carriers), etc - the thing about google pixel or the nexus lines they were doing and such is that the hardware is a known quantity

  81. It'll Hurt the devices by akicool100 · · Score: 1

    Many times when people were done with their OS installing Cynogen used to give it a new life it's a sad day :(

  82. For the Chinese... by Anonymous Coward · · Score: 0

    Finally Baidu no more.