yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] tkirton:
I believe you can.
[Desire Android Development] tkirton:
If you can access ADB, pull the dta2sd.log, dta2sd.lg1 and dta2sd.lg2 logs from /data and send them to my e-mail address (rtkirton@gmail.com). I'll check to see what the issue is.
[Desire Android Development] tkirton:
Dalvik-cache shouldn't be on the SD card by default.

If it is and you don't want it, type a2sd nocache
[Desire Android Development] Schnello:
Sorry for my late response.

I have now installed the Beta03 and i faced with the problem again. I cant open the config into the terminal via "a2sd help" etc.

2.7.5.2 runs fine on my rom so i dont unterstand what is the problem.

Maybe i need a newer version of the busybox? Can this be the reason?
[Desire Android Development] ngkwdaniel:
I'm using the old version of the Darktremor App2sd. I will need to flash the latest Darktremor App2sd to update my previous previous? How about all the commands and the settings I have entered? Will I need to redo them again?
[Desire Android Development] [armitage]:
Yep,that did it.

Error is gone...Thanks.:)
[Desire Android Development] Terepin:
Nope, won't boot.
[Desire Android Development] tkirton:
Okay...we're going to try something here.

Download the Beta 03 again (make sure you clear your browser cache). Once you download it and install it, try running a2sd help

If you are still getting the issue (which you may), type a2sd usedtbusybox. The feature isn't documented yet, but this command will put a flag file to tell launcha2sd to use the Busybox that is included with Darktremor.

Once you do that, type a2sd help again. If the problem goes away, the issue is with your installed Busybox.
[Desire Android Development] tkirton:
Not if you are upgrading...though it will really depend on how old the original is.

What version are you running now?
[Desire Android Development] tkirton:
Did you do the Data2EXT method that's listed with this rom? If so, that may be why it's not booting. The second EXT partition would never be mounted in Darktremor (the assumption was that there is only one EXT partition...which holds true for every other phone out there).

I would move /data/data to the internal storage and then execute a2sd datasd if you want the /data/data on SD card.

-- or --

You could build a small script and name it something like 10extpart If you give me your mount point for the second ext partition and the directory name that /data/data is stored in (I presume it probably is /data/data on the SD card), I'll create you a small script that you can push to your phone.
[Desire Android Development] Nitin985:
How do I run commands ???
[Desire Android Development] [armitage]:
On the phone you can use terminal emu,or connectbot (which prefer),or on pc you can use adb.
[Desire Android Development] Schnello:
Doesn't work :(. The same error message appears with a2sd usedtbusybox. But the ext part works. Strange...
[Desire Android Development] [armitage]:
just tested beta 3a and help command works fine again.

Does what it's supposed to and doesn't move all apps back to the flash.:D

Had the old beta still installed and red about the help command problem and just had to find out what it was about.

Luckily I had a nandroid from today... :D

Typed a2sd help and it suddenly moved all my apps back to flash where I didn't have nearly enough space.:D

Anyway performed a reinstall now and the new version seems to work fine so far.

Thanks for the quick fix.
[Desire Android Development] rolfd:
The Desire doesn't have write access to /system while booted. Only in recovery.
[Desire Android Development] tkirton:
Do logcat for about two minutes...then send me the results to rtkirton@gmail.com

That should include everything I need.

There are two programs that run back to back...one is a relocation program to move other apps2sd out of /system/etc/init.d so they don't interfere with my apps2sd.

The second is 04apps2sd...this is one of two launch files for Darktremor Apps2SD (the other being /system/bin/a2sd). This launches a file called launch.a2sd in /system/bin using bash.

The logcat you supplied only captures the first program (the one that generated an error). The logcat stops right before it runs the actual apps2sd, so I can't tell what's going on. That's why I need you to run the logcat for two minutes (that will allow the entire apps2sd boot sequence to run) and then send it to my direct e-mail address (so you don't have to use pastebin).

I really do appreciate you testing this for me. I just have to work the issues out...Desires and Legends have always given me trouble in relation to this program.
[Desire Android Development] gatsu_1981:
Man, I can help, but you and I speaks different languages :D

I have NO more logcat lines to show you. I actually let it sit for a while... but the behaviour was:

- the few lines you see here on my pastebin

- black screen

- phone reboots itself, so logcat dies. If i fire up another logcat, I can only provide those few lines... because it does NOT proceed more than that you can see on my logcat.
[Desire Android Development] tkirton:
Hmmm....I wonder. If it is stopping there and rebooting, I'm wondering what happens when you try to read-write /system on a nand protected phone (I think Desire is NAND protected)...does it just simply reboot?

