Continuous typing option is available under samsung keyboard settings which will give swype like typing.
Sent from my GT-N7100 using Tapatalk 2
Unbelievable. So sorry you are having this issue. I can't think of anything else to try or even what the issue may be. Mine works fine. Sorry I can't be of more help. This may be the key to your problem:Wow, what a fail from samsung.
It was that, but I can't resign to use lightflow, tasker and wp7 notifications to have swype-alike in the samsung keyboard... Even if I check it after disable everything on accessibility and stays checked, after activate it all again, it doesn't work.
I think I am going to install swype beta.
Curses!!!
I did notice the same thing with the hoover function in the pen when enabling Light Flow but I never (ever ever) would have connected this KB issue to it my self...
Hmmm...I'm sorry but I think I'll disble Light Flow...
(BTW, is there a way for developers to disable the automatic translation of app titles in the play store? Light Flows name sounds really silly translated to Swedish...)
EDIT: I did disable Light Flow in the accesibility (SP?) meny and Light Flow still works! And I have "Swype"...
Wow, what a fail from samsung.
It was that, but I can't resign to use lightflow, tasker and wp7 notifications to have swype-alike in the samsung keyboard... Even if I check it after disable everything on accessibility and stays checked, after activate it all again, it doesn't work.
I think I am going to install swype beta.
What a hard knock on Samsung for something so small in relative to how much they've done with this phone. Have you considered that maybe it is the app developer of lightflow who should update his code to work around this problem? I'm thinking apps like lightflow works by overriding some settings and controls, and it is probably more likely that the lightflow is overriding unnecessary ones.
That makes more sense to me than Samsung having code in there disabling continuous input when it seems that you have something like lightflow enabled. :angel:
It's certainly a samsung issue. I've written a tiny textbook example app that just registers the accessibility service and does nothing else and the talkback and continuous typing issues occur. It happens for all apps that register the accessibility service also and that's following the android guidelines for developing one. Believe me, if there was an easy way to work around this issue I would. There are about 20 different combinations of registering different events in accessibility and I've tried every single one and that all manifest in getting this issue. It's not always possible to work around underlying bugs such as this. There are a number of apps affected such as Tasker, Llama, noLed, missedIt, pops etc which all use the same service. I've spoken to the devs of most of these apps about the issue too. Some apps such as tasker and llama it's not as obvious as it's only if you enable monitoring notifications which they don't have enabled by default.
The developers of swype had a similar issue over the last week or so where swype got disabled when enabling accessibility services. They identified the issue and fixed their app to work. I really wish there was a way to code around this, but I've been looking for one for months as from my support e-mails it's probably the biggest reason for the app to get uninstalled.
I encourage people to report it to samsung and see what they say.
I, as a unitiated user, also think it's Samsungs fault as the phone warns that enabling Talkback diables Countious input when I enable Light Flow...Talkback countinues to be disabled...
I belive this isn't the right place for a feature request but as I am already posting about Light Flow... I'd like to make my led blink while the phone is powered on (like the ancient Ericsson GH388), much easier to find the phone in the dark...
Mabey it is possible already but I couldn't find a logical way to enable it...
Do you mean when the screen is on, or just when it's switched on (or in standby with the screen off). If you mean the latter, then using a combination for "signal" and "no signal" can pretty much do the same.
What a hard knock on Samsung for something so small in relative to how much they've done with this phone. Have you considered that maybe it is the app developer of lightflow who should update his code to work around this problem? I'm thinking apps like lightflow works by overriding some settings and controls, and it is probably more likely that the lightflow is overriding unnecessary ones.
That makes more sense to me than Samsung having code in there disabling continuous input when it seems that you have something like lightflow enabled. :angel:
Thanks for this post!
Like many other, I was unable to understand why my continuous input was disabled since a week or so.
I have my Pebble for a week and the sync application require... Accessibility...!
ps: Im using a S3