Related
Hey guys,
Been searching on this for a whle and haven't found the info I'm looking for.
How does the custom APPS2D actually work? By that I mean, what is it really doing? I know it's copying the app(s) to the partitioned ext2/3/4 area of the sdcard, but how does it know *what* part of the app to move as it seems something is always left on the phone.
I'm currently running AdamG's OpenDesire 3.0.5 (nice) and thanks to the script provided by msdl28712 in this thread here http://forum.xda-developers.com/showthread.php?t=748529, I can see that APPS2SD is saving me "188MB". Pretty nice.
But my internal memory is still going down. I started out at about 148MB I think. I'm currently at about 115MB free. Of course, that's fantastic - but it sort of suggests that, even though I've downloaded loads of apps to the sd card, they will always leave some footprint/config/data on the internal memory of various sizes (as I can see it on my info page).
So really, I am still quite limited in the number of apps I can store. Even though I gave myself a nice big 4gb ext4 partition, I'll still hit a limit because of the footprint data left behind on the phone's int memory even after "copying to SD".
Is this right or am I way off?
Although I have no Actual knowledge of what you ask I will say this. The phone needs to be able to function if there is a SD card installed or not and therefore it must have info about the apps installed in the phone memory. I would imagine its very similar to windows and the windows registry. The registry will always be stored on the windows (Phone) storage and the program resources can be anywhere. Therefore when you install an app there will always be a small amount of phone storage required to link to and handle the operations of that program.
All in my opinion.
Some apps, not all, I've found in multiple places on my Eris.
I found it strange that the market wasn't consistently placing them in both places ( actually, that's a good thing, cause it would eat double the space ), but that led me to believe that the developer who wrote whichever particular app that was being stored in 2 location, wrote it to store to additional "backup" location ...
For example, say you download an item from the Android market, and it puts it in the "data\app" folder location. Well, I'd also find another copy in the root of the "cache\" folder ....
The way I found this, was I wondering where the heck all my memory was going, especially since I'd recently installed/uninstalled some various music player apps, but the space wasn't being freed up. I went digging through various folders looking for items, and low and behold, started finding the duplicately stored APK files. I started removing them, and I've monitored that files contents on a regular basis since, which has helped.
- JB
What A2SD? A2SD+, A2SD Froyo?
Found a nice explanation on CM Wiki... can't find it now though...
but there's always short explanation by MIUI Au..if you wanna give it a tryy
http://www.miui-au.com/faq/a2sd/
johnrbrown1968 said:
Some apps, not all, I've found in multiple places on my Eris.
I found it strange that the market wasn't consistently placing them in both places ( actually, that's a good thing, cause it would eat double the space ), but that led me to believe that the developer who wrote whichever particular app that was being stored in 2 location, wrote it to store to additional "backup" location ...
For example, say you download an item from the Android market, and it puts it in the "data\app" folder location. Well, I'd also find another copy in the root of the "cache\" folder ....
The way I found this, was I wondering where the heck all my memory was going, especially since I'd recently installed/uninstalled some various music player apps, but the space wasn't being freed up. I went digging through various folders looking for items, and low and behold, started finding the duplicately stored APK files. I started removing them, and I've monitored that files contents on a regular basis since, which has helped.
- JB
Click to expand...
Click to collapse
First of all you are answering a quite old thread(hint: 8th august)
Second to clarify no, the app is not installed to several locations.. The apk file in the cache is just the one, that the market downloads in order to install it(hint: cache) upon installation the file is placed in the /data/app folder or in case you are using a2sd/a2sd+ it will be placed in /sd-ext/app(the phone still think it is in /data/app, but it wont take up space on the /data partition)
After the installation the downloaded .apk file is sometimes left behind, but as the /cache partition have a fixed size, this won't take up any space for app installs(/data) when the space is needed on the cache partition for another download or something else, the file is eventually deleted.
edit: for people, who want to know the answer to OP, please search I and many others have wrote it over and over again in this very forum.
Ok, I have a 16gig card, and had about 250 MB free, went to check, and over the space of a few days, not having taken many photos or videos, or downloading much, I was down to like 35MB, looking through my SD Card, I have loads of files and folders which I don't know what they are, some of them very small (CDAInfo on Root of SD Card, MEMSTICK.IND on Root of SD Card, etc. etc.) but some of them are quite large.
Also, looking through my Xperia Play games launcher, I have many apps that are doubled, and clicking on both opens it, so it's not just an empty container. Looking at my folders on the SD Card (.android_secure), I have things like flashplayer-1.asec and flashplayer-2.asec, each one is 16MB, and I have many of these duplicates for different apps and games. Now, I think that the .android_secure folder is used for when you move your apps to the SD Card, and I'm assuming that this occured when I flashed a new rom and reinstalled the apps (the data was created on the phone memory and then when I went to move it over, it created the 2nd version) but what I want to know is, how to AVOID this happening when I flash a new Rom, or basically, how do I avoid things like this happening.
Thanks,
Niall
Just went through the .android_secure deleting one of the multiples then checking if it still ran, it did, so I decided to delete one of all of them, and bam, all apps still run, and I'm up to 1GB of free space. The .asec files are what the phone moves to the memory card when you select move to SD in the settings. Obviously, if you are flashing a new rom it doesn't delete them, and then just creates a duplicate. Some old games that I don't play (have completed them) were still in there, some of them ridiculous sizes (Battle Bears - 47MB). Removed about 20 or so off the .asec files, most of them duplicates, some of them were unused apps, and am back up to 1Gig free.
Chuffed
Anyways, anyone know a way to avoid this happening, and also, as a word of warning to everyone...keep an eye out for things like this
Niall
Nhialor said:
Just went through the .android_secure deleting one of the multiples then checking if it still ran, it did, so I decided to delete one of all of them, and bam, all apps still run, and I'm up to 1GB of free space. The .asec files are what the phone moves to the memory card when you select move to SD in the settings. Obviously, if you are flashing a new rom it doesn't delete them, and then just creates a duplicate. Some old games that I don't play (have completed them) were still in there, some of them ridiculous sizes (Battle Bears - 47MB). Removed about 20 or so off the .asec files, most of them duplicates, some of them were unused apps, and am back up to 1Gig free.
Chuffed
Anyways, anyone know a way to avoid this happening, and also, as a word of warning to everyone...keep an eye out for things like this
Niall
Click to expand...
Click to collapse
Have you been flashing roms and not deleting your old .android.secure folder? That will happen, you should delete it before you reflash
AndroHero said:
Have you been flashing roms and not deleting your old .android.secure folder? That will happen, you should delete it before you reflash
Click to expand...
Click to collapse
lol, yeah, i'm new enough to Android, but learning as I go along
I have E4GT with Caulkins 2.9.1.
I have the following storage available on my device:
SD Card 24.25GB
USB Storage 3.25 GB
Device Memory 1.23 GB
I get the following error when trying to update apps, or install new apps:
"There is insufficient space on this device"
I have gone into settings>apps>google play> clear cache. -> no change
I have downloaded App Cache Cleaner app and cleared all cached files. -> no change
The error message is a lie written by a lazy programmer. What's actually happening is that the installation is trying to copy or move a file and can't. To circumvent this problem I have to enter root explorer and look for files related to the program I'm trying to upgrade and delete them. Sometimes I just find dangling files which aren't really needed; other times I have to delete the whole shebang and reinstall the program from scratch. One process that I've noticed can sometimes cause this problem is the auto-Odex routine that is available in the Development folder.
Bottom line though is that this problem has NOTHING to do with your available memory space.
Henri Blanche said:
The error message is a lie written by a lazy programmer. What's actually happening is that the installation is trying to copy or move a file and can't. To circumvent this problem I have to enter root explorer and look for files related to the program I'm trying to upgrade and delete them. Sometimes I just find dangling files which aren't really needed; other times I have to delete the whole shebang and reinstall the program from scratch. One process that I've noticed can sometimes cause this problem is the auto-Odex routine that is available in the Development folder.
Bottom line though is that this problem has NOTHING to do with your available memory space.
Click to expand...
Click to collapse
How do I find dangling files in explorer. Is there a was for me to determine which ones are wasted files?
before i read your reply i went into recovery and wiped cached and dalvik cache, thought it worked, because i was finally able to install or update about 3 apps, but then got the same error on the 4th app.
so those steps that have been suggested by others on different devices but with similar errors, did not resolve this issue on E4GT.
thanks for any additional help.
This may help http://bit.ly/GNQOZh take a read. I fought this a while ago and went nuts till I did what I describe.
It's usually, but not always, as simple as looking for files with the name of the program imbedded. The most recent program for me was AudioGalaxy.... so I just searched for and deleted any reference to the program that didn't look essential.
If you're REALLY stumped, then download a program from the Market like Log Viewer, which shows you the real-time system log of your Android operating system. That's how I discovered that a failed file copy was being misinterpreted as a full disc in the first place. It also will show you the name of the file being copied or moved and into which directory. Helpful hint: cut and paste the log into something like Notepad for easier reading.
By all means empty out your caches... but only to remove a potential file that's causing you a problem. Like I said, you haven't run out of free space.
Good luck!
A common source for this error is also that there are partitions on your phone that are not visible in the system settings, but which can fill up too.
If you open a console on your device, i.e. with terminal emulator, and type "df" you should see every partition and how much space is free on it.
leaderbuilder said:
This may help take a read. I fought this a while ago and went nuts till I did what I describe.
Click to expand...
Click to collapse
I did this earlier, and then downloaded App Cache Cleaner app and cleared all cached files which did not result in a solution...
im working on other suggestions from this thread
CandyIsYum said:
I did this earlier, and then downloaded App Cache Cleaner app and cleared all cached files which did not result in a solution...
im working on other suggestions from this thread
Click to expand...
Click to collapse
App Cache Cleaner isn't really that thorough.
Try SD Maid.
CandyIsYum said:
I did this earlier, and then downloaded App Cache Cleaner app and cleared all cached files which did not result in a solution...
im working on other suggestions from this thread
Click to expand...
Click to collapse
You 'cleared data' on the media and still had this issue? http://mikemartinezonline.com/blog/wp-content/uploads/2012/02/03.png I've had this issue a few times with a few people- again it just happed to me yesterday! Seems that the media storage, media hub, oovoodo, and some others were taking up huge amounst of space. In fact my media storage was at 800MB until I cleared it. Especially noticed this for me after adding and removing media and swapping different sd cards.
leaderbuilder said:
You 'cleared data' on the media and still had this issue? ] I've had this issue a few times with a few people- again it just happed to me yesterday! Seems that the media storage, media hub, oovoodo, and some others were taking up huge amounst of space. In fact my media storage was at 800MB until I cleared it. Especially noticed this for me after adding and removing media and swapping different sd cards.
Click to expand...
Click to collapse
I cleared the app cache there, and still had the issue. I also went into recovery and cleared cache, dalvik cache.
I didn't try the SDMaid method, so if someone else has this same problem, that may be a place to try.
I ended up starting with scratch with my device, and just upgraded to calkulin 2.9.2.
now my device is functioning as expected, and i can finally install angry birds space...
Well same problem shows up again.
updated to Calkulin 3.0, in hopes to resolve the problem, but still no go.
insufficient space when trying to install or update app from google play.
SD Card: 3.25GB Free / 29.7 GB
USB Storage: 7.29 Free / 11.50 GB
Device: 1.29 GB Free.
It's kind of annoying, is this something that would be resolved by going back to stock. This is getting a bit annoying.
thanks again.
Which app?
Edit: Have you tried clearing data for google play in settings/applications/all yet?
Sent from my SPH-D710 using XDA
com.android.process.media (Android Media Process is (ab)using CPU)
so, I've tried:
Settings -> Apps -> ALL -> Media Storage -> “Force stop” & “Clear data”
That didn't really help at all(((
community's users suggests following:
* its due to corrupted music/pictures (I don't have any music/pictures on my phone).
* suggestion to reformat sdcard, but toro doesn't have SD card, although through recovery I was able to check filesystem of /userdata mount point (see below):
~ # e2fsck -n /dev/block/platform/omap/omap_hsmmc.0/by-name/userdata
e2fsck 1.41.11 (14-Mar-2010)
/dev/block/platform/omap/omap_hsmmc.0/by-name/userdata: clean, 53630/1875968 files, 1921615/7493115 blocks
~ #
Click to expand...
Click to collapse
aside the fact that phone works extremely slow upon boot (due to com.android.process.media) all that high CPU eating a lot of battery (battery life isn't that great to begin with) but thanks to this bug I get to use even less.
after deleting nanodroid's backup (ROM manager), I'm seeing following (through logcat):
D/MediaProvider( 6784): object removed 71054
D/MediaProvider( 6784): object removed 71055
D/MediaProvider( 6784): object removed 71056
D/MediaProvider( 6784): object removed 71057
D/MediaProvider( 6784): object removed 71058
Click to expand...
Click to collapse
i read that if you have folders with a lot of media/picture files, it will sometimes hang while scanning. start fresh, factory reset/reflash google factory images.
bk201doesntexist said:
i read that if you have folders with a lot of media/picture files, it will sometimes hang while scanning. start fresh, factory reset/reflash google factory images.
Click to expand...
Click to collapse
i dont want to loose my /data so doing factory reset won't work for me
I had an issue with this at the beginning of the week.
I had read that it was corrupted media files, so I began investigating. I was able to fix the problem by browsing through my pictures and deleting some images that had somehow become corrupted. The corrupted files were just washed out black squares. No SD format / factory reset was needed.
t3h_g3n3r4l said:
I had an issue with this at the beginning of the week.
I had read that it was corrupted media files, so I began investigating. I was able to fix the problem by browsing through my pictures and deleting some images that had somehow become corrupted. The corrupted files were just washed out black squares. No SD format / factory reset was needed.
Click to expand...
Click to collapse
i thought that would be a problem) i found one and i delete, restarted my phone and still android media process is at least 20% cpu(
I had about half a dozen across several folders that were corrupt. I was looking at the android media process consuming my battery in about 3 or 4 hours until I deleted the bad images. I can now make it through most of a day without any problems.
Somewhere in your phone, a corrupted file lurks. It may not be where you're thinking, but it's there. And it's hungry.
t3h_g3n3r4l said:
I had about half a dozen across several folders that were corrupt. I was looking at the android media process consuming my battery in about 3 or 4 hours until I deleted the bad images. I can now make it through most of a day without any problems.
Somewhere in your phone, a corrupted file lurks. It may not be where you're thinking, but it's there. And it's hungry.
Click to expand...
Click to collapse
i went through all of my gallery and deleted those, yet after restart still doing something and by the time it's done something whatever it was doing i have 90%-70% left!!! AAAAA
is there a way to find those files some other way? can i see some debug information of gallery/android media process and see where hiccup is?
it really kills my battery( anyone has any ideas?
So yesterday I've had it and copy ask of my pictures from my phone to computer and delete them from my phone...
Reboot... and guess what?
It's still using 40/50% of cpu for about first 15 min after I reboot my phone which kills my battery big time(
I need help, anyone??
Sent from my Galaxy Nexus using Tapatalk 2
is there a way to turn on some detailed debug to figure out what's causing this exactly?!
a1exus said:
com.android.process.media (Android Media Process is (ab)using CPU)
so, I've tried:
Settings -> Apps -> ALL -> Media Storage -> “Force stop” & “Clear data”
That didn't really help(( Any other ideas? I keep reading that users saying its due to corrupted music (I don't have any music on my phone).
People are also suggesting to reformat sdcard, but we don't have SD card. Please advise, as one thing it uses CPU the other thing it uses battery and battery life isn't that great to begin with. Is there a way to do fsck or something to make sure there is no corruption of any kind?
*** UPDATE ***
I went into recovery and using adb shell got into a system can I do something like this?
Click to expand...
Click to collapse
I am having the same issue. I found this article but it says the same as the others here.
http://www.transformerforums.com/fo...help/24279-solved-media-using-94-battery.html
If I find anything else out or if you figure something out, let me know also.
a1exus said:
i dont want to loose my /data so doing factory reset won't work for me
Click to expand...
Click to collapse
Your pics and stuff are not in the /data folder. You won't really lose anything important. That is the directory a factory reset/data does. It just basically gets rid of the apps that you had installed. If you are already rooted just get titanium backup to restore. I assure you, I had the same problem up until yesterday. The factory reset was the only thing that fixed it.
The /data wipe is not going to get rid of your pics taken with the phone.
If you do a backup first you have nothing to lose by trying.
On a side note, your Galaxy Nexus does have an "sd card" it's just an internal partition.
Hope you get this resolved.
rushter said:
Your pics and stuff are not in the /data folder. You won't really lose anything important. That is the directory a factory reset/data does. It just basically gets rid of the apps that you had installed. If you are already rooted just get titanium backup to restore. I assure you, I had the same problem up until yesterday. The factory reset was the only thing that fixed it.
The /data wipe is not going to get rid of your pics taken with the phone.
If you do a backup first you have nothing to lose by trying.
On a side note, your Galaxy Nexus does have an "sd card" it's just an internal partition.
Hope you get this resolved.
Click to expand...
Click to collapse
I deleted manually all of my pictures/music yet I still having this issue((
I do have Titanium Backup and I backup my phone regularly, I may try do that...
Do the wipe, trust me. A few installs of programs is not an issue. Your personal data is not lost. Just reinstall your shops that you need and if the days is missing restore with titanium backup.
You will keep having these issues until you do.
Sent from my Nexus 7 using Tapatalk 2
Im having the exact same problem.. Media is 50% CPU, and my S3 gets hot until I stop the Media process after each reboot.
I would like to find a fix before going threw a wipe.
rushter said:
Do the wipe, trust me. A few installs of programs is not an issue. Your personal data is not lost. Just reinstall your shops that you need and if the days is missing restore with titanium backup.
You will keep having these issues until you do.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I was having the same problem and the phone was burning a hole in my pocket.
I found that the problem only seemed to occur on a reboot with android.process.media consuming 96% of the CPU for approximately 40minutes.
I attempted to add a .nomedia file to every single directory on the root of my internal SDCARD. - This made no difference.
I discovered that if I killed the process via the terminal it was eventually restarted by zygote and the same issue occured.
I found the only way to stop this from occuring was to Freeze the "Media Storage" app using Titanium Backup. But (not surprisingly) other things did not work - eg being able to capture a screenshot.
I also discovered that if I went into Titanium Backup and issued a "Clear Cached Data" for the Media Storage app, this resulted in the process ceasing it's CPU consumption - useful - but hardly a silver bullet and an annoying step to take after every reboot. (Additionally I do not know if the scan process might of kicked off automatically at some later stage anyway).
Interestingly I discovered that the phone did not overheat when it was plugged into a power supply - completely unrelated but none the less I found this interesting cause I always thought it was the CPU causing the overheating - when in actual fact it was the battery being emptied - unrelated to the issue at hand but none the less a nice tangent
Now this is what I discovered:
I have an application called NZ Topo Maps, it creates a absolutely massive directory structure to download all the tiles of NZ and cache them locally. Each directory can have many sub directories which in turns has many more and can have many many files in each.
So I deleted the entire tilecache. The result - after a reboot android.process.media consumed 5seconds of CPU.
Not convinced I browsed some maps and "cached" ~64MB of tiles - rebooted - 2:33mins of CPU time consumed... hmmmm.
So I cached ~128mb of tiles - 7:44mins of CPU time consumed after a reboot - diffidently onto something here....
Of interest - every single directory which the NZ Topo Maps program creates has a ".nomedia" included and all of the files are labelled with a *.jpg_ suffix.
So I decided to do some more research - Under the structure I had 425 sub-directories and 10615 files that ended with the suffix .jpg_
Out of curiosity I deleted all the files (including the .nomedia) and left the directory structure completely intact.
After a reboot the media process consumed 32sec of CPU time.
For the final test I deleted the directory structure:
CPU consumed: SIX seconds!!!!
Solved: Why android.process.media is consuming so much battery.... for me atleast.
So in conclusion it seems that:
1) The .nomedia directive applies only to the current directory - android.process.media will still recurse into sub directories
2) The .nomedia does not make any difference to the time it takes media to process the contents of a directory - eg - it was still doing "something" with the files in the directory.
3) The naming of files .jpg_ does not make any difference either, the process will still look at them - not sure if it is supposed to or not.
Where to from here - I would really like to find the source for this process and have a look at it's logic, but right now I just don't understand the android internals enough to be able to determine where the source is located in the source tree! I have posted another thread about this - http://forum.xda-developers.com/showthread.php?p=34326153#post34326153 hopefully someone will give me an answer because this situation is less than ideal.
Hopefully this helps someone else and sends them in the right direction?
Rowan
All,
I found this link. I would post a click-able link but I am not allowed as I am a new forum member - so I am afraid you'll have to type it in the old fashioned way from the image below.
Please head over and "STAR" the bug and/or add your own comments / experience, the more visibility it gets the more likely it is to be fixed.
Cheers.
-Rowan
I have a new HTC One X+ running JB 4.1.1 Sense+. I noticed this happens off and on that the phone gets hot and battery plummets. Using Android Task Manager, realtime process viewer and showing system processes setting turned on, I discovered also it is android.process.media consuming the CPU.
I have over 2,800 mp3 files, most are highquality high bitrate, 16GB worth. They are all put into a directory structure based on artist and album name. I'm sure this is what the process is choking on.
The question is, is it some sort of indexing that just takes days or is it going to happen every time I reboot the phone? The USB charge can't even keep up with the batter drain when it is doing this.
every reboot, so don't reboot your phone)
jazee said:
The question is, is it some sort of indexing that just takes days or is it going to happen every time I reboot the phone? The USB charge can't even keep up with the batter drain when it is doing this.
Click to expand...
Click to collapse
It happens every reboot. The following workarounds are available:
a) not reboot
b) reboot only when you are connected to power
c) use TitaniumBackup to Freeze "Media Storage" (requires root)
d) Settings -> Apps -> ALL -> Media Storage -> “Clear data”. NB: A Force Stop will result in the process being restarted by Zygote at a later time.
e) delete the large directory structure and directories with 1000's of files.
(c) works indefinitely but things stop working - eg - screenshot fails
(d) seems to work until the next reboot but all of your media is gone from the native library - but this may not effect third-party players/apps
If you're using too much power when charging via USB, you might want to get a plug in wall adapter which can supply more current.
It's a really bad situation and seems to be effecting every build of JellyBean - it's a defect in the core software.
Things which do not work:
.nomedia - placing .nomedia files in all directories, some of the directories or the root directories has no noticeable effect.
renaming files - renaming media to an unknown extension (e.g., picture.jpg -> picture.abc) has no effect
-Rowan
I personally went through:
deleting broken images inside of my gallery
deleting my music
deleting my pictures
checking filesystem on my /sdcard partition
deleting some large directories that contains a lot of files
placing .nomedia inside of some directories
bloging about this: Android Media Process (high CPU) | alexus' blog
about to commit suiside #$%#&@!)
and almost every time when i (re)boot my phone and i'm not plugged in, i'll lose about 10% of battery in first 10min of my phone is doing something...
Google! fix it already!))
Okay I have a serious issue. Randomly after moving my game data from PC to Android/obb the files mysteriously poof.
The really strange part is, is that they are not getting deleted, my file system still shows that the space is being used.
The files are nowhere to be found, and the Obb Folder is empty. This has happened countless times after full wipes and reflashing.
I am running Gummy M4 Rom 4.4.4, this seems to happen with or without xposed installed. It also seems to happen after moving a lot of data to obb.
Anyone have ANY idea what is going on?
Edit:
Upon further investigation, what seems to be happening is
After moving data to /sdcard/android/obb via pc (mtp) and rebooting
the data then moves itself to
/data/media/0/android/obb
I have no idea why it is doing this. Anybody have a fix?
UPDATE :
Ok so I figured out a workaround for this issue if anyone else is experiencing it.
Basically my obb files were disappearing after a reboot, this was after me doing a fresh rom flash and restoring the data back to obb folder.
They were then being moved to /data/media/0/android/obb , if you move back the data from here to the original location and reboot, it should stick after for that data + new data as well.
Koshirou said:
Okay I have a serious issue. Randomly after moving my game data from PC to Android/obb the files mysteriously poof.
The really strange part is, is that they are not getting deleted, my file system still shows that the space is being used.
The files are nowhere to be found, and the Obb Folder is empty. This has happened countless times after full wipes and reflashing.
I am running Gummy M4 Rom 4.4.4, this seems to happen with or without xposed installed. It also seems to happen after moving a lot of data to obb.
Anyone have ANY idea what is going on?
Edit:
Upon further investigation, what seems to be happening is
After moving data to /sdcard/android/obb via pc (mtp) and rebooting
the data then moves itself to
/data/media/0/android/obb
I have no idea why it is doing this. Anybody have a fix?
UPDATE :
Ok so I figured out a workaround for this issue if anyone else is experiencing it.
Basically my obb files were disappearing after a reboot, this was after me doing a fresh rom flash and restoring the data back to obb folder.
They were then being moved to /data/media/0/android/obb , if you move back the data from here to the original location and reboot, it should stick after for that data + new data as well.
Click to expand...
Click to collapse
I have found a workaround due to your post and I thought it would be a nice idea to wirte it here.
I came to the counclusion that if I did a fresh new reset factory and installing a large mount of files in the internal storage's obb folder it ended up being deleted after rebotting my tablet.
So I decided to do a few steps the next time I reseted my tablet. First, I copied my files using my pc into the SD Card. Then, I installed a random game from Google Play so the tablet could "adapt itself" and install its own obb folder. After that, I installed my apps but not all at once but one at the time and rebooting after every installation for making sure it was all ok.
It concluded not having the error again and after having deleted the random game from the begining my tablet had finally worked.
Hope this idea helps someone having the same problem as I did. Just don't copy all obb files at once, don't copying it directly from the computer but copying them from the SD Card and install some random game for making sure it can at least hold those obb files.
Good luck!
Hi i just had a similar problem with my huawei nova 3e(p20 lite). I was playing gta:sa and it seems started crashing a lot so i did what the developer said and cleared te cache for gta sa then powered off the phone for a few minutes before turning it back on. Before doing thos step i also use the huawei 'clean up' function under the optimiser seeing as it has these functions built in. When the phone powered back on and tried to play gta sa and it started trying to download the obbs then failed to launch and i went to the file explorer to find out all my obbs were gone.
I have never made a backup of my phone data so the data recovery methods that google suggests wont fix anything as i didnt back them up and i havent got an sd card in the phone so it's not likely that the phone has moved them elsewhere like what happened to the original poster.
Is it possible the cleanup function in the optimizer somehow recognized all the contents of my obb folder as being junk and deleted them all? But that is unlikely as i do this process many times a day when gta starts crashing and once the caches are clear and the phones ram is optimised the game runs fine every other time after a reset. If the files moved somewhere like original poster where might i find them seeing as i dont have an sd card? And if that isnt the case then i suppose i have little choice but to habve to re
download the huge obb files every time the phone wants to delete them? (another thing i noticed is that it was literallt only the obb files gone, my save gamea etc are still present and im a littlest worried if i track down the obbs and put them back or worst comes tl worst redownload them agqin, will rhis make app clear all its current data and delete my saves?