I didn't realize your phone was just rebooting at that point. The logcat is definitely not useless...it tells me that the launch.a2sd did try to run and got past the first line. I know what's past that point...switching /system to read-write. I'm expecting an error message if it can't do it...and that's why I'm questioning the behavior of the NAND protection.

Definitely will have to do something different here, but I think I know what I need to do and a workaround for it.

Thank you very much...you've been very helpful and I understand the Desire a bit better now.
[Desire Android Development] gatsu_1981:
Testing cyanogenmod 6 nightly build.

As there is no a2sd except native froyo one here, the first thing I tried was... Break my installation with your script ;)

Just kidding... I used your script a lot for my hero, it was always on my SD.

So the first thing I did was trying to enable a2sd.

And you know what?

It didn't break my installation.

But, it didn't worked anyway.

Then, I went in the terminal emulator, su, a2sd check... Bam!

Reset!

In logcat actually is not mentioned, so I think that it's not starting at all in cm6.

http://xdaforums.com/showthread.php?t=719544&page=2

BTW, NAND protection works that very way.

I tried some program that try to access system (one for changing fonts, one a root explorer) and both resetted my phone.

So, new story for CM6 is:

- CM6 with no A2SD, I think only froyo way

- installed a ton of apps, space went down to 30 MEGS, resetted into recovery

- flashed your script: it actually WAS FLASHED, since I saw a lot of "deleted files", I took a peak inside your script before puttin in my memory card so I know what I was expecting

- boot ran as your script was never installed, no slow down

- http://pastebin.com/EQd88c2e logcat here, until the "insert PIN" screen

After a while, it reboots itself. If I try to check "a2sd check", it reboots.
[Desire Android Development] tkirton:
I have a feeling it has something to do with any attempt to try to mount /system as read-write.

Here's Preview Fix 3 - Test 1: http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5-pf3-test1-signed.zip

Here's what I did: I removed any reference to switching /system to read-write (with one exception: JIT...luckily, that isn't one of those things that is required. I'll work on getting some safety functions on it to prevent an accidental reset).

Now, what I'm not sure of is /system/sd. I have put that directory as part of the build with a placeholder file. I'm not sure if NAND protection is going to interfere with an ext2/ext3/ext4 partition being mounted on top of /system/sd.

Let's see what happens...if it doesn't work, I'll switch the mount to the /data partition.
[Desire Android Development] gatsu_1981:
I will test it later.

I would really like it to work (expecially on cyanogenmod 6 since there is no A2SD at all on that rom yet).
[Desire Android Development] rolfd:
Have you not read what I posted earlier? You can not gain write access to /system on a Desire. We only have write access while the handset is in recovery.
[Desire Android Development] xtcislove:
Tested on Defrost 1.8

Not working caused in Bootloop
[Desire Android Development] PaulW21781:
/system/sd has full rewrite access. Its the physical NAND block which is mounted as /system, that has write protection under normal use. As the placeholder for /system/sd is created under the recovery console (where the nand block is allowed rw access) the access permissions to anything mounted to that (or any other location for that matter) will be solely dependant on the actual item being mounted, and not the parent filesystem its being mounted in to.
[Desire Android Development] Syc:
Error at line 48, system/sd doesn't exsist.

Rooted 2.1, with sd-card set up for app2sd. ClockworkMod Recovery (newest build).

Edit: tried mounting system and sd-card before installing from recovery, no luck.
[Desire Android Development] tkirton:
Yes, I was reading earlier.

The program was designed for phones like the G1, Hero, Eris, MyTouch3G...phones that don't have NAND protection.

It works on the Evo in its current form because Evo developers found a way to break the NAND protection on that phone.

I was expecting an error to occur...not a full reboot.

I have modified it not to do that, after you made your comment...Preview Fix 3 doesn't have /system trying to remount as read-write.
[Desire Android Development] tkirton:
That's was my fault...I screwed up the last build. Got a bit too hasty assembling the build.

Try Test 2...I made sure the /system/sd is part of it.
[Desire Android Development] tkirton:
I suspected that, but I wasn't sure. Thanks for the information.
[Desire Android Development] gatsu_1981:
Juicy logcat for you.

Last cyanogenmod, last a2sd script from you, full logcat... From first start after a2sd installation until... RESET! :D

http://pastebin.com/FL5pVBbY
[Desire Android Development] Syc:
Having some problems:

Test 2 installs perfectly, ran this in terminal:

