It’s a bit difficult to begin thinking about using the I2C bus when one doesn’t have documentation about the daemon on the phone end:
https://github.com/sailfishos/symbiosis is a dead link
6 Likes
Yep, maybe something to raise in the next community meeting.
But while symbiosis is supposed to be the daemon handling TOH, the i2c may already be usable. Playing around with i2cdetect from busybox-symlinks-i2c-tools may already allow to talk over the i2c pins of the phone? Looking in /dev/i2c-*, it seems there are several i2c buses on board, which is not surprising. Looking at permissions, only the bus 8 is usable by the default user. That may be an indication that this bus is the one exposed on the pogo pins.
I’ve some i2c gadgets at home that I would like to interface with the phone, but I first need to find a way to connect to the pogo pins reliably (my skills on board design and 3D printing are close to zero)…
1 Like
Yeah, @poetaster I wonder if… 
Ok, but if one can talk to devices directly, that would be best anyway, at least for a number of use cases I have in mind where I don’t really want the opinions of the OS gettting in my way 
1 Like
Here it landed : GitHub - sailfishos/symbiosis: Sailfish TOH service · GitHub and it’s written in Rust !
3 Likes