Recomposing / re-editing only suggests words starting with the same letters. #668
Comments
|
It's because I wasn't sure how to do it. My old Nokia phones don't have this feature and I didn't have a reference, so I just assumed preserving the last word would make more sense. But it is bugging me too and I'll fix it in the next release. For the time being, after pressing Backspace, also hit "Clear Filter" (default: DPAD Down) and you will see the "normal" word list.
Thanks! Indeed, it has come a long way, you could say it is a completely different keyboard today. It is because I am doing a lot of hard work, but also thanks to the people who have helped with ideas, bug fixing, testing on their devices, and guiding me how to add new languages that I don't speak. It is truly a community-made product. |
This application has single-handedly made using modern keypad phones a reality! So thanks for taking it up and also working with your user base, its a big deal :) I waited a very long time for a phone like this to hit the market (was using Qin F21, until the poor quality keypad became unusable. Now have the the F22 Pro.) Looking forward to the next update! Thanks for the workaround tips too. |
|
All models share the same body, meaning, all have crappy keypads. I bought an F21 Pro+ 2 years ago and the keypad started failing in a matter of months. Then I bought a second one and the keypad failed even faster. I was going to try the superglue trick they are talking about on the Internet, but then I realized I am also having connectivity problems, because of which I missed several important calls. Or it does not have real connectivity issues, but its extremely aggressive power saving policy sometimes causes disconnects, I don't know. Either way, I just gave up on this device. It looked promising, but if I can't receive calls and type with ease, what is it good for? Saying all this, I hope you have better luck than me. |
|
What is your weapon of choice at the moment? I'd be happy to compare
notes with you, but I also don't want to mess this Github thread up with
off-topic chat. PM?
…------ Original Message ------
From "Dimo Karaivanov" ***@***.***>
To "sspanak/tt9" ***@***.***>
Cc "discoball78" ***@***.***>; "Author"
***@***.***>
Date 16/11/2024 6:55:19 AM
Subject Re: [sspanak/tt9] Recomposing / re-editing only suggests words
starting with the same letters. (Issue #668)
All models share the same body, meaning, all have crappy keypads. I
bought an F21 Pro+ 2 years ago and the keypad started failing in a
matter of months. Then I bought a second one and the keypad failed even
faster. I was going to try the superglue trick they are talking about
on the Internet, but then I realized I am also having connectivity
problems, because of which I missed several important calls. Or it does
not have real connectivity issues, but its extremely aggressive power
saving policy sometimes causes disconnects, I don't know. Either way, I
just gave up on this device. It looked promising, but if I can't
receive calls and type with ease, what is it good for?
Saying all this, I hope you have better luck than me.
—
Reply to this email directly, view it on GitHub
<#668 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIYNU5R7GQZISGH3XEVQPFL2AZGSPAVCNFSM6AAAAABRXZSWAWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZZHAYTSMBYGA>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
A touchscreen, unfortunately. I can't a solid working equivalent at a reasonable price.
We've cleared out the main problem in the first two comments. I approve the off topic below. |
|
In terms of the Qin phones, I amended a typo that I made in my post earlier. I now have the F22 Pro. I've been using it since I received it in late July (so approximately four months), the keypad was better, but I have noticed only just this week the very occasional missed keystroke for the center (d-pad) button and the number 8 key, we'll see how things go. When I was using the F21, like yourself - yes the keypad started failing fairly early on, and it got pretty bad. The phone was just so cute that I honestly couldn't let it go, so I just put up with the condition, for a long time! I documented my experiences with the F21 in this thread, and it does echo your experiences: Funny part is you'll see me talking about the T9 app, before you reactivated the project. The firmware in my F22 seems to be the same as the F21, as I had basically exactly the same issues. Which was handy as I guess it helped to resolve/work around them faster when I got the F22. Resource threads that helped me greatly while breaking in the F22: Review after 1 Month of use: Duoqin F22 Pro With the F22 I struggled to get Whatsapp to stay alive, but the above thread explained 'systemizing' apps, which resolved that for me. The power management seemed to work out OK for other apps I use, after messing around with battery optimization settings for them. The assisted dialing issue was worked around as per my F21 thread notes. I found that the missed call/message problem started happening when I installed my own selected apps (on the F21), moving back to the original system apps (even though they are very featureless) resolved that. I stuck with this approach on the F22. I was willing to make a number of tradeoffs and give up some luxuries in order to use these cute phones :) Being a father/raising a family leaves me no time these days to be messing around with firmwares and hacks etc etc like my younger days. So I just stuck with the most straightforward ways of getting the phone over the line, and fit for day to day service. I also did not want to try a completely different firmware/OS as I did not want to lose some of the native Qin style functionality. One example is the screen resolution change function, when long pressing the back button you can switch to a very high resolution mode, in case an app (or website) you are using can't properly display on the screen. These kind of things would be lost with a new OS. And besides, doing this kind of upgrade would probably open up a can of worms, which I don't have the time or motivation to chase down and resolve! I was curious as looking through the issues list, I see some phones that I was not aware of existing, sometimes no matter how much you search you can't find everything. Do you have a list somewhere of all the 'known' T9 keypad phones that are currently available? I'd love to see what else is out there. I honestly find these Qin phones so cute, so I hope to use this for a while to come.... |
|
In summary though, when all is said and done, I have this F22 Pro running exactly how I want it, and if the keypad stays good, this phone is like a a dream come true for me, I'm so happy with it :) It's not as small/cute as the F21, but the keypad was just so horrible that unfortunately I had to eventually move on. |
Sspanak, l'm a long time user of Traditional T9 - I'd like to first give you high props for taking up this projecting and doing the work you have done, really very very well done mate. I was so surprised when revisiting T9, as I had used it while it was still 'dead' and not maintained anymore. After coming back to a new phone this year and suddenly saw that you had taken on the project on a given it life again!
The last update I took was the first release that included recomposing (2 updates ago). I just updated to the latest version and noticed this behavior still present, so figured I'd report this in.
When typing in a hurry and moving on to the next word, realizing that the default word was not the desired word, backspacing to it does not present the normal 'popular' suggestion list anymore, only words starting with the same letters from that incorrectly accepted word. User must then delete sometimes almost the whole word in order to see the normal suggestion list again. I've added two screenshots of both the default list Vs the recompose list.
The demonstrated scenario is a simple one where I accepted the word 'no' when what I really wanted was 'on'. When backspacing back to the word, I only get options for words starting with 'no'. From my personal use, this renders the recompose function redundant for almost any error I make, as the majority of my mistakes stem from accepting the wrong suggested word.
Another example for a larger word: Want to type 'Subnet', accidentally press space to accept the first suggestion of 'Stand'. Backspace back to the word and are only presented with words starting with Stand, Stan, Sta, St as the user progressively backspaces toward the start of the word. Have to backspace all the way back to 'S' to be able to find 'subnet'.
From a user perspective, was hoping to see the default set of words offered again (for that key combination), when backspacing back to it. This way the user can select the word they intended in the first place.
Screenshots to follow, thanks again for your work. Joe.
The text was updated successfully, but these errors were encountered: