maemo.org - Talk - TOHKBD rev2

maemo.org - Talk (https://talk.maemo.org/index.php)

- The Other Half (https://talk.maemo.org/forumdisplay.php?f=59)

- - TOHKBD rev2 (https://talk.maemo.org/showthread.php?t=93156)

Just got myself a full set of spare parts from Dirks shop! Hope it is enough to let me build a second TOHKBD (after ordering the casings from Shapeway).

Some well-deserved fame for the TOHKBD Team!

Leading german magazin c't did a feature in their Video Podcast "uplink 8.3"

TOHKBD starts at 24:40, only in german thou.

Glad to see Dirk's factory at 27:40. That's a huge building.

Dirk fixed my keyboard and now every button works. Some buttons might require some extra force, so listening and feeling the tactile feedback is not enough. But I have noticed that the more I use ths keyboard the troublesome keys start to work better and better. After two weeks of usage the last troublesome button started to work 90% of the times.

Have any of you looked into modifying small rails instead of magnets? I'm not that fond into these magnets. Shapeways case have worn a bit and now the indexing notches are not holding the keyboard (actually the rest of the phone) in firmly enough for me to type anywhere where dropping the phone could cause damage to it.

--
Hount

It is interesting how also Google is using magnets to attach the hardware keyboard to its latest Google Pixel C Tablet.

Youtube Video.

Quote:

Originally Posted by TechCrunch

Unlike on the Surface, there is no hinge on the tablet itself. Instead, it’s on the keyboard. You simply align the tablet with the keyboard and they’ll click together. All of this is held together with magnets. And those magnets are strong. I’ve stuck the C on a metal door to test them and there was no way it was going to drop. Similarly, I never worried about the tablet accidentally detaching from the keyboard.

Source: http://techcrunch.com/2015/12/08/rev...ixel-c-tablet/

The question is, got Google 'inspired' by the TOHKBD project? :D

Quote:

Originally Posted by willi6868 (Post 1491432)

The question is, got Google 'inspired' by the TOHKBD project? :D

I can only assume so, since we invented magnets.

Another lawsuit going google's way :P

Hmm. Android support is still missing for TOHKB2..

How can i overwrite file /opt/alien/system/usr/keychars/Generic.kcm
with a custom scandic one.safely.?

Did see this workaround here but which command to use foe replacing that orginal file?

https://together.jolla.com/question/...n-android-apps

Has anyone had issues with the phone compass when using TOHKBD? Static magnetic field shouldn't affect the calibration but in my experience it does. Posted my findings in TJC but here's the summary:

Quote:

Calibration [with 8-shaped motion] works pretty much ok without TOHKBD (although it seems not be spot on) but immediately goes south (pun intended) with it attached. Also, after deattaching TOHKBD the 8-shaped motion does return the north bearing to approximately where it should be.

[...]

So, it would seem that SFOS compass is not as crazy as I've thought it to be, I just need to "pack lighter" when I need it. What I don't really understand is that how the static magnetic field can have this kind of an effect? Does it e.g. scale the sensor readings so much up that rounding errors start interfering with the calibration, or what? I also noticed that the kind of "corrective motion" that is seen after turning the phone around quickly without TOHKBD is missing when it is attached (to find an analogue from mechnanical compass, it is like the needle is not floating freely).

It could be that the magnets in TOHKBD are too strong for the Jolla's magnetometer and cause it to saturate. In that case, calibration doesn't help.