I wanted to quickly address the circus of misinformation which has sprung up recently, particularly for everyone who uses CM or has been involved with the project.
tl;dr: CyanogenMod isn’t going anywhere, nor has Cyanogen Inc. discontinued it’s efforts towards the goal of bringing it to a larger audience.
It’s been seven years since I released the first version of CM, and so much has happened. The speed of the mobile space is only accelerating. I co-founded the company three years ago, knowing fully the kind of response it might invoke- an epic mix of love and hate. We had a few successes at the Inc, but also our share of stuff which just didn’t work at all. Anyone insane enough to do a startup will tell you that it will probably go wrong before it goes right, no matter how good your intentions are. All you can do is fix it, or it’s …
A couple of updates back, we made mention that we were actively testing the Cyanogen Apps package for CM 13.0. Today, we’re glad to announce that the testing has been positive, and all parties involved are ready to move forward with release.
As a reminder, C-Apps is being offered as an optional download and will not be pre-installed on CyanogenMod releases. This package will allow you to take your existing devices running CM 13.0, and make them more like the Cyanogen OS experience. Any CM 13.0 build since May 9th, 2016 and forward is compatible. Notably, this means that users on our last 13.0 Snapshot ZNH0E releases are not yet eligible – but fret not, we’ll resolve this later this month/early next month when we release the next wave of Snapshots.
Our last Developer Spotlight with Roman Birg. This time around we are moving the spotlight over to Christopher N. Hesse. He is responsible for several devices including the controversial Exynos devices like the Galaxy Note 4 and the Galaxy Tab S2. Developer Spotlights are a public nudge of appreciation to the developers that tirelessly work and contribute to a greater cause for a better OS.
Hi Chris, how is your day today? Welcome to your first Developer Spotlight! Can you give us an introduction to yourself?
CNH: Hi Steve, my day has been great so far, thanks! My name is Christopher Noel Hesse, I’m 20 years old and live in Germany, where I’m studying at University at the moment.
I’m working in the automotive industry on my non-University days and enjoy working on the Android platform there as well.
It does not surprise me one bit that you tinker with cars as well as smartphones. …
It’s been a couple weeks since our last Developer Spotlight with Mike Bestas two weeks ago. This time around we are moving the spotlight over to Roman Birg. He is responsible for several repositories today at Cyanogen Inc., but is ultimately known for his work on AOKP (Android Open Kang Project). Developer Spotlights are a public nudge of appreciation to the developers that tirelessly work and contribute to a greater cause for a better OS.
Roman, nice to have you on here. How is life and the dream?
R. Birg: Life is great! I’ve been living in Seattle with my girlfriend Dani for over two years now, and it has been amazing. We even got a chocolate lab who’s growing into a quite a fine doge (he had a lot of teenager energy). I can’t see myself leaving the PNW (Pacific North West), I love this place.
It’s been a while since our last Developer Spotlight with Brinly Taylor (UberLaggy Darwin) in August 2015. This time around we are moving the spotlight over to Michael Bestas. Mike is responsible for several Oppo and Sony devices including the R7. Developer Spotlights are a public nudge of appreciation to the developers that tirelessly work and contribute to a greater cause for a better OS.
Hey Mike, tell us a little bit about yourself. What can we expect from you in the average day?
M. Bestas: Since last year I work with my father as a smith (not sure this is the correct word, creating metal constructions) and in my free time I work on CM or tinker around with computers.
Do you have any shared interests that you have found working with metal and working with code?
M. Bestas: I always liked creating stuff. I’d say the common thing is that with the proper knowledge you …
For a few weeks now, users of 13.0 nightlies have stumbled across a ‘Weather’ category in their Settings dashboard, and rightfully wondered what it was (and why it’s empty). We’re now ready to provide some exposition on our newest feature to our mainline code.
Historically, we’ve used Yahoo! Weather and OpenWeatherMap to power the weather in the status bar or with our weather widget. Like most things these have had their pros and cons.
Yahoo! has been our default for some time, but they have made some recent changes to their API and policies, causing many bug reports of weather no longer working. Maintaining API compatibility is usually a trivial maintenence task, but Yahoo! Weather now requests every weather query go through an OAUTH implementation, and since these are traceable, counts against a quota limit 100k requests daily (which our millions of users quickly exceed even via previously anonymous requests) should we have just tried …