I have the problem that when I lock an app, I can close it anyway by swiping it to one side of the screen.
Does anyone have the same problem and knows a fix?
Maybe I can fix it by delete Cache or Data of a Systemapplication?
Related
I have the above named phone & it has started to be hgorribly sluggish when moving an application, back to any of the home screens. Delays of 8 to 10 secdonds while the application icons are displayed have become common.
I deleted a whole piles of downloaded apps in case this was a problem related to capacity. No change.
I did a 'BACK TO SYSTEM DEFAULTS' change. No different.
Anyone else seen this problem ? If so, what is the solution ?
Thanks
Sorry. I meant its is sluggish when moving 'from' an applciation back to the home screen. Bad typing. Sorry.
Has the phone still got the original VF ROM?
Have you tried clearing all the application caches?
Would post a link but not allowed. Search google for "clear application cache htc magic"
Hi,
Settings>applications>manage applications
press menu, then 'sort by size'
clear cache for the first few apps and you should notice an increase in responsiveness.
I recently began using WidgetLocker. However, When I slide the keyboard out when the display is off, WidgetLocker force closes.
I'm running Bonsai Leafless 1.0.2, Gingerbread 2.3 theme, LauncherPro and WidgetLocker when the force close occurs. Is anyone else experiencing this issue? Is there a fix?
Thanks in advance for any assistance.
Can anyone confirm this issue or is it something with my settings?
well i am running midnight ext4 v2.4 with LP and WL and I have no issues when I open the keyboard with the display off, the screen come on and WL is in Landscape.
happens to me 2 i stopped using it.
I think I *may* have found the issue. I'm not sure if it's the ROM, the theme, or some of my settings...
WithOUT WL running...
When I slide open my keyboard, it brings me to my home screen and bypasses the lock screen.
With the keyboard "closed", when I press the power button it brings me to my lock screen. If I slide out the keyboard while at the lock-screen, it bypasses the lock and brings me to my home screen.
I didn't find a setting for this in the phone settings or within Spare Parts. I guess I'll have to wipe and reflash the ROM and take it one step at a time to track down the problem.
I have been having the same problem with WL. I use GoSms to display incoming text messages on my lockscreen and i've noticed if my phone moves into landscape mode while displaying the text, WL force closes. I have tried the settings within WL to force portraid screen orientation but it didnt solve the problem
Yeah getting FC's on my R2D2 as well. Every time i slide the keyboard or set the phone in the dock. Hoping a fix comes soon.
It seems the location of the search button and the installed app icon are so close to some of the ads on the page it has made if very difficult to select those icons.
Is me and my not so fat fingers that are the problem or is there anyone else that is having this issue?
Thanks,
I don't see any ads?
Anybody using widgetlocker for a lock screen replacement, I know we know have lockscreen widgets (tho it seems only about 4 to choose from) but what I love being able to set is shortcuts for gmail, phone and messaging right there and have support for unread messages/missed calls with telsa unread.
Anyway the problem I have is that widgetlock doesn't seem to disable the soft keys (like the stock lockscreen does) so basically I can just bypass unlocking. Anybody have a work around, I know this isn't the first device with softkeys so this must have been a problem that as come up before.
NVM, root helper and 'hide navigation keys' got rid of the soft keys, only problem now is it is just so laggy/unresponsive to touch, takes several attempts to unlock. Hopefully this is just a bug with 4.2 devices and they will fix it soon.
I got a problem w/widgetlocker and the multitask softkey. When I go to the lockscreen, it takes a second for the multitask softkey to appear while the back and home keys are lighted automatically. It just happened today..does anyone w/widgetlocker experience that problem? I wonder if there's a way to fix it and it's starting to bother me.
Every time I press the mic button on the keyboard and try voice typing, the typing works but then the whole system UI stops responding to touch. I can't do anything inside any app or even in the main screen, only the physical buttons and touch within the lock screen works. Afterwards I have to access the shutdown menu from the lock screen (or use the button combination) in order to restart the device and restore touch response.
Is there a known issue with the Google Voice Typing in the device, or is it caused by some Xposed module or something?
The device is I-9300i running stock Androod Kitkat 4.4.4 Rom.
Nawarelsabaa said:
Every time I press the mic button on the keyboard and try voice typing, the typing works but then the whole system UI stops responding to touch. I can't do anything inside any app or even in the main screen, only the physical buttons and touch within the lock screen works. Afterwards I have to access the shutdown menu from the lock screen (or use the button combination) in order to restart the device and restore touch response.
Is there a known issue with the Google Voice Typing in the device, or is it caused by some Xposed module or something?
The device is I-9300i running stock Androod Kitkat 4.4.4 Rom.
Click to expand...
Click to collapse
Hi!
I had similar problems with other stock apps of android KitKat, sometimes I solved the problem deleting the app cache, in your case you can try to delete the cache of the app called Google text-to-speech. If it doesn't work try also to delete the cache of the keyboard that you're using (stock Samsung keyboard or any custom keyboard downloaded from the store).
Let me know if works!
CoDed99 said:
Hi!
I had similar problems with other stock apps of android KitKat, sometimes I solved the problem deleting the app cache, in your case you can try to delete the cache of the app called Google text-to-speech. If it doesn't work try also to delete the cache of the keyboard that you're using (stock Samsung keyboard or any custom keyboard downloaded from the store).
Let me know if works!
Click to expand...
Click to collapse
Sorry for abandoning the post. The issue resolved itself without any interference, so I can't tell whether clearing the cache helps or not. Thanks for responding anyway.