Welcome to another Developer Spotlight, a short Q & A with community staff. This is a small spectacle of a much larger picture that we focus on to recognize the many talented developers who contribute to one of the largest community driven open source projects around.
Brinly Taylor aka UberLaggyDarwin/uld, is a contributor and device maintainer part of the maintainer & bring-up team for the CyanogenMod community. He has been a core contributor to the project since 2012 with hundreds of contributions including being a big part of device bring ups. He’s currently a student in Adelaide, Australia, while spending some of his spare time reverse engineering low level firmware of Android devices.
So how did you get started with programming and tinkering with devices?
I started pretty young playing with Rockbox open source firmware for my Sandisk – got me into open source, plus then I got a Nintendo DS for homebrew projects.
At its core, CyanogenMod is a best in class example of Open Source development. Secure, fast, and full of meaningful choices for users, our goal is to make the world’s best Android OS available to hundreds of millions of users around the world.
Along with the resources of Cyanogen Inc. behind it, we’ve created the Platform SDK. This platform empowers developers to scale the open development of Android through CyanogenMod.
The Cyanogen Platform SDK is about safely giving developers deeper access to Android, while enabling them to create original experiences for users. Whether it’s creating new ways of engaging with existing applications or developing completely new experiences, our goal is to make sure the Cyanogen platform offers meaningful choices to meet the growing needs of a diverse, global smartphone population (6b+ by 2020).
The issue described in the the latest publication of Stagefright issues (link) has been patched in source for CM 10.1 -> 12.1. Nightlies for 12.1 beginning tonight (~2hours) will include this fix, in addition to all the other exploits that came as a result of Stagefright and DefCon/Blackhat.
On the topic of 10.1 & 10.2, while these have been patched for this particular series of issues, we do not intend to issue a new release for these branches – the patches are there more so to protect derivative ROMs that use our source as base code.
We will be releasing another stable version of 11.0 and 12.0 (as well as a stable 12.1 release) with all of these fixes (and more) by the end of this month. More on that in a separate post.
After the announcement of the Platform SDK in May we had a healthy amount of interest from users, CyanogenMod community developers, and third party Android developers. Since then we’ve had a stable release of the first version of the SDK, created further infrastructure to enable easier accessibility and maintenance, and expanded on the features available to third party app developers.
As a recap for release notes, the CM SDK hit a stable branching point for 12.1 on June 22nd, 2015. With this stable branching we’ve introduced a prebuilts repo which can be utilized to reference prebuilt, statically linkable java archives that match the current stable release. Likewise we’ve also updated the platform sdk’s wiki to detail everything from the downloading and including the jar in your own applications to …
We received a ton of great responses from the community regarding our contact card proposal, so we wanted to share with you a few additional contact card options based on your feedback. The initial contact card proposal was designed to optimize for the majority of users who do not have contact photos or high resolution contact photos. The secondary goal was to create a UX affordance that allows up to 5 options on the card while making those options easily reachable. After much discussion, we identified support for hi-res images as a third goal.
Due to the complexity of supporting multiple layouts, as well as consistency between low res and hi res cards, we would like to only support one layout for contact cards. We also want to preserve the original photo. We listened to your feedback and put together the additional options below.
Welcome to our second Developer Spotlight, a short Q & A with community staff. This is our way of taking a moment to recognize the many talented developers who contribute to one of the largest community driven open source projects around.
Jorge Ruesga is a contributor/feature developer, on the User Interface and User Experience team, for the CyanogenMod community. He has been a core contributor to the project since 2012 with hundreds of contributions, including dynamic live tiles. He currently works as a J2EE Architect in Spain.
You are one of the developers on the Asus TF700T and other Transformer devices, how do you find time to work on dynamic live tiles and maintain a device?
I just helped out dasunsrule32 and the others transformer guys with some UI/UX features for these devices, like dock battery or the custom keys handling of the dock keyboard. In my daily contributions, I work …