So there's this app I like using called whisper.
Occasionally it would have this bug that made it unusable. The only way to fix it was to clear cache, delete all the folders it creates(it creates a folder on the root of your phone where it stores your account data[I'm assuming]), and reinstall.
Recently I got this bug again and I can't fix it. And I'm positive it has to do with the fact that it's my phone as it works perfectly on everyone else's phone and on emulators.
So what I'm saying is if I completely wiped and factory reset my phone I'm sure it would work again. But doing that and setting everything back up is extremely annoying. I want to delete all previous traces of this app on my phone so I could do a completely clean install and hopeful solve the bug.
Almost like a targeted factory reset. So in the eyes of the app my phone would be completely new.
I've tried almost everything including wiping my ART cache to deep searching my root for the app name and deleting all the folders returned to changing my device I.D. and IMEI
tldr; How to delete all previous traces of a specific app, almost simulating a factory reset as far as the specific app is concerned.
Related
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.
Hello again.
I'm experiencing a new problem with my phone that is becoming very aggravating because it seemingly occurred when I did nothing unusual or risky with my phone. Every time I update an app in the google play store, my phone locks up and will reboot itself. Sometimes it will remain frozen until I hold down the power button myself. This problem also happens when uninstalling apps and installing apps, but it doesn't do it regularly. Sometimes it works, sometimes it doesn't. But the phone will always freeze when updating apps. Like I said, I have done nothing risky with the phone. I haven't installed or removed any apps that require superuser access. I haven't downloaded anything to my phone. All I have done is install a few apps here and there from the store, evaluate if I like them or not, and decide if I want to keep them. Recently I haven't been keeping new ones, so I promptly remove them. Out of nowhere this problem shows up when I tried to install another app (thought maybe the app caused it so I got rid of it), and now the updates freeze my phone.
The apps successfully update each time, but immediately after the process finishes, the phone locks up. After rebooting, the updates are saved and the apps aren't corrupt or anything. What can be causing this to happen? Everything on my phone was working flawlessly, and now this problem is seriously hindering the usability of my phone and I don't understand what went wrong.
My phone is the Virgin Mobile Samsung Galaxy S2 4G SPH-D710. It is rooted and is running the stock ROM.
Any help would be appreciated.
Britt47 said:
Hello again.
I'm experiencing a new problem with my phone that is becoming very aggravating because it seemingly occurred when I did nothing unusual or risky with my phone. Every time I update an app in the google play store, my phone locks up and will reboot itself. Sometimes it will remain frozen until I hold down the power button myself. This problem also happens when uninstalling apps and installing apps, but it doesn't do it regularly. Sometimes it works, sometimes it doesn't. But the phone will always freeze when updating apps. Like I said, I have done nothing risky with the phone. I haven't installed or removed any apps that require superuser access. I haven't downloaded anything to my phone. All I have done is install a few apps here and there from the store, evaluate if I like them or not, and decide if I want to keep them. Recently I haven't been keeping new ones, so I promptly remove them. Out of nowhere this problem shows up when I tried to install another app (thought maybe the app caused it so I got rid of it), and now the updates freeze my phone.
The apps successfully update each time, but immediately after the process finishes, the phone locks up. After rebooting, the updates are saved and the apps aren't corrupt or anything. What can be causing this to happen? Everything on my phone was working flawlessly, and now this problem is seriously hindering the usability of my phone and I don't understand what went wrong.
My phone is the Virgin Mobile Samsung Galaxy S2 4G SPH-D710. It is rooted and is running the stock ROM.
Any help would be appreciated.
Click to expand...
Click to collapse
Hi there,
Have you tried clearing the cache for Google Play Store in Application manager? Try this first! You could also try (I assume you also have a working CWM recovery or similar?) wiping cache and dalvik in recovery!
CarlM34 said:
Hi there,
Have you tried clearing the cache for Google Play Store in Application manager? Try this first! You could also try (I assume you also have a working CWM recovery or similar?) wiping cache and dalvik in recovery!
Click to expand...
Click to collapse
I've already wiped the cache, data, and even tried uninstalling updates for Google Play and Google Play services. Made no difference.
As for dalvik, I'm not sure what that means. Any pointers would be helpful!
Britt47 said:
I've already wiped the cache, data, and even tried uninstalling updates for Google Play and Google Play services. Made no difference.
As for dalvik, I'm not sure what that means. Any pointers would be helpful!
Click to expand...
Click to collapse
The dalvik cache will probably be under Advanced in Recovery
zj
I don't have CWM recovery. Sorry I didn't know what you meant when you asked that.
Sorry if bumping or double posting isn't allowed, but I wanted to update this thread.
I think I may have solved the issue. Makes no sense as to why it happened or how it's even related to what I did. I racked my brain for the most recent things I installed on my phone and the only app that came to mind was Cut the Rope. It was the last thing I could remember that installed fine. I removed it and nothing locked up. Then I tried updating one of my apps and presto. No freeze or reboot. Then I installed an app from the play store and it worked perfectly. Did it multiple times with no error. I feel like Android is so temperamental that if I even look at it wrong something will break. -_- I don't know. Maybe being rooted has something to do with it, but my guts don't want to believe it.
I'll put "solved" in the title once I keep using my phone and make sure it's working correctly. If so, I suppose the moral to this problem is just uninstall anything recent from your phone if you experience similar issues. Wish I could know the technical cause though.
Britt47 said:
Sorry if bumping or double posting isn't allowed, but I wanted to update this thread.
I think I may have solved the issue. Makes no sense as to why it happened or how it's even related to what I did. I racked my brain for the most recent things I installed on my phone and the only app that came to mind was Cut the Rope. It was the last thing I could remember that installed fine. I removed it and nothing locked up. Then I tried updating one of my apps and presto. No freeze or reboot. Then I installed an app from the play store and it worked perfectly. Did it multiple times with no error. I feel like Android is so temperamental that if I even look at it wrong something will break. -_- I don't know. Maybe being rooted has something to do with it, but my guts don't want to believe it.
I'll put "solved" in the title once I keep using my phone and make sure it's working correctly. If so, I suppose the moral to this problem is just uninstall anything recent from your phone if you experience similar issues. Wish I could know the technical cause though.
Click to expand...
Click to collapse
Lets hope you have it sorted now:good:
Hi,
I had a weird problem with an app (The Times and The Sunday Times) on my Xperia Z2 Tablet yesterday. Although I managed to fix it eventually, I was wondering if anyone might be able to shed some light on what happened.
The tablet had been repaired under warranty. Before I sent it off, I did a full Titanium backup, unrooted, and reset to factory defaults. As part of the repair, Sony updated the firmware from 17.1.1.A.0.402 to 17.1.2.A.0.314 (17.1.2.A.0.314 was released whilst it was out for repair). Both firmwares are based on Android 4.4.2.
I reinstalled all my user apps (not system apps) by restoring a Titanium backup, after which the The Times and The Sunday Times app was working. I used it several times, then yesterday it froze when loading. Killing the app from the recents and opening it again didn't work; this time it wouldn't load (the icon on the Nova Launcher desktop glowed for a few seconds, then nothing happened).
I then tried the following, killing the app from the recents menu before each attempt:
Clearing the app's cache.
Clearing the app's data.
Uninstalling the app and reinstalling.
Uninstalling the app, searching the entire device for the app name using solid explorer (rooted), removing any left over files, and reinstalling the app.
Uninstalling the app, running SD maid, and reinstalling the app.
Rebooting the device.
Still no luck. each time, the app icon would glow when i tapped it, the app would appear in my recent apps list as a black rectangle, but no matter how long I left it (several hours at one point), it just wouldn't load.
In desperation, I restored the app's Titanium backup with data, and it (sort of) worked. The app loaded, and allowed me to log in again (as if I'd just done a fresh install, or restored the app without data).
The weird thing is that the app has not been updated since I made the backup, so the backup version is the same as the version on the Play Store.
Does anyone know why restoring the Titanium backup would work where the troubleshooting steps I took above didn't? Is it possible that the app's data got given some weird permissions at some point that only Titanium, running as root, could sort out?
Thank you in advance!
Looking at the logcat might offer some insights into why it was not launching.
An educated guess would be that TiBu restored/overwrote a file that the other apps/system did not find and wipe and the app itself corrupts a file when launching and only restoring a working one from your backup fixed it.
If you find out what file that is, SD Maid could be updated to cover that and if it's reproduceable, you could also write the dev of the app instruction how to reproduce the issue so he can fix it.
Of course there is always the option that the server/connection was bad and it hang because of that.
Believe me, I've done many Google researches but I still cannot find a definitive answer to this subject.
When we uninstall an app using the following method: [force close - delete data - uninstall] does android allow the app to leave any data on the phone beside that left on the SD?
Please note that I'm referring to android 4.3 in, this particular case.
Well, I don't think that any data is left over once you uninstalled most of the data gets cleared up and some remains over the phones temporary files, I would say if you clear that one out to, nothing will remain everything will washed out !
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?