Related
Hi all,
I am new to this forum, so please bear with me if I have posted in the wrong section.
I am with T Mobile UK and I have the MDA Vario IV.
Recently, I have had a strange problem when using my slide out keyboard. When I use the onscreen keyboard, I can see the text as I type. However, when I use the slide out keyboard, I can see the cursor moving as I type, but I can't see the text being typed. This happens when composing an SMS, typing into Google's search box, entering log in details for Facebook, etc etc.
As I am Deaf, I obviously use SMS and emails a lot, so this is a problem, as I find the slide out keyboard MUCH easier to use than the onscreen one.
Hope you can help.
Wayne.
How fast do you begin typing after you slide out the keyboard? I know sometimes when I begin typing too quickly after sliding it out that the cursor will move while I'm typing but no letters will be displayed...but then they all pop up at once.
Have you used a tweaking tool or registry editor to turn on ClearType in Landscape?
There is a known issue with the font not displaying.
David
winthropdc said:
Have you used a tweaking tool or registry editor to turn on ClearType in Landscape?
There is a known issue with the font not displaying.
David
Click to expand...
Click to collapse
Hi mate...
Ahhh, that could be it...let me try it & get back to you.
You are correct David....that WAS the problem!
Thanks - all working fine now
keyboard lag solved - possible software conflict
I had tried all the above fixes and they helped, but did not fully alleviate the lag. I was getting annoyed and wishing my hermes was still alive.
Then I remembered that the only real difference in my keyboard setups between the fuze and the 8525 was that I was using the iphone like full qwerty sip instead of the keyboard sip. i selected the finger unfriendly keyboard sip, and voila the slide ouy now has instantaneous response. no lag at all.
It seems to be that the full qwerty sip option forces a t9 function even when you have all that turned off.
Happy again except for the laggy shift between portrait and land scape.
now to find an iphone sip clone that doesnt affect the slideout. By the way this is with the recent stock att rom.
further issues with keyboard
The lagging keyboard issue continues to nag me. it seems to be related to the fuze having a difficuly time with switching to landscape mode. for instance in opera mini when i switched to landscape to type this there is no lag. if I am using messaging for text or email, when I switch to landscape, the lag occurs until I change the sip. it doesnt matter which sip i change to or from, just that it gets changed. i suspect that it has something to do with resetting the keyboard drivers. anyone else noting this problem. Anyone know of a fix? I have t9x turned off, cleartype turned off.
OK. So I just just got a BT keyboard, which does not come with Android software (the packaging marketed it for iPhone). I think the brand is "FunGear", but that might be a no-name / Shanzhai / OEM thin. Anyway...it works pretty well. I just wrote out a 3 page business proposal on my Samsung SGS (with Froyo) at Starbucks using the keyboard.
However, there seem to be some bugs. When I use the keyboard, my phone tells me I need to use the default Samsung Keyboard. Its pretty basic. Furthermore, there are weird things that happen, like:
*it stops responding when Gmail does an auto-save
*sometimes it goes into all cap-lock mode and won't get out until I hit that on the screen.
*some characters seem wrong.
*there is screen down / screen up alt keys, but they don't seem to work.
The keyboard uses what's called the HID profile.
My question is: is there a utility or software keyboard which was made specifically for working with bluetooth keyboards which allow customization?
I havn't come across one but rather i found a edited keyboard.xml file that helped with my kb and its custom keys.
I love the GMD apps, including S-Pen Control & Gesture Control. I only use the S-Pen when I am writing or marking up drawings, occasionally when editing pictures, but by far, most of the time I navigate by hand.
I have used Gesture Control on numerous tablets & devices including the Nexus 10, Note 2, Note 10.1 & now the Note 8. It has worked flawlessly for the most part on every device I have used aside from the Note 8.
I have contacted the developer about the issue, which is that the "Back" function fails because the InputDispatcher drops the call. "Back" works fine using GMD S-Pen Control, but not on Gesture Control.
What I am wondering, since I don't see the complaint anywhere else, is if anyone else is using the app & having the same issue.
I have pulled a logcat for the app, so I know it is not a SuperUser issue, but nobody else seems to be reporting the issue, so either it is working for other, or I am the only one using GMD Gesture Control on the Galaxy Note 8.
Anyone else using this app & either having this issue?
GSLEON3 said:
I love the GMD apps, including S-Pen Control & Gesture Control. I only use the S-Pen when I am writing or marking up drawings, occasionally when editing pictures, but by far, most of the time I navigate by hand.
I have used Gesture Control on numerous tablets & devices including the Nexus 10, Note 2, Note 10.1 & now the Note 8. It has worked flawlessly for the most part on every device I have used aside from the Note 8.
I have contacted the developer about the issue, which is that the "Back" function fails because the InputDispatcher drops the call. "Back" works fine using GMD S-Pen Control, but not on Gesture Control.
What I am wondering, since I don't see the complaint anywhere else, is if anyone else is using the app & having the same issue.
I have pulled a logcat for the app, so I know it is not a SuperUser issue, but nobody else seems to be reporting the issue, so either it is working for other, or I am the only one using GMD Gesture Control on the Galaxy Note 8.
Anyone else using this app & either having this issue?
Click to expand...
Click to collapse
I have been having the same issues. I thought it was me or another app. I have the same two GMD apps. S-Pen no issues. Gesture Control "Back" is hit or miss most to the time miss.
same problem
GSLEON3 said:
I love the GMD apps, including S-Pen Control & Gesture Control. I only use the S-Pen when I am writing or marking up drawings, occasionally when editing pictures, but by far, most of the time I navigate by hand.
I have used Gesture Control on numerous tablets & devices including the Nexus 10, Note 2, Note 10.1 & now the Note 8. It has worked flawlessly for the most part on every device I have used aside from the Note 8.
I have contacted the developer about the issue, which is that the "Back" function fails because the InputDispatcher drops the call. "Back" works fine using GMD S-Pen Control, but not on Gesture Control.
What I am wondering, since I don't see the complaint anywhere else, is if anyone else is using the app & having the same issue.
I have pulled a logcat for the app, so I know it is not a SuperUser issue, but nobody else seems to be reporting the issue, so either it is working for other, or I am the only one using GMD Gesture Control on the Galaxy Note 8.
Anyone else using this app & either having this issue?
Click to expand...
Click to collapse
Works intermittently, seems to be very dependant on what app is open ie: greader pro, can three finger back from read article to summary list 90% of times but get zero response while on summary page, should return me to desktop but just flashes 'back' indicator but no flash from capacitive buttons and no action occurs.
Terry
I have the same issue. I created a custom gesture of one touch point DL and that almost leads registers. The default three touch swipe down doesn't work so I disabled it the created a customer gesture to do the same thing. It works intermittently. I contacted the developer to let him/her know. I followed the directions as well om the FAQ on his website regarding SuperSU.
Sent from my GT-N5110 using XDA Premium HD app
I've been having this issue as well.
It's not only the gmd app, but I changed my dpi in build.prop to enable tablet mode when I disabled the capacitive buttons and the back button on the nav bar acts the same way.
Must be a bug in the firmware I guess.
wrangla said:
I've been having this issue as well.
It's not only the gmd app, but I changed my dpi in build.prop to enable tablet mode when I disabled the capacitive buttons and the back button on the nav bar acts the same way.
Must be a bug in the firmware I guess.
Click to expand...
Click to collapse
I am seeing the same issue as well. Any response from the developer yet? Should I also reported the issue to the development?
I had the same problem. For me, activating "Evaluate gestures only on release" in "settings" and restarting ("Restart Service") solved the issue.
Gesendet von meinem GT-N8010 mit Tapatalk 2
griesbau said:
I had the same problem. For me, activating "Evaluate gestures only on release" in "settings" and restarting ("Restart Service") solved the issue.
Gesendet von meinem GT-N8010 mit Tapatalk 2
Click to expand...
Click to collapse
I just tried the same but no luck. Did restart the service and everything but still experiencing the same intermittent "back gesture not working" issue. It doesn't seem to be dependent on the app being used. I sometimes keep trying and repeating the gesture and sometimes it eventually works. Tried all that superuser and supersu but to no avail.
Hope developer knows how to fix it.
Thanks for the pointer anyway.
griesbau said:
I had the same problem. For me, activating "Evaluate gestures only on release" in "settings" and restarting ("Restart Service") solved the issue.
Thanks for the tips, seems work for me as well .
Sent from my GT-N5110 using xda premium
Click to expand...
Click to collapse
+1
Any news on this? Setting the evaluate option seems to improve it a bit, but still more than 50% of my back gestures are not evaluated
Gesendet von meinem GT-N5100 mit Tapatalk 2
As I need another languages to type, I have to use 3rd party keyboard apps such as smart keyboard, go keyboard or multiling keyboard.
However, from JB stock, those software keyboards stay on screen with slid out hw keyboard. This is really annoying, but I didn't find any way to mitigate this. Weird thing is that google/stock keyboards don't have this problem, only 3rd party apps are impacted.
Also, CM10 and stock ICS don't have this symptom, only stock JB is problematic. Not sure whose fault is this, but obviously some mismatch is happening around keyboard...
Even the swype in the market is bad, pre-installed swype is working as expected...
I have gestures enabled on my mix 2s and I love them. So much more screen real estate to play with. However I find they interfere with gesture typing (eg: Swype or Gboard). In particular the 'p' is very difficult to swipe when a word starts with it. Anyone got a workaround for this? The MIUI back gesture (swipe) from edge really should only apply to the top 2/3 of the screen.
I also experience the same thing. I've just decided not to swipe close to the edge when typing
Sent from my Mi MIX 2S using Tapatalk
Does your keyboard closes while typing? Could be because of this: https://forum.xda-developers.com/xiaomi-mi-mix-2s/help/miui-im-swiping-t3803874
wineds said:
I have gestures enabled on my mix 2s and I love them. So much more screen real estate to play with. However I find they interfere with gesture typing (eg: Swype or Gboard). In particular the 'p' is very difficult to swipe when a word starts with it. Anyone got a workaround for this? The MIUI back gesture (swipe) from edge really should only apply to the top 2/3 of the screen.
Click to expand...
Click to collapse
When I bought this phone immediately noticed this issue, specially annoying when I try to use swipe writing. I suspected that occurs because the system doesn't know if your are trying to write using the keys located at the edges of the screen like q, p, etc. or just using gestures. As a workaround I tried to adapt the keyboard using the one handed mode feature (Google keyboard) then moving it to the center of the screen and it worked, the lag disappears and no more false back gestures that closed my keyboard. You can see the screenshot attached.
Let me know if it worked for you.
rodaven said:
When I bought this phone immediately noticed this issue, specially annoying when I try to use swipe writing. I suspected that occurs because the system doesn't know if your are trying to write using the keys located at the edges of the screen like q, p, etc. or just using gestures. As a workaround I tried to adapt the keyboard using the one handed mode feature (Google keyboard) then moving it to the center of the screen and it worked, the lag disappears and no more false back gestures that closed my keyboard. You can see the screenshot attached.
Let me know if it worked for you.
Click to expand...
Click to collapse
How do you set the google keyboard to one handed mode?
vince_junior said:
How do you set the google keyboard to one handed mode?
Click to expand...
Click to collapse
Long press the comma button and slide to the one handed mode toggle.
rodaven said:
When I bought this phone immediately noticed this issue, specially annoying when I try to use swipe writing. I suspected that occurs because the system doesn't know if your are trying to write using the keys located at the edges of the screen like q, p, etc. or just using gestures. As a workaround I tried to adapt the keyboard using the one handed mode feature (Google keyboard) then moving it to the center of the screen and it worked, the lag disappears and no more false back gestures that closed my keyboard. You can see the screenshot attached.
Let me know if it worked for you.
Click to expand...
Click to collapse
Excellent work around thanks!
This is by far the most annoying thing I've come across with this phone! Strange. I tried the draw app test rapidly tapping between the sides and got so many false swipes it was crazy. Hopefully the sensetivity can be adjusted in a future update. Xiaomi seems to be pretty good with updates so far.