Related
Hello guys!
I am using this ROM with app2sd and Recovery Amon RA 1.5.2
My question is- when I install some apps from the Market, not from files, do they go to SD card or I have to install there manually?
Thanks a lot!
miragebg said:
Hello guys!
I am using this ROM with app2sd and Recovery Amon RA 1.5.2
My question is- when I install some apps from the Market, not from files, do they go to SD card or I have to install there manually?
Thanks a lot!
Click to expand...
Click to collapse
If you have formatted your sd properly in ext3 partition... then you shouldnt do anything.just installing from market would put it on the card.
one question..
when a app is installed in the ext3 partion, why does the menu with the internal memory lose space? or is this normal?
With a2sd, your /data/app and /data/app-private directories are actually mounted to a filesystem on your sd card. The OS still installs the apps in those directories, which just happen to be on the sd card. It's all transparent to the OS.
The dalvik cache, where virtual machines are created to run your apps, still resides in internal memory, so when you run your new app for the first time, a VM gets created, and the amount of available internal memory goes down. That's normal.
Word of caution: Never remove the SD card while the system is running. Always turn it off first.
marinierb said:
With a2sd, your /data/app and /data/app-private directories are actually mounted to a filesystem on your sd card.
Click to expand...
Click to collapse
technically it is the other way around, the sdcard is mounted to the directories. but other than that you are spot on
so what happend when i'm over the internal memory?
i mean when the internal memory shows 80mb and i am installing a lot off apps, over the 80 mb what happend?^^
does the internal memory goes in the negative?
no just u cant install more apps. the problem is the dalvik cache. i moved the dalvik chache to the sd card too to save more space.
zerofigther said:
so what happend when i'm over the internal memory?
i mean when the internal memory shows 80mb and i am installing a lot off apps, over the 80 mb what happend?^^
does the internal memory goes in the negative?
Click to expand...
Click to collapse
lol yes the memory goes into negative, and the data starts to leak out of your phone!
scnr, i can imagine two scenarios: android tells you that there is no more space left and you can not install more apps, or it will just start to freeze, give force closes, reset itself, stuff like that. i'd guess the first one, it is forseeable that one fills the rather small phone memory, so there should be routines that stop the phone from failing catastrophically. anyone up for a test?
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
So, you are thinking 'not again the *** apps2sd n00b question', but here I am
I did some research on XDA and the rest of the internet though, but nobody seems to have this problem.
I have a rooted Desire with DeFrost 6.0. With it, it is very easy to install your apps on the SD-card. I have only 8 apps on the ROM itself, but those are widgets and apps with notifications like Facebook (notifications don't work if they are installed on de sd-card is my experience).
The rest of my applications are installed on the sd-card (around 80 apps). But the problem is that all apps also have a piece of dalvikCache on the ROM as well. You all know that of course. For instance, I installed Documents To Go (5MB) on the sd-card. It also has 5MB dalvikCache on the ROM, so thats double the price .
Now if people ask here 'is it safe to move the cache to the sd-card', most of you say 'unless you want to show off how much empty space you have on your phone, I would just keep it on the phone'. But I do not have any free space.
With DiskUsage I can see that I have around 150 MB of data: 26MB system data, 15MB free space (and he is already nagging the telephone is running out of space), and more than 100MB of applications, with most of it is dalvikCache.
So is this normal? Is 80 apps really the max you can have?
My biggets app is by the way Documents To Go (5MB), and I had to delete it. So I don't have very big apps.
Just want to know how much apps you guys have
Thanks.
How have you forced the Dalvik Cache to stay on the phone memory and why/how have you copied your widgets on your phone memory?
PS: Do you use an EXT3 Partition or the Froyo legacy A2SD?
It's not unusual to move dalvik cache as well as the app. You will need root though, and then just partition your sd-card and install a rom with a2sd+. The only /data/data will take up space on the phone.
UpSpin said:
How have you forced the Dalvik Cache to stay on the phone memory and why/how have you copied your widgets on your phone memory?
PS: Do you use an EXT3 Partition or the Froyo legacy A2SD?
Click to expand...
Click to collapse
I didn't do anything to force the cache to stay on de phone. But it's normal the dalvikCache is on the phone memory right?
I use defrost 6.0 and in it you can go to settings > applications > manage applicatons, an you can move all your apps to the sd-card. I'm not sure what kind of A2SD that is.
I move any applications with widgets to my phone memory, because otherwise widgets don't work anymore if you reboot your phone.
@mortenmhp: But also a lot of people do not recommend to move the dalvikcache. Is it safe to do?
you're confusing a few things:
APPS2SD:
There are two methods used at the moment.
The Froyo method, made by Google, which you use at the moment. It installs the app on the phone memory and is able to outsource a small amount of data to the FAT32 partition on your SD-card. It does create failures with apps that use widgets or run in the background.
The A2SD+ method, integrated in DeFroST and almost every other custom ROM. You have to create an EXT3 partition on your SD card (use ROM manager for this) and then reflash the rom. After that it gets activated automatically. All apps and also the dalvik cache gets moved on the EXT3 partition on your SD card. You don't have to and you shouldn't move any apps around afterwards with the Froyo A2SD described above. Only some small data gets stored by the apps itself on the internal phone memory.
Moving the dalvik cache is safe. Maybe you confuse it with SWAP? Which isn't necessary on the HTC Desire.
ok, this is a little confusing
I'm running defrost
let's suppose that I installed the firefox app.
the diskusage tool tells me that it takes 13,4 MB in internal memory.
in applications settings, I have the option to move the app to sd card.
When I do this, my available memory does not change (102 mb)
Does that mean that firefox was already on the sd card ?
In that case how do I know what eats up my data storage ?
Thanks for precisions ?
Do you use A2SD+ together with an EXT3 partition.
If so, every app you install will get installed on the EXT3 partition on your SD-card together with the Dalvik cache, instead of your internal phone memory. If you move this app with the Froyo A2SD tool to the SD card then you'll move the app from the EXT3 partition to your FAT32 partition, stupid.
However, every app, while running, creates some temporary data files. Those files remain on the internal phone memory. And maybe Firefox mobile creates some huge data files, but the main app is installed on the EXT3 partition, now, because you moved it with Froyo A2SD, a small part is installed on the EXT3 partition and some part, the moved on the FAT32 partition. The created data remains untouched.
I had 106 MB free internal memory. Then I installed Firefox and still had 106MB free. I started Firefox, 103 MB free.
Diskusage tells me Firefox needs 2.81MB internal memory. 2.81MB of this is data.
In the Android app settings android tells me Firefox occupies 16.19 MB, 13.38 MB for the app, 2.81 MB data.
So those 13.38 MB are located on the EXT3 partition. If I move Firefox now, parts of the 13.38 MB get moved from the SD card to the SD card.
Ah, I get it now. Thank you very much. I did everything you said, so it should be ok now. So there is no need anymore to move apps, with widgets for instance, to the memory of the phone?
Thanks!
If you use app2sd with the ext partition now, then no, you don't have to move any app or widget around, and you shouldn't.
With Quick System Info you can check how much free space is left on your ext partition.
Sent from my HTC Desire using XDA App
I ran my old desire for a year or so on the Supernova Rom, but got bored with the serious lag, It got better from time to time when I cleared the dalvik cache, and reformatted the SD card. But Igave up in the end, wiped everything, reformatted the card again, and loaded Cyanogenmod 7.
It was a revelation.Everything was really snappy, and the Desire was like a new phone again.
But the troubles are returning. I started getting some lag opening apps a week or so ago, and now I am starting to get forced closures too, and the lag is getting worse.
What's going on? Is there anything I can do to stop this from happening?
Don't bother wiping dalvik, it simply rebuilds afterwards which is why it takes so long to boot...
Are you using the ROM with an sd partition, how did you create it? Any particular A2SD script?
Max 2GB ext4 partition should be done using gparted or 4EXT recovery only, not clockworkmod or minitool partition wizard.
(Remember also that your hardware is starting to age, and there are limits / apps which the Desire was never designed to handle)
eddiehk6 said:
Don't bother wiping dalvik, it simply rebuilds afterwards which is why it takes so long to boot...
Are you using the ROM with an sd partition, how did you create it? Any particular A2SD script?
Max 2GB ext4 partition should be done using gparted or 4EXT recovery only, not clockworkmod or minitool partition wizard.
(Remember also that your hardware is starting to age, and there are limits / apps which the Desire was never designed to handle)
Click to expand...
Click to collapse
Thanks
Yes, Iam using an SD partition created with gparted - my laptop runs Linux. I am using S2E.
What's puzzling me is that it ran really fast and snappy to start with, but is now slowing down again. I am getting regular timeouts -but if I choose "wait" its usually OK. But sometimes I get a forcedclose. I don't want to have to keep reinstalling the ROM to keep it fresh!
Trogladyte said:
Thanks
Yes, Iam using an SD partition created with gparted - my laptop runs Linux. I am using S2E.
What's puzzling me is that it ran really fast and snappy to start with, but is now slowing down again. I am getting regular timeouts -but if I choose "wait" its usually OK. But sometimes I get a forcedclose. I don't want to have to keep reinstalling the ROM to keep it fresh!
Click to expand...
Click to collapse
So the partition is made correctly, which is good :good:
Check your S2E settings, what have you moved to the partition?
It works best if you only move apps and dalvik cache to sd-ext. You should keep app data (e.g. saved gaems and app preferences) on your actual internal memory for speed and stability.
You should also be s-off and on cm7r2 hboot to maximise your internal memory if you have many apps. This will work best with the above, and applies regardless of your A2SD setup.
If S2E is already set to move apps and dalvik only, not sure what else it could be. Any other 'tweaks' / scripts / memory managers / task killers which can do more harm than good? Does it happen with any particular app?
Thanks.
Sorry to be so long to reply. Had to take some time out as I snapped the tendon that operates my left thumb. Yes,really.
Anyway. The problem - which is getting worse - may be that I have application data on the SD partition.And S2E won't let me change it - greyed out. Why would that be?
Trogladyte said:
Thanks.
Sorry to be so long to reply. Had to take some time out as I snapped the tendon that operates my left thumb. Yes,really.
Anyway. The problem - which is getting worse - may be that I have application data on the SD partition.And S2E won't let me change it - greyed out. Why would that be?
Click to expand...
Click to collapse
Well at least we're narrowing down the issue. I believe app data on sd-ext is almost certainly the cause of slowdowns. It works much better when stored on your actual internal memory, as nand flash is faster than your sdcard.
No idea why it won't let you change it back, I've never used it myself. I've looked at the Play Store first screenshot. Should be a case of unticking, and rebooting. Do you remember when you first configured it? Did you tick everything?
You may not be able to move it back to internal if you are on stock hboot and you have more than 150MB of app data. i.e. there's not enough free space to move it back?
It may be a case of full wiping and starting from scratch:
- Titanium backup of all apps
- Flash cm7r2 hboot using fastboot
- Full wipe, flash ROM
- Install and configure S2E
- (If above doesn't work, use another app like Darktremor A2SD, tick apps and dalvik only)
- Reboot
- Restore apps
- Check all your partitions using an app like DiskUsage. You should have much less free wasted space on /system, 287MB internal memory (/data) filling up with app data, and your sd-ext filling up with apps and dalvik.
Take it easy with the thumb!
I've tried the several of the 4.4.4 CM11, ominrom, and currently the carbonrom. All of them I'm having trouble getting several, if any, apps to the sd card.
The only apps that will go are messenger and terminal. The rest stay on the internal drive. However, even after flashing, I'm only left with 100mb to install apps on. After I run the gapps, there's not enough space to install more than one or two apps and the phone is pretty slow. It seems to be a common problem but I've done a ton of reading and believe I've followed all the instructions.
-partitioned exactly how the guide says using 4ext. no problems. ( my card is 64GB)
-a2sd via terminal also works
-my sd card shows in storage
Any help would be appreciated.
- How big is the partition, should be max 2GB.
- Install diskusage app, enable root and browse to your sd-ext partition, check that it is being used, should see /app and /dalvik-cache folders if setup correctly
- your internal memory won't read 'internal + sd-ext'. Keep apps on internal to trick them to sd-ext, so do not 'move to sd'
Thanks... I did a 1GB partition and re: your suggestion, it looks like I have everything is in order.
Does that mean the internal memory is just full with the ROM installation? Should I look at using an older/smaller rom?
rspear said:
Thanks... I did a 1GB partition and re: your suggestion, it looks like I have everything is in order.
Does that mean the internal memory is just full with the ROM installation? Should I look at using an older/smaller rom?
Click to expand...
Click to collapse
You have ~1GB space for apps and dalvik-cache.
When it says 100MB remaining, this does not mean you have 100MB left for apps. This will be used for app data like app settings / saved game data, and app caches. It will still fill up the more you install, but more slowly. Again you can use the diskusage app to browse your /data partition.
The limiting factor is that your are still on stock hboot with only ~147MB actual internal memory (the same as before you rooted)
You can flash a different hboot (requires S-OFF), then flash a corresponding older ROM with smaller /system size like CM7 or Oxygen. That along with equivalent a2sd script will give you more app space. You will always eventually run out of space though
Awesome! Thanks for your time.