yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] Poodlemastah:
Is this directly flashable on a cm nightly build?
[Desire Android Development] tkirton:
Yes, it is directly flashable on a CM Nightly Build...that's one of my test platforms.
[Desire Android Development] rahul.pillai:
Getting into a boot loop while using this on MIUI ROM.... wonder if this works on it..
[Desire Android Development] mon@diac:
no boot loop for me but SD storage settings apk is not working (FC) after DT 2.7.5.1
[Desire Android Development] rahul.pillai:
Okay, did you try the "Adv" version or the "Std" version. Also, what was the steps involved for installation?
[Desire Android Development] Swissola:
Wifi issue after Darktremor install

Hi all

Correct thread this time!

I'm running Pinky Desire 1.8 (HTC Desire) and keep getting the low space issue. On doing some research I found that Darktremor was just what I'm looking for. Installed the zip, rebooted and... no wifi.

Looked at the settings menu and wifi simply says 'Error' next to it.

On scanning through the thread I see I'm not the first person to have this issue (back in August?), is there a workaround for it or am I going to have to request pinkolin to make his ROM compatible?
[Desire Android Development] mon@diac:
Adv version and there are not any problems for installation..And I checked App2sd on Terminal..yes it works but Sd card&Phone Storage seem broken..I don't know why...
[Desire Android Development] tkirton:
That would make sense...Darktremor uses the CLI (Command Line Interface) to set settings. An APK is planned for Darktremor, but has not been built.
[Desire Android Development] mon@diac:
Miui mod has built in 2.7.5 RC3 and updated to 2.7.5.1 but Sd Card&Phone Storage gives FC..but App2SD great works...
[Desire Android Development] tkirton:
That is strange. I do know that RC3 and 2.7.5 (which 2.7.5.1 is just an update for) are slightly different in where they mount the SD card.

In RC3, it would mount it to /system/sd (actually, RC3 may have put it in /data/sd, which was very short-lived). Final (2.7.5) tried to look for /sd-ext and used that for a mount point...otherwise, it would use /system/sd (I know both works...Fresh Hero 2.4.0 doesn't have an /sd-ext while CyanogenMod Nightly Builds do).

This could be a dalvik-cache or a /data/data issue.

If it is dalvik-cache (which is the least painful to fix), go into an adb shell and type a2sd resetcache. The phone will reboot and rebuild the dalvik-cache.

If that doesn't work, then you may have to factory wipe the data.
[Desire Android Development] romracer:
Why is there a file called ":" in the 2.7.5.1 update? It appears to be "starta2sd".

And why does the installer remove everything in /system/etc/init.d? This could be detrimental to those who try and flash this on top of some other ROM.
[Desire Android Development] st0kes:
I've got this working on CM6.02, but I had to read the first 21 pages of this thread to do it. The OP needs updating with clearer instructions, apart from that no complaints here. Great tool!
[Desire Android Development] tkirton:
Did you actually use the links on the first message? There's an installation instruction guide link on it.

From the first post:

You would want the second link...those are the installation instructions.

I maintain threads for this programs in the following forums:

HTC Evo 4G

HTC CDMA Hero (main thread)

Nexus One

Droid Eris

HTC Desire

HTC Legend

HTC Incredible

HTC Tattoo

HTC Aria

MyTouch 3G

HTC GSM Hero

It's easier to post a link to the instructions in the HTC CDMA Hero than to repost it for every thread.
[Desire Android Development] tkirton:
1. The ":" looks like starta2sd...it probably was typo when I was copying files. It has been removed.

2. In order to make sure that Darktremor Apps2SD actually runs without interference from another installed Apps2SD, it clears that entire directory.

One of the first versions actually didn't clear that out...it would put an 04apps2sd in /system/etc/init.d. The problem started with Modaco ROM for Desire...it uses 40a2sd (Darktremor would run before it, then Modaco's version would come behind it and reset values).

At one time, I did have the installer just remove any Apps2SD program and dalvik-cache move programs, but there was about 15 different variants of files that I was keeping up with. This is due to no standardization...and I can't make ROM developers conform to a naming convention.

