Let’s talk marshmallows

So is been almost two weeks since Google spread the heavens and came riding down on their unicorn and threw a bag filled of Marshmallows at us.

Many of us were not looking forward to Android M. Simply because we knew what was coming. We didn’t know exactly what would be “Googlify” but we’ve been around the block a few times and know how things go down. Unfortunately, we were right on many fronts. Once we all got a chance to sync the source, add the binaries and compile for our primary device (Nexus 6), we saw that this version of Android seem rushed.

We don’t exactly know why it was rushed out but we normally see AOSP source being released around Halloween so we know it was definitely different compared to past years.

What was wrong?

A few things but compared to past years and considering these issues were on a Nexus device, it was that more annoying to see. Not providing the toolchain to compile their kernel source on one of their most recent devices (Nexus 6) and incomplete blobs which caused a lot of confusion around the Android community. Many knowledgeable developers found themselves with a deer in the headlight look because they have done what they’ve done for years and this year, they had no data/signal on last year’s Nexus. This left many of us questioning ourselves if we missed something. After regrouping, we found that these issues were effecting everyone.

Things have since looked up and we now have a somewhat functional build for most Nexus devices. YAY Google!!

Moving forward, we will start evaluating our CAF based devices and put in the work to get those booting. Hopefully we have enough coffee and liquor haha

With every Android version, things change. Source code changes, maintainers come and go and the ROM itself matures. With this also comes newer devices that we add support for and older devices being dropped. This year is no different on that front.

We have decided to drop a few devices. This decision was made not because of Android M as much as it was made because life happens and the maintainer can no longer maintain them.

Those devices include the Samsung Galaxy Note 3 (HLTE) and Sony Xperia Z (yuga). More devices maybe dropped but as of right now, those two are certain to not make it to M with us. As with all things, it is subject to change. We might gain another maintainer who does have the time to maintain those devices so don’t be surprised if they get DU flavored M in the near future.

So what about Lollipop?

Nothing much to say on that except that we’ve experienced a lot of different things and learned from that, both good and bad experiences.

Many of you have expressed the need for us to release one last build for Lollipop with Google’s security patches and we have listened and will make that happen. As of right now, we don’t know when exactly that will be but that it will happen before we release our Android M based builds.

As always, we ask for your patience and thank you for your continued support!