Database Info

[Q] Icons disappears from desktop when reboot

I think I read about this here a while ago, can not find it anymore.
After update to firmware 2.2 apps can be stores on sd-card.
BUT icons disappers from desktop when phone is restarted.
This only if its app is on sd-card.
Is there a fix for this, very annoying.

Sammi3 said:
I think I read about this here a while ago, can not find it anymore.
After update to firmware 2.2 apps can be stores on sd-card.
BUT icons disappers from desktop when phone is restarted.
This only if its app is on sd-card.
Is there a fix for this, very annoying.
Click to expand...
Click to collapse
SD Card scanning takes time when you restart your phone, so for all the apps that you have installed in your SD Card, it will take time to load. Also widgets wont load if installed on SD Card. Please check if your icons are not coming at all or they are coming with a delay?

Thanks for your answer.
I upgraded to Froyo XXJPS some 4 months ago, ever since its been like this.
I have done nothing else to the phone.
Indeed it takes awhile to scan sd-card, but they do not load back on desktop even if I repositioned them after last restart.

Sammi3 said:
Thanks for your answer.
I upgraded to Froyo XXJPS some 4 months ago, ever since its been like this.
I have done nothing else to the phone.
Indeed it takes awhile to scan sd-card, but they do not load back on desktop even if I repositioned them after last restart.
Click to expand...
Click to collapse
Check your notification bar if the sd card is being scanned or not and make sure widgets are on the phones memory. Also i would recommend rooting your phone, partitioning the sd card and using link2sd app from the android market. It moves your apps to the partition of your sd card and your phone thinks its your internal memory so it won't do a media scan on it meaning your apps load a lot faster. If you want to partition your sd card don't hesitate to message me for more info

It is not only widgets that is left out, none of the icons for the applications is loaded back. If the app is stored on sd-card that is.
Icons for apps stored on phones internal memory load fine.
I see this tiny sd-card-symbol in the notificatin bar for quite a while when reebooting. So it must be media scanned.

Sammi3 said:
It is not only widgets that is left out, none of the icons for the applications is loaded back. If the app is stored on sd-card that is.
Icons for apps stored on phones internal memory load fine.
I see this tiny sd-card-symbol in the notificatin bar for quite a while when reebooting. So it must be media scanned.
Click to expand...
Click to collapse
Yes, it's a media scan. Just move them to internal memory and it will be fine.
Sent from my GT-I5800 using XDA App

something like this happened to me a while back, the apps were not in the app drawer and also the icons changed to default white and green couldnt launch from home screen. I tried everything short off formatting memory card. I ended up reinstalling all the apps on the memory card ( wont pick up addition space since its already stored on your sd) and now they have been workinf fine since then, i can reboot or install to sd without a problem.
verdict - maybe sent a corrupted apk to sd.

as far as i know (from the time when i was on stock froyo), when you use the "original" way to move your apps to the sd card (settings/applications/manage applications, select app, press move to SD card) the icons placed on your desktop will be removed on a reboot. i dont think its a real "error" on your side, its just how its programmed in stock froyo.

I guess I was waiting for comment like yours, there is a 'bug' in froyo.
Do I have any other options than to root?
Are there updates to be found on froyo.
How did you root?
Name some of the biggest benefits in a rooted phone.

im not saying its a bug in android or in the android version we have on our phone. i dont know if other phones running android have the same "problem" with this.
if you want root do a quick search on the G3 section for it. its pretty good explained in a thread.
running a script like apps2sd requires you to partition your sd card, the best thing of it is that after its setup it needs no attention anymore, all the apps you install will be moved to the second partition untill it full. so basicly your phone is tricked into thinking that your internal mem is way larger then it should be .

