Need to fix sensors #1

RomzesRover opened this Issue Jun 14, 2013 · 9 comments


None yet
2 participants

RomzesRover commented Jun 14, 2013

We need to get sensors working and I think that the problem can be in permissions (ramdisk) or we need to write our own libsensors, to compile sensors.salsa
We use isl29018(light, proximity), and smb380 (accelerometer, orientation sensor)

@ghost ghost assigned RomzesRover Jun 14, 2013


RomzesRover commented Jul 29, 2013

on cm9 sensors works fine

zabulus commented Aug 3, 2013

Any logs for these problems?


RomzesRover commented Aug 3, 2013

I am so sorry but my current target cm9 and I only one person who works on this, so basecly I thint that we just need sensors.salsa source, but it impossible, cuz sensor isl29018 very old


RomzesRover commented Aug 3, 2013

drivers in our kernel 2.6.29 works fine I think, cuz im cm9 with this it works

it doesn't work in cm10+ cuz I think we need new sensors.salsa lib


RomzesRover commented Aug 4, 2013

D/SensorService( 385): nuSensorService starting...
E/SensorService( 385): couldn't open device for module sensors (Invalid argument)

zabulus commented Aug 13, 2013

Looks like sensors.salsa.lib uses deprecated sensors.h interface:
Here is callstack as it should be for that log you've provided:
haldevice_open <--- here is yamaha hal library.
haldevice_open(const struct hw_module_t* module, const char* name,
struct hw_device_t** device)

methods->open has the same prototype, but in new versions it opens SENSORS_HARDWARE_POLL id, but in old (before GB) it opens SENSORS_HARDWARE_CONTROL or SENSORS_HARDWARE_DATA.

As for CM9 there should be some cruthes to open right things, or there should be wrapper to wrap old interface in new

Here is patch for old sensors, found on github:



RomzesRover commented Aug 13, 2013

sensors now fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment