Firmware glitch - typing text slow on some firmware+device combinations
 

I thought about doing a more scientific measurement, in the end a very basic test suffices.

On some firmware, on some devices, typing test is sluggish.

Take Kingsoft Office ( cn.wps.moffice_eng ), take QuickEdit ( com.rhmsoft.edit ). To type text, I used Hacker's keyboard ( org.pocketworkstation.pckeyboard ).

Take a T68 using firmware 1.8.2 of 3 May 2017. Open QuickEdit, type a string like 'qwertyuiop asdfghjkl': one second later, the 'l' appears. Type the same on Kingsoft: same speed.

Now take a MaxCarta using again firmware 1.8.2 of 3 May 2017. Open QuickEdit, type the same string, like 'qwertyuiop asdfghjkl': one second later, again the 'l' appears, correctly. Type the same on Kingsoft: it takes around 15 seconds for the last letter to appear.

(I am sure also the i86 had issues - I am not reporting here since it does not have the latest firmware.)

I will try to raise this as a bug.

Hi mdp,
I finally got my tablet. Its a C67ML_Carta. I too am facing a similar typing problem.
Typing is very slow and sluggish.
I tried on both the firmwares: the factory installed 1.7.5 and the updated 1.8.0.
Tried it on the inbuilt apps and on the other android apps.
Tried it with the default keyboard and with an OTG keyboard attached and with another Multiling keyboard from Play Store.

Is there a particular firmware version that will work better with this tab ?

Its not a disabling issue, just not as fast as with the kindle.

Edit: This is odd. For the past 3 days, I had this issue, but as I disconnected the OTG keyboard, a popup came that "AOSP Keyboard has stopped working"
The typing is now way faster.. Almost instantaneous, on both onscreen and the physical keyboards.
I had also just turned the suggestions, keypresses and autocorrection stuff off. Hope this lasts.

I tend to believe that this is the issue that sometimes affects editing on Onyx devices: the device cashes screen updates and renders them only in bursts. Any such option must have a switch to disable it.

IMO the device "actually" goes to sleep at those times. I observed it when:
1. Installing apps: Sometimes the progress bar would stop on its own, but will start moving once the screen is touched.
2. If a screenshot is initiated from the settings, sometimes the countdown will pause indefinitely and will resume from the same number when the screen is touched, even after few seconds have passed.

We can try com.llamalab.automate, or simply "Automate" (as suggested to me by Guest on the "Icarus 7.8" thread - the Icarus is extreme in that regard), to verify that: Automate can disable the locks system wide, and can do it conditionally (e.g.: if bluetooth is on, disable locks).

I tried Automate: yes, preventing locks seems to be the solution.
I created a flow which:

• Uses '(Battery and Power) Device Keep Awake', with 'Processor' = 'CPU, Screen and Keyboard'
• Then goes to '(Interface) Show Notification', with 'Proceed' = 'When dismissed', so you have a way to remove the lock (if you dismiss the notification the flow comes to an end and the ability to lock should be restored).

This, in a simple straight-line flow: "Beginning" → "Device Keep Awake" →"Show Notification".
Guest suggested the flow of "if BlueTooth is on, then 'Device Keep Awake'" - which is also very sensible.

Kingsoft v5.12 seems to work perfectly now (although I only tested that briefly)!

Thanks, I tried it, it seems to work. I will comment more after further usage.

Sent from my C67ML_Carta using Tapatalk

I tried too! Thanks!
I also add "Screen rotation" and open app "TextMaker" and "bluetooth" on

On my device, Automate was a big battery drainer. Even when no flow was running, 15% battery was being used in 12 hrs. So I uninstalled it. Typing is not *that* bad without it.
I can always reinstall is when I need to do heavy typing. Or someone with a rooted device can freeze it.

Sent from my C67ML_Carta using Tapatalk

I did not notice that. Anyway, I wrote an app to enable/disable system wide wake-lock easily - two buttons (not even a switch ; ) ), a Notification for quick access. I have not tested it extensively, after having verified it I will publish it here.

It depends. Delays vary from nothing to a dozen seconds (to full freeze on other devices). So it can be crippling - and uselessly so.

Similar apps are already on google play, for example:
https://play.google.com/store/apps/d...ara.wakelocker
https://play.google.com/store/apps/d...u.thedarken.wl

Surely. Normally I code straight away irregardless (a wake lock is only a few lines of code), I cheched Automate also to see all it can do.

From the Google Play page, eu.thedarken.wl looks interesting.

The one I will post does simply: enable, disable, and quick access through notification. No background services and no complications.