Sammi3 said:
I guess I was waiting for comment like yours, there is a 'bug' in froyo.
Do I have any other options than to root?
Are there updates to be found on froyo.
How did you root?
Name some of the biggest benefits in a rooted phone.
Click to expand...
Click to collapse
The first option is to move your apps to internal memory and see if they all fit in the internal memory or not. I think rooting is an easy way to sort out your problem is the internal memory is not enough for your apps.
The latest update to froyo is XXJPU and it's blazing fast! Just update to that and root your phone using this program. All the info is on that thread but all you really need to do is go to settings > applications > development > make sure USB debugging is ticked. Then connect your phone to your computer using USB cable, open the program as administrator and click root. Follow the commands (really easy) and then after everything is done just manually reboot your phone.
Just rooting your phone doesn't really do anything dangerous etc. All it does is allows you to edit the /system of your phone as this is restricted with androids. After rooting your phone you will be able to expand your internal memory. This is done by partitioning your sd card and using an app called link2sd or a script called app2sd. The app is easier.
Hope this helps and added some useful links in there so be sure to check them out.

Accordin to KIES I allready have the latest uppdate, which I do not seems to have. Where do I find XXJPU.

[Q] .Thumbdata3 file

Whenever I try and upload a file to Google Drive or add a picture from my gallery to instagram, my phone creates a file called .thumbdata3 in the thumbnails directory on my SD card. The problem with this is not the creation of the file, it's that the file is exactly the size of all the free space on the memory card... When plugged into the computer it displays "0 Bytes Free" on the SD card...
So when I choose a file from the gallery to upload to google drive or instagram, it will hang on a black screen until this file has been created (filling up the SD card), and then upload... Then i check the free space, and it is 0Bytes.
Anyone else had this and fixed it?
PS Sorry for being a noob here

Bumping this...
Anyone had this? Or have a solution?

Same thing here, unfortunately no solution. Apparently it is safe to delete the file, but it will be recreated at some point, taking up all the space on the SD card again.
For me, it grew up to 400 MB and even beyond (IIRC), which seems a bit excessive, even taking into account that there are > 2000 pictures in the DCIM folder of my SD-card at the moment. Still, 400 MB is more than a quarter of the 1.4 GB that the pictures take up, which surely does not make much sense if that is supposed to speed up the process of reading/displaying the thumbnails!?
Does anybody know a fix? Is it ICS related? I'm on Stock 4.0.3 ICS BTW, and I never noticed this behaviour before the update...

Same here, with a SE Xperia Mini Pro (4.0.4). It happened with me when the phone tried syncing Evernote notes (with pictures attached).
Maybe this topic should be moved to a more generic sub-forum; apparently it's an ICS problem...

thumbdata3
I am also currently having this problem, specially when trying to upload/import photos from gallery to instagram. the ".thumdata3...." file can go as large as 2.5 gig for me, depenending on how much space I have on my SD card before importing pics from gallery to instagram

Same happenned to me - a siolutions that worked for me
Same happened to me the .thumdata3 ate up all remaining space (1.2G) on my Samsung Galaxy S2, android 4.0.3. Any time I deleted it, it was recreated any time I opened the camera app. Then the camera app was unable to take any pic due to sd full. If I deleted this file it was re-created any time I started camera again.
Installing and running the SDrescan app (from play store) helped. Though SDrescan made stock ringtones disappear. However reboot helped that, and the large file did not came back even after restarting camera.
This worked for me, though I am not sure in the reason. Might work for you as well, or not. I must say that android 4.0 is much worse than I expected. Not the first annoying error I have found.
My guess for the reason of the error happening: I once inserted an sd card with LOTS of media content. Then all this was cached somehow in gallery.
My guess for the reason this solution works: the app erases cached SD data thus helps reducing the thumbnail cache.

rasnadas said:
Same happened to me the .thumdata3 ate up all remaining space (1.2G) on my Samsung Galaxy S2, android 4.0.3. Any time I deleted it, it was recreated any time I opened the camera app. Then the camera app was unable to take any pic due to sd full. If I deleted this file it was re-created any time I started camera again.
Installing and running the SDrescan app (from play store) helped. Though SDrescan made stock ringtones disappear. However reboot helped that, and the large file did not came back even after restarting camera.
This worked for me, though I am not sure in the reason. Might work for you as well, or not. I must say that android 4.0 is much worse than I expected. Not the first annoying error I have found.
My guess for the reason of the error happening: I once inserted an sd card with LOTS of media content. Then all this was cached somehow in gallery.
My guess for the reason this solution works: the app erases cached SD data thus helps reducing the thumbnail cache.
Click to expand...
Click to collapse
I had the same issue, but unfortunately your solution didn't help me. Initially I thought it did, but after a reboot and launching Camera app, it hanged and created the .thumbdata3 file once again.
I also tried messing up with databases using SQLite Editor, as described here: http://forum.xda-developers.com/showpost.php?p=28466334&postcount=9, 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.

