yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] davdavo:
That actually worked, your programming is awesome :D

However, there is an "X" marked against Dalvik cache: [X] Dalvik runs from Int. Storage. Setup issue. Run a2sd repair to fix.

I wonder what it means.

Also when I go to Settings > SD Card & Phone storage, it forced closed for some reason. I think I haven't done something right. If I flash back to the original app2sd ROM version (Darktremor x.x.x RC3) there is no forced close.

Oh yeah, what's "swap"?

Cheers,

H:\>adb shell

$ su

su

# a2sd check

a2sd check

[ ] Apps2SD is launching...

__ _____

| \ |

| | |

|__/ | Darktremor Apps2SD 2.7.5.2 (2010-09-30)

Apps - [ ] Linked to SD Card.

[ ] No Apps2SD Flag File not found.

[*] Programs run from SD card

To run from internal storage, type a2sd remove

Private Apps - [ ] Linked to SD Card.

[ ] No Apps2SD Flag File not found.

[*] Private Programs run from SD card

To run from internal storage, type a2sd remove

Dalvik Cache - [ ] Regular directory.

[ ] Dalvik to SD flag file found.

[X] Dalvik runs from Int. Storage.

Setup issue. Run a2sd repair to fix.

Swap - [ ] Partition not present or no swap support.

[*] Swap does not start.

ZipAlign - [*] Running at boot.

To deactivate it, type a2sd nozipalign

Dalvik Heap(MB) - [*] 24m

....

....

#
[Desire Android Development] lilnev:
How do you migrate to a new SD Card when the existing SD Card already has Darktremor App2SD installed?

ROM - CM6 Nightlys

Currently - 4 GB SD Card with ext3 (dalvic cache not on SD)

New - 16 GB Class 6 SD Card. (here I plan to move dalvic cache as well)

I found a document here but it's doesn't match for the Desire.

Any advise is appreciated.
[Desire Android Development] deskmat81:
I'm using a semistock rooted rom with A2SD+ that seems (to me) to don't work properly on my Desire. Can I install your script without problems? And is it possible to uninstall it if i'll have any problem? Thanks
[Desire Android Development] kimzplaze:
hi.. is it possible for me to install this and use this on a stock rooted 2.13.707.1 ?

thankz a lot =)
[Desire Android Development] fusionstream:
Hi.

I noticed I was running out of space on the ext3 partition so I shut the phone down, took out the sd card then expanded the partition, finally replacing the card in the phone. It all went fine for a while until I started to hit the old partition limit, then the "out of space" warning appeared.

Checking "File Manager" shows me that my Applications is 92% full. What is the problem here?

I have already tried an a2sd reinstall. Still no joy.

EDIT: I have had a look around the system. It appears that /data/data is 120MB while with the remaining 41MB in /data/misc. Is this an error?

I would also like to suggest that some safeguards be put into place to prevent "a2sd remove" from losing apps when there is no space left on the phone.

Running on a HTC Desire Froyo Stock Rom, rooted then modified to allow a2sd to startup.
[Desire Android Development] tkirton:
Looks like something may be resetting Dalvik-cache. What's the lines right before that statement?

That's strange. Do you have any other force closes on any other program? This issue may be related to the first problem you are having.

Swap is a special partition that moves idle physical memory to when the operating system requires more memory to run a program. Works like a swap file in Windows. It's not required in Android to run, but some people feel the phone is a bit more responsive during heavy loads with it. It's an option. I run a 32mb swap file on mine...I wouldn't go higher than that.

Cheers,

H:\>adb shell

$ su

su

# a2sd check

a2sd check

[ ] Apps2SD is launching...

__ _____

| \ |

| | |

|__/ | Darktremor Apps2SD 2.7.5.2 (2010-09-30)

Apps - [ ] Linked to SD Card.

[ ] No Apps2SD Flag File not found.

[*] Programs run from SD card

To run from internal storage, type a2sd remove

Private Apps - [ ] Linked to SD Card.

[ ] No Apps2SD Flag File not found.

[*] Private Programs run from SD card

To run from internal storage, type a2sd remove

