Sunday, 2021-01-03

*** Herrie|2 is now known as Herrie02:44
*** Sellerie1 is now known as Sellerie02:44
T42<simonschmeisser> mal: the hw-settings.ini on device is the same as here
T42<simonschmeisser> test_sensors:
mal@simonschmeisser the hw-settings.ini is really in correct location?12:02
T42<simonschmeisser> mal: I think so: -rw-r--r--    1 root     root          1396 Nov 23 18:32 /usr/share/csd/settings.d/hw-settings.ini18:53
T42<linusdan> @edp_17 : Happy new year :)19:23
T42<linusdan> By experiment. I want to see if it works outside the base of hybris-12.1. For now it still didn't work, I'm stuck on the samsung logo 😂19:23
mal@simonschmeisser does journalctl have any messages from sensorfw19:29
T42<simonschmeisser> mal: actually I couldn't find anything from sensorfw in the joutnalctl:
mal@simonschmeisser what happens if you do systemctl restart sensorfwd?20:19
T42<edp_17> @linusdan [@edp_17 : Happy new year :)20:20
T42<edp_17> By experiment. I w …], I see. If you can ssh or telnet into the device to grab some logs, there is hope. 😉20:20
T42<simonschmeisser> mal: now there is a few lines in journal:
malso which sensors work now?20:26
T42<simonschmeisser> light doesnt, proximity sometimes switches but seems more like random, gyro pass, accel has gx at 1.4, compass fails20:30
maladd this kind of config for proximity
malhow bright light have you shown to light sensor?20:38
T42<simonschmeisser> mal: good point, it's somewhat dark in here ... using a 700lm headlamp I can make it show 18304 but the values are somewhat sticky and do not update?20:44
T42<simonschmeisser> current light value I mean20:45
T42<simonschmeisser> 20hybris-features.ini has ProximitySensor=false and LightSensor=false  does that matter?20:50
T42<simonschmeisser> mal: there are a few more of these in the logs: Jan 03 21:46:12 Sailfish sensorfwd[6699]: Invalid interval requested for node ' "proximityadaptor" ' by session ' 15 ':  020:53
mal@simonschmeisser do not otherwise touch mce configs related to sensors20:55
malonly the file I mentioned20:55
T42<simonschmeisser> sure20:55
malit's normal to see some "Invalid interval requested for node" messages20:56
T42<simonschmeisser> now proximitysensor "works" worse, doesn't flip anymore at all20:57
T42<elros34> if you have light sensor reported by evdev_trace (if it's iio device then in sysfs) then you could at least check whether it reports sane values20:58
malyeah, check if there are sensors in "evdev_trace -i" output20:58
malalso some strange devices needed power toggling via sysfs to make sensors work properly20:59
malnot sure if that could be needed20:59
T42<simonschmeisser> what package is that in?21:00
T42<elros34> mce-tools21:02
T42<simonschmeisser> mal: proximity is there but at 0
T42<simonschmeisser> cannot identify light sensor21:06
T42<elros34> check how proximity behaves evdev_trace -t 121:10
T42<elros34> it might be proxmity and als sensor in one21:12
T42<simonschmeisser> does not give any output21:13
T42<elros34> search in /sysfs for 6180, it might have parameters/enable or something similar21:18
T42<simonschmeisser> @elros34 ls /sys/class/input/event1/device/   -> capabilities  event1        id            modalias      name          phys          power         properties    subsystem     uevent        uniq21:30
T42<elros34> something more like /sys/module/*6180*/parameters21:32
T42<simonschmeisser> ah ok21:34
T42<elros34> according to driver this should be enable_ps_sensor property21:35
T42<simonschmeisser> ls /sys/module/stmvl6180/ -> uevent   version21:36
T42<elros34> what about /sys/kernel/range/enable_ps_sensor?21:37
T42<simonschmeisser> that exists21:40
T42<simonschmeisser> echo 1 > ?21:40
T42<elros34> sure21:41
T42<simonschmeisser> now evdev_trace -t 1 spits out lots of stuff21:42
T42<simonschmeisser> but the csd test does not change21:43
T42<simonschmeisser> sometimes it includes a value for distance21:44
T42<elros34> the only one you should care is ABS_DISTANCE or ABS_HAT1X. There is evdev adaptor in sensorfw which can be adapted for that driver as last resort but I not sure whether it will be work correctly21:52
T42<elros34> do you have  state: OPEN -> CLOSED messages from mce now?21:54
T42<simonschmeisser> Jan 03 22:42:59 Sailfish mce[742]: modules/proximity.c: mp_datapipe_set_proximity_sensor_actual(): state: OPEN -> UNDEF21:56
T42<simonschmeisser> only one21:56
T42<simonschmeisser> HAT1X is the sensor on the back for autofocus21:59
T42<simonschmeisser> "infra"red22:00
T42<elros34> are you sure? that would mean we debug wrong sensor22:01
T42<simonschmeisser> yes, also DISTANCE is on the back22:02
T42<simonschmeisser> seems like cm vs mm22:02
malbased on test_sensors output the proximity sensor is "RPR0521 Proximity Sensor"22:06
T42<elros34> so I guess something like that: Maybe you will find something in logcat then22:31
T42<simonschmeisser> @elros34 I get this line a couple of times but it's not that informative    (offset=6)22:50
T42<simonschmeisser> I think I give up for now, will rather try to work on the pinephone camera once more tomorrow23:00
T42<agnesmarain> Fwd from Telegram:

Generated by 2.17.1 by Marius Gedminas - find it at!