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 …
We left the M release builds in the oven longer than we thought, but nothing a little graham cracker and chocolate can’t make that much better. CM13.0 brings Android 6.0.1 (r17) goodies such as the battery saving ‘doze’ functionality and new permissions model, alongside the CM features you’d expect.
This is the first non-nightly release for CM13, which means this will the first step many of you take into the world of Marshmallow. M brings along a handful of items that will pose issues if you are caught unaware, so in the interest of saving you some potential heartburn, we’re going to highlight that there are a couple of different update scenarios applicable.
Update scenario 1: CM 12.1 release or nightly user + Googley bits
Update steps: Update to the latest TWRP image available for your device. Download CM13.0 (if available for your device) and your Googley bits of choice for M. Reboot to recovery, and flash …
Many users have noticed that we haven’t enabled WhisperPush capabilities into CM13, though there are patches up that include that updated work and integration into the MMS apks for both 12.1 and CM13.
We’ve ultimately made the decision that we will no longer be supporting WhisperPush functionality directly within CyanogenMod. Further, WhisperPush services will be end-of-lifed beginning Feb 1st 2016. As this is a server side implementation, all branches of CM from CM10.2 and forward will be affected.
We are still very big proponents of the secured messaging protocol, but maintenence of our own implementation saw some hiccups (longstanding registration issues & issues with various countries) which ultimately led to our decision. Our recommendation to users who rely on this functionality is to hop onto the Signal application (details at bottom on this post).
A little over two years ago we debuted our joint project to integrate WhisperPush into CyanogenMod.