The files are based from CyanogenMod, which is the most popular rom that is supported on multiple platforms. This allows greater compatibility with roms.

I am more than willing to work with anyone who may be loading something else in that directory and need it included as part of the setup.
[Desire Android Development] st0kes:
Yes I did, but I was unsure whether I needed the new installer or alternate installer version, so I started reading the thread. And once you start reading, it's all about people with CM6 having issues .... anyway all's well that ends well, it is working now.
[Desire Android Development] tkirton:
Not an issue. I have to do updates to the first message for all the threads, so I'll make that clear on the difference between the two.

CM6 was a problem for me. For all of Darktremor 2.7.5 until the final version, there were one issue after another in getting it working, especially on the daily builds.
[Desire Android Development] gatsu_1981:
You can have fun. S-OFF for Desire has been release, it means that many person will not have to care for /system being written during Android runtime ;)
[Desire Android Development] tkirton:
Finally!!! This is great news.
[Desire Android Development] mattiadj:
A question by newbie.

I'm running with leeDroid 2.1a which has the app2sd but I noticed that my internal memory go down faster.so my questions are:is this script better than the which one included in leeDroid?and how can I test it on my ROM?

Thanks

sent from the future
[Desire Android Development] tkirton:
leeDroid 2.1a may be using a basic form of Apps2SD, which simply moves the applications to the SD card (the original goal for Apps2SD). It may not move the dalvik-cache to the SD card, which also consumes space on the /data partition (and lots of it)

I'll check it out.
[Desire Android Development] mattiadj:
So what can I do??

sent from the future
[Desire Android Development] tkirton:
If you don't want to change Apps2SD, go into an ADB shell and type the following:

cd /system/xbin

dalvik2sd on

That should (at least by the way the code looks) move dalvik to your SD card.
[Desire Android Development] mattiadj:
Thanks!

Can I type these command from terminal app?how can I after check if davilk cache is moved?

Edit: from terminal emulator command davilk2sd is unknow

sent from the future
[Desire Android Development] davdavo:
Hi Guys,

I want to install this at the ROM level onto the Miui ROM, found here.

http://xdaforums.com/showthread.php?t=792123

How do I do that? I want to install it at the ROM level and then flash the ROM to use. Please don't tell me to flash the ROM and then install Darktremor through recovery or adb.

Can this be installed to the ROM before I flash?
[Desire Android Development] tkirton:
Okay...I won't tell you to flash the ROM then install Darktremor through recovery (although that's really how you do it).

First question: does your rom already support Apps2SD or an Apps2EXT solution? (doesn't have to be Darktremor but the Froyo solution doesn't count)

I'm looking to see if the boot image file needs to be modified or not. If it doesn't, it makes this installation a lot easier.
[Desire Android Development] davdavo:
Hi,

Yes, I think it supports one of them, it says A2SD+ in system settings, but one of the forum members said it needs to be activated? Which leads me to the next question, how can it be activated/installed (with your version) at the ROM level?

Thanx :)
[Desire Android Development] davdavo:
Hi,

Fantastic explaination.

Thanx for the link to the new version :D

I opened the darktremor.zip, looked inside the init.d folder which contains these files:

00banner

01sysctl

02firstboot

04apps2sd

99complete

However, when I opened my ROM.zip and looked inside system/etc/init.d/ there are also 5 files with the exact file names just like above. What do I do, replace them all with Dartremor's new version?

Also in step 4. My ROM don't have a data folder, what can I do?
[Desire Android Development] sbazsi:
install

Im very new to all this (root/hack/etc) stuff.

I want to install darktremor, to free up some space.

I already rooted my phone. I made a nandroid backup, and a titanium backup.

After that I flashed the darktremorinstall.zip.

Now I now, that I should made a full wipe.

My question is, if I make a full wipe, after that I install darktremor, can I reinstall all my stuff from a recovery? Even from nandroid, or from titanium?

Thank in advance.
[Desire Android Development] tkirton:
1. Replace 04apps2sd from the ROM with the 04apps2sd from the Darktremor zip (Step 5)

