[SOLVED][Q] Low Storage Space Warning - Galaxy S II Q&A, Help & Troubleshooting

I had flashed RootBox, the most recent one, and I started getting Low Storage Space warnings after every reboot. I thought reflashing might solve this problem, so I did the following :
1. In recovery, Wipe Data/ Factory reset
2. Wipe Cache
3. Wipe Dalvik Cache
4. Format /system
5. then Flashed SlimBean 4.2.2 v1 Stable
Now, again I am getting the same problem, I haven't installed many apps though, the list of apps installed are:
1.Chrome
2.Download All Files
3.ES File Explorer
4.Titanium Backup
5.instagram
6.Maps
7.jetAudioPlus
8.MX Player
9.ROM Toolbox
10.Viber
11.WhatsApp
12.YMail
That's All...
I don't know what problem might be.. I have also searched a lot, in XDA as well as Google. but no suitable solution.
Anyone can help me solve this.??

guru_iyer said:
I had flashed RootBox, the most recent one, and I started getting Low Storage Space warnings after every reboot. I thought reflashing might solve this problem, so I did the following :
1. In recovery, Wipe Data/ Factory reset
2. Wipe Cache
3. Wipe Dalvik Cache
4. Format /system
5. then Flashed SlimBean 4.2.2 v1 Stable
Now, again I am getting the same problem, I haven't installed many apps though, the list of apps installed are:
1.Chrome
2.Download All Files
3.ES File Explorer
4.Titanium Backup
5.instagram
6.Maps
7.jetAudioPlus
8.MX Player
9.ROM Toolbox
10.Viber
11.WhatsApp
12.YMail
That's All...
I don't know what problem might be.. I have also searched a lot, in XDA as well as Google. but no suitable solution.
Anyone can help me solve this.??
Click to expand...
Click to collapse
Its viber thats causing your problem look here http://forum.xda-developers.com/showthread.php?t=2117444 under the letter S for storage. I found this answer in 15 seconds under the root box thread. Please look at rom threads for solutions before posting.

Viber Low Storage error when pressing "Hold to Talk"
gaosphappy said:
Its viber thats causing your problem look here http://forum.xda-developers.com/showthread.php?t=2117444 under the letter S for storage. I found this answer in 15 seconds under the root box thread. Please look at rom threads for solutions before posting.
Click to expand...
Click to collapse
None of the suggestions in this thread worked for me. Including the alternative thread you suggested.
Although my problem has very similar symptoms - the cause (and therefore the solution) is different.
Symptoms: Viber (version 4.1.1) gave me a "Low Storage Space" message whenever I pressed the "Hold and Talk" button.
My Solution: I discovered that there was a file called "_ptt_id_counter" in folder /data/data/com.viber.voip that had incorrect uid/gid.
The uid/gid were not the same as every other file and folder in this subtree.
I guess that "ptt" means "press to talk". I also guess that the id_counter (4 bytes in size) is probably a long integer and should be able to be
both written and read. The permissions were only 600 on the file. So, I used adb to chown the uid & gid to be the same as the other files/folders.
It then worked.
I am not an Android programmer. However, I have worked with Unix since 1982 and Linux since 1997.
I also tried booting into recovery and running permissions check/fix. But, I guess there isn't a manifest that specifies what the correct file permissions should be? (I haven't got that far in my OO learning).
I think the culprit that (somehow) caused the error was the Backup app I was using. (Ultimate Backup by Jrummy) but, I can't be sure and I don't want to "point the finger".
If someone could please tell me where in an APK one could locate a "spec"/"layout" of what files should have what permissions - it would be helpful. I know that uid/gid doesn't need to be specified generally because each app runs in it's own sandbox and the uid/gid is set to that of the owning pid. But, there must be something somewhere that specifies what the "chmod" permissions are. Isn't there?
If not - then I just have to assume it's a memory corruption and (perhaps) related to the CM11 Nightly that I am using. But, I am a Newbie and I am not permitted to post in that forum (yet).
-----------------------------------------------------------------
Phone: HTC Desire HD
Rom: Daily driver - unofficial CM11 by Mustaavalkosta.
Radio: 12.69a.60.29U_26.17.14.11_M

Related

Insufficient Storage - Android Market App Download

