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.
We’re two months into the CM13 Marshmallow work and nearing our feature complete mark in anticipation of a release towards the end of January. As we work towards finishing and stabilizing the multitude of devices in our roster, we’ve now unblocked the other half of our contributor teams – our Translators. These 1600+ individuals are responsible for localizing the software for our features (which we’ll go through on another post) and new regions. This post is for all of you translators.
CrowdIn is now CM13 ready! Michael Bestas (translation lead) has done his due diligence and carried forward as many translations as possible from CM12.1 to reduce the workload for CM13. In total, we count roughly 380 new strings (not including plurals) as a delta from 12.1.
Additionally, we are now making use of CrowdIn’s new version management functionality. The ultimate goal here is to reduce the amount of effort required on the part …
We’ve been pretty quiet publicly on the CM13 (Marshmallow) progress, but we’ve been busy bees behind the scenes. Today, we’ve enabled the first wave of devices to receive CM13 nightlies. Now, before you jump head first into flashing these, please take a moment to read the items below – as they will impact your experience.
If you are on CM 12.1 YOG4P or CM 12.1 YOG7D releases, we recommend you stay on course with the SNAPSHOT release channel and not jump to nightlies unless you are willing to accept a dip in quality. Our stable branches are vetted, CTS run and (in some cases) shipped on retail devices – which means the quality of those branches is far and above that of nightlies. We’d advise these folks to stay on the SNAPSHOT train, and we’ll have a quality approved SNAPSHOT for CM13 sometime Jan. If you are on a 12.1 nightly, you can ‘dirty flash’ CM13 …