[G2 and Desire Z Android Development] BRad Barnett:
Ok, yes! So, htc_ril.so is having a segfault. If you look at the post on the CM forums, it references a bug on the tracker. If you go there:

http://code.google.com/p/cyanogenmod/issues/detail?id=2847

You will find this log:

http://code.google.com/p/cyanogenmo...t3.txt&token=12318b747a01014c10ad0e9879c18d13

That log has this:

I/power ( 1481): *** set_screen_state 0
I/DEBUG ( 1371): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 1371): Build fingerprint: 'tmobile/htc_vision/vision/vision:2.2/FRF91/277427:user/release-keys'
I/DEBUG ( 1371): pid: 2300, tid: 2303 >>> /system/bin/rild <<<
I/DEBUG ( 1371): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000004
I/DEBUG ( 1371): r0 100ffb34 r1 00000001 r2 000000ff r3 00000000
I/DEBUG ( 1371): r4 000000ff r5 afd41504 r6 00000000 r7 100ffb34
I/DEBUG ( 1371): r8 000000ff r9 0000b788 10 00000001 fp 100ffd7c
I/DEBUG ( 1371): ip 8037e96c sp 100ffa88 lr 80359541 pc afd18ad0 cpsr 20000030
I/DEBUG ( 1371): d0 643a64696f72646e d1 6472656767756265
I/DEBUG ( 1371): d2 0000000000000034 d3 0000000000000031
I/DEBUG ( 1371): d4 0000000000000000 d5 0000000000000000
I/DEBUG ( 1371): d6 0000000000000000 d7 0000000000000000
I/DEBUG ( 1371): d8 0000000000000000 d9 0000000000000000
I/DEBUG ( 1371): d10 0000000000000000 d11 0000000000000000
I/DEBUG ( 1371): d12 0000000000000000 d13 0000000000000000
I/DEBUG ( 1371): d14 0000000000000000 d15 0000000000000000
I/DEBUG ( 1371): d16 0000000000000000 d17 0000000000000000
I/DEBUG ( 1371): d18 0000000000000000 d19 0000000000000000
I/DEBUG ( 1371): d20 0000000000000000 d21 0000000000000000
I/DEBUG ( 1371): d22 0000000000000000 d23 0000000000000000
I/DEBUG ( 1371): d24 0000000000000000 d25 0000000000000000
I/DEBUG ( 1371): d26 0000000000000000 d27 0000000000000000
I/DEBUG ( 1371): d28 0000000000000000 d29 0000000000000000
I/DEBUG ( 1371): d30 0000000000000000 d31 0000000000000000
I/DEBUG ( 1371): scr 00000000
I/DEBUG ( 1371):
D/SurfaceFlinger( 1481): About to give-up screen, flinger = 0x93680
I/DEBUG ( 1371): #00 pc 00018ad0 /system/lib/libc.so (fread)
I/DEBUG ( 1371): #01 pc 0005953e /system/lib/libhtc_ril.so (ril_func_screen_state_notified)
I/DEBUG ( 1371): #02 pc 0003902e /system/lib/libhtc_ril.so (ril_request_on_request)

And so on.

So, the clearly rild, a daemon that must use htc_ril.so, is crashing because the lib does not match the build. Note that the version of htc_ril.so you're using in this case, is from a Sense rom. This means that likely you'd have to include the rild from a sense rom, in order to not have this crash.

I do not believe that using any sense libs in CM is a good idea at this point, from what we've seen. That is, unless we find everything using libhtc_ril.so libreference-ril.so libril.so and then replace them with sense variants...

Then, check them, to make sure other software doesn't explode because they aren't native android builds.

At this point, the best option would be to instead recompile rild under CM, so that it no longer supports ro.ril.fd.scroff.timeout and scron, and so that it won't try to access those functions in the sense libraries...

And, from what we've seen here, some of the differences in these RIL libraries are more about supporting the GUI, than anything. After all, if a sense rom can operate the same hardware, and not need to have any info about ro.ril.fd.scroff.timeout...

NOTE: at this point in time, I'd make sure you aren't using an Sense UI based libs in a CM rom right now. FYI, that's most of the RIL libs.