Related
I have partitioned sd card and I have the hello im apk on the sd and I want it on my phone because it wont let me change my buddy pic it says please make sure your sd card is in the phone so Im going to try to put it back on internal storage to see if it works. So how do I move it? I parted with apps2sd but the app wont work with cyan 4.0.1 so how Do I move it?
Apps2sd is really an all or nothing proposition. You can't have one app on internal memory and the rest on the SD card.
If you want to get rid of apps2sd altogether I can tell you how to move everything back.
OTOH, if an app is complaining about the sd card it's probably talking about the fat32 partition that it wants to store images on. Is your fat32 close to being full or something?
on a side note im on cyan 4.0.1 I was at 3.6.8.1 when I used the apps2d app and now when I try to open it it says Oops! Looks like you need to go through the tutorial to set up apps to sd. Please go to blah blah blah why is it doing this
what do I have to do to get this app running gain I already haves apps going to sd.
The top part of Cyanogen's stable thread says not to use any other method of apps to sd because his has a script built in.
So. Stop fiddling with whatever apps2sd app you have.
go to terminal and type:
Code:
su
ls /dev/block/mm*
Tell me what you see. (And please take a moment to make your posts a little more readable, I'm having a hard time deciphering what you're asking/saying. )
what Am I suppost to do? I dont want to do it without knowing
open the application 'terminal emulator' -- this is like the dos 'command prompt' in windows or a term window in Linux
type 'su' and press enter -- this Switches User to root, or the administrator of the machine (your phone)
type 'ls /dev/block/mm*' -- 'ls' is 'list' directories. /dev is where all the devices are, block is hard-drive like devices (your internal memory and the sd card) and mm* is every block device that starts with 'mm....' which should be mmcblk0 (the sdcard), mmcblk0p1 (the fat32 partition) and mmcblk0p2 (the ext partition)
If the last exists, the cyanogen automatic apps2sd will have already moved all your applications there. If only one exists, it means you either formatted the whole SD card to ext2 for apps2sd (and left nothing fat32) or formatted none of it and your apps are already on your phone.
if your 'ls /dev/block/mm*' says that you have a mmcblk0p2, than run "ls /system/sd/app/*" and you should see a bunch of files ending in .apk. If so, then you have to undo apps2sd to get the Hello IM app back to internal memory.
Report back on the outputs of the above and further instructions will be provided.
Ok Iv done all that so how do I undo them and if so how will I get them back?
Tell me what all that said back when you typed it in. THEN I can tell you what to do.
I see all my apk files now what? I want to move that 1 app onto the phone memory and every other apk on the sd. Im ready for the next step.
I see a bunch of files ending in .apk now what?
Hmm. I just looked up 'Hello IM!' and see that it's a paid app.
So, we can move just paid apps to the internal memory and leave the free ones on the sd card.
if yes run the following in terminal emulator:
su
rm /data/app-private
mkdir /data/app-private
cp /system/sd/app-private/* /data/app-private
Copying the apps may not work and you may have to uninstall/reinstall, but when you install them they'll be on the internal memory.
Oh, but cyanogenmod will put them back on the sd card when you reboot, so if having the app on the internal memory does fix the problem, you'll have to edit the a2sd script.
The problem isn't that your apps are on the sdcard. The app itself doesn't know. Your partions may be out of whack or the app itself may just need to be reinstalled.
When your apps are on the sdcard they are on a different partition then what every app uses your sdcard for. Not sure if I wrote that where you can comprehend it or not...
wat do u mean out of wack
PsychoI3oy said:
If you want to get rid of apps2sd altogether I can tell you how to move everything back.
Click to expand...
Click to collapse
I've done some searching, and haven't found any way to do this that has worked for me. Could you please pass some of this info along?
Thanks.
HowTo - un-apps2sd (on CyanogenMod)
Ok, this is based on the assumption that you are running a Cyanogen rom. I'm sure it could be adopted for use on another one, but Cyanogen 4.0.x is what I'm running. You'll probably have to re-install any paid apps (app-private) but normal apps should run fine after this.
Instructions for use with adb:
Code:
adb remount
adb push a2sd.txt /system/bin/a2sd
adb shell
# rm /data/app
# mkdir /data/app
# cp /system/sd/app/* /data/app/
# rm /data/app-private
# mkdir /data/app-private
# cp -r /system/sd/app-private/* /data/app-private
# reboot
for terminal emulator, assuming the new a2sd.txt is on your sdcard:
Code:
mount -o rw,remount /system
mount -o rw,remount /data
cp /sdcard/a2sd.txt /system/bin/a2sd
and then continue the adb instructions from after 'adb shell'
after reboot you can confirm that it worked by running:
ls -l /system
from terminal emulator (no need to remount/su) and you should see 'app' and 'app-private' as directories (and not app -> /system/sd/app).
If you're running some other a2sd method, you'll have to edit/remove the script that's doing the linking, then delete the symlinks and copy back (should be similar to above).
The modified a2sd.txt attached just takes away the apps-to-sd part. Dalvik-cache is still run from /system/sd/ as are whatever other magical juicy bits he's got in there.
If you upgrade to another Cyanogen rom, the new version of a2sd will get pushed and everything will be moved back. The only way to get rid of it permanently would be to delete the ext2/3/4 partition on your sd card.
If you decide you want apps2sd again and don't want to upgrade, just put the a2sd.orig.txt back as /system/bin/a2sd and reboot, it'll automagically move everything back to the /system/sd/app on your ext partition.
I just did the un-apps2sd then put the original back and everything's fine (and was fine with un-apps2sd).
That should cover most things....
Thank you so much for the step by step instructions.
One minor correction, maybe, shouldn't there be a '/' at the end of the second to last line?
Also, for me I didn't copy over the modified a2sd.txt file. After I copied everything to internal I shutdown the phone and deleted the ext partition. All seems to be working well!
Thanks again.
daveerickson said:
Thank you so much for the step by step instructions.
One minor correction, maybe, shouldn't there be a '/' at the end of the second to last line?
Also, for me I didn't copy over the modified a2sd.txt file. After I copied everything to internal I shutdown the phone and deleted the ext partition. All seems to be working well!
Thanks again.
Click to expand...
Click to collapse
Trailing slashes are optional in most shells, including this one.
Glad it worked for you.
these doesn't seem to be working for 4.2.1, no a2sd file exists in /system/bin, maybe he moved it somewhere else, i'm trying to find it but i'm not being lucky.
any help?
No, he broke up the bits that were in a2sd and spread them across several files in /system/etc/init.d/
http://wiki.cyanogenmod.com/index.php/Removing_Apps2SD has the instructions now.
Introducing...
Darktremor Apps2SD 2.7.5.3 Beta 04
Date of Release: January 29, 2011
Download Current Version
Instructions - Change Log - Commands - ROM List - Developer's Guide
Darktremor Apps2SD Fan Page ----
Darktremor Apps2SD Development Group
Are you installing Darktremor Apps2SD on your phone? Here are the instructions to help you: Facebook
Are you a developer wanting to include Darktremor Apps2SD in your latest ROM? Here is the Developer Guide: Facebook
Click to expand...
Click to collapse
Update on Beta 4
It seems I'm getting mixed results with these betas. I'm not sure why this is occurring, some people have been able to get this working right while others have had a hard time with it.
Currently, I'm rebuilding the entire program. This takes a while because I have to figure out how to pack all these options into the program but make it small enough to where it will run correctly.
I will say that some of the beta features are coming back out...one of them is the search for a partition code. I suspect that code may be leading me into issues with certain platforms, so I'm going back to the 2.7.5.2 method of mounting (mmcblk0p2 or mmcblk1p2).
Also, parts of the code will use Busybox Ash (the only code that won't will be starta2sd, which will still use Bash for the time being). The startup code will definitely use Busybox Ash.
Until then, here are the links to the the last two betas and the last official release:
Version 2.7.5.3 Beta 04 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.3-beta04-signed.zip
Version 2.7.5.3 Beta 03 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.3-beta03-signed.zip
Version 2.7.5.2-1 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.2-1-signed.zip
And, if you want past versions, you can view the repository: ftp://dtuser:[email protected] (ignore the smiley face...that's XDA doing that.)
Click to expand...
Click to collapse
Beta 04 took longer than I expected to release. I have done major changes to the code:
1. New commands: convert-ext4 - This will convert your EXT3 partition into EXT4. Just a friendly reminder on this command: Not every rom supports EXT4, so it is possible to go into a boot loop if you switch roms. Use with caution.
2. Reworked convert-ext3 (convert-ext4 gets similar code)...now a flag file is set before the reboot (no conversion is done before the reboot). At load time, the conversion is performed. This takes longer in the reboot process and you may think your phone has locked up...wait about five minutes before doing anything with the phone.
3. Repair is rebuilt...now it uses existing commands to repair the setup (reinstall, remove, cachesd, cachepart, nocache, datasd, nodata). Definitely shrinks the code.
4. Added fix_permissions program to the package. This may help with Superuser issues when using the datasd feature. It is used in reinstall, remove, datasd and nodata.
5. a2sd install is back!!! Both a2sd install and a2sd reinstall do the exact same thing.
6. Dalvik heap code has been shrunk and now creates a file called dalvikheap. Actually, the code has been doing this all along (since about 2.7.5.2, I think), but I never put the code in to use the file.
7. Low Memory Killer code has also been shrunk and uses a file caled dtset_lowmem to set the low memory killer parameter.
8. Replaced Busybox PS function with Toolbox PS. The issue with Busybox PS is that it gives a false reading when I look for android.process.acore (which is the main program when the GUI starts up). If that is present, the program thinks you are trying to run Darktremor without any command line parameters. This was because Busybox would report the process was there when, in reality, it wasn't (validated this when my phone was boot looping.) Toolbox's PS reports the correct setting. This should fix the bootlooping issues some people are experiencing.
9. New commands: usedtbusybox and usedefaultbusybox - these commands may help in diagnosing issues that is may be related to the native Busybox on your rom. a2sd usedtbusybox will use the Busybox that is packaged with Darktremor. a2sd usedefaultbusybox will turn back on the scan behavior of the program introduced in Beta 03.
10. Support for Darktremor Apps2SD version 2.7 and earlier has been discontinued. To upgrade correctly from one of those versions, use version 2.7.5.3 Beta 03b or earlier.
11. Finally fixed stalled boot issues (or at least my tests with several roms says so.)
See the change log for additional details.
You will notice that if the program runs repair and finds a problem, it will correct the issue and reboot. You will see a second reboot when the dalvik-cache clears (this is to fix timing issues with CyanogenMod...I can't control that startup as well as I can other roms). This only happens if repair is ran or you flash a new rom (as repair will realign all data). If you are upgrading from a previous version of Darktremor, you should not see the reboots.
Click to expand...
Click to collapse
This is Darktremor Apps2SD, a multipurpose program that primarily allows a user to execute applications created for the Android OS on their Secure Digital card (with the proper setup...more on that later). But, Darktremor Apps2SD is all about stability. The goal is to be able for all users of the Android OS to be able to take advantage of a method to run their applications from a secure digital card.
But just because the Darktremor Apps2SD is all about stability, doesn't mean it isn't packed with features:
- Move applications (both free and paid) to the Secure Digital card.
- Move Dalvik Cache to run either from your Secure Digital card or from your cache partition and clears the cache on demand.
- Boot Loop Protection: prevents the phone from boot looping in the event the SD card could not be mounted.
- Dalvik JIT for faster performance on Roms which support it.
- User selectable sizes for the Dalvik heap sizes, allowing a user to freely optimize their system.
- Activate a swap partition on your SD card and sets how often the swap partition is utilized.
- Automatically fixes configuration issues.
- Users can check the free space on their SD card and check the installation to make sure all is setup correctly.
- Runs ZipAlign on demand...this makes your programs load faster.
- Built in help system for easy reference of commands.
- All features can also be reversed without repartitioning your Secure Digital card.
- New logging features assists in troubleshooting issues.
- Commands to set the Low Memory Killer feature at boot time. Great for those people who are the "set it and forget it" type.
- And more...
Darktremor Apps2SD is not the same as Froyo Apps2SD. Froyo Apps2SD creates a secure folder on the FAT32 section of your SD card (this is the section that you see when you mount your phone to your computer) and stores the programs there. This is nice as you don't have to do anything special with the phone, but it isn't backwards compatible with older versions of Android (Cupcake, Donut, Eclair) and, because of the way Froyo works, older programs not designed for Froyo will automatically stay on your internal storage (unless you install a program that forces the move to your SD card).
Darktremor Apps2SD takes a different approach. Based on the original CyanogenMod works, Darktremor Apps2SD uses symbolic linking to force Android into moving your applications to the SD card. Because Android will not allow anything to be ran from the FAT32 partition on your SD card (and, in Froyo, it will only allow you to run programs from a special folder), Darktremor utilizes filesystems called EXT2, EXT3 and EXT4. Each one of these filesystems is native to Linux (the operating system running Android), which allows you to run programs from them (same as, say, a computer running Ubuntu). This method is completely compatible with all versions of Android, including Froyo. In fact, you can run both the Darktremor Apps2SD and Froyo Apps2SD at the same time.
Check out the list of Roms that either have Darktremor Apps2SD installed or are compatible with Darktremor Apps2SD. Click on the link labeled ROM List at the top of this message.
Reserved...created because a Tattoo rom has it as part of its build.
I just tried to flash Apps2SD 2.7.5 RC1, but installation fails:
------------------------------------------------
E: Failure at line 48:
set_perm 0 0 0777 SYSTEM:xbin/a2sd
Installation aborted.
-----------------------------------------------
Is there something that I can do?
I love this script. I think I'm going to be using it in the next version of my ROM. Thanks for making it, it's great
It shouldn't do that.
Try the RC3 (about to release it): http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5-rc3-signed.zip
If that doesn't work, let me know and we go from there. There's a recovery log file that is created...I just have to remember where it is at (was looking at it just this morning).
dancer_69 said:
I just tried to flash Apps2SD 2.7.5 RC1, but installation fails:
------------------------------------------------
E: Failure at line 48:
set_perm 0 0 0777 SYSTEM:xbin/a2sd
Installation aborted.
-----------------------------------------------
Is there something that I can do?
Click to expand...
Click to collapse
alredy running rc3 in our rom hehe
Which rom is that?
danne_jo said:
alredy running rc3 in our rom hehe
Click to expand...
Click to collapse
PuzzleROM
Sent from my Tattoo using XDA App
tkirton said:
Which rom is that?
Click to expand...
Click to collapse
As said before, PuzzleROM
http://forum.xda-developers.com/showthread.php?t=749932&page=10
I saw that during my sweeps of the forums...added into my list.
danne_jo said:
As said before, PuzzleROM
http://forum.xda-developers.com/showthread.php?t=749932&page=10
Click to expand...
Click to collapse
i have installed your APPS2SD on a Tattoo with a shipped non modified rom (I rooted my phone and have ARMON 1.6 recovery though) fine however after the reboot I didn't notice any difference so i checked the with apps2sd check command. here is the output
# a2sd check
a2sd check
[ ] Apps2SD is launching...
[ ] Starting Apps2SD Check Program.
[ ] Searching for Mount Point...
[Ô£ö] Mount point /data/sd located.
[ ] Checking for ext partition
[Ô£û] Ext partition found, but not mounted.
Your rom may not be setup to run Apps2SD.
Check with your rom developer if the boot image
is programmed to run Apps2SD.
Your partition may be using an EXT4 partition,
but your rom may not support EXT4. Repartition
your SD card to use EXT2 or EXT3.
please note i have formatted my sd and have done a ext2->ext3 already.
what should i do now ?
pardol said:
i have installed your APPS2SD on a Tattoo with a shipped non modified rom (I rooted my phone and have ARMON 1.6 recovery though) fine however after the reboot I didn't notice any difference so i checked the with apps2sd check command. here is the output
# a2sd check
a2sd check
[ ] Apps2SD is launching...
[ ] Starting Apps2SD Check Program.
[ ] Searching for Mount Point...
[Ô£ö] Mount point /data/sd located.
[ ] Checking for ext partition
[Ô£û] Ext partition found, but not mounted.
Your rom may not be setup to run Apps2SD.
Check with your rom developer if the boot image
is programmed to run Apps2SD.
Your partition may be using an EXT4 partition,
but your rom may not support EXT4. Repartition
your SD card to use EXT2 or EXT3.
please note i have formatted my sd and have done a ext2->ext3 already.
what should i do now ?
Click to expand...
Click to collapse
Stock ROM doesn't support A2SD as it has no means to execute the script.
Try HCDR.ROM or PuzzleROM
Ahh. Makes more sense now.
Sent from my HTC Tattoo using XDA App
pardol said:
Ahh. Makes more sense now.
Sent from my HTC Tattoo using XDA App
Click to expand...
Click to collapse
Further to your last message i have accidentally found this link where it shows how to move the apps to /system/sd and then all should work.
i have not done anything as such because i am not too familiar with shell scripting and want to avoid to brick the phone.
I know you said APPS2SD does not work with stock roms (not sure why but you are the master here :> ). can this help or there is no way to get it to work ?
actually i noted i am missing a kin d of pre-requisite to complete the script: there is no system/sd entry when using this command so i guess no hope
busybox df -h
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 93.0M 0 93.0M 0% /dev
tmpfs 4.0M 0 4.0M 0% /sqlite_stmt_journals
/dev/block/mtdblock3 150.0M 139.9M 10.1M 93% /system
/dev/block/mtdblock5 165.1M 142.1M 23.0M 86% /data
/dev/block/mtdblock4 150.0M 3.1M 146.9M 2% /cache
/dev/block//vold/179:1
5.8G 1.8G 4.0G 31% /sdcard
It doesn't work with Stock roms because there's no command in init.rc to launch Apps2SD (which is part of the boot.img). Now, you can modify the boot.img (or get an already modified boot.img) to add support. It will retain the stock rom feel but has a modified boot image.
pardol said:
Further to your last message i have accidentally found this link where it shows how to move the apps to /system/sd and then all should work.
i have not done anything as such because i am not too familiar with shell scripting and want to avoid to brick the phone.
I know you said APPS2SD does not work with stock roms (not sure why but you are the master here :> ). can this help or there is no way to get it to work ?
Click to expand...
Click to collapse
That is because the EXT partition isn't mounted, so Linux (the OS behind Android) doesn't see an EXT partition on the SD card (needs a mount command to be executed, which Apps2SD does, but the rom doesn't launch the program).
pardol said:
actually i noted i am missing a kin d of pre-requisite to complete the script: there is no system/sd entry when using this command so i guess no hope
busybox df -h
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 93.0M 0 93.0M 0% /dev
tmpfs 4.0M 0 4.0M 0% /sqlite_stmt_journals
/dev/block/mtdblock3 150.0M 139.9M 10.1M 93% /system
/dev/block/mtdblock5 165.1M 142.1M 23.0M 86% /data
/dev/block/mtdblock4 150.0M 3.1M 146.9M 2% /cache
/dev/block//vold/179:1
5.8G 1.8G 4.0G 31% /sdcard
Click to expand...
Click to collapse
i have the same problem and in order to run A2SD i have to mount the EXT3 Partition manually ; anyone knows how to auto mount the ext3 partition at system startup ?!!
ok. i have been able to install a2sd correctly and have it running since a ferw weeks now. The only flipside is i need a PC to be able to reboot the phone since the Ext3 partition does not start.
Is there a command i can put in the init.rc file to autorun a2sd in place of doing a
adb shell a2sd
every time i reboot the phone ?
Hi, how about if after start up , manually mount the ext3 partition and manually run apps2sd app ? As I rarely reboot the system so I think this can be an alternative solution. but could someone let me know the command ? thx
I'm really surprised that there is no documentation on this thing that I can understand. I'm having major issues with CM7 with DT A2SD. Every one of my widgets is broken. I can't tell what's installed to EXT and what's not. If I go into Manage Applications, all of the widget apps are installed to phone. I have next to zero internal space left.
I need to know how I can differentiate what's on internal, what's on Froyo SD, and what's on DT A2SD - As well as how to move them and tell where each app is going.
i honestly wish i knew. this is on my list to do, but i didnt feel like formatting my memory card cause there's so much on it, so i am just hoping gingerbread improved method will give me enough space.
i wish there was a tutorial or wiki for DT A2SD. you prob should just read that whole thread and it is explained there somewhere.
Some quick commands executed from adb shell or even the terminal on the phone can give you some more information:
a2sd check will give you basic diagnostic information from the DT a2sd script - this will reveal what is running where (apps on /sd-ext, data location, etc).
ls -al /data will help you understand what a2sd actually does for you. If a2sd is set up correctly, you should see an entry similar to "app --> /sd-ext/app", which indicates your /data/app directory is symbolically-linked to your /sd-ext partition (the ext-formatted partition on your SD card). This makes Android see /sd-ext/app and /data/app as the exact same thing, and everything within that folder will actually reside on the /sd-ext partition. The same thing applies to the dalvik-cache.
You can find out more about using a2sd via the a2sd help command, which shows an easy-to-understand listing of the various a2sd commands available.
All the documentation is in DarkTremor's thread.
There is no choosing in A2SD. If it's installed - all apps that are shown as "internal" go to EXT partition. But the phone doesn't know it, and you won't see it in OS visually in any place.
You can choose if you're sending your app data and your Dalvik-cache to SD also, that you can do from the Terminal (command line).
I should probably mention that all apps that are installed to SD using stock Froyo method, remain there - and cause a waste of space. So using A2SD you should move ALL your apps to "internal memory" (substituted with EXT partition).
This is a handy link for Darktremor users...
http://www.facebook.com/note.php?note_id=158826790833326
Sent from my Nexus One using XDA App
Hmm.. maybe I should had included some more info.
If I use Root Explorer and check my sd-ext folder, it does have apps within, and from install date I can tell they're from my CM7 install (plus I wiped everything including SD-EXT before flashing anyway). The problem is that some of these apps are things I do NOT want on SD-FAT or SD-EXT, I need them on internal (basically anything that I use with widgets, and LauncherPro). Pretty sure having widgets on EXT is what's causing my home screens to **** the bed.
Checked Install Location, right now that's set to Automatic.
If I go to Manage Applications, these apps appear to be on internal (Move to SD card is available on the button). I've read the FB page and original thread, I still see no way to differentiate between Internal, SD-FAT and SD-EXT - or how to move them between with certainty.
/sd-ext is the same as internal for all intents and purposes. You don't choose what apps to run off of /sd-ext, they all do. This is not causing your widget issues.
If you use DT a2sd, "Internal" becomes synonymous with "sd-ext". They are one and the same.
You SHOULD, however, move all of your apps off of SD-FAT - that is the implementation of "apps to sd" that breaks widgets.
Ok, I moved all of my apps off of SD-FAT and back to internal.. seems to be going well so far. The only thing I'm curious about now is that I didn't really get any space back, I still only have 21MB free (cleared browser and market cache as well). I've obviously messed something up somewhere along the line. Any ideas? I'm such a n00b at this apparently.
I really appreciate the help thus far guys!
You shouldn't have. Your space doesn't change as a result of moving apps to SD and back anymore - because they're all either on EXT, or partially on EXT and partially on FAT32.
If you don't have enough space left on internal memory - which can happen, if you have a lot of apps and they use a lot of data - you can move app data to SD and also Dalvik-cache to SD. This is done using command line commands.
One of those is usually enough.
I prefer the Dalvik-cache on SD - it might be a bit slower (never noticed that), but at least system settings (that are stored in /data/data) remain on the phone's internal memory and aren't prone to corruption.
Jack_R1 said:
You shouldn't have. Your space doesn't change as a result of moving apps to SD and back anymore - because they're all either on EXT, or partially on EXT and partially on FAT32.
If you don't have enough space left on internal memory - which can happen, if you have a lot of apps and they use a lot of data - you can move app data to SD and also Dalvik-cache to SD. This is done using command line commands.
One of those is usually enough.
I prefer the Dalvik-cache on SD - it might be a bit slower (never noticed that), but at least system settings (that are stored in /data/data) remain on the phone's internal memory and aren't prone to corruption.
Click to expand...
Click to collapse
On that note, moving the dalvik-cache is generally a better idea than moving /data/data. Better stability and compatibility and whatnot. Only bother with moving /data/data if you really really need the space.
You can move the dalvik-cache to sd with the a2sd cachesd command in either the terminal or adb shell.
OH MAN THANK YOU! Moved dalvik to SD-EXT and that did it! 120MB free! Time for a downloading spree!
level5music said:
OH MAN THANK YOU! Moved dalvik to SD-EXT and that did it! 120MB free! Time for a downloading spree!
Click to expand...
Click to collapse
Glad to help
CM7 can make you install apps on the sd card, how does it differ from app2sd or app2ext? i have been trying to decide if i should partition my new sd card or its not necessary. There must be an advantage to have app2ext right?
Thank you.
CM7 basically allows you to move all applications using Froyo's app2sd mode. Even ones that have disabled it (like live wallpapers and widgets as those won't work when installed that way).
app2sdext works differently as it will install apps directly to an ext partition on your sdcard (that you manually have to set up). This functionality is NOT build into CyanogenMod, but is easily added with a number of different apps/scripts. This will give you a lot more free space on your phone, and all apps can be installed there regardless of whether they have widgets or have services running. Most app2sdext options will also give you the option of moving the dalvik cache to the sdcard which will save you a substantial amount of space on your internal memory.
Basically, if you want a lot of memory intensive apps, your only decent option with a Nexus One is an app2sdext solution. (I have it with a 1GB partition, and I will soon either need to resize it or delete apps... adding app2sdext was the second best thing I ever did to my phone behind installing CyanogenMod on it.)
bassmadrigal said:
CM7 basically allows you to move all applications using Froyo's app2sd mode. Even ones that have disabled it (like live wallpapers and widgets as those won't work when installed that way).
app2sdext works differently as it will install apps directly to an ext partition on your sdcard (that you manually have to set up). This functionality is NOT build into CyanogenMod, but is easily added with a number of different apps/scripts. This will give you a lot more free space on your phone, and all apps can be installed there regardless of whether they have widgets or have services running. Most app2sdext options will also give you the option of moving the dalvik cache to the sdcard which will save you a substantial amount of space on your internal memory.
Basically, if you want a lot of memory intensive apps, your only decent option with a Nexus One is an app2sdext solution. (I have it with a 1GB partition, and I will soon either need to resize it or delete apps... adding app2sdext was the second best thing I ever did to my phone behind installing CyanogenMod on it.)
Click to expand...
Click to collapse
why didnt i think of that? thank you for your reply... now i should decide whether to do it now or wait till i have reached maybe about a hundred apps. by the way does it have any effect on the speed of the phone if you do that?
I am on cm7 and decided to put cache apps on sd card using ta utility is there any other new apps like that? ta
Can you do this with rooted stock?
lolobabes said:
why didnt i think of that? thank you for your reply... now i should decide whether to do it now or wait till i have reached maybe about a hundred apps. by the way does it have any effect on the speed of the phone if you do that?
I am on cm7 and decided to put cache apps on sd card using ta utility is there any other new apps like that? ta
Click to expand...
Click to collapse
I have a class 4 32GB card, and I didn't notice any appreciable difference in speed. I have moved my apps and dalvik cache to the sdcard using DarkTremor's a2sd. I currently have 260 apps installed on my phone, and that is pushing the internal phone space and the 1GB partition I set up for ext. I am about to bug danger-rat for his instructions on how he resized his internal partitions to give the data residing on the phone more space (I will basically shrink the cache partition and I am looking at resizing my ext partition to 1.5GB or 2GB.
I couldn't live without this anymore. I don't know how I went so long without it. It is so nice to just browse the online market and click install on countless apps without worrying about your space.
If you want to try and move the app data (resides in /data/data) to the sdcard, I have heard that it is recommended to have a class 10 card to keep up with speed requirements. I am not sure how many apps support that.
brettbellaire said:
Can you do this with rooted stock?
Click to expand...
Click to collapse
I believe you can. You would have to have a custom recovery. The main thing I am not sure is if it will mount the ext partition. If you have a custom recovery, do a nandroid backup (just in case it doesn't work), flash the zip for DarkTremor, and reboot the phone (the first boot will take longer).
brettbellaire said:
Can you do this with rooted stock?
Click to expand...
Click to collapse
yes you can.
bassmadrigal said:
I have a class 4 32GB card, and I didn't notice any appreciable difference in speed. I have moved my apps and dalvik cache to the sdcard using DarkTremor's a2sd. I currently have 260 apps installed on my phone, and that is pushing the internal phone space and the 1GB partition I set up for ext. I am about to bug danger-rat for his instructions on how he resized his internal partitions to give the data residing on the phone more space (I will basically shrink the cache partition and I am looking at resizing my ext partition to 1.5GB or 2GB.
I couldn't live without this anymore. I don't know how I went so long without it. It is so nice to just browse the online market and click install on countless apps without worrying about your space.
If you want to try and move the app data (resides in /data/data) to the sdcard, I have heard that it is recommended to have a class 10 card to keep up with speed requirements. I am not sure how many apps support that.
I believe you can. You would have to have a custom recovery. The main thing I am not sure is if it will mount the ext partition. If you have a custom recovery, do a nandroid backup (just in case it doesn't work), flash the zip for DarkTremor, and reboot the phone (the first boot will take longer).
Click to expand...
Click to collapse
thanks for the reply i think i read on darktremors post class 4 will do for the data2sd. I have class 4 16GB sd card would 1GB good for the ext? ty
It really depends on how much you think you will be installing. I did a 1GB partition on mine, but now that I install most of the Amazon free daily apps, that space is dwindling quickly. I have programs that will resize the partition for me, but most will have to wipe the card and partition it manually. I do have the install location set to automatic, so it allows developers to specify whether they want it in the "internal" (really it is on the sdext partition, but to the phone it is internal) or external using the froyo method. The Angry Bird apps all default to install on the sdcard, so my installed app base is even larger than 1GB.
bassmadrigal said:
... adding app2sdext was the second best thing I ever did to my phone behind installing CyanogenMod on it.)
Click to expand...
Click to collapse
I second this
Sent from my Nexus One using XDA App
is it true that cwm sets the partition to ext3 by default? unlike in ra recovery where you still need to convert it? ta
I have heard that it creates it in ext3, but right now, DTa2sd is showing that it is a ext2 partition. I can't figure out how to find out for sure while the card is in the phone. Either way, it is getting mounted as an ext2 partition.
temasek said:
I thought CWM will create ext3 by default? Your steps are ok, np.
Anyway when u read the ext partition type in android, most likely u will see ext2 if u are using official DT script cuz of the auto syntax it uses.
Click to expand...
Click to collapse
then it maybe so, this was posted on the darktremor thread
http://forum.xda-developers.com/showthread.php?p=14134665#post14134665
Well, whether or not it is formatted as an ext3 partition, Android is still mounting mine as an ext2 partition.
Code:
mount | grep ext
NOTE: the "|" is called a pipe. On the keyboard it is the shift option on the backslash key "\". I don't know exactly where it is on the stock keyboard, but on swype it is located under the "D" key when the keyboard has the shift key pressed and you access it by longpressing.
To get your sdcard to ext3, you just need to turn on journaling. You can do this through adb while in the recovery (because you need the partition unmounted to do this).
Code:
adb reboot recovery
adb shell
mount system
e2fsk /dev/block/mmcblk0p2
tune2fs -j /dev/block/mmcblk0p2
reboot
Supposedly Android should auto-mount this as ext3 on boot (which you can check with the first command). At that point, I don't think it will matter what a2sd shows. As the writing of the journal (the big thing with ext3, since it helps minimize write errors on a bad shutdown) is done at the OS level, not the a2sd level.
I know it was discussed a lot, but since things are constantly being updated i can't get a hold of what is working at the moment. I will be brief.
16 GB SD card, First partition is primary 14 GB FAT32, second partition is ext3 1 GB.
I am using Cyanogenmod 7 7.2.0 RC1 on Motorola Milestone. I also have androidiani open recovery and kabaldan's mmcfix module installed.
After the partitioning was complete (in card reader) i returned the SD card in the phone and booted to open recovery where I formated all caches and factory restored CM7 everything is clean.
Questions:
1. When I launch File Explorer (the one within the rom) SD-EXT on root is empty, no folders or anything, but if I launch terminal emulator and cd sd-ext then ls there they are. Why?
2. I play couple of memory intensive games (like Dead Space and GTA3), but since I have only 256 mb ram they often crash (without error) when loading a level or saved game (yes I have chainfire3D). Will moving dalvik cache and cache to sd-ext help free more ram so I can crash less?
3. What is the point of moving dalvik and cache to sd-ext and where can I find a guide how to do it?
Thanks.
CeBits said:
I know it was discussed a lot, but since things are constantly being updated i can't get a hold of what is working at the moment. I will be brief.
16 GB SD card, First partition is primary 14 GB FAT32, second partition is ext3 1 GB.
I am using Cyanogenmod 7 7.2.0 RC1 on Motorola Milestone. I also have androidiani open recovery and kabaldan's mmcfix module installed.
After the partitioning was complete (in card reader) i returned the SD card in the phone and booted to open recovery where I formated all caches and factory restored CM7 everything is clean.
Questions:
1. When I launch File Explorer (the one within the rom) SD-EXT on root is empty, no folders or anything, but if I launch terminal emulator and cd sd-ext then ls there they are. Why?
2. I play couple of memory intensive games (like Dead Space and GTA3), but since I have only 256 mb ram they often crash (without error) when loading a level or saved game (yes I have chainfire3D). Will moving dalvik cache and cache to sd-ext help free more ram so I can crash less?
3. What is the point of moving dalvik and cache to sd-ext and where can I find a guide how to do it?
Thanks.
Click to expand...
Click to collapse
1) The File Manager bundled with CM7 doesn't have ROOT access, which is required to read the files on /sd-ext. Try using Root Explorer, for example.
2) No, it won't. What will probably help you is to disable JIT (gives you more free RAM), install V6 Supercharger by zeppelinrox (reorganizes how RAM is used) and remove ChainFire3D (it only helps if you reduce the texture quality to 16-bits, otherwise it's just one more layer between your apps and the GPU).
3) The point of using sd-ext is to overcome the storage limitations of the Milestone (not its RAM limitations), allowing you to install more apps without using app2sd (which renders apps on the SD unusable when you plug the device to a computer).
I hope it helps (=
Disabling surface dithering also helps.
I tried 7.2.0-RC2 without V6 and it works great, plus no more side effects, like Maps "forgetting" pre-cached areas =D
Hi. I followed pontomedon's guide to partition my 8GB card with OpenRecovery (parted & tune2fs). So I got 1 GB ext3. And installed CyanogenMod 7.2.2.
But in the CM Settings "Use internal storage" is grayed out and says "This device doesn't have expanded internal storage". Has something gone wrong? What's the best way to confirm that SD ext is working?
If ext would work, would the phone's memory still be used fully first, and SD ext only after that, or how does it go? I've now set Install location to "Internal".
I've heard of S2E (simple2ext) app, maybe I'll try it next.
mantokoski7 said:
What's the best way to confirm that SD ext is working?
If ext would work, would the phone's memory still be used fully first, and SD ext only after that, or how does it go? I've now set Install location to "Internal".
I've heard of S2E (simple2ext) app, maybe I'll try it next.
Click to expand...
Click to collapse
Your storage as in FAT partition on sdcard is working?
You can "mount | grep sd-ext" and "df /sd-ext" to check if sd-ext is mounted and how much space it has.
sd-ext is treated as internal memory. All user installed apps are moved to ext partition. Internal storage (data) is used for app data (configuration, etc.)
Thanks. Why does it show it as ext4. 8% is used... I guess it's working after all. Now let's install some games!
/dev/block/mmcblk0p2 on /sd-ext type ext4 (rw,noatime,nodiratime,barrier=1,data=ordered)
Filesystem /dev/block/mmcblk0p2 1K-blocks 936666 Used 70298 Available 816397 Use% 8% Mounted on /sd-ext
I installed Root Browser Lite and it shows the installed apps in sd-ext, also Dalvik-cache for those apps is there, which is good I think.
how to format?
mantokoski7 said:
I installed Root Browser Lite and it shows the installed apps in sd-ext, also Dalvik-cache for those apps is there, which is good I think.
Click to expand...
Click to collapse
Hi, my question is very close to this topic : when I try to install another rom I got all the old applications coming from the previous install. Is there a way to format the ext 2 in the same time we update or change CM?
Thx
Use -FuFu-'s MiniMod Recovery - it has an extended wipe menu, including ext-wipe.
http://forum.xda-developers.com/showthread.php?t=1091787
Eiertschik said:
Use -FuFu-'s MiniMod Recovery - it has an extended wipe menu, including ext-wipe.
http://forum.xda-developers.com/showthread.php?t=1091787
Click to expand...
Click to collapse
I'm using 2ndBootOR . What is the differcnce between them?
bibile said:
I'm using 2ndBootOR . What is the differcnce between them?
Click to expand...
Click to collapse
With 2ndbootOR you can use "wipe_ext2.sh" from MiniMod by -FuFu, or any other script. Just copy file to "scripts" folder.
FuFu's latest OR is based on the 2ndbootOR, so it does everything the 2ndbootOR does, but it also has additional scripts. So it really worth a try.
Thx I'll update my second phone (I have not seen these answers before)
Sent from my U8860 using xda app-developers app