-
-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v27 Bugs on Sonim XP3plus #435
Comments
Here is the longer explanation of 2, if you are curious why is that. In the beginning, TT9 used to always automatically activate itself, but there were many reports it wouldn't deactivate when one finished typing. This is because Android doesn't know how to handle the case when the keyboard activates itself, instead of the current application activating it. The last two examples are #364 and #367, but the same happens in other applications and on other phones, too. And now, the control is entirely in your hands. If the app decides not to activate TT9 on startup, you can do so using OK, or by touching the screen, as per the Android standard. I realize this may cause inconvenience, but it is the lesser of two evils. Also, after discussing the same in #429, I realized all this is a bit unclear. I'll add the explanation in the manual to avoid the confusion to some extent. And this is one of the reasons I said the native keyboards provide better experience in some regards. They are built for this phone and for this set of apps and now when to show and hide. And being a universal keyboard TT9 simply can't handle all possible devices.
There is a way to check if TT9 is lagging. Go to the Settings and scroll down to the bottom. Click on the version name and a "secret" screen will open. Then click on "Usage Stats". In the summary section, the first row would look like "Queries: XXXX, Average Time: XXX ms". The average time is the average word load time. It should be below 50 ms for smooth experience. Anything slower than that will be recorded and you would see it in the "Slow Queries" section below. This is not so bad either, because all slow queries will be cached and should again finish in less than 10 ms. The cache will live until you restart your phone or until Android decides to start killing apps, to redistribute the memory. Now, if you see high average times and slow queries keep accumulating, this means your phone is just too slow for TT9. I may be able to do some squeeze some more performance in the future, but I believe I've done almost everything possible in v27.0. On the other hand, if most queries run fast, you probably have a hardware problem. CAT S22 phones and Qin F21 are known for their bad keypads. The CAT repeats key presses, while the Qin phone misses them. They just build low quality keypads nowadays and this may be the case with Sonim, as well. There is more info about similar problems in #399
I'll check this out. I am unaware of any such problems. |
The lagging issue does seem better. The "pressing once to activate TT9" can be easily gotten used to, and sounds like capitalization will be fixed. Just bought you 5 beers man, thanks for the great work. |
I have fixed small bugs, somewhat related to what you reported. The only thing I could not reproduce was the Add Word window navigating to some other screen. However, I have changed the way it works completely, so the problem might have just went away. Let's wait for v28.0 a couple more days and see how it works. If you are still experiencing any of the above, please report back.
Much appreciated! |
@theancientways, v28.0 is out. Please, install and let me know if any of the issues still persists. I think I was able to fix everything, besides the Add Words thing, which I was not able to reproduce. |
@sspanak I don't know what you did in v28.0 but you fixed the lag issues on the Sonim XP3plus. I also see you fixed the "add word" and upper case word issues. You pretty much fixed all the major issues I had with TT9. Kudos!! Donating again to thank you. |
Excellent! And thank you for the donation again. Since there is nothing left to do, I am closing this. |
Downloaded v27 today and two bugs I'm noticing right off the bat are:
There seems to still be an issue with missed keypresses but I need to spend more time with it to verify. If there are new settings that are causing these issues that I don't know about my bad, but please let me know if there are.
Edit: I'm also noticing when I add a new word to the dictionary, before the popup would happen in whatever text window I was in, now the popup takes me to the app settings, and then after pressing ok I have to navigate all the way back to the text window I was in.
The text was updated successfully, but these errors were encountered: