When attempting to enter commands in the terminal on my C2, I often, er, usually end up with a screenful of command prompts and the return key remains highlighted until I tap it or the screen again.
How can I stop it doing this?
Another problem with the terminal is that it doesn’t accept my password, which I assume is the same numeric code I enter to start the C2?
Is this the default SfOS terminal that magically appears when you activate developer mode?
That one uses its own keyboard.
I just had a quick look, I don’t see what could be causing this. Keyboard delay should be set to something like 3000 ms by default. The lowest is 1000.
Sliding the Keyboard Delay slider to min (=1000ms) might have improved things a little, but the Return key “sticks” every 2-3 times I enter a command. Tapping Return with no command is less susceptible. There is often a delay between tapping a key and the key becoming highlighted, but Return is the only one I’ve seen become stuck - which is when my screen fills with command prompts until I tap the screen.
The Keyboard Delay slider doesn’t seem to have much effect. Setting 10000ms seems to respond at the same rate as 1000ms. 10000ms = 10s, so I would expect a significant delay. ???!
I just wanted to rule out the only adjustable thing that seemed like it could be related.
Honestly I have a hard time seeing this as a software issue, but you should
ssh into your phone
start fingerterm from the command line
(optional: start devel-su journalctl -f in a separate ssh session)
reproduce the issue
see what you see
Could it be the touchscreen being “stuck” in that area? Wasn’t there a testing tool somewhere - ah yes, go to Settings => System => About product and tap the build number many times, opens CSD tool, which has touchscreen tests.
The CSD tool couldn’t find anything wrong with the touch screen, although the gyro fails every time I try it. Should I ask for a new phone?
ETA:
I needed to have Remote Connection enabled - works now. Here’s what I get:
| Sailfish OS 5.0.0.77 (Tampella)
'—
[defaultuser@JollaC2 ~]$ fingerterm
[D] unknown:0 - Using Wayland-EGL
library “libutils.so” not found
library “libdmabufheap.so” not found
library “libbase.so” not found
library “libz.so” not found
library “libcutils.so” not found
library “android.hardware.graphics.mapper@4.0.so” not found
library “libgralloctypes.so” not found
library “libhidlbase.so” not found
library “libhardware.so” not found
library “libc++.so” not found
library “libion.so” not found
And you reproduced the issue while using fingerterm in this way? Did all those not found errors come up immediately, or some only when the return key got stuck?
Weirdly I get completely different output on my Xperia X 10 II that does not have the issue:
$ fingerterm
[D] unknown:0 - Using Wayland-EGL
library "libui_compat_layer.so" not found
library "libGLESv2_adreno.so" not found
library "eglSubDriverAndroid.so" not found