# Help Using EM7355 with Android 6

**URL:** <https://forum.sierrawireless.com/t/help-using-em7355-with-android-6/9071>\
**Category:** MC/EM Series\
**Created:** [March 8, 2017, 12:53am UTC](https://forum.sierrawireless.com/t/help-using-em7355-with-android-6/9071 "2017-03-08T00:53:36Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![browe](https://avatars.discourse-cdn.com/v4/letter/b/2bfe46/32.png) [@browe](https://forum.sierrawireless.com/u/browe)\
**Post date:** [March 8, 2017, 12:53am UTC](https://forum.sierrawireless.com/t/help-using-em7355-with-android-6/9071/1 "2017-03-08T00:53:36Z")

</div>

I am having trouble merging the Sierra Wireless Android RIL 6.0 code into my Android source. I am building Android 6.0.1 for the Snapdragon u820 SOC (running Linux Kernel v3.18.20) and using the Android RIL 6.0.9 for ARM.

Specifically, I have copied the new driver files for the GobiNet driver into the kernel, but after compiling I receive errors. For example, in QMIDevice.c, there is a macro redefinition:

kernel/drivers/net/usb/QMIDevice.c:279:0: warning: “SET\_CONTROL\_LINE\_STATE\_REQUEST\_TYPE” redefined  
error, forbidden warning: QMIDevice.c:279

Looking at the code, it appears SET\_CONTROL\_LINE\_STATE\_REQUEST\_TYPE is defined in QMI.h and QMIDevice.c. Is there anyway to resolve this redefinition? Are there specific compiler options I need to include/remove?

---

<div class="post-metadata">

**Author:** ![Rex\_alex](https://avatars.discourse-cdn.com/v4/letter/r/73ab20/32.png) [@Rex\_alex](https://forum.sierrawireless.com/u/Rex_alex)\
**Post date:** [April 10, 2017, 8:57am UTC](https://forum.sierrawireless.com/t/help-using-em7355-with-android-6/9071/2 "2017-04-10T08:57:24Z")

</div>

Hello,  
Generally “macro redefinition” is considered as warning by the compiler . It seems that in your compilation environment a flag named as -Werror has been set, this flag turns warning into error which does not allow compilation to be successful .  
removing this flag from your compilation environment may solve your problem.

Thanks,  
Rex