Dalvik Cache - [ ] Regular directory.

[ ] Dalvik to SD flag file found.

[X] Dalvik runs from Int. Storage.

Setup issue. Run a2sd repair to fix.

Swap - [ ] Partition not present or no swap support.

[*] Swap does not start.

ZipAlign -

[*] Running at boot.

To deactivate it, type a2sd nozipalign

Dalvik Heap(MB) -

[*] 24m

....

....

#[/QUOTE]
[Desire Android Development] tkirton:
Quick and dirty steps:

1. Move apps back to internal storage (a2sd remove)

2. Save the contents of your FAT32 SD partition to a computer.

3. Boot into recovery.

4. Swap the cards (do that in recovery)

5. Make your EXT3 partition on the new card

6. Put the contents of your FAT32 SD card back on your SD card

7. Boot phone.

8. Move the apps back to SD card (a2sd reinstall)

9. Move dalvik-cache to SD card (a2sd cachesd)

1 and 2 can be done in reverse order.
[Desire Android Development] tkirton:
I would look at an application such as CacheMate to remove the internal caches. /data/data will continue to grow as this is where the settings for each of your programs are stored (not to mention the Marketplace and Internet Browser caches are there as well).

I'm not sure what /data/misc is about. I'll look that one up.

As for safeguards during a2sd remove...I'll think about it. However, I do have a question for you: doesn't your recovery program have a way to backup the EXT partition? In Amon_RA's recovery (the one I use for my Evo) and Godspeed Recovery (the one I use for my Hero), both have Nandroid, which will backup the EXT partition.

If it does have a way of backing up the EXT partition, might I suggest that you perform the following steps:

1. Boot into recovery

2. Run your backup program.

3. Copy the contents of your FAT32 SD partition to your computer

4. Resize your SD card

5. Copy the contents of your backup on your computer to your FAT32 SD partition

6. Restore from your backup program

7. Reboot

It's just a thought...I don't know what recovery you are using, so this may all be a moot point.
[Desire Android Development] fusionstream:
The above's link with diminishing free space pre-a2sd just dawned on me! doh! Thanks for the pointer.

ClockwordMod has it. But it was an old backup. The good thing is that dalvik cache appears to keep the old apps registered. So for the most part I knew what I had to reinstall. Oddly enough some user specific data disappeared on reinstall (which from my conjectural observations of how the update process works appears to be counter intuitive).

Anyway, as pointed out /data/data was causing the "full space warning". Have symlinked the folder to /system/sd/data. Perhaps this could be yet another feature for Darktremor a2sd? =D

Cheers and thanks for the help, and more importantly, for this app!
[Desire Android Development] lilnev:
Thanks. I figured it out. I did it about the same with a few extra steps.

BTW, on the Desire you can't take out the sd card while the battery is in the phone.
[Desire Android Development] maxq1:
@ OP/tkirton,

i'm currently using ali ba's azure rom on my legend. would like to try this. some noob questions though. kindly enlighten...

