Oppo's CyanogenMod Phone Gets Blessed To Run Google Apps

sfcrazy writes "Google has blessed Oppo N1 by passing it in their compatibility test suite. What it means is that this will be the first phone outside Google's Open Hardware Alliance (OHA) to run Google services and apps legitimately. The phone will be available on December 24th."

Comments

Phew

[recoiledsnake]

Thought it was going to get banned like Aliyun because of the stories below.

http://www.theverge.com/2012/9/14/3335204/google-statement-acer-smartphone-launch-aliyun-android

http://www.theverge.com/2011/05/12/google-android-skyhook-lawsuit-motorola-samsung/

http://arstechnica.com/gadgets/2013/10/googles-iron-grip-on-android-controlling-open-source-by-any-means-necessary/3/

Anyone know if Jolla phones are banned from being made by the Android OEMs because they're using a third party jvm for compatibility?

Re: Phew

[Miamicanes]

Well... in the case of Cyanogenmod, it's more like, "Google kind of turns a blind eye to end users installing them, because it knows that 99.9% of the people downloading them are installing them on phones that shipped with GApps to begin with." It's kind of like how if you ask a Microsoft Licensing Specialist about using an OEM copy of Windows to install a virgin copy of the same version of Windows on a computer that shipped with a crapware-laden copy from the manufacturer, they'll tell you it's officially forbidden... but if you get your hands on an install disc somehow, call Microsoft to phone activate it, and give them the number printed on the COA on the bottom of the computer, they'll activate it anyway.

Google doesn't give a shit if someone with a Samsung phone installs GApps after reflashing it to Cyanogen. They care ENORMOUSLY if a carrier somewhere in the world sells phones from Shenzhen with unlicensed copies of GApps. As long as the barrier to doing it is high enough to require a fair amount of technical skill to install GApps on never-licensed hardware (as opposed to originally-licensed hardware that was just reflashed), they don't really care. And more importantly, they know that if they tried TOO hard to stop people with the skills to reflash from doing it, it would cost them several orders of magnitude more sales and lost goodwill, because we're the ones that two dozen people ask for advice when it's time to buy a new phone.

If you don't believe me, find a friend or family member who owned a Motorola Android phone that got its bootloader permalocked (Photon, Electrify, Atrix2, others) and ask them what they think about Motorola's current phone.... Make sure you're wearing asbestos clothing, because you'll need it...

cyanogenmod scam

[tero]

Too bad cyanogen went from great open source community effort to a cold moneygrab by couple of greedy guys. Wouldn't touch it with a pole now.

https://plus.google.com/+GuillaumeLesniak/posts/L8FJkrcahPs

Re:cyanogenmod scam

[Antonovich]

Solved. If it bothers you so much, don't read it on your 2560x1440 display, read it on a tablet or cellphone. Sheesh, how 'bout some lateral thinkin' there!

Re:cyanogenmod scam

[game kid]

Copied from the linked page, due to the various complaints about viewing area etc. and because even viewing Google+ gives their creepy management strange ideas and is generally a Bad Thing. Of course, this meant that I had to view the page. Links generally not preserved (they were almost all to +Real Names anyway). Slashdot has a nicer viewing area for this sort of thing (but the Beta will probably "fix" that, don't worry).

Guillaume Lesniak
Shared publicly - Sep 20, 2013

I remained silent about the whole Focal relicensing troubles for now. There was a lot of drama between the app being GPL, and the fact Cyanogen Inc wanted to use it, which drove some frustration between me, some CM contributors, and CM leaders. As a result, to avoid any problem, Focal has been removed from CyanogenMod. I think you deserve explanations and “behind the scenes” view on how all of this happened, and to know it’s not just a last-minute decision or ragequit.

This is the true, fully-featured story of the “Focal drama”. It's not a rant about how Cyanogen Inc is bad or anything (and it can be a good thing, with a few conditions, see at the end of the post), but just an insight on how this all happened, and how some people were and are feeling.

A few months ago, I decided to work on an app to replace AOSP’s Camera app after +Steve Kondik expressed concerns about the camera experience on CyanogenMod in a G+ post. I decided to take the challenge, and build up a camera app that would be up with users’ expectations: accessible and innovative UI, but fully-featured.
You all know how that worked out - the app has been out for some time now. I’ve been keeping the “internal” CM team (read: the CyanogenMod Dev private G+ group) tuned with my progress, releasing them mockups, screenshots and videos of the progress. Luckily, nobody ever leaked what it was, even with the big storm we started with the Nemesis trailer.

A few days before we started organizing Focal’s launch, I was approached by +Koushik Dutta and +Steve Kondik . They wanted to talk to me about CyanogenMod’s future developments, that sounded cool. Koush told me in a video chat Cyanogen’s plans since he left Samsung: they found investors, and they’re ready to push forward Cyanogen Inc, a company selling services for CyanogenMod. At first, that sounded amazing, getting a few bucks for working on something I’ve been doing for free for some time. That would allow the student I am to get some stuff and get a kickstart for my future life. That would have given me the chance to spend more time on CM, as I wouldn't need to work elsewhere. Now, I didn’t have much information about what were Cyanogen Inc plans to make money, but I expected it to be through some kind of services - koush told me about CMID, which later became CMAccount, or other premium things like a one-click installer, or even a CMPhone. That sounded like a nice addition to CyanogenMod, leaving the community intact, and adding more value to the software distribution.
I had a similar chat with Steve, where he explained me some of the other aspects of Cyanogen Inc, his philosophy about it, etc. Okay, that sounds like a good plan, get me involved and enhance the open distribution I know and love. I have a few emails back and forth between Steve, Koush and me, talking about what I could work on, what I could enhance on Focal, etc. They’re telling me they’re looking into contracts, and I wait.

That’s when the “drama” started.

I got a Hangouts chat from Koush, saying that Focal would need to be relicensed because GPL isn’t ideal -- wait what, not ideal for an Open Source project?

“The issue is that we need to be able to relicense it”
“It’ll be open as GPL, but CM can do what they want with it.”

Yes, Cyanogen Inc. will need to do changes in CyanogenMod’s source code - because here’s another

Re:Root?

[BobSwi]

No, it'll probably be easy to do but it seems that root was not allowed: http://www.androidcentral.com/oppo-n1-cyanogenmod-edition-passes-google-cts-launching-dec-24 Writing on the CM-dev list, community lead Abhisek Devkota (better known as ciwrl) described it as "a major milestone for everyone in this project," adding "aside from root access, we were not forced to make any compromises in terms of features or functionality."

Re:Try unmaximizing your browser window

[gman003]

The purpose of a windowed computing environment is that you can assign any (rectangular) amount of space to a program, in proportion to how much it is being used.

When I wrote that, all I had open was Firefox (two tabs - /. and the G+ post) and Steam (doing some downloads in my other monitor). I gave Firefox 100% of the screen because nothing else needed it.

A website should use as much space as it is given. If I give it only a small area, it should only use that, but if I give it more space, it should actually utilize it instead of making me scroll through several screens of text when all that content could have fit into one.