I have an issue with the size of the thumbdata3 file in DCIM/.thumbnails on internal memory (camera is set to store to ext SD) at the moment it is 314MB on internal memory but the thumbdata3 file in the DCIM/.thumbnail folder on ext SD is less than 1MB (I only have around 100 photos and pictures on my phone) - but camera still works (other than in the scenario described below)
If I delete the large thumbdata3 file from internal memory and then attempt to use the camera, the photo is taken without any problem but when I try to view it in either gallery or QuickPic by clicking through from the 'last image taken thumbnail' in the camera and then click back to carry on taking another picture the camera FC's. It usually does this twice and is then absolutely fine - apart from the fact that the large thumbdata3 file has been recreated on internal storage.
I've tried it numerous times and every time the same results - delete thumbdata3 from internal memory, couple of camera FC's, large thumbdata3 file recreated, no more problems (bar the loss of 314MB of storage)
I've tried replacing the thumbdata3 file on internal memory with a copy of the smaller one from Ext SD, creating a blank thumbdata3 file and setting it as read only/no write permission and neither have helped.
Its a bit weird and annoying but I won't let it take the shine off my fun with CM9, however it would be nice to recover that large chunk of storage space to be put to better use.
All the same, many thanks Arco - Beta 1 is my first CM9 install and its great :good:[/QUOTE]
Hi - haven't full troubleshooted this issue yet, but see my notes here. I have the same issue (GNEX JB 4.1.1 stock) and for me it is caused by the app KeepSafe which hides/unhides pics/videos on your phone. Note I believe this is an interaction issue between this app and the media scanning functionality in JB (and I suspect ICS), and so there are likely other apps that have the same issue. For me it creates 1 or 2 .thumbdata3 db files each around 1.3GB.
Certainly, irrespective of app causing it, you can follow the steps to purge Gallery and Media Storage, resync your gmail account and they should disappear on their own. Opening the camera and taking a photo causes the db to come back at around 400MB with a single thumbnail - one of the test files I was hiding and unhiding with KeepSafe but has since been deleted. Can't really explain this behaviour!
Any way, I made some notes on what I tested, the results and some ponderings in case this helps someone work it out:
Thumbdata3
Hiding in keep safe seems to create both the thumbnails and thumbdata file.
Clearing data/cache for gallery and media storage removes all these files? So far doesn't seem to be the case. File and db still there after. Rerunning the media scanner now. Perhaps they caused it? Also forced resync of all items in gmail account. Thumbs and db now gone. Not clear if it was the media scanning completing or the re-sync, but steps to resolve issue now appear deterministic.
Tested with single pic. Restored. No thumbs. Re-hid, thumbnail appeared for this pic and a 435MB db file.
All thumbs were for pics hidden in keep safe. However previously there were far more thumbs. Speculate - cumulative issue thru successive hide/restore cycles, possibly due to file name collision avoidance.
Deleting pic in file explorer also causes the problem? Does not appear to be the case. Gallery/Media Scanner/Media Storage handles this manual intervention far better under ICS/JB. Previously, manually removing a picture rather than deleting it thru Gallery tended to mean the tile/thumb remained. Scanner didn't or didn't very effectively detect this. Probable algorithm change in ICS. Now it sees the deletion immediately. Possibly implicated in keep safe not correctly interacting with the gallery/media scanner properly under ICS/JB.