su
a2sd

terminal exited as app2sd moved it to the sdcard, so I'm not sure if it finished correctly. It worked fine until i installed some new apps, as they got installed on the phone, and the shortcuts just showed the package name. I decided to run the terminal commands again, which seemed to complete the a2sd setup, but then all apps started to crash.

After a reboot i was stuck in the bootcycle, and i had to restore my old rom.

Any tricks/suggestions/ideas? I'll test anything as long as i can restore everything afterwards.

Oh, and how do i supply a logcat?

Edit: i learned to read, disregard that. Will supply one in 6-7 hours, as I'm not home atm.

Edit2: is it supposed to launch at boot? Because logcat didn't show any traces of a2sd starting anywhere before i started it manually. I haven't been able to "capture" it yet, as i started it via adb shell (which kills logcat).

It seems to be working well before rebooting, then logcat prints this during the looping bootcycle:

I/vold ( 53): New MMC card 'SU16G' (serial 94855405) added @ /devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:aaaa

I/vold ( 53): Disk (blkdev 179:0), 31116288 secs (15193 MB) 3 partitions

I/vold ( 53): New blkdev 179.0 on media SU16G, media path /devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:aaaa, Dpp 3

I/vold ( 53): Partition (blkdev 179:1), 29993292 secs (14645 MB) type 0xc

I/vold ( 53): New blkdev 179.1 on media SU16G, media path /devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:aaaa, Dpp 2

I/vold ( 53): Partition (blkdev 179:2), 998833 secs (487 MB) type 0x83

I/vold ( 53): New blkdev 179.2 on media SU16G, media path /devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:aaaa, Dpp 1

I/vold ( 53): Partition (blkdev 179:3), 124100 secs (60 MB) type 0x82

I/vold ( 53): New blkdev 179.3 on media SU16G, media path /devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:aaaa, Dpp 0

I/vold ( 53): Evaluating dev '/devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:aaaa/block/mmcblk0' for mountable filesystems for '/sdcard'

I/vold ( 53): Aborting start of /sdcard (bootstrap = 1)

I/vold ( 53): Volmgr not ready to handle device

D/vold ( 53): Bootstrapping complete

http://pastebin.com/QDCfaV9n
[Desire Android Development] tkirton:
I don't see where Apps2SD is starting...this may be a problem if the rom isn't starting it and you ran a2sd install.

But I don't see any the usual signs where it can't locate things like the apps and dalvik-cache. I did see where it couldn't find a rommanager.apk, but that was located in /system/app. I was looking for some indication of a crash, but didn't see it.

This is rather perplexing.
[Desire Android Development] tkirton:
Apps2SD isn't stating...the rom isn't setup to start it.

Which rom are you using? I'll see about modifying the boot image to run apps2sd. I need to find the base address for Desire boot.img. I'm hoping it is the same as the Nexus One.
[Desire Android Development] Syc:
I know the rom isn't set up to use it, it's vanilla 2.1, just rooted.

I was hoping that this script integrated a2sd to any rom, isn't that possible?

As for the boot.img, it's probably the same base address as Nexus One (why wouldn't it be?), so if you write a patch for it I'll be happy to report back anything you'd like to know.
[Desire Android Development] tkirton:
It does integrates a2sd into any rom...but the rom has to be already setup to run it (usually via Busybox Run-Parts). There's no way I can extract a boot image, modify it, and put it back into the phone while Apps2SD is running (mainly because the tools aren't available for the ARM processor).

I'll download the rom tonight and make the modifications. I'll use the Nexus One values to reassemble it.

The reason I say I'm not sure is that the Hero and Eris actually use different values than the Nexus One. The Evo uses the Nexus One addresses, so it's probably safe to say the Desire uses them as well.
[Desire Android Development] tkirton:
I apologize for the issue. The same thing happened to me when I ran it earlier this morning...which caused me to panic since I released the code in that state.
[Desire Android Development] tkirton:
Hmmm...I think I know where the problem is.

It is your Busybox. But you're getting the message from a2sd rather than launcha2sd. The a2sd uses the native Busybox. Not sure what line is causing the issue, but most of that file is used to move the logs and create a new one.

I've compiled a new program just for you: http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.3-beta03b-signed.zip

This is Beta 03b...the difference between this version and Beta 03a is that a2sd (and the dtapp program that is converted to a startup file on install) will use the Darktremor included Busybox rather than your native Busybox.

