There is a folder named LazyList in the internal storage.... I delete it and it's back been through three d4's and they all had it... what is said folder for...
Sent from my DROID4 using xda
The folder "LazyList" is simply a cache folder for images viewed from one app or another. Look at the name...it's probably just there to make it easier for apps to use one consolidated cache instead of each one creating and using their own
Thank you kindly....
Sent from my DROID4
Related
Hi everyone.
So today I was looking at my sd card through a file explorer and I've always seen a folder there called 'LOST.DIR' and it had always been empty until today.
So I was wondering what is that folder for??
and can I delete anything inside that folder? or will it screw up my phone in some way? I have about 11mb there that I could free if I erase that folder.
thanks in advance.
The Lost.dir is used for compatibility with the MacOS. LOST.DIR is a special folder that holds all the corrupted or orphaned files found during a file system check. File system checks are completed during the Android mount process.
thank you.
Can I just remove the folder for I will never use any mac machine with my nexus one?
Sent from my Nexus One using XDA App
hycian said:
Can I just remove the folder for I will never use any mac machine with my nexus one?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
You can remove it, but it will probably be re-created sooner or later. When that happens just remove it again - it's safe
Gallery still display pictures from the directory even though it has the file .nomedia.
I have cleared data from media and gallery, then reboot still has problem.
Sent from my GT-N7000 using xda premium
Just put a full stop in front of folder name
Sent from my GT-N7000 using xda premium
Do you mean change the folder name? But this won't work right since some folders with default name such as "download"
Sent from my GT-N7000 using xda premium
I just rename folders I made like .picture and this will hide it from gallery. If you can't do it in default folders just move the items in your own folders.
Sent from my GT-N7000 using xda premium
Adding a file name .nomedia in the folder will prevent media scan for picture file in that folder, it is working in GB. After upgraded to ics it's not working.
Sent from my GT-N7000 using xda premium
Just make a new folder and put a fullstop infront. Copy your files into that. Simples
Sent from my GT-N7000 using xda premium
hmm, strange, same thing is happening with me, but only for newly added .nomedia files.
i have .nomedia files in loads of folders containing app specific pictures, and they don't appear in the gallery, but if i add a .nomedia file to one of my own folders it seems to be ignored by the default gallery, even though quickpic hides the folder as intended.
have you tried wiping the "media storage" data under application settings?
I have exactly same problem as your. After I cleared gallery and media data, only existing pictures are ignored. If I add new picture, gallery will show up again.
Did you perform factory reset after upgraded to ics?
Sent from my GT-N7000 using xda premium
i've had ics since the german rom was released, and yes, i did a factory reset afterwards.
i have numerous folders with .nomedia files in them that are constantly being updated with new pictures by apps etc. and the gallery still ignores them, it only seems to be a folder that the gallery has already indexed, when i add a .nomedia file to it, the gallery still shows it.
just did a media storage wipe and the folder i put the .nomedia file into has disappeared as expected after a reboot.
moved another picture into the folder and checked again and it's still hidden from the gallery.
I think this is being caused by a change to the behaviour in ICS that triggers a media scan. I have an issue where just renaming a .nomedia file would trigger a media scan in gingerbread but does not in ICS, hence files in the folder are not shown in the gallery even though the .nomedia file is renamed.
I suspect this is the case here, that adding the new .nomedia does not trigger the media scan.
I am having the same problem, but with mp3 and wav files. I have many that are created by programs like Loopstack, Caustic and Audio Evolution that I don't want appearing in my music player.
What I found works, is if you create the .nomedia file on the phone.
Then connect the phone to a PC via MTP.
Rename the folder (I just add a 1 to the end).
Rename it back to the original folder name.
Disconnect the phone and it rescans and "recognises" the .nomedia file.
HTH,
Rich
I added the .nomedia file to my folder, wiped data from media storage (under applications), rebooted the phone and the files no longer appear in the Gallery.
This method only work for existing media file, subsequent new add media file will be shown up again.
Sent from my GT-N7000 using Tapatalk 2
.nomedia with images and music files
I think I've been able to solve this somewhat.... For those who have an audio file and an image(in your music folder) and you don't want the image showing up in the gallery but you do want it showing in your music directory(album art), you will need to go into the folder with the picture-create a folder(i call it 'pic')-put the image in that folder along with a '.nomedia'. Make sure that the music file is not in the new folder but the new folder is within the overall folder.... Confused? Music/U2/The Joshua Tree/Pic/Image and .nomedia file - Hope this helps
you can see images here:
androidforums.com/samsung-galaxy-s3/595398-nomedia-your-music-images-showing-gallery
It still shows your image with the music\artist in the media player, but now doesn't show in the gallery. You do not need to rename the music folder(like you would if you were just adding a .nomedia file) because your adding a new folder all together.
just clear cache as someone said and reboot phone.. good enough to have the .nomedia work with existing photos.. As mentioned when you add more you will have to do it again.
Adding .nomedia to a folder should make android gallery ignore that folder. But for some reason a movie i received thru bluetooth keeps on appearing even ic i already put a "." on ghe directory, or moved to another directory or even create new folder add nomedia then move the file. Pls help me hide this file from my gallery. Im using stock ics. Thanks
dknight178 said:
Adding .nomedia to a folder should make android gallery ignore that folder. But for some reason a movie i received thru bluetooth keeps on appearing even ic i already put a "." on ghe directory, or moved to another directory or even create new folder add nomedia then move the file. Pls help me hide this file from my gallery. Im using stock ics. Thanks
Click to expand...
Click to collapse
Try deleting the cache from the Media Storage app and rebooting. Alternatively you can download any number of apps from Google Play to hide files and folders.
Sent from my GT-N7000 using xda premium
What is the preload folder for? Most of the APKs in it are also in the system folder. But the system folder has the corresponding odex files that come with the APKs. Is it safe to delete the ones in the preload folder?
Sent from my GT-N7000 using Tapatalk 2
I delete multiple applications preload before installing the ROM and never had any problem, I have done over 10 ROMs. You can delete without fear.
---------- Post added at 08:49 PM ---------- Previous post was at 08:48 PM ----------
And you can delete to system/app too :good:
I have no intentions of un installing any of my apps. I'm just wondering if deleting the APKs in the preload folder won't affect what's already installed in my phone.
Sent from my GT-N7000 using Tapatalk 2
l0rd_almighty said:
I have no intentions of un installing any of my apps. I'm just wondering if deleting the APKs in the preload folder won't affect what's already installed in my phone.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
There will not.
l0rd_almighty said:
What is the preload folder for? Most of the APKs in it are also in the system folder. But the system folder has the corresponding odex files that come with the APKs. Is it safe to delete the ones in the preload folder?
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
It could be mostly because you came from a rom that used preload partition and before installing the new rom, you did not format preload partition.
nokiamodeln91 said:
It could be mostly because you came from a rom that used preload partition and before installing the new rom, you did not format preload partition.
Click to expand...
Click to collapse
I did. Formatted systems folder as well. Even used philz cleanup tool via his kernel just to make sure.
Came from the Ultimate rom based of the JB leak. Formatted the system folder, the preload folder. Wiped dalvik and cache. Then did the clean up using philz kernel.
I then installed the official German JB using PC odin and rooted once more using philz kernel.
i have not installed the stock rom.. so you mean to say on stock rom the apps are there in both preload and system folder?
nokiamodeln91 said:
i have not installed the stock rom.. so you mean to say on stock rom the apps are there in both preload and system folder?
Click to expand...
Click to collapse
Not all but some of them are. One example is the SecGallery2_Galaxy.apk. I can see it in both the preload and the system folders. A couple more examples are SecSettings.apk, the SecEmail.apk and a few more.
Reason I'm asking is I wanted to install a few mods like the Airview and the Lockscreen shortcuts, both of which were excluded in the official JB release for some reason. Instructions that were mentioned in thier respective threads here in XDA is to install either the preload or the system version of the zip files via cwm. I have to choose one or the other "depending" on where the original APKs are. That's where my problem comes in. For the Airview mod, I have the SecGallery in both the preload and the system folders. So I want to know how to figure out which one of those folders I should be using for the mods that I mentioned.
I installed the stock odexed rom and used the xml to permissions folder and the gallery apk to system. Change permissions and air view works.
nokiamodeln91 said:
I installed the stock odexed rom and used the xml to permissions folder and the gallery apk to system. Change permissions and air view works.
Click to expand...
Click to collapse
I'm going to try it out when I get home.
They are in preload as the system partition is no longer big enough to handle jb roms efficiently. Preload is now just an extension of system without the need to repartition tue phone
The equivilant app in system folder is jusy a placeholder apk its 1kb and contains a link to the preload app.
You can move some to system if you wish but you may face issues as the partition becomea fuller.
Sent from my GT-N7000 using xda premium
But that's not what I see in the stock odexed rom. In that there are 2 gallery apk one in system/app of 12.07MB and one in preload of the same size.
nokiamodeln91 said:
But that's not what I see in the stock odexed rom. In that there are 2 gallery apk one in system/app of 12.07MB and one in preload of the same size.
Click to expand...
Click to collapse
Same with me. 2 of the same size in each of the folders.
Sent from my GT-N7000 using Tapatalk 2
Re: Preload and system foderPreload and system foder
To understand this better,you need to know about symlink in linux os.
Symlink is like shortcut to a certain file in windows.Symlink actually creates a path to original file in a specific directory.
In roms,preload/symlinks/ is symlinked to /system/apps.Linux(also android) shows symlinked files in both source directory and also the destination directory creating an *illusion* that the file exists in both the directories.But in reality,the file exists only in source directory which is /preload/symlinks in this case.The symlinked files in /system/app are just a generic pointer to the files in preload.
Deleting symlinked file in /system/app will also delete original file in /preload and vice-versa.
Long story shortreload is just an place holder for extra apps which is accessed via shortcut in system/apps.(This not an absolute/accurate answer)
Sent from my GT-N7000 using xda app-developers app
Thanks Vijai for the explanation.. i understand that these are pointers.. but should be of the same size as the one in preload ? In deodexed roms there is only one file but in odexed .. there are 2
nokiamodeln91 said:
Thanks Vijai for the explanation.. i understand that these are pointers.. but should be of the same size as the one in preload ? In deodexed roms there is only one file but in odexed .. there are 2
Click to expand...
Click to collapse
It is not two files of same size actually.After symlink,the os mirrors the atributes and properties of the file from preload to system.So we feel that the file actually exists in two places of same size.But it is not.It only exists in preload.
Sent from my GT-N7000 using xda app-developers app
Ok this makes sense.. But if I pull the one from system/app using adb, should I get the link or the entire app? I currently get the app.
nokiamodeln91 said:
Ok this makes sense.. But if I pull the one from system/app using adb, should I get the link or the entire app? I currently get the app.
Click to expand...
Click to collapse
The app.You get a file(which represents error) only if the symlinked file/directory goes missing.That means,if 2 dir are symlinked and the source dir goes missing,the symlink turns into a file which is not the case if a file is missing inside the directory.But if the symlink is between files,Symlink is broken if the source file goes missing.
Have you got ubuntu on your pc?When try symlinking and experiment with it,It will answer most of your doubts .Actually ubuntu shows it more graphically than android which does gets u confused
Sent from my GT-N7000 using xda app-developers app
Looking for a definitive answer here, as I have searched and read and I still have yet to find an answer so please don't tell me to go search or read such and such thread. Thanks.
So I have gone from 4.1 to 4.3 and back and forth several times and my question is how to handle the file structure change. I understand that a new emulated file structure is located at data/media/0 but should I copy my old data there? Is there anyway to prevent the multiple user file structure? I tried pushing a layout_version file and changing permissions but when I flashed a 4.3 Rom it still created a 0 folder.
Sent from my HTCONE using Tapatalk
Konfuzion said:
Looking for a definitive answer here, as I have searched and read and I still have yet to find an answer so please don't tell me to go search or read such and such thread. Thanks.
So I have gone from 4.1 to 4.3 and back and forth several times and my question is how to handle the file structure change. I understand that a new emulated file structure is located at data/media/0 but should I copy my old data there? Is there anyway to prevent the multiple user file structure? I tried pushing a layout_version file and changing permissions but when I flashed a 4.3 Rom it still created a 0 folder.
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
The actual location when viewed with a root file manager has been here on 4.1.2:
/data/media
Once you flash a 4.3 ROM, the actual location gets changed (and all the files moved) to here:
/data/media/0
The problems arise if the version of your custom recovery is not compatible with a 4.3 ROM. If it is not and you keep flashing 4.3 ROMs you might soon end up in trouble. If, while using the 'older' custom recovery, you continue flashing, your sdcard ends up somewhere around here:
/data/media/0/0/0/0/0/0 (etc.)
with all your files copied to every '0' directory and your symlinks end up the same way, and your device quickly runs out of space
Using a file manager that will show hidden files and folders, copy/move the files in the last '0' directory to:
/data/media/0
Now you can delete all the "extra 0" except for /data/media/0
Reboot
Profit?
Sent from my HTCONE using Tapatalk
elvisypi said:
The actual location when viewed with a root file manager has been here on 4.1.2:
/data/media
Once you flash a 4.3 ROM, the actual location gets changed (and all the files moved) to here:
/data/media/0
The problems arise if the version of your custom recovery is not compatible with a 4.3 ROM. If it is not and you keep flashing 4.3 ROMs you might soon end up in trouble. If, while using the 'older' custom recovery, you continue flashing, your sdcard ends up somewhere around here:
/data/media/0/0/0/0/0/0 (etc.)
with all your files copied to every '0' directory and your symlinks end up the same way, and your device quickly runs out of space
Using a file manager that will show hidden files and folders, copy/move the files in the last '0' directory to:
/data/media/0
Now you can delete all the "extra 0" except for /data/media/0
Reboot
Profit?
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
Thank you, I understand all that. What I don't get is should I copy all over my old data (backups and so on) into the /data/media/0 folder?
Sent from my HTCONE using Tapatalk
Konfuzion said:
Thank you, I understand all that. What I don't get is should I copy all over my old data (backups and so on) into the /data/media/0 folder?
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
Yes that's what I said
Sent from my HTCONE using Tapatalk
Konfuzion said:
Thank you, I understand all that. What I don't get is should I copy all over my old data (backups and so on) into the /data/media/0 folder?
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
I personally only do it on an as-needed basis, but it really depends on your usage. Before switching b/t 4.1 and 4.3+ ROMs, I make sure to copy/paste my SMS backup and/or MyBackup (rerware) backups to the appropriate file structure I am moving to. The apps themselves will only look in their current file structure when you try to restore. Of course in order to copy/paste the backups, you have to allow root access in ES File Explorer or whatever you use. TWRP backups can stay in the /0 structure just fine, as it will always look there in recovery.
Music and pics can be a challenge since they take up a lot of space, and replicating them in two different file structures will eat up a lot of storage. I don't store a lot of media on my phone, though, so I'm not sure the best way to address that. It's easy enough to find pics through file explorer, but I'm sure music playing apps only look in one folder or structure by default.
For most other apps, they will store their settings in each structure without taking up too much space, so it's fine to leave them as-is. Whenever you restore a Nandroid it's going to overwrite them again anyway.
Not sure if I have helped, but just sharing my experience.