Develop Bugs

[Q] a2sd confusion

I wiped my SD card, partitioned it with a 512MB ext3 (via Amon RA), reflashed cyanogen 7.2 ...
I thought CM had 'built in' a2sd -> ext, but even after moving apps to SD, my ext partition is still totally empty!
It's actually moving my apps to .android_secure on the FAT partition!
And installing apps is filling up my internal memory ...
Do I need to enable ext usage in CM?
Help!

im not sure about cm, but i know in other roms iv used you had to use terminal and type the following:
su[ENTER]
a2sd reinstall[ENTER]
if your not sure you can always flash dt a2sd and do the above and go from there. Also... why only 512mb ext3 partition? i got a 32gb card and used a 3gb ext3 partition. i wanted to make sure i NEVER ran out of space for apps. I dont remember if i saw it there, did you upgrade your ext2 to an ext3 partition via AMON-RA? in case you need dt a2sd here is the link.
http://forum.xda-developers.com/showthread.php?t=715938

I see, thanks, didn't know had to 'activate' it.
But in the meantime, I installed S2E (from Market) – now my ext is filling up –*but my internal is still down to 83MB!

I think I figured it out -- it's my app data (/data/data 130MB) and dalvik cache (/data/dalvik-cache 107MB) that are still internal.

Question about [ROM][Jan 23. 2013] MildWild V-4.9 JG

Hello, I had older version of this ROM , and there was a function in Settings>Applications, to move application to SD card/To phone/To SD-ext.
Now in the newest version of this ROM there is no such thing as Move to SD-ext. Maybe someone could tell me how can I move apps to sd-ext ?

Mildwild removed this option from around V-4.3, which is why I'm still on that rom. It allowed you to choose apps on internal, sd-ext or classic froyo apps2sd.
The latest version moves apps and dalvik cache to sd-ext automatically, you don't have to do anything. As long as you have a correctly partitioned sd card (4EXT or gparted), it will work.
Keep apps on internal to trick them to sd-ext, i.e. don't 'move to SD' . Also use cm7r2 hboot to maximise space as well.
If you install another app like 'diskusage', it will tell you how all your partitions are being used.

eddiehk6 said:
Mildwild removed this option from around V-4.3, which is why I'm still on that rom. It allowed you to choose apps on internal, sd-ext or classic froyo apps2sd.
The latest version moves apps and dalvik cache to sd-ext automatically, you don't have to do anything. As long as you have a correctly partitioned sd card (4EXT or gparted), it will work.
Keep apps on internal to trick them to sd-ext, i.e. don't 'move to SD' . Also use cm7r2 hboot to maximise space as well.
If you install another app like 'diskusage', it will tell you how all your partitions are being used.
Click to expand...
Click to collapse
I partitioned my card correctly, because on earlier version it worked, but now it shows me o 65mb used and 82mb free. My partition is 1GB. So i assume something is wrong because apps are not moved to sd-ext automatically ?

MisterMonitor said:
I partitioned my card correctly, because on earlier version it worked, but now it shows me o 65mb used and 82mb free. My partition is 1GB. So i assume something is wrong because apps are not moved to sd-ext automatically ?
Click to expand...
Click to collapse
Install diskusage like I said, you should see your sd-ext partition being filled up. You need to understand what is stored where.Your user app apks and dalvik cache should be automatically moved to sd-ext, and app data should be on internal memory (data partition),
However, 65MB used and 82MB free is your internal memory correct? This adds up to 147MB, which means you are on stock hboot. With diskusage look at your system partition, on stock hboot you will see a lot of free space on /system which is completely wasted. You should change hboot to cm7r2 to use space more efficiently.
Your rom system size is ~140MB. On stock hboot, your system size is 250MB, so you waste 110MB. cmr72 hboot has 145MB system, so you waste only 5MB. The saved space is converted to extra internal memory, 147MB increases to 287MB
What I believe is that your sd-ext partition is working fine, except that your internal memory (/data) appears to be filling up quickly because it is only 147MB, when when it should be 287MB total by simply switching to cm7r2. 287MB should be filled up by app data only (not apps or dalvik), which is plenty.
To change hboot you need to be s-off:
- Nandroid backup
- Get the hboot from alpharev.nl, then flash cm7r2 hboot using fastboot, guide here
- Reboot back to recovery, full wipe and restore nandroid.

[Q] Link2sd not working for me

hi link2sd appears that it not working in my phone
1- i rooted my phone (GALAXY ACE s5830i)
2- i used cwm recovery to partation the 4gb sd card into 1024 mb and 0 swap (ext 3)
the proplem is when i link an apllicaton to sd my internal memory decrease not increasing
and when press move to sd it works but link to sd not works as i said in the previous
so can any one help me ?????
i need link2sd because the internal memory is 190 mb only
:crying::crying::crying::crying::crying::crying::crying::crying:
so if you can help just help me

