Original message: Installing applications on an SD card on a GT540 (Post # 5687678) В© DenHome66
***
Installing applications on the SD card on the GT5403 in 1 [attachment = "690534: app2sd_G .... 10_3in1.zip"]
The attached file contains everything necessary for installing applications on the memory card (KP) in whole or in part, on phones with the “Superuser” installed, i.e. need root =
root .
Installation is reduced to running a script that performs the necessary actions with an additional section of the memory card and rebooting the operating system (OS). Those. everything is simple, it remains to choose the desired script. In folder
gscript there are three of them:
пїЅ1 a2sd.sh ,
пїЅ2 a2sd_data.sh and
пїЅ3 a2sd_data_DH.sh .
The installation process has been repeatedly described in this topic and in the neighboring ones, so in a nutshell:
1. Save the installed (I use
Titaniumbackup ).
2. Turn off the phone, remove the CP, insert it into the computer (card reader), reduce the size of the existing fat16 / 32 partition, create a new BASIC partition - the type of file system
ext2 , section name is empty. (I did it with
Paragon Hard Disk Manager from page 19 section
ext2 SECOND , i.e. on right)
3. We copy
three folders from archive
to root cards (section
Fat ), rearrange the card in the phone, turn on the phone.
4. We do a hardware reset = hard reset = XP. We go through the welcome screen. If you have chosen a script
пїЅ2 -a2sd_data.sh, then you must do this if selected
пїЅ1 or
�3 , then you can not do XP, but simply delete all applications except vital ones in order to free up the phone’s memory as much as possible (then it will fit more). For
пїЅ1 and
пїЅ3 You can install / restore the desired one (if XP was done). Recovery from backup does not take much time.
5. We set, if not worth it, and run
Gscript (available in the archive). Add the selected script (left button, "Add script", "Load file", select, "Save"), run it and wait ... If successful, we see
"done, reboot phone" click dig
"close" and you can right there (from Gscript)
"Reboot" .
6. Restore / install applications. We use it.
Not sure what to choose? I’ll try to save you (as I can) from reading 70 pages, although the latter is useful.
A bit of theory: almost all custom Android OS applications are installed in a folder
/ data / app , and it takes up most of the space allocated for the user in the phone’s memory. There are applications that must be installed in the folder
/ data / app-private , what, why and how - search drives. Settings and application data are located in the folder
/ data / data - the ratio of the volume of data to the volume of the application itself is different, in my case ~ 140Mb of application (
data / app ) accounts for ~ 35MB of data (in
/ data / data ), i.e. ~ 1/4. About the same amount (I have ~ 40MB) is the folder
/ data / dalvik-cache , and moreover, it is constantly growing (application caches are stored there that accelerate their work, for example, Gallery, Maps, YouTube, ...)
To transfer user data from the phone’s memory, these scripts exist that simply copy files from the phone to the memory card and initiate the “substitution” of “native” folders with files to the folders from the memory card when the OS boots.
пїЅ1 a2sd.sh - transfers to KP:
/ data / app and
/ data / dalvik-cache .
Folder
/ data / data that is used when loading the phone, it is unchanged and always in the phone’s memory, which guarantees the device’s operability without a CP, in this case, naturally, the applications installed on it disappear along with the card. This option works stably for most users who install it. However, when returning the KP "to their homeland", some applications need to be reinstalled, the reason for this is, apparently, the folder that changes when the OS boots
/ data / dalvik-cache at least the Polish script "progenitor"
/ data / dalvik-cache remains untouched and this problem is absent. Recovery (reinstallation), in the presence of the saved copies (Backup) - a minute business.
пїЅ2 a2sd_data.sh - transfers the entire folder to the CP
/ data along with all content including
/ data / data , which is used by the phone when booting the OS until it is "replaced" (mounting) it with the same name from the CP, so an important condition for the stable operation of this very "economical" script is, in my opinion, the mandatory execution of XP before use script. Then, when loading the OS, the folder
/ data / data It remains empty (until the moment of mounting the gearbox), which minimizes the possibility of errors. Perhaps the failure to fulfill this particular condition leads to unstable operation of the device for most users (according to the survey). Using the phone without a CP is not recommended. Prerequisite: KP db not lower than
class 6 .
пїЅ3 a2sd_data_DH.sh - transfers to KP: the entire folder
/ data (like
пїЅ2 ), but critical to its location, folder
/ data / data remains in the phone’s memory (as in
�1 ), and with any reasonable (logical) use of the phone with the CP, or without it, there is no disruption to the OS (at least I could not do this). Retribution for stability - some consumption of space from the phone’s memory (but less than in
пїЅ1 ).
If you will never remove the CP from the phone, then any of the scripts works fine.
If you plan to sometimes use the phone without a CP, then use the script
пїЅ3 and follow a few simple rules (the rules apply to
пїЅ1 ):
1. We removed the KP * and removed the application from the phone: on the KP (in
/ data / app ) this application remained, because it was copied when installing the script, therefore, after you return the KP to the phone, you need to delete it again, anyway, this application will no longer work normally, because his data from
/ data / data deleted by you (maybe you will see an error message until you uninstall this application again).
2. Reverse situation - When the KP is installed, you deleted the application installed before the script was applied: this application will remain in the phone’s memory (the folder in which it lies is “replaced” by the same folder from the KP), therefore, after removing the KP, it must be deleted again, by for the same reason as in
p.1 . (no data, there will be an error).
3. We removed the KP and installed the application on the phone (for example, from the Market): it is not on the KP and it will not appear there itself (copying occurs only once, when installing the script), therefore, after you return the KP to the phone, this application need to restore / reinstall if you need it. (You will not see any errors, because there is no application - there are no errors).
4. The reverse situation - with the installed KP, you installed the application: it is not in the phone’s memory, and if you want it to work after removing the KP, you need to install it in the phone’s memory (downloaded without the KP): do this from the Market or insert the KP on your telephone and you will have
.apk and / or backup (TitaniumBackup must already be installed in the phone’s memory, for example, I put it in
/ system / app along with Gscript), another installation option: use a script
mount.sh - he will mount the partition
ext2 in / system / sdcard then just copy
RootExplorer `oh the right apk from
/ system / sdcard / data / app at
/ data / app (check rights =
permissions and after rebooting it will work).
* “They ran out of KP” - it means: they turned off the bodies, took out the card, turned on the bodies. “Installed KP” - it means: they turned off the bodies, inserted the card, turned on the bodies, unless otherwise specified.
Problems that may occur during installation: If we see
"No such file or directory" - this suggests that the ext2 partition was not mounted and that it was necessary to double-check and recreate
ext2 (you can change the program for the breakdown, make the section the first, maybe just repeat this procedure, being more careful). Remember your gestures, after which the script is installed, and all subsequent installations, after XP or flashing, will pass without problems.
If used for stakingAcronisand nothing happens - you don’t have to torture him and yourself, put Paragon and smash the card with them. If after installing the script (any) the applications load slowly, change the KP to a faster one.
P.S. All of the above is my personal vision of what is happening, based on repeated experiments, and in no way claims to be an inexorable truth.
P.S.P.S In order to avoid repeating the questions, I insert here the answers to the questions already asked (although similar questions have already been asked and the answers are full, but ... as they say "to the heap" in one place:
What lies in the folders (in the "trailer"): AT
app2sd and
app2sd_data contains:
The above scripts and:
check.sh - Writes the size of available space for applications and checks if the script is installed.
umount_a2sd.sh - removes vold.sh, restores vold, so after rebooting nothing is mounted. Useful in cases where everything is "ripe", or you just want to reinstall the script, change it to another option, for example.
sdcard_clear.sh - mounts the ext2 partition and removes everything from it. Useful after umount_a2sd.sh, applicable in the above cases.
mount.sh - simply mounts the ext2 partition (if it booted without a CP, and then inserted the latter) Useful for cases when you need to look at the contents of both the phone and the CP at the same time (delete, copy).
AT
gscript lie:
vold and
vold.sh (or its clones: vold_data.sh, vold_data_DH.sh) - are copied when the script is installed on the phone, and later, when the phone is loaded, vold calls vold.sh, and
vold.sh , in turn, mounts (replaces) the necessary folders.
busybox also copied when installing the script, needed to create the necessary folders with the desired content.
How to remove all traces from app2sd: if you want to get rid of the script (from installing applications on the SD card) forever! hereandhereit was written. Quotes:
1.On the phone, go to the root explorer, and use the pens to delete / system / sdcard (the entire sdcard folder), / system / bin / vold2 and /system/etc/vold.sh
2. take out the flash drive, recreate ext2 on it, load the device (without a flash drive), climb into root explorer and soak it with vold.sh pensCorrections from
Binger :
1. Go to the Root Explorer and stomp in / system and there we completely delete the folder / system / sdcard;
2. Without leaving Root Explorer, go to / system / bin, find two files vold2 and vold there, delete (!) Vold and rename vold2 to vold;
3. While in Root Explorer, go to / system / etc and delete the file vold.sh there;
4. We leave Root Explorer, cut down the body, remove the gearbox, extinguish the ext2 partition (or re-create it - it depends on what you plan to do next), install the gearbox back into the phone and cut it;
The sequence of actions may vary, since, for example, with the inserted CP, the body may not boot
Creating an ext2 partition in Paragon Hard Disk Manager в„ў 2010 Professional [attachment = "696165: Paragon.JPG"]
Took from a rutracker
The modified script No. 3 with the output of error messages and the removal of dalvik-cache lieshere.