Related
I start using a second partition for my apps and some of the caches...
But is there more? Yes there is (i hope). But what else? Any ideas, more is better...
What do you need:
A FAT32 / EXT2 partition combo on your CLASS 6 MicroSD (the EXT2 from 100mb to 1,5gb as max recommend (real max = 2gb)!
Only at "others" there is one way to move cache without EXT2 partition.
Do it yourself:
(Private) Apps to SD: http://forum.xda-developers.com/showthread.php?t=462882 (Apply on your own Rooted System)
Complete ROM:
(Private) Apps to SD: http://forum.xda-developers.com/showthread.php?t=480582 (modded JF1.42 RC33)
Other:
- Apps Caches (no ext2 needed): http://forum.xda-developers.com/showthread.php?t=471653 and http://androidcommunity.com/forums/f28/updated-move-caches-to-sd-card-11167/
- Apps Caches (with ext2): Change the paths from: "/sdcard/cache" to "/system/sd/cache" from http://androidcommunity.com/forums/f28/updated-move-caches-to-sd-card-11167/
I will add everything that's relevant to putting stuff from your ROM to your FLASH!
i hope we can move everything to the sd lol ;P
Theoretically it is but i think it will be to damn slow But if we put the core and much used stuff on system (something like vista does it with mem, preload stuff i use alot to my system and stuff i don't use a lot to my sd or somthing... But i don't have skills to do something like that (i suck with linux :S).
Yeah, it's possible. But as you said, the issue would be with the speed of everything... I know some basic Linux, but not to move the entire OS to the SD, otherwise I'd try it myself, and test the speed of it.
Phromik said:
Yeah, it's possible. But as you said, the issue would be with the speed of everything... I know some basic Linux, but not to move the entire OS to the SD, otherwise I'd try it myself, and test the speed of it.
Click to expand...
Click to collapse
the most i have tried is i moved the entire /data folder over to the EXT2 partition and then mounted the SD to /data .. so when you pull up available space it says 1G+ available on the phone for apps .. actually pretty kool but i can't get the SD to mount to /data on the phone boot and the slowness is definitely a factor .. anyone who wants to try for themselves is welcome .. but i can't speak for any errors you might get
LucidREM said:
the most i have tried is i moved the entire /data folder over to the EXT2 partition and then mounted the SD to /data .. so when you pull up available space it says 1G+ available on the phone for apps .. actually pretty kool but i can't get the SD to mount to /data on the phone boot and the slowness is definitely a factor .. anyone who wants to try for themselves is welcome .. but i can't speak for any errors you might get
Click to expand...
Click to collapse
how do you do it that it shows in storage available that u have 1G+ available space. i would want that to show for me.
Smokuevo said:
how do you do it that it shows in storage available that u have 1G+ available space. i would want that to show for me.
Click to expand...
Click to collapse
in my script i put in my modified JFv1.42 you can do:
#copy.sh all
this moves everything to the SD (the ultimate in G1 lag) and then from Terminal again:
#mount /dev/mmcblk0p2 /data
this should work (unless i forgot a step) .. then when you look at the available space you should see the entire EXT2 partition listed for the phone .. to get my script you can either flash my modified update.zip that has the modified init.rc and mountd.conf or else just copy my script to your phone
what if i already did copy.sh data copy.sh app .. will copy.sh all mess anything up?
whats the reverse step
Well the first stap is backing up ofcourse! So the only step if you screw up is putting the backup back...
back up didnt work. got to try cupcake though. haha.
now getting stale nfs files
Smokuevo said:
what if i already did copy.sh data copy.sh app .. will copy.sh all mess anything up?
whats the reverse step
Click to expand...
Click to collapse
i did put in "copy.sh undoall" to reverse the steps .. but this will also move apps and if you have too many apps if could crash the phone .. i may need to remove apps from the undoall process
after i did the command to make the room on my SD show up as my memory how do i revert that back to normal to see the space on my phones internal mem?
Smokuevo said:
back up didnt work. got to try cupcake though. haha.
now getting stale nfs files
Click to expand...
Click to collapse
on a linux distribution type :
fsck.ext2 -p [your partition] mine is /dev/sdd2 for example
Good news for those who have disabled security on their HTC Desire.
Having tried Firerat's Custom MTD patch on my HTC Desire and almost bricking it twice, I decided to break it apart and examine things in more detail.
As it currently stands v1.5.3 of his patch will corrupt your mtd0 partition if applied to your desire, so do not try it!
I read through lbcoder's custom partitions layout thread, then broke apart Firerat's patch to determine what it was doing, and what was going wrong on the HTC Desire.
The result, I have modified Firerat's Custom MTD script so it works on the HTC Desire and have successfully modified the partitions on my phone so system is 125MB, cache is 5MB, and data is 317MB.
Now after moving all my apps & dalvik-cache from SD-EXT back to DATA I still have 130MB free! w00t!
I will be providing minimal support for this, I am purely providing this to allow others to modify their partition table just as I have done. Ensure you read Firerat's original thread for further information and/or troubleshooting, it's 99% his patch/work, I just made a small change to stop mtd0 from being overwritten.
These are the steps I performed on my phone and are based on ClockworkMod Recovery v2.5.0.7.
If none of this makes sense to you then this is not for you:
Disable security on your phone. (S-OFF in FASTBOOT)
Place bravo-recovery-v1.5.3-CustomMTD.zip & bravo-boot-v1.5.3-CustomMTD.zip on SD card
Reboot into recovery
Take a Nandroid backup
Create mtdpartmap.txt on SD card with size of system & cache, the example provided sets system to 125MB and cache to 5MB, this will depend on your ROM: echo "mtd 125 5" > /sdcard/mtdpartmap.txt
Format system, data, and cache (found under mounts and storage)
Flash bravo-recovery-v1.5.3-CustomMTD.zip, this patches recovery to use the new partition sizes
Reboot into recovery
Format system, data, and cache again for good measure (found under mounts and storage)
Flash ROM, or restore Nandroid backup, it will be flashed to NAND based on new partition sizes
Prior to rebooting, flash bravo-boot-v1.5.3-CustomMTD.zip, this patches ROM kernel to load with same partition sizes.
Enjoy
Warnings:
Do not attempt to flash radio via recovery/ZIP, only do it via fastboot.
Has only been tested on HTC Desire, may not work on other phones.
Some users have suggested small cache size affects performance in games, if you play games on your phone it may be worth setting cache to 20-35MB
Uninstalling:
Removing this is simple.
Boot in to fastboot
Fastboot flash the original unmodified clockwork img
Reboot into recovery
Format system, data, cache
Install ROM/ZIP, gapps etc, reboot
Download:
bravo-recovery-v1.5.3-CustomMTD.zip
bravo-boot-v1.5.3-CustomMTD.zip
Credits:
AlphaRev - for bringing S-OFF to HTC Desire
Firerat - for the original patch. I will be forwarding you the exact changes/details shortly.
Lbcoder - for coming up with the idea
Skraw ( CM forums ) - for getting lbcoder interested
Koush - for AnyKernel
Cyanogen & Co - for giving us all such great ROMs to play with
Amon_RA and Koush - for giving us something to patch
Techjosh - for fixing the patchers for use with Rogers (EBi1)
Mblaster - for pointing out my nasty habit of using -r zip flag at the end of command ( breaks compatibility with older zip versions, fixed in AutoPatcher v1.5)
Kali- for porting CM6 to Desire thanks a bunch
I don't take any credit for this, other than the time invested to get it working on the Desire.
Code:
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 208112 0 208112 0% /dev
tmpfs 208112 0 208112 0% /mnt/asec
/dev/block/mtdblock3 128000 123932 4068 97% /system
/dev/block/mtdblock5 315008 184048 130960 58% /data
/dev/block/mtdblock4 5120 776 4344 15% /cache
/dev/block/mmcblk0p2 505636 2307 477224 0% /sd-ext
/dev/block/vold/179:1
7431564 5413644 2017920 73% /mnt/sdcard
/dev/block/vold/179:1
7431564 5413644 2017920 73% /mnt/secure/asec
/dev/block/dm-0 3124 1504 1620 48% /mnt/asec/com.google.android.stardroid-1
Reserved
Just in case
Interesting
Nice work.
Now THIS is what I was waiting for when I s-offed my desire
Good stuff can't wait to try it out.
Thanks.
Yeahaa ... that's what many people waiting for ... Thank you very much for that work !
Nice work!
Very very Interesting...
HTC Desire
DeFrost 5.1 rom
Which is the command to see the partition sizes? i undestand is under adb but cant find the commands
wait a sec... couldn't this be used to resize the /system to fit the complete Desire HD rom... ofc that would not allow you to have custom apps, but still
daedelus82, you seem to have made the most out of your nightshift . Thanks from all of us wondering how to put S-Off to good use.
Hi, that seems very good news and tool but can you explain me the advantage to resize or manipulate the partition ??
My English is not perfect for understand "lbcoder's custom partitions layout thread" or "Firerat's patch".
Regards, Oijkn.
Short Question: Is there anything that prevents us from mounting /dev/block/mmcblk0pX as /data? Seems like a trivial Apps2SD for me, but perhaps that would be too easy...
Otherwise ~420MB /system would be possible. Don't know if thats enough for those DesireHD Roms.
Oijkn said:
Hi, that seems very good news and tool but can you explain me the advantage to resize or manipulate the partition ??
My English is not perfect for understand "lbcoder's custom partitions layout thread" or "Firerat's patch".
Regards, Oijkn.
Click to expand...
Click to collapse
The main use is to get more space for apps on /data by shrinking /system to exactly the size needed for the rom you use and shrinking /cache as it is not really used anyway (at least on g1 it was only used for ota updates, which you don't get on a custom rom).
Other use would be to fit a huge rom on a blown up /system partition.
Question before you release it: how to predict what size of /system I need? It is equal to size of /system folder in ROM's flashable file?
Second question: it is good idea to shrink /system to something like 5 MB and move all system apps to /data (then all apps can be easily uninstalled and updated)?
mblaster said:
The main use is to get more space for apps on /data by shrinking /system to exactly the size needed for the rom you use and shrinking /cache as it is not really used anyway (at least on g1 it was only used for ota updates, which you don't get on a custom rom).
Other use would be to fit a huge rom on a blown up /system partition.
Click to expand...
Click to collapse
Thanks mate for the explain ^^ I understood a little better. Do you think that patch will make my desire more efficient ??
I think this will benefit the community a lot.
Sense HD users might finally get the whole system on nand.
AOSP users will have more memory to install appss on nand.
Win-win for everybody
Will this script Resize the Partitions automatically depending on which ROM you are flashing?
wow
it sounds great
worst case we delete some unnecessary apps, and HD port can fit to the device
wow
i tried this on my g1, trust me its not worth the trouble. stick with apps2sd if youre having space problems.
warsng said:
i tried this on my g1, trust me its not worth the trouble. stick with apps2sd if youre having space problems.
Click to expand...
Click to collapse
But thats just it though... I am using using A2SD and still having space trouble!
I put this short guide together because I tend to see a lot of confusion regarding what a "wipe data / factory reset" does to your phone.
These are the steps you should take before loading a new ROM:
1) Download your new ROM and relevant supporting or needed files like modem, alternate kernel, etc., and place them on your internal SD.
2) Backup your applications, settings, messages, etc., with a backup tool like Titanium Backup, image specific backup tool, etc.
3) Boot into recovery and run a “wipe data/factory reset"
4) Follow the developers ROM loading instructions.
When you perform a “wipe data/factory reset” the content of the following directories are deleted :
/data
/cache
/datadata
/sd-ext
/sdcard/.android_secure
Nothing else on your SD card (internal or external) outside of these directories is modified so it is safe to leave files outside of the above mentioned directories without fear of losing them. Your external SD card and SIM do not need to be removed. The goal here is load a new or updated ROM in as much a clean environment that you can. Files left behind in these, especially cache and davlik-cache can cause some of the strangest problems. The kind that nobody can really resolve.
/cache - This is the partition where Android stores frequently accessed data and application components to make these, as implied, respond much faster as well as faster to retrieve / access.
/datadata – This directory contains the library, database, user specific configuration files as well as log files for its specific application installed in the /data directory.
/data directory is where your contacts, messages, settings and apps that you have installed go. Wiping this partition essentially restores it to the way it was when you first booted it, or how it was after your last custom ROM install.
If your ROM uses an /sd-ext partition on your SD card for data storage your /data directory is mapped to /sd-ext and wiping the /sd-ext directory will result in losing your data.
/sd-ext is used for apps moved to your SD card. Your Android OS runs natively in an ext format while your SD card has a fat32 format, which is used typically for USB storage devices, Windows computers, etc.
The sd-ext partition is an additional partition on your SD card that acts as the /data partition when used with certain ROMs that have APP2SD or data2ext enabled. It is popularly used on devices that have little memory allotted to the /data partition. A misfortune that in my experience, Captivate does not partake in. Still, users who want to install more programs than the internal memory allows can take advantage of this partition and use it with a ROM supporting this feature.
The folder named .android_secure is where apps are stored when you perform the "move from phone to SDram/SD card" operation.
Consider this, Apps2SD uses the fat32 portion of your SD card, which is obviously limiting because it isn't Androids native file system. However, if you format your SD card, or partition a part of it as a ext file system, you can trick the phone into thinking it's part of the Android OS native environment. This will allow you to move applications, widgets, even cache and davlik cache over to it.
Disclaimer! I am not responsible for any damage you may cause to your phone or SD Card if you try to enable/use sd-ext.
To enable sd-ext in ClockWork Mod (ROM Manager):
Boot into CWM
Go to Advanced
Then to "Partition SD Card"
Choose an sd-ext size
Then choose a swap size, or not. Swap is just like windows' virtual memory. The system will use it when you're running low on RAM and use it as temporary RAM storage. This is where you'll probably see an increase in speed.
Just for fun I put sd-ext at 512MB and Swap at 64MB which is probably more than plenty for the swap. The swap will assist a little with memory and with the extra space I can move my apps over to it with a program like App2SD or in most custom ROMs nowadays just use the "move to USB" option in "Manage Applications". Titanium Backup will also move apps to SD for you and I'm sure you can find plenty more in the market.
You can also use a tool like Minitool Partition Wizard:
1. Open Minitool Partition Wizard
2. Delete Existing Partition from SDCard (Backup data first!!)
3. Create Fat32 Partition
Note: Set all partitions to PRIMARY (Steps 3 - 6)
4. Create EXT2 Partition (System) about 150MB-200MB depend on ROM
5. Create EXT2 Partition (Data) about 150MB-250MB
6. Create EXT2 Partition (Cache) about 50MB
Personally I don't see a need to do any of this on either of my Captivate phones though I have played with it on my DEV phone.
And since it does play a big role and needs to be cleared at times...
Davlik-Cache - dalvik cache is a program cache area for the program "Dalvik". Dalvik is a java based virtual machine that is the base for running your (.apk) programs. In order to make access times faster (there wasn't a JIT compiler installed by default until Android 2.2), the dalvik-cache is the result of dalvik doing a optimization of the running program/s. This optimization is kept so that it is then re-used every time you use your application/s. By default, davlik-cache is located in your /data partition.
No, I'm not looking for donations. Just trying to clarify things for some.
Great info, but a "guide" assists you in doing something, this is just straight info.
While I initially intended on writing it to guide flashers into the benefits of a wipe data / factory reset, and avoiding the myriad of strange issues experienced, I can see now where it can more construed as informational. Hmmm... maybe I'll add more to it or ask a mod to change the title topic for me.
Regardless, my hope is that some people get some benefit out of it otherwise I've only wasted my time.
Thanks, I've been wondering for a while what that actually did.
Great start for a guide that should clear the boards up a bit. I vote it to be stickied after adding a bit more info on backing up, partitioning the sd card, dalvik cache, etc.
I think it is important to explain that a reset should not be done after flashing a custom ROM because it deletes the Dev's settings/data/non-system apps. Instead flashers should either reset after flashing back to stock or before flashing a custom ROM over the current custom ROM.
Cozmo1 said:
I put this short guide together because I tend to see a lot of confusion regarding what a "wipe data / factory reset" does to your phone.
When you perform a “wipe data/factory reset” the content of the following directories are deleted :
/data
/cache
/datadata
/sd-ext
/sdcard/.android_secure
/cache - This is the partition where Android stores frequently accessed data and application components to make these, as implied, respond much faster as well as faster to retrieve / access.
/datadata – This directory contains the library, database, user specific configuration files as well as log files for its specific application installed in the /data directory.
/data directory is where your contacts, messages, settings and apps that you have installed go. Wiping this partition essentially restores it to the way it was when you first booted it, or how it was after your last custom ROM install.
If your ROM uses an /sd-ext partition on your SD card for data storage your /data directory is mapped to /sd-ext and wiping the /sd-ext directory will result in losing your data.
/sd-ext is used for apps moved to your SD card. Your Android OS runs natively in an ext format while your SD card has a fat32 format, which is used typically for USB storage devices, Windows computers, etc.
The folder named .android_secure is where apps are stored when you perform the "move from phone to SDram/SD card" operation.
Consider this, Apps2SD uses the fat32 portion of your SD card, which is obviously limiting because it isn't Androids native file system. However, if you format your SD card, or partition a part of it as a ext file system, you can trick the phone into thinking it's part of the Android OS native environment. This will allow you to move applications, widgets, even cache and davlik cache over to it.
Nothing else on your SD card (internal or external) is modified so it is safe to leave files outside of the above mentioned directories without fear of losing them.
If you plan on trying several different ROM's and/or updating your favorite ROM every time a new version is released you need to invest in an application like Titanium Backup or one that comes with your ROM if it's supplied with one. MIUI includes one that works extremely well. Performing a “wipe data/factory reset" after loading your new ROM and before booting into it should provide you with a smoother transition to your newly chosen or upgraded ROM. Having a standard backup and restoral process should help you enjoy it quicker too.
Click to expand...
Click to collapse
Here is something I keep in a word file to help answer what you are also trying to answer. It is a bit shorter and simplified but it may help to polish your thread for us simpletons.
Dalvik cache is a place where the Android OS re-compiles the executable programs the first time to optimize them. It does this when you make a major change like replace the kernel/modem. Clearing the Dalvik cache will force Android OS to recompile the apps for the the new kernel/modem. This can take time on the first boot after clearing the Dalvik cache.
Also the main data Cache is used by the Android OS at run-time to write temporary files for specific reasons. You want to clear this out so it doesn't re-use the old cached data.
Manually clearing both caches allows the new kernel/modem to be installed in a "cleaner" environment. It's just preventative maintenance.
snowake said:
I think it is important to explain that a reset should not be done after flashing a custom ROM because it deletes the Dev's settings/data/non-system apps. Instead flashers should either reset after flashing back to stock or before flashing a custom ROM over the current custom ROM.
Click to expand...
Click to collapse
This actually makes perfect sense to me. I have modified my OP because of your input. Thank you very much, snowake!
Cozmo1 said:
This actually makes perfect sense to me. I have modified my OP because of your input. Thank you very much, snowake!
Click to expand...
Click to collapse
do u have more info about "format your SD card, or partition a part of it as a ext file system" or how to do that.
i have read someone format part of the sdcard (class 10)to ext 2 or 4,to make the write n read faster.is that what you mean.can u guide me to the right direction.thank in advance.
? ? ? about this......(However, if you format your SD card, or partition a part of it as a ext file system, you can trick the phone into thinking it's part of the Android OS native environment. This will allow you to move applications, widgets, even cache and davlik cache over to it.)
Cozmo1 said:
This actually makes perfect sense to me. I have modified my OP because of your input. Thank you very much, snowake!
Click to expand...
Click to collapse
I struggled with all of this my first first few flashes.
xpakage said:
...Dalvik cache is a place where the Android OS re-compiles the executable programs the first time to optimize them.
...
Also the main data Cache is used by the Android OS at run-time to write temporary files for specific reasons.
Manually clearing both caches allows the new kernel/modem to be installed in a "cleaner" environment. It's just preventative maintenance.[/I]
Click to expand...
Click to collapse
That is much more boiled down. I looked back at the "how to flash" threads and a couple good explanations on custom roms. None explain this that I found.
Cosmo, here are some more thoughts on misunderstandings I have had and seen posted. Like post above I pasted from my notes, so may be incorrect.
Bootloaders: Same for Froyo/Eclaire in both i897 and i9000 roms. GB requires new bootloaders, but i897 are apparently cross-compatible. However, issues seem to pop up on i9000 roms with GB i897 bootloaders. If flashing back to Froyo, use the full jf6 stock, not cezar's stock eclaire without bootloaders.
Using Tibu: If no useful data (i.e. Bookmarks on dolphin) then simply click data only when restoring user apps. Typically no issues when restoring user apps after switching Android versions. However, system apps should not be restored because of the rom customizations. Especially when switching to GB because it uses different directory structure. I do not seem to have issues when staying on same version and restoring foreground (user accessible) apps with data only or restoring green text color sys apps with Tibu as icon (i.e. Accounts).
Rom manager: really only need the app if flash to stock and need to flash rom directly from cwm. If so, then flash cwm (top button in menu) and choose phone. This places update.zip in /sd, which is opened after selecting "reinstall update" in stock recovery. Usually have to select it twice for it to work. This will replace ATT stock 2e recovery (blue text) with cwm 2.5 (froyo).
Voodoo color, lagfix, sound: must either be included in kernel. Lagfix simply allows user to format sd as ext4 (linux). Color balances display so less blue iodes are used and color is more realistic. Sound allows clearer sound through headphones through tweaks enabled in voodoo app. If sound is not in kernel then purchase voodoo pro in market and it will install it into the kernel (if rooted, even if stock).
Thanks for clearing that up!
- Aaron
Updated with more details.
Really, really useful. Had no idea partition options were available to this extent! Especially swap. By mini tool are you referring to Easus' program? I am definitely checking this out tonight. Thanks!
Great guide. In order to clear
/sdcard dir I master clear it after flashing to stock. Is there an alternate method besides deleting dirs myself?
snowake said:
Great guide. In order to clear
/sdcard dir I master clear it after flashing to stock. Is there an alternate method besides deleting dirs myself?
Click to expand...
Click to collapse
That is probably the safest way to do it within the phone itself. An alternate way would be to mount it to your computer:
In Windows right click the drive that was assigned to your internal SD card and then click on format. By default it'll most likely set you to Fat32 and if you click format it'll say its complete, but nothing will be deleted. Android being a Linux OS doesn't use fat. You can format it by choosing exFat, but by doing this...
!!!WARNING!!! be aware that you will lose everything on your internal SD card AND your external SD card.
Emphasis placed mainly for others that read this and might not know.
Safer and easier to do it within the phone.
snowake said:
Really, really useful. Had no idea partition options were available to this extent! Especially swap. By mini tool are you referring to Easus' program? I am definitely checking this out tonight. Thanks!
Click to expand...
Click to collapse
This one is from MiniTool, though I wouldn't be surprised if Easus owned them. I didn't investigate to confirm. You can get the free home edition of MiniTool Partition Wizard here.
Very nice infos. Deserves a sticky, although, probably in a different thread.
Some information on what "Master Clear" in Odin would also be helpful - I have never trusted my phone to 'truly' clear everything on the phone, I have found the Odin Master Clear option to be much more complete.
It is a bit odd, I do this with my PC every six months, I back everything up and format the drive and start over again (after running Spinrite on all the drives) - I do this on / around New Years and again over 4th of July weekend and I decided this past weekend to also do the same with my smart phones (4 Cappies) and tablets (Ipad and 2 Android tabs) this past weekend.
It gives me that sort of squeaky clean feeling and seems to make my devices run smoother. Maybe its all in my head, dunno *shrugs*.
One thing I can say however, I have not had a hard drive go bad on me since I started the Spinrite thing 10 years ago (I still have an 8 GB hdd in my desktop that is working!!).
Any decent update(r)-script will do this for you.
Sent from my Infuse 4G
littlewierdo said:
Very nice infos. Deserves a sticky, although, probably in a different thread.
Some information on what "Master Clear" in Odin would also be helpful - I have never trusted my phone to 'truly' clear everything on the phone, I have found the Odin Master Clear option to be much more complete.
It is a bit odd, I do this with my PC every six months, I back everything up and format the drive and start over again (after running Spinrite on all the drives) - I do this on / around New Years and again over 4th of July weekend and I decided this past weekend to also do the same with my smart phones (4 Cappies) and tablets (Ipad and 2 Android tabs) this past weekend.
It gives me that sort of squeaky clean feeling and seems to make my devices run smoother. Maybe its all in my head, dunno *shrugs*.
One thing I can say however, I have not had a hard drive go bad on me since I started the Spinrite thing 10 years ago (I still have an 8 GB hdd in my desktop that is working!!).
Click to expand...
Click to collapse
I can run some tests on Odin's master clear to confirm what it does. Initially I would believe it does the same as a "wipe data / factory reset", but testing should let us know for sure. I'll test it this weekend. Maybe sooner.
Awesome to hear that I'm not the only advocate for SpinRite and I still use it a lot though not every 6 months like you do. It's definitely worth having and using.
MikeyMike01 said:
Any decent update(r)-script will do this for you.
Sent from my Infuse 4G
Click to expand...
Click to collapse
I totally 100% agree with you, MikeyMike01. Unfortunately, not all update scripts are created equally Asides from teaching people how to script themselves or parse through it, a task I do not have the time or patience to tackle, this it probably the easiest and best way to have users try to avoid the many and strange issues posted that possibly / most likely could've been avoided by using the tools at their disposal.
On a side note... I didn't notice you got yourself an Infuse 4G. Congrats! How do you like it? I've been out of contract for almost a year now and wouldn't mind upgrading (my wife is in contract), but I haven't seen anything really worth upgrading to or that does something I really need/want that the Captivate cannot, atm. I haven't looked up any specs and reviews on the Infuse yet tho.
I reverted back to cinni bell froyo from 6.3 R3
I would like to get link2sd card to work. I got it semi working but it would use 10% of what I allocated and then say it was full so I couldnt install anything from there on.
I partitioned it using gparted... 15g and 1g for the ext2.
open recovery checking with sdcard utiilites. errors and says it fixes it.
check with the froyo sd card util and do not see the added space... says around 100meg
download and install link2sd.. crashes and pull battery... odd time I get it to install and when i select to move a program to sd it has a container error.
I can use the link feature tho.
Sometimes I get the memory is full and other times I get get a crash when I attempt to install either from apk or from market... (i have gotten different results between attempts to get the sd card partition properly from googling all sorts of threads)
I don't know what I'm doing wrong. Any help would be greatly appreciated!
Would the sd card util say the added space if the partition worked properly?
I don't think the cincinnati bell froyo supports Link2SD without changing the boot scripts (because it does automatic app2ext). How did you try to add Link2SD support?
I guess thats why I am having so much trouble. The Cinni keeps changing it on me?
I either installed the link2sd from sd card or from the market.
You're going to have to edit the /system/oc file. First copy the original to /system/oc.bak then edit /system/oc. At the end of /system/oc you will see:
Code:
# enable sd-ext
if [ -e /dev/block/mmcblk0p2 ] ; then
insmod /system/lib/modules/ext2.ko
insmod /system/lib/modules/jbd.ko
insmod /system/lib/modules/ext3.ko
[B] mount /dev/block/mmcblk0p2 /sd-ext
if [ $? -eq 0 ] ; then
mkdir /sd-ext/app ; chmod 777 /sd-ext/app
[[ -d /data/app ]] && cp -a /data/app/* /sd-ext/app/
[[ -d /data/app ]] && rm -R /data/app
ln -s /sd-ext/app /data/app
fi
[/B] fi
Delete the bolded lines.
Honestly, I strongly recommend RusMod 1.19 over the CBW if you really want to run a Dexter13 ROM. http://forum.xda-developers.com/showthread.php?t=1118575
I nandroided an image without link2sd.
I edited the OC file as suggested.
Restarted device. Installed Link2sd.
Rebooted again.
Tried to move a program and it is still getting the container error.
Went back to open recovery and checked with the sd utilities and it said
ext2 was ok.
So I guess I will try that russianmod and see how that goes.
I'll have to wait till it downloads. Its really slow...
Does that one still give full camera function?
xtwister6 said:
I nandroided an image without link2sd.
I edited the OC file as suggested.
Restarted device. Installed Link2sd.
Rebooted again.
Tried to move a program and it is still getting the container error.
Went back to open recovery and checked with the sd utilities and it said
ext2 was ok.
So I guess I will try that russianmod and see how that goes.
I'll have to wait till it downloads. Its really slow...
Does that one still give full camera function?
Click to expand...
Click to collapse
i'd try khalpower's v4 rom. it was my favourite before cm6 arrived. it has full camera functionality. get the one thats themed with steelepicblue. everyone's favourite. hehe
eejin2 said:
i'd try khalpower's v4 rom. it was my favourite before cm6 arrived. it has full camera functionality. get the one thats themed with steelepicblue. everyone's favourite. hehe
Click to expand...
Click to collapse
+1 on that. Too bad it isn't being worked on anymore, but it still works plenty good enough and stable too. I miss the radio but I have managed w/o it and moved on to Tune-in, Jango and Iheart.
I am always harking on this but ext partitions don't have to be sooo big. A good size is 350-400mb and even sometimes that is too big. 1GB imho is way too much wasted space that could be used for music, movies, pix,...
Figure that an average app is on the heavy side (like Flash or something like that) not usually more that 15-20mb. Like I said, on the heavy side. I have 60+/- apps and only about 125mb taken up in my partition. My /cache partition will fill up faster than my ext partition.
Look at it like this
8 bits = 1 Byte
1024 Bytes = 1 Kilo Byte
1024 Kilo Bytes = 1 Mega Byte
1024 Mega Bytes = 1 Giga Byte
1024 Giga Bytes = 1 Tera Byte
You would have to have a crapload of moster MBs (like Flash/ Moboplayer/ Angry Birds) to take up that whole 1gb partition. And even then your dalvik-cache will be too full to take that many apps and you'll have to start deleting some to make space.
xtwister6 said:
download and install link2sd.. crashes and pull battery... odd time I get it to install and when i select to move a program to sd it has a container error.
I can use the link feature tho.
Click to expand...
Click to collapse
I think I may have misunderstood what you wrote. So, Link2SD is working, it's the native froyo App2SD that doesn't work? You may have to delete the /sdcard/.android_secure directory.
So I thought I would start from scratch.
Put Bright 2.1 rom
Put steel blue v4 as suggested.
Install the link2sd 1.9.1
When I try to put an app on the SD it gives me an error
Failure
pkg: /data/app/ (filename.apk)
Then it says its on the sd. So I check the sd-ext directory and nope..
So I thought I could just create the directories data/app/
but still get the above failure
I tried changing the ext2.ko file to the 840kb but that doesn't do anything.
This os version doesnt have the OC file as stated above.
I think I'm close and don't know what else to try.
I appreciate the help.
-- I also redid the sdcard with gpart
formatted the whole card to fat32
-resized and created the ext2 partition
formatted to 500 meg using ext2
Woodrube said:
Figure that an average app is on the heavy side (like Flash or something like that) not usually more that 15-20mb. Like I said, on the heavy side. I have 60+/- apps and only about 125mb taken up in my partition. My /cache partition will fill up faster than my ext partition.
.
Click to expand...
Click to collapse
does link2sd not create use the ext2 if you link it? That's why I am trying to get this to work so that it doesn't touch too much of the internal memory?
Mioze7Ae
I am attaching the sd-card diagnotics like it says in your sig.
It does say fix me but I've run the util and it seems to go back to needing
repair each time after starting up?
Thanks for posting the sdcard-info.txt. You need to create an empty /sd-ext/link2sd directory and reboot.
I tried that and I am still getting the same error. Do I have to add sub directories into the link2sd directory such as data/app ?
No, you shouldn't have to touch /data at all and you don't need to do create any directories other than /sd-ext/link2sd. Can you rerun the diagnostics?
attached is the diagnostics.
Again thanks for your help!
Ate you putting your app folder on /sdext/link2sd and not /data/lunk2sd? Remember if you are using link2sd you name your folder link2sd. If you are using app2ext you name it app. It also kind of looks from the txt file that your ext partition is an ext4. Might be reading that wrong bit I definitely see ext4 in there and kahls v4 doesn't support that.
Edit: quick question. How are you trying to "put" your apps on ext? Hopefully you aren't going to settings>apps>manage>move to SD.
Oh, sorry I didn't also catch this the first time... only our most recent ROMs support ext4 (CM6, XDAspecial, Bravo). ext3 should work and ext2 will definitely work. You can use nandroid to backup your sd-ext partition (I think it's called SD data in the nandroid menus), Then just nandroid restore it and your /sd-ext will be reformatted as ext2.
It should be ext2. Thats how I formatted the partition.
I had both folders /data/app and link2sd on the card. I deleted the /data/app folder and rebooted.... still getting the error.
it seems to keep pointing to data/app folder in the error message
Oh, you're right. I was misreading my own diagnostic log. *facepalm* Hmm. Nothing looks wrong...
Here Mz, this is for you. Found it on another thread.
Do you have this folder, sd-ext/link2sd? What error do you get when you launch the link2sd apk? IIRC /data/app is only symbolic links.
Might want to reformat and start over by just putting folder in SD-ext/link2sd and wiping out all the previous issues. Am usually against reformatting, but in this case might be best option.
I posted this in a thread in the Dev. section but that's probably not the appropriate place for it - I've been installing ROMS (SCV7, Swifty Trix) with BootMenu on the second system with Leak #1 on the primary system. On the primary system I have ~ 4 gigs allotted to app storage and on the second I only have ~ 200 mbs. I can't even begin to install a basic set of application... are there any suggestions on how to remedy this situation? I've been Google-ing the subject but haven't found much information so far.
EDIT - So, I guess "RTFM" should always be in mind:
Q: I have a "low storage space" on 2nd system?
Webtop partition size is only 1.3GB.
To make thing simple, the included boot_second.sh script bind mount /system & /data inside this webtop partition.
You have at least 4 option, if you want to have bigger /data
1.Reassign /data to /sdcard (IO speed depend on sdcard speed rating)
2.Reassign /data to /dev/block/userdata (this will replace all your data for stock system)
3.Reassign /data to /dev/block/cache (bind /cache to somewhere else e.g : /webtop/cache)
4.Use a lightweight ROM (/system size = small)
You need to modify these files to suit your needs.
/preinstall/bootmenu/script/boot_stock.sh
/preinstall/bootmenu/config/stock.recovery.fstab
/preinstall/bootmenu/script/boot_second.sh
/preinstall/bootmenu/config/second.recovery.fstab
Sorry, for now you all have to configure this files manually.
--------
So, this is a little beyond what I've done with Android thus far... for now I haven't been able to figure out how to work it out. Any suggestions would be much appreciated. Thanks!
goto
1) mounts/format
2) format webtop
3) toggle second system recovery (main menu)
4) install/restore whichever ROM u desire
i think erasing webtop will pretty much free system space in "second system"
and remember second system is usually considered as trial purpose
as far as my exp. changing something in first system will somtime affect the second system
Happy flashing
aguacateojos said:
I posted this in a thread in the Dev. section but that's probably not the appropriate place for it - I've been installing ROMS (SCV7, Swifty Trix) with BootMenu on the second system with Leak #1 on the primary system. On the primary system I have ~ 4 gigs allotted to app storage and on the second I only have ~ 200 mbs. I can't even begin to install a basic set of application... are there any suggestions on how to remedy this situation? I've been Google-ing the subject but haven't found much information so far.
EDIT - So, I guess "RTFM" should always be in mind:
Q: I have a "low storage space" on 2nd system?
Webtop partition size is only 1.3GB.
To make thing simple, the included boot_second.sh script bind mount /system & /data inside this webtop partition.
You have at least 4 option, if you want to have bigger /data
1.Reassign /data to /sdcard (IO speed depend on sdcard speed rating)
2.Reassign /data to /dev/block/userdata (this will replace all your data for stock system)
3.Reassign /data to /dev/block/cache (bind /cache to somewhere else e.g : /webtop/cache)
4.Use a lightweight ROM (/system size = small)
You need to modify these files to suit your needs.
/preinstall/bootmenu/script/boot_stock.sh
/preinstall/bootmenu/config/stock.recovery.fstab
/preinstall/bootmenu/script/boot_second.sh
/preinstall/bootmenu/config/second.recovery.fstab
Sorry, for now you all have to configure this files manually.
--------
So, this is a little beyond what I've done with Android thus far... for now I haven't been able to figure out how to work it out. Any suggestions would be much appreciated. Thanks!
Click to expand...
Click to collapse
All of that is not needed, and you will mess up your install on first system too.
I get trying new things out and trail blazing, but next time do a little research first. There are people who don't think and search for a problem and find your solution try it and learn they now have to fxz, but don't know how or can't.
This appears to be way beyond you. Next time try something a little smaller and less likely to screw something up for those that don't know or not very capable.
shardul.phatak said:
goto
1) mounts/format
2) format webtop
3) toggle second system recovery (main menu)
4) install/restore whichever ROM u desire
i think erasing webtop will pretty much free system space in "second system"
and remember second system is usually considered as trial purpose
as far as my exp. changing something in first system will somtime affect the second system
Happy flashing
Click to expand...
Click to collapse
What he said ^^