Cyanogen Partners With Microsoft To Replace Google Apps
Unknown Lamer writes: Microsoft and Cyanogen Inc have announced a partnership to bring Microsoft applications to Cyanogen OS. "Under the partnership, Cyanogen will integrate and distribute Microsoft's consumer apps and services across core categories, including productivity, messaging, utilities, and cloud-based services. As part of this collaboration, Microsoft will create native integrations on Cyanogen OS, enabling a powerful new class of experiences." Ars Technica comments, "If Cyanogen really wants to ship a Googleless Android, it will need to provide alternatives to Google's services, and this Microsoft deal is a small start. Microsoft can provide alternatives for Search (Bing), Google Drive (OneDrive and Office), and Gmail (Outlook). The real missing pieces are alternatives to Google Play, Google Maps, and Google Play Services."
Rather than distribute more proprietary services, how about ownCloud for Drive, K-9 Mail for Gmail, OsmAnd for Maps, and F-Droid for an app store? Mozilla and DuckDuckGo provide Free Software search providers for Android, too. With Google neglecting the Android Open Source Project and Cyanogen partnering with Microsoft, the future for Free Software Android as anything but a shell for proprietary software looks bleak.
Rather than distribute more proprietary services, how about ownCloud for Drive, K-9 Mail for Gmail, OsmAnd for Maps, and F-Droid for an app store? Mozilla and DuckDuckGo provide Free Software search providers for Android, too. With Google neglecting the Android Open Source Project and Cyanogen partnering with Microsoft, the future for Free Software Android as anything but a shell for proprietary software looks bleak.
...at least we're out of the frying pan!
How can I believe you when you tell me what I don't want to hear?
seems Microsoft decide to have a real serious fight with Google ! who will win ? Apple
I'm guessing this is just a matter of the cyanogen guys going from "open android" philosophy to "how can we make ourselves money?"
Comment removed based on user account deletion
This.
Cyanogen is dead.
How much money are those services going to offer Cyanogen to be included? I'm pretty sure at least 90% of the reason for this deal is that Cyanogen Inc needs revenue and Microsoft was willing to provide it in order to increase their toe hold in Android devices. Open is nice, but the Cyanogen people need to pay the bills.
Owncloud is not a cloud *service*, but a platform for creating your own (I actually prefer Seafile incidentally).
Ditto for K-9 mail, not a service, but an app.
XML is like violence. If it doesn't solve the problem, use more.
seems Microsoft decide to have a real serious fight with Google ! who will win ? Apple
Not necessarily. Like Google, IBM once created an open platform and Microsoft got into a serious fight with them. Microsoft won. And IBM was a 500lb gorilla in those days like Google is today, a very different IBM than today.
The PC vs Mac platform fight was separate from the fight within the PC platform over the operating system. Similarly the Android vs iOS platform fight may be separate for an operating system fight within Android.
If Microsoft can do something to better integrate Cyanogen based devices into the corporate workflow they might have some leverage. Plus an operating system that gets bug fixes and security updates might warrant some attention.
Hasn't the future of 'open' android always looked bleak, more or less by design? At the bottom of the stack, we have SoC vendors who don't give a damn, handset OEMs who don't give a damn and/or actively prefer that older handsets remain as outdated as possible so you'll buy something new, and carriers who have largely the same incentives as handset vendors; but with their own crapware. This ensures that hardware support is spotty and typically weak for anything except whatever the device shipped with(and it's a moot point on the cryptographically locked devices). Markedly worse than the PC world in terms of vendor helpfullness or ability to do much of anything without a BSP or cobbling blobs together from vendors with slightly longer update support windows.
From the top of the stack, the 'free' parts of android are basically Google's hardware abstraction layer for google play services, and getting steadily more so.
if I wanted Microsoft Apps, I would buy a Microsoft Phone. Very Unfortunate.
I'm guessing this is just a matter of the cyanogen guys going from "open android" philosophy to "how can we make ourselves money?"
Eventually one graduates from college and has to pay bills.
"Open" projects generally need to be subsidized. Either by gov't (including much of academia) or corps. Linux is a prime example, long gone are the days of it being a hobbyist/enthusiast project. It is now primarily a corporate subsidize, corporate sponsored and corporate directed effort. Frankly such corporate involvement is largely responsible for its success.
Perhaps corporations can get cyanogen out of the dorm and mom's basement and get it some serious usage.
Google has its issues but Microsoft is worse. Greedy assholes and I will never use Microsoft Apps.
I am definitely moving away from CM as soon as this bundling gets in place. What would be the best alternative Omnirom? Something else?
But now you're stuck with Microsoft.
Is this supposed to be some kind of improvement?
"Oh noes, google is teh big evil corp'ration, let's go with teh Microsoft". I mean, what the hell are they thinking?
This just sounds like the point at which the free software folks sell out and say fuck it, let's just follow the money.
I have a hard time people are going to buy an Android device, so they can wipe it, kick out Google, and bring in Microsoft. If you want that, buy a Microsoft device and get on with it.
Lost at C:>. Found at C.
Fork Cyanogen.
If people are upset at the arrangement, they will move.
Company-less Android will still be a thing because people want it.
Although in saying that, at this point in time, I'd honestly rather have Microsoft than Google. Google have destroyed pretty much any reason to like them now.
It seems like Microsoft is trying to be what Google was 10 years ago and vice versa. Bing (stupid, stupid name) Maps runs as fast as the old Google maps that everyone loved and with Google sunsetting that one now, it's either that or Mapquest...
From the CM site: To highlight the one take away that matters to CyanogenMod users â" We are not bundling or pre-installing Microsoft (or any Cyanogen OS exclusive partner apps) into CyanogenMod.
It maybe sucks for those who buy a phone with CM pre-installed, but they've already announced that there's no plan to install any MS junk into CyanogenMod, and it's highly unlikely that the community would stand for it if they tried.
So, not something to worry about terribly much. Yet.
Log in or piss off.
Companies like IBM and Red Hat has poured millions into Linux. Red Hat is hardly a passive repackager. You're not "A. Capitalist", you're just "A. Confused and Stupid"
The world's burning. Moped Jesus spotted on I50. Details at 11.
This provides a basis for antitrust investigation and lawsuits over Google's agreements they forced on manufacturers to not sell Android devices without Google's apps. For instance, Samsung makes an android phone with Google's apps so they can't make an android phone with different app store/maps/search apps for China or they would be breaching the illegal restraint-of-trade contract Google forced them to sign.
Even if for no other reason, this is a cheap way for Microsoft to get Google into a regulatory quagmire. But Google brought it on themselves by abusing their position.
I mean, really? A Googleless Android sounds like a fun idea, if a bit ludicrous, but pairing up with Microsoft to do it seems to me to defeat any purpose whatsoever you might have to undertake this endeavor.
Could the Cyanogen Mod group please file a trademark and sue Cyanogen inc for the brand confusion?
I'd really appreciate it. Thanks
http://en.wikipedia.org/wiki/Jury_nullification
for any sort of Exchange email.
Nine works great but costs something like $10 and doesn't do pop or imap.
There was another app (IIRC it has a paper airplane icon) worked okay with exchange as well. The rest, if you setup folders, you don't get alerts if a new email lands in a folder outside of or a sub-folder of INBOX.
IBM once created an open platform
They didn't create an open platform - the platform was "opened" for them by Compaq, and IBM saw a threat. Microsoft, on the other hand, saw an opportunity and happily licensed their code to all comers.
Compaq et al were able to create clones because the IBM PC was an open platform.
"Lowe presented a detailed business plan that proposed that the new computer have an open architecture, use non-proprietary components and software, and be sold through retail stores, all contrary to IBM tradition"
http://en.wikipedia.org/wiki/I...
Microsoft doesn't have a choice but to partner with someone. Sure they hold patents that Android needs (or so they say), but what is someone calls their bluff? The need someone like this because their efforts to enter the mobile market have failed. At the server side they have more competition than ever - which is why .NET at the server gets open sourced. It's do this or fade away.
Fortunately, MS has enough money to spend so that they can do this. Other companies recognized their failures only after they were either bought or went bankrupt.
As much as a dislike Microsoft (software and business ethic), I have to give them credit for being wise.
But now you're stuck with Microsoft. Is this supposed to be some kind of improvement?\
If your device gets no patches under factory android but it does under cyanogen, then yes it is an improvement. A huge improvement.
From the same link:
The success of the IBM computer led other companies to develop IBM Compatibles, which in turn led to branding like diskettes being advertised as "IBM format". An IBM PC clone could be built with off-the-shelf parts, but the BIOS required some reverse-engineering. Companies like Compaq, Phoenix Software Associates, American Megatrends, Award, and others achieved fully functional versions of the BIOS, allowing companies like DELL, Gateway and HP to manufacture PCs that worked like IBM's product. The IBM PC became the industry standard.
Using off-the-shelf parts is not the same as being open.
IBM published the source code to their BIOS. That is pretty open and greatly facilitated the creation of a compatible BIOS.
Rather than distribute more proprietary services, how about ownCloud for Drive, K-9 Mail for Gmail, OsmAnd for Maps, and F-Droid for an app store? Mozilla and DuckDuckGo provide Free Software search providers for Android, too.
It's like whoever wrote this doesn't understand how modern software/device manufacturers think.
Half their business plan involves data mining and vendor lock-in.
Although I need to say that bloggers or wanna-be-reporters are getting it wrong. You know what? Pink ponies are real.
is my friend. It's kind of interesting to watch all of this shake out. Apple and Google hate one another. Microsoft has traditionally been anti-open source. Google hates Microsoft. Apple embraces open source...as long as you play by their rules. Microsoft and Apple have an alliance, albeit an uneasy one. IBM hates Microsoft and now had teamed up with Apple.
So Microsoft figures the best way to get Google is to team up with Apple and Cyanogen. We'll see how effective it is but it seems like a bit of a desperation move on Microsoft's part.
Cyanogen isn't "replacing" Google apps with Microsoft, they are including Microsoft apps in addition to the Google apps. At least for now anyways...
Releasing the source code would actually made it worse for the compatibles - in order to prevent infringement, the clones had to reverse engineer the BIOS in a clean room fashion, so no looking at the source code at all.
There are two parts to the clean room approach. One is the specification phase where one team defines the necessary behavior for a compatible system. This team may look at the copyrighted material. In the IBM PC case the fact that this team was looking at commented source code rather than disassembled binaries was a big advantage, it made their job far easier.
The second phase, which is performed by an entirely different team with no connection to the specification team (other than their output, the specification), is the implementation. Whether the specification they received came from disassembled binaries or source code makes no difference. Well, other than if the spec is source code based it is probably more compatible. So in the IBM PC case we may have had fewer incompatibilities in the spec which made implementation easier too, fewer bug hunts later on.
IBM published the source code to their BIOS. That is pretty open and greatly facilitated the creation of a compatible BIOS.
Heh. No. Compaq reverse-engineered their BIOS. Here's some more reading material.
"Open" does not mean without copyright. The fact is those working on a compatible BIOS had the IBM source code with comments to work from in order to define what a compatible system needed to do. That is a huge advantage compared to disassembling binaries. The fact remains that IBM published the source code to the embedded firmware, that is by definition open. The fact that it is copyrighted and may not be distributed without permission does not change this.
I don't think "clean room" was as you described. I believe one team had access to copyrighted materials including the commented source code. They created a specification that describes the required compatible behavior without any mention of any copyrighted. The "clean" part of the process is the next step. A separate team implements a compatible BIOS working *only* from this specification. The implementation team has no contact with the specification team other than this specification. I think the implementation team was also selected from people who had never programmed the PC before.
The fact that IBM was open with the source code and the specification team had access to commented source rather than disassembled binaries was a great advantage. Keep in mind that this source code listing was official IBM documentation on how to use the BIOS. IBM intended it to be viewed by PC programmers so that they could make use of BIOS API calls.
As an example of IBM being open with their BIOS source code see their PC Hardware reference manual:
http://www.retroarchive.org/do...
Open listings like this were *the* documentation on how to use the BIOS API calls.
I think so. I'm feeling pretty optimistic today.
Microsoft is irrelevant. Almost no one is going to want to run their software. But it'll get people more used to thinking back in desktop terms: "The browser" not "Chrome." "The mailreader" not "Gmail." This could maybe be the wedge that gets Google off our Android phones. And no, not by replacing them with Microsoft. By replacing them with whatever.
Sure, you can already do that, but there's no network effect to help guide you that way. Now the word "choice" will appear in front of your face more often, and that's bad news for Google and Microsoft and good news for users.
...the fact is those working on a compatible BIOS had the IBM source code with comments to work from
... they clean-room reverse engineered it.
A clean room design involves *two* teams. A dirty team that reverse engineers and writes a specification for a compatible device, and a clean team that does the actual implementation using only the provided specification. The "wall" is between these two teams, the implementation team has no contact other than the specification.
The dirty part of the team had a much easier time creating the specification given that they had commented source code. This source code, widely distributed by IBM to PC programmers, was the BIOS API documentation. This is a night and day difference with respect to reverse engineering and the fact that IBM didn't want a compatible BIOS to be produced does not change this.
No need for fork Cyanogen. Free and open Android is already available at the Android Open Source Project.
F-Droid excludes all non-free software. And by default, it hides apps with antifeatures such as advertisements and reliance on non-free add-ons or services. So how are the developers of an app on F-Droid supposed to keep a roof over their heads? And would your suggestion also work for games?
But Cyanogen can't even seem to get bluetooth to work properly on my 3 year-old LG Optimus G. The BT MAC address is always an incorrect value, causing major connection and audio streaming issues. I have been a big fan of CM roms for 5-6 years now, but there are too many bugs they can't seem to rectify these days for me to take them completely seriously. This is especially true if they want to do Android without Google.
Good luck to them, but dancing with the devil (and undisputed king of unresolved bugs) doesn't seem like the way to perfect Android, even if it means taking the lead away from Google. This is disappointing, to say the least.
This is a hacked account, for which the owner can not be held responsible.
Are great.
Except for consumers who would rather deal with more polished and more varied software. Expectations are higher. OsmAnd is a pain to use and butt-ugly. F-Droid is full of simple apps, ugly apps, garbage apps, and a couple of gems. OwnCloud is a gem, though the service and set-up process isn't as easy as "signup with your google/apple/microsoft account and get all your files!". K-9 isn't as pretty or smooth as gmail, and then.. You're still using Gmail. Or outlook. Or another service you have to set up manually somewhere and manage.
Cyanogen would have committed _business_ suicide for choosing those over Microsoft or Google. Now whether they are committing suicide by choosing Microsoft is quite possible too, although it definitely makes a lot more business sense.
and at the end of the day you waste your time commenting on slashdot same as me. Glad you use that financial freedom so wisely.
"Rather than distribute more proprietary services,"... Do not confuse CyanogenMod (CM) with Cyanogen Inc.. The later is a 1B$ valuated company, not an NPO. CM is to Inc. much what AOSP stands for Android: an open-source project backed by a for-profit organization that takes the helm.
Android itself is nothing more than a Google certified AOSP+GApps package. Gapps (market, big data collection, and so on) and OEM support/certification is the way Google monetizes the free AOSP. If Cyanogen Inc. is to succeed as a company, they must have a proven Mobile market exit strategy that should be similar to this. That strategy can be good, bad, or so-so for the stereotypical user:
I predict a third option (the so-so one) is what's cooking, as Microsoft/Cyanogen Inc both need to take a stand for their financial goals, yet Inc surely wants to steer clear from total dependency on a third-party, and keep up their FOSS/XDA-community driven popularity - they are, after all, the ones who freely do all the heavy lifting on CM, and Cyanogen Inc, much like a RedHat or an Oracle, is reaping gains from an open environment needing professional supervision. They would be shooting themselves in the foot otherwise.
I'm not wasting it: judging from the moderation it's clear that OSS people are now even more bent on working for free for people like me. More money in the bank for the likes of us.
Now go back to your OSS project, you are wasting my money.
Sorry I'm an internet millionaire too, with preferred private capital investments. It is you who work for me.