Producing Qwerty OtherHalf --order counter: 75/75 --ordering closed - Page 78 - maemo.org

Active Topics

Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (13)
to SailfishOS by edp17 - 1 hr, 19 mins ago
Sailfish OS for the Samsung Galaxy Note 4 (SM-N910C) - (treltexx) (79)
to SailfishOS by edp17 - 1 hr, 23 mins ago
U-Boot for Nokia RX-51 with BootMenu (updated version 2012.10-rc3-1) (843)
to Alternatives by Arno_11 - 6 hrs, 42 mins ago
List of well performing apps on Leste (34)
to Maemo 7 / Leste by biketool - 1 day, 6 hrs ago
Maemo repository (5)
to Community by dredlok706 - 3 days, 2 hrs ago
Re-commissioning N9 in 2018 (127)
to MeeGo / Harmattan by smatkovi - 3 days, 4 hrs ago
Porting apps to Leste (41)
to Maemo 7 / Leste by Arno_11 - 3 days, 22 hrs ago
N900 is not recognizable on any of my devices (windows 10,7, xp) What can I do? (1)
to Nokia N900 by nieldk - 5 days, 10 hrs ago
more...

Page 78 of 81

Thread Tools

Ozymandias	2014-05-05 , 06:32
Posts: 136 \| Thanked: 58 times \| Joined on Apr 2012	#771

A few of my keys still require a lot of pressure to register, so typing at the moment is a bit slow because I have to constantly check whether the key worked.

Anything I can do on my end to make this work a bit smoother?

Thanks and again, great job!

Ozymandias	2014-05-05 , 07:40
Posts: 136 \| Thanked: 58 times \| Joined on Apr 2012	#772

My kb stopped working. Don't know if it's software or hardware, did reinstall and several reboots, but kb seems dead :/

	pycage	2014-05-05 , 08:54
	Posts: 3,404 \| Thanked: 4,474 times \| Joined on Oct 2005 @ Germany	#773

Originally Posted by Ozymandias

My kb stopped working. Don't know if it's software or hardware, did reinstall and several reboots, but kb seems dead :/

Try starting tohkbd manually as root in the terminal. My keyboard showed the same, but after starting it manually, the keys worked again (but with auto-repeat too fast). Looks like a software issue.

__________________
Tidings - RSS and Podcast aggregator for Jolla - https://github.com/pycage/tidings
Cargo Dock - file/cloud manager for Jolla - https://github.com/pycage/cargodock

	kimmoli	2014-05-05 , 21:24
	Posts: 562 \| Thanked: 2,744 times \| Joined on Dec 2013 @ Espoo, Finland	#774

Originally Posted by pycage

...(but with auto-repeat too fast). Looks like a software issue.

There is no auto-repeat implemented.

This can be caused if you have managed to start multiple instances of tohkbd, one through systemd, one directly from /usr/sbin

check ps -A | grep tohkbd what is running.

Best way is to systemctl restart tohkbd.service
and check status with systemctl status tohkbd.service

__________________
TOH ideas, concepts and creations since 2013 toholed tohuart toheink Heebo tohIRi i2ctool tohmm LeTOH FMTOH

The Following User Says Thank You to kimmoli For This Useful Post:
pycage

dirkvl	2014-05-08 , 17:54
Posts: 1,104 \| Thanked: 5,652 times \| Joined on Feb 2010 @ Holland	#775

Making some moar keyboards this weekend! Very busy now during the week with going to college, but have some parts ready to be assembled

Ozymandias	2014-05-09 , 13:37
Posts: 136 \| Thanked: 58 times \| Joined on Apr 2012	#776

Keyboard still not working. systemctl status shows some error at the end:
tca8424: readInputReport failed, wrote -1, expected 6: Transpor...107

Edit: Checked status after reboot, didn't see an error. Did systemctl restart. Now status shows a different error: failed to write "67" to /sys/class/gpio/unexport

Edit 2: Another status check: This time again the first error, plus this:
tca8424: reset failed, wrote -1, expected 4: Transport endpoint...(107)

Last edited by Ozymandias; 2014-05-09 at 13:52.

	kimmoli	2014-05-10 , 12:46
	Posts: 562 \| Thanked: 2,744 times \| Joined on Dec 2013 @ Espoo, Finland	#777

Originally Posted by Ozymandias

Keyboard still not working. systemctl status shows some error at the end:
tca8424: readInputReport failed, wrote -1, expected 6: Transpor...107

-1 means that comms over I2C with keyboard failed

Originally Posted by Ozymandias

Edit: Checked status after reboot, didn't see an error. Did systemctl restart. Now status shows a different error: failed to write "67" to /sys/class/gpio/unexport

The unexport fails as it has been already unexported. just inconvenient error.

Originally Posted by Ozymandias

Edit 2: Another status check: This time again the first error, plus this:
tca8424: reset failed, wrote -1, expected 4: Transport endpoint...(107)

-1 means that comms over I2C with keyboard failed

__________________
TOH ideas, concepts and creations since 2013 toholed tohuart toheink Heebo tohIRi i2ctool tohmm LeTOH FMTOH

Ozymandias	2014-05-11 , 06:50
Posts: 136 \| Thanked: 58 times \| Joined on Apr 2012	#778

So likely hardware problem? Should I try to open the kb snd check for broken cable or something?

dirkvl	2014-05-11 , 07:17
Posts: 1,104 \| Thanked: 5,652 times \| Joined on Feb 2010 @ Holland	#779

Originally Posted by Ozymandias

So likely hardware problem? Should I try to open the kb snd check for broken cable or something?

The cable has a limited life. Shall I send you a new cable? Probably better if we continue over email/pm

Last edited by dirkvl; 2014-05-11 at 08:38.

dirkvl	2014-05-13 , 15:05
Posts: 1,104 \| Thanked: 5,652 times \| Joined on Feb 2010 @ Holland	#780

David P, Heikki P, Pavol -> on the mail!
anokin was already sent before the weekend

The Following User Says Thank You to dirkvl For This Useful Post:
Heik

Page 78 of 81