Hi All,
Thanks Keving and e_maks for the reply.
With more research I found that the name has as to be some particular
format.
e.g sensors.<boardname>.so,sensors.<productname>.so.
Now the call is coming to my HAL layer but now I see only my sensors
not others.
So the question is that can we have multiple HAL layers for sensors and
need to integrate all the sensors
in one layer??.
In the nexus 7 I see that sensors.msm8960.so loads all the sensors and I
cant name my as same so
I have made sensors.flo.so and this gets called but then I lose other
sensors.
Can somebody throw some light on this as I am really stuck with this now.
Regards
Sunil
On Monday, December 30, 2013 11:10:50 AM UTC+8, Sunil Thakur wrote:
>
> Hi,
>
> I am trying to add new sensor to the android latest release 4.4.2.I have
> developed the HAL layer for my sensors.
> I dont have the hardware to test the same so I want to test the call flow
> reach my HAL layer.
>
> The issue is that I dont see call flow coming to my HAL layer.
>
> I have build the lib123.so and its there properly compiled in the
> /system/lib/hw.
>
> My question is that we call hw_get_module() from the Framework code to
> initiate the particular module.
>
> SensorDevice::SensorDevice()
> : mSensorDevice(0),
> mSensorModule(0)
> {
> status_t err = hw_get_module(SENSORS_HARDWARE_MODULE_ID,
> (hw_module_t const**)&mSensorModule);
>
> ,.....
> }
>
> I see that all the sensors present in the devices comes up but no call to
> my HAL layer.
> 1. What more settings to be done.
> 2. How all different sensors get called with one call hw_get_module.I dont
> see other hw_get_module call to other sensors
>
>
> I am struggling with this for quite a sometime now.
>
> Any urgent help is highly appreciated
>
> regards
> Sunil
>
>
--
--
unsubscribe: [email protected]
website: http://groups.google.com/group/android-porting
---
You received this message because you are subscribed to the Google Groups
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
