What's up, guys? I searched but I couldn't find a related topics to my question.
I've been on CM9 for about 2 days now & I'm having problems with Google Voice. It seems that it's delaying notifications for my texts. I have to manually go into the app & check if I've received any. I've checked all the settings on CM9 & in the voice app with no results. Occasionally, it'll push the texts, but it's not consistent.
Another thing is the physical keyboard. For the "fn" button, I have to toggle instead of pressing it once & pushing the character I want. Same thing goes for the "shift" key. If I press it once, it stays on CAPS LOCK.
I was on cleanGB before this & I had no problem with it. I just decided that since RC1 was released, a lot of bugs would've been worked out, so I decided to give CM9 a try. It's still a cool ROM, though.
I don't have a "task killer" or any of that stuff, so I can't see what the problem is. I was wondering if anyone else is experiencing any of this or if there is a fix?
Sent from my SPH-D700 using xda app-developers app
I've also been having issues with the GV app not updating consistently for the last 1-3 months. Also had a few calls not route to the phone, and lots of other problems. It's a bummer but I'm leaving GV and going back to standard SMS.
Hey - not sure if this is the right place to put this as I had the same issues with the Swiftkey app on my Galaxy s2. The problem I have is intermittent.
If i go into my messaging, or email app or WhatsApp - the keyboard appears as normal however when typing on it - nothing appears at all in the text field. I have to quit to homescreen 2 or 3 times and then go back into messaging and start typing for anything to appear.
Also sometimes what happens is that the keyboard will appear and will type as normal however the top line above the keyboard which contains the predictive words won;t appear - again the resolution is to quit the messaging app that i'm in and return to it. Really frustrating at times - esp when I can't type a message!
Does anyone else have this problem? I've updated to the latest swiftkey.
I'm running stock ROM however i've rooted the handset but the problem was happening before rooting too.
Any suggestions would be welcome - apart from that i'm loving the handset.
Not sure if it's just my luck, but one thing I've noticed is when typing in a login field it clears randomly. Using stock keyboard and CleanRom currently. Happens in stock as well. Only thing that I can find to get around is getting my email added to the dictionary prediction field and swiping it in. Is it just me? Basically I type out s-h-a-m-p-o-o *bam, cleared*. Sometimes I get through a couple more letters, sometimes I don't. It's a bit frustrating.
Any one else or any ideas?
I'm using thumb keyboard on my n5110, stock android 4.1.2. Sometimes while typing the keyboard disappears. Other times the cursor jumps around on the page instead. Sometimes both.
The weird thing is that this is my 2nd Note 8 and it never happened on the first one. I exchanged it and the second Note is perfect in every way except this keyboard issue. Could it be a hardware issue? I'm guessing no but it's weird that it never happened on the first device.
I've switched to SwiftKey now and to see if it happens with other keyboards. It happens infrequent enough that I'll have to use it for a while to be sure.
Can you tell me what you were doing? I own thumbs keyboard and I can try to recreate it if you want. Ive happily switched to SwiftKey but I do appreciate the features of thar keyboard.
Sent from my GT-N5110 using Tapatalk 4
I am using Opera as my browser and the OS is 10.0.16.HD65AA. Often when I start typing a long post into an edit window of Opera the input frezzes. That is I am still typing on a GBord, it shows me suggestions for misspelled words, I can backspace and I see text changing in the keyboard's suggestion row, but... text in the text input field is not updating.
I have to wait around 10 seconds for it to unfreeze and update, often I have to click somewhere in the middle of the earlier writen text to force update within the same 10 seconds. I have already tried to switch off non-essential options of gboard like spell checking to no avail.
This is not new, I remember I had the same on my previous Pixel. It just stopped to happen at some point, I just don't remember what has triggered the change. Any leads maybe? Am I alone with the problem?
Does your whole phone freeze or only the browser?
I have a similar problem with Vivaldi, I normally just switch to the homescreen and back to the browser to unfreeze it immadietly.
It probably is problem with the app not the phone, you could try testing a different browser Firefox/Kiwi for example.
lilmonkehfellah said:
Does your whole phone freeze or only the browser?
I have a similar problem with Vivaldi, I normally just switch to the homescreen and back to the browser to unfreeze it immadietly.
It probably is problem with the app not the phone, you could try testing a different browser Firefox/Kiwi for example.
Click to expand...
Click to collapse
Not even a browser, I can still scroll the page. That is only input text field doesn't update.
You should test a different browser just to isolate the cause, you could also try to use a different keyboard app swiftkey for example and see if the issue persists.
lilmonkehfellah said:
You should test a different browser just to isolate the cause, you could also try to use a different keyboard app swiftkey for example and see if the issue persists.
Click to expand...
Click to collapse
This defeats both the purpose and the experiment. But I have tried it. Using any other browser is simply a nightmare obscuring the initial problem: all that panning and scrolling, random moving of input controls etc basically forces mistypes which is the way to unfreeze Opera in the first place. Honestly I don't know how people are using other browsers on Android if they have to write texts there.
Anyhow, the same problem exists in FF and Chrome. It is just not the biggest of their problems, so bothers less.
The main point here: I really had the same issue on Pixel and it has disappeared somehow, I don't remember how unfortunately. So I know it is possible to get rid of it. My question was: probably someone knows how.
Problem is solved with Android 11 FW.