Welcome to the Slashdot Beta site -- learn more here. Use the link in the footer or click here to return to the Classic version of Slashdot.

Thank you!

Before you choose to head back to the Classic look of the site, we'd appreciate it if you share your thoughts on the Beta; your feedback is what drives our ongoing development.

Beta is different and we value you taking the time to try it out. Please take a look at the changes we've made in Beta and  learn more about it. Thanks for reading, and for making the site better!

cancel ×
This is a preview of your comment

No Comment Title Entered

Anonymous Coward 1 minute ago

No Comment Entered


Phew (3, Interesting)

recoiledsnake (879048) | about 4 months ago | (#45751971)

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 [theverge.com]

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

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

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 (1)

tlhIngan (30335) | about 4 months ago | (#45752299)

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 [theverge.com]

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

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

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

Yes, the terms of the OHA prohibit OEMs that ship Android phones from making "Android compatible" phones.

But Oppo is shipping an Android phone, so it's not an issue. If Oppo were to ship an Aliyun phone or a Jolla phone, they too will get a phone call reminding them of their legal commitment to not make a phone that does not run Android but can run Android apps. (So you can make a phone running your own OS, as long as it does NOT run Android apps).

Yes, it's CyanogenMod, but it's still Android in the end. That's perfectly allowed. In fact, Cyanogen is the only one allowed to distribute Gapps outside of Google.

Though, this makes the Blackberry announcement interesting - since Foxconn makes a lot of Android phones for others - are they going to be harassed for making Blackberry phones since those can run Android apps that are not Android?

Re: Phew (1)

Anonymous Coward | about 4 months ago | (#45752341)

What the hell are you talking about?

CM was explicitly ordered to remove the Gapps. They are not allowed to distribute them.

OHA has nothing to do with the ability to run Android apps. Nothing.

Re: Phew (4, Interesting)

Miamicanes (730264) | about 4 months ago | (#45752501)

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

Re: Phew (1)

Shavano (2541114) | about 4 months ago | (#45759587)

But that's about license-to-distribute. Google denied them the right to distribute Google apps because they're proprietary applications, while the rest of Cyanogenmod is Android Open Source (or possibly a few apps might be CyanogenMod-proprietary).

Google separately provides a way for users to download a zip containing Google Apps, not as a nice thing for CyanogenMod users, but because they want you to run Google apps on your phone so they don't want to put high barriers to getting the official, latest Google apps on there.

Maybe some day Google will see some advantage to only allowing Google Apps to be distributed by manufacturers or only by carriers or something like that, but that day is not yet.

Re:Phew (0)

Anonymous Coward | about 4 months ago | (#45753029)

jolla runs sailfish OS. It uses libhybris to run Android apps, so Google has no say in that. The play store and be installed, so one assumes they made everything "compliant".

Re:Phew (1)

recoiledsnake (879048) | about 4 months ago | (#45753383)

Read the links I posted. Google has no say in what Jolla does, but it potentially stop certifying or revoke access to OHA to any OEM that ships Jolla phones.

Good to See (1)

madwheel (1617723) | about 4 months ago | (#45752009)

I'm glad they're supporting them. I just hope this phone doesn't come with a barrage of preinstalled apps that I don't need or want. If the phone is clean and basically a Nexus-like device with some cool Cyanogen mods, I'm all for it. I want better hardware at lower prices (who doesn't), but I also want a good experience on the phone. We'll see what this does to the future phone market.

OpenBSD + Truecrypt + Rip Anywhere Mp3 player (-1)

Anonymous Coward | about 4 months ago | (#45752037)

OpenBSD + Truecrypt + Rip Anywhere Mp3 player
Give me an mp3 player which has the following features:

1. OpenBSD
2. TrueCrypt - choice of encrypting all of device with 1st run and in settings
3. Rip from any device - an extension to the device (like the front part of ST:TNG ship's dish which separates for example) which allows CDs to be inserted and ripped on the fly without a computer connection, and the ability to plug into any electronic device which has the ability to contain audio files, scan for, and rip any audio files - all with the option to convert them to a format of your choosing

Re:OpenBSD + Truecrypt + Rip Anywhere Mp3 player (-1)

Anonymous Coward | about 4 months ago | (#45752139)

You want them to put a CD-ROM in a phone? Oh a removable... err ever heard of a USB port?
WTF you still playing with mp3s for anyways? Cymbals sound washed out as shit :(
Hahahaha, TrueCyrpt... because your ripped mp3s are valuable!
OpenBSD? Seriously...for mp3s? You know what I think? I think you want a device like this so you can go to Wal-Mart, open items, copy disc, replace item so they can't say you stole anything. Kinda like how I got Counter-Strike when I was a kid. Except I just wrote down a cd-key.

Basically, with all these weird requirements, it sounds like you want to build this thing yourself. Well quit talking about it and have at it.

Root? (1)

ksemlerK (610016) | about 4 months ago | (#45752133)

Does it come pre-rooted?

Re:Root? (5, Informative)

BobSwi (607571) | about 4 months ago | (#45752141)

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 [androidcentral.com] 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:Root? (1)

Pinky's Brain (1158667) | about 4 months ago | (#45752329)

I wonder if the N1 can install unsigned ROMs ... if only signed ROMs can be installed on the N1 (ignoring exploits) then the leaders of Cyanogenmod are pretty much tiviozing the project (at some point a phone would come around with no available exploit).

Re:Root? (1)

PopeRatzo (965947) | about 4 months ago | (#45753755)

I'm trying to find a reference for "tiviozing". Can you explain?

I was following the conversation up to then.

Re:Root? (1)

drinkypoo (153816) | about 4 months ago | (#45754121)

I'm trying to find a reference for "tiviozing". Can you explain?

I was following the conversation up to then.

I plugged 'tivoizing' into wikipedia and the top result was Tivoization [wikipedia.org]. Now you, too, know how to use the internets. HTH, HAND.

cyanogenmod scam (4, Informative)

tero (39203) | about 4 months ago | (#45752135)

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 [google.com]

Re:cyanogenmod scam (0)

gman003 (1693318) | about 4 months ago | (#45752203)

I just have one thing to say - I'll get back to reading that once I finish this rant:

I'm reading this on a maximised window on a 2560x1440 display. Why the flying fuck is all the content packed into a 500px box? Fully 2/3rds the width of my screen is completely and utterly unused. Even on my secondary 1600x900 monitor, it's wasting half the screen on a grey background.

Seriously, it's nearly 2014, we have electric cars and robots on Mars. And yet Google, pretty much the biggest web corp on the planet, with plenty of talented designers and programmers and everything else, decided their social networking site needs to present posts in a way that works on XGA screens? Not even XGA - that post would fit on straight-up VGA resolution from the late 80s.

Re:cyanogenmod scam (0)

wbr1 (2538558) | about 4 months ago | (#45752365)

WTF, are you reading this in Google+?

Re:cyanogenmod scam (1)

foobar bazbot (3352433) | about 4 months ago | (#45756357)

The OP, tero, posted a link to a Google+ post. Then GP gman003 posted a rant about Google+'s screen layout. Then you ask

WTF, are you reading this in Google+?

Well, yeah, he was reading that Google+ post in Google+; where else would one read a Google+ post?

We have a threaded discussion system to make stuff like this clear. Perhaps you should try using it...

Re:cyanogenmod scam (3, Funny)

Antonovich (1354565) | about 4 months ago | (#45752371)

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 (1)

Jmc23 (2353706) | about 4 months ago | (#45752947)

I guess stuff like that still exists today because people are so dumb that they think complaining about something like that on a totally unrelated site is going to have any effect.

Stop being stupid, if you don't like it then complain to the website designer!!

Re:cyanogenmod scam (0)

Anonymous Coward | about 4 months ago | (#45753209)

Are you sure he's not talking about the Slashdot beta [slashdot.org], which I am sometimes redirected to. It's much worse than Google+.

Try unmaximizing your browser window (1)

tepples (727027) | about 4 months ago | (#45754207)

Why the flying fuck is all the content packed into a 500px box?

To minimize line transition errors (skipping or rereading a line), it's best to make body text columns no wider than about 80 characters. In CSS, that's about 30em to 40em, and with the default 16px font, 500px is about 31em.

Fully 2/3rds the width of my screen is completely and utterly unused. Even on my secondary 1600x900 monitor, it's wasting half the screen on a grey background.

Try unmaximizing your browser window and resizing it to half the width of your screen. There's a reason that Windows is plural (except for Window 8). If you let us know what desktop operating system you're using (and, in the case of X11/Linux, what window manager), I can give detailed instructions.

Re:Try unmaximizing your browser window (2)

gman003 (1693318) | about 4 months ago | (#45754827)

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.

Put what else in that space? (1)

tepples (727027) | about 4 months ago | (#45754861)

A website should use as much space as it is given.

A column of text can't get bigger than a specific width without becoming hard to read. What should the web site put in the rest of the space? A pile of ad banners? It's like maximizing a file browser window showing a folder with three files in it. What should be shown in the rest of the window?

Re:cyanogenmod scam (5, Informative)

game kid (805301) | about 4 months ago | (#45752411)

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 way they will finance the project: customization for their customers (e.g. carriers). This will imply the work done by the community will be sold to a third party by Cyanogen Inc, and that they have to do changes that they cannot put online publicly. A future conversation with Steve Kondik will reveal that they might need to put hardware-specific enhancement for some camera devices, and that has to be hacked in the Camera app code. Putting these changes inside Camera apps instead of Hardware Abstraction Layers (HAL) could break other apps, which ironically kind of go against the goal of CTS (because then, only the “official” camera app will have those enhancements). Of course, those hardware enhancements are trade secrets, so they cannot be published back to CyanogenMod’s public repositories...

So this is where I started to feel screwed. I didn’t think much further, but I felt like I had no other choice but comply with Cyanogen’s relicensing, and allow them to do whatever they want with my code, and sell it customized to their vendors. They used the Contributor License Agreement as an argument, saying that basically they could do anything with my code since I submitted it.

At the same time, the “cyngn.com” domain was discovered, and concerns rised about what the hell it was. People such as pulser_g2 started to find connections between Cyngn.com, Kirt McMaster, Steve Kondik, Koushik Dutta, and all these people working at a “secret company” in a “secret location”. From ways I cannot even explain, he was able to come up with everything Koush and Steve told me, how they’d make money, and what are their future plans. Since he already knew everything, I told him about what was going on with Focal licensing, and he came up with the fact that this wasn’t legally right: the software is licensed as GPL, the repository on CyanogenMod’s github is forked from my GitHub, so it didn’t go through the Contributor License Agreement (which only applies to Gerrit submissions), and the Berne convention can prove through the commits history that I did fully write the app, and not Cyanogen Inc. - and even if the CLA would apply, it only allows them to sublicense the software, not relicense or dual-license it without my permission.

I didn’t want to be a jerk on that licensing story, and went ahead to resolve the issue directly in private with Steve. At the same time, other people such as Andrew Dodd (Entropy512) beginned to hear echoes about something was going on with Cyanogen, and heard about the GPL licensing issues around the time Land of Droid revealed the connections. He got really upset about that, getting only silence or vague answers from CM leads, turning around sentences.
That’s where they started lying to the community, denying they had something to do with cyngn.com, denying there was a commercialization of CyanogenMod going on. When people said “Why would Focal get relicensed?” they would just say “No, it’s not relicensed. It will stay GPL.” - yes, that’s where “relicense” became “dual-license”, where the app would remain GPL publicly, but still allow Cyanogen Inc to do what they want with it. But they didn't mention that publicly.

pulser_g2 raised some points on an XDA post that became quite famous, quoted by some news websites, and raised to the attention of some CM leads.
The official answer was: “Don’t interfere, don’t reply, let it go”

So, they didn’t confirm or infirm that CyanogenMod was or was not going commercial. If it wasn’t going commercial, they would have denied it. But here, they ask to “let it go”. Why not tell the truth? For them, it was better to just sweep it under the rug. But who was right in the end?

At that point in time, I still had no news about the contracts I was meant to receive weeks ago for working with Cyanogen Inc on Focal. I pinged ciwrl, who told me to check with koush, who told me to check with Steve, who didn’t reply.

At that time, they also started scrapping features from CyanogenMod. Device’s “Advanced settings” disappeared, without getting a proper replacement first. Some features aren't considered as useful enough, and didn’t make it into the new CMHW HAL. Even if users want something, they won’t get it if it’s not useful enough. Save to external SD disappeared as well from the AOSP Camera app, because it breaks Google’s CTS. Root access is planned to be COMPLETELY removed by default, and to be downloaded in a separate package. Users don’t use root anyway, they say. All of this because of a future CyanogenMod Phone, which has to pass CTS to get Google Apps officially. Want some exotic features? Too bad. You won’t get them if Google don’t. Wasn’t that the point of CyanogenMod originally? Derp.

That’s when my concerns started to raise about the community contributions. People such as +Neboja Cvetkovi contributed a lot of features to CyanogenMod’s launcher “Trebuchet”, and felt bad about not getting any reward for his work, when Cyanogen Inc. would make money out of it. Same concerns were raised by other maintainers and developers who contribute, or used to contribute to CyanogenMod. It was the last bit required for multiple people to leave the CyanogenMod development community, or for some users to simply stop using CyanogenMod. They didn’t know exactly what Cyanogen Inc was up to, but since the leaders would just lie to them to hide the truth, they felt let down. And it was clear from my chats with Steve that they had no ideas or plans, besides contracting everyone, to reward contributors. But they cannot just contract everyone, like nebkat as he’s not old enough yet to have a contract. Some other people just don’t want to be contracted, but still want to get a reward. It’s only recently that I told Steve that people would be totally happy with some perks (computer stuff, t-shirts, usb drives, devices for big contributors, etc.), and it seems like he didn’t think about that at first.

This continued for some time, until now. Cyanogen Inc is now public, and they revealed (part of) their plans for the near future. And a sentence struck me on most news sites that relayed the news: they talk about “Cyanogen’s new Camera app” -- what WHAT? So it’s Cyanogen’s camera app now? It not a CONTRIBUTION anymore?! - They claim it's their app, and I still had no news about the whole licensing thing, even if I had the chance to raise the point a few times.
This was too much this time - I pulled the alarm. I first contacted +Abhisek Devkota on why it was phrased this way, to be welcomed with a “You submitted it” Uhm, no, but he wasn’t going to argue with me, and told me to see that with Steve, which I did. After some chat, explaining how he could reward nebkat and other contributors, he told me that he was still waiting on me to “list my pricing, features and milestones for Focal” -- which I did, back on July 23rd. I never had any answer, seemingly because the “Focal drama started” and he got frustrated. From there, it seemed like Steve just wanted to stop dealing with it because “this is too much drama”. The exact drama part that bothers him? Well, some contributors weren’t happy about what Cyanogen Inc is. +Andrew Dodd really insisted and wanted to have explanations on WHY Focal would need to be relicensed, and why all this secrecy, without any real answer ever.

And how does Steve deals with these kind of reactions now? Easy answer:
“Oh god please tell me the story. grabs popcorn” https://plus.google.com/u/0/101093310520661581786/posts/1ev1FJpSCE3 [google.com]

Well, here’s your story. And here’s how they treat huge contributors like Andrew, who aren’t big enough and don’t open their mouth with the right people. The most ironical thing? If they want to dual-license, it is to make non-open changes to the apps. So, we’ll need CyanogenMod for the CyanogenMod Phone, because the code shipping on the device won’t match the public code.

Steve’s argument to avoid rewarding people, is that people wants to be “retroactively paid” - but he doesn’t seem to understand that people contributed when CyanogenMod was still a project all about open source, that wasn’t removing features from the ROM, and that had no commercial intentions. Nebkat contributed a lot of stuff in the Launcher, which is a central component of CyanogenMod today. But he did it a few months ago, “before” Cyanogen Inc, so he doesn’t deserve anything. But Cyanogen Inc can sell it to his customers.
Entropy512 wanted to clarify that point for his situation, which is true for many other contributors: “Some people like myself contribute to the project to keep our minds sharp and it's rewarding in and of itself. I make more than enough money in my day job. If someone is planning on creating a closed source fork, which is the only thing that dual licensing enables, it is no longer rewarding.”

Now, don't get me wrong. Cyanogen Inc is a huge milestone for CyanogenMod, and I can only applaud Steve for the initiative and being able to get there. There are not only dark points with the company, far from that. There’s a big bright side: CyanogenMod will become more stable, and will eventually get more features (even if they’re not going to do anything against CTS). Device support might get enhanced, since they’re paid to work on it now (even if issues existing for a LONG time aren’t fixed). And users maybe will get official support.

But the community can feel let down at some point. People from external ROMs would have loved to contribute back to CM at some point. However when Cyanogen’s leaders refers to Paranoid Android or AOKP, they call it “that other ROM”. Steve, always saying “Go ahead and fork”, isn’t actually taking seriously contributions from other developers. And since external contributors know their contributions are going to be ignored, they just don’t submit anything.
I could go on and on with many other things, how the code review is done (or rather, not done), how submissions are just -2’d without explanations, how they criticize XDA users (yes, where ¾ of their user base come from), how they complain people don’t contribute, when they DID but the patch was ignored because the maintainer didn’t want it at that time, how unstable devices are tagged as RC/stable (without asking their maintainers ; Netflix won’t run on a “stable” build of CM for exynos devices), etc. But I’m not here for that.

At this point, on my end the issue is solved, Focal is pulled from CyanogenMod. It wasn't a last minute decision, it wasn't just because I discovered it just now. It's something that has been running for around two months, and the solution was only found yesterday after a long discussion, and because it had to be stopped quickly.
I will keep on improving the app, fixing bugs, and make it better. If it’s not in CyanogenMod, then it will find room in another ROM. The app is GPL, and I will put it up on the Play Store at some point.
I have plans to raise the awareness of the importance of Open Source, and how GPL doesn't prevent any paid work, and that that there are easy ways to keep the community happy with such a situation.
And at the same time, I wish the best to Cyanogen Inc.

Keep in mind: CyanogenMod wouldn’t be what it is today without its contributors. If you’re able to run CyanogenMod on your device today, it might not be only thanks to Steve, Koushik or Ricardo. There are hundreds of people behind them who pushed many patches, and enabled many devices as a hobby. Have you ever heard of them?

Re: cyanogenmod scam (0)

Anonymous Coward | about 4 months ago | (#45752607)

To me it looks like a VC trap..

Thank you for your work. (1)

emil (695) | about 4 months ago | (#45752983)

I'm a user of CM10.1, and I appreciate your efforts and participation. I wish you could have found a more satisfying solution. I will look forward to Focal's availability.

It seems hard to commercialize a GPL codebase. Even RedHat had to abandon their community distribution to keep their developers paid, which upset a lot of people (including me).

Perhaps you can try again in another project. I hope you can make it work if you do.

Re:Thank you for your work. (1)

game kid (805301) | about 4 months ago | (#45753081)

For the record, I am not Mr. Lesniak, just someone who copied his comment from his G+ page. :)

I do agree a thank you is in order for his work, and I think for bringing the story to light too.

Re:Thank you for your work. (1)

emil (695) | about 4 months ago | (#45755463)

Well, thanks for copying, even if I do feel a few neurons short for not realizing the repost.

Re:cyanogenmod scam (1)

Anonymous Coward | about 4 months ago | (#45752587)

I would never buy another Oppo device as they refuse to implement a partition structure that allows for device encryption.

One Major Problem (0, Insightful)

Anonymous Coward | about 4 months ago | (#45752137)

This means the phone will run Google's apps and services... Who would want that?

Re:One Major Problem (0)

Anonymous Coward | about 4 months ago | (#45752969)

Who? Almost everyone who buys an android phone.

If it's not on Amazon or the publisher's site (1)

tepples (727027) | about 4 months ago | (#45754283)

This means the phone will run Google's apps and services... Who would want that?

Anybody who wants to run an Android application whose publisher has chosen not to make it available through Amazon or as an APK on the publisher's own web site.

That phone looks nifty in some ways (1)

idioto (259918) | about 4 months ago | (#45752171)

Never heard of it, and the article doesn't mention much about it, but upon researching it's got some cool gizmos. The one that stuck out to me was that you could control it from the backside. And you all know that's what we want with any device.

I don't want Google (1)

Anonymous Coward | about 4 months ago | (#45752383)

Can Oppo do a non Google version? Because I don't want to be forced to sign up a Google account and have it track me. I've ditch Gmail already thanks to the NSA and don't see why watching a cat video on YouTube should mean I have to give up privacy.

Re:I don't want Google (1)

ChunderDownunder (709234) | about 4 months ago | (#45752469)

Cyanogenmod doesn't depend on Google services - it's based on the open source AOSP code.

This phone is blessed by Google to access the Play store and associated services. As with any Android(TM) phone, it'll come preloaded with Google Apps on the shipped firmware but presumably you're under no obligation to use them.

I assume too that one can wipe the phone with a 'clean' CM 1x image that doesn't include Google taint at all...

Re:I don't want Google (0)

Anonymous Coward | about 4 months ago | (#45753235)

How do apps on Cyanogenmod receive notifications? You don't want every app polling because that will kill the battery. The usual solution on Android is Google Cloud Messaging. If you want (quite reasonably) to avoid Google, what do you do?

Check for New Comments
Slashdot Account

Need an Account?

Forgot your password?

Don't worry, we never post anything without your permission.

Submission Text Formatting Tips

We support a small subset of HTML, namely these tags:

  • b
  • i
  • p
  • br
  • a
  • ol
  • ul
  • li
  • dl
  • dt
  • dd
  • em
  • strong
  • tt
  • blockquote
  • div
  • quote
  • ecode

"ecode" can be used for code snippets, for example:

<ecode>    while(1) { do_something(); } </ecode>
Sign up for Slashdot Newsletters
Create a Slashdot Account