mazen atef said:
hi link2sd appears that it not working in my phone
1- i rooted my phone (GALAXY ACE s5830i)
2- i used cwm recovery to partation the 4gb sd card into 1024 mb and 0 swap (ext 3)
the proplem is when i link an apllicaton to sd my internal memory decrease not increasing
and when press move to sd it works but link to sd not works as i said in the previous
so can any one help me ?????
i need link2sd because the internal memory is 190 mb only
:crying::crying::crying::crying::crying::crying::crying::crying:
so if you can help just help me
Click to expand...
Click to collapse
So why do you think that posting your Galaxy Ace problem in the HTC Desire Q&As section is a good idea? Try asking in your phone's section.
Anyhow, try partitioning with Gparted.

Remember each device has it's own section....so you should have posted here
However, I also rooted that phone for my sister, link2sd is not a good method. You actually no longer need to 'move to SD', as that does move it to the sd-ext partition but the FAT32 partition. You have to keep it on internal, link it using the app, then reboot I think, kind of clumsy
Regardless, i gave up on link2sd because it wasn't an efficient method for me, especially when apps got updated, and memory still ran out.
I found CronMod INT2EXT script worked best.
- Backup your sd card
- Repartition your sd card using gparted (find a video guide), ~1.5GB ext4 partition, the rest FAT32, no swap.
- Copy contents back to sd card
- Titanium backup or similar all apps if necessary
- Nandroid backup (just in case)
- Full wipe and reinstall ROM, reboot
- Reboot back into recovery, flash INT2EXT4+ script, as it leaves data on internal for better speed
- Now restore your apps etc. Don't 'Move to SD' with this script either. Just keep on internal will trick them to sd-ext.
- Install an app such as 'DiskUsage' to browse your partitions to check they're working correctly.

Thank You
eddiehk6 said:
Remember each device has it's own section....so you should have posted here
However, I also rooted that phone for my sister, link2sd is not a good method. You actually no longer need to 'move to SD', as that does move it to the sd-ext partition but the FAT32 partition. You have to keep it on internal, link it using the app, then reboot I think, kind of clumsy
Regardless, i gave up on link2sd because it wasn't an efficient method for me, especially when apps got updated, and memory still ran out.
I found CronMod INT2EXT script worked best.
- Backup your sd card
- Repartition your sd card using gparted (find a video guide), ~1.5GB ext4 partition, the rest FAT32, no swap.
- Copy contents back to sd card
- Titanium backup or similar all apps if necessary
- Nandroid backup (just in case)
- Full wipe and reinstall ROM, reboot
- Reboot back into recovery, flash INT2EXT4+ script, as it leaves data on internal for better speed
- Now restore your apps etc. Don't 'Move to SD' with this script either. Just keep on internal will trick them to sd-ext.
- Install an app such as 'DiskUsage' to browse your partitions to check they're working correctly.
Click to expand...
Click to collapse
Thank you for help also i posted my question in the wrong forum

[Q] Best ROM for space

Hi,
I've had to bring my Desire out of retirement until the end of my contract.
I am currently running Cyanogen Mod 10.0.0 but I am down to little space and apps don't update and I can't add new ones.
I have an SD card with 1 GB ext3 storage on it.
Which is the best configuration/ROM to allow me to have enough space to download all the apps I want without significant lag please?
Cheers

Do you understand current configuration first to understand why you're low on space?
- Have you run the A2SD commands from terminal emulator i.e. moved apps and dalvik to sd-ext?
- Is your /data (internal memory) partition full, or is it your 1GB sd-ext? Could you create a bigger partition?
- Check your /data partition with an app like 'DiskUsage', you may have some updated system apps like Play Store on /data which you could move back to /system.
If you have genuinely run out of space on that ROM, the limiting issue is stock hboot which I assume you are running. Even with apps and dalvik moved to sd-ext, you only have 147MB space for app data which can still run out.
Switch to a different hboot (requires s-off) with smaller system, and a ROM which moves apps and dalvik to sd-ext. I recommend one of Mildwild's, MW10 based on redux will fit onto OxygenR2 hboot with 332MB /data partition for instance.
I also recommend to repartition your sdcard with max 2GB ext4 partition if you have enough spare sd space. ext4 is also slightly faster than ext3.

eddiehk6 said:
Do you understand current configuration first to understand why you're low on space?
- Have you run the A2SD commands from terminal emulator i.e. moved apps and dalvik to sd-ext?
- Is your /data (internal memory) partition full, or is it your 1GB sd-ext? Could you create a bigger partition?
- Check your /data partition with an app like 'DiskUsage', you may have some updated system apps like Play Store on /data which you could move back to /system.
If you have genuinely run out of space on that ROM, the limiting issue is stock hboot which I assume you are running. Even with apps and dalvik moved to sd-ext, you only have 147MB space for app data which can still run out.
Switch to a different hboot (requires s-off) with smaller system, and a ROM which moves apps and dalvik to sd-ext. I recommend one of Mildwild's, MW10 based on redux will fit onto OxygenR2 hboot with 332MB /data partition for instance.
I also recommend to repartition your sdcard with max 2GB ext4 partition if you have enough spare sd space. ext4 is also slightly faster than ext3.
Click to expand...
Click to collapse
Thanks,
I'll try to deal with everything.
apps and dalvik have been moved using terminal emulator and yes, it's the 147MB that is the issue, not the ext3.
I have s-on
So if I have the s-off can I incorporate my ext3 or ext4 with internal storage to create a much bigger internal storage?
Cheers

