Related
Hello All,
I am attempting to work with Swype support, as I keep getting stuck in the DRM with the beta, which disables the product and pops up "registered on another device, limited functionality", etc.
They have said they have tested it throughly, and have been "unable" to recreate the issue.
I would like to show them how many people are experiencing this issue, and have simply abandoned the beta, and have gone back to the WORKING leaked prerelease.
Please post here if you have had any issue related to the Swype beta, and explain what you have tried to fix it.
THanks!
zimphishmonger said:
Hello All,
I am attempting to work with Swype support, as I keep getting stuck in the DRM with the beta, which disables the product and pops up "used on another device, limited functionality", etc.
They have said they have tested it throughly, and have been "unable" to recreate the issue.
I would like to show them how many people are experiencing this issue, and have simply abandoned the beta, and have gone back to the WORKING leaked prerelease.
Please post here if you have had any issue related to the Swype beta, and explain what you have tried to fix it.
THanks!
Click to expand...
Click to collapse
I don't know what the cause is but I do know how to fix it. Simply long press on any text input box to bring up the "text input" option and select a different keyboard. Once that is done, do it again only this time select Swype. Bingo, back in action.
ItsDon said:
I don't know what the cause is but I do know how to fix it. Simply long press on any text input box to bring up the "text input" option and select a different keyboard. Once that is done, do it again only this time select Swype. Bingo, back in action.
Click to expand...
Click to collapse
Doesnt work for me, and I've been working with support and tried EVERYTHING (uninstall\reinstall, re-register, all the suggested fixes, etc)
I signed up for the beta, downloaded the file and installed it. I could swype all day and nothing appeared in the text box. Installed one of the previous unreleased versions and it worked fine, uninstalled and tried the beta again with same failure mode. Swype doesn't make it easy to comply with their requests to use approved software.
Both Swype support and myself have no idea why, but we were finally able to get Swype up and running on my phone.
Huge thanks for Brian from Swype support for his help, and I recommend anyone having issue to contact their support to see if you can get the issue resolved.
The app has a somewhat complicated (encrypted) registration process, and somehow that was not completing successfully, so def let support know if you are running into similar issues
This happened to me too. I gather it happens every time I install a different ROM, I need to contact Swype to get my Beta account re-authed.
Stuff that, I can't be bothered, I'll just wait until the paid version comes out.
Thought I'd give it another try and still get the "Limited Functionality..."...As usual with restricted access, DRM, etc, it is the ones who try and follow the rules who lose...the pirates will always find a way. Back to the leaked version for me, I guess, though I do think the HTC IME keyboard is still faster and more accurate.
I also get the "limited functionality" message, but only occasionally.
I haven't tested this hypothesis, but seems like it only does this to me when I am at home--and when I'm at home, I'm usually on wifi.
Maybe there's some kind of DRM that didn't take into account that people may occasionally switch from 3G to wifi connections.
If I had more time I'd try messing with it a bit, but I'm just headed to sleep.
There's probably a call home check on first application start up. When you wipe or switch ROMs, that will be cleared, but their servers already have the product registered.
Try backing up the app-data for Swype in between wipes/ROM updates.
I got the "limited functionality" message every time, no ROM updates between download and install. I even reinstalled the installer, redownloaded, etc and it just doesn't work. Glad it didn't work, because it convinced me to go back to HTC IME which is faster and more accurate for me.
http://www.mediafire.com/download.php?toniw2xejzz
its from the other swype thread and this worked for me.
hope for the rest also
well, after some time testing and thinking about this issue i found out whats the cause of it, it happens after rebooting the phone, the reason for this is that rooted roms zip align newly installed apps which changes a lot of things in the file, and i think that the registration process requires the main apk to remain unchanged, maybe someone can contact swype developers and tell them about this and hope that they can find a solution for it.
I have confirmed with a swype tech that there is a registration\call back home immediately following the install of the apk. If successful it will have a quick spinner stating "reristering swype" and the ask you to "enable swype".
I, unfortunately, seem to have major issues getting it to actually call back home, where it states "Swype has already been installed. please uninstall and try again" (I had previously uninstalled it).
In the end, had to revert back to the leaked versions
m_kayali said:
well, after some time testing and thinking about this issue i found out whats the cause of it, it happens after rebooting the phone, the reason for this is that rooted roms zip align newly installed apps which changes a lot of things in the file, and i think that the registration process requires the main apk to remain unchanged, maybe someone can contact swype developers and tell them about this and hope that they can find a solution for it.
Click to expand...
Click to collapse
Ive tried MULTIPLE times to uninstall and reinstall swype w/o rebooting, so I think it wouldn't have a chance to zipalign until the next reboot.
Kind of sad that Swype hasn't gotten back to me yet
Somehow, I am using the Beta version I downloaded myself. I was trying out Super D for a week which is when the Beta was open, later I went back to Dwang and Swype broke when using the Beta installer but I got it working using AppMonster. Here's the steps I followed over that time:
- Wipe phone and install Super D
- Install AppMonster from Market
- Sign up for Swype Beta
- Download SwypeInstaller and install Swype Keyboard
- Perform backup with AppMonster
- Wipe phone and install Dwang
- Download SwypeInstaller and install Swype Keyboard
At this point I got the "Limited Functionality" message
- Wipe phone and install Dwang again
- Install AppMonster from Market
- Restore backup of Swype with AppMonster
Now I can go into Settings and enable Swype in the usual way. I have been using it without a problem for a couple of weeks now.
What solved it for me
I had Swype installed and working on a G1 with Cyanogen latest but after an uninstall it stopped working for me with the same error messages as described here in this forum.
What solved it for me is not pushing the done button on the touch screen after the package install but pushing the back key on the phone. This got me in the registering Swype screen after which the swype installer crashed. Swype is fully working however using these steps.
just go back to installer , log in and reinstall. Everytime i flashed a new rom i did this. I found out u can do this 10 times, before they cut u off. Obviously they know whats up?!
obviously i like the real beat with vibration option and more stable. im using now the final pre release that was made available in a couple posts above mine. no vibration, but it works. this keyboard is fantastic!
Hello everyone,
I want to run a few JavaME apps on my Milestone.
I followed the steps, that I found on a site called LeakDroid..
but when I start the Java app, it force-closes :/
Maybe I need a different version, but I don't really know..
Did anyone manage to get it running?
Nobody managed to get JBed working on a Milestone?
A little late. But it might help. Have a look at java2me explorer and java2me manager. it worked for some games with me. Off course not all off them. Some still crash, but better than nothing. I´m shure others things exist/will appear.
Hope it helps someone.
I have recently installed the AOKP GalaxianSoup Rom, and I was really happy with it because it is really smooth, however I found an issue which forces me to use Honeycomb rather than ICS. When I use the stock browser after a while it becomes unresponsive. It doesn't load pages and even if I force close it still I can't view any webpages. I tried to figure out what causes this and it might be related to Flash content. I also observed this problem with AOSP and CM9 Roms too. I am asking everyone: is this a common issue or it can be only found at me. What can be done to resolve this problem? Thanks for the answers in advance!
GLevi91 said:
I have recently installed the AOKP GalaxianSoup Rom, and I was really happy with it because it is really smooth, however I found an issue which forces me to use Honeycomb rather than ICS. When I use the stock browser after a while it becomes unresponsive. It doesn't load pages and even if I force close it still I can't view any webpages. I tried to figure out what causes this and it might be related to Flash content. I also observed this problem with AOSP and CM9 Roms too. I am asking everyone: is this a common issue or it can be only found at me. What can be done to resolve this problem? Thanks for the answers in advance!
Click to expand...
Click to collapse
There is a common browser issue similar to what you described, but Force stopping the browser fixes this issue every time. To prevent it happening you can set Plugins to On demand. And yes, it is related to Flash.
poisike said:
There is a common browser issue similar to what you described, but Force stopping the browser fixes this issue every time. To prevent it happening you can set Plugins to On demand. And yes, it is related to Flash.
Click to expand...
Click to collapse
Is it possible that there will be some kind of fix for this in the future?
The problem
Hi, I've been experiencing significant interface stuttering whenever an application has been granted accessibility permissions.
Video of the problem
Here is a video demonstrating the issue, read below for technical information: https://www.youtube.com/watch?v=wFVKCx5zVmQ
Facts about the problem
Ok so here's what I know so far:
It doesn't matter which service you grant access to, it will lag the same. I've tried LMT, Swipe Navigation, LastPass, TalkBack, and a few more I can't even remember at the moment.
It doesn't matter what ROM or Kernel you are on. I've tried Euphoria with LK and Hydra, rooted stock with stock kernel and LK, and Benzo with whatever the default Benzo kernel is. Doesn't make a single difference.
It does not only affect Relay for Reddit comment collapsing. It also affect Google Newsstand's mini/big card transition, news source transitions, Google Now transitions, basically anywhere there is an animation in the OS I can notice the stuttering.
Anyone else experience this? Any ideas? It is driving me crazy.
I'm not experiencing that
I've used custom roms/kernels almost all of them in the development forum lol
I wonder if maybe it's a particular accessibility itself? I feel like since its needing to be authorized in accessibility that it might be conflicting with something else, who knows?
People usually try booting the phone into safe mode and seeing if maybes its a third party app?
Thats my 2 cents! Hopefully it helps
It has nothing to do with a specific accesibility from what I can feel, stuttering occurs regardless of the app.
I have full wiped several times to test and can't find a solution.
Does anyone else experience this or have any ideas?
Can anybody duplicate this?
Should I RMA?
ggmask said:
Can anybody duplicate this?
Should I RMA?
Click to expand...
Click to collapse
adjust your governor/scheduler. me, i like using ondemand/deadline.
simms22 said:
adjust your governor/scheduler. me, i like using ondemand/deadline.
Click to expand...
Click to collapse
I've done this when using LK/Hydra, but I am not running stock kernel. None of the adjustments made any noticeable difference unfortunately
I really hate to bump this but the video only has 16 views and I'd love someone else to confirm or deny the same behavior when granting an app accessibility permissions.
If this is common behavior I won't RMA, but if no one else can recreate this I'm going to.
Oh, another thing I noticed: you don't have to test it in an app like Relay for Reddit, you can also do it in the Chrome browser on a site that has a lot of information. What I've noticed is that, when accessibility is granted to any app, visiting XDA forums becomes almost unusable. It takes FOREVER to scroll and when I can scroll it is extremely choppy. Disable the accessibility permission? Completely solves the problem.
You are NOT crazy. I have been searching, seeing if anyone else had this problem. I am using a completely stock Nexus 6 (not rooted), and because of the screen size I have been tinkering with apps to help with one handed use (like pie controls, handy soft keys, etc). They also require accessibility to be enabled. Whenever I install them, I notice (about once every 6-7 times) that when I open my app drawer on Nova launcher, it will half freeze, half stutter. Most of the time it's fine, but once every few times it happens. I haven't paid too much higher attention to whether jt causes stuttering in other apps, but it drives me nuts and so I uninstall the app and go back to stretching my thumb to use the stock nav keys. Wish this would get fixed. Kind of unacceptable for a Nexus - that kind of stuttering is why I don't like using Samsung devices.
Here is the Swipe Navigation developer saying it is definitely a thing in Lollipop with accessibility settings. (screenshot from Play Store comments on Swipe Navigation app). I wish someone could figure this out - I guess we have to wait for Google to do that?
I am using PieControl Pro and I do believe it makes the animations in the Play story stutter when I open a page and use the back button to go back to the app overview. The Play store was never completely smooth no matter what, but when I disable accessibility for PieControl Pro, it becomes a little better. So yeah, accessibility does seem to affect UI performance. I'm on stock Android 5.1 with Franco Kernel.
wbarnes4393 said:
You are NOT crazy. I have been searching, seeing if anyone else had this problem. I am using a completely stock Nexus 6 (not rooted), and because of the screen size I have been tinkering with apps to help with one handed use (like pie controls, handy soft keys, etc). They also require accessibility to be enabled. Whenever I install them, I notice (about once every 6-7 times) that when I open my app drawer on Nova launcher, it will half freeze, half stutter. Most of the time it's fine, but once every few times it happens. I haven't paid too much higher attention to whether jt causes stuttering in other apps, but it drives me nuts and so I uninstall the app and go back to stretching my thumb to use the stock nav keys. Wish this would get fixed. Kind of unacceptable for a Nexus - that kind of stuttering is why I don't like using Samsung devices.
Click to expand...
Click to collapse
Thank you! I was losing my mind tryingbto figure this out so I opened a support ticket with Google play store and the person who handled my case was able to reproduce it and has made a note of it (whether this means there's an official bug report or not I don't know). He also said this issue cannot be used to RMA, since it wouldn't do anything anyway.
Unless someone can confirm that they DO NOT have this issue.
Im using swipe navigation and I'm noticing stutter as well. Wonder why this happens. Took me a while to figure it out.
Would you mind pointing me to the Google page where you reported this? I would like to star it as well, and follow their updates.
As a follow up, today I decided to tinker around and install pie again. Since the Nova app drawer animation is what I always notice stuttering first, I decided to just turn Nova animations off. Then, I went into Android settings, developer options, and reduced the three animation settings to 0.5x. I may just be seeing what I want to see, but the UI hasn't seemed to stutter with Pie enabled in accessibility (yet). Going to try this for a day or two.
I've gotten the same issues with Lastpass.
Lastpass even states on their site that it's a lollipop issue.
https://lastpass.com/support.php?cmd=showfaq&id=8166
ggmask said:
Thank you! I was losing my mind tryingbto figure this out so I opened a support ticket with Google play store and the person who handled my case was able to reproduce it and has made a note of it (whether this means there's an official bug report or not I don't know). He also said this issue cannot be used to RMA, since it wouldn't do anything anyway.
Unless someone can confirm that they DO NOT have this issue.
Click to expand...
Click to collapse
Sorry if this counts as bringing up an old thread, although it's not THAT old
Anyway, I've come here just to corroborate all your findings and confirm that I am also experiencing this ugly bug. A few days ago I installed Greenify which, among other things, asked to enable Accessibility features for it. Thinking nothing of it I did as requested. Next day I start noticing some UI lagginess and choppiness, which was especially noticeable to me in Relay for Reddit since I use it a lot (too much for my own good in fact) and I distinctly remember it had very smooth scrolling between comments just a few days ago. In the mean time, I completely forget I've granted Greenify accessibility control so I went on a mission trying to fix this inexplainable, sudden UI choppiness, by trying to flash a different kernel, trying different governors, dirty flashing my ROM, trying all the other tweaks, and finally doing a factory reset and flashing the stock ROM all over again (luckly I did make a nandroid). Nothing helped. I was at my wits end when I tried searching the app's subreddit for anyone experiencing the same issue and found a comments saying accessibility features were to blame. I felt stupid for not researching it before. However, this bug is very insidious as it just creeps up on you, with no reason. I also don't know how can accessibility features affect UI smoothness this way.
Yes, hopefully will be fixed in M maybe? I haven't checked around to see if those who have installed M preview have checked to see if the bug has been fixed there. Fingers crossed.....
Not fixed in M. Everyone should go star the issue so it gets fixed!
https://code.google.com/p/android-developer-preview/issues/detail?id=2092
wbarnes4393 said:
Not fixed in M. Everyone should go star the issue so it gets fixed!
https://code.google.com/p/android-developer-preview/issues/detail?id=2092
Click to expand...
Click to collapse
Still isnt fixed ) But my lag rather appears when tapping on any app icon, then it highlights, then go lag, then opening animation starts.
Post this over on reddit and see if you can bring a bit more attention to the issue.
Chrome keeps saying aw snap and it says same with different browsers that I tried to install, any help?
Doesn't sound like something that has anything to do with Magisk... Unless you've used it to change any settings you shouldn't have.
But, oh well, you never know... If you want any kind of help you should provide a lot more detail and possibly also some relevant logs.
fixed it by uninstalling the emoji switcher