Go Back   Android Forums > Android Discussion > Android Applications
Android Applications All the information you could ever want about Android Applications. Learn about apps and get help with them... all here! New apps can be found and announced in the Applications Announcements forum linked below.

Get excited for the Samsung Galaxy S5! Find everything you need and discuss it in our Galaxy S5 Forum!

Like Tree1Likes
  • 1 Post By lexluthor

test: Reply
 
LinkBack Thread Tools
Old October 18th, 2012, 12:25 PM   #1 (permalink)
Senior Member
Thread Author (OP)
 
gtbarry's Avatar
 
Join Date: Jul 2012
Location: California
Gender: Male
Posts: 1,844
 
Device(s): Nexus 5 (US - GSM) and Nexus 7 (2013). All stock
Carrier: t-mobile (USA)

Thanks: 132
Thanked 702 Times in 521 Posts
Default Swype 1.3.1.9274 not working on Jelly Bean

I was prompted to update swype this morning. I did so, and now everytime I select swype it closes automatically and I get the android keyboard. Anyone else having this issue?

- Swype Beta is checked in Language & Input (android keyboard is selected and grey in this screen)
- Choose Input Method screen. I select "Swype Beta". It flashes to Swype. Then reverts back to Android keyboard immediately
- I have cleared cache, etc. and rebooted the phone. This brought me to the new swype EULA and activation process. Which I did successfully. I rechecked all settings.

Jelly bean 4.1.2
Swype 1.3.1.9274 (downloaded on 18 October, 2012)

Thanks!

gtbarry is offline  
Last edited by gtbarry; October 18th, 2012 at 12:51 PM.
Reply With Quote
sponsored links
Old October 18th, 2012, 12:51 PM   #2 (permalink)
New Member
 
Join Date: Apr 2010
Location: Southern California
Gender: Male
Posts: 3
 
Device(s): Galaxy Nexus, Motorola Xoom, Nexus 7
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

I have the exact same problem. I did the update on my Nexus 7 as well, but didn't run into this problem.
CHRISTEVAN is offline  
Reply With Quote
Old October 18th, 2012, 12:52 PM   #3 (permalink)
New Member
 
Join Date: Oct 2012
Posts: 1
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

having the same issue on a rooted galaxy nexus, running stock firmware 4.1.2
viperfan7 is offline  
Reply With Quote
Old October 18th, 2012, 01:01 PM   #4 (permalink)
The Real Bass Creator
 
Digital Controller's Avatar
 
Join Date: Sep 2012
Location: Cincinnati, Ohio
Gender: Male
Posts: 10,683
 
Device(s): Galaxy Note 3 with JellyBeans 6, Nexus 7, (RIP) Galaxy Nexus with 4.4 SlimKat, (RIP) Droid Incredibl
Carrier: Verizon

Thanks: 526
Thanked 2,770 Times in 1,806 Posts
Default

My Swype is acting fine on my GNex with a nightly of Cm10...sounds like a weird error, have you tried reinstalling swype yet?
__________________
Want Faster help? Read this before posting!

I love this community and so should you! So before posting please read:
Site Rules & Guidelines and Android FAQ's
Digital Controller is offline  
Reply With Quote
Old October 18th, 2012, 01:33 PM   #5 (permalink)
New Member
 
Join Date: Apr 2010
Location: Southern California
Gender: Male
Posts: 3
 
Device(s): Galaxy Nexus, Motorola Xoom, Nexus 7
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

It might be affecting only those with stock versions of Jelly Bean. I did uninstalled swype beta as well as the installer then reinstalled everything. Still no luck.
CHRISTEVAN is offline  
Reply With Quote
Old October 18th, 2012, 01:46 PM   #6 (permalink)
Senior Member
Thread Author (OP)
 
gtbarry's Avatar
 
Join Date: Jul 2012
Location: California
Gender: Male
Posts: 1,844
 
Device(s): Nexus 5 (US - GSM) and Nexus 7 (2013). All stock
Carrier: t-mobile (USA)

Thanks: 132
Thanked 702 Times in 521 Posts
Default

Quote:
Originally Posted by Digital Controller View Post
My Swype is acting fine on my GNex with a nightly of Cm10...sounds like a weird error, have you tried reinstalling swype yet?
Uninstalled. Reinstalled. Reactivated. EULA accepted. Selected. Still crashing.

