Related
THIS UTILITY IS FOR FASCINATE TOUCHWIZ FROYO/GINGERBREAD ONLY
UPDATED FOR EC09 GINGERBREAD
I have created a format utility that can be used from within CWM3 recovery. Just select the ZIP in CWM3 recovery, and the package will do ALL of the work for you.
These utilities come in two independent packages which will completely format your device with EXT4. As a bonus, it will create all directories and setup all ownership and permissions in accordance to the Fascinate.
Voodoo recovery does not currently allow you an option to select a format style, and furthermore does not truly format any partition unless it runs through the Voodoo "lagfix" transition upon booting the device.
There is one caveat in order to use EXT4: you need a kernel that supports it, and this would be using a "Voodoo" style kernel that has built in support. Luckily, most of the "good" kernels available have this ready to go.
Understand that this package will completely wipe your system, data, datadata (dbdata), and cache. This is a "full" wipe of the device. If you already have a ROM installed on your device and want to keep your device the way it is, and also want EXT4, then use the Voodoo method to switch to EXT4. The reason for this is because it backs up your data before it formats.
After you use this package, you can install any ROM of your choosing, as the package will already self-manage Voodoo's methods for "enabling" or "disabling" the "lagfix".
--------
Please report if the package is not working.
A good indicator of this is if you try to install the package and it only takes 1 second to work, then says it is finished. This means it is probably not working, however, if you are formatting the same type of file system over itself with no pre-existing data on the device, it will take the aforementioned 1 second to work.
To see if it worked: mount each partition in CWM3 recovery, then adb shell into your device and type the mount command, in the listing you should see what file system your partitions are using. If the big four all say EXT4, then the package install has been successful.
In order to assure that it will work correctly, use the latest version of a CWM3 recovery that you can find. I can personally vouch for nemesis2all's OTB CWM3 Recovery v3.0.2.8x.OTBv2. Unfortunately not all CWM3 recoveries are the same, and yours may not work with these utilities. If you find a recovery that works fine, post it here and I will update this.
--------
Packages updated: 6/28/2011 - 12:57PM EST
EXT4 Format ALL (formats everything): http://www.mediafire.com/?6hx7f8g7c8vv6xz
EXT4 Format CACHE: http://www.mediafire.com/?2621a888ydv41mg
EXT4 Format DATA: http://www.mediafire.com/?ck2bb340yybpe4z
EXT4 Format DBDATA: http://www.mediafire.com/?ahxzs8xsyyvemed
EXT4 Format FOTA: http://www.mediafire.com/?42ijpi67grdb6mm
EXT4 Format PREINSTALL: http://www.mediafire.com/?d42as1l3pdbhr2t
EXT4 Format SYSTEM: http://www.mediafire.com/?rgs46hhq8qd951t
--------------------
If you like my work, consider donating, or thanking me by clicking the thanks button
thanks for this
navenedrob said:
I have created two format utilities that can be used from within CWM3 recovery. Just select the type of file system you want to use, select it in CWM3 recovery, and the package will do ALL of the work for you.
These utilities come in two independent packages which will completely format your device with either RFS or EXT4. As a bonus, it will create all directories and setup all ownership and permissions in accordance to the Fascinate.
Voodoo recovery does not currently allow you an option to select a format style, and furthermore does not truly format any partition unless it runs through the Voodoo "lagfix" transition upon booting the device.
There is one caveat in order to use EXT4: you need a kernel that supports it, and this would be using a "Voodoo" style kernel that has built in support. Luckily, most of the "good" kernels available have this ready to go.
Understand that this package will completely wipe your system, data, datadata (dbdata), and cache. This is a "full" wipe of the device. If you already have a ROM installed on your device and want to keep your device the way it is, and also want EXT4, then use the Voodoo method to switch to EXT4. The reason for this is because it backs up your data before it formats.
After you use this package, you can install any ROM of your choosing, as the package will already self-manage Voodoo's methods for "enabling" or "disabling" the "lagfix".
Please report if the package is not working.
A good indicator of this is if you try to install the package and it only takes 1 second to work, then says it is finished. This means it is probably not working, however, if you are formatting the same type of file system over itself with no pre-existing data on the device, it will take the aforementioned 1 second to work.
To see if it worked: mount each partition in CWM3 recovery, then adb shell into your device and type the mount command, in the listing you should see what file system your partitions are using. If the big four all say EXT4 or RFS (depending on script used), then the package install has been successful.
In order to assure that it will work correctly, use the latest version of a CWM3 recovery that you can find. I can personally vouch for nemesis2all's OTB CWM3 Recovery v3.0.2.8x.OTBv2. Unfortunately not all CWM3 recoveries are the same, and yours may not work with these utilities. If you find a recovery that works fine, post it here and I will update this.
Click to expand...
Click to collapse
Ok, I think I'm having a complete idiot moment here so please be patient with me. What would be the benefits of me running this on my device that is currently running jt's CM7 with OTB 1.5 kernel and EXT4 (voodoo for those who don't know) already converted? Thanks in advance.
It would be of no use. Unless you need to format your entire device.
So this would be a good thing to flash in place of wiping between rom flashes? Does it have any benefits compared to a regular data and cache wipe when you are already converted to ext4?
It would be a good idea to flash it in that scenario, yes. Currently no ROM will do the job that this package will for you, which is why a lot of ROM's say not to wipe your device, because you'll run into major issues if you do. When you do your "wipes" through recovery it doesn't really do anything besides a recursive delete of files, so it doesn't really format anything (even though it says "format" in the menu system). The only time it actually does any formatting is during the Voodoo transition. When you do wipe those areas, it does not leave the file structure intact and also does not leave the ownership and permissions intact. These packages completely solve that problem. Also, these packages are focused on performance so everything is done that is possible to make sure that your file system is as fast as possible.
navenedrob said:
It would be a good idea to flash it in that scenario, yes. Currently no ROM will do the job that this package will for you, which is why a lot of ROM's say not to wipe your device, because you'll run into major issues if you do. When you do your "wipes" through recovery it doesn't really do anything besides a recursive delete of files, so it doesn't really format anything (even though it says "format" in the menu system). The only time it actually does any formatting is during the Voodoo transition. When you do wipe those areas, it does not leave the file structure intact and also does not leave the ownership and permissions intact. These packages completely solve that problem. Also, these packages are focused on performance so everything is done that is possible to make sure that your file system is as fast as possible.
Click to expand...
Click to collapse
Ok, so basically what you are saying is this would be ideal to use instead of data/cache/dalvik wipe for rfs to rfs and ext4 to ext4, correct? Thanks in advance.
That's correct.
I've teamed up with nemesis2all and we are thinking about adding all of these abilities to the OTB kernel, so you'll be able to choose different kinds of file systems and format options through CWM3 recovery instead of having to use these packages here. That will come when it comes, but for now this is the ideal solution.
EXT2/EXT3/EXT4/XFS/RFS etc...
Also, I've updated the attachments in the post.
navenedrob said:
That's correct.
I've teamed up with nemesis2all and we are thinking about adding all of these abilities to the OTB kernel, so you'll be able to choose different kinds of file systems and format options through CWM3 recovery instead of having to use these packages here. That will come when it comes, but for now this is the ideal solution.
EXT2/EXT3/EXT4/XFS/RFS etc...
Also, I've updated the attachments in the post.
Click to expand...
Click to collapse
Just to let you know, I ran the ext4 package and I got some serious lag issues after I installed my rom and it actually starting going into a soft boot loop. It began to act very weird and unstable. I booted back into recovery and I wiped everything the way I usually do and formatted the system/data/dbdata/cache manually in mounts and storage and reinstalled. It's better than it was but it still seems like it is kinda slower and more laggier than it was before I ran the package. Any ideas? Thanks man.
You'll need to give me more information than that to determine your problem.
What kernel are you using? What recovery are you using? What ROM are you running? What are the results of running the mount command with all partitions mounted?
navenedrob said:
You'll need to give me more information than that to determine your problem.
What kernel are you using? What recovery are you using? What ROM are you running? What are the results of running the mount command with all partitions mounted?
Click to expand...
Click to collapse
OTB 1.5, CM7. It's kinda weird. When I ran your package and then flashed cm7 and booted it, it was laggier than I have ever seen my phone and when I would try to do certain operations it would soft boot. At one point I couldn't even turn wifi on. So, I booted back into recovery and wiped and manually formatted everything and reinstalled everything. After that it was still kind of laggy but much better. I restored all of my apps and got my phone back to all my custom settings. Then I began to notice that it wasn't really lagging anymore, in fact it seemed pretty snappy. I ran quadrant to see if the numbers were the same as before to determine if I was in fact ext4 converted. Surprisingly the numbers were higher than normal. And I even noticed in titanium backup that some of my internal memory had been freed up. I can't explain it but everything seems to be running really good right now. It's almost like after running your package the phone had to be conditioned, and once it was conditioned it ran real good. But, that doesn't explain why it was soft booting and wifi wouldn't work. Who knows.
Not really sure exactly, it actually could have been a few different things causing the "issues". I'm going to try your exact scenario and see what happens.
kidserious said:
OTB 1.5, CM7. It's kinda weird. When I ran your package and then flashed cm7 and booted it, it was laggier than I have ever seen my phone and when I would try to do certain operations it would soft boot. At one point I couldn't even turn wifi on. So, I booted back into recovery and wiped and manually formatted everything and reinstalled everything. After that it was still kind of laggy but much better. I restored all of my apps and got my phone back to all my custom settings. Then I began to notice that it wasn't really lagging anymore, in fact it seemed pretty snappy. I ran quadrant to see if the numbers were the same as before to determine if I was in fact ext4 converted. Surprisingly the numbers were higher than normal. And I even noticed in titanium backup that some of my internal memory had been freed up. I can't explain it but everything seems to be running really good right now. It's almost like after running your package the phone had to be conditioned, and once it was conditioned it ran real good. But, that doesn't explain why it was soft booting and wifi wouldn't work. Who knows.
Click to expand...
Click to collapse
It's possible that since you wiped your market was trying to restore all your apps in the back ground which was taking all your memory up and making your phone lag. But after you restored all your apps it was all set
Coreyc1123 said:
It's possible that since you wiped your market was trying to restore all your apps in the back ground which was taking all your memory up and making your phone lag. But after you restored all your apps it was all set
Click to expand...
Click to collapse
What I meant was as soon as it booted (during setup wizard) it was super laggy. I download TB from the market by itself and it took forever to register. I was doing the GPS fix and it soft booted. I couldn't turn wifi on and it soft booted. All before I did a batch restore in TB. And I know that the market begins to sync automatically as it always does but this was much much different.
Sent from my SCH-I500 using Tapatalk
kidserious said:
What I meant was as soon as it booted (during setup wizard) it was super laggy. I download TB from the market by itself and it took forever to register. I was doing the GPS fix and it soft booted. I couldn't turn wifi on and it soft booted. All before I did a batch restore in TB. And I know that the market begins to sync automatically as it always does but this was much much different.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
I had these same symptoms one time that I installed kasonate v7, but after reflashing, the next time it didnt.
I know you're not talking about the same cm version, but they might be related and not related to the format utility.
Ok, I ran this package again to make sure that I didn't do something wrong and to see if I would get the same results. I ran the package, flashed cm7 then gapps then OTB GB 1.5. all from the recommended recovery in your post. Again I ended up in a soft boot loop and wifi was acting up again and was causing a boot loop. So once again I booted into recovery and wiped data/cache/dalvik normally and formatted manually via mounts and storage and reinstalled again and she's running like a dream. Very weird but I must say I am very happy with the results I ended up with, regardless of how I got them. So obviously, this was not your intention for it to be done this way but I do see an improvement in responsiveness, speed and memory being freed up. Before, my free internal memory was 1.49 and now it is 1.52. Thank you sir, I appreciate this.
Thanks for this utility! Works great. Went from Jt's cm7 to the miui/touchwiz rom and ran the utility in between. My phone is running faster than ever and no issues. Thanks again!
Sent from my SCH-I500 using XDA App
Yeah running this on mesmerize with heinz 57 best my phone has ever run quadrant of 2250s @ 1.5 ghz
Sent from my SCH-I500 using XDA App
stephenj37826 said:
Yeah running this on mesmerize with heinz 57 best my phone has ever run quadrant of 2250s @ 1.5 ghz
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
You're welcome, the utility enables a few nice options as far as file system performance is concerned, that Voodoo doesn't at this time.
Do tell oh and thanks a million
Sent from my SCH-I500 using XDA App
"Error downloading app from market. There is insufficient space on the device."
That's the error that I get when I try to download big apps, like Third Blade, etc. I notice that this happens with apps that are bigger that 30mb.
I just want someone to confirm that the game can be downloaded in a Samsung Vibrant.
I really have a lot of space in my device so this is not the problem.
I'm on trigger right now.
Sent from my SGH-T959 using XDA App
i have that same problem!! but only with that game and i have alot of room too
i wanna play third blade toooo
im on cm7
I had that problem on BOTH of those ROMS.
Mostly CM7.
Everyone suggested to just ODIN, it didn't work for me, so i just changed rom and it was good again?
Before doing anything, i think you should backup everything on your SD CARD, then try and format sd, and then try download.
i may be wrong.
/cache is full. Go in with root explorer or similar, and clear out some stuff. You might even need to go into /cache/dalvik and delete a few installed apps (don't fret, they should rebuild after a reboot) for it to initially fit. That's where Android places the zip before installing a new app, or an update. I go in there all the time and clear any updates or apps I just installed, and I rarely have issues with not being able to d/l larger apps. I'm on latest Trigger CM.
Sent from my rough sketch of a Vibrant on a brick.
Disable voodoo, it works for me every time
i just made something like
mkdir /mnt/sdcard/external_sd/cache
mount -t bind /mnt/sdcard/external_sd/cache /cache
and i have no problems regarding /cache space now
theli_ua said:
i just made something like
mkdir /mnt/sdcard/external_sd/cache
mount -t bind /mnt/sdcard/external_sd/cache /cache
and i have no problems regarding /cache space now
Click to expand...
Click to collapse
What exactly would that command do if I put it into an Android command prompt emulator
theli_ua said:
i just made something like
mkdir /mnt/sdcard/external_sd/cache
mount -t bind /mnt/sdcard/external_sd/cache /cache
and i have no problems regarding /cache space now
Click to expand...
Click to collapse
This would need some modification to work for CM based ROMs, but looks like its creating a cache folder on and forcing system cache to the external sd? I wonder if this would work for CM? Anyone?
Sent from my rough sketch of a Vibrant on a brick.
This happened to me awhile back, it really sucked.
After trying everything, eventually it cleared up when I cleared dvk cache (or whatever its called) in advanced settings of clockwork
Droidificator said:
/cache is full. Go in with root explorer or similar, and clear out some stuff. You might even need to go into /cache/dalvik and delete a few installed apps (don't fret, they should rebuild after a reboot) for it to initially fit. That's where Android places the zip before installing a new app, or an update. I go in there all the time and clear any updates or apps I just installed, and I rarely have issues with not being able to d/l larger apps. I'm on latest Trigger CM.
Sent from my rough sketch of a Vibrant on a brick.
Click to expand...
Click to collapse
I currently don't have anything inside the /cache and I still get the problem.
kxlling said:
Disable voodoo, it works for me every time
Click to expand...
Click to collapse
Interesting, I'm gonna try that.
theli_ua said:
i just made something like
mkdir /mnt/sdcard/external_sd/cache
mount -t bind /mnt/sdcard/external_sd/cache /cache
and i have no problems regarding /cache space now
Click to expand...
Click to collapse
Seems a little big risky but I can try it later.
The thing is guys, have you downloaded Third Blade? I need some proof.
Thanks.
u cant download third blade on cm7!! ive tried it on 3 cm7 phones to my knowledge
This worked for me.
HTH,
LV.
LordVetinari said:
This worked for me.
HTH,
LV.
Click to expand...
Click to collapse
I have tried everything in this thread and all of the others I found by searching the forums.
Allow a noob to ask a question, please... What do you do with this zip?
found in /cache via root explorer a leftover 16mb apk.. deleted & market installs working again.. THANKS!
I get an Insufficient Space error every time I try to install some larger apps (latest examples: Paradise Island and Duke Nukem 3D).
I have tried every suggested fix I can find online. I have cleared the market cache, uninstalled market updates, cleared dalvik cache, cleared regular cache, checked partition usage of /data, nothing has changed this behavior.
As a final step I ODIN'd back to stock and reinstalled Bionix Nextgen V2. Made sure to do the 20 minute wait n' reboot. Tried installing the same apps via the Market once the ROM was installed and the old market doesn't even give me the error, it shows the download arrow in the notification bar for a couple seconds and then it just disappears.
I'm at my wits end on this one. Seems my choice is to either run CM7 and have non-functioning GPS or Bionix and have a semi-functioning market.
Does anyone have any suggestions?
I wiped my cache partition and dalvik from recovery. Rebooted and I could now install Wind-Up Knight. It's all I had to do. CM7.
Update: For whatever reason my /cache on Bionix Nextgen V2 is set to 24.7 Mb after a fresh installation. No wonder it wouldn't install 27+ Mb apps.
I finally fixed this issue myself with a symlink:
Ran inside Terminal Emulator (you will need to run the commmand su after opening terminal emulator to get root rights):
umount /cache
rmdir /cache
mkdir /mnt/sdcard/external_sd/cache
ln -s /mnt/sdcard/external_sd/cache cache
As soon as I exited Terminal Emulator I was able to install large apps.
Update again: And now it's broken again. Cache is remounted to the old settings and the umount command now just gives me a "Failed" without any other useful error information.
HELP!!! How do I permanently fix this?
Update again v2: Rebooted into recovery, wiped cache and Dalvik, got an error indicating my sd card isn't partitioned correctly "E:Can't mount /dev/block/mmcblk1p2" when wiping Dalvik, but from what I'm finding online that's not a huge deal. Rebooted, ran my commands above again and cache is symlinked again, large apps install ok again.
How do I make this permanent?
Same problem, disabling Voodoo worked for me
solution worked for me like charm....
After browsing around, I found out solution:
The problem is in the cache folder (that I assume used by the market) is using small partition (around 20mb in my case).
So to solve this we need to change it to bigger partition.
1. You gonna need Android Terminal Simulator or equivalent terminal app. This will also require your Android rooted.
2. Type ’su’ (root permission request will be showned, you need to approve it).
3. Type ‘cd /’
4. Type ‘umount /cache’
5. Type ‘mount -o rw,remount -t rootfs rootfs /’ (to set the folder access to rw – read write)
6. Type ‘rmdir /cache’ (delete cache folder)
7. I personally using root explorer to do point 5-6
8. Type ‘mkdir /sdcard/cache’
9. Type ‘ln -s /sdcard/cache /cache’ (to link cache folder to /sdcard/cache – which shoud have bigger partition size)
Works like a charm!!!
Thanks to jimmy!
jimmod.com/blog/2011/10/android-market-error-on-downloading-error-downloading-there-is-insufficient-space-on-the-device/
jimmod dot com
I have heard people say that you can use Titanium Backup to uninstall stock apps. I don't have the pro version, do I just go to the Backup/Restore menu and click the app and uninstall? Is that it? Also, some of the apps don't seem to show up in Titanium backup. Specifically, I wanted to uninstall Messenger, but I can't find it in the list. Another thing is I want to uninstall the Google Search so that the search capacitive button won't have that app pop up or any of the search app for that matter. Is it safe to uninstall Google Search?
With stock apps its always wise to keep a backup in case you accidentally delete something that the phone requires. I don't know if the free version of Titanium can delete system apps, but the paid version can freeze them which means the apk is still there, its just not allowed to run. You can also go to /system/app with a root enabled file explorer (ES file explorer, root explorer, etc), find the apk file and rename it to .bak.
spunker88 said:
With stock apps its always wise to keep a backup in case you accidentally delete something that the phone requires. I don't know if the free version of Titanium can delete system apps, but the paid version can freeze them which means the apk is still there, its just not allowed to run. You can also go to /system/app with a root enabled file explorer (ES file explorer, root explorer, etc), find the apk file and rename it to .bak.
Click to expand...
Click to collapse
+1. Or just delete the app.
Be careful. You will MESS up if you delete any essential system app.
LIFE! Enjoy it while you Still have it!
Since ICS you can just disable the system (stock) apps that you don't want, in Settings->Apps. It's much safer to do that than to remove/uninstall. You won't gain anything from the extra freed /system partition space anyway.
Sent from my Desire HD using xda premium
Try "Root App Delete".
I used it on my Asus Slider.
Use Titanium Backup to do so !
'elkos' said:
Use Titanium Backup to do so !
Click to expand...
Click to collapse
Buuuuuut the OP says it doesn't work with TB. so we were giving him choices
LIFE! Enjoy it while you Still have it!
Lifehacker7 said:
Buuuuuut the OP says it doesn't work with TB. so we were giving him choices
LIFE! Enjoy it while you Still have it!
Click to expand...
Click to collapse
Sorry my bad !!
At least titanium helps in letting us know which are system application
spunker88 said:
With stock apps its always wise to keep a backup in case you accidentally delete something that the phone requires. I don't know if the free version of Titanium can delete system apps, but the paid version can freeze them which means the apk is still there, its just not allowed to run. You can also go to /system/app with a root enabled file explorer (ES file explorer, root explorer, etc), find the apk file and rename it to .bak.
Click to expand...
Click to collapse
So renaming to .bak will freeze the app and prevent it from running? Is bak a special system file or can it be anything? When my Google search app is frozen, does that also mean my search button will no longer work?
spunker88 said:
With stock apps its always wise to keep a backup in case you accidentally delete something that the phone requires. I don't know if the free version of Titanium can delete system apps, but the paid version can freeze them which means the apk is still there, its just not allowed to run. You can also go to /system/app with a root enabled file explorer (ES file explorer, root explorer, etc), find the apk file and rename it to .bak.
Click to expand...
Click to collapse
But the thing was how to delete system app.I know this is an old thread but want things to get more clearer for newbies including me in the future. What will changing the apk file to .bak will do? And i heard other things as well that you have to mount r/w etc.
Incomplete knowlegde is dangerous.
---------- Post added at 01:50 AM ---------- Previous post was at 01:46 AM ----------
sashank said:
Since ICS you can just disable the system (stock) apps that you don't want, in Settings->Apps. It's much safer to do that than to remove/uninstall. You won't gain anything from the extra freed /system partition space anyway.
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
Why we will not gain anything from the freed extra space? Some phones do not have much internal space so they can have apps of their choice
kitu34 said:
But the thing was how to delete system app.I know this is an old thread but want things to get more clearer for newbies including me in the future. What will changing the apk file to .bak will do? And i heard other things as well that you have to mount r/w etc.
Incomplete knowlegde is dangerous.
---------- Post added at 01:50 AM ---------- Previous post was at 01:46 AM ----------
Why we will not gain anything from the freed extra space? Some phones do not have much internal space so they can have apps of their choice
Click to expand...
Click to collapse
Because you don't gain anything from extra /system space. Apps that you install through Play Store/sideload are installed to /data, which is what 'internal memory' is. When a phone is said to have low internal memory, it means that the /data partition is small.
If you delete an apk from /system, you'll get some free space in that partition which is practically useless. Yes, if you really want to then you can replace an apk from /system with one of your choice, and that will save space in your internal memory (/data), but whenever you update that app from Play Store/sideload, it will put the updated apk in /data. So now you essentially have two apks of the same app on our device. You'd rather have just installed the app normally without fiddling with the /system partition and saved some time. Yes, if you're *really* inclined, then you can manually replace the apk of every /system app with the updated one, either with a root browser or Titanium Backup's 'convert to /system app' function. This seems like a very pointless thing to do for every update of each app.
sashank said:
Because you don't gain anything from extra /system space. Apps that you install through Play Store/sideload are installed to /data, which is what 'internal memory' is. When a phone is said to have low internal memory, it means that the /data partition is small.
If you delete an apk from /system, you'll get some free space in that partition which is practically useless. Yes, if you really want to then you can replace an apk from /system with one of your choice, and that will save space in your internal memory (/data), but whenever you update that app from Play Store/sideload, it will put the updated apk in /data. So now you essentially have two apks of the same app on our device. You'd rather have just installed the app normally without fiddling with the /system partition and saved some time. Yes, if you're *really* inclined, then you can manually replace the apk of every /system app with the updated one, either with a root browser or Titanium Backup's 'convert to /system app' function. This seems like a very pointless thing to do for every update of each app.
Click to expand...
Click to collapse
Thanks a lot,i really appreciate.Just as i wrote the earlier post i realized by deleting a system app that i am not gaining any space.You were right,i should have known that you are more experienced and i am a newbie so instead of assertively saying that i should have asked as to why we will not gain any space.
System storage is where system apps are not in internal storage, i came to know this as i have quick info pro app which showed this.But my question is i have 19mb free system storage now after deleting apps,is that enough? Actually first i had to delete coz home button was not working but now though the ram is less.Though the phone is not that smooth but if i increase more free space in system storage will that benefit?Coz in that case i will have more ram then,and maybe system would work smoothly if it has enough free system storage.
I am using CM10 4.2.2.
kitu34 said:
Thanks a lot,i really appreciate.Just as i wrote the earlier post i realized by deleting a system app that i am not gaining any space.You were right,i should have known that you are more experienced and i am a newbie so instead of assertively saying that i should have asked as to why we will not gain any space.
System storage is where system apps are not in internal storage, i came to know this as i have quick info pro app which showed this.But my question is i have 19mb free system storage now after deleting apps,is that enough? Actually first i had to delete coz home button was not working but now though the ram is less.Though the phone is not that smooth but if i increase more free space in system storage will that benefit?Coz in that case i will have more ram then,and maybe system would work smoothly if it has enough free system storage.
I am using CM10 4.2.2.
Click to expand...
Click to collapse
No problem, we all are newbies at the beginning and learn along the way.
The reason manufacturers and ROMs put all their apps in /system, is because certain apps that are essential to the Android system require higher privileges which are only granted to /system apps. Now apart from those essential apps, there are also a lot of non-essential ones like file managers, Flashlight, Facebook & Twitter apps and a game or two (like HTC Teeter). These are put in the /system partition so that they will survive a factory reset. When a normal user does factory reset, only /data and /cache are wiped. /system stays intact so that after the factory reset, all user installed apps and user data is deleted and the phone is back to factory condition. Suppose the manufacturers had put all the non-essential apps in /data, they would have been wiped too and then some confused users would say that the apps which came with their phone are not there anymore. Suppose you manually delete some apps from /system using a root browser or adb, they won't be there anymore when you factory reset. I've seen many users who've messed around in /system, deleted some really important app/file and gunked up their phone, then factory reset in hopes of restoring everything to the original state with no luck. Only way to get everything back then is to flash a stock ROM or manually push the required app/file again through adb in recovery and set correct permissions, or create a flashable zip of the file and flash it. I'm talking about rooted stock ROMs. If you're running a custom ROM, you can just re-flash the ROM and get everything back.
There is no actual benefit of having free /system space because you can't install things there. You can have a full /system partition and it won't make a difference unless the size of your ROM update suddenly increases a lot and there's no space to flash it, but that won't happen because ROMs are almost always well below the /system partition size. RAM is different. It's just like the RAM chip in a computer. You can regard /system, /data, /cache as different partitions of a hard disk, which in the phone's case is flash memory. Those partitions are in no way related to RAM. Your phone has a fixed amount of RAM which is mentioned in the spec sheet, and unlike computers this RAM is soldered to the motherboard so you can't swap it out for higher RAM. So that's why phones with less RAM will always be slow during heavy use no matter what you try, can't help that (except by creating a swap partition in the SD card if your ROM's kernel supports it). Freeing /system space won't increase your RAM and won't make your phone run faster. These days devices are shipping with a minimum of 1 GB RAM which is enough to run current Android versions decently. Even my HTC Desire HD with 768 MB RAM does a decent job thought it slows down every now and then.
sashank said:
No problem, we all are newbies at the beginning and learn along the way.
The reason manufacturers and ROMs put all their apps in /system, is because certain apps that are essential to the Android system require higher privileges which are only granted to /system apps. Now apart from those essential apps, there are also a lot of non-essential ones like file managers, Flashlight, Facebook & Twitter apps and a game or two (like HTC Teeter). These are put in the /system partition so that they will survive a factory reset. When a normal user does factory reset, only /data and /cache are wiped. /system stays intact so that after the factory reset, all user installed apps and user data is deleted and the phone is back to factory condition. Suppose the manufacturers had put all the non-essential apps in /data, they would have been wiped too and then some confused users would say that the apps which came with their phone are not there anymore. Suppose you manually delete some apps from /system using a root browser or adb, they won't be there anymore when you factory reset. I've seen many users who've messed around in /system, deleted some really important app/file and gunked up their phone, then factory reset in hopes of restoring everything to the original state with no luck. Only way to get everything back then is to flash a stock ROM or manually push the required app/file again through adb in recovery and set correct permissions, or create a flashable zip of the file and flash it. I'm talking about rooted stock ROMs. If you're running a custom ROM, you can just re-flash the ROM and get everything back.
There is no actual benefit of having free /system space because you can't install things there. You can have a full /system partition and it won't make a difference unless the size of your ROM update suddenly increases a lot and there's no space to flash it, but that won't happen because ROMs are almost always well below the /system partition size. RAM is different. It's just like the RAM chip in a computer. You can regard /system, /data, /cache as different partitions of a hard disk, which in the phone's case is flash memory. Those partitions are in no way related to RAM. Your phone has a fixed amount of RAM which is mentioned in the spec sheet, and unlike computers this RAM is soldered to the motherboard so you can't swap it out for higher RAM. So that's why phones with less RAM will always be slow during heavy use no matter what you try, can't help that (except by creating a swap partition in the SD card if your ROM's kernel supports it). Freeing /system space won't increase your RAM and won't make your phone run faster. These days devices are shipping with a minimum of 1 GB RAM which is enough to run current Android versions decently. Even my HTC Desire HD with 768 MB RAM does a decent job thought it slows down every now and then.
Click to expand...
Click to collapse
Thanks a lot,it was really great and helpful.! It was a very clear explanation,esp for a newbie.Very few people write so much for others,i am impressed.Even i fill pages for others and never assume they know anything or much.
But coz of ;less system storage only my rom was not working properly,or my phone was not working properly.I had just 48kb free.
Ok like i have a system app which is running all the time and consuming ram,won't i gain ram if i delete that?Apps or phone shows an app and memory,that is resident and shared memory or Ram an app is using?
Last thing,you talked about swapping partition for ram in sd card.I do not know how to do that,so yesterdday only sought an app for this but it did not work.Maybe my free space was also less,though apps preset was starting from 200mb,i bought new sd card today but just read at another swapper's review that some people bricked their phone.I too got scared,hehehe, and stopped for a while.One day when you are free do share a link or something from where i can follow the steps to do this considering i am a newbie and do not understand technical terms that much.I have never used ADB or commands also,never needed that,just recovery.And i rooted with superoneclick without doing anything,it was that simple and flashed reading a help article though phone went into fastboot but luckily one guy helped me for one hour but i only removed my battery.Before buying a new phone i want to try somethings on this,just little more ram would be enough..So that's it hehehe.Ok friend see you later and i must say you are a nice man.God Bless You
Use root browser lite, navigate to system/app and delete it. U need root
sashank said:
Since ICS you can just disable the system (stock) apps that you don't want, in Settings->Apps. It's much safer to do that than to remove/uninstall. You won't gain anything from the extra freed /system partition space anyway.
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
Hello.
I'm having issues removing stock apps from custom rom.
I've tried Rom Toolbox, Root uninstaller, manually deleting apk from Root browser, nothing works. They are removed that time, but when I restart the phone, all of the apps are still there.
I thought maybe I don't have root access, but I've checked with Root checker and it was OK.
With other custom roms it worked OK, I could remove apps.
sashank said:
No problem, we all are newbies at the beginning and learn along the way.
The reason manufacturers and ROMs put all their apps in /system, is because certain apps that are essential to the Android system require higher privileges which are only granted to /system apps. Now apart from those essential apps, there are also a lot of non-essential ones like file managers, Flashlight, Facebook & Twitter apps and a game or two (like HTC Teeter). These are put in the /system partition so that they will survive a factory reset. When a normal user does factory reset, only /data and /cache are wiped. /system stays intact so that after the factory reset, all user installed apps and user data is deleted and the phone is back to factory condition. Suppose the manufacturers had put all the non-essential apps in /data, they would have been wiped too and then some confused users would say that the apps which came with their phone are not there anymore. Suppose you manually delete some apps from /system using a root browser or adb, they won't be there anymore when you factory reset. I've seen many users who've messed around in /system, deleted some really important app/file and gunked up their phone, then factory reset in hopes of restoring everything to the original state with no luck. Only way to get everything back then is to flash a stock ROM or manually push the required app/file again through adb in recovery and set correct permissions, or create a flashable zip of the file and flash it. I'm talking about rooted stock ROMs. If you're running a custom ROM, you can just re-flash the ROM and get everything back.
There is no actual benefit of having free /system space because you can't install things there. You can have a full /system partition and it won't make a difference unless the size of your ROM update suddenly increases a lot and there's no space to flash it, but that won't happen because ROMs are almost always well below the /system partition size. RAM is different. It's just like the RAM chip in a computer. You can regard /system, /data, /cache as different partitions of a hard disk, which in the phone's case is flash memory. Those partitions are in no way related to RAM. Your phone has a fixed amount of RAM which is mentioned in the spec sheet, and unlike computers this RAM is soldered to the motherboard so you can't swap it out for higher RAM. So that's why phones with less RAM will always be slow during heavy use no matter what you try, can't help that (except by creating a swap partition in the SD card if your ROM's kernel supports it). Freeing /system space won't increase your RAM and won't make your phone run faster. These days devices are shipping with a minimum of 1 GB RAM which is enough to run current Android versions decently. Even my HTC Desire HD with 768 MB RAM does a decent job thought it slows down every now and then.
Click to expand...
Click to collapse
Not all apps are in the system partition, a lot of the bloat like the text to speech, play store, play services (185+mb by itself) and quite a few others are soaking up space like crazy in the data partition (u gotta figure it's another way google\phone makers use to slow your phone so u upgrade) and I'm guessing those are the ones that the original poster wants to remove
This error is still not answered on the forums so im starting a new thread.
i get the error as the title.
sd card space is not the problem.
i tried formatting the sd card.
i have less than 50 apps installed.
wiped dalvik cache, and all other sorts people say on other posts.
(my phone is LG P936 so "fix permission" screws up the phone. all text disappears)
have latest cwm recovery.
and still get the error.
any answers please?
and please dont reply if you are going to write an opinion.
only answers please.
sorry for my rude behaviour but I'm sick and tired of reading posts full of opinions and "maybe"s.
Not sure if you ever got this fixed but I 'm suffering from the same error. I tried pretty much everything you tried (even fix permissions) and I have about 20GB free on my SD card so space shouldn't be an issue. I have not yet tried formatting the SD card since it has always worked and CWM is able to write to it because the following files are created:
- boot.img
- data.ext3.tar
- recovery.img
- system.ext3.tar
The files that are missing are (based on older backups):
- .android_secure.vfat.tar
- cache.ext3.tar (probably because I wiped it first?)
- nandroid.md5
I have attached the log from CWM in the hopes that someone can tell me what is wrong. The error occurs at the end of the progress bar of 'backing up /data'.
hey just use TWRP Recovery. It's way better than CWM. normal backup on cwm took me like an hour but twrp was never longer than 10minutes.
Today I have formatted the SD card and tried again, but as expected it did not change anything.
ceoleaders said:
hey just use TWRP Recovery. It's way better than CWM. normal backup on cwm took me like an hour but twrp was never longer than 10minutes.
Click to expand...
Click to collapse
I guess I will give this a try. Can I just install it over CWM or can they run side by side?
different reciveries cannot be run side by side as they are installed on a different partition. so it will always be installed over your current one.
ceoleaders said:
different reciveries cannot be run side by side as they are installed on a different partition. so it will always be installed over your current one.
Click to expand...
Click to collapse
Well, I tried TWRP and it also fails at backing up my data partition. The log is a bit more clear though and it seems to get stuck on "/data/data/com.android.vending/cache/images" which is the last line before it gives an error. I checked the "images" folder and it seems empty but I cannot delete it. Tried ES File Explorer and Terminal Emulator but no way to get rid of it. The folder appears to be related to Google Play, so I cleared all data and cache from Google Play, even uninstalled the updates but there 's simply no way to get rid of it. I 'm not sure if this is the reason why the backup fails, but I CAN copy the folder and even rename it.
Pff looks like I 'm going to have to do a clean install after all .
Hello, I too have this problem and unfortunately TWRP is not available for my phone.
I used to be able to do CWM backups fine on my old phone, and they work great on my tablet. But they consistently fail at "/data" on my Galaxy Ace II x. Might it be because I'm using Link2SD? I don't see why that would cause a problem, but maybe it's having trouble with the symlinks?
Hmm. Seems the issue was that, despite having only 1.28 GB total available storage space on stock, the backups wanted more than 4 GB. Cleared some room on my microSD card and suddenly backups worked fine! Of course, shortly after I installed CyanogenMod, which has much smaller backups...
Sent from my GT-S7560M using Tapatalk 4
I forgot to report back here but the only way I found to fix the problem was by doing a clean install. After that, I was able to backup my data partition again. I then restored my apps ' data with TB and was unable to backup the data partition again. I 'm guessing one of my apps had corrupt data, but never got to find out which one it was.
maybe your partition not match with recovery, like something wrong vold.fstab
Just in case anyone still wants to know how to fix this, I managed to solve it by running these commands:
1. run adb shell in recovery.
2. unmount data partition (umount /dev/block/mmcblk0p26). -> this one failed so I skipped it
3. run e2fsck /dev/block/mmcblk0p26
See http://forum.xda-developers.com/showpost.php?p=48659092&postcount=868 for original post.
I got a few HTREE errors and a bunch of duplicate names which I renamed when prompted. Booted the phone and rebooted into TWRP and now I am able to backup my data partition again. :good:
EDIT: Problem reappeared so I tried the above commands again but it said that the filesystem was clean. Ran 'e2fsck -f /dev/block/mmcblk0p26' instead and had to fix a bunch of HTREE errors from Facebook again and duplicate names from Xprivacy but now I 'm able to backup my data partition again.
Dude just selest the backup format as both zip and tar filea
Hi guys anyone know where files can be written to on android without root access? I have an app which uses Hive login (com2us/gamevil games), and it saves the username in the login field even if I uninstall the app and go as far as doing factory reset on my phone. When I reinstall the game after a factory reset, the username remains pre-filled in the space. Any idea where these are being saved to?
Sounds like it's either on your sdcard, online, /data/data/"appname"/ or in the cache of the app.
think it may be online. The login page from within the app looks like a landing page for a browser, so maybe the game itself uses some internal browser to load the login page. What I don't get though is why this information is still saved despite the fact that I wiped every accessible partition on my device /sdcard /data /cache, etc. Autofill information is saved locally right?
I'm concerned about this because I saw 3 more names on the dropdown list yesterday. They are not mine, and all have a format of 4 letters and 4 numbers, so this suggests my device was compromised and I think a botscript ran. What I'm wondering is whether or not the script can still be saved on my device, since this autofill stuff seems pretty persistent. I wasn't sure if it's possible for malicious code to write something to a partition that isn't wiped with a conventional reset, and then re-establish itself after a wipe.
gtcardwhere said:
think it may be online. The login page from within the app looks like a landing page for a browser, so maybe the game itself uses some internal browser to load the login page. What I don't get though is why this information is still saved despite the fact that I wiped every accessible partition on my device /sdcard /data /cache, etc. Autofill information is saved locally right?
I'm concerned about this because I saw 3 more names on the dropdown list yesterday. They are not mine, and all have a format of 4 letters and 4 numbers, so this suggests my device was compromised and I think a botscript ran. What I'm wondering is whether or not the script can still be saved on my device, since this autofill stuff seems pretty persistent. I wasn't sure if it's possible for malicious code to write something to a partition that isn't wiped with a conventional reset, and then re-establish itself after a wipe.
Click to expand...
Click to collapse
If it somehow got root access it can be anywhere. /system, /etc anywhere.
Maybe ask over in the security discussion? I myself am not that experienced with malware on android.
Sent from my One Plus One