Try that and see if the message finally goes away.
[Desire Android Development] deejay6901:
finally it work on me... all cache has been moved to the card now. nice work! tkirton:) hope this gets better on the final release.... cheers!
[Desire Android Development] Nekromantik:
if I am having no issues with beta 2 is it worth upgrading to 3b?

also will it be possible to improve performance with cache on SD?
[Desire Android Development] tkirton:
You can upgrade to 3a or 3b (3b is an unreleased version for a bad interpreter problem one user was having...I believe that is more of the user's Busybox implementation than Darktremor). Between 2 and 3a or 3b, I would upgrade...there was a complete rebuild of the dalvik-cache move portion which now makes it reliable.

As for improving performance with the SD card, there's a patch that the Evo uses that I'm going to go find that does something with the SD card reader to speed it up. If that works, I may be able to apply it to multiple phones using Darktremor.
[Desire Android Development] ngkwdaniel:
I'm using 2.7.5.2. So do I need to redo the commands and the settings when I flash the latest script?
[Desire Android Development] bakedecake:
I don't know what's going on with this, it says the data is on the internal storage but if you look at the partition usage it's almost empty so it must be on the ext.

This is how it installed 2.7.5.3 beta 3a, I haven't changed anything.

Gone back to the 2.7.5.2 script and moved dalvik cache to ext, I guess this is the a2sd+ setup, performance is fine so it must just be when data is on the ext that it slows down.

$ export PATH=/data/local/bin:$PATH

$su

# df -h

Filesystem Size Used Available Use% Mounted on

tmpfs 202.9M 32.0K 202.9M 0% /dev

tmpfs 202.9M 0 202.9M 0% /mnt/asec

tmpfs 202.9M 0 202.9M 0% /mnt/obb

/dev/block/mtdblock3 250.0M 122.7M 127.3M 49% /system

/dev/block/mtdblock5 147.6M 6.3M 141.3M 4% /data

/dev/block/mtdblock4 40.0M 1.6M 38.4M 4% /cache

/dev/block/mmcblk0p2 980.5M 160.8M 769.9M 17% /sd-ext

/dev/block/mmcblk0p2 980.5M 160.8M 769.9M 17% /data/dalvik-cache

/dev/block/mmcblk0p2 980.5M 160.8M 769.9M 17% /data/data

/dev/block/mmcblk0p2 980.5M 160.8M 769.9M 17% /sd-ext/app

/dev/block/mmcblk0p2 980.5M 160.8M 769.9M 17% /sd-ext/app-private

/dev/block/vold/179:1

13.9G 3.0G 10.9G 21% /mnt/sdcard

/dev/block/vold/179:1

13.9G 3.0G 10.9G 21% /mnt/secure/asec

/dev/block/dm-0 17.2M 15.8M 1.4M 92% /mnt/asec/com.rovio.angrybirds-1

/dev/block/dm-1 31.4M 29.4M 2.0M 94% /mnt/asec/com.ezone.Snowboard-1

# a2sd check

[ ] Apps2SD is launching...

__ _____

| \ |

| | |

|__/ | Darktremor Apps2SD 2.7.5.3 Beta 3a (2011-01-25)

[ ] GetProp Command = /system/bin/toolbox getprop

[ ] SetProp Command = /system/bin/toolbox setprop

[ ] Mount Point = /sd-ext

[ ] Starting Apps2SD Check Program.

Darktremor 2.7.5.3 Beta 3a Apps2SD Status Report

===================================================================================

Legend: []=Setting is correct

[]=Setting is correct, but not optimal.

[]=Setting is incorrect and needs to be fixed or option is not available.

===================================================================================

Block Device - [] 0

Partition Type - [] EXT2

Mount Point - [] /sd-ext

Support EXT2? - [] Yes

Support EXT3? - [] Yes

Support EXT4? - [] Yes

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 /cache flag file not found.

[ ] Dalvik to SD flag file not found.

[] Dalvik runs from Int. Storage.

To run from SD card, type a2sd cachesd.

To run from /cache partition, type a2sd cachepart.

Data - [] Program Data on Internal Storage.

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

[] Swap does not start.

ZipAlign - [] Not running at boot.

To activate it, type a2sd zipalign

Dalvik Heap(MB) - [] 32m

Low Memory

Killer Settings - [] 2048,3072,4096,6144,7168,8192

Note: Values are in pages.

1 page = 4KB memory.
[Desire Android Development] Terepin:
No, ROM already has A2SD script.
[Desire Android Development] yukkio:
Hi,

I'm trying to move /data/data to internal but when I execute a2sd nodata I get this:

[ ] Apps2SD is launching...

__ _____

| \ |

| | |

|__/ | Darktremor Apps2SD 2.7.5.3 Beta 3a (2011-01-25)

[ ] GetProp Command = /system/bin/toolbox getprop

[ ] SetProp Command = /system/bin/toolbox setprop

[ ] Mount Point = /sd-ext

[ ] Starting Darktremor Apps2SD Version 2.7.5.3 Beta 3a

[ ] Launching Apps2SD Start Program with nodata

[ ] Starting Darktremor Apps2SD in nodata mode

[X] /data/data is not symbolically linked.

Moving not supported.

[ ] Setting File System Ready property to 1.

What's wrong?

Stupid question: a2sd commands in recovery mode?

BR.
[Desire Android Development] Schnello:
Thanks for comp the revb but the problem is the same.

I ask now my rom cook for the new rev of the busybox. Maybe this fix the problem.
[Desire Android Development] yukkio:
More info about my problem:
[Desire Android Development] tkirton:
Nope...your settings are retained when you upgrade to 2.7.5.3.
[Desire Android Development] Nekromantik:
whats the main difference when cache is on NAND vs cache partition?

Does internal memory still go down alot if you leave cache on the chace partition?
[Desire Android Development] tkirton:
If the dalvik-cache is on SD card or Cache partition, the internal storage will still go down, just slower. The issue at that moment would be the program data (/data/data). That stores all aspects of the programs loaded on your system, including cache data.
[Desire Android Development] Nekromantik:
ok thanks.

i will try to move cache to cache partition to see if its faster.

edit:

can someone help

I forgot to nandroid before I moved cache to cache parition and when I ran the command it said unable to mount and then phone rebooted and was stuck on why so serious so I flashed ROM over the top and now I get boot loops so I then flashed the a2sd script and still getting boot loops.

can anyone save me msgs etc as I want to avoid going back to nandroid from yesterday
[Desire Android Development] tkirton:
If you can gain access to ADB, shell into the phone and type:

a2sd nocache
[Desire Android Development] tehownt:
I have a problem running beta 04:

I partitionned the SD card using Rom Mgr, then installed Cyanogenmod 6.1.1, then installed DT (app2sd, cachesd) but whenever I run convert-ext3 or convert-ext4 I get the following error:

/system/bin/starta2sd: line 1156: [: ==: unary operator expected
[X] Kernel does not support EXT3 partition.
[ ] Kernel supports the following filesystems:
(....)
nodev devpts
ext2
ext3
ext4
(...)

'uname -a' returns:

Linux localhost 2.6.35.9-cyanogenmod #3 PREEMPT etc... so definitively supports ext2,3,4 as a filesystem.

I dug a bit into the scripts,

'cat /proc/filesystems' returns that the system supports ext2,3,4, but when using

'cat /proc/filesystems | grep -q -e ext4; echo -e $?' it returns 0 because -q says so (0 if pattern found, 1 otherwise from busybox 1.16.2).

So the property a2sd.ext4 is set using this command which behaves the opposite of what it should (sets $ext4part to 0 instead of 1)...
[Desire Android Development] tkirton:
Actually, the code for convert-ext3 and convert-ext4 is correct. I would suspect that the ext3part and ext4part are blank due to a new shell being launched from launcha2sd.

Edit: That error you see in the output confirms that there is nothing set for ext3part...the variable isn't being passed.

Redownload Beta 04 file (it will internally be labeled Beta 04a). I have added two lines to the starta2sd file:

In convert-ext3:

ext3part=`$gpcmd a2sd.ext3`

In convert-ext4

ext4part=`$gpcmd a2sd.ext4`

These will pull the properties instead of depending on the variable to transfer between shell environments (those properties do get set in launcha2sd)
[Desire Android Development] ghiki:
Is it normal that the "beta4" does not work well with the Cyanogen Nightlyes (specifically CM7 v22)? When you install a custom kernel , phone freezes before boot anim. starts.

It's strange but with this version, works ok (I can install custom kernel [coutts] before installing ROM/A2SD script)
[Desire Android Development] 2000impreza:
CM roms use a separate script for A2SD. Try removing the init.d script below followed by reflashing darktremor A2SD update zip.

/system/etc/init.d/10apps2sd
[Desire Android Development] Xinot:
I did run beta 03 with Oxygen v2.0 RC7 and had issues when flashed rom, and dtapps2sd right after this.

No problems at all when flashed rom, and after 1st boot retrned back to recovery and installed dtapps2sd. I did move dalvik to sd (class 2) too and all was fine.