Related
After I enabled Darktremor Apps2SD, my internal memory went from 157 to about 89. Sweet. Unfortunately, I am seeing a marked increase in internal memory used over the past week or so. I am not near any critical threshold, but I am concerned with its rate of growth. Is there any way to "clean it out" besides using CacheMate, which I believe only clears app cache that is in the app file (correct me if I'm wrong).
I have not installed more than 3 apps since the A2SD, and believe all of them are "move to SD" enabled. I verified their location using Astro. I do use web browsers, flip between Dolphin and Opera - still deciding on which I want to keep. I also use Tasker for many things, but I'm far from being a power user. Tasker is on my SD, though the dev claims it won't move to SD. (I'd like to put it back to internal because it seems a little sluggish)
So how do I "clean up" my internal memory? Is it all just factory apps and Dalvik? Can I wipe Dalvik and reboot and find less internal memory used?
duckredbeard said:
After I enabled Darktremor Apps2SD, my internal memory went from 157 to about 89. Sweet. Unfortunately, I am seeing a marked increase in internal memory used over the past week or so. I am not near any critical threshold, but I am concerned with its rate of growth. Is there any way to "clean it out" besides using CacheMate, which I believe only clears app cache that is in the app file (correct me if I'm wrong).
I have not installed more than 3 apps since the A2SD, and believe all of them are "move to SD" enabled. I verified their location using Astro. I do use web browsers, flip between Dolphin and Opera - still deciding on which I want to keep. I also use Tasker for many things, but I'm far from being a power user. Tasker is on my SD, though the dev claims it won't move to SD. (I'd like to put it back to internal because it seems a little sluggish)
So how do I "clean up" my internal memory? Is it all just factory apps and Dalvik? Can I wipe Dalvik and reboot and find less internal memory used?
Click to expand...
Click to collapse
Yes, that's exactly what I do whenever I feel the internal memory needs to be cleaned up, or if I uninstall several apps - just to make myself feel like I'm taking good care of my phone - wipe Dalvik and reg caches through recovery, reboot, and voila. It takes a little longer for the phone to boot as it is recreating the cache for the apps you still use but my phone is still running like a champ so I'm happy.
Apps on SD (not ext) are still potentially taking up quite a lot of space, so I personally move stuff that installs to SD to "internal" on my phone, that way it goes to ext, including its data.
Also, the browser seems to cache a lot of data, not just browser cache, but some other stuff, but it's more of an issue with 2.2... but if your Aria is 2.2, try killing the Browser from the Applications list or a task killer and see what happens to /data
Failing that if you're rooted, go look yourself and see what's taking space. For me all of my used space is accounted for in dalvik-cache. If I install many more apps, I'll have to move dalvik to sd.
If your running Froyo then you should look up TA Utility and Move2SD.
TA utility moves your cache to your SD card and Move2SD lets you Move all your apps to the SD card. You got to be Rooted to use these app but I love the space I got now on my phone.
khaytsus said:
Apps on SD (not ext) are still potentially taking up quite a lot of space, so I personally move stuff that installs to SD to "internal" on my phone, that way it goes to ext, including its data.
Click to expand...
Click to collapse
hang on a second ... you say that you have an ext partition on your SD card and all apps are installed there when you select "internal" installation??
That's what a2sd does. It moves the internal applications (and optionally the dalvik cache) to a partition on your SD card. This frees up the internal memory on your phone.
Ok, that I know. I was just confused with your description.
I use A2SD as well but it does not need an ext3 partition. It goes straight to my fat23 SD card.
Then you're not using DT's A2SD which is what this thread is about.
what exactly is app2sd??
I am using RAFDROID ROM on a TMOUS HD2
in the instructions he said that if I am using a euro HD2 with 512 rom I should partition my sd card
so I did not do that and flashed the rom on my NAND
then when I started using apps I noticed that after two weeks usage I have only 50 MB left!!!!
so I want to activate app2sd and move my apps to the sd card..
so please I need some help from the experienced users on this great forum that can advise me about what exactly is this and how to activate and use it
thanks in advance!!
Apps2sd moves your apps to the sdcard, usually to an ext 3/4 partition. I don't know about the ROM you're using, but on the one I use (mdj's Cyanogen 2.6), you can move apps to external storage like this: settings --> applications --> manage applications. Then select an app and there is an option to move to sdcard.
@freeincolorado, the method you described is not A2SD+, that method is called move2sd.
A2SD+ puts the dalvik cache as well as the applications in a EXT2/3/4 partition, usually called the sd-ext partition. This method will still show you that the application is in the ROM. However, the sd-ext is used instead, depending on the chief implementing A2SD+ in their ROM, the remaining ROM space is suppose to report the partition "sd-ext" free space, however, certain ROMs are not properly done in my view, and will report the userdata partition free space instead. Such as MDJ's Cyanomodgen 7+ Gingerbread.
How to use A2SD+
Usually, they require you to partition your SD Card into 2 primary partition. The first partition is FAT32 where you store all your extras, such as music, ebook, etc (Like how your SD card is presently used). The 2nd partition is EXT2/3/4 depending on your preference, most people do not use EXT2 anymore as it does not support Journaling, since data can be easily corrupted with a battery pull. EXT3 and EXT4 contains journaling feature, so when battery is pulled, data corruption is minimal.
NOT ALL ROMS SUPPORT EXT4. This is a kernel thing, so if the rom uses a kernel that does not use EXT4, then it will not read the partition.
A2SD+ has a nice feature as well, when you switch ROM, you do not need to re-install all the applications, since all applications are placed in the sd-ext folder, including the dalvik cache. However, this also includes the system default applications which might not be compatible with another rom build.
Hello again, I need clarification with this subject...
I had a difficult time in rooting my android, thinking I failed. so for many times I rooted, installed xrecovery, then most importantly apps2sd. but I don't think it works, then I found all about Links2sd. I installed it, and each time after installing I always select the "link2sd" option, and I check the include davlik cache, but my phone memory is continually decreasing... is this normal or not? could there be a conflict with apps2sd and link2sd since I don't know if I have deleted apps2sd. sorry I'm an android newbie. Thanks..
Well... if you had app2sd link2sd would monit about it and asked you to uninstall it first.
If you don't know if your phone is rooted, look through apps - if you have a superuser app - you're rooted
As for link2sd working or not: connect your phone to the computer and open minitool partition wizard home. It will see your ext2 partition along with free and occupied space. If there are any apps on ext2 partition of your SD card - apps are installing there and the slight decrease of space is due to the existing shortcut files. Because you have created ext2 partition, haven't you?...
I did what you said and yes I found files on the other partition I created. but problem is, some files still go to the phone memory, for example the game app "ninjump" has 15mb installed on the phone memory while on links2sd it shows that it is linked to the sd card.
also, I tried removing the memory card, and when I turned on my x8 the programs were missing, so I suppose links2sd is working.
only problem is now is that some chunks are still installed to the phone memory. is there a way of totally redirecting everything to the sd card?
link2sd: Leave data files in Internal Memory, and you can choose the apps to SD
app2sd: Copy all data from the application to the SD, It's all automatic
nowonanx8 said:
I did what you said and yes I found files on the other partition I created. but problem is, some files still go to the phone memory, for example the game app "ninjump" has 15mb installed on the phone memory while on links2sd it shows that it is linked to the sd card.
also, I tried removing the memory card, and when I turned on my x8 the programs were missing, so I suppose links2sd is working.
only problem is now is that some chunks are still installed to the phone memory. is there a way of totally redirecting everything to the sd card?
Click to expand...
Click to collapse
Ok, here's the deal - how many times did you install ninjump in the past? If more then once, and meanwhile you moved it to or from ext2 it might have (though the probability is very slight) that you have two apps - one in internal storage and one in ext2 storage.
So, navigate into ext2 partition (it's a folder in root directory - sdext or so) and look for this app. It might be hard, as names of linked apps are somewhat messed up, but there should be icons If there is no app on ext2, try switching it back to internal mode and then onto ext2 again - perhaps without linking dalvik cache.
chequebo1 said:
link2sd: Leave data files in Internal Memory, and you can choose the apps to SD
app2sd: Copy all data from the application to the SD, It's all automatic
Click to expand...
Click to collapse
Thank you, that was sooooo relevant!
APP2SD
I having problem with the app2sd too..i dunno whether it works...This is what i had done..I had busybox, superuser, and xrecovery installed and rooted. But when come to partitioning the sd card, i partitioned it into 3 parts : FAt, ext2 and ext3...after that i installed the update.zip and custom zip of app2sd...the phone starts not recognizing the sd partition...anyone can help here??
I use titanium backup to see app2sd works or not. if a2sd decrease, so it work.
if internal still decrease, I guess some file or even some app just can't work with app2sd.
one question too, how or can I move games data from fat sdcard to ext2 partition? like gameloft data. I need my fat space for other file
Graveir said:
Ok, here's the deal - how many times did you install ninjump in the past? If more then once, and meanwhile you moved it to or from ext2 it might have (though the probability is very slight) that you have two apps - one in internal storage and one in ext2 storage.
So, navigate into ext2 partition (it's a folder in root directory - sdext or so) and look for this app. It might be hard, as names of linked apps are somewhat messed up, but there should be icons If there is no app on ext2, try switching it back to internal mode and then onto ext2 again - perhaps without linking dalvik cache.
Click to expand...
Click to collapse
I tried navigating to the ext2 partition using minitool partition wizard, and I indeed saw files that I have installed there. so do you mean that apps2sd is better than links2sd? thanks..
Well... I'm not saying anything is better, though I used both solutions in three different ways.
For stock SE ROM link2sd is better, since you only need to partition SD card into primary fat32 and primary ext2 - nothing more. Then you install an app and all works fine.
With custom ROM you cannot use link2sd, since they all have app2sd hack preinstalled (well, you can always modify files, but what for?). Problem occurs when you have this hack AND ext2 partition. The hack then moves automatically all your apps to ext2 memory along with dalvik cache if you install them in internal storage. If you install in external storage, the app goes to fat32 secure folder and dalvik cache remains in ext2. If you don't have any ext on custom ROM, dalvik cache is always in internal storage, while you can move any non-system app onto fat32 sd card.
The ext2 solution in custom ROMs may seem convinient, but for me it was not. When you use apps like phone locator, they should always dwell in internal memory, since SD card can be easily taken out, while deleting such an app from a remotely locked down phone would require flashing, otherwise the device is useless for the thief
Well actually both app2sd and link2sd are typically similliar. I've tried app2sd before and it still leave some files in internal memory. So will link2sd. But link2sd is much more easier to use because once your phone is rooted you just need to install it on your phone without going through the adb shell thing. Easy for newbie for sure. But you just have to manually link new installed applications and games. That's what differ link2sd with app2sd. Now I'm using link2sd. If you want to make sure, why don't you try those froyo phone. Try to use the app2sd stuff on those phone. They still install some applications on their internal as well although they have built in app2sd.
Sent from my E15i using XDA Premium App
Hi mates,
When we are flashing a Custom Rom from the CWM, we are normally instructed by the Devs only to do few steps on CWM like “Wipe Data/Factory Data Reset, Wipe Cache etc.. which we simply follow, but most of the people don’t know, including me, what these options and many other options of CWM are really standing for.
When I googled, I could not find a thread which explains about these options in a single thread, so I would like to share with my friends about what I found the Common Options of the CWM here...
Obviously these are commonly applicable for all the devices which are having CWM, but I am always concern about my favorite Galaxy S II.
People who are completely new to Recovery and these options, I suggest them to read this thread first and give a thanks to it's author.
What Is Recovery & Download Mode?
The oder and segregation of the below items in the CWM menu may vary or some of them may be removed in different custom recoveries designed by respective Developer.
CLOCKWORKMODE BASED RECOVERY MENU
1) Reboot Menu :
reboot system now
This one is self-explanatory.
2) Install Menu :
choose zip from (internal/ external) sdcard /
Lets you install any zip file (with any name) from any location on your SD card. The file can be for a ROM, a kernel, an application, a theme or any mod as long as it is in recovery-flashable zip format.
apply /sdcard/update.zip
This one is essentially the same as the ‘apply update from sdcard’ option of the main menu. widely used option for installing a ROM that you have downloaded and copied to your SD card. Entering this option will bring up a screen that will allow you to browse your SD card for the zip file.
apply update from sdcard
This can be used for installation of any official or unofficial update, ROM, kernel, theme etc. that is in a zip format installable from recovery, as long as the file is named update.zip and it has been placed on the root of your SD card (i.e. not in any sub-folder). Selecting this option will bring up a rather annoying confirmation prompt but this has saved us on multiple occasions from a lot of trouble we would have been into due to accidental key presses.
toggle signature verification
Turns the signature verification on and off. When signature verification is on, you will not be able to install any custom ROMs that haven’t been signed by the developers (most custom ROMs aren’t signed). Switching it off skips the signature verification check and proceeds with the installation.
toggle script asserts
Seldom-used option for a vast majority of users. It simply turns script asserts on or off. If you don’t know about these (I don’t), it’s best not to change this option.
3) Wipe Menu
wipe data/factory reset
This option wipes all user data on the device as well as cache. Doing this will leave your phone in the state it was in when you bought it or when any custom ROM was first installed. It will also wipe any sd-ext partition that you might have setup. (see more about sd-ext below under partition)
wipe cache partition
This is a good practice to do this before flashing any ROM. The /cache partition just stores temporary files that are not critical to device operation and can be re-generated easily, this Wipes the cache partition of the device to clear all the data accumulated there over use. This is often used before installing a new ROM, app, kernel or any similar mod via recovery.
Wipe Dalvik Cache
Allows you to wipe the cache for the Dalvik virtual machine. The dalvik cache wipe is quite similar to cache wipe but it stores the post ran java applications. Since Android is JAVA based, it uses the same java virtual machine for compiling. The dalvik cache just stores post-compiled applications in order to speed up the system. Wiping this just forces the system to re-cache those application. It causes no problems but a slight hint of lag on first boot. This is required before most ROM installations and at other occasions too, for fixing some problems.
Wipe Battery Stats
Wipes the saved battery usage statistics and effectively recalibrates the battery. Useful in various scenarios when Android isn’t showing correct battery levels.
4) Nandroid menu
backup and restore Undoubtedly one of the most important features provided by a custom recovery, the backup and restore feature – also known as Nandroid backup – allows you to take a snapshot of your phone’s entire internal memory including all partitions, and save it on the SD card.
Backup
Takes a Nandroid backup, as explained above.
Restore
Lets you restore a previously taken backup. Entering this option presents you with a list of existing backups from the SD card that you can choose from for restoration.
Advanced Restore (new options are available separately to restore from external or internal SDcard in the latest CWM)
This option is similar to the Restore option but once a backup has been selected to be restored, this option allows you to choose what parts of it to restore. You can choose to restore the boot, system, data, cache and sd-ext partitions.
5) Storage menu
mounts and storage
Allows you to perform maintenance tasks on all the internal and external partitions of your android device
mount/unmount /system, /data, /cache, /sdcard, /emmc.
These options let you toggle between mounting or unmounting these respective partitions. Most users don’t need to change these options.
format system, data, cache, sdcard or sd-ext
These let you directly format any of these partitions. Take extreme care with this option as formatting any of these partitions will result in losing all data on them, especially the boot and system partitions. Formatting the system partition will remove your ROM and leave your phone without an operating system while wiping the boot partition may brick your phone unless you restore or flash another one before rebooting your device. See below more explanation about these partitions.
mount USB storage
Lets you enable USB mass storage mode for your SD card right from recovery so that you can connect it to your computer via USB and transfer any files to/from it without having to leave recovery.
6) Advanced
This section contains a few options most users will not require, Here are the options from this section:
Report Error
In case of errors, this feature can be used to save a log of recent ClockworkMod recovery operations on the SD card that you can later report from Android using ROM Manager.
Key Test
Lets you press any of the hardware keys to see if they are properly functioning, and to see their key codes.
Partition SD Card
This option gives you a no-frills way to partition your SD card properly for use with ROMs that support data2ext (a very handy hack for low internal memory devices that enables an /sd-ext partition on the SD card to be used as the internal user data storage i.e. as the /data partition). Once this option is selected, you will be given options to choose the sizes for the /sd-ext partition as well as an optional /swap partition on the SD card, and will then automatically format it for you, leaving the remaining space for normal SD card usage. This option will wipe all data from your SD card so use it with caution!
Fix Permissions
Fixes the file permissions for the internal memory partitions back to default. This is very useful as a fix for several errors and Force-Closes that start appearing after you or an application you installed and provided root access end up messing up the permissions of important files.
PARTITIONS :
The Android uses several partitions to organize files and folders on the device. Each of these partitions has a distinct role in the functionality of the device, but not many Android users know the significance of each partition and its contents. In this guide, we will take you on a tour of Android partitions, what they contain and what can be the possible consequences of modifying their content.
Let’s start with a list of standard internal memory partitions on Android phones and tablets. These are:
• /boot
• /system
• /recovery
• /data
• /cache
• /misc
In addition, there are the SD card partitions.
• /sdcard
• /sd-ext
Note that only /sdcard is found in all Android devices and the rest are present only in select devices. Let’s now take a look at the purpose and contents of each of these partitions.
/boot
This is the partition that enables the phone to boot, as the name suggests. It includes the bootloader and the kernel. Without this partition, the device will simply not be able to boot. Wiping this partition from recovery should only be done if absolutely required and once done, the device must NOT be rebooted before installing a new one, which can be done by installing a ROM that includes a /boot partition.
/system
This partition basically contains the entire operating system, other than the kernel and the bootloader. This includes the Android user interface as well as all the system applications that come pre-installed on the device. Wiping this partition will remove Android from the device without rendering it unbootable, and you will still be able to put the phone into recovery or bootloader mode to install a new ROM.
/recovery
The recovery partition can be considered as an alternative boot partition that lets you boot the device into a recovery console for performing advanced recovery and maintenance operations on it. We have already learnt about this partition and its contents above.
/data
Also called userdata, the data partition contains the user’s data – this is where your contacts, messages, settings and apps that you have installed go. Wiping this partition essentially performs a factory reset on your device, restoring it to the way it was when you first booted it, or the way it was after the last official or custom ROM installation. When you perform a wipe data/factory reset from recovery, it is this partition that you are wiping.
/cache
This is the partition where Android stores frequently accessed data and app components. Wiping the cache doesn’t effect your personal data but simply gets rid of the existing data there, which gets automatically rebuilt as you continue using the device.
/misc
This partition contains miscellaneous system settings in form of on/off switches. These settings may include CID (Carrier or Region ID), USB configuration and certain hardware settings etc. This is an important partition and if it is corrupt or missing, several of the device’s features will will not function normally.
/sdcard
This is not a partition on the internal memory of the device but rather the SD card. In terms of usage, this is your storage space to use as you see fit, to store your media, documents, ROMs etc. on it. Wiping it is perfectly safe as long as you backup all the data you require from it, to your computer first. Though several user-installed apps save their data and settings on the SD card and wiping this partition will make you lose all that data.
On devices with both an internal and an external SD card – devices like the Samsung Galaxy SII – the /sdcard partition is always used to refer to the internal SD card. For the external SD card – if present – an alternative partition is used, which differs from device to device. In case of Samsung Galaxy S series devices, it is /sdcard/External_sd while in many other devices, it is /sdcard2. Unlike /sdcard, no system or app data whatsoever is stored automatically on this external SD card and everything present on it has been added there by the user. You can safely wipe it after backing up any data from it that you need to save.
/sd-ext
This is not a standard Android partition, but has become popular in the custom ROM scene. It is basically an additional partition on your SD card that acts as the /data partition when used with certain ROMs that have special features called APP2SD+ or data2ext enabled. It is especially useful on devices with little internal memory allotted to the /data partition. Thus, users who want to install more programs than the internal memory allows can make this partition and use it with a custom ROM that supports this feature, to get additional storage for installing their apps. Wiping this partition is essentially the same as wiping the /data partition – you lose your contacts, SMS, market apps and settings.
Now whenever we install a ROM or mod that requires we to wipe certain partitions before the installation, we should be in a better position to know what we are losing and what not and thus, we’ll know what to backup and what not.
Best Regards
http://forum.xda-developers.com/showthread.php?t=1134290
Yep. Been done before a long time ago. Tho I do admire your initiative in putting the info together
Stifler69 said:
http://forum.xda-developers.com/showthread.php?t=1134290
Click to expand...
Click to collapse
No Doubt this one should be on the top of this thread,
What a simple and awesome explanation about the Recovery & Download mode, many thanks to pulser_g2
I know, majority of users only need the simple steps and shortcuts, they don’t care what’s happening internally and theoretically, but some are really curious to know…
Many thanks mate....
zaheedahmed said:
No Doubt this one should be on the top of this thread,
What a simple and awesome explanation about the Recovery & Download mode, many thanks to pulser_g2
I know, majority of users only need the simple steps and shortcuts, they don’t care what’s happening internally and theoretically, but some are really curious to know…
Many thanks mate....
Click to expand...
Click to collapse
Nah mate you do what you have to do. It is a good thread and provides good information. Nice work. Just wanted to show you Pulsers thread as well though because he has done something similar to yours long time ago..But anyway good work and if you need any help let me know
Thanks, will save later text in PDF and keep it on PC just to have one more tutorial about things
Awesome write up!! Brilliant!
As you are so knowledgeable about CWM, perhaps I can ask you a question?
When I do a backup, it says that no external SD card was found, so it skipped the external?
When I check under mounts, the only option for the external SD card is to UNmount.... This would suggest that the card is mounted, correct?
So how would I go about backing up the external card too?
Thanks!
Sent from my SGH-I727R using xda premium
Question, if i do nandroid backhp through CWM, i suppose it saves files that i dl such as apps/games, or i need to download later again 600mb+?
Sent by powaaaaah of GT-I9100 Taparatatatalk!
shaggyskunk said:
Awesome write up!! Brilliant!
As you are so knowledgeable about CWM, perhaps I can ask you a question?
When I do a backup, it says that no external SD card was found, so it skipped the external?
When I check under mounts, the only option for the external SD card is to UNmount.... This would suggest that the card is mounted, correct?
So how would I go about backing up the external card too?
Thanks!
Sent from my SGH-I727R using xda premium
Click to expand...
Click to collapse
Thank you for your appreciation,
I would like to express once again as I mentioned in the starting of the thread that this is only a humble effort of the undersigne that I searched for such information and combined at one place here....
As far as I know about your problem of SD card storage, this is a compatibility issiue which varries on one custom recovery to another, also one SD card to another. such issues are fixed by developers in their latest versions of recoveries.
I experienced once the same issue which was resolved when I changed my SD card.
And my current (touch) recovery of Redpill v1.3 allows me to Backup and restore from external SD card with all available options flowlessly.
Thanks
X-Plosiv said:
Question, if i do nandroid backhp through CWM, i suppose it saves files that i dl such as apps/games, or i need to download later again 600mb+?
Sent by powaaaaah of GT-I9100 Taparatatatalk!
Click to expand...
Click to collapse
Between CWM & Titanium, you should not have to download anything.
Sent From my Two Tin Cans & String Device on The Wookie Network
X-Plosiv said:
Question, if i do nandroid backhp through CWM, i suppose it saves files that i dl such as apps/games, or i need to download later again 600mb+?
Sent by powaaaaah of GT-I9100 Taparatatatalk!
Click to expand...
Click to collapse
Of course it backs up all your installed apps and system data along with the ROM, but it do not back up the additional data which is downloaded and stored in User's partition of your SD card by the applications, such data will remain on your SD card untill you format it, available to support your apps when you return to the previous ROM.
awsome eplanation
as above posts say awsome explinationculdnt b clearer now then all
zaheedahmed said:
Of course it backs up all your installed apps and system data along with the ROM, but it do not back up the additional data which is downloaded and stored in User's partition of your SD card by the applications, such data will remain on your SD card untill you format it, available to support your apps when you return to the previous ROM.
Click to expand...
Click to collapse
Yes, but when I do format/wipe all, I guess then it deletes all that is on SD card as well, such as game files and music? If so, I'd rather just copy paste it on my PC, then after doing all wipes and formats, just copy back from PC
Zaheed, you are far too humble! Your post was brilliant, informative & timely.
Sent From my Two Tin Cans & String Device on The Wookie Network
X-Plosiv said:
Yes, but when I do format/wipe all, I guess then it deletes all that is on SD card as well, such as game files and music? If so, I'd rather just copy paste it on my PC, then after doing all wipes and formats, just copy back from PC
Click to expand...
Click to collapse
When you do normal wipes (data/ factory reset, cache, dalvik) before installing/restoring ROM, it won't touch any data which is saved in your SD Card normally, but it is more safer if you back such application data to you PC which normally find in a folder "Android/ Data /xxx" in the root of SDcard
Thanks for info.
I have read a lot on this but am still nor clear whether a wipe data/factory reset includes a full cache wipe. Most rom install instructions tell you to do both, but it seems a wipe cache is redundant if you factory reset.
SimboXXX said:
Thanks for info.
I have read a lot on this but am still nor clear whether a wipe data/factory reset includes a full cache wipe. Most rom install instructions tell you to do both, but it seems a wipe cache is redundant if you factory reset.
Click to expand...
Click to collapse
Yes, you are right, I also understand the same, but the option for merely wiping cache is kept for using in some odd situations, like when we fingered to the ROM and got some error, then we got a no-wipe version of the existing ROM to reflash, such case we need only to wipe cache…. I have got an error recently on CWM when I reflashed my no-wipe Checkrom v6 without wiping anything, then I wiped only cache, problem solved…..
what ever may be the theory, do as the developers directed for their ROM…..NO RISK
shaggyskunk said:
Zaheed, you are far too humble! Your post was brilliant, informative & timely.
Sent From my Two Tin Cans & String Device on The Wookie Network
Click to expand...
Click to collapse
thanks mate...
Thanks for the thread, you can never know too much. On second thoughts, there's probably no danger of that.
What would be really good if you have the knowledge, is a detailed guide on CWM Edify scripting. I'm sure many people would find that useful, especially me. There doesn't seem to be a lot of good guides or information on the language, at least I can't find them yet. If you have any good links I'd definitely appreciate it as well.
Here's another bit of information, that answered a question I had....
In case anyone else has this question...
Here is the answer from:
http://android.stackexchange.com/qu...ter-no-sd-ext-found-skipping-backup-of-sd-ext
" This means you do not have an ext3/4 partition on your sdcard. This really ins't a big deal, this is like a legacy part of the nandroid backup process. CM doesn't "officially" support the sd-ext partition any more anyhow."
Hope it helps someone else... In the end, the answer is pretty straight forward.
Sent From my Two Tin Cans & String Device on The Wookie Network
Sent from Down The Rabbit Hole, using Tapatalk 2
I've just installed the Paranoid-Jellybean 1.99
http://forum.xda-developers.com/showthread.php?t=1793180
on my EU HTC HD2
I can't anderstand what sd the idea behind program S2E, it seems its purpose is to move apps to SD but when used it this way then all newly installed Widgets disappeared What's more even without launching S2E in Settings thare are options to move individual apps to SD (not for all in fact)
it isn't talking about the normal fat partition on the sd card, you must have an EXT partition created before using the app.
What it does, is take the ext partition on the sd card and makes the system think that it is internal memory, thus giving you more 'internal' memory for apps and data and such like.
This isn't the same as choosing 'move to sd ' in the settings - apps options, as this moves the app to the FAT (windows) partition of the sd card. Some apps wont work when 'moved to sd', however they WILL work from the ext partition, because android thinks its internal.
So, if you haven't already got an ext partition, back up the contents of your current sd card (it will get wiped) then reboot into cwm, choose 'advanced - partition sd card' and choose a partition size. (512 or 1024 is usually plenty) then restart android and try the app again.
Any apps that you have already 'moved to sd', go move them back to internal, and the system should automatically move them from the FAT partition to the EXT partition.
Tahnk you for your explanation. Also I must apologize I confused the names of the programs - in fact its S2E rather than A2S (the previous post have written from memory). However probabely this s2e serves the same purpose, as it has such relevant commands:
Applications - Location: /data/app
Private apps - Location: /data/app-private
...
and so on, until:
Dalvik cache - Moving from /data to /sd-ext
So, I've chosen the first option and got displayed:
Application
Moving from /data to /sd-ext
Reboot is required!
and rebooted the phone, but the result was disappointing - several apps dissappeared including all Widgets!
Of course I've had ext3 partition previously set.
What was wrong?
Other question please: exactly WHAT is worth moving to SD Ext partition, Dalvik cache too?
yea they do the same/similar things - namely move parts of the system to the ext partition, and create symbolic links so that the system doesnt notice they've moved.
You seem to be moving your entire data folder to the ext, which i believe has an impact on boot performance, since the data partition wont be mounted straight away, and android needs it during boot.
I don't know a great deal about the various app2sd scripts, but the ones i've used normally only move the /data/app/ (your user installed apps folder) and the dalvik cache to the sd-ext partition.
samsamuel said:
yea they do the same/similar things - namely move parts of the system to the ext partition, and create symbolic links so that the system doesnt notice they've moved.
You seem to be moving your entire data folder to the ext, which i believe has an impact on boot performance, since the data partition wont be mounted straight away, and android needs it during boot.
I don't know a great deal about the various app2sd scripts, but the ones i've used normally only move the /data/app/ (your user installed apps folder) and the dalvik cache to the sd-ext partition.
Click to expand...
Click to collapse
So won't it exert excessive load on SD card which could lead to some sort of instability or other issues?
ioy said:
So won't it exert excessive load on SD card which could lead to some sort of instability or other issues?
Click to expand...
Click to collapse
better than exerting load on the nand and increasing the chances of bad blocks, right?
samsamuel said:
better than exerting load on the nand and increasing the chances of bad blocks, right?
Click to expand...
Click to collapse
theoretically YES but then does it also apply for the whole Android ROM itself (please compare the neighbouring discussion "is NAND Android better than SD and why?")
ioy said:
(please compare
Click to expand...
Click to collapse
no thanks, i have far more interesting things to do. i couldn't care less if there's excess load, though i'm pretty sure there isn't, since i've been running an ext partition for several months and no problems.
Have you understood me well? I've asked about the problem probably NAND ROMs themselves wear NAND memory too so would it be safer (for the device) to use SD ROMs (which write only on SD memory all the time)? How do you think, could it be the case?
i think if it were of any real benefit, people would be talking about it, but no one does. I guess its down to you, if YOU think it will help, then do it. If you don't, don't!
I guess battery drain would be teh real deal maker/breaker. I havent used sd android, but i believe it to be (in general terms) a little less stable, more prone to slowdowns, and harder on teh battery. But thats all anecdotal evidence, as i said, ive never booted sd android.
(edit - i must say, in humour, not meaning offence, that between this thread and your other thread, you sound like a guy who just bought a sports car and wants to cycle to work to save wear and tear on teh car )