2. If you don't have /data, just take the entire /data folder from Darktremor zip and put it in your ROM. That will create a /data in your rom.
[Desire Android Development] davdavo:
I will give that a go :D

I flashed your 2.7.5.2. install .zip in recovery after I flashed the ROM. The phone had a few forced close, but I'll try your suggestion above :)
[Desire Android Development] wollyka:
Quick question for the experts: now that S-off is released, is it possible to have an Apps2sd that also moves the data/data to the SD card? It will save a LOT of space..
[Desire Android Development] tkirton:
Looks like you aren't rooted. I think the developer messed up your root.

The moment you typed "su", the prompt should have changed from "$" to "#". Since your screenshot states it didn't, it looks like rooting is messed up.

What rom are you using? I can look up the rom and see if there are problems with it (usually people will complain in the forum)

In the meantime, you may want to try reflashing the rom again...allow it to boot. Then go into adb shell again and type su (then press ENTER). If the prompt changes from $ to #, then it may have something to do with a startup script. If that's the case, you can try flashing Darktremor 2.7.5.2 (the installer will leave most of the startup scripts intact).

Darktremor 2.7.5.2: http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.2-signed.zip
[Desire Android Development] tkirton:
I can. The first runthough at it in an earlier 2.7.5 version didn't go so well...but I can explore that option again.

The only downside would be that, if the SD card goes out, you may not be able to boot (since the core functions are also using /data/data). A boot protection mode for /data/data would act the same as a factory wipe.

But, if you understand the risks involved, I can certainly try to add that as an option for Darktremor 2.7.5.3.
[Desire Android Development] davdavo:
I am using the miui rom (odexed), but someone deodexed it that I flashed.

http://xdaforums.com/showthread.php?p=8395975#post8395975

[/I]

It didn't change from $ to #. So the next question is, how do I root it? :D

Having said that, it does have Superuser installed as default...does that count as a root?

edit:

I just reflashed the ROM and it's different this time. It's still stock, I haven't applied your suggestions from above to update to the latest version yet.

C:\android-sdk-windows\tools>adb shell

adb server is out of date. killing...

* daemon started successfully *

$ su

su

# a2sd check

a2sd check

[ ] Apps2SD is launching...

[ ] Starting Apps2SD Check Program.

[ ] Searching for Mount Point...

[*] Mount point /data/sd located.

[ ] Checking for ext partition

Darktremor Apps2SD Status Report

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

Legend: [*]=Setting is correct

[!]=Setting is correct, but not optimal.

[X]=Setting is incorrect and needs to be fixed.

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

Partition - [*] Mounted as EXT2

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.

Swap - [ ] Partition not present.

[*] Swap does not start.

ZipAlign - [*] Not running at boot.

To activate it, type a2sd zipalign

Dalvik Heap(MB)- [*] 24m

Low Memory

Killer Settings- [*] 1536,2048,4096,5120,5632,6144

Note: Values are in pages.

1 page = 4KB memory.

Values represent the following:

1st number = Foreground App

2nd number = Visible App

3rd number = Secondary Server

4th number = Hidden App

5th number = Content Provider

6th number = Empty App

Property Patch - [*] File System Ready property

found.

[*] Boot image init.rc patched.

[Ôüç] For a list of commands that you can use with Apps2SD

Type: a2sd help

# a2sd reinstall

a2sd reinstall

[ ] Apps2SD is launching...

[ ] Starting Darktremor Apps2SD Version 2.7.5 RC3 2010-08-16

[ ] Checking for Dalvik Heap Size.

[ ] Starting Darktremor Apps2SD in reinstall mode

[ ] Checking ext mount.

[ ] Installing Apps2SD Links...

[ ] Removing No Apps2SD flag file.

rm: can't remove '/data/.noa2sd': No such file or directory

[ ] Setting File System Ready property to 1.

#
[Desire Android Development] Pyr0x64:
according to the output you posted, a2sd is working, it says

[*] Programs run from SD card

and

[*] Private Programs run from SD card

