All apps, after one opening (meaning reading or browsing for some article) gets corrupted cache. on the second opening of the app nothing shows, it just repeat some random GUI asset over and over again.
if I then close the app, clear the cache and reopen it all seems to work fine.
This is not isolated to one app in particular, spanning from Google (after one search from the home screen I have to clear the cache or I can't search for anything else);
The Guardian, The NYTimes etc.
Related
Every since switching over to Vegan7.1, I have had problems with only news applications force closing immediately. I am from MI, so it applies to Detroit News, Free Press and MLive. I have cleared their individual caches and data, reinstalled and still nothing. My guess is they think I am on another device and don't like the resolution? Any suggestions?
I'm on MeanBean (not sure how this applies to other ROMS).
It was failing 99.99% of the time over Bluetooth.
I just tried uninstalling Google Search with Titanium Backup.
Then Reinstalling from Google Play Store.
Still Broken.
Then I Cleared Data on Google Search, Rebooted to recovery and Cleared Cache (thinking some BAD learned data might be the cache).
BINGO It works perfect OVER Bluetooth now.
I don't know if it was the, clear data, reboot or the clear cache but these steps absolutely fixed it.
Uninstall With Titanium Backup.
Install from Market.
Go to Apps and Clear Data (again this might clear corrupt learned data).
Boot to recovery, Clear Cache.
Reboot
I tried 5 names that would COMPLETELY fail before.
I can't say if this will stick for good, but it looks promising.
That's it.
Read Posts below...
Wait !!!
It stopped working.
I swear it worked perfectly !!! for 5 minutes.
I put the phone down to write this post.
Picked it up and said the SAME names and now they completely miss.
I wonder if it rebuild the bogus lookup table or something again.
Yeah, the Google Now voice dialing is pretty poor.
Apparently moving the app from a system app to a data app should give you the option of using either GNow or the stock Voice Dialer (at least it did on ICS). Is the stock Voice Dialer included in the build?
My device is bricked currently, so I can't check/test.
Captain_Throwback said:
Yeah, the Google Now voice dialing is pretty poor.
Apparently moving the app from a system app to a data app should give you the option of using either GNow or the stock Voice Dialer (at least it did on ICS). Is the stock Voice Dialer included in the build?
My device is bricked currently, so I can't check/test.
Click to expand...
Click to collapse
I don't think the old search is included but that might allow a 3rd party app to work.
Sorry to hear about your bricking.
Well at least I found a pattern...
More Info...
It's the clear cache that momentarily fixes it.
Works every time.
Reboot to Recovery
Clear Cache
Reboot
Voice Dial Over Bluetooth Works every time using say 3 different names.
Wait a minute and then it will fail with the SAME names no matter how many times I say it.
This is STRICTLY Bluetooth. Handset works fine.
My guess is when I reboot with cleared cache, it skips using the optimized search database. Because it always pauses when it works after I say the name.
I think the search database is somehow only compatible with the handset.
Once the search database is built the Bluetooth then uses it and fails from there on.
Clearing Data or Cache from the Apps Settings seems to have no effect. But clearing cache from Recovery does. It might be that when I do it from recovery there is an implicit reboot too. But Force Close, Clear Data, Clear Cache will not bring it back.
Ok here's the thing. I downloaded the new version of Falcon Pro (the one that is not available anymore on the play store), I did the procedure to find out how to have a token, everything was fine. Once I logged in the app closes itself. Anytime I open it, it stays opened like for 1-2 sec and then it closes. There's no crash log because, I think, it's not an actual crash. It works just fine from the widget: I can open the tweets from the widget, but if I try to open the main page of my feed (from anywhere, widget or other apps) it stays open for a moment and it crashes (or closes). In one of these moments I have been that fast to be able to tap on settings and send a bug report to the developer. I tried already to reinstall the app, clean the cache, clean app's data, fix permissions, clean dalvik cache, uninstall other twitter apps... nothing worked!
Any ideas?
PS: I don't if I was clear enough; long story short: the problem seems to be related just to the main page!
PS2: I am on CM 10.1-20130720-NIGHTLY-i9100
same problem here
dariodejaneiro said:
Ok here's the thing. I downloaded the new version of Falcon Pro (the one that is not available anymore on the play store), I did the procedure to find out how to have a token, everything was fine. Once I logged in the app closes itself. Anytime I open it, it stays opened like for 1-2 sec and then it closes. There's no crash log because, I think, it's not an actual crash. It works just fine from the widget: I can open the tweets from the widget, but if I try to open the main page of my feed (from anywhere, widget or other apps) it stays open for a moment and it crashes (or closes). In one of these moments I have been that fast to be able to tap on settings and send a bug report to the developer. I tried already to reinstall the app, clean the cache, clean app's data, fix permissions, clean dalvik cache, uninstall other twitter apps... nothing worked!
Any ideas?
PS: I don't if I was clear enough; long story short: the problem seems to be related just to the main page!
PS2: I am on CM 10.1-20130720-NIGHTLY-i9100
Click to expand...
Click to collapse
It happens to me too. Please help!!!
Best bet would be to ask the developer directly (on Twitter).
On OOS 3.1.3 there has been some initial speculation about getting google play services to work correctly, but many have figured out how to work around this by just clearing data etc.
However, I believe I've found a bug when downloading apps which are deemed as "Large Apps", which prompts the box saying whether you would like to download over Wifi or not.
During the download, it will freeze, and if you wait long enough, a box will pop up stating that you have background data restricted for google play and it needs it to function.
For me, on smaller apps when downloading them this does not occur.
In the screenshot attached you can see I was trying to download an app, when it got to around 90% or so, this popped up.
In my data usage -> 3 dot menu -> restrict background data are both set to off on Mobile Data and Wifi. Likewise, google play store under data usage has no restrictions either.
I have made sure that sync is all configured correctly, cleared play store/services data and cache, and the whole cache in recovery but with no result.
Can anyone else relate to this? I'm unsure how to fix it/find a (temporary) work around
Alright, so I copied 1 million digits of Pi to my v60's clip tray (for educational purposes), and now it restarts when I open the keyboard. I have uninstalled or disabled every clipboard/keyboard related app I can find, including the stock LG keyboard (using adb shell pm uninstall --user 0 com.lge.ime). I have restarted the phone, used the Smart Cleaning app to clear memory and temp storage, and copied other (much shorter) phrases to the clipboard in an attempt to clear Pi from the clipboard history.
Evidently, something in the phone has stored Pi in some sort of history or backup, and now every time I open the keyboard (now using AnySoftKeyboard), it waits about 15-30 seconds, then stutters, freezes, crashes, and restarts.
What can I do, barring a factory reset?
Edit: I tried rebooting into safe mode, and it still crashed upon clicking a text input field, even though AnySoftKeyboard didn't come up (since it's not a system app).
This is probably to late as you probably have figured it out by now, but for the next person who has this issue , try this. Go to settings, then apps, find the keyboard app , and go into storage and delete all its data.
I actually believe I tried that, and it didn't fix the issue. Eventually, the issue just went away - I think I had copied enough unique strings in normal usage that it just pushed Pi out of the clipboard history.
Any update to this at all?
Welcome to XDA
I've seen this happen. Been a long while. Clearing the cut/paste data using the Edge Clipboard may be how I solved it. It wasn't anything drastic. Also try clearing the system cache from the boot menu as that can resolve many strange issues.
How would I clear the system cache, and what exactly is the Edge clipboard?