I am very confused by the current situation with having additional space for apps on Cyanogen 6.1 RC1
I was previously running 6.0.2 and used the DarkTremors A2SD with a 512Mb partition and all worked well without issue.
When I attempted to upgrade to 6.1 RC1 my Desire hung at the operator screen and wouldn't move any further.
After doing some reading I was led to believe that this was due to EXT3 partitons not being supported on 6.1 and that the 'prefered' method of gaining additional space was to use CustomMDT.
I followed the instructions on
http://forum.cyanogenmod.com/topic/...nd-installing-cyanogenmod6-gapps-cmtd-dta2sd/
Where I
blew away the 512Mb partition (now all FAT32),
Copied the mtdpartmap.txt (for firerats)
flashed the MTD recovery,
wiped cache, system and boot
Rebooted
Flashed 6.1 RC1
Flashed google apps
Flashed the MTD boot
Rebooted
When I restart however I only have 90mb of internal phone storage available.
I even tried using Daedelus82's but that made no difference.
I must be going wrong somewhere....
Can anyone help????
DarkTremors app2sd script posted in the nightly CM thread worked just fine for me. Only thing you have to do manually is putting dalvik cache to SD afterwards and you get full 144MB free space.
thed0g said:
DarkTremors app2sd script posted in the nightly CM thread worked just fine for me. Only thing you have to do manually is putting dalvik cache to SD afterwards and you get full 144MB free space.
Click to expand...
Click to collapse
Can you tell me how you do this please?
You need an ext3 partition like before and flash this DT script after ROM install :
http://dl.dropbox.com/u/12542/dtapps2sd-2.7.5-rc1-cm6-bravo-signed.zip
then when booted, in Terminal emulator type:
su
a2sd cachesd (move dalvik to sd card)
Phone will reboot after and there should be more space available after (144mb on Desire stock mtd partitions). Works perfectly for me.
really strange. It worked no problem at all when I wiped and reinstalled everything.
Wonder why it wouldn't allow me to upgrade.....
Thanks the help! Back up and running
Related
Hi I just rooted my phone using a method from another website ( not sure if i can post the website as that is xda-developers policy.. )
It rooted fine and it loaded back and i could use my phone.
Then I try to install app sd, i follow a guide to the letter, and once it rebooted it just gets stuck at the htc white screen. I've been waiting for 10 minutes and nothing loads. Is it bricked? I can still go into bootloader or whatever but how do i get it back? Is it the SD card?
I'm using a 8GB sdhc card Kingston Class 4. If it has to do with anything. What do i do? I really need to use the phone!!!
What rom did you install?
Does the rom you have not already have Apps2SD integrated? (check thread title of rom and change log notes to find out)
Are you able to get into Recovery Mode?
If you did not flash a Froyo only (not Sense UI) rom, did you forget to partition your SD card before rebooting?
Sent from my HTC Desire using XDA App
i install whatever rom that came with the package of rooting from android.modaco.com. I don't knwo what it is but i'm guessing its some 2.1 rom.
No i think the roms was used jsut for rom, so i dont' think app2 sd is integrated. I am able to get into recovery mode, but don't know what to do it from there.
I actually partition the sd card and did the ext2 to et 3 and after it finished i rebooted and it just get stuck on this screen. What i did now is install a custom rom on it and it boots. However I want to load back just the htc rom that came with the root package and add Apps 2 SD
On MoDaCo, there should be an option to download a custom 2.1 based rom that already includes A2SD in the downloads section. Try downloading that rom, in Recovery Mode, do a full wipe, flash the rom, and while still in Recovery Mode, partition your SD card with 0 MB swap, ext2 size of 512 MB, rest to FAT32. Then convert ext2 to ext3.
If you still have the same issue, report back here bud.
Just make sure it is a 2.1 based rom that you are attempting to flash with A2SD. If it is a 2.2 Froyo based rom without Sense, then you do not partition your SD card at all as it is setup differently.
does your sd card have an ext partition? if your using an apps2sd with a dalvik cache script, your fone wont boot without a ext partiton because your fone has nowhere to put the dalvik cache lol
Thank to the two of you for your help. I was planning to use 2.1 as I only wanted a2Sd because i ran out of space very easily installing apps and games.
Anyways i wipe and install the official froyo sense one from adamg from here in the desire forums. Now i'm confused, he saids he has google's app2 sd, legacy app2 sd, and davlik cache app2 sd..
Can u guys explain the differences? What is app 2 sd+ ??
I understand google's one is the one that comes with froyo that it only works if the developers of the games and apps code it in, or else it wont' move to the sd card. Legacy is the one which uses the ext3 partition ( which i still have btw.. ) but i don't know how to use that one even though its already preinstalled. I have no idea about davlik cache except that i had to clear it before i install app2sd.. and i'm in the blind for a2sd+ ...
Thanks
I read somewhere minimum class of sd should be 6 for apps2sd. Also had a freeze once, i panicked then took battery out, went into recovery and just re-installed ROM and it worked after that.
@Supergluey basically, a2sd just moves the apps, while a2sd+ also moves the dalvik cache.
The Froyo implementation is pretty lame (only moves apps if allowed by creator) and is best ignored.
If your rom comes with the legacy a2sd (not Froyo native) then you can partition your sd card in Recovery Mode by setting a 0 MB swap size, an ext2 size (dedicated for apps) of 512 MB, and remaining space to the FAT32 file system (mass storage space).
You then convert ext2 to ext3 while still in Recovery Mode.
Explanation about how Dalvik cache works: when Android OS starts up, the DalvikVM looks through all of your applications (.apk files) and frameworks, and builds a tree of dependencies. It uses this dependency tree to optimise the bytecode for every application and stores it in the Dalvik cache. The applications are then run using the optimised bytecode. This is why when you install a new ROM, sometimes it takes a very long time to boot for the first time. Any time an application (or framework library) changes, it's re-optimised and the cache is updated.
Sent from my HTC Desire using XDA App
MasDroid said:
@Supergluey basically, a2sd just moves the apps, while a2sd+ also moves the dalvik cache.
The Froyo implementation is pretty lame (only moves apps if allowed by creator) and is best ignored.
If your rom comes with the legacy a2sd (not Froyo native) then you can partition your sd card in Recovery Mode by setting a 0 MB swap size, an ext2 size (dedicated for apps) of 512 MB, and remaining space to the FAT32 file system (mass storage space).
You then convert ext2 to ext3 while still in Recovery Mode.
Explanation about how Dalvik cache works: when Android OS starts up, the DalvikVM looks through all of your applications (.apk files) and frameworks, and builds a tree of dependencies. It uses this dependency tree to optimise the bytecode for every application and stores it in the Dalvik cache. The applications are then run using the optimised bytecode. This is why when you install a new ROM, sometimes it takes a very long time to boot for the first time. Any time an application (or framework library) changes, it's re-optimised and the cache is updated.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Thanks MasDroid. I get the differences now. But i have a problem. So like my last post I install the official froyo rom that is posted on here by AdamG. I loved it cause its based off some hong kong test rom and i'm in HK However, he added more features to it such as the apps to sd (not the froyo one ) and davlik cache app to sd.
I formatted my 8GB with the swap file , fat 32 and ext 2 converted to ext 3 respectively to the sizes you stated. However whenever i install apps it still goes to the internal memory! I tried different partitions and it still doesn't' work! I tried wiping everything and re-flashing the rom and it doesn't' work. I also tried forcing it to install to external but all apps just fails to install. I tried reformat and remove all partitions and re partition again once through recovery mode and another through the android sdk and using adb. Is it the sd card problem?
When i first rooted my phone, with defrost and then later changing to devillian. It worked. Apps were installed on sd card but i changed roms because i found out it was dragging the internal memory as well. So i would still gt the "I have no space" message. What can I be doing wrong?
ruisinho said:
I read somewhere minimum class of sd should be 6 for apps2sd.
Click to expand...
Click to collapse
Definitely not true.
I use Apps2SD on my 16gb Sandisk Class 2 card and never have any lag whatsoever.
Regards,
Dave
foxmeister said:
Definitely not true.
I use Apps2SD on my 16gb Sandisk Class 2 card and never have any lag whatsoever.
Click to expand...
Click to collapse
+1
16 gig Sandisk class 2, absolutely no difference or lag comparing to internal memory
Hi,
I have a problem with installing TitaniumBackup Pro (and maybe more).
I have a Desire (root, S-ON) and used Oxygen. When I tried to install Google Maps I got an error that there isn't enough space and installation failed. Then I switched to GingerVillain (did a full wipe between) where Google Maps was included. I tried to install my Titanium Backup Pro Key and now here the installation fails. On internal memory, cache and ext3 on the SD (1024MB) is enough free space. If I try to update Google Maps over the market, it also fails with the error that there isn't enough space.
What can I do, I don't necessarily want to S-OFF for partitioning layouts, or can it possible be a problem with the SD Card (1st partition 1024MB ext3, rest FAT32)
Thx in advance for help
Phone Stats:
HTC Desire Pvt4
Root
S-ON
GingerVillain 2.2 (altough the problem also exists with Oxygen)
floxyz said:
Hi,
On internal memory, cache and ext3 on the SD (1024MB) is enough free space.
Click to expand...
Click to collapse
Can I ask how much free space in each right now?
According to A2SDGUI (free/total):
internal: 118MB/150MB
SD-EXT: 718MB/914MB
/cache: 32MB/40MB
I never got the total of cache higher, even with moving it around with an other rom.
But with the current one I did nothing like that, just wiped, install the rom and tried to install and update all my apps.
First partition should never be ext. it should be fat 32.second should be ext.
All a2sd/data2sd scripts refer to the second partition
Swyped with my Starburst Classic based Desire with Intelligent Data2sd
Thank you!
I will try to repartition, wipe and then install everything from the beginning.
I hope this will work.
No reason why it shouldn't
Swyped with my Starburst Classic based Desire with Intelligent Data2sd
Two things...
1.) I partitoned with AmonRA (also in the first step), so everything should be ok with the partition layout.
2.) I used the repair ext function of AmonRA and suddenly the installation works. I'm not sure if the now working installation and the repairing are connected but I see no need now to restart with wiping and flashing all over again.
Thanks for the replies anyway!
As I need more space on my internal memory I'm messing around with app2sd and came across a couple of questions:
which a2sd script is preferred on cm7 2.3.4: darktremor or firerat?
which method is preferred: move apps or move dalvik cache?
I formatted my sd card with two primary partitions so far: 1st one is fat and second one (512 MB) is ext3 for a2sd. rather use ext3 or ext4?
Thanks for any help.
Best regards,
SoulStyle
I didn't install any A2SD scripts and I can move anything to the SD card.
(cm 7.0.3)
1) I have been using Darktremor, and it works well.
2) Depends on your SD Card. If it is fast enough, you can move the dalvik as well. Personally, I move apps only.
3) Although EXT4 is supposed to be faster, on the Wildfire, the gains are probably negligible, if any,.
Thanks for the input
My first try with DTa2sd beta 04 went terribly wrong. After install some apps have simply gone missing and a a2sd remove didn't bring them back. The following a2sd reinstall gave my phone the final punch and left it unbootable and I had to pull the battery and do a complete reinstall. So I learned the hard way that nandroid and titanium backups do serve a purpose
Any idea what could have gone wrong?
Btw, is the a2sd option in cyanogen 7.1 settings compatible with DTa2sd?
SoulStyle said:
The following a2sd reinstall gave my phone the final punch and left it unbootable and I had to pull the battery and do a complete reinstall.
Click to expand...
Click to collapse
Same thing with me as well.
I tried partitioning with rom manager and recovery. Tried different ext sizes (128 , 256, 1024) with 0 MB swap. Partitioning is OK. But after running the DTApps2sd script from recovery, the phone gets stuck on the splash screen. Don't know what's wrong. Still not solved.
Use an older version. (Atleast Beta 3, or the last stable version). Beta 4 causes issues.
OK XDA I rarely post, But today I just need a little help. So I'm running Synergy RC1 and I can't seem to get DTA2SD beta5 script running for the life of me. I've only got about 49.95mb of internal storage left. I have a 8gb partitioned with 1gb of EXT3, A 32mb swap and the rest is Fat 32. I have flashed A2SD Via Recovery and Synergy updater. I have to to be missing something. I've tried running reinstall commands from ADB and terminal, No go. The Script keep telling me it found the EXT partition but its not mounted, never gets any further than telling my it found a EXT partition but its not mounted. It never finish's. Can Someone please P.M me or reply back here. I'd like to get this working.
EDIT:I have switched to 7-13 Nightly synergy From Goo-inside. All is right as rain. No problems. MYN should update his post, RC1 A2SD is not working. What a Long Night.
Did you flash the DT A2SD from DT's thread or did you use the Synergy Updater?? Because that's what you have to use, since the script is modified for Synergy
I flashed the one from synergy updater.
Sent from my PC36100 using XDA Premium App
If you've already partitioned your SD card with an ext3 partition, you shouldn't need the DT a2sd script because the Syngery RC1 rom comes with the CM a2sd script built in. With that in mind, as soon as you install apps, they will be stored in the ext3 partition. I currently have 341 MB of available internal storage space and I am currently using the Synergy RC 1 rom with the built in a2sd script.
Maybe I'm going to have to start from scratch, I partitioned post install and the built in a2sd didn't pick up on my ext 3. Was hoping not to have to start from scratch.which is why I tried installing the beta 5 from synergy updater. I will start with a clean fresh install tonight after a nand backup.
On the other hand anyone posting here tried the synergy kingdom rom? Does it run as smooth as synergy rc1?
Sent from my PC36100 using XDA Premium App
ugh had this problem with the kingdom/synergy rom couldn't take it and went back to kingdom revolution rom of virus's cuz at least it worked there and left my phone running great
Still no luck.
To no avail, I just can't seem to get this working. I've re-flashed my recovery, repartitioned to removed all partitions, run error check on SD card in windows. I've followed the "How-to" to a "T" even though I've been doing this since the days of my hero. Figured it couldn't hurt to follow a guide. I'm at my wits end. I just don't understand why this isn't working. I'm going to format, re-partition 128 swap, 1024 EXT3, wipe everything, fresh clean bare bones install and try using the A2SD from synergy updater. But I think I'm going to flash it before I boot for first time. If anyone can shed some light in my direction I would be really greatful
Wire P. Snyder said:
To no avail, I just can't seem to get this working. I've re-flashed my recovery, repartitioned to removed all partitions, run error check on SD card in windows. I've followed the "How-to" to a "T" even though I've been doing this since the days of my hero. Figured it couldn't hurt to follow a guide. I'm at my wits end. I just don't understand why this isn't working. I'm going to format, re-partition 128 swap, 1024 EXT3, wipe everything, fresh clean bare bones install and try using the A2SD from synergy updater. But I think I'm going to flash it before I boot for first time. If anyone can shed some light in my direction I would be really greatful
Click to expand...
Click to collapse
Still nothing. Hmm. Well I'm stumped and out of idea's. Someone with a little more dev experience please shoot me a P.M. I know if I'm having problems getting this to work. There are plenty more out there in the same boat.
TBH, this is why I left Synergy ROM. I could see that my apps were on the SD Card, so that part worked, but running any a2sd commands, like a2sd reswap and I'd get A2SD: Not Found, so I couldn't start swap, even though A2SD Check showed DT was installed and A2SD Reinstall worked to move my apps.
Wire P. Snyder said:
To no avail, I just can't seem to get this working. I've re-flashed my recovery, repartitioned to removed all partitions, run error check on SD card in windows. I've followed the "How-to" to a "T" even though I've been doing this since the days of my hero. Figured it couldn't hurt to follow a guide. I'm at my wits end. I just don't understand why this isn't working. I'm going to format, re-partition 128 swap, 1024 EXT3, wipe everything, fresh clean bare bones install and try using the A2SD from synergy updater. But I think I'm going to flash it before I boot for first time. If anyone can shed some light in my direction I would be really greatful
Click to expand...
Click to collapse
Try this: zero for the SWAP size, 1024 or 2048 for the ext3 and the rest for FAT. Afterwards, go to the wipe menu and wipe EVERYTHING in it except the SD card and then flash the rom. This *should* work for you.
posting & replying via my EVO 4G
dougjamal said:
Try this: zero for the SWAP size, 1024 or 2048 for the ext3 and the rest for FAT. Afterwards, go to the wipe menu and wipe EVERYTHING in it except the SD card and then flash the rom. This *should* work for you.
posting & replying via my EVO 4G
Click to expand...
Click to collapse
I tired that Several times Last night, I tired almost everything I could think of but no worries, I flashed The latest nightly 260+mb free, This thing is running snappy as hell too! Nightly missing the task manager from quick settings and I cant login in to HTC Hub but those are the only two problems I have run in to so far.
Hello folks
My issue is this:
GSM Desire
Class 10 SD
4ext Recovery (used to partition sd)
I'm trying to install various JB roms. The a2sd never works. When I download the gui it says it can't start because either no scripts, no partition, etc.
I've tried a lot of Roms including ones where a2sd is meant to be built in. I've also installed from Terminal and it seems to optimise all the apps on reboot but internal memory is still the standard and apps still in Internal (it's meant to go up to my ext4 partition right? it's about 1.5G)
I've worked my way through these (can't post the link but its the Alchemister custom rom blogspot for the Desire.)
each one the same problem.
Checkext and diskspace both see the partition. Strangely, L2SD seems to crash each of the Roms if I install it.
So far the only Rom to work correctly is a Supernova Gingerbread one. It gave me the 1.5G. So, the partition appears to be good.
Both are primary too.
I would like a JB one as the supernova rom is very laggy.
Running a Miui at the moment and also really liked the Touchwiz one on the list as well.
I only started doing this two days ago as my contract was up so I'm very new to this. Any help would be greatly appreciated. Thanks.
Let's make sure your partition works. Download the rom in my sig. It's a very stable rom, that has a script integrated that moves data/app and dalvik cache to sd-ext. Flash it, then install a few apps. If the internal storage gets filled up quickly, then it probably is a partition fault, and you'll have to repartition.
If it does work, then you did something wrong when you installed the other roms.
Are you sure you did a full wipe before installing all those roms?
a2sd problem solved
Thankyou Andoo,
I've got it working now. It was two things that were confusing me. They were mentioned in the partitioning guide that you attached.
1. I was not aware that you were not meant to see the full size of your Ext4 partition as internal storage. For anyone else with this problem, you can see how your Ext partition is being used if you download Freespace app from the market. I had assumed that you could see the ext as internal space as that is what a few of the earlier Roms i looked at said that that would happen. (it does for the Supernova Rom)
2. When I was downloading and installing apps such as FB or Maps, they were still taking a big chunk out of my internal memory so I assumed that it wasn't working. However, when I chose to put the data as well as cache to the Ext, it hardly took anything out of my internal storage at all. I have a class 10 card and so far everything seems fairly brisk and responsive. I Chose Y/Y/Y when installing a2sd from Terminal instead of the recommended Y/N/Y.
If things start to get slow, I might try the Mount2SD script in the attachment -I think this allows you to chose individual large apps to go to Ext instead of all of them.
Thanks again for your help. I now have a useful and quick phone again.
PS the MildWild 9.5 Rom you suggested - I hadinstalled this before and had real problems with the WiFi disconnecting every couple of seconds and the same thing happened again when I installed from your link. I'm using the Touchwiz at the moment and all seems well.
abaaaabbbb63 said:
Let's make sure your partition works. Download the rom in my sig. It's a very stable rom, that has a script integrated that moves data/app and dalvik cache to sd-ext. Flash it, then install a few apps. If the internal storage gets filled up quickly, then it probably is a partition fault, and you'll have to repartition.
If it does work, then you did something wrong when you installed the other roms.
Are you sure you did a full wipe before installing all those roms?
Click to expand...
Click to collapse