That would be excellent.
Please also count some € for a participation in the work.
I would be very interested!
But we’d have to find out the specs and chip if not decided yet.
My use would be professional and needed information would be: 1. Color temperature, 2. Green/Magenta correction and 3. exposure in diaphragm/speed.
But of course, the device must comply with the OP needs first.
1 Like
Just thinking… Perhaps generic interface boards with TOH pads tracks-linked to soldering pads would even be of interest?
This way, anyone could solder wires that would easily connect to the phone.
Well, it’s not as simple as that. You basically need a small controller on the TOH side since the requirements (ie. addressing and signalling to the phone) won’t be covered by generic sensors, even if they have I2S support. So, a generic TOH with a small controller might be a good idea… there is some work in this direction (with an esp board) at https://forum.sailfishos.org/t/cots-lora-3d-printed-toh-shell though I don’t think I’d go with a module, per se. One could piggyback on that project using the footprints it provides for the modules…
Ah thanks, I was not aware of that.
Yes yes yes 
for those who have no idea on how to make/design/order boards.
This really needs some kind of brainstorming session. Choosing an mcu and making it extensible is non-trivial, though going the module route, ie. using a common size like the waveshare or seed mini boards might to the trick …
3 Likes
Are you really sure that a microcontroller with firmware is needed? From what I know:
- You can directly connect I3C and I2C target ICs to the same physical bus and use all of them at their respective maximum speed.
- A buffer/translator IC between I3C and I2C is only needed for connecting I2C target devices that use features for which I3C is not backwards-compatible, for example: clock stretching. The datasheet of the I2C chip in question should contain this information. I guess, such buffers/translators can be bought off the shelf.
- From the bus-side of things, the Jolla Phone only requires a small I2C memory chip at target address 0x50 inside the TOH shell which contains identification and initialisation information as specified here. It does not require complex stuff like a microcontroller or whatever.
- On that very same bus, you can then connect any I3C/I2C chips or ready-made modules of your preference.
EDIT: Here is how this basic identification circuit looks like in the case of the Snow White TOH: Jolla Phone 2026 The Other Half - How does it work? - #7 by moripeluka
THIS! 
(20 characters)
Well, let’s see, so I need to have a circuit with a specialized chip to manage the bus. That’s one issue. Second issue, I probably need to manage communication on the bus, given that the defaults stuff like ‘wake on’ are not going to be implemented by generic modules. That’s issue number 2. And the list grows, the more I think about it. But, I’d be happy to be proven otherwise by a concrete example. For instance, a simple TOF sensor.
EDIT: For my part, I use a number of I2C devices and generally (from my driver end of it) use the default bus IDs which, if I’m using 2 TOF sensors, a display and a DAC would not be possible (I believe) with the chip in the linked document.