Unfortunately, this ROM is hit by the following CM bug:
There’s a workaround…
… but it has to be applied to the äpps during building them, so it doesn’t help us users of this ROM in the general case.
I’ll try to dig for a fix, but if someone better equipped to do that than me (spezi?) can do that, please do. We’ll probably just need to exchange one file on /system, just like with my hotfix for Bluetooth internet sharing.
Update: found a fix. The patch from https://git.replicant.us/replicant/f...1ff1e7f7242908
worked and was easy enough to binary apply.
adb pull /system/lib/libandroidfw.so
from the device and disassemble it (“objdump -d libandroidfw.so | less”, might need “sudo apt-get install binutils-multiarch” on the host system first). Then search for the call to _ZN7android10ResXMLTree5setToEPKvjb in the function _ZN7android12AssetManager10getPkgNameEPKc (the first occurrence, most likely). It will look roughly like this:
fcc4: 2300 movs r3, #0
fcc6: 4641 mov r1, r8
fcc8: 4602 mov r2, r0
fcca: 4620 mov r0, r4
fccc: f003 fc4e bl 1356c <_ZN7android10ResXMLTree5setToEPKvjb>
In a hex editor, it looks like this:
FCC0 28 46 B8 47 00 23 41 46 02 46 20 46 03 F0 4E FC (F.G.#AF.F F..N.
The “movs r3,#0” is passing false (the default value) as the third argument to the method call, we will need to change it to “true” according to the patch, so we change the \x00 to \x01 and get:
fcc4: 2301 movs r3, #1
In a hex editor, after the change, it looks like this:
FCC0 28 46 B8 47 01 23 41 46 02 46 20 46 03 F0 4E FC (F.G.#AF.F F..N.
Note how the \x00 (or \x01 now) is *before* the \x23.
I’m attaching the fixed file for the 2016-07-22 ROM.