So I am not getting ideal battery life on ElementalX kernel with the stock ROM 6.0.1. I installed the free version of Wakelock Detector. Then I converted it to a system app from within the app itself. Now the app doesn't work anymore with the error "Failed to perform this task at the moment, try again later" as a toast message. Then I tried to uninstall it with Titanium Backup Pro. TB says "Cannot remove system app. Failed to locate the apk file." I can, however, freeze the app OR disable it from settings>apps.
Then I tried to purchase the full version and I have the same exact issue with that version.
Other things I tried:
Cleared the cache and Dalvik
Cleared the app data
Checked for the app in Device Administrators, they arent listed in there.
At first TB seemed to uninstall it fine but the app was still in the app drawer.
I'm going to go berserk if I have to clear my data and restore all my apps and settings. Hours lost. Any assistance is greatly appreciated.
Try reflashing system
Sent from my Nexus 5X using Tapatalk
Use a root explorer to delete the apk file and reboot. Should be sufficient.
Apk should be in /system/app
Had the same problem. WLD was giving me a constant Android OS wakelock. Used root explorer to find the apk and delete it.
https://play.google.com/store/apps/details?id=com.speedsoftware.rootexplorer
Sent from my Nexus 5X using Tapatalk
Thanks fellas!
I never actually had to delete an app this way. I searched for the entire name of the apk, com.uzumapps.wakelockdetector using root explorer, a staple app of mine nearly since day 1 of my android love affair. After that I deleted the 2 folders that came up and all files in the dalvik. Then I wiped both caches and there seems to be no trace of the 2 apps anymore. One thing to note is that it was not located in /system/app. And I'm an idiot because I didn't note the directory that it was actually in.
Related
So I flashed a custom theme here http://forum.xda-developers.com/showthread.php?goto=newpost&t=1803273 and I flashed it over wicked r5.
I also also installed another zip from there to change the jellybean messaging app to the stock touchwiz.
It worked but randomly I get a Unfortunately messaging has stopped error.
Try clearing your cache or fixing permissions. Also, it might just be a bit too much tweaking.. Hopefully you can get it to work.
Sent from my SGH-T999 using xda premium
Every time ive seen that doing a factory reset has fixed it.
BACK UP YOUR INTERNAL SD FIRST!!!
Good luck!
Edit: try daves suggestion first though!
Sent from my SGH-T999 using xda app-developers app
DocHoliday77 said:
Every time ive seen that doing a factory reset has fixed it.
BACK UP YOUR INTERNAL SD FIRST!!!
Good luck!
Edit: try daves suggestion first though!
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Yeah, I spent a whole day trying to fix this, in the end had to do a factory wipe.
Corrupt sms / mms database
This has to do with a corrupt db file. It can either happen if something goes wrong with titanium backup/restore process. Or also if you manually copy these files from another older backup (when an older android was installed).
First backup the existing sms/mms with smsbackup from appstore. It is free.
With an explorer app like ESFile explorer, go to "/data/data/com.android.providers.telephony/databases" (or something similar in your phone where the sms / mss .db files are located).
Make a backup of the files here and then Delete all the files.
Then restore the sms from smsbackup app. Voila ! No crash anymore
No need to do a factory wipe.
If everything works fine, you can delete the backup folder containing the old db files.
FYI: After upgrading to Wicked's v.7 I stopped getting these errors. Been a week so far with no probs.
genardas said:
So I flashed a custom theme here http://forum.xda-developers.com/showthread.php?goto=newpost&t=1803273 and I flashed it over wicked r5.
I also also installed another zip from there to change the jellybean messaging app to the stock touchwiz.
It worked but randomly I get a Unfortunately messaging has stopped error.
Click to expand...
Click to collapse
Hi please see http://forum.xda-developers.com/showthread.php?p=27695693 ..... it may be related to your CSC. Or alternatively (in my case) I had mistakenly frozen the system app "BadgeProvider" using Titanium Backup. Constant "Messaging has stopped" kept coming up until I unfroze BadgeProvider.
shriramrs31 said:
This has to do with a corrupt db file. It can either happen if something goes wrong with titanium backup/restore process. Or also if you manually copy these files from another older backup (when an older android was installed).
First backup the existing sms/mms with smsbackup from appstore. It is free.
With an explorer app like ESFile explorer, go to "/data/data/com.android.providers.telephony/databases" (or something similar in your phone where the sms / mss .db files are located).
Make a backup of the files here and then Delete all the files.
Then restore the sms from smsbackup app. Voila ! No crash anymore
No need to do a factory wipe.
If everything works fine, you can delete the backup folder containing the old db files.
Click to expand...
Click to collapse
Thanks I tried restoring one too many things related to SMS with titanium backup which screwed up the messaging app, I wasn't able to receive or read msgs. Your solution worked, I just had to reboot after deleting.
If you rooted your phone, anyone, and you deleted or renamed some system apps to stop them loading then you could face problems with the SMS Messaging app.
Just make sure the system app "WebViewGoogle" is left intact (in the folder data/system/app)
If you deleted it then put it back in, if you renamed it (e.g. from "WebViewGoogle.apk" to "WebViewGoogle.apk.old") then name it back to "WebViewGoogle.apk"
This app must be intact for the Messaging app to work. properly.
I'm starting to get an "Out of space" message when installing apps. It happened a couple of times from Market, and now its happening when I side load apps. From all indications I have plenty of space (11 GB free). I've cleaned cache, force stopped Market and Google Frameworks clearing their cache, rebooted into recovery and wiped cache, wiped dalvic, and fixed permissions. Its getting to the point that Market updates are hit and miss as to whether they will install. Is this a RAM issue? What can I do next? Running JR6 w/ Franco #264. Thanks.
v12xke said:
I'm starting to get an "Out of space" message when installing apps. It happened a couple of times from Market, and now its happening when I side load apps. From all indications I have plenty of space (11 GB free). I've cleaned cache, force stopped Market and Google Frameworks clearing their cache, rebooted into recovery and wiped cache, wiped dalvic, and fixed permissions. Its getting to the point that Market updates are hit and miss as to whether they will install. Is this a RAM issue? What can I do next? Running JR6 w/ Franco #264. Thanks.
Click to expand...
Click to collapse
Check if you have a .odex file in /data/data (from Titanium Backup)
if you do, delete it. That caused some issues for me.
Sent from my Galaxy Nexus using xda premium
Thanks for the suggestion. I do use TiBu but seaching with Root Explorer, I did not have any odex files in that folder. I do have less than 20 odex files total, most located in the /data/app/ folder, ranging in size from a few kB up to 3 MB. Are they safe to delete? Not even sure if I go back to an earlier nandroid, I may still end up with the same problem. Its not crippling at the moment, so I'll hang on for a while to see if there are any other ideas I can try before wiping and reloading.
EDIT:
OK, one of the odex files in the /data/app folder was from the program I could not install. I deleted it, and was then able to install the program. WTH? I tested deleting one of the other odex files (to see if I could just delete them all) and the program would just FC immediately. I guess the only odex files that are safe to delete are of apps you no longer use. Not sure why the odex file kept me from installing the program, but at least it is fixed. Thanks to Lesicnik1 for putting me on the right track. Cheers.
So, here's the deal. Last night I decided to flash one of the 4.2 ROMs to my VZW GNex. I tried doing a restore with TiBu, and afterwards Gmail and the Play Store kept force closing, so I ended up formatting cache, dalvic, and data, and installing the latest Cyanogenmod nightly. I realized that maybe my TiBu restore was wonky, so I'm just starting from scratch this time.
My question is this: Even though I'm back on 4.1.1 now, I have what looks like a second copy of my SD Card on my SD Card in the form of the 0 directory. What can I do about this? Can I delete the 0 folder? Where are the system files located now? I'm afraid that if I flash a 4.2 ROM again that I'll have 4 identical folders instead of 2, and I'll be out of memory.
Sent from my Galaxy Nexus using Tapatalk 2
It should be possible to delete it yes.
Sent from my i9250
JuanOfMany said:
So, here's the deal. Last night I decided to flash one of the 4.2 ROMs to my VZW GNex. I tried doing a restore with TiBu, and afterwards Gmail and the Play Store kept force closing, so I ended up formatting cache, dalvic, and data, and installing the latest Cyanogenmod nightly. I realized that maybe my TiBu restore was wonky, so I'm just starting from scratch this time.
Click to expand...
Click to collapse
wait, you went through all that because the play store and gmail were force closing? i hope that you first tried deleting the app data from the play store and gmail, and tried fixing_permissions first. usually there are easy ways to fix things instead of wasting time starting over from scratch. even deleting both apps and reinstalling them would be much easier.
upgrade to 4.2 using this guide and you will keep the old sdcard format.. no more"0" folders
http://forum.xda-developers.com/showthread.php?t=1999214
Well, I did try deleting the app data for Gmail, but I don't know how to fix permissions. I suppose I should look into that next time I have this problem.
Regarding the duplicate data, which set is being used? The set in the home directory? Or the data set in 0? I don't want to delete the wrong data, of course.
Sent from my Galaxy Nexus using Tapatalk 2
JuanOfMany said:
Well, I did try deleting the app data for Gmail, but I don't know how to fix permissions. I suppose I should look into that next time I have this problem.
Regarding the duplicate data, which set is being used? The set in the home directory? Or the data set in 0? I don't want to delete the wrong data, of course.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
delete the "0" folder you shouldnt have any issues
The /0 folder? Seems like that's where all my data is now. Should I copy folders over to sdcard0 first? If I install another 4.2 based ROM, will I end up having a sdcard0/0/0 directory?
Wait.. Never mind. It seems that the /0 folder is missing now. I must have fixed it by accident or something.
Sent from my Galaxy Nexus using Tapatalk 2
Here is my situation I came from Android rom 4.1.2 then upgraded to 4.2(gave me problems) downgraded to 4.1.2 and I am having "0 file folder" I was wondering if I can move the files/folders that is currently in "0 folder" into the regular internal storage folder.
Here it is visually I currently have [Computer>Galaxy Nexus>Internal storage>0](folder with all my data)
can it be just [Computer>Galaxy Nexus>Internal storage](with all of the data moved from "0 folder")
I have 2.6gb free, and I cannot install or update any apps. insufficient storage keeps popping up. Is there a fix for this on the Galaxy S4? I am running stock rom and kernel, just rooted.
Have you tried a reboot? Or clearing data on the play store app?
Sent from Flip's Galaxy S4
yep, tried clearing data and cache from playstore, and google frameworks. Rebooted into recovery, wiped dalvik. Uninstalled and freed up to 4.6gb of space and it still says insufficient storage.
This is a bug that showed up for me in JB and I think it has to do with rooting as well (not sure).
(HINT - The error is really not insufficient storage but this is the only error code that playstore understands...)
But here is the fix-
1. Use a root explorer and go to /data directory
2. (I'm on conference call right now so I cannot verify the dir names but they should be close) Go to the applib and the data directories (/data/applib and /data/data), there ought to be folders of the app that you cannot install, just delete them and go back to the playstore and install the update.
3. If there error still there then, go to /data/app as well, and delete the app completely.
4. WARNING, you will (may) lose the settings for whatever app you have error with, so you may want to backup the app beforehand and then restore the app (data only) after doing all of this.
Lolento said:
This is a bug that showed up for me in JB and I think it has to do with rooting as well (not sure).
(HINT - The error is really not insufficient storage but this is the only error code that playstore understands...)
But here is the fix-
1. Use a root explorer and go to /data directory
2. (I'm on conference call right now so I cannot verify the dir names but they should be close) Go to the applib and the data directories (/data/applib and /data/data), there ought to be folders of the app that you cannot install, just delete them and go back to the playstore and install the update.
3. If there error still there then, go to /data/app as well, and delete the app completely.
4. WARNING, you will (may) lose the settings for whatever app you have error with, so you may want to backup the app beforehand and then restore the app (data only) after doing all of this.
Click to expand...
Click to collapse
I used to get such errors even on a custom firmware based off Sprint's stock Evo 3D ice cream sandwich image... wish I would've known this sooner. (I also used app2sd and even though I had like half of my SD card left it would still toss up this error.)
Hello!
I recently get this error probably after I rooted my device, whenever I try to download something from play store. When I click install or click accept (after clicking install) I get this error (10/10 cases). Then I keep getting it on a random basis. I deleted the data and cache (even rebooted between each one), then went to play store. It shows the apps and works for a long period of time (but eventually shows the error). But when I try to download something, I happens again. I checked the Download Manager and it is enabled.
I had backed up the play store using Titanium backup, then wiped its data and then uninstalled it from the system. Don't ask why lol.
But when I tried to restore it, Titanium backup was stuck at its progress. Then I had to place the APK of the backed up play store (the updated version of the play store (5.0.31) not the factory version.) in the /system/apps/ and set the rx- r-- r-- permissions. I checked the Titanium backup backup file and apparently it had some data for the data/data path. So I manually put it there and set the permissions like any other folder that is there. Keep in mind that I tried to reboot in between each attempt.
I used OpenVPN to access it but no luck.
Tried to delete dalvick-cache folder, but that didn't fix it neither.
Booted into safe mode, cause I thought maybe some of the applications are causing this like Xposed, Greenify and SetCPU (which I uninstalled just in case). This again didn't do it.
I rooted the device with Kingo root using a pc.
Android is 4.4.4.
My only guess left is that I should find the factory version of the Google Play that was installed?
As you can see I'm kind of running out of options here.
Could somebody offer an advice besides factory reset and being careful next time??