Related
Ok, I cannot find anything related to my problem, and I CAN`T be the only one with this.
First things first: My name is Lane, long time lurker, first time poster. I have a P-3113 GTab2 7", stock rooted JB 4.1.2, and a IVSO bluetooth keyboard case. Over the last week, I've been trying to find a way to hide the soft keyboard while using the BT keyboard. I started with "Null Keyboard", but all it did was get rid of the keyboard entirely. I still like using the soft keyboard when I need it in a pinch. I don't like having to switch manually. Then I found AnySoftKeyboard, which i freakin' love.
But now i have a problem.
When the default keyboard is set to AnySoft (or any other keyboard for that matter), i can use it and its wonderful features for a total of 5-10 minutes before Android complains and throws up an error message, then switches the default keyboard back to Samsung... I even caught a screenshot of the error just now. You can see AnySoftKeyboard in the screenshot behind the message, but then it switches to the Samsung keyboard.
Lka1988 said:
Ok, I cannot find anything related to my problem, and I CAN`T be the only one with this.
First things first: My name is Lane, long time lurker, first time poster. I have a P-3113 GTab2 7", stock rooted JB 4.1.2, and a IVSO bluetooth keyboard case. Over the last week, I've been trying to find a way to hide the soft keyboard while using the BT keyboard. I started with "Null Keyboard", but all it did was get rid of the keyboard entirely. I still like using the soft keyboard when I need it in a pinch. I don't like having to switch manually. Then I found AnySoftKeyboard, which i freakin' love.
But now i have a problem.
When the default keyboard is set to AnySoft (or any other keyboard for that matter), i can use it and its wonderful features for a total of 5-10 minutes before Android complains and throws up an error message, then switches the default keyboard back to Samsung... I even caught a screenshot of the error just now. You can see AnySoftKeyboard in the screenshot behind the message, but then it switches to the Samsung keyboard.
Click to expand...
Click to collapse
It is an error i might recognize.. Does it happen with ny other keyboard too??like swift key or ny other that stock??
If you get prob just in AnySoft then its the problem in programming made by the app developer,
if other keyboards crash too then i guess its the problem in your rom.. Did you flash ny thing on your current rom??
Also,
Try using WIFI keyboard if you want no keyboard display while typing from external keyboards via usb
ROM is stock JB, just rooted. Nothing else flashed. This happens with other keyboards, too, like SlideIt, Null, and AnySoft.
As far as I know, this only happens when I have my bluetooth keyboard connected.
It is really not that hard to switch input methods between a BT keyboard and an onscreen keyboard, no app is needed to easily go back and forth between those two. There should be a notification that shows up to easily switch input methods when a text box is tapped.
It looks like the second line says "change BT input method to stock Samsung keyboard", if that's any help.
Attached is the said notification.
Sent from my GT-P3110 using xda app-developers app
blagginspaziyonokip said:
It is really not that hard to switch input methods between a BT keyboard and an onscreen keyboard, no app is needed to easily go back and forth between those two. There should be a notification that shows up to easily switch input methods when a text box is tapped.
It looks like the second line says "change BT input method to stock Samsung keyboard", if that's any help.
Attached is the said notification.
Sent from my GT-P3110 using xda app-developers app
Click to expand...
Click to collapse
He knows how to change the keyboard, but when he changes it , it reverts back to the stock one with the error shown in the attachment of OP
Lka1988 said:
ROM is stock JB, just rooted. Nothing else flashed. This happens with other keyboards, too, like SlideIt, Null, and AnySoft.
As far as I know, this only happens when I have my bluetooth keyboard connected.
Click to expand...
Click to collapse
if you use just stock keyboard, do you get the same error and the stock keyboard refreshes/reboots??
mhrsolanki2020 said:
if you use just stock keyboard, do you get the same error and the stock keyboard refreshes/reboots??
Click to expand...
Click to collapse
No, only when an alternate KB is set as default.
I really hate what Google have done to the keyboard in Lollipop. The predictions have been changed for the current word to show suggestions that aren't what you are trying to type, (if you are typing accurately.)
On the face of it, this seems to be a logical decision. In practice though, your eyes have to keep going upto your message to check what you have just typed is correct. You then have to go all the way down to the space bar to get the next word prediction. :silly:
Under the old system, if you were typing accurately, you would just press the middle button without your eyes ever having to go up and find where you are typing. This would then prompt the next word prediction without ever having to look upto the message or down to press the spacebar.
Is there any way to get the Kit Kat keyboard into Lollipop. (Its a deal breaker for me and could influence the Moto X 2014 vs Nexus 6 decision!)
See attached Kit Kat and Lollipop. In the example, I'm trying to type, "The."
I just tried your scenario and it seems to be working fine on Lollipop.
As soon as I type 'T', the Google keyboard suggests the word 'The'. If I tap on that suggestion it then suggests the next predicted word.
If I type 'Th', it still suggests 'The' as the predicted word, but it also highlights or bolds the suggested word, indicating that I can hit the space bar to accept the suggested word 'The'.
If I go ahead and type the whole word 'The' without selecting the suggested word after either of the first two times it suggested it, it assumes I didn't want the word 'The' after all and suggests a different word.
Is that not the behavior you're seeing?
StringerE said:
I just tried your scenario and it seems to be working fine on Lollipop.
As soon as I type 'T', the Google keyboard suggests the word 'The'. If I tap on that suggestion it then suggests the next predicted word.
If I type 'Th', it still suggests 'The' as the predicted word, but it also highlights or bolds the suggested word, indicating that I can hit the space bar to accept the suggested word 'The'.
If I go ahead and type the whole word 'The' without selecting the suggested word after either of the first two times it suggested it, it assumes I didn't want the word 'The' after all and suggests a different word.
Is that not the behavior you're seeing?
Click to expand...
Click to collapse
It is also what I see in Lollipop. Whilst it seems logical, when you are swiping, you only tend to check the word when you have finished a swipe. In KK, this mean't always going to the suggestion bar and confirming which also mean't insert space and then mean't next word please. Your eyes need almost no movement.
In lollipop however, when you have finished the swipe, your eyes have to go all the way upto the text, find where you typed and check it is what you wanted, then go all the way down to the spacebar and press it to ask for the next word suggestion.
It just means you can swipe so much faster on KK than you can on LP as your eyes are having to work alot less. :crying:
For me, the L version seems to be better at determining what I'm trying to swipe without me having to check it. I usually go ahead and swipe out the 2-3 sentences I want in my text/reply/post/whatever and then go back and verify it says what I wanted to say. And I've found it has been more accurate on L than it was on KK. Any incorrect words I see at that point I click on and the suggested replacement is usually what I wanted. If I verified each word as I swiped it would definitely be slower.
In other words, I rarely select the suggested words. I just swipe out what I want to say without looking up and then go back and verify before sending. And it's typically pretty accurate.
Is anyone seeing really bad lag while typing? Maybe I just type too fast but after I think I'm done with a word I look at the screen and it's still spelling it. I have vibrate on key press on, popup on keypress on and the text correction on.
kgry said:
Is anyone seeing really bad lag while typing? Maybe I just type too fast but after I think I'm done with a word I look at the screen and it's still spelling it. I have vibrate on key press on, popup on keypress on and the text correction on.
Click to expand...
Click to collapse
I've had no problems with keyboard lag and I'm using 5 on the Nexus 7 2013, (Which is a much slower device.)
IDK about Swype type input but tapping is worse with white on white keys. I fixed it by switching to the older theme. I realized my eyes play a part in my accuracy apparently because muscle memory isn't enough. It's weird.
MrObvious said:
IDK about Swype type input but tapping is worse with white on white keys. I fixed it by switching to the older theme. I realized my eyes play a part in my accuracy apparently because muscle memory isn't enough. It's weird.
Click to expand...
Click to collapse
It's good that Google gave you the choice to switch back to the old keyboard look. I just wish Google would give me the option to switch back to the kit kat swipe functionality. I can't buy a nexus 6 until they fix this!
I faced the problem on android 5.0, did they solved on 5.1?
McGyver dei poveri said:
I faced the problem on android 5.0, did they solved on 5.1?
Click to expand...
Click to collapse
The keyboard still sucks in 5.0.2
I don't think 5.1 is out yet?
It's out but not for my note3... Only the LG keyboard is as fast and comfortable as this for me. A part the autocorrection problem, they also removed the option to remove the "change language button" it wastes space for nothing... Bah..
For example now I'm typing on the forum and I have to watch the super small text in the forum box ... I'm a lot slower than before that was in the center of the keyboard, and ofc I make more mistakes... Silly choice by google's engineers
For example now I'm typing on the forum and I have to watch the super small text in the forum box ... I'm a lot slower than before that was in the center of the keyboard, and ofc I make more mistakes... Silly choice by google's engineers
Click to expand...
Click to collapse
Exactly the problem I have. If Google don't sort it out in 5.1 I'm staying on kit kat for sure. I get what Google were trying to achieve but they need the option to do both kk and lollipop prediction methods.
Personally I hate it. I have had to type words like "complaint" dozens of times over even though my swiping technique hasn't changed because the software thinks I'm trying to type "composition". Now, mind you, I swipe over to the A and there is no A in "composition".
Any news from android 5.1?
McGyver dei poveri said:
Any news from android 5.1?
Click to expand...
Click to collapse
No change.
Argh!!! That really sucks. Looks like it's staying on kk for me. :crying:
Would be nice if someone could hack the Google keyboard :angel:
Just an update for people having the same issue as me in Lollipop.
On the Play store, there is an app called Jellybean Keyboard 4.3. :highfive:
This app pretty much gets around my issue with the Google Keyboard and has worked fine for the last week I've been testing it with only a few niggles:-
- Emotions requires a separate download.
- When the app updated a few days ago, it forgot what it had previously learned.
I still dont understand why Google Keyboard cant contain a tick box in the settings entitled, "Include typed word in suggestion box in Lollipop." :crying:
Oh dear god. I tried Lollipop once on my N4 - it was awful. Now I plan to switch to 5.1 and see how it is one more time (and check if there is better battery life) but that keyboard abomination still scares me and its sad to know that it still persists...
However I'll try to live with that - at least for one day - cuz I wanna try EuphoriaOS tommorow Maybe I'll try to install Google Keyboard from 4.4.4... Somehow.
Just go for the jellybean keyboard as above. :angel:
The other day I softbricked my phone and spent hours trying to get it back. I was lucky enough to get back using Smart Switch to restore firmware, but it installed 5.1.1. Whatever, I'm living without root.
However, I noticed since then that I can no longer double tap on a word to select it. I have to long press on a word to highlight it. Anyone else experience this? Kind of annoying. I was so used to the double tap.
Finally, someone else noticed. I noticed the same thing. Ever since I updated to 5.1.1 on my s6, double tap to highlight is completely gone. Very annoying
supernaru428 said:
Finally, someone else noticed. I noticed the same thing. Ever since I updated to 5.1.1 on my s6, double tap to highlight is completely gone. Very annoying
Click to expand...
Click to collapse
What both of you mean? I have the 5.0.2 version and when I double tap some text it just zooming in, where does it highlight something?
When you're texting for example. Double tap any word you entered, and it will highlight and allow you to copy it or remove it.
JusTeN_ said:
What both of you mean? I have the 5.0.2 version and when I double tap some text it just zooming in, where does it highlight something?
Click to expand...
Click to collapse
supernaru428 said:
When you're texting for example. Double tap any word you entered, and it will highlight and allow you to copy it or remove it.
Click to expand...
Click to collapse
This. Sorry, I should've clarified that I meant when you're typing. Not just any text.
Yep, annoying as hell.
On a good note, though, now you can long press to highlight the word and then just swipe the new word and it replaces it. Prior to 5.1.1 it would not replace it with the new word, it would only grab letters from the new word that were not in the previous word and replace it with those letters, which was even more annoying and made absolutely no sense.
daewond3r said:
This. Sorry, I should've clarified that I meant when you're typing. Not just any text.
Click to expand...
Click to collapse
Oh, actually I use long press to highlight something, not double tap.
has anyone had any progress or a workaround for this issue? It's killing me - I've used this feature for years.
Swype's website still says that double tapping a word should select it. I tried other keyboards and none of them allowed me to double-tap select anything but I do not know if they supported double-tap select before the update. I'm also curious whether this applies to all devices or just Galaxy S6.
Pretty annoying.
deepfryerdan said:
has anyone had any progress or a workaround for this issue? It's killing me - I've used this feature for years.
Swype's website still says that double tapping a word should select it. I tried other keyboards and none of them allowed me to double-tap select anything but I do not know if they supported double-tap select before the update. I'm also curious whether this applies to all devices or just Galaxy S6.
Pretty annoying.
Click to expand...
Click to collapse
We're talking about the stock Samsung keyboard.. which is not Swype. So what Swype says, doesn't matter lol
ingenious247 said:
We're talking about the stock Samsung keyboard.. which is not Swype. So what Swype says, doesn't matter lol
Click to expand...
Click to collapse
Obviously the problem is bigger than just the Samsung keyboard. Samsung's site doesn't say anything about double-tapping to select text whereas Swype does mention it. So, what Swype says is very relevant to this conversation because it proves that the problem is not with the keyboards, it's with Android. lol
deepfryerdan said:
Obviously the problem is bigger than just the Samsung keyboard. Samsung's site doesn't say anything about double-tapping to select text whereas Swype does mention it. So, what Swype says is very relevant to this conversation because it proves that the problem is not with the keyboards, it's with Android. lol
Click to expand...
Click to collapse
Wish they hadn't changed it. double-tap is faster (to me) than long-press.
At least I've got a workaround.
deepfryerdan said:
has anyone had any progress or a workaround for this issue? It's killing me - I've used this feature for years.
Swype's website still says that double tapping a word should select it. I tried other keyboards and none of them allowed me to double-tap select anything but I do not know if they supported double-tap select before the update. I'm also curious whether this applies to all devices or just Galaxy S6.
Pretty annoying.
Click to expand...
Click to collapse
Don't know if you have this issue fixed, but it happens the same here with Note 4. Very annoying indeed.
Well, it works for me, both with Samsung's keyboard and SwiftKey.
Sent from my SM-G920I using Tapatalk
Left Samsung after Note 2 and came back to the S9 and yeah, it's annoying... My Android/Huawei phone didn't have this problem.
This is driving me crazy & I can't believe there's no fixes online! Upgrading from my Galaxy S3 of 3yrs to a GS7, so Kitkat to Oreo, & just whyyy did they nix the "double tap to select text typed"?? Siighh.. ;(
There MUST be a way to re-enable it..
Yeah, it's 2021 already yet Samsung still hasn't managed to fix a bug it introduced (many!) years ago.
If Samsung doesn't really know how Android works, we can only hope our devices don't just blow up one day as a result of Samsung's pure reliance on trial and error.
To be clear, it is stated by Android spec that while in a text field, upon a double-tap a word gets selected; hence current behavior is called a bug as the functionality is simply not there
Pretty much what the title says. My Samsung S6 is set up to use the Google keyboard and the Google Now launcher.
I'll receive a notification for a message, tap the notification, then hold my finger over the scanner to unlock and go directly to the app that notified me.
The phone unlocks fine, and I'm taken directly to the app (usually Facebook or SMS)
Normally, the first thing I'll want to do is reply to the message for which I was notified, so I'll tap in the text field but receive no response. It sometimes takes several seconds for the phone to respond and display the Google keyboard. This doesn't occur with the Samsung keyboard.
Has anyone else experienced this, or have a fix?
Luefox said:
Pretty much what the title says. My Samsung S6 is set up to use the Google keyboard and the Google Now launcher.
I'll receive a notification for a message, tap the notification, then hold my finger over the scanner to unlock and go directly to the app that notified me.
The phone unlocks fine, and I'm taken directly to the app (usually Facebook or SMS)
Normally, the first thing I'll want to do is reply to the message for which I was notified, so I'll tap in the text field but receive no response. It sometimes takes several seconds for the phone to respond and display the Google keyboard. This doesn't occur with the Samsung keyboard.
Has anyone else experienced this, or have a fix?
Click to expand...
Click to collapse
I also have this issue. I thought locking the keyboard in the memory would resolve it but nope. No idea what causes it. I managed to fix it a while back but I have no idea what I did that fixed it.
Luefox said:
Pretty much what the title says. My Samsung S6 is set up to use the Google keyboard and the Google Now launcher.
I'll receive a notification for a message, tap the notification, then hold my finger over the scanner to unlock and go directly to the app that notified me.
The phone unlocks fine, and I'm taken directly to the app (usually Facebook or SMS)
Normally, the first thing I'll want to do is reply to the message for which I was notified, so I'll tap in the text field but receive no response. It sometimes takes several seconds for the phone to respond and display the Google keyboard. This doesn't occur with the Samsung keyboard.
Has anyone else experienced this, or have a fix?
Click to expand...
Click to collapse
Clear the app data for Google Keyboard. That seems to have fixed it for me.
hillbeast said:
Clear the app data for Google Keyboard. That seems to have fixed it for me.
Click to expand...
Click to collapse
This works for me temporarily, but it's usually within a day or two that the keyboard becomes slow to respond again.
If left alone for long enough without clearing the data, it becomes slow to respond just switching between apps too.
Hi guys.
My keyboard has been pushed upward after Android 10 update and it's irritating the hell out of me. Same no matter using Google or SwiftKey. Already tried changing the preferences and layouts of the keyboard but this is the lowest I can go. Is there a setting I can change? Thanks in advance
https://drive.google.com/file/d/10lKplzPWdWTTwIqWrjnel3wL-6mSiBu_/view?usp=drivesdk
Facing the same issue
I downgraded to Android 9.0 solely because of this.
It's in design. The idea is to place it in the same space as if there were navigation keys. Actually I like it a lot myself, when I used the gestures in android 9 I kept missing keys because the keyboard wasn't in the place I was used to (but that's just me)
Blackherted said:
It's in design. The idea is to place it in the same space as if there were navigation keys. Actually I like it a lot myself, when I used the gestures in android 9 I kept missing keys because the keyboard wasn't in the place I was used to (but that's just me)
Click to expand...
Click to collapse
It's not a joke getting millions of users to retrain their muscle memory over and over again. Just give us a bloody option. Fml.
ImperatorShade said:
I downgraded to Android 9.0 solely because of this.
Click to expand...
Click to collapse
Was there anything else dissatisfying in Android 10? I'm currently considering to update & desperately want to hear/read other people's opinions on the matter.
Same issue here, but actually I think I like it, at least in portrait mode, since these phone keep getting taller an taller, the new position for the keyboard with this "invisible" bar it's actually more comfortable, doesn't look that good but meh, in the other hand, it is hell of an issue in landscape mode!
ImperatorShade said:
I downgraded to Android 9.0 solely because of this.
Click to expand...
Click to collapse
I havent updated myself, can u give some instruction on how to revert to pie
If it's that annoying, you could try the google gboard floating keyboard app, then you can move it around to wherever you want it to be.
wmunn said:
If it's that annoying, you could try the google gboard floating keyboard app, then you can move it around to wherever you want it to be.
Click to expand...
Click to collapse
No
X4R said:
No
Click to expand...
Click to collapse
That's not much of a response to go on, can you elaborate? or do you just not like change of any kind?
wmunn said:
That's not much of a response to go on, can you elaborate? or do you just not like change of any kind?
Click to expand...
Click to collapse
It does not work like that. The gap is not usable. Not way to put anything on top of this part of the screen. Just wanted to inform you that it is not possible to make the keyboard float there
The gap is totally a waste. I used to type anytime by swiping and then clicking the enter key, which would be just in the bottom right corner of the device, so i didn't need to actually look at the keyboard while typing. I could just feel the corner of the screen and then my hand would automatically tap on the enter, but now no longer. There's just a useless, ugly black border there.
Also, in Google Chrome, you type something in the address bar, but accidently touch that black bar, it closes the keyboard and everything you typed just get cleared.
The struggle is real my dude. I found an adb command to correct the issue. It works fine until I notice it changes the height of the screen and stretches it out. Now there are buttons I cannot see because they are off the screen. If they don't make this "feature" optional, I might have to just decide to deal with the gap. Other than that, I like android 10.
This gap annoying me too
The gap is one of those reasons why I don't update to Android 10! ?
pycxe-01 said:
The gap is one of those reasons why I don't update to Android 10! ?
Click to expand...
Click to collapse
Attached my screenshot of OpenBeta 5 Android 10 and swift key
strongst said:
Attached my screenshot of OpenBeta 5 Android 10 and swift key
Click to expand...
Click to collapse
What happens if you would remove those arrows & disable "Back, Home, Recents" buttons?
Here's my screen from Android 9:
pycxe-01 said:
What happens if you would remove those arrows & disable "Back, Home, Recents" buttons?
Here's my screen from Android 9:
Click to expand...
Click to collapse
I think if the keyboard will be more near the bottom, the keys on the outside will be rounded, which makes them smaller
For me it fixed after changing gestures settings to 3-button type
yes, but we don't want to use on screen buttons, but gestures..