View Single Post
Old October 19th, 2012, 08:48 PM   #17 (permalink)
UncleMike
Senior Member
 
UncleMike's Avatar
 
Join Date: Nov 2009
Location: Central NJ
Posts: 2,122
 
Device(s): Moto X - GSM DE
Carrier: Not Provided

Thanks: 59
Thanked 391 Times in 324 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