Bombed them on twitter, facebook and youtube (that's what you get for not having any other way to get a hold of you). Let's see if we get a reply.
gtbarry is offline  
Reply With Quote
Old October 18th, 2012, 03:01 PM   #7 (permalink)
Senior Member
 
Join Date: May 2010
Location: Long Island, NY
Posts: 3,957
 
Device(s): Samsung Galaxy S3, HTC One S, iPhone 5s, Nook HD+, Nook Color
Carrier: Verizon and T-Mobile

Thanks: 131
Thanked 386 Times in 247 Posts
Default

Quote:
Originally Posted by gtbarry View Post
Uninstalled. Reinstalled. Reactivated. EULA accepted. Selected. Still crashing.

Bombed them on twitter, facebook and youtube (that's what you get for not having any other way to get a hold of you). Let's see if we get a reply.
Try here too.
Swype BETA for Android

I know they read those forums.
gtbarry likes this.
lexluthor is offline  
Reply With Quote
The Following User Says Thank You to lexluthor For This Useful Post:
gtbarry (October 18th, 2012)
Old October 18th, 2012, 03:10 PM   #8 (permalink)
New Member
 
Join Date: Oct 2012
Posts: 2
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

Same exact issue. I'm running Vicious JB (taken directly from AOSP months before Verizon decided to release the update) and Swype was fine until this morning when I upgraded. I can access all the settings, etc., but every time I try to actually switch to Swype, it flashes and then goes back to the stock keyboard. Considering how much they damage Swype with each update, this may be the final push for me to not use them anymore.
The Greatjon is offline  
Reply With Quote
Old October 18th, 2012, 03:49 PM   #9 (permalink)
Senior Member
Thread Author (OP)
 
gtbarry's Avatar
 
Join Date: Jul 2012
Location: California
Gender: Male
Posts: 1,844
 
Device(s): Nexus 5 (US - GSM) and Nexus 7 (2013). All stock
Carrier: t-mobile (USA)

Thanks: 132
Thanked 702 Times in 521 Posts
Default

Quote:
Originally Posted by lexluthor View Post
Try here too.
Swype BETA for Android

I know they read those forums.
Thanks! I'm on them in the forum. They should have made this easier to find off their website so I wouldn't have taken the fight to twitter, etc.
gtbarry is offline  
Reply With Quote
Old October 18th, 2012, 04:40 PM   #10 (permalink)
Senior Member
Thread Author (OP)
 
gtbarry's Avatar
 
Join Date: Jul 2012
Location: California
Gender: Male
Posts: 1,844
 
Device(s): Nexus 5 (US - GSM) and Nexus 7 (2013). All stock
Carrier: t-mobile (USA)

Thanks: 132
Thanked 702 Times in 521 Posts
Default

Latest from swype:
"We have been able to reproduce this in-house and are confident we know what the issue is.

We are still investigating this but will keep this thread updated as we have more information.

We'll reach out to you further if needed."


In the meantime they are recommending:

"you should be able to use Swype be disabling any apps that are in Android Settings > Accessibility."

Which is only a temporary fix and I think (and hope!) they know that.


Official Galaxy Nexus Jelly Bean Swype Issue Thread
gtbarry is offline  
Reply With Quote
sponsored links
Old October 18th, 2012, 04:45 PM   #11 (permalink)
Junior Member
 
Join Date: Feb 2011
Location: Southern IL USA
Posts: 20
 
Device(s): LG Optimus V
Carrier: Not Provided

Thanks: 0
Thanked 4 Times in 3 Posts
Default

If you're rooted, you can also temporarily move the stock keyboard files out of /system/app, and still use any accessibility apps and Swype. There are instructions in that thread on the Swype forum. That's what I've done for the time being.
csx321 is offline  
Reply With Quote
Old October 18th, 2012, 04:54 PM   #12 (permalink)
New Member
 
Join Date: Oct 2012
Posts: 1
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by gtbarry View Post
Thanks! I'm on them in the forum. They should have made this easier to find off their website so I wouldn't have taken the fight to twitter, etc.
I found that it is a problem with Lightflow. Go to accessibilty under settings and deselect Lightflow. Mine worked when I did this.
jghayes is offline  
Reply With Quote
Old October 18th, 2012, 05:03 PM   #13 (permalink)
Junior Member
 
Join Date: Feb 2011
Location: Southern IL USA
Posts: 20
 
Device(s): LG Optimus V
Carrier: Not Provided

Thanks: 0
Thanked 4 Times in 3 Posts
Default

Quote:
Originally Posted by jghayes View Post
I found that it is a problem with Lightflow. Go to accessibilty under settings and deselect Lightflow. Mine worked when I did this.
It's actually a conflict with anything that uses Android's Accessibility services. For me, it was the Augmented Smartwatch notification system for the Sony Smartwatch.
csx321 is offline  
Reply With Quote
Old October 18th, 2012, 05:47 PM   #14 (permalink)
Senior Member
Thread Author (OP)
 
gtbarry's Avatar
 
Join Date: Jul 2012
Location: California
Gender: Male
Posts: 1,844
 
Device(s): Nexus 5 (US - GSM) and Nexus 7 (2013). All stock
Carrier: t-mobile (USA)

Thanks: 132
Thanked 702 Times in 521 Posts
Default

I don't personally believe good things will happen to swype's marketshare or credibility if they say "nothing else can use Accessibilty Services except us."

This would make people choose between them and Tasker. Them and Light flow. Them and Talkback. Etc.

A long term fix seems to be in the works/near future and can't be released soon enough for me.
gtbarry is offline  
Reply With Quote
Old October 18th, 2012, 05:48 PM   #15 (permalink)
Member
 
zebug's Avatar
 
Join Date: Apr 2010
Location: Houston, Texas
Posts: 333
 
Device(s): Verizon Galaxy S4
Carrier: Verizon

Thanks: 137
Thanked 189 Times in 96 Posts
Default

Yep, once I disabled things in accessibility, swype started working. On a side note I love this forum. Figured I wasn't alone. Let's hope they fix this fast as I love my lightflow
zebug is online now  
Reply With Quote
Old October 18th, 2012, 06:12 PM   #16 (permalink)
Senior Member
Thread Author (OP)
 
gtbarry's Avatar
 
Join Date: Jul 2012
Location: California
Gender: Male
Posts: 1,844
 
Device(s): Nexus 5 (US - GSM) and Nexus 7 (2013). All stock
Carrier: t-mobile (USA)

Thanks: 132
Thanked 702 Times in 521 Posts
Default

currently swype has not posted a fix for this other than disabling everything else in Accessibilty Services. (Which I do not believe is a long term fix.)

On the official swype forum someone mentioned this and it works:
- under apps disable the Android keyboard
- reboot phone and select swype.

Worked for me and I have both swype and lightflow working.
gtbarry is offline  
Reply With Quote
Old October 19th, 2012, 08:48 PM   #17 (permalink)
Senior Member
 
UncleMike's Avatar
 
Join Date: Nov 2009
Location: Central NJ
Posts: 2,123
 
Device(s): Moto X - GSM DE
Carrier: Not Provided

Thanks: 59
Thanked 392 Times in 325 Posts
Default

Quote:
Originally Posted by gtbarry View Post
currently swype has not posted a fix for this other than disabling everything else in Accessibilty Services. (Which I do not believe is a long term fix.)

On the official swype forum someone mentioned this and it works:
- under apps disable the Android keyboard
- reboot phone and select swype.

Worked for me and I have both swype and lightflow working.
Working here too.

Edit: I take that back. While this did manage to keep Swype selected as the current keyboard, the accessibility issue that's the root cause of the problem was causing Tasker use of the accessibility service to fail, meaning it couldn't detect any notifications. After an hour or so trying to figure out why Tasker suddenly wasn't working as expected, I restored the previous Swype using Titanium Backup and Tasker functionality is back to normal.
__________________
Dropbox referrals: http://db.tt/GfR6Q7v8
UncleMike is offline  
Last edited by UncleMike; October 20th, 2012 at 07:40 AM.
Reply With Quote
Old October 22nd, 2012, 02:42 AM   #18 (permalink)
Senior Member
Thread Author (OP)
 
gtbarry's Avatar
 
Join Date: Jul 2012
Location: California
Gender: Male
Posts: 1,844
 
Device(s): Nexus 5 (US - GSM) and Nexus 7 (2013). All stock
Carrier: t-mobile (USA)

Thanks: 132
Thanked 702 Times in 521 Posts
Default

Swype has gone mostly dark on this after staying mostly on top of this on the 18th when the issue broke???

Last thing on their official forum was "ensure that all applications or settings that are in Android Settings > Accessibility are disabled/turned off." And how should that be considered a final solution?

No word on an update or real fix? And demanding to be the only app or program running in Accessibility sounds somewhat unrealistic.

Be nice to hear something current from Swype.
gtbarry is offline  
Reply With Quote
Old October 22nd, 2012, 07:28 AM   #19 (permalink)
The Real Bass Creator
 
Digital Controller's Avatar
 
Join Date: Sep 2012
Location: Cincinnati, Ohio
Gender: Male
Posts: 10,683
 
Device(s): Galaxy Note 3 with JellyBeans 6, Nexus 7, (RIP) Galaxy Nexus with 4.4 SlimKat, (RIP) Droid Incredibl
Carrier: Verizon

Thanks: 526
Thanked 2,770 Times in 1,806 Posts
Default

I have always loved Swype, and usually they respond quickly to errors like this, it is kind of saddening that it has taken them this long to do anything about this issue.
Digital Controller is offline  
Reply With Quote
Old October 22nd, 2012, 11:45 AM   #20 (permalink)
Senior Member
Thread Author (OP)
 
gtbarry's Avatar
 
Join Date: Jul 2012
Location: California
Gender: Male
Posts: 1,844
 
Device(s): Nexus 5 (US - GSM) and Nexus 7 (2013). All stock
Carrier: t-mobile (USA)

Thanks: 132
Thanked 702 Times in 521 Posts
Default

Swype was really active on the 18th when this issue blew up on them.

They had one more post on their official forum on the 19th.

Then after my posting on the official forum (on the 22nd) about their silence, this is their current response:

"We understand that this is a temporary solution and as I stated before we are still investigating the issue.

On another note:

Is anyone out there without apps that interface with accessibility experiencing this issue?

Thanks!"
gtbarry is offline  
Reply With Quote
sponsored links
Old October 22nd, 2012, 02:33 PM   #21 (permalink)
Senior Member
 
tcat007's Avatar
 
Join Date: Jan 2011
Location: Texas
Posts: 1,723
 
Device(s): Nexus 7, 16gb (GrooveIP, T-mobile Hotspot device)
Carrier: none

Thanks: 66
Thanked 259 Times in 239 Posts
Default

No problems on Nexus 7 (not rooted). Updated on the 18th no issues. I don't have any apps listed in the accessibility section other than Talkback and Widgetsoid, and they are both off.
tcat007 is offline  
Reply With Quote
Old October 23rd, 2012, 09:25 PM   #22 (permalink)
Senior Member
Thread Author (OP)
 
gtbarry's Avatar
 
Join Date: Jul 2012
Location: California
Gender: Male
Posts: 1,844
 
Device(s): Nexus 5 (US - GSM) and Nexus 7 (2013). All stock
Carrier: t-mobile (USA)

Thanks: 132
Thanked 702 Times in 521 Posts
Default

Alleged fix on the way. Posted on official Swype forum on 23, October.

"Hi all!

This has been fixed and will be delivered to you via an OTA within the next 72 hours!

Feel free to respond with any questions you may have. Thank you all for your patience!"
gtbarry is offline  
Reply With Quote
Old October 24th, 2012, 01:16 PM   #23 (permalink)
New Member
 
Join Date: Oct 2012
Posts: 2
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default Fix one thing, break another...

So the update to restore basic functionality is great and all, but they changed the duration of the vibration back to the overly long setting, rather than the new&improved short vibration that was on par with the stock keyboard and softkeys.
The Greatjon is offline  
Reply With Quote
Old October 24th, 2012, 11:26 PM   #24 (permalink)
Senior Member
Thread Author (OP)
 
gtbarry's Avatar
 
Join Date: Jul 2012
Location: California
Gender: Male
Posts: 1,844
 
Device(s): Nexus 5 (US - GSM) and Nexus 7 (2013). All stock
Carrier: t-mobile (USA)

Thanks: 132
Thanked 702 Times in 521 Posts
Default

I received the OTA update today. Everything is fine for me.

I enabled my android keyboard and rebooted the phone. Android keyboard is back now.

I have seen on their official forum that people are having issues with having two swypes installed after the update, removing of personalization/dictionary, auto spacing not working etc. I luckily have none of these.
gtbarry is offline  
Reply With Quote
Old October 25th, 2012, 12:35 PM   #25 (permalink)
Senior Member
Thread Author (OP)
 
gtbarry's Avatar
 
Join Date: Jul 2012
Location: California
Gender: Male
Posts: 1,844
 
Device(s): Nexus 5 (US - GSM) and Nexus 7 (2013). All stock
Carrier: t-mobile (USA)

Thanks: 132
Thanked 702 Times in 521 Posts
Default

Nice timing on this announcement...

SwiftKey Flow brings trace-typing to predictable keyboard [VIDEO]

Looking forward to giving this a try.
gtbarry is offline  
Reply With Quote
Reply


Go Back   Android Forums > Android Discussion > Android Applications
Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT -5. The time now is 05:41 PM.
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.