God is an Iron…

God is an iron,” I said. “Did you know that?”

I turned to look at her and she was staring. She laughed experimentally, stopped when I failed to join in. “And I’m a pair of pants with a hole scorched through the ass?”

“If a person who indulges in gluttony is a glutton, and a person who commits a felony is a felon, then God is an iron.”

– Spider Robinson, God Is An Iron (1977)

This is what I get for tempting fate.  The last entry was about the sanctity of the repo; Anyone want to guess what happened to it?

*double facepalm*

For the past 3 days, we’ve been toiling mightily on getting the code-base back to a build-able state.   In order to build, one must destroy – but I digress.

We’ve revamped the build system, and a few other things, to keep up to date with the goings-on in the Android world.   Some things are fixed, others are still in the works, and a third category to encompass “things that are yet to be” (meaning, they are on the back burner).  New devices are coming, as we get them working.  As well, existing ones are getting overhauled and updated to bring them into spec with others.

At this point, we’ve semi-formally implemented a modification freeze, pending updating and verification of existing devices.  Of course, this doesn’t stop us from reading suggestions, but it does mean that the pace of things might calm down a little.  The belt and braces model of things dictate getting the house built, then remodeling.

Now that the housekeeping has been taken care of…


My Anti Anti-CM Harangue

CyanogenMOD (CM) is a very polarizing topic – Either you love it or hate it.

Yes, I consider it a topic rather than simply an Android ROM.

Too many folks consider CM to either be the digital second-coming, or the bastion of (feckless) evil.  It’s neither.

For the first crowd, anything not CM related is probably worthless and will eat your cat.  For the second, CM will still eat your cat, but will cackle mercilessly while doing it.  Let’s face it, CM is the Gold Standard for custom Android Platforms.  I’m not reluctant to say this publicly.

CM has the sheer scope in numbers and background to manage fixes and enhancements beyond what Google provides.  Quick Settings, for example, with the awful long-press to activate setting in AOSP is atrocious in practice.  I can’t even begin to wonder what was going through the minds of the original devs who decided this was going to be a great idea.  Its ass-backwards and counter-intuitive.  Someone along the line inverted it on the CM platform, and life was good (TouchWiz also provides this, never checked on Sense).  Indeed, it was such a wonderful thing we’ve included the option of selecting which style you want in OctOs.  Does the fact the original idea (but not the implementation) originated with CM?  No, not at all.  Somewhere, sometime, someone said “I want this” and made it happen.

CM isn’t evil.  They, like us, do their own thing – and do it well.

If you want to pick a cause to roust yourself out of chair for, here are a couple of suggestions.