I have opera and Dolphin installed in extended memory. For some reason when I go to an email provider like gmai! Or I need to fill something like writing this, when I tap the screen to get the keyboard it doesn't matter come up. Sometimes it will resize. Other times it just flashes blue and refuses to do anything. Any thoughts?
I don't want to be rude, but we could use a little more information. Are you stock, custom GB, or HC? When was it last working, if ever? Any recent downloads? Any changes or tweaks to any settings? Have you downloaded a new keyboard replacement, etc?
Forgive me. Completely stock best buy flyer. I do have SwiftKey and graphetti installed, you Graphetti won't come up at all. Recently crashed device installed everything I could in extended memory.
Everything worked before crash except sometimes some apps wouldn't load, sometimes I would get out of memory errors and sometimes the keyboard would get a mind of its own and display multiple letters for each letter I would type.
I believe Swiftkey has to be purchased after a certain number of days (14) or it stops working (at least the tablet version). I have used graffiti going all the way back to the days of my apple newton. For graffiti, there is no free edition, so that should not be an issue. I had graffiti installed but did not like it. You probably already did this, but swiftkey won't work unless you go through the five steps. You activate those either in settings or in the apps folder by selecting it. Graffiti also needs prior steps before it works. Does the standard keyboard still work when you select it?
You need to use SwiftKey x for tablets on the Flyer. The phone version is not supported and does not function properly.
Related
I have a Sprint Touch Pro 2 with stock WM6.5 ROM.
When I type in Opera Mini (say posting a forum message), after a while pressing a space bar (or a comma / period sign) starts erasing the previous word. This is very repeatable. Also once it starts happening, it affects any other keyboard, including the hardware one.
At first I thought it was related to FingerKeybd, so I yesterday uninstalled it and jumped through some hoops to get my English ROM device to type in two languages using HTC native keyboard. However, it appears the bug is still there, although in a modified version - now pressing space erases letter "I" only.
The problem is only with Opera Mini - I can type anywhere else with no issues. I also have a strong suspicion that it's somehow related to suggested words option being turned on, however I use this feature and don't want to give it up.
I did submit a bug to Opera team but it was immediately dismissed as something specific to my particular unit.
I am curious if anyone else had this problem... surely I can't be the only one !
I have the same problem. Thats horrible.
Same problem here. I have autocomplete turned off but it's still happening. It will also erase "ierd" if you type wierd but won't erase it if you type starting with another letter. The crazy thing is it cleared up for a while until I did a hard reset and erased the "fix".
I don't have this bug anymore. I think it may be related to TF3D (Sense). I stopped using Sense several months ago - got tired of lags and memory issues, tried Titanium and never looked back. This seems to have also fixed my Opera keyboard issue, somehow. I've been through many hard resets (trying different things, screwing up, hr to get back to basics) and so far no issues with keyboard. It may be not related as much to Sense as to CHT running on top of it; don't know - try switching to Titanium and see if that helps.
I used to use mini 4.2 and really liked it, but couldn't use the newer versions because the keyboard is just too buggy. I don't really remember what the keyboard did, I just remember that typing was nearly impossible. I use Resco for my sip.
I had the same thing, search Opera mini forum for "kuifje_opera". It turned out to be the autocorrect feature.
i dont face this problem.. perhaps try reinstalling it, + delete cache files? works fine for me! what about in you HW Keyboard, any problems there?
same
Same problem on rx3115 ROM 1.01.11a.
wm2003SE
any fix?
Try to use Opera mini 5 beta. From my experience with opera mini for about year I can say that the previous beta version i more stable and there are few problems on the rendering of sites and keyboard input in text fields compare to latest 5.1 version. The only thing I do not like in beta version is no so smoothly scrolling vs 5.1.
It is not a Opera problem. Here is what I did and get rid off it:
- Open Start Menu
- Go to: Settings>Personal>Input
- Now you are in Input Method, from the tabs above click Word Completition and uncheck everything there. Now go on the tab Options (on the right) and uncheck Capitalize first letter of the sentence and Scroll upon reaching the last line.
- Click OK (bottom right) and exit the Start Menu.
- Thats it!
This is what I did and solve the same problem, now everything is great when typing texts.
I am using Windows Mobile Pro 6.5.3, so I don't know if it's gonna work on 6.0, 6.1 or 6.5, but considering that this is an all WinMo option, I think it would work on any WinMo OS. Try it, you ain't gonna screw anything
Cheers.
i haven't had a chance to try it on my NC yet, but i think we might now be official.
http://stage3-beta.swype.com/android/supported/
I'm installing the update now i will tell you if it works.
ngrenn35 said:
I'm installing the update now i will tell you if it works.
Click to expand...
Click to collapse
Thanks! Don't forget to include what ROM you're running.
Honeycomb build 4 not working w swype
I installed todays swype and i can tap out words but not swype. I know i am using the right keyboard because it does trace but the words wont display.... Honeycomb build 4.
Works great for me on CM7 v14
It looks great but I can't actually use the swype function, like the poster before said.
Running CM7 and when I swype the border flashes blue but no word appears. Otherwise, it's nice to see some large screen support from Swype. I love it on my Vibrant
Doesn't work for me (NF 0.6.8.3). I can type but can't Swype.
It worked for a second then quit, cm7 v14 Keyboard is nice for fat fingers. Soo close.
I have phiremod v4.1 and the swype does as the others said; I can see the keyboard and the swpe gestures, but no words appear, I can tap them out as with the regular android keyboard, but swyping does nothing. It does make a noise after a swype gesture though.
Also when I put the NC in landscape view, the skype app takes up the entire screen.
still not able to try on my NC, but when swype does that behavior on my nexus one, if i switch to the android keyboard then back to swype through the input method selector, everything works great.
fzr-r4 said:
still not able to try on my NC, but when swype does that behavior on my nexus one, if i switch to the android keyboard then back to swype through the input method selector, everything works great.
Click to expand...
Click to collapse
You may well be my hero. I can't confirm that it worked for sure, as it threw a licensing fit since I used it on HC instead of CM7, so I'll revert back to HC and try this again. The licensing fit never occurred until I tried what you suggested.
Tried that method of switching to Android KB and back, still didnt work for me, same as everyone else.
I'm getting the same results on CM7 v17. I'm also getting a message that says swype is configured for another device and may not work correctly when I first switch over to it.
g
Boinky said:
I'm getting the same results on CM7 v17. I'm also getting a message that says swype is configured for another device and may not work correctly when I first switch over to it.
Click to expand...
Click to collapse
yeah, shoot, me, too. eMMC Honeycomb 2nd edition.
Sent from my Nexus One using XDA App
I have read in another thread that Nookie Froyo tends to spout random IMEI numbers when an app asks about the device it is installed again. Swype authenticates the beta by IMEI and you are limited as to how many IMEIs you can install it on. Thus the licensing problem - install Swype and it locks itself to the reported IMEI. Then run it again, and it thinks it's installed on another device.
Licensing errors
I'm also getting licensing errors but the keyboard does appear to load correctly on, CM7 #17,
damn. Was so excited too. Wont swype. Have been dying to put it on my NC, typing on this thing sucks.
Sometimes the betas get hacked (but no posting warez here!) so they are not IMEI locked anymore. Unless we can figure out a way to report a stable IMEI on the NC across all firmwares per device, that may be our best bet .
Will try when the WSVGA will be supported in french..
Yes I can confirm what is being said here about the IMEI... Definitely the root cause here as reported on the swype official forums.
The way I see it, this can be worked around without the need to hack the Swype package. My understanding is all we need to do is spoof the telephony stack a little better, so that the IMEI is consistent. I am at work so I cannot do too much to find out how hard that would be.
android API call for getting IMEI is
android.telephony.TelephonyManager.getDeviceId()
First step would probably be to override this function and just report to logcat to confirm the Swype Licensing process (Would have to check both "Swype installer" and "Swype" applications this way, full end to end install process) calls that function to retrieve the IMEI instead of using another method.
Then if that works, override the function to return a static number. Does anyone know if the IMEI can be used to reverse lookup manufacturers and devices models the same way MAC addresses can? If so, we may need to carefully pick the number returned so that if Swype does a reverse lookup it thinks we are using a valid device - Such as Galaxy tab, which I believe is functioning under the latest beta.
I am definitely not an expert android dev, I barely understand this stuff so far. Just hoping to get the conversation started because I'd really like to swype.
So I was all rooted. I had Go Launcher, Market, and Swiftkey all working awesomely. My NT life was good. Then Swiftkey started throwing up errors. So I went to Any Cut to find a shortcut to Swiftkey's settings. There was like 8 settings under activities but not a specific Swiftkey settings. So I created shortcuts to the 8 settings and thought I would try them all and maybe one was for swiftkey.
When I clicked on the second settings shortcut the NT through up an error that stated there was an authorization error and the tablet would reset. When the tablet restarted it forced a wipe to factory settings. I thought...that sucks...but whatever I'll start over.
When the tablet had finished and restarted It started to go through the setup screens as one might expect. However, Swiftkey is apparently still selected as the keyboard and the NT keeps giving the Swiftkey force close errors. I can't enter in my registration info because I haven't an effin' keyboard. I didn't have usb debugging turned on so I don't think I can use adb to remove swiftkey. Although, I've never really used ADB unless I'm rooting and following very specific instructions from one of these forums.
Is there a way to bypass the initial registration and sign in crud so I can install root explorer and remove Swiftkey?
Sorry for the long story. Hopefully someone will have a suggestion on how to fix this.
Thanks in advance.
tldr- NT hard reset and now stuck without keyboard because Swiftkey was still selected and Swift key won't work during initial registration....argh!
Tip the screen corners starting top left in clockwise motion.
http://nookdevs.com/NookColor_Factory_Mode/Skip_Out_of_Box_Experience
This has worked for people to skip registering their device good luck god bless.
I did test this method when i got t the last prompt to skip Oobe(out of the box experience) I did get a force close error. However I just reopened the menu by hitting the volume up and the lower right portion of the screen. The Oobe button came back up and i clicked it with success, bypassing the registration.
Well I was able to bypass the Nook Experience BS...Thanks for the tip! But I still didn't have a keyboard to download any apps from the browser. So I created an epub file with Callibre that contained web addresses of all the software I needed to get rid of Swiftkey from system/app. I then transfered the epub to the nook...opened it with Nook's reader....selected a web address....and did a google lookup from within the reader. I was able to download and install what I needed, and it worked. All Better.
demonhater said:
Well I was able to bypass the Nook Experience BS...Thanks for the tip! But I still didn't have a keyboard to download any apps from the browser. So I created an epub file with Callibre that contained web addresses of all the software I needed to get rid of Swiftkey from system/app. I then transfered the epub to the nook...opened it with Nook's reader....selected a web address....and did a google lookup from within the reader. I was able to download and install what I needed, and it worked. All Better.
Click to expand...
Click to collapse
I think what you did is really smart( never mind the semi brick part) and important. This could help out a lot of people that lose keyboard access or other issues that occur. Using the nook reader with google search was a great way around your problem.
SwiftKey force closes on me randomly and will not stop until I re-run the apk inside /System/App again but after that it works fine for awhile. I wonder if it's just SwiftKey because I haven't tried any other keyboards yet
I've noticed several keyboards don't stick after a reboot. Thickbuttons and Hackers seems to be the only 2 I've tried that do stick.
yaggermr said:
I think what you did is really smart( never mind the semi brick part) and important.
Click to expand...
Click to collapse
The scary part was that the NT forced a random wipe on it's own after a quick error about "authorization."
Sorry didn't know about the authentification error and I was joking about the semi brick part. I just thought your recovery method could help somebody out of semi brick hell.
No need to say sorry. I knew you were joking. And hopefully, it will help someone else.
Hi there!
I have just installed Team-B's CM7. First thing I do, install the market, and then install the Swiftkey tablet X Trial from the market.
The keyboard pops up as normal, but it doesn't make the predictions. I changed the input method to the one that comes with CM7 and it works with predictions just fine. When I select back the swift key to be my input method, the predictions are there and work fine.
This doesn't persist, i.e., when I go to another textbox I have to do this procedure again.
And it doesn't predict at all. I mean, when I write some rubbish and it won't correct me, so it's not that it's simply not showing the predictions bar.
(btw, didn't find anything on the wiftkey documentation or FAQ)
My question is why doesn't it predict at the first time I hit the text box? What do I have to do to solve this?
Any ideas?
Cheers
I've been running the beta version of Swiftkey 3 for a couple months which I loaded from the Swiftkey site. It has run OK, and yesterday Swiftkey released it on the market. Paid version is on sale for one week. I ran paid version all day yesterday and that runs ok also. Only problem I see with this version is predictions with apostrophes ('). It doesn't seem to learn them. It has same problem on my GNex too. I'd recommend a different apk.
recently I bought doogee x5 max smartphone from china and I am satisfied with everything except for ONE THING.
the keyboard. even if I type in normal speed. it eats up my words therefore appears like this generally(when typing "xdadeveloper", it is shown on the screen like "xddvlopr") I didnt have same issue with my previous phones (in total 4)
and among all keys , some specific keys work worse than others like P or T
I tried everything I could do for instance, updated using OTA, manually flash stock firmware via needrom, had factory reset 3 times, installed almost every keyboard applications on google play turned off every animation setting in developer option.
its not like a lag I guess since if its not about the letter I type being shown say 2 seconds later, but it just omits the some of the letter in a word.
any advice will be greatly appreciated. I know this is cheap phone so I can not expect too much but this annoys me as HEXX because this is keyboard, used everyday, every time I do the task with my device.
Thank you!
ps) my smartphone has android 6.0 marshmallow, mediatek mtk6580, 1gb ram and 8gb rom, I never tried rootfor this phone. because I bought this just a week ago and I admit I am not gadget prick with plentiful knowledge on machines.
Hmm. This is an odd issue if it is affecting different keyboard apps as well...
I'm wondering if it is a problem with the touch sensitivity? Do you have the same issue whether the phone is upright or on it's side? With different keyboard apps, do the same letters not appear or is it random? Does it make any difference on the other keyboard apps if you resize the keyboard or not (only some support this)?
es0tericcha0s said:
Hmm. This is an odd issue if it is affecting different keyboard apps as well...
I'm wondering if it is a problem with the touch sensitivity? Do you have the same issue whether the phone is upright or on it's side? With different keyboard apps, do the same letters not appear or is it random? Does it make any difference on the other keyboard apps if you resize the keyboard or not (only some support this)?
Click to expand...
Click to collapse
touch itself works just fine when I tap on anything such as web surfing, playing games and checking my emails etc.. and whether upright or sideview, its the same sadly and I dont mean some letters does not completely work but its lame and untyped 3 or 4 times out of 10 , high enough to not have a normal daily use. but yeah, whatever keyboard app I use, same letter goes wrong. and resizing the keyboard layout makes no difference.
I wish there is magic pills to cure this disease. like performance booster app or something if you can recommend me.