Related
I have Cyanogen's 4.2.3.1 installed with the 2.0 Maps application and Navigation works correctly for me.
Since I installed Navigation I am getting a huge "Double tap to answer" button that pops up on my screen when a call comes in.
A) It seems to have shortened the amount of time my phone rings before sending to voicemail
B) The double tap is flaky
C) It looks like ****
I have searched Google and the forums to see if this was an issue people had but can only find people talking about the in-call unlock screen.
Does anyone know why this is happening and how to stop it?
Is your navigation actually on while this is happening? If you have the little triangle above in your task bar then it is.
If you are fully exited from maps this shouldn't come up. At least it doesn't on my phone.
This happens all the time now. Even with GPS off and the Maps app not even loaded. Persists through reboots.
Odd. This happens while I have maps loaded, but not when its not loaded.
How did you install navigation?
push back our old build.prop
Will pushing back my old build.prop disable navigation?
No navigation only needs it for the install. I thought that might be the problem. Push your old prop files back and good luck!
this happend to me aswell, but i actually liked the double click - box look
that would also happen when my phone was just sitting here, no nav on, it would just light up, and have the double click box lit up.
i was on 4.2.3.1.
all that ended when i flashed cyan 4.2.4
i didnt wipe.. or fix permissions.
i installed navs from other thread [basically just the update.zip and clear data]
and everythingg works just fine. thanks to all!
I didn't know 4.2.4 was out yet but thought a Cyanogen Mod update would probably fix that issue. Reverting to my previous *.props has fixed all the issues.
You should've posted this in the Q&A section or an existing related thread.
Anyways.. To get rid of the double tap box, you need to push back the original build.props. If you do that however, you'll lose navigation in a few hours, like 6 or 7 hours.
There's already a thread about this that's named something like "unlocked features from new build.prop".
tee aiy emm said:
You should've posted this in the Q&A section or an existing related thread.
Anyways.. To get rid of the double tap box, you need to push back the original build.props. If you do that however, you'll lose navigation in a few hours, like 6 or 7 hours.
There's already a thread about this that's named something like "unlocked features from new build.prop".
Click to expand...
Click to collapse
I will remember that next time. After being on here for almost 3 years I forget that the newbie youngsters like to change how we have done things here. Like one thread per issue. Thank you for the helpful link to the thread you thought I should have posted it in, great to see that XDA hasn't gone all to hell with newbie senior members who just throw out dictates and then can't even do a decent job of helping people.
use this if you are running cyanogen http://forum.xda-developers.com/showthread.php?t=583684
Heres the thread for updated features from build.prop
http://forum.xda-developers.com/showthread.php?t=583030
I just did the install with the newest cyanogen and then tried calling myself and I dont have any issues.
Also, navigation works fine.
I have a G1 with CM 4.2.4, and I'm not having the issue either. I tested incoming calls with the NAV and in maps.
I finally got Navigation -and- paid apps in Market to show, but, I am experiencing the same problem as the OP mentioned.
I don't want to lose Navigation but this is a little annoying. Someone mentioned if I put the original build.prop and build.trout.prop back, Navigation will not show up. How can we get the best of both worlds?
[delete - repeat post]
Proxin said:
I finally got Navigation -and- paid apps in Market to show, but, I am experiencing the same problem as the OP mentioned.
I don't want to lose Navigation but this is a little annoying. Someone mentioned if I put the original build.prop and build.trout.prop back, Navigation will not show up. How can we get the best of both worlds?
Click to expand...
Click to collapse
i swear i feel like people just post without reading anything. i posted a link to a thread that will fix your problem. look up a few posts. another member here had an update.zip that will install the maps without breaking the market, without making the weird floating box, and without any other weird problems. if you are running cyanogen it will work perfect.
the .props need to me modified to allow navigation to remain longer than a few hours. just apply the update-navigation.zip from recovery mode and it will fix your issue.
Babaki said:
look up a few posts. another member here had an update.zip that will install the maps without breaking the market, without making the weird floating box, and without any other weird problems. if you are running cyanogen it will work perfect.
Click to expand...
Click to collapse
Actually I am having this same issue WITH using that .zip but for me it is no big deal. We are lucky to have Nav, I will take it with whatever problems (temporary of course) it comes with!
i had the double tap issue after i manually installed nav on wednesday. today i ran that .zip and the box is gone. i dont get why it would work for some people and not others.
the zip was actually updated 3 or 4 times. so if you applied it when it was first dropped, maybe you have an old version
Hey folks,
I just flashed over the latest phiremod and I'm having a couple of small issues. 1: Whenever I go into settings > about phone and hit "status," it force closes on me before I can even see any info (like batt. status, level etc). Anyone experience anything similar and if so, found any workaround?
2: I downloaded and installed the newest version of Google Voice from the market but can't set it up. During set up, after I provide the number associated with it the next step attempts to set up voicemail (and obviously can't) so I just press the option to "skip" it, but whenever I do so the set up screen and the buttons go grey and just stay that way. Anyone know of any workarounds?
Thanks for any help!
Hope it's alright to bump this. Again, if anyone has any idea on a fix, I'd really appreciate it. (Of course, if I missed a thread or two about these same issues, feel free to throw in a link.)
Thanks!
This crazy problem started last week with my Galaxy S running Serendipity ROM.
Now, when I want to compose a text or email with voice, it isn't using english. I thought it was Spanish at first (no I can't speak Spanish). But sometimes it's typing different words or even numbers for the same words I speak.
I say "this is a test", and I get, "nosotras". As I'm typing this, it is now typing the same thing for the same words. It wasn't doing that yesterday. three times I got three different responses.
I have made sure that English is selected in settings. the only thing I can think of that has changed in the last couple of weeks (months even) is I re-installed Google voice app. The problem started a day or two after that, the best i can recall. I've been running this ROM since I first got the phone two years ago. I don't install new software very often.
So, what's going on with my phone? Some crazy virus? Has the phone become self aware and decided to toy with me? Voice text is one of my most favorite features, i really want it to work again.
Try clearing the data in the 3 voice programs and maybe Google voice too.
Which program are you using for your speech-to-text conversion? I'm using Google Voice myself, but I don't see any built-in conversion software. Is it tied to the keyboard program you're using?
If you can't get anything else to work, you can try the newest Swype beta; it has Dragon conversion software built in, and in my experience, it works pretty well.
I'm not sure what program it is. It came with the Serendipity ROM. I'll have to dig around and find out.
How/where would i clean my programs?
tweakedlogic said:
I'm not sure what program it is. It came with the Serendipity ROM. I'll have to dig around and find out.
How/where would i clean my programs?
Click to expand...
Click to collapse
Go to settings - applications - manage applications, then find the individual applications. Click the app, and then the "clear data" button. That will reset the offending app's data.
Thank you very much. clearing the data worked. I hope it stays fixed. I think the one that fixed it was clearing the swype keyboard. I never liked the swype KB, I should just remove it if it's going to cause trouble.
Thanks again.
Hi guys, I really hope I can get some help here, can't find anything about the problems I am encountering.
I am using this phone for about 4 weeks now, and it's working fine, except for some problems with widgets. I have problems with 3 apps/widgets now; they all worked fine on my old phone, a HTC Sensation XE (rooted, with different ROM's and Android versions). They all have strange behaviour. At first I thought I had some settings set wrong in the apps themselves, but I tried everything I could think of and now I have to conclude that the problems start with the phone itself.
I am encountering problems with the following apps:
aCalendar+: widget, but also opened app get in some kind of update loop; sync icon starts spinning, stops and immediately starts again, and on and on. It does sync properly though in the meantime.
Plume: Most of the time the widget does not respond to manually syncing. Only after I open the app and sync manually (which works fine), and go back to the widget, I can finally sync using the widget.
Transparent clock & weather: Most of the time, the clock does not keep track of the time, it just hangs. Only when I tap the widget, or refresh the weather, it syncs with the internal clock, like it should. Sometimes though, the clock does keep track for a short time, but in the end it will hang again.
I tried out a lot of different things with the P7 energy- and network apps settings. Also I upgraded to firmware version 126, but it all doesn't make any difference. It's all really annoying, especially because I never had those issues on my old phone.
Anybody got a clue?
flupke02 said:
I am encountering problems with the following apps:
aCalendar+: widget, but also opened app get in some kind of update loop; sync icon starts spinning, stops and immediately starts again, and on and on. It does sync properly though in the meantime.
Plume: Most of the time the widget does not respond to manually syncing. Only after I open the app and sync manually (which works fine), and go back to the widget, I can finally sync using the widget.
Transparent clock & weather: Most of the time, the clock does not keep track of the time, it just hangs. Only when I tap the widget, or refresh the weather, it syncs with the internal clock, like it should. Sometimes though, the clock does keep track for a short time, but in the end it will hang again.
I tried out a lot of different things with the P7 energy- and network apps settings. Also I upgraded to firmware version 126, but it all doesn't make any difference. It's all really annoying, especially because I never had those issues on my old phone.
Anybody got a clue?
Click to expand...
Click to collapse
Can you provide the play store links of this apps?
I would try and test it.
This apps are enabled in protected apps?
flupke02 said:
Transparent clock & weather: Most of the time, the clock does not keep track of the time, it just hangs. Only when I tap the widget, or refresh the weather, it syncs with the internal clock, like it should. Sometimes though, the clock does keep track for a short time, but in the end it will hang again.
Click to expand...
Click to collapse
I have test this app.
I think you mean this app: https://play.google.com/store/apps/details?id=com.droid27.transparentclockweather
I was able to reproduce your problem and solve it.
Please set this app as "protected app". You didn't have set it, so the app would be closed then the screen get off.
You can set this: Settings -> Protected Apps -> Check the checkbox of this app.
Then your widget is working.
Then an app don't set up as protected, the app would be closed on screen off.
DJ BlackEagle said:
I have test this app.
I think you mean this app: https://play.google.com/store/apps/details?id=com.droid27.transparentclockweather
I was able to reproduce your problem and solve it.
Please set this app as "protected app". You didn't have set it, so the app would be closed then the screen get off.
You can set this: Settings -> Protected Apps -> Check the checkbox of this app.
Then your widget is working.
Then an app don't set up as protected, the app would be closed on screen off.
Click to expand...
Click to collapse
Thanks for your help, I already tried that out before. It do not think it made a difference though. Anyway, the time freezing issue also happened when using the phone for some time, I mean without screen off time, so it should not make any difference. But in the meantime I updated the app, and that seems to work.
The links for the other apps:
https://play.google.com/store/apps/details?id=org.withouthat.acalendarplus&hl=nl
https://play.google.com/store/apps/details?id=com.levelup.touiteur&hl=nl
I contacted the developer of Acalendar+, and as far as I understood there should be an update coming in the near future that should resolve the problem. I installed another calendar app in the meantime, which just works flawlessly, so maybe I just stick to that one...
I hope Plume gets a working update too, so I can enjoy me phone without being annoyed
Thanks again for your effort!
flupke02 said:
Thanks for your help, I already tried that out before. It do not think it made a difference though. Anyway, the time freezing issue also happened when using the phone for some time, I mean without screen off time, so it should not make any difference. But in the meantime I updated the app, and that seems to work.
The links for the other apps:
https://play.google.com/store/apps/details?id=org.withouthat.acalendarplus&hl=nl
https://play.google.com/store/apps/details?id=com.levelup.touiteur&hl=nl
I contacted the developer of Acalendar+, and as far as I understood there should be an update coming in the near future that should resolve the problem. I installed another calendar app in the meantime, which just works flawlessly, so maybe I just stick to that one...
I hope Plume gets a working update too, so I can enjoy me phone without being annoyed
Thanks again for your effort!
Click to expand...
Click to collapse
Oops, I just found out you were right about the protected apps thing. I have not had the issue with the screen active since the last update, but indeed, after screen-off time, the issue is back again. So I guess I should indeed use the protected apps setting.
I don't understand why this is necessary though. I mean, the internal system clock just carries on ticking in standby mode, so why wouldn't the app just sync with that automatically when I activate the screen? Or would it be so that the app has always been active in standby mode on my old phone, and is it only because I now have this protected apps mode on this new phone that I am getting aware of this? If you understand what I mean, this is quite hard for me in English...
flupke02 said:
Oops, I just found out you were right about the protected apps thing. I have not had the issue with the screen active since the last update, but indeed, after screen-off time, the issue is back again. So I guess I should indeed use the protected apps setting.
I don't understand why this is necessary though. I mean, the internal system clock just carries on ticking in standby mode, so why wouldn't the app just sync with that automatically when I activate the screen? Or would it be so that the app has always been active in standby mode on my old phone, and is it only because I now have this protected apps mode on this new phone that I am getting aware of this? If you understand what I mean, this is quite hard for me in English...
Click to expand...
Click to collapse
I've experienced similar issues. Like you I use aCalendar+ which is very good. However I don't use any of the widgets that come with this app. I prefer Smooth Calendar instead. So far, no problems at all. And as for the clocks, it seems a bit hit and miss. I was using DIGI Clock Plus but had no end of trouble with it. It just won't update on wake up. Protected or otherwise. I've given up on it. The clock widgets from HD Widgets work just fine. There's an amazing array to choose from. Maybe it's an Android issue, maybe Huawei. Who knows? I think the best solution is to find apps and widgets that work and discard those that don't.
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.