have moved some apps to sd already (via azure's built-in apps2sd feature, i think). if i want to install your scripts, do i need to bring all those apps back to internal memory first?

after this has been installed, do all apps i install from thereon get automatically installed on the ext3 partition? what about existing apps (sort of a follow-up from question #1)?

is there any advantage between creating a physical swap partition VS using an x% for swap under ext3?

thanks in advance!
[Desire Android Development] tkirton:
The /data/data move is scheduled as an experimental feature for the next major version.
[Desire Android Development] tkirton:
I believe that's the same with the Evo.
[Desire Android Development] tkirton:
No, the program will create a symbolic link to /system/sd/app (or /sd-ext/app). It won't erase any programs.

All apps will be installed on the EXT3 partition.

You can't create a swap under ext3 (unless you are using compcache, which creates a swap file). It is either a linux swap or no swap (again, unless you are using compcache).

It does not affect your phone if you decide not to use a swap file. Some people like it, others don't.
[Desire Android Development] ck_looi:
I have installed a2sd in my latest CM nightly, and i would like to say it runs very smooth :D

just to ask, what should i do if i update my phone to future CM nightly, do i need to flash the a2sd zip again??

Thanks for e help.
[Desire Android Development] tkirton:
Unfortunately, yes.

CM nightly builds do not have Darktremor preinstalled, so when you flash the CM nightly, immediately flash Darktremor Apps2SD. This is the method I use to test Darktremor on the ever-changing nightly builds.

The reason for this is that the CM nightly builds, just like most roms, formats the /system partition prior to installing. This automatically wipes out the programs associated with Darktremor.
[Desire Android Development] ck_looi:
thanks for the help. So, after that, do i still need to run "a2sd cachesd" to enable davlik-cache running on sd card?
[Desire Android Development] tkirton:
No, you shouldn't have to do that part, as the flag files are stored on /data, which isn't erased unless you do a factory wipe.
[Desire Android Development] ck_looi:
got it...thanks a lot
[Desire Android Development] ck_looi:
@tkirton

I just flash latest CM 225 nightly over 224 nightly, then apply the a2sd flashable zip. after that i reboot the phone, and the phone now hangs at the bootanimation for more than 10 mins. Is this normal?

update: now it boots into the system, i guess is becoz 100+ of apps i have installed...
[Desire Android Development] maxq1:
thanks, man! was able to successfully install the 10/03 version on my legend running azure + oc kernel. had davlick-cache moved to sd too. everything seems to be fine. (crossing my fingers so i don't jinx myself :D). great work!

some clarifications though:

running adb logcat (i'm checking something out: particularly BlaY0's overlay thingy, btw) on my pc seems to keep my gizmo from booting properly. it's stuck on that animated cm boot logo. removing the batt and unhooking the gizmo from pc gets the thing to work normally again though. should this be the case?

after executing the command 'cachesd' on my gizmo's terminal emulator, some command lines appear to be running then my gizmo reboots all by itself. after rebooting though, all seems to be fine. again, is this normal?

again, heap of thanks, man!
[Desire Android Development] highway04:
help

i follow the step tat u provide to install to a rooted stock froyo desire... but some how it din work out for me... its say its not mounted ([X] Ext partition not mounted)...

what should i do??? or which part tat i missed???

when i run a check in the terminal... it say ext partition found, but not mounted... wats wrong wif it???

edit: juz found out tat it doesnt work wif stock rom... where can i get a boot.img for stock rom???
[Desire Android Development] myeveryheart:
I use Apps2SD with the Apps2SD direct method, but I don't know what "simply put a file with the Apps2SD code in /system/bin and name it a2sd" mean???

:confused:
[Desire Android Development] aidanbree:
I have been attempting to upgrade from CM 6.0.2 to CM 6.1 RC1 however my Desire is hanging on the operator logo. I then tried to wipe and install CM 6.1 but end up in a boot loop.

Could this be a conflict with A2SD?

Cheers
[Desire Android Development] maxq1:
^ did you move davlik-cache to sd? if so, we have the same problem. on my legend, upgrading from cm6 (azure rom-stable) to the nightlies got my gizmo stuck on the boot logo.

i think the only work around is to move everything back as is (pre-apps2sd; i.e., return davlik, apps, etc to internal cache/storage) PRIOR to using/upgrading to another rom. haven't tried it though. don't have time to re-build my gizmo if anything goes wrong :D
[Desire Android Development] tkirton:
I've heard of this on the Desire, where you have to pull the battery on CM to get it to boot (that is after you flash Darktremor). I'm not sure why that happens, and I thought maybe I can duplicate it on my Evo (unfortuately, I'm not running CM6 on it as it doesn't have 4G yet...but I do run the nightly builds of CM on my Hero). No such luck, but sometimes my Evo takes a bit longer to move from the Evo screen to the animated screen.

As for cachesd, any of the cache commands will restart the phone. This is normal (some programs are sensitive when the dalvik-cache is moved while the phone is running...a reboot fixes those issues).
[Desire Android Development] tkirton:
Are you trying to build your own rom or just installing it on a current rom you are running?
[Desire Android Development] tkirton:
I would think if you were going from CM6 stable to CM6.1 nightlies, you would want to wipe first (I know, it's still CM, but I'm more old-school...when you go from production code to beta code, you would want to clear everything out to avoid conflicts).

You may try clearing out the Dalvik-cache and see if that helps.
[Desire Android Development] tkirton:
More apps you have, the longer it will take on first boot from any new flash.
[Desire Android Development] maxq1:
@ tkirton

haven't tried that, bro. but i'm guessing that the problem is w/ cm6 (or 6.1) not having native support for ext partitions. let's say i have a 6.0 rom now w/ dt apps2sd already installed and all apps + davlik on sd. installing a 6.1 rom over this, even w/ wipe, won't read the ext partition upon re-boot, thereby the bootloop. just a theory though...
[Desire Android Development] myeveryheart:
I'm trying to build my own rom.

You said "To use Apps2SD with the Apps2SD direct method, simply put a file with the Apps2SD code in /system/bin and name it a2sd

To use Apps2SD with the Busybox Run Parts method or the CyanogenMod Froyo method, simply put a file with the Apps2SD code in /system/etc/init.d and name it anything...just make sure it starts with a two-digit number"

Since I use the direct method, should I also copy Apps2SD code in /system/etc/init.d?

By the way, I make ROM based on cm-6.1.0-RC3-Droid.

Oh, In the cm-6.1.0-RC3-Droid ROM, it like this

00banner

01sysctl

03firstboot

04modules

05mountsd

20userinit

In your zip,it like this

00banner

01sysctl

02firstboot

04apps2sd

99complete

So, what should I do?
[Desire Android Development] sreeramu:
Hi Friends,

I installed dtapps2sd today , but after i reboot or if i install application, i am able to see apk file in both /data/app/ and /sd-ext/app/ ....is there is any wrong in my configuration......?
[Desire Android Development] tkirton:
Replace 05mountsd with the 04apps2sd file...just make sure you rename the 04apps2sd to 05apps2sd once you replace 05mountsd

So, /system/etc/init.d should look like this:

00banner

01sysctl

03firstboot

04modules

05apps2sd

20userinit

Now you are good to go.

As for the direct method...normally, no...but if these files are in there, then CM is calling this from inside the init.rc (which means you didn't have to do the direct method).

If I remember correctly, CM calls this using two steps:

First step is the init.rc, which should have a line that looks like:

exec /system/bin/sysinit

Second step is the file /system/bin/sysinit. It should have this line:

/system/xbin/busybox run-parts /system/etc/init.d

(Note: Since that file is part of Darktremor, I know it's correct...run it on my CyanogenMod nightly build rom).

If those two are present (or at least the first line), the direct method is not necessary.
[Desire Android Development] tkirton:
That's normal and indicates Darktremor is working correctly.

The /data/app directory is symbolically linked to /sd-ext/app, so when you go into the /data/app directory, you are redirected to /sd-ext/app.

If you really want to make sure, type the following in either a terminal program or adb shell:

ls -l /data

Look for the line with "app" in it. If you see the following, all is working correctly:

app -> /sd-ext/app
[Desire Android Development] sreeramu:
tkirton Yes i am getting same thanks for your quick replay...
[Desire Android Development] myeveryheart:
Ok! thanks~I will try.

Since I don't need the direct method, does that mean I don't need to make a new boot.img, right?

I found I should use the CM method which means I need a new boot.img. And it works well! Great!

But there's a thing, when I install Angry Birds, it is in sd not ext. However, other programs are just in ext. Then I went to the CM settings-Application settings-Install location-Internal, I reinstall Angry Birds, it is in sd again. Then I went to applications-Manage applications-Angry Birds-move to phone, and it was in ext.
[Desire Android Development] highway04:
forgive my noob-ness

try to built a boot.img for my stock rom... some how i fail rite here... could u jz create a boot.img for me??? thx

what i get is this....

ubuntu@ubuntu:~$ ls

Desktop Downloads Pictures Templates workspace

Documents Music Public Videos

ubuntu@ubuntu:~$ cd workspace/

ubuntu@ubuntu:~/workspace$ chmod 755

chmod: missing operand after `755'

Try `chmod --help' for more information.

ubuntu@ubuntu:~/workspace$ chmod 755 *

ubuntu@ubuntu:~/workspace$ cd scripts/

ubuntu@ubuntu:~/workspace/scripts$ ./getramdisk

[ ] Extracting Ramdisk from Boot Image

Page size: 2048 (0x00000800)

Kernel size: 2299564 (0x002316ac)

Ramdisk size: 167324 (0x00028d9c)

Second size: 0 (0x00000000)

Board name:

Command line: no_console_suspend=1

Writing boot.img-kernel ... complete.

Writing boot.img-ramdisk.gz ... complete.

[ ] Uncompressing Ramdisk Image

534 blocks

ubuntu@ubuntu:~/workspace/scripts$ ./makeramdisk

rm: cannot remove `../newramdisk.gz': No such file or directory

[ ] Creating Ramdisk Image newramdisk.gz

534 blocks

ubuntu@ubuntu:~/workspace/scripts$ chmod 777 mkbootimg

ubuntu@ubuntu:~/workspace/scripts$ ./makeboot ../boot.img-kernel ../newramdisk.gz ../newboot.img 0x20000000

[ ] Creating New Boot Image

./makeboot: line 4: ./scripts/mkbootimg: No such file or directory

ubuntu@ubuntu:~/workspace/scripts$

here is my boot.img link mediafire.com/file/rpz1qb2cppchrw6/boot.img

pls help me... please....
[Desire Android Development] xNavyblue:
I am running a rooted stock Froyo on Desire.

I created a first EXT partition and a second FAT partition on the micro SD card. However, the clockworkmod would not mount the FAT partition where the zip file is and thus I am not able to flash the file this way. I tried turning the first partition into FAT and put the zip file there, I was ablebto flash the zip file, and later I turned the partition back to an EXT partition. Of course it won't work this way.

My question is, does the sequence of the partition matter? I tried using the ROM manager but for some reason the partition function doesn't work. Can someone tell me how to flash this zip file? Please pardon my scant Linux/Android knowledge.
[Desire Android Development] tkirton:
Sorry for the delay: been busy lately and my e-mail notifications are getting mixed in with all my other e-mails. Been doing online Christmas shopping, so lots of confirmation e-mails.

See if you have the file mkbootimg in your scripts folder.

If it isn't there, download it from http://www.darktremor.info/files/tools/mkbootimg and put it in your scripts directory. Make sure you perform a chmod 777 on it.
[Desire Android Development] tkirton:
Yes, the sequence does matter. The first partition must be FAT32 (otherwise, Android won't find your SD card). Second partition, at least for now, needs to be EXT.

Also, you said you are running this from a stock Froyo on Desire. Unless the stock rom you are running is a modified stock rom, you won't get Darktremor to work. The command to launch Darktremor isn't present in unmodified stock roms.
[Desire Android Development] Zephyron:
Hi, I have a question, so I've been using CM6 and 6.1 with the stock froyo app to ext. Last night I decided to try out your script (works amazing), but I was wondering about the .android_secure folder that is created for the froyo app to ext on my sd card. I read that apps were automatically moved from the phone to the sd card on the first startup of your app2sd. What about the apps that are already on the sd card because of CM's option to install apps on external? Does all the apps already on the sd still get moved to the partition or is it still using the froyo method?
[Desire Android Development] madd0g:
Set the options where to install the apps in CM settings to internal and move all the apps already on SD back to "phone" (those are the apps in use of Froyo's a2sd). You'll be faster with this : http://www.appbrain.com/app/apps-to-sdcard/com.easyfilter.app2sd In future, you can check if the freshly installed app is on the SD card and move it back to "phone" to keep the .android_secure clean ;]
[Desire Android Development] tkirton:
Anything that is already in the .android_secure folder will stay there. Because Darktremor and Froyo Apps2SDs are two different implementations, both can work together. Moving apps to external storage will store them on the FAT32 partition of the SD card while moving apps to the internal storage will store them on the EXT partition of the SD card.
[Desire Android Development] Zephyron:
Thanks for the explanation! Worked perfect