Related
[TIP/TRICK] Stop Stock Gallery From Creating .thumbnails Folder! Save SD Card Space!
First off, I'll start by saying: "I am not responsible if you brick your phone! Always make a nandroid backup before using my steps/messing with Autostarts! (It's a very powerful application!)"
If you use a 3rd party gallery app (Like QuickPic, my personal favorite...) - You are probably tired of wasting over 100mb of space on your SD card... (And waiting a long time for booting up as well...) I had no need for the /sdcard/DCIM/.thumbnails folder taking up space on my SD card, so this is how to disable the stock Gallery app from doing so!
I researched a little on how to accomplish this and came up with little information, so I thought I'd share:
What you'll need:
1.) Autostarts app (I used: Version 1.7.0)
---
Steps/Directions:
1.) Run Autostarts
2.) Look for these entries: Media ejecting/mounted
3.) Choose either entry (ONLY CHOOSE ONE, IT DOES NOT MATTER WHICH! Choosing one entry will disable both entries in Media ejecting AND Media mounted!)
4.) Click on BootReceiver
5.) Choose Disable (A popup will show saying "This is a system app, are you sure? etc.)
6.) Done! Reboot. On boot, go to /sdcard/DCIM/ and look inside for the usual .thumbnails folder, it should be contained with a few (SMALL) files now!
Note: (Make sure you disable the entry BootReceiver ONCE, it should "strikeout" (as in: draw a line through) the entry BootReceiver, to show it has been disabled on boot.) - zmag
Hmm, seems I just looked in my folder and I saw the darn .thumbnails file again... If anyone knows how to disable the stock Gallery app from wasting boot time & sd space; PLEASE TELL ME!!! - zmag
Well, it looks like this is not a big issue for anyone out there - but it still annoys me.
I have since "frozen" the stock Camera and Gallery apps with Titanium Backup Pro, and still; no luck.
Now, granted when I reboot my phone and look in my DCIM folder it doesn't seem to be creating the .thumbnails folder 100% of the time. But the folder is still being created somehow, and my only guess is from a third-party app (and I can't seem to pinpoint which one) but I'm gonna test to find out which and post my results...
I wish someone out there could give me some input, I've been talking to myself here for too long. - zmag
This isn't the same, but you can create a filetype named '.nomedia' and place it at the root of the folder where you want and it will stop displaying the thumbnails in the gallery app.
http://smartadopter.wordpress.com/2...mbnails-showing-in-the-android-photo-gallery/
OK I believe I may have found the possible solution to this problem.
I was searching around on how to fix this problem as well, and tried a few things myself and believe I have found a solution, so I had to sign up for xda to share with everyone else. So please be gentle as this is my first post, although im a long time lurker.
I also got rid of the stock gallery (uninstalled with Titanium Backup) and now use Quick Pic. although I have removed the stock gallery it still builds that 60mb+ thumbnails directory on my SDcard. I was using SD Maid to delete it but it gets annoying that it kept reappearing even after the uninstall of stock gallery.
Now to start fixing,
I realized it was actually a large single file itself named ".thumbdata3-1967290299" in "sdcard/DCIM/.thumbnails/" that was taking up the 60mb+ , the smaller individual thumbnails Quick Pic created only added up to a 1mb or so.
So what I did was I just grabbed a random useless file from my SD card I didn't need anymore (an alarm clock plus backup .bak file, but I would assume the *new file" option in root explorer would do the same) and I renamed the unneeded file the same name as the file in /.thumbdata/ (the the .thumbdata3-19672902099).
Now I had a .thumbdata file that was only 1.75kb and just simply moved it to the sdcard/DCIM/.thumbnails/ folder and replaced the 60mb .thumbdata file with the smaller one.
After a few restarts of my phone, opening and browsing Quick Pic, checking my thumbnail size a few times with both SD Maid and Root Explore - I now have a much smaller 1.75kb file instead of the old 60mb file.
Hopefully this well help some of you out and solve your problem as well, as far as I can tell it is no longer making that thumbnail file expand so large on my phone.
Phone: HTC Hero CDMA
ROM: Cyanogenmod 7.1
Carrier: i-wireless/sprint
hewillmakehell said:
OK I believe I may have found the possible solution to this problem.
Click to expand...
Click to collapse
i've tried both your copied file trick and making a new file with root explorer, both to no avail. ".thumbdata3--1967290299" always reverts to its old size if any app associated with the gallery is opened.
has yours really stopped reappearing?
i can't figure out where the large thumbnail data is stored, but it must be in the system somewhere...
problem solved
hey i figured out how to fixed this on my atrix. should be the same for all android phones.
http://forum.xda-developers.com/showthread.php?p=28447099#post28447099
There's no "external.db" inside my "com.android.providers.media" folder.
However, I didn't even understood what I was supposed to do with this file. What he meant with "trim the thumbnails table with an sql editor"?
I quoted the post you linked below:
i found the place where the thumbnail data is stored, which was making the huge thumbnail file and crashing Entertainment Center.
it isn't storing the entire ".thumbdata3--1967290299" file (which can be hundreds of mb for some people), rather a large (tens of mb) .db database file that is being used to recreate it on demand.
/data/data/com.android.providers.media/databases
external.db
with Root Explorer i could view the file, and Speed Software also sells an sql editor which you can use to trim the thumbnails table.
*be careful: deleting entries from this file also seems to delete it from the device! i deleted all records from the thumbnails and images tables..
learn from my mistake. i thought it would regenerate, but it deleted all images from /sd card. good thing i backed up all my photos first, but better to use the filter option and trim out only the records for files that are no longer on the device.
".thumbdata3--1967290299" now reappears, but a whole lot smaller.
Gallery opens so much faster now, and Entertainment Center works again!
hope it helps!
Click to expand...
Click to collapse
i bet it is hiding somewhere. maybe it's slightly different on other phones.
the issue was that i had an ever-expanding sdcard/dcim/.thumbnails/.thumbdata3--1967290299 file being recreated every time i accessed the gallery viewer, even after that thumbnails folder was erased.
my device was keeping track of ALL the media files that were ever on it, not just the ones presently on it. so the more files that passed through my device, the bigger the thumbdata file kept getting. the external.db file contains a table that lists all media files along with a bunch of attributes for each. apparently this db file is used to generate the thumbdata file. all the info for deleted files just leads to more padding inside the thumbdata file, so it keeps getting bigger.
by trimming the table i meant to delete the records in the external.db that correspond to thumbnails for media no longer on the device. that file is an SQLite file, so to open it you need a special viewer/editor. i first used the SQLite Viewer that comes with Root Explorer. with that, i could see the all the redundant thumbnail entries. to edit it, i got the SQLite Editor, though i'm sure there are other ways. then it's a matter of recognizing which files it lists that are no longer on your device, and getting rid of those rows from the table. in my case the external.db file went down from 8mb to 500kb after i did that.
screenshot 1 showing tables inside external.db, using SQLite Editor
screenshot 2 showing 'thumbnails' table
TBN FILE 2gb
hi
i have a huge thumbnail file in he sd card its almots 2GB
i have already came to opeing the list for thumbnails in the editor
but i dont know how to filter it that i can delete only the files which are not in the sd card (i.e already deleted ) plss guide me throught ,,, this and u will be a star:good:
whitebreadstyle said:
i bet it is hiding somewhere. maybe it's slightly different on other phones.
the issue was that i had an ever-expanding sdcard/dcim/.thumbnails/.thumbdata3--1967290299 file being recreated every time i accessed the gallery viewer, even after that thumbnails folder was erased.
my device was keeping track of ALL the media files that were ever on it, not just the ones presently on it. so the more files that passed through my device, the bigger the thumbdata file kept getting. the external.db file contains a table that lists all media files along with a bunch of attributes for each. apparently this db file is used to generate the thumbdata file. all the info for deleted files just leads to more padding inside the thumbdata file, so it keeps getting bigger.
by trimming the table i meant to delete the records in the external.db that correspond to thumbnails for media no longer on the device. that file is an SQLite file, so to open it you need a special viewer/editor. i first used the SQLite Viewer that comes with Root Explorer. with that, i could see the all the redundant thumbnail entries. to edit it, i got the SQLite Editor, though i'm sure there are other ways. then it's a matter of recognizing which files it lists that are no longer on your device, and getting rid of those rows from the table. in my case the external.db file went down from 8mb to 500kb after i did that.
screenshot 1 showing tables inside external.db, using SQLite Editor
screenshot 2 showing 'thumbnails' table
Click to expand...
Click to collapse
I had the sam issue, but unfortunately your solution didn't help me. I have only a couple of pictures on my phone, but a lot of GBs of music on SDCard and I think this is he reason why .thumbdata3 file is so large on my phone.
I also tried using SDRescan as proposed here: http://forum.xda-developers.com/showpost.php?p=28516079&postcount=6, but that didn't help either.
I've done some more research and found a solution here: http://www.mobilephonetalk.com/show...in-memory-card&p=311954&viewfull=1#post311954. After I deleted the .thumbdata3 file, created a blank one with Root Explorer and removed write permission to it, the file stays at 0 bytes and Camera and Gallery apps still work fine.
mihir880 said:
hi
i have a huge thumbnail file in he sd card its almots 2GB
i have already came to opeing the list for thumbnails in the editor
but i dont know how to filter it that i can delete only the files which are not in the sd card (i.e already deleted ) plss guide me throught ,,, this and u will be a star:good:
Click to expand...
Click to collapse
it sure would be nice if android did that automatically
i don't know how though, sorry.. maybe there is a way, but it is surely safer to backup the media files to another drive, trim the db, then move them back if necessary.
---------- Post added at 09:47 PM ---------- Previous post was at 09:42 PM ----------
strom87 said:
I've done some more research and found a solution here: http://www.mobilephonetalk.com/show...in-memory-card&p=311954&viewfull=1#post311954. After I deleted the .thumbdata3 file, created a blank one with Root Explorer and removed write permission to it, the file stays at 0 bytes and Camera and Gallery apps still work fine.
Click to expand...
Click to collapse
i guess that's one way of doing it. it just means all the thumbnails have to be recreated every time you open the gallery or file browser.
strom87 said:
I had the sam issue, but unfortunately your solution didn't help me. I have only a couple of pictures on my phone, but a lot of GBs of music on SDCard and I think this is he reason why .thumbdata3 file is so large on my phone.
I also tried using SDRescan as proposed here: http://forum.xda-developers.com/showpost.php?p=28516079&postcount=6, but that didn't help either.
I've done some more research and found a solution here: http://www.mobilephonetalk.com/show...in-memory-card&p=311954&viewfull=1#post311954. After I deleted the .thumbdata3 file, created a blank one with Root Explorer and removed write permission to it, the file stays at 0 bytes and Camera and Gallery apps still work fine.
Click to expand...
Click to collapse
How did you removed write permission from the thumbdata3 file with RootExplorer. If I try this, then I get a message, that that is not possible on the SD-Card and nothing happens!! The permissions stay !!!
Sunnymen1975 said:
How did you removed write permission from the thumbdata3 file with RootExplorer. If I try this, then I get a message, that that is not possible on the SD-Card and nothing happens!! The permissions stay !!!
Click to expand...
Click to collapse
You can try creating a folder instead of a file(no need to set permissions). So far, it's working
lbrfabio said:
You can try creating a folder instead of a file(no need to set permissions). So far, it's working
Click to expand...
Click to collapse
Another quick way that seems to work:
Code:
rm -rf /mnt/sdcard/DCIM/.thumbnails && touch /mnt/sdcard/DCIM/.thumbnails
rm -rf /mnt/sdcard/external_sd/DCIM/.thumbnails && touch /mnt/sdcard/external_sd/DCIM/.thumbnails
Hello, I also have this problem. Now I put another file with that name and that seems to work.
However, I came on this because my device went suddenly very slow.
Is it possible that the application that writes these .thumbnail files is still searching through the complete device, even when it cannot update the file?
And, how can I inspect what app is causing this file or slow down?
Fixed!... deleted .thumbnails folder and then created a file called .thumbnails using root explorer....thats worked for me in my THL w1..saved 1.2 gb of space!
Is there anyway to stop the stock camera from posting pics in the DCIM folder? I am somewhat ocd and would like them to be posted in a folder of my choosing.
estranged1977 said:
Fixed!... deleted .thumbnails folder and then created a file called .thumbnails using root explorer....thats worked for me in my THL w1..saved 1.2 gb of space!
Click to expand...
Click to collapse
Created a file or a folder?
petrsiri said:
Created a file or a folder?
Click to expand...
Click to collapse
try create folder (I do this and see no more thumbdata3-files yet two months)
Guys, after to my surprise, being prompted by my xperia-sp that i had only owned for about a month! that i couldn't install an app i wanted to install, because i had run out of space!, i decided to investigate where all my 5,800mb user available space had gone, and i was eventually able to claw back approx 2GB by deleting in my opinion useless files from my internal drive.
I thought it will be a good idea to share my findings for those who like me didnt know about the listed below.
Below are the main culprits
1. /mnt/sdcard/DCIM/.thumbnails = >182mb
(sony/android system running bloatware - a solution =
delete '/mnt/sdcard/DCIM/.thumbnails' folder, then create a file named '.thumbnails' (obviously without the quotes) and then move to'/mnt/sdcard/DCIM/' folder, this solution found here - http://forum.xda-developers.com/showthread.php?t=2416688 ,so credits to the original poster.)
2. /sdcard/App_Manager/App_Backups = >745mb !!!
(created by ROM Toolbox app - see here - http://forum.xda-developers.com/showthread.php?t=1350751 , credits to the original poster.)
3. /sdcard/MyAppSharer = >100mb
(created by MyAppSharer app)
4. /sdcard/bluetooth = >600mb
(created as you receive files via bluetooth)
5. /sdcard/demovideo = 90mb
(sony demo video bloatware, i personally just moved them to my external sd, as they are somewhat funny/interesting vids.)
6. /mnt/sdcard/video/xperia_hd_landscapes.mp4 = 41mb
(another sony demo video bloatware).
notes
=-=-=
* the above spaced used/saved are for my xperia-sp, your own 'real estates' may be different, depending if you use you the apps that create some of these folders & files or how long you've been using your xperia-sp for.
* also removing these extraneous files will also reduce the size of your nandroid backups, which can only be a good thing.
Hope this helps someone
b00b said:
Guys, after to my surprise, being prompted by my xperia-sp that i had only owned for about a month! that i couldn't install an app i wanted to install, because i had run out of space!, i decided to investigate where all my 5,800mb user available space had gone, and i was eventually able to claw back approx 2GB by deleting in my opinion useless files from my internal drive.
I thought it will be a good idea to share my findings for those who like me didnt know about the listed below.
Below are the main culprits
1. /mnt/sdcard/DCIM/.thumbnails = >182mb
(sony/android system running bloatware - a solution =
delete '/mnt/sdcard/DCIM/.thumbnails' folder, then create a file named '.thumbnails' (obviously without the quotes) and then move to'/mnt/sdcard/DCIM/' folder, this solution found here - http://forum.xda-developers.com/showthread.php?t=2416688 ,so credits to the original poster.)
2. /sdcard/App_Manager/App_Backups = >745mb !!!
(created by ROM Toolbox app - see here - http://forum.xda-developers.com/showthread.php?t=1350751 , credits to the original poster.)
3. /sdcard/MyAppSharer = >100mb
(created by MyAppSharer app)
4. /sdcard/bluetooth = >600mb
(created as you receive files via bluetooth)
5. /sdcard/demovideo = 90mb
(sony demo video bloatware, i personally just moved them to my external sd, as they are somewhat funny/interesting vids.)
6. /mnt/sdcard/video/xperia_hd_landscapes.mp4 = 41mb
(another sony demo video bloatware).
notes
=-=-=
* the above spaced used/saved are for my xperia-sp, your own 'real estates' may be different, depending if you use you the apps that create some of these folders & files or how long you've been using your xperia-sp for.
* also removing these extraneous files will also reduce the size of your nandroid backups, which can only be a good thing.
Hope this helps someone
Click to expand...
Click to collapse
Recently I found something that help me a save more space in my SP. For Tapatalk users, go to SD00/Tapatalk4/Sessions/remote-cache. Delete all files. For me save +- 900 mb of temporary files. I hope that help.
Sorry for the bad English, but the government of my country just decided this year, to investite in education. Maybe is the world cup.
Enviado de meu C5303 usando Tapatalk
thanks for adding to the conversation... will check it out
Try to use an app called Link2SD that moves your apps to your external SD Card which really helps if you have Root.https://play.google.com/store/apps/details?id=com.buak.Link2SD If you are a gamer, which I don't think cause if you are you would complain about it, you should buy the app Folder Mount, because Link2SD does not move Obb files(huge 'only' game files).https://play.google.com/store/apps/details?id=com.devasque.fmount
Sent from my C5303 using xda app-developers app
holy crap my .thumbnails folder is 1.44 GB
I think once we delete the thumbnails folder, and then open the album app, it is going to rebuild the same thing over again !
aniket_ said:
I think once we delete the thumbnails folder, and then open the album app, it is going to rebuild the same thing over again !
Click to expand...
Click to collapse
you are right will build again automatically :C mine builded again 984 MB !!!
guys, after you delete the .thumbnails folder, you must -
create a file named .thumbnails
and place it where the .thumbnails folder used to be and this will stop the android system recreate the .thumbnails folder as there is a file named .thumbnails that you created.
It worked for me since my original post and my phone works as normal.
Remember create a file named .thumbnails not a folder named .thumbnails
p.s.
see the attached screenshot of my DCIM folder on my Xperia SP
b00b said:
guys, after you delete the .thumbnails folder, you must create a file named .thumbnails and place it where the .thumbnails used to be and it will not recreate the .thumbnails folder as there is a file named .thumbnails that you created. It worked for me since my original post and my phone works as normal.
Remember it a file named .thumbnails you should create not a folder named .thumbnails
Click to expand...
Click to collapse
Aah.. Did not read the op thoroughly. :good:
Hi folks!
So, inspired by the discoveries on this thread, I set about creating an app to easily discover and delete space-wasting files. This app is now in Alpha stage, and will be advanced to Beta as soon as it is feature-complete.
Requirements: capability-unlock (interop-unlock plus EnableAllSideloading). In the case of files that can't be deleted normally, the app will attempt to use the Samsung-specific RPC Component to move them to the SD card (and delete them from there). The app will still run on non-Samsung phones, or those without SD cards (although you'll get a warning at launch in either case) provided they meet the other requirements, but some folders won't be cleanable.
Current state: Alpha 0.2.1
History:
Alpha 0.2.1: Files will now be checked for the Read-Only flag, and it will be removed if possible, both before attempting an in-place deletion and after moving to SD. In case of an error, the exception type will now be given in the report. Files with a "Modified" date in the future will now be included by default as well.
Alpha 0.2.0: Added Move-to-SD-and-then-delete as a work-around to permissions issues. Added warnings if Samsung RPCComponent or SD card are not present. Truncated overly-long messageboxes to avoid the app hanging for a few minutes due to an accidental tap. Re-compiled as release build for performance.
Initial release (20 Feb 2014)
Source code is available at https://wp8storagecleanup.codeplex.com/
Please post feedback here!
Known issues:
Many locations that we nominally have access to don't actually grant *delete* access, only read and write/create (yes, NT tracks permissions for Delete separately from Write). Thus, a lot of files that you'd like to delete might not actually go away. (Sadly, this includes the EdmCache\Lib folder mentioned in the thread linked above). I'm working on it!
Should be fixed as of 0.2.0, if you have a Samsung phone and an SD card!
Many locations set the Read-Only flag on their files, making them un-deletable even with move-to-SD.
Should be fixed as of 0.2.1, which removes RO flags either in-place or acter move-to-SD
The app startup is pretty slow. Well, it's actually fairly fast, but it seems slow because the entire structures of all relevant directories are traversed before the UI is shown. I will move that to a background/async thread "soon".
Viewing the files for some locations (like the TIF folders, which often have hundreds or thousands of files) will cause the app to hang for a long time while it tries to format kilobytes of text into a MessageBox.
As of 0.2.0 this problem should no longer occur, as the messages will be truncated before being displayed in the MessageBox.
There's no way to change the list of locations. Well, not short of re-compiling the app, at least. I'll move them to external storage soon.
Features I want to implement:
Filtering (especially for specific folders) to files older than a certain date. This is actually already supported by the app; there's just no UI for it.
Adding additional locations for cleaning out files from, and removing locations too. Ideally, these would persist across runs of the app.
One button to select (or clear) all locations.
Option to hide locations which have no files of interest (just to make the list smaller).
Ability to edit a given location's filters (filtering on filename patterns is already implemented, but again, there's no UI for it). This should persist too.
At some point, the ability to select (or de-select) specific files or folders for deletion, in case the filtering isn't fine-grained enough. This is pretty easy to add; I just hate writing XAML.
While I'm at it, the ability to delete directories might be good. Currently this tool only deletes files.
More detailed errors when deleting a file fails. It's *usually* ERROR_ACCESS_DENIED, but it could be something else (like the file being in use by another program).
An option to move files to the SD card instead of deleting them. This would save space while providing the ability to implement an un-delete. True un-delete would require some kind of log or structure to the moved files.
Speaking of logs, I really should have the app generate one. Again, the basic stuff is already there; in fact, it generates *too much* text, so much so that I had to make it truncate MessageBox contents at about a KB.
Option to report file sizes in units based on powers of 1000 or powers of 1024 (currently it uses powers of 1000).
Internationalization would be good.
Possibly, at some point in the future, the ability to check (and clean out) the storage of other apps. You can clean them by just removing (and re-installing) them, of course, but sometimes that's a pain, and a more specific filter may be good.
Possibly an in-app update notification when new versions come out...
Reserved for OP.
Good work waiting for further versions
Sent from my GT-I8750 using Tapatalk
Hack:
Move "undeletable" files to directory, where you can delete them with RPC and delete.
the RPCComponent doesn't actually change the file ACLs, and may even turn inherited ACLs into file-specific ones when used; I previously tried copying files from unreadable locations to System32, and was still unable to read them even though I could now see them and see their file size. Very irritating.
My work-around for that is to move them to the SD card, which (being a FAT file system) has no ACLs at all. They can then be deleted from there. This works great... if you have an SD card. While I imagine most Ativ S users have installed such a card (it's one of the best features of the Ativ S, the only first-gen WP8 device to both have good specs *and* a microSD card) and they're pretty cheap if not (only needs to be big enough to briefly store the file being moved; 4GB would be more than enough), it's annoying to introduce dependencies like that. Still you've gotta do what you've gotta do...
GoodDayToDie said:
the RPCComponent doesn't actually change the file ACLs, and may even turn inherited ACLs into file-specific ones when used; I previously tried copying files from unreadable locations to System32, and was still unable to read them even though I could now see them and see their file size. Very irritating.
My work-around for that is to move them to the SD card, which (being a FAT file system) has no ACLs at all. They can then be deleted from there. This works great... if you have an SD card. While I imagine most Ativ S users have installed such a card (it's one of the best features of the Ativ S, the only first-gen WP8 device to both have good specs *and* a microSD card) and they're pretty cheap if not (only needs to be big enough to briefly store the file being moved; 4GB would be more than enough), it's annoying to introduce dependencies like that. Still you've gotta do what you've gotta do...
Click to expand...
Click to collapse
Just make it an option
OK, I implemented the Move-to-SD-and-then-delete hack. It's considerably slower that in-place deletion but it works. I also built the app for Release (rather than debug) which improves initial performance somewhat, and truncated long messages so you don't have to watch the phone struggle to display a messagebox with 200KB of text.
installed on my lumia 520 with developer unlocked...Not able to open.
Deployed successfully....but no app icon in Application list....
How to launch it?
tell me?
You need capabilities-unlock, it is not possible yet on Lumias. Only on Ativs
Sent from my GT-I8750 using Tapatalk
Got an error deleting my Internet Explorer Temp Files
edit: same with all other files
trytogetme said:
Got an error deleting my Internet Explorer Temp Files
edit: same with all other files
Click to expand...
Click to collapse
maybe they were currently in use?
-W_O_L_F- said:
Hack:
Move "undeletable" files to directory, where you can delete them with RPC and delete.
Click to expand...
Click to collapse
That´s the best solution atm. For example I move files from the appdata folders with the RPC to the local storage of my app and delete them there using a background worker.
Amirphp said:
installed on my lumia 520 with developer unlocked...Not able to open.
Deployed successfully....but no app icon in Application list....
How to launch it?
tell me?
Click to expand...
Click to collapse
If you actually managed to even get it installed, I'm impressed! It should have reported an error. This app uses both ID_CAP_INTEROPSERVICES and some capabilities that installable apps aren't supposed to have at all. There should have been at least two different errors if you tried to install it on a Lumia...
@trytogetme: Are you using the newer version, and do you have an SD card in the phone (with at least a bit of space; it doesn't need much)?
If so, I'll try to dig deeper into what the problem could be. @error0x0000034 has a good point, though; you may want to try running the app immediately after rebooting the phone.
I have same problem, with little files too
Sent from my GT-I8750 using Tapatalk
GoodDayToDie said:
@trytogetme: Are you using the newer version, and do you have an SD card in the phone (with at least a bit of space; it doesn't need much)?
If so, I'll try to dig deeper into what the problem could be. @error0x0000034 has a good point, though; you may want to try running the app immediately after rebooting the phone.
Click to expand...
Click to collapse
Restarting the phone doesnt help for me.
Still the error. The app doesnt care what folder I want to clear. Got that error every time
Hmm. I'll see if there's something I can do about that. One thing I found is that some files are marked Read-Only. Unlike proper ACLs, that flag persists after the move to microSD. It's easy to remove, though. I'll add code to check for, and remove, that flag.
Can you connect your phone to USB and check the SD card? If there's a folder called "StorageCleanerTemp" on the root of the SD card, that means there were files moved by the PRCComponent but which the app subsequently failed to delete. The most likely reason is that they were flagged as Read Only. (it's worth noting that this would have removed them from the phone's internal storage anyhow...)
I just deleted my Temporary Internet Files using v0.2.0, exactly the same as you can get here. It took something like 10 minutes - I really need to optimize that - but it worked, deleting some 2600 files totaling over 200MB.
GoodDayToDie said:
If you actually managed to even get it installed, I'm impressed! It should have reported an error. This app uses both ID_CAP_INTEROPSERVICES and some capabilities that installable apps aren't supposed to have at all. There should have been at least two different errors if you tried to install it on a Lumia...
Click to expand...
Click to collapse
i used xap Deployer 2.0
And installed without any error...
But No app icon...as i told earlier.
But when i tried to deploy via windows Power Tools...then i got error...
But no error with Xap deployer 2.0.
Are there any other folders or files that could be deleted to regain space from system files?
My system is at 9.59GB, but even the StorageCleanup says I can free up to 215.3MB only, with the Store app package cache holding only 1-2 .zmz files (with about 30MB, the most is in Temporary Internet files, at about 170MB)...
Each time I delete some apps I installed previously (just about 4GB of apps right now), pretty soon that free space gets "eaten up" by the system leaving me with just MB/KBs free?! It's unreal how Microsoft hasn't at least addressed this as a bug yet, maybe it's going to be fixed in 8.1, hopefully developer preview's coming soon...
@GoodDayToDie - I wanted to rebuild the xap myself and see if I could help out myself somehow, but I'm having a problem with deploying the app from VS2013 with the standalone WP8SDK installed, in particular with these capabilities:
<Capability Name="ID_CAP_CHAMBER_PROFILE_DATA_RW" />
<Capability Name="ID_CAP_COMMS_SERVICES" />
<Capability Name="ID_CAP_COMMS_APPLICATIONS" />
<Capability Name="ID_CAP_COMMS_COMMON" />
<Capability Name="ID_CAP_DU_SHARED_DATA" />
<Capability Name="ID_CAP_DUASVC" />
<Capability Name="ID_CAP_EDM_CACHE_WRITE" />
<Capability Name="ID_CAP_ENTERPRISE_SERVICE" />
<Capability Name="ID_CAP_PHONE_INTERNAL" />
<Capability Name="ID_CAP_PUBLIC_FOLDER_FULL" />
<Capability Name="ID_CAP_ZMFSERVICES" />
failing build with these 1 error + 10 warnings:
The 'Name' attribute is invalid - The value 'ID_CAP_CHAMBER_PROFILE_DATA_RW' is invalid according to its datatype 'String' - The Enumeration constraint failed, etc...
How do you get around it please? And is your CRPComponent free to use/distribute? I'd like to use some of its method calls (which I will share afterwards - hope you don't mind that I got it from the xap file - the dll&winmd files)...
I want to share this tutorial for all those of you are annoyed because any game or app on Lollipop or Kitkat with ART activated not works , to the fact some even they are not posiblle to be installed .
First of all make clear that I've tested only with two apps .with Modern Combat 5 on a i9100 ( galaxy s2 international variant) with lollipop ( remix resurrection using 5.2.7 )
and whatsapp + in Art with slimsaber 4.4.4 for art with kitkat is easier. But the procedure should work with other applications , test if this process work with other apps,
I think the way to install lollipop should work with all . Also tell you that you must be root in your terminal.Well I continue explain de process to do this:
-Example 1. Modern Combat 5. It was available for my device actually buy it and I worked on the last stock that came 4.1.2 . So nothing lollipop or installed , and the market did not appear after putting the RR 5.2.7
So examine how the applications were installed in the partition data / app , in this case I noticed as was the Brothers in Arms 3 what I installed an runs perfect amd smoothly on lollipop
with my device , and after that tell you how serious the process ( once you memorized it, can be done quickly ) :
1- got the apk and game data in this case I use the version 1.1.0k the game, extracting it from titaniumbackup
2 - put data file extension .obb in android / obb / game folder (in this case com.gameloft.android.ANMP.GloftM5HM ) , if not create you have to make it so
3 - the apk we duplicate copy it twice to get back , and we will use one of the two copies to put with extension .zip
4 - this copy with .zip extension we open with winrar , es explorer unzsip or similar in the same cell or whatever you want , but that's easier ,
and seek the lib folder, this folder unpack where we please stay with the path where this
5.go that folder to unzip those files and we notice that within lib we armeabi - v7a and x86, like mine is an ARM 'll take this , go in and see the files and libMC5.so libgenerator.so
these have to be copied to a path that will create a root explorer, I'm in the next step :
6.You have to got some browser root (root browser for example ) , installation and use giving root permissions of course
with root explorer let's data / app and create the com.gameloft.android.ANMP.GloftM5HM -1 folder (for we must always know what the data folder of the game, we know of sources
where we got the game or app or the name given to the backup titaniumbackup
( but that if no antics , only basic form, eg com.gameloft.android.ANMP.GloftM5HM or com.gameloft.android.ANMP.GloftAMHM and always adding -1 ), then as I said we created with root explorer
in data / app the com.gameloft.android.ANMP.GloftM5HM -1 folder and this folder and give the pressed (or mark with v better) permissions on owner : read, write and execute , a group : read and execute ; and others to read and execute
v should be the brand with the entire left column of the right and also entire medium alone box above. Now you also have to change the owner of this folder , pressing ( and choosing ownership )
a system ( 1000 : system in both , owner and group) in the 2 boxes
7 Once done from the root explorer go to the path where we keep extracted lib folder with subfolders armeabi - v7a and x86 both with files
libgenerator.so and libMC5.so , but will copy these two armeabi - v7a the folder ( repeat that in mine case, the other will be the x86) multiple choice or as the root explorer and mark and copy
Now we return to the route data / app / com.gameloft.android.ANMP.GloftM5HM -1 and it will give new folder (or copy those files and then recolocaremos , but better do just as I put ) and create lib folder entered this
and create a subfolder turn the arm so as we would in data / app / com.gameloft.android.ANMP.GloftM5HM -1 and another lib folder within this arm call, enter this arm and paste here
files and libMC5.so libgenerator.so said before .
8.Now we go to root explorer where you leave the game or application .apk here com.gameloft.android.ANMP.GloftM5HM.apk ( why I told you to do apk two copies , one for her in zip and other the original )
We owe this apk copy and turn to data / app / com.gameloft.android.ANMP.GloftM5HM -1 and paste it inside ( outside the lib folder) and rename it in there to base.apk , so we would have :
Route data / app / com.gameloft.android.ANMP.GloftM5HM -1 within which we would have one base.apk and the lib folder in which we would have the folder containing arm turn the libgenerator.so files and libMC5.so
9 - While remember before we gave permissions and change owner to com.gameloft.android.ANMP.GloftM5HM -1 folder , now we must do all that is within it and are as follows :
10 - base.apk - owner permissions : read and write ; group: only read ; others: just read --ownership : owner : 1000 : system ; group: 1000 : system
-carpeta lib- owner permissions : read, write and execute ; group : read and execute ; others : read and execute - ownership : owner : 1000 : system ; group: 1000 : system
-carpeta arm- owner permissions : read, write and execute ; group : read and execute ; others : read and execute - ownership : owner : 1000 : system ; group: 1000 : system
-libgenerator.so and libMC5.so both files like each: owner permissions : read, write and execute ; group : read and execute ; others : read and execute - ownership : owner : 1000 : system ; group: 1000 : system
11.Now we have the game or app installed but not yet ready to leave our app drawer (and actually work, that also depend on whether apk and data corresponds thereof)
we have to go to the recovery of our rom and wipe the dalvik and cache to optimize it for our system to recognize , also warn that without prior permission even so not to ( so put them well )
expect a little minutes and flies already running, MC5 , which in this case buy the market google play and not work after I started work lollipop in this and a lot more smooth.
-Example 2: I did something similar but easier to solve when trying to install whatsapp apk same or mods that are in 4.4.4 once passed ART execution system , in that case was only move the .apk
to partition data / app and rename your installation name com.whatsapp - 1.apk owner permissions : read and write ; group: only read ; others: just read and --ownership : owner : 1000 : system ; group: 1000 : system and reboot device
and the same rom without wipe dalvik still optimized app.
Hope you helps.
by Yhazarus ( EDU80 eol )
great guide!
thanks for your time to write this guide, although i think that most people would stay on dalvik if art isn't compatible with their apps.
@yhazarus Is the name have to be "lib*appname*.so" and "libgenerator.so" ? Because I didn't find those names on Noozxoide Rewire E series when I change the extension of the base.apk to base.zip and opened it.
I find the names are mostly have the extension of '.pmo', while the '.so' file isn't even one of those names. Can you help me, the ART broke this and the developer hasn't respond even to one of our (the ones who got lollipop) complaints.
..
.....
Cliffs: I was suspicious of how little free internal storage I had on my Z Play so I started looking into where it had all gone. I found Motorola to be reserving space for OTA updates and enforcing the reservation actively -- I worked around it and got my 1.2 GB back.
If you have root access you can use the steps below to resolve -- otherwise, at least you'll be more informed about whats going on with your storage.
----------------------------------------------------------------------------------------------------------------
According to Android settings my 16GB Z Play running 6.0.1 has 9.41 GB of storage left after the partition allocated to /system. Not long after I got the phone setup with my usual set of applications I received an insufficient storage warning -- SOMETHING was eating up a ton of space.
A photo backup I had run was partly to blame and since I hadn't yet used my SD Card, this was my fault... I resolved that -- but the math still didn't work.
I started digging around until I came across a directory that I would later learn is reserved space for OTA download and cache.
If you're able to access your file system, take a look at /data/data/com.motorola.ccc.ota/reserved
You're going to find 12 files, each 100 MB -- sequentially named dummy1.zip, dummy2.zip, etc.
These are created by the OTA client, located in /system/priv-app/3c_ota -- and the amount of space reserved using the dummy files is determined by a file called reserved_space.txt located in /system/etc/motorola/com.motorola.ccc.ota. If you open this file you'll see '1200' -- representing the amount of space in MB to be reserved.
First, you should remove the dummy.zip files, but only deleting the files is pointless since the files will be recreated by the OTA client.
To prevent them from being recreated you can:
A.) Disable/delete the OTA client (I renamed mine, dropping the APK extension)
B.) Edit the reserved_space.txt file
Thanks for looking out Moto, but I'll take it from here.
w0rdie said:
Cliffs: I was suspicious of how little free internal storage I had on my Z Play so I started looking into where it had all gone. I found Motorola to be reserving space for OTA updates and enforcing the reservation actively -- I worked around it and got my 1.2 GB back.
If you have root access you can use the steps below to resolve -- otherwise, at least you'll be more informed about whats going on with your storage.
----------------------------------------------------------------------------------------------------------------
According to Android settings my 16GB Z Play running 6.0.1 has 9.41 GB of storage left after the partition allocated to /system. Not long after I got the phone setup with my usual set of applications I received an insufficient storage warning -- SOMETHING was eating up a ton of space.
A photo backup I had run was partly to blame and since I hadn't yet used my SD Card, this was my fault... I resolved that -- but the math still didn't work.
I started digging around until I came across a directory that I would later learn is reserved space for OTA download and cache.
If you're able to access your file system, take a look at /data/data/com.motorola.ccc.ota/reserved
You're going to find 12 files, each 100 MB -- sequentially named dummy1.zip, dummy2.zip, etc.
These are created by the OTA client, located in /system/priv-app/3c_ota -- and the amount of space reserved using the dummy files is determined by a file called reserved_space.txt located in /system/etc/motorola/com.motorola.ccc.ota. If you open this file you'll see '1200' -- representing the amount of space in MB to be reserved.
First, you should remove the dummy.zip files, but only deleting the files is pointless since the files will be recreated by the OTA client.
To prevent them from being recreated you can:
A.) Disable/delete the OTA client (I renamed mine, dropping the APK extension)
B.) Edit the reserved_space.txt file
Thanks for looking out Moto, but I'll take it from here.
Click to expand...
Click to collapse
The folder that you mention I have it empty, I have not deleted anything, so it was originally
Possible that it varies by firmware - can you post your About Screen / Build Number?
Mine is XT1635-01 | MCOS24.104.35.1-9
a pop out saying i have 100mb left. free some space to continue using the app successfully
how to free the space and why this pop out keeps on coming?
Isn't there a reason why these dummy files exist? Does OTA update still work fine after you delete them?