cartron | # 91 | 2014-09-20, 21:31 | Report

Awesome Kimmo!
Thanks!!!

Kabouik | # 92 | 2014-09-21, 01:53 | Report

The switches still seem not to work here, though the scripts do work as intented if I manually run them with sh dipXon.sh as root in the terminal.

journalctl -f | grep diptoh finds no journal, or shows nothing (no error either) if run as root. And diplog shows nothing new (but there are some lines originating from my first few trials when the script were still default).

How can I check that the service is running/not conflicting with any other OH service?

---

Last edited by Kabouik; 2014-09-21 at 02:26.

kimmoli | # 93 | 2014-09-21, 06:36 | Report

That sounds strange;

You can check service with systemctl status harbour-diptoh-daemon

To check what is running, ps -A | grep toh When diptoh is not attached, you should see this:
If you have journalctl -f | grep toh running while attaching diptoh, what you see?

And you could try to add 2-3 layers of paper between the PCB and 3D print.
Just small ~10mm pieces to position where contacts are.

Or you can try to manually start the diptoh
systemctl start harbour-diptoh-daemon (open another ssh session to do this, or New Window from fingerterm) and keep that journal running on the other.)

Hope this helps.

Kabouik | # 94 | 2014-09-21, 18:28 | Report

Thanks Kimmo.

Then, the service is running correctly. I had toholed running though, so I stopped it, disabled it, and I restarted diptoh but still no fortune when trying the switches again.

I already added two layers of papers between the PCB and the OH 3D print yesterday. :[

Here's what I get when attaching diptoh: http://hastebin.com/zuwapoqeyu.avrasm

Apparently there's something wrong with the EEPROM. That's weird because I did check that I entered the correct values when I used i2ctool, and after the first trials, the scripts where correctly echoing to diplog.

---

Last edited by Kabouik; 2014-09-21 at 18:33.

kimmoli | # 95 | 2014-09-21, 18:43 | Report

Did you have prototype toholed? (my bad memory)
The new versions should not be running, only when it is actually attached, just like the diptoh

öh. Copied it here to easier commenting:

Sep 21 20:27:16 Jolla systemd[1]: Stopping Diptoh Other Half...
^ this is caused by opening the TOH microswitch (removing TOH), then it kills the daemon.
Sep 21 20:27:16 Jolla harbour-diptoh-daemon[791]: Received signal SIGTERM
Sep 21 20:27:16 Jolla harbour-diptoh-daemon[791]: vdd set to off
Sep 21 20:27:16 Jolla harbour-diptoh-daemon[791]: diptoh exiting, bye
Sep 21 20:27:16 Jolla systemd[1]: Stopped Diptoh Other Half.
^ daemon is now shutdown, but there is prints from daemon so it has been started at some point.
Sep 21 20:27:19 Jolla kernel: toh-core toh-core.0: No valid eeprom present
^ This occurs when TOH microswitch is pressed again, but there is no contact between toh pcb and phone.

If you try this when attaching toh: start from top, and while applying pressure to the area where PCB is (making sure there is contact) and bending the print a little (2-3mm) to make the microswitch-corner to be last to snap in.

(I have discussed with Jolla to add some retries/delay to the eeprom reading procedure)

Kabouik | # 96 | 2014-09-21, 18:54 | Report

Yep I had prototype toholed, have I missed some new versions of the software?

Here's what happens when attaching the toh as you said:

# Here I just removed diptoh:
[root@Jolla nemo]# journalctl -f | grep toh
Sep 21 20:51:28 Jolla systemd[1]: Stopped Diptoh Other Half.

# And reattached it as you said:
Sep 21 20:52:13 Jolla kernel: platform toh-core.0: parent platform should not be sleeping
Sep 21 20:52:13 Jolla kernel: wakeup wake lock: tohd
Sep 21 20:52:13 Jolla kernel: active wake lock tohd
Sep 21 20:52:13 Jolla systemd[1]: Starting Diptoh Other Half...
Sep 21 20:52:13 Jolla systemd[1]: Started Diptoh Other Half.
Sep 21 20:52:13 Jolla harbour-diptoh-daemon[27420]: diptoh starting, yay. My version is 0.1
Sep 21 20:52:13 Jolla harbour-diptoh-daemon[27420]: vdd set to on
Sep 21 20:52:13 Jolla harbour-diptoh-daemon[27420]: mcp23009 initialized
Sep 21 20:52:13 Jolla harbour-diptoh-daemon[27420]: Worker started
Sep 21 20:52:13 Jolla harbour-diptoh-daemon[27420]: Write failed.
Sep 21 20:52:13 Jolla harbour-diptoh-daemon[27420]: Dips toggled: 111111
Sep 21 20:52:13 Jolla harbour-diptoh-daemon[27420]: Nothing actually changed
Sep 21 20:52:16 Jolla tohd[783]: timeout; terminating discovery

Switches seem to work now.
...
Well they stopped working 2 minutes later.

---

Last edited by Kabouik; 2014-09-21 at 19:02.

kimmoli | # 97 | 2014-09-21, 19:01 | Report

no, no updates for proto.sw

The journal you copied is ok.
That one "write error" is unknown, and i have it too.

Do you have all switches at position 1 (on) ?

And you dont see anything if toggling now?

Kabouik | # 98 | 2014-09-21, 19:03 | Report

Yep, all were at position 1. First trials have worked (demo-mode, bluetooth, wlan), and then switches have stopped working (even those I cited).

kimmoli | # 99 | 2014-09-21, 19:08 | Report

öö, so it works few times now? (or was this the first time you tried it and it worked?)

set all to OFF and reattach, does it show like this then
Sep 21 20:52:13 Jolla harbour-diptoh-daemon[27420]: Dips toggled: 000000
Sep 21 20:52:13 Jolla harbour-diptoh-daemon[27420]: Nothing actually changed

Kabouik | # 100 | 2014-09-22, 12:44 | Report

Yes Kimmo, I edited the previous message (20:54) when I realized switches were working with the custom scripts! But it stopped working a few minutes later. I removed the diptoh and replaced it again the way you advised, and it works again. I guess it stopped working yesterday because of a bad contact, or because perhaps I moved two switches at the same time inadvertently? Would that be an issue if that happens? Considering that I have very short nails and that the switches are tiny, this can happen quite often.

Anyway, thanks for your very valuable help Kimmo!