if you want the dalvik cache on your sd as well, type: a2sd cachesd
[Desire Android Development] davdavo:
I think a few people said it's not working out of the box and you have to enable it in adb. I followed this guide. If that is the case, why would they implement it and not enable it? Can I enable it in my ROM then flash?

http://xdaforums.com/showpost.php?p=8395975&postcount=172
[Desire Android Development] wollyka:
Thanks. Yeah, it will be interesting at least to add it as an option to play with :)
[Desire Android Development] Rockzz:
Hello, I'm a new android user, with HTC Desire. I took the day to understand all the software layers around this OS, and now am at this point :

- unrevoked-rooted

- goldcard

- flashed from Orange v2.1 to RUU v1.15

- re-rooted to backup, then upgraded through OTA to RUU v2.2, re-rooted again for backup

I want to stay the nearest possible of the RUU roms, but only aim at one customization : a2sd+, since phone memory space vanishes really fast.

So I partitioned fat32/ext3/swap, only have the Clockwork Mod, don't know if the Amon Ra would substitute to it or can be installed as an addition, and plan to apply a2sd+ zip from recovery, trusting my partition scheme (formatted FAT through android OS, added an ext3 and a swap to the end of disk, with "about" 512MB and 32MB to avoid breaking cylinders in the middle, then augmented the FAT32 partition : so, original FAT32 partition remain unchanged, same start sector, boot and lba flags as stock, except size, the goldcarded-mbr is preserved, only the partition tablee changes) ;) This is the first doubt in real :s

The second doubt, and I hope you can provided a sure answer tkirton, is : I read several thread about a2sd+ not beeing safe (mass-storage-PC-mount from OS, mounting the FAT part. one time, then the ext part. some other times, or mounting the whole sdcard device, requiring to manually edit the system fstab to force mount of the 1st partition, the FAT). This is a big concern and if it's true, I'm anguish this kind of issue has not been one of the first preoccupations of the a2sd+ app. I don't try to be bad ;) Just don't get it. If you can explain me.

I read the /etc/vold.fstab file, and it mentions that the stock "auto" setting ("1" beeing the issue workaround) will choose "the first acceptable (or something like this) partition" as mass-storage, what is not transparent at all.

Maybe the numerous people who encountered the issue did an erroneous partioning, so that vold could not find any valid partition in auto, and ended up with mounting the whole SD ?

I really hope you get concrete info on this : storage is the crucial spot, you know it :p
[Desire Android Development] tkirton:
Okay, it looks like it was a bad flash. That's good.

Well, it looks like the program is working. If you wish to upgrade to the newest version, you are more than welcome to. Otherwise, the program is working as designed.

If you want to move dalvik-cache, you can use a2sd cachesd (to move to the SD card) or a2sd cachepart (to move to the cache partition).
[Desire Android Development] tkirton:
Let me assure you that Apps2SD (a.k.a. Apps2EXT, A2SD or A2SD+) isn't as bad as people make it out to be. I've have a 16GB Class 6 card that is being used for my Evo. I originally used it for my Hero. It has been running an Apps2SD configuration since about November 2009. I've had to reformat once, that was while I was debugging Apps2SD (didn't unmount properly from the SD card when I was transferring data to it).

I put my card through some severe abuse...so one failure is good. Typically, a user may never see a failure in the card. It really depends on the quality of the card you are using. Using EXT3 greatly reduces the chance for corruption on the filesystem level.

Amon-RA recovery is a replacement to Clockworks. I prefer Amon-RA over Clockworks.

Now, what I'm not familiar with is the goldcard partition. If you are thinking about using Darktremor Apps2SD, this could pose an issue. If you possibly could, can you send me a list of your partitions on your SD card (e-mail: rtkirton@gmail.com)? I may have to make adjustments in 2.7.5.3 to accommodate for the goldcard partition.
[Desire Android Development] tkirton:
Bump...new version released: 2.7.5.2
[Desire Android Development] davdavo:
I've got your post from above saved as a bookmark. Gold info ;)

O.K, I've successfully updated the ROM's outdated version of Darktremor to 2.7.5.2. Thanx heaps.

