Hi Kimmo!

I really want to buy one of your new TOHOLED-case. How do I order?

My PM-function doesn't work

/Edgarx100

For inquiries, send me email to

Done!
Many thanks,Kimmoli

how about the price ?

I'm in progress of refractoring toholed packaging as per request by Jolla.

It will combine everything in a single RPM package.

No actual functional changes, but i for those who use manually installed packages, i will post here an update after it passes Jolla QA.

For me it seems, that the 1.1.1.27 has an sideeffekt to the proxymity sensor.
I always have the settings 'Display off when active' and 'Proximity' checked.
So normal use case for me at night:
- put the jolla on the table with toholed on top
- put something on the proximity sensor to switch the oled off(to not lighten the room)

The day use case for me is of course the oled activated (during meetings for example).

Actually the proximity sensor doesn't work as reliable as before.

After systemctl restart harbour-toholed.service i switch the main display off.
Then i put my finger on the proximity sensor and off.

Before the sailfishos update i'm sure you could activate the oled by the proximity sensor like a switch.
Now sometimes i have longer response times than before until the point where it doesn't act anymore .

By restarting the service i can again use it for some times.
So generally i suppose the sensor is ok.

Anyone can state that behaviour or am i the only one having this problem ?

(journalctl - f out of the box reports nothing about the proximity sensor state)

The 'Display off when main active' needs some work, e.g. it will turn oled on, even when proximity is present when phone's own display goes off. And seen also that oled is on, even when phone's display is on.


This has always been sort of like this. The toholed proximity sensor does not wake up the phone, it should serve this when phone's own proximity is triggered (which wakes up the phone from sleep)

And it should also check the proximity every 30 sec.


should show proximity state changes when hovering hand over it:

Now, one thing that can be, the proximity threshold is too close to the "ambient" value.
This can be checked by enabling ALS (disable 'Display off when active' for the test).
Run above journal command, and expose phone to different lights (with e.g. flashlight) keeping objects away from the sensor. Then following prints are shown, and prox value should remain about the same:
For my toholed, ambient proximity is kinda high, ~580 and close to the default threshold level of 650. (This is caused by the IR light reflecting already from the 3d-print)
maximum for this value is 1023.
(Most of the assemblies had ambient values < 200)

I have made factory calibrations for these, as it did depend on the color of the otherhalf, and also how accurately i managed to align pcb to the 3d print.
calibration value is stored in eeprom, and you should see it in journal, when restarting harbour-toholed.
My toholed has proximity threshold of 901
if the value shown there is 0 or >1023, the default 650 is used.

Changing eeprom value can be done with i2ctool, i'll provide instructions if the proximity threshold value needs tuning.

But, typical cause for proximity not to react, is that phone is sleeping (or there is some lint/fluff in the small holes, gently pressurised air puff should take care of it)

Thanks for the fast response.
I can find the proximity log entries in the log now.
Actually the sensor works as expected - perhaps the phone had to many parallel tasks so the reaction if the sensor was delayed.
Actually no problem.
I'll continue observing it.
Hope I was wrong and it only was a temporary problem and has nothing todo with the update or whatever .
Thanks again for the help and background information !
Uwe

Prototype of Lastu-toholed


Say Thanks to this post if you like it.

I like it very much. The price is totally acceptable and I would love to order one but I have this problem. Any hint on how to debug it? As mentioned there, neither lshal nor dmesg provided the answer, nor did cleaning the contacts as suggested here.