hikeit wrote: > Quick question for the community... > It seems that setting the RILD library path and tty can be done in > multiple locations. > > In boot.img it can be set in default.prop as: > rild.libpath=/system/lib/libreference-ril.so > rild.libargs=-d /dev/smd0 > >
> In boot.img it can be set in init.rc as: > service ril-daemon /system/bin/rild -l /system/lib/libreference-ril.so > -- -d /dev/smd0 > Look at the code, seems that it check the -l option and then it looks for the property database to load the library. I don't know the difference between the system.prop and build.prop Michael > In system.img it can be set in build.prop as: > rild.libpath=/system/lib/libreference-ril.so > rild.libargs=-d /dev/smd0 > > > What takes precedence? If different arguments are specified in each > one, which will actually take effect? > I'll be testing it out empirically, but if someone already knows the > answer, that'd be quicker :D > > Thanks! > > > > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