I´ve the same problem.
After restarting the phone, the camera freezes for a while and regenerates the file, no matter how many media files are in the phone or sd card, it always growth to 431mg after restarting.
(I also find many lost files in the LOST.DIR (almost 2.300gb...many are dissapeared files that I forget about them!)

The .thumbdata files on my SGSIII take up ~4 GB worth of space. Already a quarter of my phones internal memory is being wasted. I wonder if this is a bug or "working as intended"? It makes me wonder how google can still justify the lack of an external microsd card slot on their nexus phones when there is so much space being mismanaged by the OS.

It's works
strom87 said:
I had the same issue, but unfortunately your solution didn't help me. Initially I thought it did, but after a reboot and launching Camera app, it hanged and created the .thumbdata3 file once again.
I also tried messing up with databases using SQLite Editor, as described here: http://forum.xda-developers.com/showpost.php?p=28466334&postcount=9, 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
It's works with me!

that works
That works for me:
1. copy name of thumbdataX--x file
2. delete that file
3. create folder named the same as deleted file; reboot your device
4. look in folders named LOST.DIR (you can find it in the root directory of your internal memory and your SDcard) - huge temporary files may be left in these folders, so delete these files
New thumbdata file can't replace the folder and doesn't appears :victory:

until now the folder solution works :laugh:

Kyonex said:
That works for me:
1. copy name of thumbdataX--x file
2. delete that file
3. create folder named the same as deleted file; reboot your device
4. look in folders named LOST.DIR (you can find it in the root directory of your internal memory and your SDcard) - huge temporary files may be left in these folders, so delete these files
New thumbdata file can't replace the folder and doesn't appears :victory:
Click to expand...
Click to collapse
It doesn't work, camera still overwrites the .thumbdataX--x folder. And as /mnt/sdacard is using FAT32, I also can't set file permission to 000 or use /dev/null symlink.

[Q] Assistance on symlink tweak

A little background will probably help here; I've long been frustrated that if you have your music in the Google Music app and pin it to your device, Google obfuscate it in such a way that other applications can't access that music. Why is this annoying? Because it forces you to make choices you probably wouldn't otherwise and can end up with you having to clog up your internal memory with all your music when it would make far more sense to have it all on your external SD card where all apps can access it. Of course Google made another security decision that any app that had data on the SD card had it in it's own folder, almost completely scuppering the concept of having a shared Music folder on an external SD.
So I came up with a plan;
- When I purchase new music, I'll drop it into a folder on my laptop and Google Music Manager will sync that up to my account so it's available in the cloud and as a backup. No fuss there.
- BitTorrent Sync will then take care of syncing it to a folder on my phone's SD card and any other devices that take my fancy (can't have it in a folder on the root of the SD card called Music - Google won't allow apps to store they files that way so it goes in something like /com.bittorrentsync/data/Music etc).
- Create a symlink from the internal Music folder to the bittorrent Music folder and Hey Presto!
My initial expectation was that all apps *apart* from Google Music would be able to see those files and for the time being, I would have been happy enough with that - better that 99% of potential apps work nicely than only 1%.
So I've done all the above - I had to use FolderMount to do the symlink as I'm not a linux pro
However, the odd thing is that the exact opposite of my expectation has happened. Google Music can see the files (when you set "Downloaded only" in the Google Music app), other music apps can't! So far I've only tried DoubleTwist and DJay2 but neither can see anything and neither have a setting to change where they scan for media.
So I guess my question is - is it even possible to have all apps get their Music from a single resource on the external SD card, whether using a symlink or otherwise? Is there anything I could have done better? Any other advice?
EDIT: I'm running Android 4.4.4 on an LG G3 which is rooted to allow me to run FolderMount
EDIT 2: Thanks to this page: https://www.doubletwist.com/help/qu...nges-to-sd-card-support-in-android-44-kitkat/
I thought I had everything working. The DoubleTwist page describes how to completely clean the AMS database and force a reindex. One reboot and a few minutes of waiting and all apps have access to my symlinked folder!!! However, Google Music and DoubleTwist are not showing quite the same number of tracks and adding new tracks to the sync'd folder doesn't seems to force and update of the media DB.
So, is this lofty goal even possible? I find it very odd that Android would have such a security requirement that essentially made it impossible for apps to be able to access a centralised resource of music files on the external SD card.

Titanium Backup & Internal Storage: Does Not Display Apps Which Exist on SD

Hey Guys -
I've looked everywhere for a solution to this issue and even submitted a request to Titanium's developers, but have yet to find a solution or get a response. In fact, I can't find an issue matching mine online. Posting here hoping someone can help...
The Issue
When launching Titanium Backup on my Shield (6.01 / Rooted), it lists only 289 apps. The problem is that I have a total of 310 user / system ones installed therefore roughly 20 apps aren't listed. I'm wanting to upgrade my tablet to 4.2 and want to backup first, but many of the apps I frequently use are installed to the sd physically.
Why I Think It's Happening
Apps not listed seem to be all of the ones whose files are physically stored on the SD by the OS - I don't think it's related to permissions at all. When upgrading to Marshmallow, I formatted my 64gb SD as "Internal Storage" as doing so makes space management so much easier. No more having to use 3rd party apps to manage and create symlinks for apps I manually copy to the SD. Android seems to dynamically moves / copies things to the SD as needed which works well. If wanting to install a large (1gb+) app, sometimes I must go to an app's properties in Settings and choose to have it's files physically stored on the SD, but that's rare and still using an OEM toolset.
Attempted Workarounds
Most topics I've found when looking for a resolution dealt with not being able to restore apps involving an SD which isn't my issue. Still, I did try the following:
- Tried different storage Providers when setting backup folder location
- Looked all over for potential settings that may have an effect
- Ensured everything's up to date (all is except minor version behind on OS)
- Created new Data Profile in TB
- Tried default settings in TB
Example
Attached are a couple of screenshots for my installation of "Borderlands 2" which is one of the apps affected. As installed it's just shy of 4gb, it must exist on an SD or be the only thing installed, yet it does not appear in TB. To note, when using a file explorer such as FX, the OBB & Data folders / files for applications existing physically on the SD still appear when browsing to Android\Obb or Android\Data from internal storage. In fact, they aren't even listed as symlinks.
Tablet Specs
- Nvidia Shield Tablet (Not K1, but was replaced after battery callback)
- Android 6.0.1
- Rooted /w SuperSU (binary 2.78) All prompts set to "Grant"
- Titanium Backup Pro 7.5.0
- 64gb microsd formatted as Internal Storage (Fastest write and best rated I could find as of 6 months ago)
- Storage (as reported by OS in Settings)
- 70.28gb total
- 63.96gb used
- Internal Storage: 8.31gb of 11.61gb used
- Samsung SD Card: 55.65gb or 58.67gb used
Any suggestions? Thanks!

Hi, in the meantime could you try another software to make your app's backup, helium is my current choice (slide down in first page and select full backup instead of data only).
regards

Storage access bugged

Hey guys, new here, hope it's right to post this here and not in my device's section but it's probably pretty empty in there.. Anyways, i have a very strange problem with my storage access where apps can't properly see contents in my storage (both internal and sd card) meaning the following: apps know folders exist and that space is taken up, but they seem to be unable to actually read or write files somehow. For example the storage tab in the settings shows how much space is free but the categories like pictures, music etc files show 0 bites, except for apps, that section shows up fine. Another example: fx file explorer can't show the amount of used space in the general overview or the folder information tab. But when i actually go into a folder it does show how much space is used and how much is free. I can open a music file in the built in fx music player but when i try to open in an external app it cant play it, shows its at e.g. 116:27:01 out of 5:52 actual play time and that the media format may not be supported. I'd post screenshots but i cant actually make any as the system cant save them.
I have tried restarting, even had a security update from before a few days that i was to lazy to install so i did that, still no change. I also tried removing the sd card to no avail. Since the google play services were using up alot of battery i tried deleting cache, data and even updates for both them and the play store but it seems that this was just another symptom and not the cause. So i think the culprit might be the whatsapp beta version 2.19.365 which crashed at the splash screen for most of it's users. I somehow managed to update it but the problems started when i tried opening it so i don't see what else would be the culprit. I've already contacted their support but tbh i don't ecxpect much help from them.
I'm on an unrooted Honor 7x with Emui 9.1 (based on Android 9).
Does anybody have any idea on what i might try except for a factory reset? I would really like to avoid doing that.
I thsnk everybody who took their time to read and maybe even answer this. Hope your day is going better. Cheers