Okay... I searched the forums and didn't see a good answer to this question so I thought I'd post it here along with what worked for me.
I flashed over to GeeWiz recently from a rooted, stock Fascinate (and I love the new ROM). When I was re-installing my apps, I started getting an error message in the market saying I had insufficient storage. I tried manually remapping the cache using a terminal emulator with no joy (I may have screwed it up).
I finally got fed up and wiped my Dalvik Cache and voila, it started downloading again. I got about 60-80 MB of apps downloaded and hit the wall again. After rebooting into recovery and wiping it again, it started working again.
Problem: Insufficient Storage Space Available (Android Market)
Possible Solution:
1.) Reboot into Recovery (if you don't have Clockwork installed, flash it, then reboot into it)
2.) Using the volume keys, scroll down to advanced
3.) Press the return/go back soft key to enter the next menu
4.) Scroll down to Wipe Dalvik Cache, choose it
5.) Scroll down to Yes - Wipe Dalvik Cache, choose it
6.) Wait until it's cleared
7.) Press the Menu key to go back until you see Reboot System Now
8.) Reboot - It will take a few minutes for the cache to get rebuilt so be patient
Hopefully, this will help some. If anyone else has any ideas, please post them!
Wook
Perhaps you should also wipe regular cache...
Has anyone seen John Connor?
Similar problem on Samsung Vibrant with CM7
Thanks for posting this solution. I just wanted to add on that I'm having a similar problem (Samsung Vibrant Cyanogenmod 7) but it's only when downloading large apps from the market. I can download as many as I want that are a few MB but trying to download one that is around 40MB says I don't have enough space. I've tried wiping Davlik cache and eventually reformatted all partitions and reinstalled ROM clean and still get the same error.
I actually just posted a thread on this and then noticed your solution (even if it didn't work in my case
Might be a different issue, but maybe related. So if anyone has run into similar issues and found solutions I'd appreciate hearing some other solutions too.
I posted a thread on my issue here: http://forum.xda-developers.com/showthread.php?p=18991642#post18991642
but i'll follow both these threads!
That one I think I understand... but, unfortunately the answer is that the Dalvik cache partition (where the market APK's are downloaded to) on many original Samsung devices (i.e. Fascinate) is only about 35 MB in size. Anything larger will get rejected as being too big. Most of the newest devices have a larger download partition.
I've seen a few posts on different forums on remapping the download cache to a different, larger partition... but nothing specific to our devices. I've tried following other posts just to see if it works, but suceeded only in either having no effect or messing it up worse and having to reinstall the ROM (not a big deal, but frustrating).
Until one of the smart people here tells us how to remap **our** cache to a larger partition... I'd do a Google search for the APK of the app you are trying to install. That worked for me to install an app about 40 MB in size.
** edit **
I see that you were able to download the app after deleting everything in the cache folder. I guess your device is lucky enough to have a larger download partition than mine does
Glad to see you got it to work!
** 2nd edit - How to remap your market cache to the SD card **
-- UPDATE -- (Thanks to grickson here at XDA)
Problem: Insufficient Storage Space Available (Android Market)
Possible Solution: Remap cache folder to your SD card
** WARNING **
I am not responsible if you mess up your device doing the following. It manually remaps your market cache to your SD card to give you extra space. The only caveat is that if you remove your SD card (or while the SD card is unmounted) the market will not work. If you are worried about losing market functionality, DON'T try this. If you mistype (or the world suddenly tips over or some other unforeseen consequence), you can ruin your ability to run the Android Market at all. Please remember, you can repeatedly clear your Dalvik cache as often as needed to continue downloading apps. you can also get most larger APK's if you spend a few minutes browsing for them. You have been warned!
** END WARNING **
1.) Download and install a terminal emulator
2.) Open the terminal emulator and type su
3.) Allow the app to always have root access and exit
4.) Restart the terminal emulator and type su, the prompt should change to a #
5.) Type the following commands:
# cd /data/data/com.android.vending
# rm -R cache
# mkdir /sdcard/cache/
# mkdir /sdcard/cache/marketCache
# ln -s /sdcard/cache/marketCache cache
- What these commands do are (in order): change directory to your cache folder, delete the entire cache folder, create a directory on your SD card named cache, create a subdirectory in that one called marketCache, link the phone's market cache to the newly created folder on your SD card
To reverse this process (hopefully):
1.) Open the terminal emulator and type su
2.) Type the following commands:
# cd /sdcard/cache/
# rm -R marketCache
# mkdir /data/data/com.android.vending/cache
# ln -s /data/data/com.android.vending/cache cache
Alternately, (from what I understand) you can just repartition your device and reinstall your ROM of choice using ODIN and your market should be back to the way it was.
I'd seen that same remapping to sdcard idea as well, I just didn't want to mess with it, figured there had to be a way to get it to work right how it's supposed to, but maybe not.
Clearing /cache worked for me though. On my Vibrant with with CM7 market downloads are cached directly in the /cache folder. there's a dalvik-cache folder in there too. but i just deleted everything out of /cache, then downloaded ok, then rebooted and it recreated dalvik-cache folder and other sub folders in /cache. another work around option for people.
rxwookie said:
That one I think I understand... but, unfortunately the answer is that the Dalvik cache partition (where the market APK's are downloaded to) on many original Samsung devices (i.e. Fascinate) is only about 35 MB in size. Anything larger will get rejected as being too big. Most of the newest devices have a larger download partition.
I've seen a few posts on different forums on remapping the download cache to a different, larger partition... but nothing specific to our devices. I've tried following other posts just to see if it works, but suceeded only in either having no effect or messing it up worse and having to reinstall the ROM (not a big deal, but frustrating).
Until one of the smart people here tells us how to remap **our** cache to a larger partition... I'd do a Google search for the APK of the app you are trying to install. That worked for me to install an app about 40 MB in size.
** edit **
I see that you were able to download the app after deleting everything in the cache folder. I guess your device is lucky enough to have a larger download partition than mine does
Glad to see you got it to work!
** 2nd edit - How to remap your market cache to the SD card **
-- UPDATE -- (Thanks to grickson here at XDA)
Problem: Insufficient Storage Space Available (Android Market)
Possible Solution: Remap cache folder to your SD card
** WARNING **
I am not responsible if you mess up your device doing the following. It manually remaps your market cache to your SD card to give you extra space. The only caveat is that if you remove your SD card (or while the SD card is unmounted) the market will not work. If you are worried about losing market functionality, DON'T try this. If you mistype (or the world suddenly tips over or some other unforeseen consequence), you can ruin your ability to run the Android Market at all. Please remember, you can repeatedly clear your Dalvik cache as often as needed to continue downloading apps. you can also get most larger APK's if you spend a few minutes browsing for them. You have been warned!
** END WARNING **
1.) Download and install a terminal emulator
2.) Open the terminal emulator and type su
3.) Allow the app to always have root access and exit
4.) Restart the terminal emulator and type su, the prompt should change to a #
5.) Type the following commands:
# cd /data/data/com.android.vending
# rm -R cache
# mkdir /sdcard/cache/
# mkdir /sdcard/cache/marketCache
# ln -s /sdcard/cache/marketCache cache
- What these commands do are (in order): change directory to your cache folder, delete the entire cache folder, create a directory on your SD card named cache, create a subdirectory in that one called marketCache, link the phone's market cache to the newly created folder on your SD card
To reverse this process (hopefully):
1.) Open the terminal emulator and type su
2.) Type the following commands:
# cd /sdcard/cache/
# rm -R marketCache
# mkdir /data/data/com.android.vending/cache
# ln -s /data/data/com.android.vending/cache cache
Alternately, (from what I understand) you can just repartition your device and reinstall your ROM of choice using ODIN and your market should be back to the way it was.
Click to expand...
Click to collapse
hi, sorry to butt in, but I've been browsing all over trying deleting caches and dalvik caches (which deleted a few of my apps for some reason) and just tried this method but no luck. just wondering if you have any other ideas?
Hello,
Having just encountered the Issue of Insufficient Storage Space Available (Android Market) after loading a recent ROM, it ocurred to me to do just that-Wipe dalvic. I was hoping that would work, rather than having to Odin, etc.
yeah, the remapping cache to sd card, didn't work for me either
I had this problem as well after flashing the stock EH03 Odin package and then flashing SuperClean v3.05 in cwm. I forgot to wipe cache/delvik and had some fc's and got the "Insufficient Storage Space" warning when attempting to download apps from the market.
I booted back into cwm, cleared cache/delvik, went into "mounts and storage" and made sure dbdata was mounted and repaired permissions. Rebooted and all was well!
MOD EDIT: No warez discussion please
Thank you rxwookie :good:, the sd remap worked fine* for me and I did and a wipe dalvik also. On Nexus One ICS BCM-RC4.1U2
*two folders were created with files inside the /sdcard/cache/marketCache after installing a program, but I saw no apk
@gentle_giant: I tried your way but it seems that removes the curent patches and you have to repatch again.
rxwookie said:
That one I think I understand... but, unfortunately the answer is that the Dalvik cache partition (where the market APK's are downloaded to) on many original Samsung devices (i.e. Fascinate) is only about 35 MB in size. Anything larger will get rejected as being too big. Most of the newest devices have a larger download partition.
I've seen a few posts on different forums on remapping the download cache to a different, larger partition... but nothing specific to our devices. I've tried following other posts just to see if it works, but suceeded only in either having no effect or messing it up worse and having to reinstall the ROM (not a big deal, but frustrating).
Until one of the smart people here tells us how to remap **our** cache to a larger partition... I'd do a Google search for the APK of the app you are trying to install. That worked for me to install an app about 40 MB in size.
** edit **
I see that you were able to download the app after deleting everything in the cache folder. I guess your device is lucky enough to have a larger download partition than mine does
Glad to see you got it to work!
** 2nd edit - How to remap your market cache to the SD card **
-- UPDATE -- (Thanks to grickson here at XDA)
Problem: Insufficient Storage Space Available (Android Market)
Possible Solution: Remap cache folder to your SD card
** WARNING **
I am not responsible if you mess up your device doing the following. It manually remaps your market cache to your SD card to give you extra space. The only caveat is that if you remove your SD card (or while the SD card is unmounted) the market will not work. If you are worried about losing market functionality, DON'T try this. If you mistype (or the world suddenly tips over or some other unforeseen consequence), you can ruin your ability to run the Android Market at all. Please remember, you can repeatedly clear your Dalvik cache as often as needed to continue downloading apps. you can also get most larger APK's if you spend a few minutes browsing for them. You have been warned!
** END WARNING **
1.) Download and install a terminal emulator
2.) Open the terminal emulator and type su
3.) Allow the app to always have root access and exit
4.) Restart the terminal emulator and type su, the prompt should change to a #
5.) Type the following commands:
# cd /data/data/com.android.vending
# rm -R cache
# mkdir /sdcard/cache/
# mkdir /sdcard/cache/marketCache
# ln -s /sdcard/cache/marketCache cache
- What these commands do are (in order): change directory to your cache folder, delete the entire cache folder, create a directory on your SD card named cache, create a subdirectory in that one called marketCache, link the phone's market cache to the newly created folder on your SD card
To reverse this process (hopefully):
1.) Open the terminal emulator and type su
2.) Type the following commands:
# cd /sdcard/cache/
# rm -R marketCache
# mkdir /data/data/com.android.vending/cache
# ln -s /data/data/com.android.vending/cache cache
Alternately, (from what I understand) you can just repartition your device and reinstall your ROM of choice using ODIN and your market should be back to the way it was.
Click to expand...
Click to collapse
Nice work, but note that the issue is not market-specific.
If you were to try and sideload that same app, you would get the same message -- it is from the device, not from the market.
I know this to be true since I tried it. I regularly backup all apps with ES File Explorer's App Manager (I also do the same with TB and NAND backup). When I came across the error message, I tried sideloading with no luck.
Since I am able to do updates and a rare occassional new download, I wonder if there is something about the specific apps involved.
It also is not the quantity of apps installed. I've read of someone having six apps installed. I have almost one-thousand (my dalvik resides on my Ext4 SD-EXT partition, so it can grow).
There is probably a solution staring us all in the face, but as for me, I seem blind to it.
I guess problem [RESOLVED]
rxwookie said:
Okay... I searched the forums and didn't see a good answer to this question so I thought I'd post it here along with what worked for me.
I flashed over to GeeWiz recently from a rooted, stock Fascinate (and I love the new ROM). When I was re-installing my apps, I started getting an error message in the market saying I had insufficient storage. I tried manually remapping the cache using a terminal emulator with no joy (I may have screwed it up).
I finally got fed up and wiped my Dalvik Cache and voila, it started downloading again. I got about 60-80 MB of apps downloaded and hit the wall again. After rebooting into recovery and wiping it again, it started working again.
Problem: Insufficient Storage Space Available (Android Market)
Possible Solution:
1.) Reboot into Recovery (if you don't have Clockwork installed, flash it, then reboot into it)
2.) Using the volume keys, scroll down to advanced
3.) Press the return/go back soft key to enter the next menu
4.) Scroll down to Wipe Dalvik Cache, choose it
5.) Scroll down to Yes - Wipe Dalvik Cache, choose it
6.) Wait until it's cleared
7.) Press the Menu key to go back until you see Reboot System Now
8.) Reboot - It will take a few minutes for the cache to get rebuilt so be patient
Hopefully, this will help some. If anyone else has any ideas, please post them!
Wook
Click to expand...
Click to collapse
I recently had the same problem on my device htc explorer. I had rooted my device so i used The APP LUCKY PATCHER and selected Options>Troubleshooting. There i found out an option called Insufficient storage available so when i selected it , it had done something and when it was over i could install the app that was causing the trouble! Hope it would work fr u people! But remember
ur device must be rooted and install LUCKY PATCHER!!
gentle_giant said:
Ola,
I copy-pasted the lines below. It did fix it for me. And I have been spending many, many hours if not days digging through search results..
My thanks go to GTAFan9999 on AndroidCentral for pointing me in the right direction.
After this some apps that refused to update in the past, updated just fine, I could reinstall Facebook and Whatsapp.
BTW, you will have to google Lucky Patcher, you won't find in on Google Play.
"I had this problem a few days back. I fixed mine by running "Lucky Patcher" and then going to the troubleshoot section in the menu and picking "Remove fixes and backups (insufficient storage available"
Click to expand...
Click to collapse
Thanks for that, I'll give that a try if I see it again. It seemed to only be specific ROMs for me at least. I always got it with CM7 and 9, but other ROMs like AOKP and team passion ROMs never gave that error. So it must be something in their coding as well. Maybe CM just hadn't bothered to fix/patch it and AOKP/Passion had, I dunno
gentle_giant said:
Ola,
I copy-pasted the lines below. It did fix it for me. And I have been spending many, many hours if not days digging through search results..
My thanks go to GTAFan9999 on AndroidCentral for pointing me in the right direction.
After this some apps that refused to update in the past, updated just fine, I could reinstall Facebook and Whatsapp.
BTW, you will have to google Lucky Patcher, you won't find in on Google Play.
"I had this problem a few days back. I fixed mine by running "Lucky Patcher" and then going to the troubleshoot section in the menu and picking "Remove fixes and backups (insufficient storage available"
Click to expand...
Click to collapse
+1
If any of you have Titanium Backup installed before, try uninstall it and delete App Manager folder from you sdcard.
It worked for me, no idea about you guys though.
I have xperia neo, and I am probably in "the wrong part of town", however I wanted to share some of my experience. When I was running stock Gingerbread I had no problems at all with this, with CM9.1 I tried the lucky patcher thing and it seemed to have worked. But when using stock ICS after downloading around 10 apps, and the free space going down from 300mb to below 90, the problem is there. Any thought on why GB was ok? I am considering going back to GB.
Seems to be finally fixed
I've been poking about trying to find a solution to my "insufficient space" issue, which as most of you seem to be in agreement is a blatant lie you are being told by your phone.
Anyhow, a reboot to recovery and a cache wipe is certainly now allowing me to update the apps I couldn't previously.
Thanks to the xda community, once again.
Incidentally , I'm running a Galaxy S2 I9100, with CM9 RC1
Same error .. insufficient memory P-3113 samsung tab 2
P-3113 tab 2 android 4.1.1 build UECLK7
32gb external 8gb internal
Used script to swap memory from here...
http://forum.xda-developers.com/showthread.php?t=1961097
All worked fine.
device memory Total 29.69gb apps 2.53gb audio 24k misc files 162mb ? Available 28.63gb
SD Card total 4.56gb Avail 2.86gb
In apps manager Device memory reads 1.6gb used - 3.0gb free
I can not install some apps from the GApp store "Insufficient storage available"
I can install from amazon.
Using cwm, wiped davlik and main cache, checked and mounted /data, fixed permissions. rebooted.
Tried to download and install lucky patcher... no luck installing.
Nothing help so far. just trying to download and install the sixaxis cntroller app ( very small ) yet a larger file from amazon will install fine.
any ideas? Thanks to everyone in advance.
UPDATE can install Kunundrum game app 14mb from GApp store but not sixaxis controller 147k insufficient storage is this some block?
Thanks
wsiegel said:
P-3113 tab 2 android 4.1.1 build UECLK7
32gb external 8gb internal
Used script to swap memory from here...
http://forum.xda-developers.com/showthread.php?t=1961097
All worked fine.
device memory Total 29.69gb apps 2.53gb audio 24k misc files 162mb ? Available 28.63gb
SD Card total 4.56gb Avail 2.86gb
In apps manager Device memory reads 1.6gb used - 3.0gb free
I can not install some apps from the GApp store "Insufficient storage available"
I can install from amazon.
Using cwm, wiped davlik and main cache, checked and mounted /data, fixed permissions. rebooted.
Tried to download and install lucky patcher... no luck installing.
Nothing help so far. just trying to download and install the sixaxis cntroller app ( very small ) yet a larger file from amazon will install fine.
any ideas? Thanks to everyone in advance.
UPDATE can install Kunundrum game app 14mb from GApp store but not sixaxis controller 147k insufficient storage is this some block?
Thanks
Click to expand...
Click to collapse
simply install this app http://bit.ly/HknMhv & choose location external storage

what just happend? apps on sdcard

I have the CM10 [skang jellybro] fascinate rom installed, and coming from a cm9 rom, all my apps didn't fit because they switched the partition around [making the app partition only 468MB, and the system partition 1.5 GB].
So anyway I had to move a lot of apps to the sdcard. So I just downloaded a newer version of my rom, and wiped cache/dalvik, nandroid backup, then I installed the new zip.
Then I rebooted, and it had to 'optimize' apps [create dalvik cache?] and after that finished...I only had about 15-20 apps show up in my app drawer. [I have probably around 40] So I clicked on Zedge, on my homescreen, and it said "App isn't installed." I then started to worry..:S I googled apps on sdcard disappearing.. and so I opened titanium backup, and under Batch operations, it said "Restore missing apps (6)," and they were 6 apps that I'd uninstalled but didn't delete the backup. so then I wasn't sure what to do next, because I did not create a fresh titanium backup prior to updating my rom [because I did a nandroid instead..] so then I went to Manage Apps, and then.. for some reason, all my apps showed up again! all the ones on my sdcard.
I tapped Zedge again on my homescreen, and it loaded up! So my question is, what happened? Why did my apps disappear, and then just show up again? was it loading titanium backup? or did the rom just scan the sdcard for apps?
Sounds like it just messed up the media scan of the sdcard which I have heard happens from time to time... not sure if that's related to your issue, but now are all your apps installed or are you still missing some? Next time I would just reboot again and let it re-scan to see if it helps
Crawshayi said:
Sounds like it just messed up the media scan of the sdcard which I have heard happens from time to time... not sure if that's related to your issue, but now are all your apps installed or are you still missing some? Next time I would just reboot again and let it re-scan to see if it helps
Click to expand...
Click to collapse
ah.. yes they are all there, but I was just wondering why did they disappear, and then why did they just show up all of a sudden?
I guess if it is the media scan thing, that would explain it.
Fast Boot option may be the culprit
mvmacd said:
ah.. yes the [apps] are all there, but I was just wondering why did they disappear, and then why did they just show up all of a sudden?
Click to expand...
Click to collapse
CUT TO THE SOLUTION BELOW -- SEARCH FOR ////
Some (not all) of my apps moved to SD (all by Titanium Backup Pro) have begun to disappear and (sometimes) reappear without warning after I began to add and delete large Virtual Machines created in QEMU from my 16GB SanDisc class 10 microSD card on my HTC Droid Incredible running rooted stock Verizon Android Froyo 2.2.3. I know this thread is far from my phone's "home base", but from what I can tell this problem with disappearing apps located on an sdcard is NOT determined by hardware or even Android version.
I also happen to use LauncherPro by Federico Carnales instead of the built-in HTC Sense launcher. I noted elsewhere on XDA that a user had suggested that because at least some (maybe all) launchers start before the SD Card that this may be a problem, especially if changes are made to the sdcard that the launcher did not perform, or was not active during their performance by other apps such as Titanium Backup. That fits my situation, because I unmounted the SD, physically removed it to a PC, and added/deleted large VM files to save (lots) of time. No problems of this sort before I did this, so there must be some connection.
I noted that other users have tried reformatting SD, substituting different brands of SD, using newer/older SD etc. None of these reliably helped. So I skipped these options.
//// The (simple!) solution I tried that SEEMS to work (only time will tell!) is buried in the main Android Settings (accessed from the Menu button while in Home screen). Under "Applications" there is a setting "Fast Boot" that I checked long ago and forgot about (it seemed like a good thing to do at the time). The text warns "Turn off to use some Market apps" (that shows the age of my 2-yr old used phone and Android OS -- ohmygosh!-- because it refers to Market rather than Google Play Store!) Anyway, I unchecked the option and rebooted the phone.
Yes, it took a bit longer to boot (maybe a whole minute!), but after waiting about another minute ALL my home screen apps had normal icons and loaded properly. Titanium Backup Pro batch scenarios confirmed there were no apps in a forced uninstalled state (i.e. I had not done the deed, the system somehow had done it or at least rendered the apps "invisible" to Titanium, which decided they needed reinstallation).
The only odd behaviour was that auto brightness was turned off after I unchecked Fast Boot and rebooted. Going into Android Settings > Display and rechecking "auto brightness" took care of that. No other oddities or strange behaviours thus far (but it has only been about an hour).
I will report back here on this thread only (Samsung Fascinate > Fascinate Q&A > What just happend? apps on sdcard) if anything else requires reporting. Silence implies success!
link: https://www.google.com/url?q=http:/...ds-cse&usg=AFQjCNE3D5NrpiSqCRSof-ou1mn6iyeGVg
(I am copying this original post (without edits) to other relevant threads, but will not post anything further elsewhere -- only here. This is a bit arbitrary (although this thread appears to be the most recent active one on this topic), but I hope this approach pleases the XDA sysops/admins) :angel:
EDIT 2012-12-26-a:
Nearly all of the 100+ apps on my HTC DINC (Droid Incredible) continue to behave normally after the "fast boot OFF" fix. (No disappearing act.) However, I did find one that appeared to be installed but really was not: ASTRO File Manager. I used Titanium Backup Pro to reinstall app+data from a backup. It only took a couple of minutes, and after that all went normally.
The only other noticeable issue right after the fix is that nearly all of my installed, functioning apps were listed as "missing" by Titanium Backup in its Batch scenario list (although they were NOT counted in the total number of apps listed with the scenario -- that number was 61, and it should have been nearly 170 based on the number of apps actually in the physical list). After about a day or so of regular usage, a re-check of the "missing apps" Batch scenario found all the functioning apps no longer listed; the 61 missing apps were valid -- they were all from earlier ROMs belonging to the original HTC setup and another phone (MOTO OG Droid). Since I have kept the MOTO as an emergency backup smartphone, I might conceivably want to revive some of these apps.
EDIT 12-26-b:
Some other potentially useful points I have gathered in my survey of this topic across XDA:
1. This problem happens most often when using the "Disk drive" option in the USB Debugger system app. It also happens after physically returning the sdcard to the phone after removing and inserting it into a PC.
2. Those who have wiped the app data cache also report serious problems.
3. Wiping the dalvic cache while in Recovery mode automatically triggers a rebuild of that cache, which may make apps behave oddly or disappear until the rebuild is complete, which reportedly "takes time"
Personally, I did only #1 myself, and the fast boot removal fix seems to work well for that one.
I cannot confirm the others, but they seem to make sense to me, and I doubt the fast boot removal fix would have any influence on them.
4. There are some signs that apps installed to internal phone storage can behave in the same way. This may mean that the fast boot OFF tweak may prove beneficial to any storage area, since they all come on-line after the OS loads from phone memory.
EXT4ALL (aka Convert2ext4) = final fix for dalvik cache related bugs (?)
Further investigation of the Dalvik cache reveals a significant connection between it and a number of odd and unpleasant behaviours, including Low Disk Space warnings and disappearing apps.
Fortunately, there are some excellent XDA forum threads about dealing with the Dalvik cache.
The best recent place to start seems to be here:
[Q] Incredible running CM7.2 "Low on space" message (launched 2012-12-14)
http://forum.xda-developers.com/showthread.php?t=2047424
It is not because of the focus on the Droid Incredible or CyanoModGen in this thread, but the attention paid to the more universal fix "EXT4 4 ALL" aka "EXT4ALL" or "Convert2Ext4". (Thanks to Senior Member cmlusco for his post #9 on the thread that got me started in the right direction!)
Files can be found at these locations:
Goo.im site http://goo.im/devs/tiny4579/mods
DINC.does-it site http://dinc.does-it.net/EXT4_Mods/
One version of this fix (Convert2Ext4_no_data_limit_normal_dalvik.v2.0.zip) moves the Dalvik cache from the default, limited 150MB internal partition to the "unlimited" (or at least maximum) 750MB internal partition.
Any phone with a kernal installed that supports ext4 can utilise this fix.
[ I personally use gingertiny 2.6.35.14-v2+ (2012-02-13), which has supported ext4 since late 2011]
My own experience has been to flash the "no data limit normal dalvik" zip file using ClockworkMod 5.x Recovery -- this was entirely painless. I just downloaded the file into my phone's downloads folder on the sdcard using a web browser, then ran CM Recovery (with a little assist from ROM Manager), selected "install a zip from sdcard" and navigated to the file. It was all done in 5 minutes. After manually rebooting a second time, everything seems to be working normally after about half a day of regular use.
For those who flash a new or updated ROM sometime in the future, you would need to flash this fix after doing so.
There is plenty of information contained on the main threads of this topic. Links aplenty can be found; just follow the ones provided in the thread I suggest here to get started.
Hopefully, this brings an end to my struggles with my phone's storage issues, and to others of you reading this post and following the links to the threads and downloads.
FYI -- My storage values changed as follows after running the fix:
Total Internal memory: 748MB --> 770MB (22MB increase)
ROM free space: <1MB --> 20MB (close to the value change of total internal memory)
Used internal memory: ~335MB --> 464MB (close to 128MB increase)
Remaining internal memory: ~420MB --> 306MB (close to 128MB decrease)
So, it seems that my ROM was being used to cache app data, which would explain why the value kept declining even though I NEVER added anything to it (using Titanium Backup Pro or anything like it). When free space on my ROM literally ran out, Android OS hit the proverbial panic button and warned me to free 512kb minimum to allow Gmail to download new mail. Now, it has 20MB free (and will hopefully stay that way, since I NEVER intend to transfer anything into the ROM!) -- The internal memory usage jump of 128MB probably indicates the Dalvik cache.
SUMMARY:
1. Turning off "fast boot" in Android settings helps some, but it does not get to the heart of the issue. It will NOT make a Low Disk Storage warning go away.
2. Once you have a Low Disk Storage warning, you MUST uninstall enough apps to make it go away (keep track of what you take away, because you can reinstall them very soon!)
3. With no LDS warnings showing, flash the "Convert2ext4 no data limit normal dalvik" zip file. THIS APPEARS TO BE THE REAL SOLUTION!
4. Reinstall your recently removed apps, and you should be good to go! :fingers-crossed:
PS>>> One last unresolved issue: I am still unclear exactly WHERE the dalvik-cache ends up, since my Astro file browser cannot locate anything containing the word "cache" that does not now report "EMPTY". There are a large number of "com." folders containing software I have installed found in the /mnt/asec/ folder. The total size of the contents of this folder (362 MB) is within 100MB of the amount of internal memory reported in use. Does that 100MB represent the current size of the Dalvik cache files, or at least include them? If so, where are they located? If anyone can help me figure this bit out, I would be grateful! :fingers-crossed:

[Q] HTC ONE X+ apps unable to access storage after installing custom ROM

Hi everyone,
I need some help with some errors that are occuring after installing the [International] 2013/03/05 AOKP 4.2.2 - 2.0b ROM.
I'm using the international version of the HTC ONE X+.
First off, I have to mention that I am quite noob at these things besides rooting and installing oxygenrom once on the HTC DESIRE, 2 years ago.
Let me explain the problems:
1) when connected to my pc via USB, I can access the phone's storage listed as sdcard, but there is totally nothing inside, and I am unable to copy anything to the sdcard.
2) Also when I try to download anything using the stock browser from this rom, the browser crashes, Google play also crashes immediately when I try to open it. File Manager (safe access mode) throws up the error message "the file or folder was not found" and is empty.
3) Camera and gallery indicates that there is no storage available.
After checking "storage" from settings, it clearly indicates 53.23gb available, 72.11mb (apps), 12.13mb cached data.
I've checked the recovery and discovered that my original data is stored in the directory /0/0/0/0/0, I suspect this is because I didn't realise I had to install the 4.2 kernel separately before I flashed the custom ROM that I tried to install the ROM many times before I realised my mistake and installed it correctly.
I suspect that somehow the ROM is malfunctioning after my mistakes while installing it, causing the many /0 directories and thus while there is available storage space, the apps are unable to read/write data for some reason.
I would install an old ROM version to try to fix this but as I have mentioned above, I cannot transfer any files via USB either.
I'm hoping that one of you can provide some insight into what has gone wrong and perhaps give me some advice on how to re-install your ROM without getting these errors.
If there is any further information I can provide to you please let me know.
Thank you for any help rendered
Same Problem
I've the same problem did you manage to fix it??
If you don't have important data stored on your phone yet, the easiest way is probably format your /data partition in TWRP recovery, wipe/factory reset your phone and the install the rom via "adb sideload" command.
In case you don't know what that is or how to use it, there are two tutorials in the HTC One X+ General forum on unlocking/rooting/flashing on this phone, everything you need to know is written down there.

