# MC7304 with Android 4.2

**URL:** <https://forum.sierrawireless.com/t/mc7304-with-android-4-2/8257>\
**Category:** MC/EM Series\
**Created:** [October 28, 2015, 10:34am UTC](https://forum.sierrawireless.com/t/mc7304-with-android-4-2/8257 "2015-10-28T10:34:16Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![egrewe](https://avatars.discourse-cdn.com/v4/letter/e/ed655f/32.png) [@egrewe](https://forum.sierrawireless.com/u/egrewe)\
**Post date:** [October 28, 2015, 10:34am UTC](https://forum.sierrawireless.com/t/mc7304-with-android-4-2/8257/1 "2015-10-28T10:34:16Z")

</div>

Hi,

we try to install the RIL for the MC7304 in our Android 4.2 (AndroidRIL\_QMI\_V3.1.1\_ARM\_4.2\_V1.0\_bin.zip).

We have installed the kernel files and the RIL Driver so far. We have not done the Android modifications yet.

After Integration we found the following devices:  
ttyUSB0  
ttyUSB1  
ttyUSB2  
ttyUSB3  
ttyUSB4  
qcqmi0

After modification of our libc (the RIL Driver was searching for the functions \_\_strchr\_chk and \_\_strrchr\_chk, which were not in our libc) the RIL starts.

In logcat -b radio we see:

10-26 08:43:47.250 I/RIL ( 2373): 3G modem monitor thread is start  
10-26 08:43:47.290 I/RIL ( 2373): Entering RIL\_Init…  
10-26 08:43:47.290 I/RIL ( 2373): Opening tty device automatically  
10-26 08:43:47.290 I/RIL ( 2373): Using network interface usb0 as primary data channel.  
10-26 08:43:47.290 I/RIL ( 2373): RIL\_Signalinit  
10-26 08:43:47.290 I/RIL ( 2373): \>\>\> voice feature disabled  
10-26 08:43:47.290 I/RIL ( 2373): \>\>\> persist.sierra.notification NOT set: debug radio notifcation disabled  
10-26 08:43:47.290 I/RILQAPI ( 2373): starting swi\_osapisdkprocesscreate  
10-26 08:43:47.330 I/RILSLQS ( 2400): SU:Process Started, version: (NO TAG)  
10-26 08:43:47.340 I/RILSLQS ( 2400): SU:7 -\> task started  
10-26 08:43:47.340 I/RILSLQS ( 2400): QM:Task started  
10-26 08:43:47.340 I/RILSLQS ( 2400): SU:12 -\> task started  
10-26 08:43:47.350 I/RILSLQS ( 2400): SU:1 -\> task started  
10-26 08:43:47.350 I/RILSLQS ( 2400): SU:17 -\> task started  
10-26 08:43:47.350 I/RILSLQS ( 2400): UDIAG:DS Shell launched  
10-26 08:43:47.350 I/RILSLQS ( 2400): UDIAG:DS Shell launched  
10-26 08:43:47.350 I/RILSLQS ( 2400): UDIAG:DS Shell launched  
10-26 08:43:48.310 I/RILQAPI ( 2373): SDK Pid set  
10-26 08:43:48.310 I/RILSLQS ( 2400): QM:qmqmireq/1394: Request: QMI Instance 0  
10-26 08:43:48.310 I/RILSLQS ( 2400): QM:SDK-\>Mdm: request received : ipcch/svctype/xactionlen/clientnum: 0/00f7/4/12  
10-26 08:43:48.310 I/RILSLQS ( 2400): QM:SDK-\>Mdm: request validated : ipcch/svctype/xactionlen/clientnum: 0/00f7/4/12  
10-26 08:43:48.310 I/RILSLQS ( 2400): QM:SDK-\>DCS: Request Sent : ipcch/xactionid: 0/0001  
10-26 08:43:48.310 I/RILSLQS ( 2400): QM-DCS:SDK-\>DCS: Request Received : ipcch/xactionid: 0/0001  
10-26 08:43:48.310 I/RILSLQS ( 2400): QM:qmshortresp( 6, ch: 0)  
10-26 08:43:48.310 I/RIL ( 2373):  
10-26 08:43:48.310 I/RIL ( 2373): QCWWAN2kEnumerateDevices unable to find device… 6  
10-26 08:43:49.310 I/RILSLQS ( 2400): QM:qmqmireq/1394: Request: QMI Instance 0  
10-26 08:43:49.310 I/RILSLQS ( 2400): QM:SDK-\>Mdm: request received : ipcch/svctype/xactionlen/clientnum: 0/00f7/4/12  
10-26 08:43:49.310 I/RILSLQS ( 2400): QM:SDK-\>Mdm: request validated : ipcch/svctype/xactionlen/clientnum: 0/00f7/4/12  
10-26 08:43:49.310 I/RILSLQS ( 2400): QM:SDK-\>DCS: Request Sent : ipcch/xactionid: 0/0002  
10-26 08:43:49.310 I/RILSLQS ( 2400): QM-DCS:SDK-\>DCS: Request Received : ipcch/xactionid: 0/0002  
10-26 08:43:49.310 I/RILSLQS ( 2400): QM:qmshortresp( 6, ch: 0)  
10-26 08:43:49.310 I/RIL ( 2373):  
10-26 08:43:49.310 I/RIL ( 2373): QCWWAN2kEnumerateDevices unable to find device… 6  
10-26 08:43:50.310 I/RILSLQS ( 2400): QM:qmqmireq/1394: Request: QMI Instance 0  
10-26 08:43:50.310 I/RILSLQS ( 2400): QM:SDK-\>Mdm: request received : ipcch/svctype/xactionlen/clientnum: 0/00f7/4/12  
10-26 08:43:50.310 I/RILSLQS ( 2400): QM:SDK-\>Mdm: request validated : ipcch/svctype/xactionlen/clientnum: 0/00f7/4/12  
10-26 08:43:50.310 I/RILSLQS ( 2400): QM:SDK-\>DCS: Request Sent : ipcch/xactionid: 0/0003  
10-26 08:43:50.310 I/RILSLQS ( 2400): QM-DCS:SDK-\>DCS: Request Received : ipcch/xactionid: 0/0003  
10-26 08:43:50.310 I/RILSLQS ( 2400): QM:qmshortresp( 6, ch: 0)  
10-26 08:43:50.310 I/RIL ( 2373):

The RIL continues writing these logs (unable to find device).

Nothing else happens. What can be the problem for not finding the device?

Thanks  
EG

---

<div class="post-metadata">

**Author:** ![egrewe](https://avatars.discourse-cdn.com/v4/letter/e/ed655f/32.png) [@egrewe](https://forum.sierrawireless.com/u/egrewe)\
**Post date:** [October 28, 2015, 11:29am UTC](https://forum.sierrawireless.com/t/mc7304-with-android-4-2/8257/2 "2015-10-28T11:29:33Z")

</div>

Additional Information:

We see in rild.c that the RIL driver does not return from the rilInit(&s\_rilEnv, argc, rilArgv) call.