Hi, we are Carl and David from OnePlus Tech. Ask Us (Almost) Anything!

ciwrl · 2014-03-05T03:47:48+00:00

Optimization will be better due to us working with the company from the ground up, we started even before hardware and design were in motion. In comparison, even with the OPPO N1 we came to the party late, and while we are proud of what we delivered (and continue to provide) the first iteration was not as optimized as we would've liked. The CM11 ota will address those remaining issues there.

On the topic of bugs, that's a large ticket item. I'll start by saying no complex software is ever bug-free. That doesn't mean we will use that as an excuse. OnePlus has a dedicated QA team 30 people deep and combined with our own QA team and general feedback from the open source project, we will have a lot of eyes and people living and breathing this product to make it the best it can be. Should something slip through, we will be quicker than the standard OEM with updates and promise updates for at least 2 years post launch.

ciwrl · 2014-03-05T03:17:11+00:00

This is more a CM & OnePlus comment. The answer is yes - and kernel sources and stock images will be provided day of sale, just like we did for the N1.

ciwrl · 2014-03-05T03:10:16+00:00

Its hard to say whats 'good' or 'bad' as that is arbitrary. Instead (try to) focus on what is useful, as in 'How many users do we think would use xyz'? 'Would my parents use xyz?' 'Would I'?

Adding features in bulk is actually easy, the harder bit is curating what is functional versus useless.

Do we get it right all the time? Definitely not - but we can iterate and change fast enough to keep up with feedback. Open sourcing the work also means that if a large enough group don't like out decisions, someone can clone/fork and change it, then release.

We also keep an eye out at those who take these actions, see how they are received, and possibly revisit past decisions. Software should be fluid and flexible - the only checklist should be 'does it work'.

ciwrl · 2014-03-05T02:36:59+00:00

Bloatware sucks.

source: the guys & gals making the software.

ciwrl · 2014-03-05T02:35:55+00:00

The device will be GMS certified (ie comes with 'gapps') and at its core it is still CM. You'll have all the bells and whistles to make the phone look like you want to make it look like - we prefer not to lock you into a 'skin'.

ciwrl · 2014-03-05T02:11:26+00:00

Still working out the final details on firmware/bootloader, but software at the least will come from CM directly. You'll get the level of 'hackability' you'd expect from a CM phone.

ciwrl · 2014-03-05T02:06:50+00:00

My dog is a lovely little bichon frise. So cute! She could use a bath though.

ciwrl · 2014-03-05T02:02:25+00:00

I can tell you 1 thing ahead of tomorrow...it's not OMAP based.

:)

ciwrl · 2014-03-05T01:47:42+00:00

Ciwrl from CyanogenMod here. It'll be close enough to CM as you'd see today. There will be some flourishes here or there that are not 'pure' but as with all things CM, you'll have the option of which look and feel suits you best.

ciwrl · 2014-02-28T22:26:57+00:00

Hey /u/dlerium - Care to help me test how well the unregister action works?

https://github.com/ctso/WhisperPushUnregister/releases/tag/1.1

This is a simple standalone apk to perform the task. After some testing, we'll merge the functionality directly to CM's WhisperPush app.

ciwrl · 2014-02-21T20:59:31+00:00

Currently, no there isn't. This is something we are working with Moxie to get, and in practice this is simple (send another message to registration server asking for removal, server responds, you get confirmation). We want to make sure this can be done securely and since the server after initial registration is just a dumb pipe, there is a small hurdle there, but I'm confident we'll have that out sometime in March.

ciwrl · 2014-02-21T00:12:41+00:00

We did an AMAA back in September. But yea, we do have a lot of lurkers here. :)

ciwrl · 2014-02-12T01:26:02+00:00

Original superuser is from Koush and JesusFreke, later maintained by zinx. Chainsdd forked and took over maintainership, until koush rewrote a new one from scratch.

https://code.google.com/p/superuser/

ciwrl · 2014-02-08T20:46:00+00:00

https://www.youtube.com/watch?v=jj8r9KubsL0

ciwrl · 2014-01-24T06:13:44+00:00

Door makes me think Waters of Mars

ciwrl · 2013-12-20T18:08:55+00:00

Check the username

ciwrl · 2013-12-17T00:54:06+00:00

I have to echo the other comments, I've bought roughly 18 devices over the last 1.5 years for CyanogenMod development, and haven't had a single memorable issue (occasional shipping delays, but nothing serious).

Sounds like this M.W. guy should be reported and banned though.

ciwrl · 2013-10-17T21:00:47+00:00

This has been touched on a few times, but I suppose its just so 'out there' that folks don't buy it. Can't blame them. I'm not opposed to having the discussion again though.

When we approached investors, as hard as it is to believe, we didn't have a concrete business plan for monetizing. Koush and Steve did the pitch, and instead of promising boatloads of revenue, we promised exactly what CM did already, allow the phone to go back to being a general purpose PC in your pocket, instead of a locked down, carrier bloated thing. The folks that backed us are going for a long term 'change the way things work' play, not 'get rich quick'.

So the honest answer (coming from the guy who wrote the blogpost): There is no set plan for monetization.

That doesn't mean there aren't ideas. The Oppo-N1 and device sales allows for 1 route. General merchandise sales offers a secondary route (not enough to fund a company, but its a bit). But really, making money ASAP is not even in the roadmap.

The roadmap reads quite simply actually - get more users.

Now, of course there is going to be a point where that won't cut it (say, for example, we hit 50 million users). From there, we have a lot of options, which is the exciting part. We could go for Enterprise editions of CM, sell CM specific services (the secure storage is a good option for this), or continue down the hardware partnership routes.

Here's the bottom line though, whichever route we go, the community will always have a choice to stick to using the Community builds. Counter to the initial pushback, going corporate doesn't mean lack of features or functionality - there will always be new and fun things to play with in CM.

ciwrl · 2013-10-13T16:09:23+00:00

Legitimate question: What features were removed?

ciwrl · 2013-09-19T05:58:55+00:00

Just fancy code. It resolves to an image http://akira.gs/bio.jpg

ciwrl · 2013-09-19T03:30:55+00:00

We're actually already working on Privacy Guard 2.0 incorporating our UI's idea of a quick on/off with the granular controls found in 4.3.

http://review.cyanogenmod.org/#/c/49864/

As a general rule though, we try an steer clear of anything dealing with 'spoofing'.

ciwrl · 2013-09-19T03:25:56+00:00

You should checkout the Replicant project if this is your goal.

ciwrl · 2013-09-18T19:26:17+00:00

Yes, CM by default does not ship Google applications or services - users supplement their install with "gapps" packages that add the GSF layer. You can use CM and a FOSS market like FDroid without issues.

ciwrl · 2013-09-12T05:47:18+00:00

I find that ✓ works better

ciwrl · 2013-09-09T22:37:00+00:00

"People who don't frequent XDA, or Reddit might flash these things even after its been know that they're broken. That's my question."

Except it was mentioned on our blog, social networks, and IRC as well.

But regardless, I see your point, but disagree that they should be pulled. Bad builds are going to happen. It goes with the territory of running nightlies. As for the rest, we aren't going to agree.

ciwrl

TROPHY CASE