[Q] android.process.media error after CM 10.1

First, I apologize for the inevitable incorrect use of terminology - I'm trying my best.
After hours and hours of reading up, I finally attempted to internally install CM10.1 to my Nook Tablet 8GB v 1.4.3. I appreciate all the helpful posts on this forum, and primarily used http://forum.xda-developers.com/showthread.php?t=2037368 and http://forum.xda-developers.com/showthread.php?t=2056626 to go through the steps. I hit a few snags along the way, but in the end I think I was successful.
Now I get an error message every time I boot: "Unfortunately, the process android.process.media has stopped." I click okay, then everything seems to work fine. I have tried some suggestions from here, including clearing caches and stopping google's automatic syncs, but nothing has fixed the problem. As far as I can tell, everything works okay otherwise.
Any ideas on how to fix this message? Could it mean that I did not successfully complete the installation process? (Are there ways to tell if the installation was not successful other than not having a brick?)
Android Version 4.2.2
CyanogenMod Version 10.1-20130421-NIGHTLY-acclaim
Happy to provide any more details that would be helpful. And many thanks in advance.
eyeshaveit said:
Now I get an error message every time I boot: "Unfortunately, the process android.process.media has stopped." I click okay, then everything seems to work fine. I have tried some suggestions from here, including clearing caches and stopping google's automatic syncs, but nothing has fixed the problem. As far as I can tell, everything works okay otherwise.
Any ideas on how to fix this message? Could it mean that I did not successfully complete the installation process? (Are there ways to tell if the installation was not successful other than not having a brick?)
Click to expand...
Click to collapse
This happened to me after I dirty-flashed CM 10.1 over another CM 10-based rom. Let me see if I can remember what I did to make it go away... I think it has something to do with a file or process that Android uses to index/keep track of media files on internal and external sd cards, and deleting or wiping the cache or data on that particular process fixes things. I will do some checking around and post back here if I (re)find more specific info.
EDIT: Found it, I think... Do a force stop, clear data, and clear cache on the "Media Storage" app, then reboot and see if it goes away.
Sooo... did it work?
johnseeking said:
Sooo... did it work?
Click to expand...
Click to collapse
Sorry...long week.
Unfortunately, it didn't work. I had also seen suggestions on the forum of similarly stopping and clearing Google Account Manager, Google Services Framework, and a few others (can remember them all), but those didn't do it either.
I have now also had an error message about Themes not responding - can't remember the exact wording. It's happened 2 or 3 times, doesn't seem to have any other consequences other than requiring me to acknowledge the error.
Could I have strayed somewhere along the installation pathway and inadvertently made this a dirty install?
eyeshaveit said:
Sorry...long week.
Unfortunately, it didn't work. I had also seen suggestions on the forum of similarly stopping and clearing Google Account Manager, Google Services Framework, and a few others (can remember them all), but those didn't do it either.
I have now also had an error message about Themes not responding - can't remember the exact wording. It's happened 2 or 3 times, doesn't seem to have any other consequences other than requiring me to acknowledge the error.
Could I have strayed somewhere along the installation pathway and inadvertently made this a dirty install?
Click to expand...
Click to collapse
You need to load into recovery and do a factory reset/wipe data, clear cache, clear dalvik cache. If you dirty installed (installed over another ROM that's not in the same version) you'll have problems with the ROM. If you're using an older cm7 or cm9 I'll suggest you update to cm10+ succulent.
datallboy said:
You need to load into recovery and do a factory reset/wipe data, clear cache, clear dalvik cache. If you dirty installed (installed over another ROM that's not in the same version) you'll have problems with the ROM. If you're using an older cm7 or cm9 I'll suggest you update to cm10+ succulent.
Click to expand...
Click to collapse
I tried to go back to the beginning to see what I did wrong - hoping to fix the problem but also trying to learn. I'll explain in a bit of detail...
Tried to follow the process outline here: http://forum.xda-developers.com/showthread.php?t=2037368. I was able to access root using NT16or8gbV47SDimagefile.img, but was unable to get any further as it kept saying "No files found" when trying to flash rom and gapps zipped files. After trying multiple reformats, partitions, etc, I abandoned following this process. (Of note, I did make sure that debugging and allowing installation from unknown sources were active - to no avail.)
I then followed this process: http://forum.xda-developers.com/showthread.php?t=2056626. In addition to Step 6 - "Wipe data and factory reset," I also cleared cache and dalvik cache as suggested. Everything else went very smoothly. I've now been running CM 10.1 for a few hours without any error messages. I'll report back anything that pops up over the next few days.
I tried to improvise a bit and flash CWM recovery internally as described here: http://forum.xda-developers.com/showthread.php?t=1640958. I was never succesful using flash_CM9-10_CWM_6.0.2.5_8-16gb_emmc.zip, though I'm not sure it's really necessary. (In trying to do this, I modified step 2.b from Digixmax's guide - rather than using the recovery image from CM9-10_CWM_v6.0.1.2_8-16gb_tools_sdcard.zip, I tried using the flashable emmc.zip noted prior. In the end, I just followed Digimax's steps without modifications.) What do you think? Is there any reason to continue trying to flash CWM internally?
Thanks a million to all.
eyeshaveit said:
...
I tried to improvise a bit and flash CWM recovery internally as described here: http://forum.xda-developers.com/showthread.php?t=1640958. I was never succesful using flash_CM9-10_CWM_6.0.2.5_8-16gb_emmc.zip, though I'm not sure it's really necessary. (In trying to do this, I modified step 2.b from Digixmax's guide - rather than using the recovery image from CM9-10_CWM_v6.0.1.2_8-16gb_tools_sdcard.zip, I tried using the flashable emmc.zip noted prior. In the end, I just followed Digimax's steps without modifications.) What do you think? Is there any reason to continue trying to flash CWM internally?
...
Click to expand...
Click to collapse
As long as you have SDcard-based CWM available for recovery purpose (see http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31) you don't really need to flash CWM internally. But if you'd like to flash it internally you can grab a flashable CWM zip file from Succulent's repo http://goo.im/devs/succulent/acclaim/recovery and install it using SD-cased CWM (just like you had installed the ROM/gapps zip files except there is no need for wiping cache/data & doing factory reset in this case).

[Q] Android is upgrading 1 of 1 error

Actually my Ace II GT-I8160 experience multiple problems. Like it can't mount sdcard0 due to the bug of the ROM I updated. This android is upgrading bug, and the "some symlinks failed, error status 7" when installing my ROM.
"Android is upgrading. Optimizing app 1 of 1"
Kinda strange though because its only 1 that restores the exact apps and actions for example I uninstalled apps and then it comes back every time it reboots and it upgrades.
Please help me fix this.
I had done many things like:
1. Installing the original firmware using Odin. (Still does the same problem)
2. Re-installing my ROM (It had an error "some symlinks failed, error Status 7)
3. Factory Reset, Wipe Dalvik Cache, Wipe Cache Partition in ClockWorkMod. (Still does problem repeatedly)
4. There are no .ODEX files in data/app that make it solved as easy as pie.
I think there is something I need to delete in folders (I am in Root Access Mode so I can access all files EXCEPT sdcard0 files).
If you have anything you could do to help me fix this (these actually but I prioritize the every reboot upgrading of app only 1 of 1) problem(s?).
Thank you in advance .

Categories

Resources