PoshCat1 said:
Thanks,
I'll try to deal with everything.
apps and dalvik have been moved using terminal emulator and yes, it's the 147MB that is the issue, not the ext3.
I have s-on
So if I have the s-off can I incorporate my ext3 or ext4 with internal storage to create a much bigger internal storage?
Cheers
Click to expand...
Click to collapse
Not quite
S-OFF is merely an enabler, in this case it allows you to change hboot.
It has nothing to do with your sd-ext partition. This is handled by the A2SD script. Your internal memory still won't read 'internal + sd-ext' like it is currently, but the sd-ext is still doing its job.
What I would recommend:
- Titanium backup all user apps, backup contacts to Google, SMS with SMS backup and restore if you want
- Flash 2.3.3. RUU from here, put PB99IMG.zip on root of sd card and boot to bootloader, accept it when found
- Run Revolutionary to gain s-off (search for guides)
- Flash 4EXT recovery (see my sig, use fastboot or 4EXT app)
- Switch hboot using fastboot (to OxygenR2 if using Mildwild 10)
- Reboot to recovery, full wipe ("wipe all partitions except sd card" option)
- Flash ROM.zip
- Restore

eddiehk6 said:
Not quite
S-OFF is merely an enabler, in this case it allows you to change hboot.
It has nothing to do with your sd-ext partition. This is handled by the A2SD script. Your internal memory still won't read 'internal + sd-ext' like it is currently, but the sd-ext is still doing its job.
What I would recommend:
- Titanium backup all user apps, backup contacts to Google, SMS with SMS backup and restore if you want
- Flash 2.3.3. RUU from here, put PB99IMG.zip on root of sd card and boot to bootloader, accept it when found
- Run Revolutionary to gain s-off (search for guides)
- Flash 4EXT recovery (see my sig, use fastboot or 4EXT app)
- Switch hboot using fastboot (to OxygenR2 if using Mildwild 10)
- Reboot to recovery, full wipe ("wipe all partitions except sd card" option)
- Flash ROM.zip
- Restore
Click to expand...
Click to collapse
Thanks,
I will try that when I get some time.

[Q] Internal memory and sd ext

hello guys
im using CyanoMod007 (CM10.1.2 | JB 4.2.2 | A2Ext+) [STOCK | CM7] [v31 | 07/08/13] rom and i have a problem.
i though my apps would go in the 1gb sd ext partition i created, intead i have my internal memory with 148mb almost full. what have i done wrong?

How did you partition your sdcard? Should be done with 4EXT recovery or gparted only, not minitool or clockworkmod recovery
Your internal memory will read 148mb because you're still on stock hboot.
You can increase it slightly by changing to cm7 hboot (requires s-off) and installing the cm7 version if the ROM.
However your internal memory still won't read 'internal + sd-ext'. You may need to activate a2sd using terminal commands, should be in the ROM op or search the thread.
Move apps and dalvik to sd-ext, most of the time you need to keep apps on internal to trick them to sd-ext (do not 'move to sd')
Finally check all your partitions by installing DiskUsage app and see how your /sd-ext and /data (internal memory) is filling up, understand HOW your memory is being used

eddiehk6 said:
How did you partition your sdcard? Should be done with 4EXT recovery or gparted only, not minitool or clockworkmod recovery
Your internal memory will read 148mb because you're still on stock hboot.
You can increase it slightly by changing to cm7 hboot (requires s-off) and installing the cm7 version if the ROM.
However your internal memory still won't read 'internal + sd-ext'. You may need to activate a2sd using terminal commands, should be in the ROM op or search the thread.
Move apps and dalvik to sd-ext, most of the time you need to keep apps on internal to trick them to sd-ext (do not 'move to sd')
Finally check all your partitions by installing DiskUsage app and see how your /sd-ext and /data (internal memory) is filling up, understand HOW your memory is being used
Click to expand...
Click to collapse
tnks for your reply mate...
im still new to all this, what i can tell you is that i used 4ext to partition the card and then recovered a backup i had. its s-off.

shaca said:
tnks for your reply mate...
im still new to all this, what i can tell you is that i used 4ext to partition the card and then recovered a backup i had. its s-off.
Click to expand...
Click to collapse
Before you do anything, install DiskUsage as advised.
- Browse to your /sd-ext partition, you may need to enable root permissions. If it's not filling up with your apps then you haven't activated A2SD.
- Browse to your /system partition, you'll find that you have a lot of free space here as you are still on stock hboot. This is effectively wasted space. If you change hboot you'll have a smaller /system and therefore larger /data (internal memory) :good:
So like I said, if you want app space, change to CM7r2 hboot using fastboot commands (search for a guide), full wipe and install the ROM again.
Follow the instructions as written in the first post to activate A2SD. Recommend you choose to move dalvik cache only to sd-ext.