[Galaxy S II Original Android Development] HardCorePawn:
Just to be clear...

I have tested this extensively... I have other people testing it... This is why we don't do nightlies...

Yes, we are including CM's open source RIL

NO, we don't have the RIL issues that Rootbox has (because I figured out what was wrong and fixed it) :fingers-crossed:

For the record, initially, I did have a broken RIL... Couldn't send touch tones in a call, couldn't hangup etc...

TLDR; PROTIP: make clobber, tell your friends ;)

Long Version: Turns out that, for whatever reason, the old (Sammy blob) version of libril.so was being cached and injected into the build, despite the fact that it had been removed from vendor/samsung/proprietary/i9100/lib/ :confused:

So, you'd end up with new opensource /system/bin/rild, but old /system/lib/libril.so.

They wouldn't play nicely together and you'd get the messed up phone functionality... :rolleyes:

Old version of libril.so was, from memory, 49,100 bytes, new compiled one was 35,336 bytes...

So I did what I always do when things are not being recompiled properly... I did a "make clobber"... Which completely removes the entire build directory AND wipes the compiler cache...

Et voilà... New libril.so is built and used and everything works as it should... :thumbup: :cool:

Note: The compiler cache is useful, in that it can cut down compile time dramatically... A full build from scratch after make clobber, using 2 threads (have to play nice with rest of team sharing build box :p) will take about an hour... If the cache is available... It'll take less than 30minutes! Very handy if you're doing a lot of compiling...

The only issue, is that sometimes, you get situations like this, where, for whatever reason, the system doesn't detect a change and just bundles the old libraries in... :(

Which brings me to my last point... Why I am (and most of the Slim team are) hesitant to do nightlies... (to be honest, I'm not 100% comfortable with weeklies, but they're a good way to get feedback on new features and real world user testing ;))

Nightlies are, usually, just automatic builds of whatever is in the repo... About the only checking, is that the compile finished without errors...

This is why they are always plastered with warnings that they are highly experimental in nature, possibly broken, use at your own risk, read before you flash, make backups etc...

And yet, people still moan and whinge and complain at the devs and say things like "y u release broken build??!?"...

I personally, and the Slim team as a whole, take quality seriously... Sure we've made mistakes in the past, and released subpar versions.. . And you know what? We were so concerned about it, that we modified our entire dev and release process to try to make sure it never happens again...

This is why we:

- moved away from the "every 2 weeks" release cycle we used to have.

- implemented gerrit to allow for proper peer code review and testing

- implemented a release cycle that involves code freeze, dedicated testing and final release

Will our ROM always be perfect? No... But will we always strive to make it as close to perfect as possible? YES! :D

Sent from my SlimBean pwned GT-I9100