Quote:

Originally Posted by

Hi everyone,

I got my phone in apr 2013. Apparently, on cm12/13 it seems to be affected by this bug. So, to clear any doubt, I wonder if downgrading to kitkat might help in general.

Even if the battery gain was to be dramatically high, security is my first corcern. The last

Android security bulletins (ASB) contain a lot of critical bugs; anyway from them I discovered that kitkat still get security updates from google and from CMxLog that someone still add to about page that cm11 is updated to respect the "MM YYYY ASB". I trust cyanogenmod in that.

So since I never tried to compile aosp and as this rom wasn't updated in a while, I synced cyanogenmod repos and I compiled it with the instructions on cyanogen wiki.

The rom is good and stable.

The only change I had to do was to replace these files



/system/framework/webview

/system/framework/webviewchromium.jar

/system/lib/libchromium_net.so

/system/lib/libwebviewchromium.so

/system/lib/libwebviewchromium_plat_support.so



with ones from cm-m12-official because logcat tells me that the webview i compiled goes segfault when I try to open messages in mms.apk, k9 mail and settings in rar and amaze. In general, the code is untouched.

As you can see from the screenshot below, without gapps, with major instant messengers (whatsapp, telegram foss with smart push disabled) and email push notifications (k9 mail), battery drain on idle is basically non-existent:







I wanted to share this build with you because I think this is an amazing community.

I plan to update this rom every time an ASB comes out (once in a month, as long as google keep supporting kitkat, which I hope is long).

Obviously, the ROM is updated to the latest android security bulletin of 1st june 2016.



Zio Guiduccio



Download

MD5SUM: 4B129774050768E8D21114D7816A8D56

CM-11-20160611-GUIDUCCIO-mako.zip