Related
Hey guys
Im on holiday now so cannot really check myself the differences, but just wanted some quick info on the A2SD, with the official froyo i was hoping everybody will start using it, but somehow people still using the old method, whys that?
thanks
Froyo A2SD is completely reliant on app developers. If the devs doesn't allow it in their app then it can't be moved to the SD card. This is really only a problem because Froyo is still new.
Old A2SD you can dump everything on the SD
However, I'd be interested in seeing if there is a way to force an app onto the nand using A2SD+. Would work better for things like widgets, home replacements etc, as they'd run quicker for people with slow sd cards.
Probably because the FroYo one sucks !
Why ? Well, mostly because devs have to rewrite their apps so they can use FroYo's app2sd function...
With the "old-fashioned" a2sd, there is no need to do anything, just sit and enjoy the free space
APP2SD allows you to move certain apps to your SD card and run them from there BUT as these are placed on the normal root of the SD when you mount the SD, via USB for example, you loose access to these apps until you remount SD. This means you cant install widgets to the SD and such like.
APP2SD+ on the other hand uses an ext3 partition (or ext4 on newer versions) which then installs all apps & widgets to that partition and when the SD is mounted you dont lose any apps or widgets as is located in a seperate partition.
Hope that helps.
Sent from my HTC Desire using XDA App
Sent from my HTC Desire using XDA App
wow! thats quick thanks for you input guys think you explained everything i wanted to know really
Id want to use the offical a2sd as i think using ext3 partitioned sd card have already slightly damaged the card cuz it keeps giving me errors everytime i connect it to a pc
mrwookie6379 said:
APP2SD allows you to move certain apps to your SD card and run them from there BUT as these are placed on the normal root of the SD when you mount the SD, via USB for example, you loose access to these apps until you remount SD. This means you cant install widgets to the SD and such like.
APP2SD+ on the other hand uses an ext3 partition (or ext4 on newer versions) which then installs all apps & widgets to that partition and when the SD is mounted you dont lose any apps or widgets as is located in a seperate partition.
Hope that helps.
Click to expand...
Click to collapse
So let me understand the names:
APPS2SD = Froyo Original (comes with official Froyo release)
APPS2SD+ = Hacked version which has been out since FRF50 leak?
EDIT: But if APPS2SD+ is so much better (keeps apps on ext3 partition), why to people keep using the original APPS2SD on their ROMs?
Check this explaination. Quoted from neoKushan from yesterdays thread.
neoKushan said:
Ok, so here's the deal, in a very longwinded way that should hopefully explain everything and answer ALL questions.
You have an SD card in your phone and, a bit like normal PC Hard Drives, you can "partition" them (split them into two or more sections of different filesystems). Normally, your SD card is just one big FAT32 partition, which is fine for storing your pics, messages, emails, etc.
Now, other then your Phone's SD card, your phone will have its own internal flash memory (or "NAND") storage. Tradditionally with Android, you could only install applications to this NAND storage, you cannot install them onto your SD card. So if you have an empty 32GB SD card, but only 5Mb of internal phone storage, you still wont be able to install many apps, if any at all.
This was done to protect the apps from things like piracy - it's not easy to access the location where apps are installed on your phone's internal storage (normally impossible without root), so you can't for example buy an app, copy it, refund it, then install it again.
Still, this is no good for those of us who like to install lots and lots of apps, legitimately, as we run out of internal storage very quickly.
So Google came up with a way to install apps to the SD card. A folder is created called something like .android_secure and this stores (I believe) encrypted versions of applications, but there's a few catches:
1) Apps aren't automatically stored here, you have to manually "move" them
2) Not all apps are capable of being moved, in fact most apps aren't, the developer needs to update their app and allow it. Some apps aren't and wont be updated and some developers may not want to allow it for whatever reason.
3) Not all app data is moved, most of it is but some data is left on your phone so many people still run out of internal storage quickly.
4) You can force ALL apps to be moved to this area by default, but it breaks incompatible ones - such as Widgets, which are unable to load due to the SD card not being "prepared".
So that's Froyo's version. Before Froyo existed, some very clever people came up with a thing called "Apps2SD". Remember I said that your SD card normally is one big FAT32 partition? Well, Apps2SD works by having your SD card patitioned into TWO filesystems. A normal FAT32 partition for your usual stuff and a secondary "EXT" partition. EXT is just a filesystem, like FAT32 or NTFS, but it's the filesystem used by Android internally. The SD card is normally FAT32 because it's a "universal" filesystem, that just about any machine will be able to read, whereas EXT filesystems are generally Linux only, but I digress.
EXT has several different versions. The most common one you'll see is ext3. The main difference between ext2 and ext3 is "journaling", which is just a fancy way of saying that should an operation (such as copying, writing or reading) be interrupted unexpectedly (say, by you turning your phone off), then no data should be lost or corrupted. You know how when you turn your phone on, it says "preparing SD card"? It takes a few minutes, but what it's actually doing is checking that the FAT32 partition hasn't been damaged, because FAT does NOT have journaling. If you used a computer back in the Windows 98 days, you may remember that lovely blue "Scandisk" screen that had to run every time you didn't shut your computer down correctly - that's the same thing. But then Windows 2000/XP came along with NTFS, which also has journaling, meaning you had less chance of loosing data. But I digress once more.
So you have your SD card partitioned into EXT and FAT32. Generally it doesn't matter if it's ext3 or ext4, but you don't get any real advantage with ext4 over ext3 in this instance. Apps2SD then runs a special script on your phone which "symbolically links" the folder from your phone's internal storage where your apps are normally stored, to the ext partition on your SD card. A symbolic link is a bit like a shortcut for folders, except it's transparent to the OS: In other words, Android doesn't know that when it's installing it's apps to the internal phone storage, it's actually being stored on the SD card. This effectively boosts your internal phone memory from the previous 5mb that you had in my example above, up to whatever size you made the ext partition on your SD card (often 512Mb or 1Gb, but it depends on how many apps you install).
Plus, because it's "journaled", it doesn't need to be "prepared", meaning it's ready to go as soon as the phone starts - so your widgets and apps work immediately (unlike "forced" Froyo Apps2SD, where widgets disappear).
The catch with Apps2SD is that whatever space the ext partition takes up is taken away from the SD card. So if you have a 4Gb card (with something like 3.5Gb of actual storage) and you make a 512Mb ext partition, your SD card will "shrink" to 3Gb. The space isn't actually lost, it's just being used by the ext partition. If you reformat your card, you'll get it back.
Finally, there's a difference between "Apps2SD" and "Apps2SD+". Remember I said that your apps are stored on a special folder inside your Phone's NAND storage? Well, that was a bit of a lie. It's actually stored in TWO places. There's a second area which is called the Davlik Cache. You don't really need to worry about what this is for (Hint: IT's to do with the Java runetime your phone uses to run apps), all you need to know is that apps use it to store data, which also eats up internal phone memory. Apps2SD+ moves davlik cache to the ext partition on your SD card as well, freeing up even more space. Some people believe that this may come at the cost of performance, as the internal NAND memory should be faster than your SD card (Which is why you also get people arguing over which "class" SD card is better for Apps2SD - the logic being that a faster SD card means less impact from this move), but the truth of the matter is that your applications will be running from your Phone's RAM anyway, so performance isn't really impacted at all. Since most apps are only a few hundred Kb's in size, or a couple of MB at the most, it's a non-issue.
Finally, any recent version of Apps2SD/Apps2SD+ should work with an SD card that is or isn't formatted with an ext partition. It'll check for this partition when your phone first boots and if it's not there, just use internal phone storage.
Having an ext partition WITHOUT Apps2SD+ shouldn't cause any issues, either, so you can format your SD card whenever you're ready.
So in summary:
Apps2SD "fakes" your phone's internal memory and puts it all on a hidden section of your SD card.
Apps2SD+ pushes even more content to the SD card, freeing up even more space on the phone itself.
"Froyo" Apps2SD has various limitations that "old" apps2SD does not, but is much easier to handle as it doesn't involve any kind of "partitioning".
Click to expand...
Click to collapse
That's a great summary, thanks for that!
But... how can I create an ext3 partition on a new SD card? I don't want to use ROM Manager because that has a maximum of 512Mb for ext3, I want to make 1gb or more.
Also, what size should I make swap partition?
Vice83 said:
That's a great summary, thanks for that!
But... how can I create an ext3 partition on a new SD card? I don't want to use ROM Manager because that has a maximum of 512Mb for ext3, I want to make 1gb or more.
Also, what size should I make swap partition?
Click to expand...
Click to collapse
You can do that thru recovery-windows.bat by going thru recovery mode by volume down + power, go to recovery then when the red exclamation point appears just run the recovery-windows.bat by double clicking on it. You can get these files from r5-desire-root-alt from the rooting process files (search the forums for this if you don't have it). But be cautious cause when you partition your sd card, all your files will be wiped so make sure to backup everything you need. Cheers!
Edit:
Actually this summary about the ap2sd and ap2sd+ and froyo ap2sd should be stickyed for everyone, so it would not be ask over and over again.
Couple of extra ways to partition:
1) Flash AmonRA's Recovery to your phone (I used Unrevoked to do it)
2) Use GParted on a Linux LiveCD (e.g Slax) to partition your card exactly how you want it
Vice83 said:
That's a great summary, thanks for that!
But... how can I create an ext3 partition on a new SD card? I don't want to use ROM Manager because that has a maximum of 512Mb for ext3, I want to make 1gb or more.
Also, what size should I make swap partition?
Click to expand...
Click to collapse
ROM Manager is probably the easiest way to do it, but I was stuck with EXACTLY the same problem when I rooted. I chose to flash AMON Ra recovery (don't have the link, but you can google it up), and then used that to create a 1024MB ext partition. Then used AMON Ra again to convert the ext partition to ext3. Hope that helps.
However, one question I have regarding neoKushan's explanation is that if I did create a 1024MB ext3 partition, then the same capacity should be visible in the phone's internal memory. However, after I rooted and restored my apps, I could only see about 100+ MB of free internal memory. Can anyone help me with this please? Am using the Opendesire Official Froyo 1.0c ROM that has A2SD built in
deepdevil said:
ROM Manager is probably the easiest way to do it, but I was stuck with EXACTLY the same problem when I rooted. I chose to flash AMON Ra recovery (don't have the link, but you can google it up), and then used that to create a 1024MB ext partition. Then used AMON Ra again to convert the ext partition to ext3. Hope that helps.
However, one question I have regarding neoKushan's explanation is that if I did create a 1024MB ext3 partition, then the same capacity should be visible in the phone's internal memory. However, after I rooted and restored my apps, I could only see about 100+ MB of free internal memory. Can anyone help me with this please? Am using the Opendesire Official Froyo 1.0c ROM that has A2SD built in
Click to expand...
Click to collapse
I'm not sure about what exact capacity for the internal memory after partitioning to ext3 but when I was on Opendesire before for the eclair 2.1 after I'm done flashing the rom and setting up the whole ap2sd+ my internal memory was 410mb. I used:
swap=0
ext=1024
fat32 is for the rest of the card
Then after upgrading to froyo rooted ROM, I'm only getting 140mb tops. I dunno... I'm too lazy now to get into it right now... maybe soon I'll play around with it again so I can get back my 410mb internal space with the ap2sd+
Stewge said:
Froyo A2SD is completely reliant on app developers. If the devs doesn't allow it in their app then it can't be moved to the SD card. This is really only a problem because Froyo is still new.
Click to expand...
Click to collapse
Not 100% true, because you can change the default install location to SD card (via ADB if stock, and an app if rooted) and then you can have the vast majority of your apps on SD card even if they've not been updated for Froyo.
Regards,
Dave
I always thought the main negative with A2SD+ was that the cache was moved to the sdcard, which of course would wear out the sdcard (slightly) quicker.
Vice83 said:
So let me understand the names:
APPS2SD = Froyo Original (comes with official Froyo release)
APPS2SD+ = Hacked version which has been out since FRF50 leak?
EDIT: But if APPS2SD+ is so much better (keeps apps on ext3 partition), why to people keep using the original APPS2SD on their ROMs?
Click to expand...
Click to collapse
Not exactly!
Prior to Froyo, there were principally two versions of Apps2SD:
1. APPS2SD (or A2SD )
2. APPS2SD+ (or A2SD+)
The first would move your apps to the EXT partition, and the second would move your apps and the Dalvik cache to the EXT partition (see here for an explanation of the Dalvik cache).
Now we have Froyo, we have "native", or "Froyo" apps2sd as well, which does much the same as (1) above except that there is no EXT partition and the apps are on the FAT32 partition of your SD card.
Regards,
Dave
sparksalot said:
I always thought the main negative with A2SD+ was that the cache was moved to the sdcard, which of course would wear out the sdcard (slightly) quicker.
Click to expand...
Click to collapse
Dalvik cache is only actually updated when a new app is installed or and old app is updated, so whilst it will incur more writes to SD card, it probably isn't anywhere near as much as the apps write themselves to the FAT32 partition.
Regards,
Dave
Great summary, but can I format my 8 GB SD card as EXT3 and just forget about the FAT partition? I'm using Ubuntu on my laptop and my EXT4 /home partition is just fine for storing images, movies etc. I really don't get this ado about having an EXT and a FAT partition. Or am I wrong here?
quick question, if i move to another bigger sd card, can i copy my card and transfer it to the new one without losing the EXT, and the apps on it? would i need to make a image of the card? thanx for any advice.
make a backup of them first on your pc and copy them to the newly partitioned sdcard....ext to ext and fat to fat
So there is 3 versions?
1. Froyo A2sd = fat32 only = apps installed to sd
2. A2sd = fat32 + ext = apps installed to sd in ext partition
3. A2sd+ = fat32 + ext = apps installed and Dalvik cache moved to sd in ext partition
Is there any more variants? lol
Sent from my HTC Desire using XDA App
I'm really confused, first with all the different a2sd variants and ones that are made by Darktremor or other people or the FroYo version. This is as much as I know for this app.
Secondly, I really couldn't find any information on doing partitions manually or setting ALL partitions to ext since I have a linux box, I really don't care to use windows to copy over files or whatever. I have a VMware box to do that on my windows machine anyways.
Third, the ClockworkMod recovery has NO options to do the partition following Darktremor's faq, and I don't know if I should install another recovery after flashing my hboot to 0.93 S-OFF (Alpha)
Mind you I only had my android for about 6 days and this is my first one, so learning curve is hard.
Please help
1) the names can be confusing but old apps2sd is an ext partition on your SD card that appears to the system as internal storage. Froyo apps2sd is using Froyo to transfer mapps to the fat32 partition (normal partition) of your SD card. You just need to use context because people tend to use apps2sd for both.
2) you can use gepart to partition. You need a fat32 partition for apps to write to and for any personal data because Android looks to that partition for that kind of data. I have my SD card as 5 gb fat32 and 3 gb ext3. Fat32 goes first.
3) go to ROM manager. Partition SD card. Choose size....there is only 3 sizes though.
If anything I wrote is wrong I'm sure I'll be corrected.
Sorry to hijack the thread, but since this is related to a2sd in general I might as well ask it here. What's the effect of having a2sd+ on your battery? Would it lower battery life due to cache and apps being stored mainly on SD instead of internal memory? I observed that this was often the case when I store always-on apps on SD back on my old Windows device.
So no way of not using a fat32 eh?
It still seems I don't have much space left after using the Rom manager way. I have 120meg free on internal mem.
Could I just format using linux mkfs? I want to make the apps partition about 2GB to hold more apps. Though it seems some widgets can't take putting on SD card, it dissipates.
BriEE said:
So no way of not using a fat32 eh?
It still seems I don't have much space left after using the Rom manager way. I have 120meg free on internal mem.
Could I just format using linux mkfs? I want to make the apps partition about 2GB to hold more apps. Though it seems some widgets can't take putting on SD card, it dissipates.
Click to expand...
Click to collapse
Widgets must be installed on internal storage, or they wont work.
If you want an easy method to make a ext 3 partition use ROM manager premium from the Market. It will make you automatically an ext3 partition with a maximum of 512 mb which is enough (put swap to 0). Just keep in mind that first inside ROM Manager you need to select the option Flash ClockworkMod Recovery, and after that go to the SD partition option otherwise it wont work. And also remember you need to have the PREMIUM version otherwise it might not work
Now if you want to have more than a 512 mb you can use gparted. It is a livecd which means that can work on linux, mac or windows just reboot with the cd inside and is quite straightforward to use. Hope this helps.
Hello guys, any thought about that issue maybe?
http://forum.xda-developers.com/showthread.php?t=816098
I'm having trouble getting apps2sd+ to work on the MIUI rom. I've used rom manager to partition the card and when i go to sd settings its showing the partition as apps2sd+ but when i download apps it seems to be using the partiton and the phone memory? Also when i go on titanium backup it doesnt show the partition at all???
steslatt said:
I'm having trouble getting apps2sd+ to work on the MIUI rom. I've used rom manager to partition the card and when i go to sd settings its showing the partition as apps2sd+ but when i download apps it seems to be using the partiton and the phone memory? Also when i go on titanium backup it doesnt show the partition at all???
Click to expand...
Click to collapse
Try using an app from the Android Marketplace called Quick System Info to check that is it working correctly. Your internal memory may still go down as only portions of the apps (i.e. data) you install are sent to the sd card's ext partition.
The partition worked but its saving all the app on the phone memory as well as the sd card
steslatt said:
The partition worked but its saving all the app on the phone memory as well as the sd card
Click to expand...
Click to collapse
Have you tried clearing the Dalvik cache? Might help some.
Yes i've tried everything, wiped dalvik, factory reset, formated sd card again and partitioned it again. Going to try another rom now. Shame i quite liked the MIUI
steslatt said:
The partition worked but its saving all the app on the phone memory as well as the sd card
Click to expand...
Click to collapse
Thats impossible, the way apps2sd works, it moves the /data/app/ directory to the SD-EXT... as masdroid explaned, the reason your internal storage is decreasing is apps2sd dosent move the data/data directory, this remains on the internal storage, some apps use a large amount of space in /data/data/ some use none at all. but from what i have read, your apps2sd is working pefectly
I am having the same issue. When I use 'File Manager', I see a folder sd-ext but there is nothing in there.
I've already went through Systems >> Settings >> Manage Applications and moved all my apps (the ones allowed) onto the SD. I don't know where or what folder it's actually being saved in though.
I used ROM Manager to partition the SD card. I even went through 'Terminal' to do the commands that would push it to the ext3 but I'm still not understanding what I'm doing wrong.
I'm on the latest version of MIUI. Can someone please help me?
The MIUI rom has a2sd desactivate by default, you have to put -> a2sd reinstall in a terminal then reboot and finish with -> a2sd cachesd
EDIT: First you have to write -> su
You need to turn it on yourself
Sorry for my bad English!!
anthack01 said:
The MIUI rom has a2sd desactivate by default, you have to put -> a2sd reinstall in a terminal then reboot and finish with -> a2sd cachesd
EDIT: First you have to write -> su
Click to expand...
Click to collapse
Hi anthack01, thanks for the response. So that means any apps that I have moved to the SD already (based on the cupcake process) will have to be redownload again?
Also, if I upgrade to a newer version of MIUI, I would have to do this process via Terminal each and every time?
luvtommie said:
Hi anthack01, thanks for the response. So that means any apps that I have moved to the SD already (based on the cupcake process) will have to be redownload again?
Also, if I upgrade to a newer version of MIUI, I would have to do this process via Terminal each and every time?
Click to expand...
Click to collapse
try miui d2ext version rom.......
m using it with 1gb card partitions n its showing 1gb internal memory .. so i can install lots of application with few hd games too.... if any problem u can pvt me.....
luvtommie said:
Hi anthack01, thanks for the response. So that means any apps that I have moved to the SD already (based on the cupcake process) will have to be redownload again?
Also, if I upgrade to a newer version of MIUI, I would have to do this process via Terminal each and every time?
Click to expand...
Click to collapse
The apps you moved to SD card (FAT32-partition) should be moved back on internal storage.
No, you don't have to do that (as far as I remember).
I have a problem, and i cant manage to solve him, so any help will be apriciated.
I installed Runnymede AIO V6.0.4.3 Special Edition Stable Version
Problem is that every new app that i install goes diractly to the sd-ext. The partition of sd ext is 512, but after installing ROM it size is down to about 80 mb. So after installing few apps sd ext is full and i get an error. Meanwhille i have about 125 mb free on internal storage!
I tried su
a2sd remove, but it tells a2sd not found!
I`m really lost, tried everything for couple of days, so if anyone can help me, please do so...
This ROM requires 1 to 1.5GB ext4.
You might need to extend the sd-ext partition.
The easiest would be to backup your phone, repartition through recovery and reinstall the ROM.
I've been using this ROM for quite some time now and everything works perfectly with a 1GB ext partition.
But the rom is allready installed on sd ext and every other app that i installed later is also on sd ext. But now my sd ext is full, so i want to set as my default location internal memory, but i dont know how to do that... Does anyone have idea?
vnugo said:
But the rom is allready installed on sd ext and every other app that i installed later is also on sd ext. But now my sd ext is full, so i want to set as my default location internal memory, but i dont know how to do that... Does anyone have idea?
Click to expand...
Click to collapse
Sd Ext is "internal memory" - the a2sd etc scripts essentially fool the phone into thinking the sd Ext is part of the internal storage. Therefore increases the data storage for your user apps and is where they will install. This is why you have plenty of internal phone storage, but isn't anything to worry about.
Your actual problem using this Rom is that in common with other later sense Roms, parts of the Rom are also installed to the Sd Ext. This is why the sd Ext size needs to be bigger than 512MB, its filling up because its got parts of Rom plus all your user apps on it.
Sure the Rom thread will recommend what size is, needed. So do a nandroid (include sd Ext if AmonRa recovery), copy sd card contents to pc as backup, repartition using Gparted, copy sd backup back to card, nandroid restore.
Sent from my HTC Desire using Tapatalk 2
You should try ad2sdx in order to increase the number of installed apps.
c90 said:
You should try ad2sdx in order to increase the number of installed apps.
Click to expand...
Click to collapse
Can you explain it little bit to me? I`m not sure how this works.
Do you mean how the script works or what do you have to do to get the script working?
Sent from my HTC Desire using Tapatalk
what do i have to do to get the script working?
Do a backup (titanium, so that you can copy the backupfiles into your harddrive), and repartition the SD card. 1,5 to 2 Gb should be more than enough. Your problem is the same one I had with MIUI-XJ. Like people have said over, the problem is too little space on the partition. If you want to keep your messages and whatever else, there are apps to backup them as well. So... Yeah, 1,5-2GB of ext4 partition, than rewind.
But my sd card is already partitioned. How can i erase sd-ext, so i can partition it again?
Personaly if it was me id boot into recovery then do a backup then wipe/factory reset, wipe dalvik+cache and partition sdcard again (1gb) atleast, flash rom (install) restore backup. But thats just me
Sent from my HTC Desire using xda premium
gomcho said:
This ROM requires 1 to 1.5GB ext4.
You might need to extend the sd-ext partition.
The easiest would be to backup your phone, repartition through recovery and reinstall the ROM.
I've been using this ROM for quite some time now and everything works perfectly with a 1GB ext partition.
Click to expand...
Click to collapse
Woops mist ur post sorry. But i agree
Sent from my HTC Desire using xda premium
Hi,
I have upgraded from 2.3.7 to a JB MOD. I prepared my SD card in gparted with a 500mb FAT32 and the rest as EXT4. I have inserted the SD card and 'setting\storage' only sees the in built 150MB EXT and the 500MB FAT32 on the SD Card but no 3GB EXT4 partition. In terminal I ran a2sd install and on the reboot it said 'optimising' apps and I thought it was moving apps. However, when I install apps from the store they are installed on the in built RAM.
Using app2sd I can't move any apps I used to be able to on 2.3.7.
Can someone please advise?
Thanks
Paul
csjjpm said:
Hi,
I have upgraded from 2.3.7 to a JB MOD. I prepared my SD card in gparted with a 500mb FAT32 and the rest as EXT4. I have inserted the SD card and 'setting\storage' only sees the in built 150MB EXT and the 500MB FAT32 on the SD Card but no 3GB EXT4 partition. In terminal I ran a2sd install and on the reboot it said 'optimising' apps and I thought it was moving apps. However, when I install apps from the store they are installed on the in built RAM.
Using app2sd I can't move any apps I used to be able to on 2.3.7.
Can someone please advise?
Thanks
Paul
Click to expand...
Click to collapse
Here is your most likely scenario because it happened to me: If you created your partition on a PC, for some reason it doesn't work properly (well at least in my case). Then the phone doesn't read the SD card properly. What you should do is upgrade clockswork mod recovery on your phone to the most recent version and create the EXT version using the recovery console by booting into recovery.
Thanks
iyf said:
Here is your most likely scenario because it happened to me: If you created your partition on a PC, for some reason it doesn't work properly (well at least in my case). Then the phone doesn't read the SD card properly. What you should do is upgrade clockswork mod recovery on your phone to the most recent version and create the EXT version using the recovery console by booting into recovery.
Click to expand...
Click to collapse
Hi,
thanks for the reply. I'll see what version I have. It is probably old as it is 15 months since I did the CM 7 install to my phone.
Paul
it should be 500mb ext4 and the rest fat 32, also 1gb ext4 is recommended and dont use ClockWorkMod recovery to partition sdcard, use 4ext recovery instead. CWM makes bad partitions
Sent from my HTC Desire
Is there a specific way around?
jmcclue said:
it should be 500mb ext4 and the rest fat 32, also 1gb ext4 is recommended and dont use ClockWorkMod recovery to partition sdcard, use 4ext recovery instead. CWM makes bad partitions
Sent from my HTC Desire
Click to expand...
Click to collapse
Hi,
I read the FAT32 should be first and the EXT4 the rest. Is that correct?
Paul
csjjpm said:
Hi,
I read the FAT32 should be first and the EXT4 the rest. Is that correct?
Paul
Click to expand...
Click to collapse
yh. i was only quoting coz u said u had 500mb fat 32 and 3gb ext4. the fat 32 should have the biggest size not ext4
Sent from my HTC Desire
jmcclue said:
yh. i was only quoting coz u said u had 500mb fat 32 and 3gb ext4. the fat 32 should have the biggest size not ext4
Sent from my HTC Desire
Click to expand...
Click to collapse
I've redone my card (3GB FAT32/500MB EXT4) but my in built memory seems to run out of space for apps quickly. I thought the SD-Card EXT4 partition was supposed to add more space for apps to the phone.
Is this not true?
csjjpm said:
I've redone my card (3GB FAT32/500MB EXT4) but my in built memory seems to run out of space for apps quickly. I thought the SD-Card EXT4 partition was supposed to add more space for apps to the phone.
Is this not true?
Click to expand...
Click to collapse
what JB did u install? theres acouple i think that u have to activate the a2sd by doing the following in terminal emulator
su
a2sd install
y
n
y
then ur phone reboots and a2sd is activated and apps will go to ur ext4 partition
Sent from my HTC Desire
have done that once
jmcclue said:
what JB did u install? theres acouple i think that u have to activate the a2sd by doing the following in terminal emulator
su
a2sd install
y
n
y
then ur phone reboots and a2sd is activated and apps will go to ur ext4 partition
Sent from my HTC Desire
Click to expand...
Click to collapse
Hi,
I am using Elk759 JB ROM. I did run the a2sd in terminal after redoing the partitions. It reboots and says optimising apps 1/...79 (whatever number). I can't tell if it has moved anything onto the EXT4 partition of my SD card.
I will boot into a live linux and take a look on that partition.
If it isn't working is there anything I can do?
Thanks
Paul
That seems to have worked as I've installed loads of apps and it hasn't complained about space.
Thanks for all your help.
Paul