However, I have a problem that I can't figure out. How do I insert the flags into the ROM so that dalvik cache2sd and zipalign are activated out of the box. At the moment it's there, but not activated, I did a check straight after I updated the ROM according to your instructions above, and after I flashed it. The results below. It says dalvik cache runs from internal memory, zipalign not run on boot.

If you don't mind also explaining, is there any advantages in having a heap size of 32 over 24?

C:\android-sdk-windows\tools>adb shell

$ su

su

# a2sd check

a2sd check

[ ] Apps2SD is launching...

....

....

Darktremor 2.7.5.2 Apps2SD Status Report

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

===

Legend: [*]=Setting is correct

[!]=Setting is correct, but not optimal.

[X]=Setting is incorrect and needs to be fixed or option is not availabl

e.

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

===

Block Device - [*] Found

- [*] /dev/block/mmcblk0p2

EXT Partition - [*] Mounted

Mount Point - [ ] /sd-ext

Partition Type - [*] EXT2

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.

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) - [*] 24m
[Desire Android Development] tkirton:
Add the following two files to your ROM:

/data/.dalvikcache

/data/.zipalign

To do that, simply type the following in the /data directory of where you have your rom broken out at:

echo "x" > /data/.dalvikcache

echo "x" > /data/.zipalign

Now, if you want to do this from the rom on your phone, type the following two commands:

a2sd zipalign

a2sd cachesd

Zipalign doesn't start on boot for a reason. Some protected apps tend to corrupt when zipalign is ran across it.

Dalvik to SD is also not installed at boot. This is for stability (in the event the SD card is not present during first boot).

Now, in Linux, these are hidden files (the "." in the front automatically declares it hidden), so you will need to modify your zip command to include hidden files.

As for Dalvik-cache, a study was done on the Nexus One regarding dalvik heap sizes and 24m actually was the best setting (32m would actually slow the system). This may not be true for higher powered phones. I personally can't tell the difference.
[Desire Android Development] davdavo:
Created:

.dalvikcache

.zipalign

Unfortunately putting the two files into /data folder doesn't work, and I know why it doesn't work. My ROM doesn't recognize the data folder at all, even if I create one, it ignores it. The structure of the ROM is below:

META-INF

system

boot.img

How would I go about forcing it to install/copy data folder? I think it's something to do with the update-binary & updater-script? :)

I am not really fussed, I'm curious for educational purposes :p

Thanx.

Here are the first few lines of the script:

assert(getprop("ro.product.device") == "bravo" ||

getprop("ro.build.product") == "bravo");

show_progress(0.500000, 0);

format("MTD", "system");

mount("MTD", "system", "/system");

show_progress(0.500000, 40);

package_extract_dir("system", "/system");

symlink("busybox", "/system/xbin/[", "/system/xbin/[[",

set_perm(0, 0, 06755, "/system/xbin/procrank");

set_perm(0, 0, 06755, "/system/xbin/su");

show_progress(0.200000, 0);

show_progress(0.200000, 10);

assert(package_extract_file("boot.img", "/tmp/boot.img"),

write_raw_image("/tmp/boot.img", "boot"),

delete("/tmp/boot.img"));

show_progress(0.100000, 0);

unmount("/system");

...

...
[Desire Android Development] tkirton:
Try this:

assert(getprop("ro.product.device") == "bravo" ||

getprop("ro.build.product") == "bravo");

show_progress(0.500000, 0);

format("MTD", "system");

mount("MTD", "system", "/system");

mount("MTD","userdata","/data");

show_progress(0.500000, 40);

package_extract_dir("system", "/system");

package_extract_dir("data","/data");

symlink("busybox", "/system/xbin/[", "/system/xbin/[[",

set_perm(0, 0, 06755, "/system/xbin/procrank");

set_perm(0, 0, 06755, "/system/xbin/su");

show_progress(0.200000, 0);

show_progress(0.200000, 10);

assert(package_extract_file("boot.img", "/tmp/boot.img"),

write_raw_image("/tmp/boot.img", "boot"),

delete("/tmp/boot.img"));

show_progress(0.100000, 0);

unmount("/system");

unmount("/data");