Might just be operator error here, but I installed Swype yesterday and it worked just fine. Didn't alter build.prop or anything. I get the pop up keyboard, but when I try to actually type by swiping nothing comes up. the line appears like it's trying to trace out the word but no letters ever show up on my screen. Am I doing something wrong?
PS-The keyboard works fine if I tap the keys, so it installed successfully, it just won't let me trace out the words(which rather defeats the purpose of having it installed)
That is because while swype works on our nook colors, our nook colors do not have an androidID or IMEI, which is a unique number given to any device with a cell radio. That number is required to give swype its "swype" functionality.
well that's depressing. Is there no workaround as of yet?
Swype works just fine, no build.prop edits needed. Refer to this thread
http://forum.xda-developers.com/showthread.php?t=973010&highlight=swype
You do have to be rooted, follow the instructions in post 29 (step 1 not needed if already rooted). I was rooted with AutoNooter, and used Root Explorer to put the apk in the posted location.
As my original post said, I am rooted(using CM7) and did get it installed fine. It's the swyping function that isn't working. Is that working for you?
has anyone got it working on honeycomb?
nicbennett said:
As my original post said, I am rooted(using CM7) and did get it installed fine. It's the swyping function that isn't working. Is that working for you?
Click to expand...
Click to collapse
Yes, the swyping function works fine for me. Sorry, though, can't help you as far as CM7, I am stock autonootered.
fwiw, I just downloaded the SlideIT trial and it is B-E-A-Utiful. swype is way too much hassle when you can pay $6.50 and have the same features for no work.
Related
After GSB Gingerbread 1.7 and up, swype has given me the message "The swype package you installed is configured for another device and will operate with limited functionality. Please contact Swype about this issue." However, using 1.6 and below, it works fine.
P.S. I really think this 10 posts or less can't post in the development discussion forum is not needed. Some people like me are just naturally good at things and want to post to report an issue or a bug. If we really are supposed to post in the question and answer thread, then having others post in the rom pages is unnecessary...
Swype is pretty finicky with GB in my experience. I've hit this problem a number of times. remove swype, remove installer, I use estrongs (any explorer with root privileges will do) I don't remember the exact location but there is a random swype file that sometimes gets left in a folder in /data somewhere. Delete it. Reboot and wipe dalvik. Reboot and let the apps reload and then follow the swype email. This has always worked for me, maybe it could for you too. Swype will still disable on reboot, but just change to a different keyboard and back and it will work again. Doesn't seem to be a real fix for that aspect yet.
Sent from my GSBv1.7-ERIS using XDA Premium App
Clearing the dalvik cache seemed to have done the trick! I didn't find the random swype file though. Thanks!
I have had some new trouble starting with 1.9. Previously with GSB (and KGB) all I had to when it booted up was switch keyboards and switch back and it would quit some latin process and then be fine. However, starting with 1.9, it works just fine on startup except that it won't let me double tap to edit. After switching keyboards around, the latin process still force closes, but I don't get the double tap feature back.
Swype already knows about this issue and says that you should just click the swype key for now.
andrew951 said:
Swype already knows about this issue and says that you should just click the swype key for now.
Click to expand...
Click to collapse
I didn't even know you could do that! That will help a bunch. Thanks!
Sent from my GSBv1.9 ERIS using XDA App
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.
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.
I tried to install swype but it wont seem to work, i just get this: http://img713.imageshack.us/img713/9071/screenshot2012052211152.png
Can someone help me figure out what's wrong?
Same here, may be an issue with some custom asus stuff....
(Maybe the same which prohibits downloading the offline map for Wi-FI Finder?)
// edit: Reinstalling solved the problem
reinstalling? I tried reinstalling the swype downloader twice and it still gave me the error
Swype might not have been updated to work on ICS?
Just fyi, but the Asus keyboard also supports Swype-like text input. It might not have all of the same features included in Swype but it works basically the same way and as well.
IMO Swype is far less convenient when your keyboard is large like it is on the Transformer Prime. You just have to move your finger so much farther in order to hit letters and spell out words, but then again to each his own.
I was able to figure it out but thanks anyways
the newest swype beta is tablet compatible.
the keyboard itself is resizeable so you can actually use it with 1 thumb.
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.