• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Want more space for apps, what are my options?

A ROM won't modify the internal partitions - that's something you have to do yourself if you want/need to.

Generally the first post of a ROM's thread at XDA will explain any requirements, such as which hboot/memory tables work and the suggested partition sizes. If you have a 1GB ext partition that works for most ROMs (some Sense 3 ROMs are very bloated and might benefit from more, but I reckon that 1GB would be fine for JB).
 
That isn't a Sense ROM - it's based on CyanogenMod. The "Stock/Sense/Data++" in the thread title is telling you which HBOOTs it's compatible with (you'll see there are different download links for the different hboots). Though from the screenshots it looks like they have used a Sense 4 wallpaper :)

Yeah, can't see anything about sd-ext partition size. Well I'm 99.9% sure a Gig will at least cover it.
 
That isn't a Sense ROM - it's based on CyanogenMod. The "Stock/Sense/Data++" in the thread title is telling you which HBOOTs it's compatible with (you'll see there are different download links for the different hboots). Though from the screenshots it looks like they have used a Sense 4 wallpaper :)

Yeah, can't see anything about sd-ext partition size. Well I'm 99.9% sure a Gig will at least cover it.

Ah I see! You've helped me out there, as I thought "Stock/Sense/Data++" meant it was a Sense ROM.

Do you mind telling me what my HBOOT is then now I have S-OFF thanks to AlphaRev.nl live boot disc? It says 0.93 where it used to say 0.80
 
Ah I see! You've helped me out there, as I thought "Stock/Sense/Data++" meant it was a Sense ROM.

Do you mind telling me what my HBOOT is then now I have S-OFF thanks to AlphaRev.nl live boot disc? It says 0.93 where it used to say 0.80

This isn't what it means for HBOOT, it's refering to the size of your system partition. If you install quick system info and put up here what size system partion it reports we'll be able to tell you. Just for reference if it is 147mb, then that's stock. Being S-off, you can fastboot flash different size system partitions and leave more room for apps (the data partition) from Alpharev. ie, HBOOTS.
 
hi all, I realised that even with A2SD I still don't have enough space for apps, so I wondered if anyone can recommend a great stable Data2SD rom? I am going to give it a go because I heard you can get up to 2GB internal memory
 
You can still use Froyo/Gingerbread "move to sd" with an Apps2sd ROM. I know apps are getting bigger all the time but I'm amazed you've filled your partition.

Hadron is likely to know more about data2sd but I never liked relying too heavily on the sd card. I've had too many problems with them.
 
Actually I don't know any more than you do. SUroot used it for a while, and decided that he didn't think it was a good idea. I didn't even have a high-speed card, so decided it definitely wasn't for me. For space I preferred to use a small ROM, custom HBOOT (to get more real internal space) and use a2sd in addition (moving apps with large library components and no widgets to sd the traditional way, as that does save extra space). I'd take AOSP ROMs which were already small and strip out stuff I didn't want, so I was running different AOSP ROMs in system partitions between 75-90 MB. Of course if you really wanted to maximise you could take dGB and add an a2sd script, but since SUroot built that one precisely so as not to need a2sd I always felt that would be disrespectful (though with a 60MB or 65MB hboot and judicious use of move to SD you could fit a surprising amount in with that ROM).

One thing I would check: some a2sd scripts move the dalvik cache, and some don't. Moving dalvik does slow the phone down, but it's a small effect, and unless you are already running a very fast ROM you won't notice it. It does however make a huge difference to space, so if you aren't moving the dalvik cache and are short of space I'd try that first. Don't worry about speed, because data2sd will be slower. AOSP ROMs that don't move dalvik usually have an option to do so (sometimes flashing a different a2sd script).

But yeah, there are limits to what you can do this way, and if you exceed them all I can suggest is get a fast card, a largish partition, and try a few and see what data2sd works. Nandroid first, of course, in case it doesn't work out.

I will confess that I'm not at all unhappy not to have to worry about this stuff any more!
 
You can still use Froyo/Gingerbread "move to sd" with an Apps2sd ROM. I know apps are getting bigger all the time but I'm amazed you've filled your partition.

Hadron is likely to know more about data2sd but I never liked relying too heavily on the sd card. I've had too many problems with them.

OK I will "shelve" the D2SD idea for a while then, I should really get to the bottom of what is going on with my A2SD because I cannot understand how I have filled it, something must be broken/not configured, as I only have like 6 apps!

I ran the "DiskUsage" app which Hadron recommended to someone else and I can't work out what it's telling me but it says Data 290MiB and Applications 285MiB ..... I genuinally think something is wrong with the A2SD part, because on the MildWild 9 I never had any problems with space, I seemed to have my full 1GB.
 
Is this still with VJ's ROM you linked a few posts earlier? If you followed the a2sd install instructions in that thread it should have moved your dalvik cache to sd-ext, but not app data (a2sd install followed by Y Y Y rather than Y N Y should move app data, so if you are tempted to test data2sd you could take a nandroid then try that).

To understand what's going on, maybe try just using a root-capable file browser (root explorer, ES, etc) and looking at /sd-ext and seeing what is actually on there?
 
Is this still with VJ's ROM you linked a few posts earlier? If you followed the a2sd install instructions in that thread it should have moved your dalvik cache to sd-ext, but not app data (a2sd install followed by Y Y Y rather than Y N Y should move app data, so if you are tempted to test data2sd you could take a nandroid then try that).

To understand what's going on, maybe try just using a root-capable file browser (root explorer, ES, etc) and looking at /sd-ext and seeing what is actually on there?

Yes indeed with the same ROM. I didn't touch anything after I flashed it as I asked in the thread and was explicitly told that the installation enabled A2SD.

You've got a good point about seeing which files are where, I will try that. I got impatient this afternoon and installed MildWild 9.5 and I've just been like a kid in a sweet shop on the Play Store and got everything I can, and the internal memory has dropped by 3-4MB so I have to assume it is working on this ROM and somehow wasn't on the previous 007 one. Being a techy I would feel more comfortable knowing why it wasn't working before. I can only presume that I should have ran some commands at the terminal to get A2SD working
 
Back
Top Bottom