yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] teorouge:
May you suggest the operations needed to the ROM zip file to take it away A2SD+ support and add DATA2SD script without all the zip flashes? I mean, I "tweaked" it removing unneeded apk's and such, how can I make it DATA2SD enabled from the very first ROM flash? :confused:
[Desire Android Development] sibere:
If you know how to remove apps from the rom, then it shouldn't be a problem for you to follow instructions in the OP of this thread to enable DATA2SD manually on your phone.
[Desire Android Development] teorouge:
Thanks, that's what I did:

removed stuff2sd.txt from \system\etc\init.d\ and inserted 01data.txt (that should be like applying the APP2SD killer zip, right?);

swapped busybox in \system\xbin with the DATA2SD one (though it's older...);

swapped fstab in \system\etc with the DATA2SD one;

inserted the 5 files (debugfs, e2fsck, ...) in \system\bin\;

inserted the 7 files (libext2fs.so, libext2_blkid.so, ... ) in \system\lib;

now I don't know what to do with files in META-INF and scripts.

I know I'm an Android (Linux) noobie, hope Windows knowledge may help somehow! :D

EDIT: actually, removing apps from the zip ain't difficult at all: open in 7zip, delete the apk's I don't need, close it and flash... am I missing something?
[Desire Android Development] sibere:
The problem with A2SD roms, is that the A2SD stuff can be spread in other directories, even in the init.rc script. This is why I don't recommend to use a A2SD ROM to use DATA2SD. Do you have any other script in init.d? did you chmod 01data correctly? You should also rename 01data.txt to 01data. Many ROM have different ways to implement A2SD and it's near impossible to deal with those different options.

To make it simple for you, try to start with an non A2SD rom :) (init.d script enabled though)
[Desire Android Development] Droidzone:
Sibere, he didn't even prepare the file system. He didn't do any of the initialization. He just placed the files in place.didn't set any permissions or the mk2fs.

Instead of trying to reverse engineer the script, why didn't you just follow sibere's instructions from the op? If you didn't want to use the flash, this would have been the most straightforward approach.
[Desire Android Development] teorouge:
Oh, don't even know what chmod is (I'm googling now, btw)! Thought it could be just a delete/move/copy files inside zip to achieve DATA2SD from scratch, but I'm not ready to mess with scripts... maybe I'll ask Ne0 about his APP2SD+ scripts to remove. :)

Thanks, for the time being then I'm going with the usual (boring! ;) ) full wipe, ROM flash and install (1st time) DATA2SD procedure (as this is a new ROM version and I'm full-wiping)... thanks anyway, this mod rocks to no end!
[Desire Android Development] sibere:
Well in that case you should read carefully the OP before trying anything yourself and then asking why it's not working ;)
[Desire Android Development] ceno666:
droidzone, just wanted to let you know...i think there was something messed up with my clockworkmod, now the desire is S-OFF with alpharev and this fixed clockwork as well.

Just installed DATA2SD with your packages and now finally the ext4 is in use! yeah! :-)
[Desire Android Development] alexcavaco:
sibere,

With the performance improvements for the next version of DATA2SD, do you think journaling could be enable without lowering performance too much?

I'm just thinking on the case of using an 'adb reboot' or any other reboot that does not do the HTC's clean umount of data.
[Desire Android Development] sibere:
Honestly I haven't played too much with journal options to tell you wich one is better for safety or which one is better for performance when using DATA2SD. I'd say if you want journal, just use tune2fs to add a journal. leave default mount options.
[Desire Android Development] ceno666:
What is the best way to benchmark the I/O performance?

Now that my desire is running with DATA2SD iam not really sure that it got a performance boost.

I want to compare the difference with numbers, any advice?
[Desire Android Development] [deXter]:
Look for a program called "Tap Benchmark" in the forums.
[Desire Android Development] ceno666:
thx, i get 4558... please let me know what is your score.
[Desire Android Development] sibere:
Quadrant (free) is usually used to bench phones.
[Desire Android Development] ceno666:
@quadrant i get 1167
[Desire Android Development] [deXter]:
Tap Benchmark: 7088.

Quadrant: 1831

Specs:

SDCard: 8GB Transcend Class 6 with journaling enabled

ROM: Oxygen2.0 RC7 (OS: Gingerbread)

Launcher: LancherPro Lite (no widgets or LWP. only icons.)

Kernel: default (_thalamus kernel)

CPU Scaling: none/default; default governor (ondemand?)
[Desire Android Development] Lanbase:
dexter do have journalling of or on, do you use the latest test versions of oxigen? have you applied sqlite hack? is your logcat clean ( no permission errors?) is your ext fs reported clean in recovery?

how did you setup data to sd?

lol, alot of questions, its just i am running oxygen and data2sd aswell

and have some minor issues.

grtz

Sent from my HTC Desire
[Desire Android Development] sibere:
WOOW!! Literally WOW! Over 7000 at TAP!!

I must have a sh*ty SD, I can only get about 3000 (class 6 transcend)
[Desire Android Development] [deXter]:
Hi,

1. I kept journaling on when I was on Oxygen, now that I'm using Starburst (Sense HD ROM) I find no need to use journaling. (But those scores were with journaling enabled. I remember getting ~2200 on Quadrant without journaling)

2. Yes, applied the libsqlite hack.

3. No, had a ton of permission errors as well in my logcat. I've reported it but no one seems to know what's the cause (or have just ignored the post...) I still intend to find out though what's the cause for those errors (in the future). I have a feeling they could be the reason for some of the issues I've faced in Oxygen / Gingerbread.

4. Generally yes. On Oxygen, at boot time I usually see that fsck has to fix a few things and the fs gets modified - for the most part the system seems to work fine but occasionally an app stops to work (probably because of corruption that fsck couldn't fix) so I just reinstall the app. Haven't faced this behavior on StarBurst though as Sense based ROMs cleanly unmount /data.

5. @sibere as well: Forgot to mention that I'm also using the using the Dalvik2Nand script, so there isn't too much I/O load on the SD.

Also for StarBurst, I've resized my MTD partition such that /system is 250MB , /cache is 150MB and the rest is for /data (~45 MB?)

Also, since I've moved to StarBurst, Tap scores have fallen to ~3000. Perhaps Gingerbread has some new I/O or db optimizations?
[Desire Android Development] sibere:
Well if.you've reduced your data to such a low value, you may get issues in the near future because now /data is used to store dalvik-cache data. Why did you change /cache from 40 to 150mb ?

Sent from my HTC Desire with DATA2SD :)
[Desire Android Development] th3:
Looks like a broken bench - too easily manipulated by drastic margins.

2800-3000 in TAP is pretty bad seen as I get that with the standard Class 2 95% full, internal NAND full and 180 apps in D2SD + dalvik-cache on SD with a Sense HD ROM.

------------------------------

- Sent via HTC Desire -
[Desire Android Development] [deXter]:
My dalvik-cache is on /cache.
[Desire Android Development] sibere:
So you've modified the

01data script and the simlinks don't you? On the last version, dalvik cache is stored on mtdblock5 (NAND data)
[Desire Android Development] sibere:
could be a broken bench indeed.
[Desire Android Development] Droidzone:
@Sibere, I was reading through that forum about optimization of Fat. Should I remove the ext partition before doing that?

Also if I do the optimization of Fat32, then create an ext and restore Nandroid, would that lead to a loss of optimization?
[Desire Android Development] [deXter]:
Yep. I've been doing that way since a while now.. besides, it makes more sense to have dalvik-cache in the /cache partition.

No need to remove the ext partition, although you could end up with a few KBs or MBs of unpartitioned space in between the two partitions (not an issue though). And no, restoring nandroid will not lead to a loss of optimization as nandroid doesn't backup/restore to the sdcard.
[Desire Android Development] alexcavaco:
Doing a nandroid in ClockworkMod 2.5.0.7 it does backup the ext4 partition data and also restore's it.

I do not know if it restores the entire partition (with size and options), or if it just restores the data.
[Desire Android Development] [deXter]:
Hmm, that's odd. On 3.0.0.5 it just backs up the main partitions as defined in the system - it doesn't explicitly backup sd-ext. Also, while backing up I've noticed that it "copies" the files, so I'm pretty sure that it should also be restoring the files - because if it were to create an exact image of the partition (say, using dd) then it would have to restore the image thus you'd be loosing whatever fs optimizations you've performed. Which is not the case here.

In any case, since it doesn't touch the FAT partition (except for .android_secure), it shouldn't mess with the FS layout on the sdcard.
[Desire Android Development] Droidzone:
You must be using udk's buggy version of CWM. sd-ext is backed up by kali's CWM 3.0.0.5R3
[Desire Android Development] [deXter]:
Thanks, wasn't aware of a second CWM. (Only recently switched over to CWM from AmonRA)
[Desire Android Development] rayiskon:
first of all are u sure u have a kernel that supports ext4?

one more thing, i have a feeling that u didn't let the system boot and stabilize after flashing a2sdkiller, or did u ?
[Desire Android Development] Araba21:
But the ROM supports ext4. I have never installed the kernel.

Which kernel do you recommend?

S2dkiller But I have to use it or not?

I have a bit of confusion.
[Desire Android Development] rayiskon:
did u flash one of the recommended kernels in the OP of ur ROM thread ?

Kernels:

For Desires that supports low voltages in all freqs:

875mVSpecial -NeoPhyTe-2.6.32.28-Halcyon_HAVS.875Esp_CFS_SLQB_VR_v38-> http://neophyte.vipme.com/ftp/_Extra...LQB_VR_v38.zip

For Desires that supports low voltages:

875mV -NeoPhyTe-2.6.32.28-Halcyon_HAVS.875_CFS_SLQB_VR_v38-> http://neophyte.vipme.com/ftp/_Extra...LQB_VR_v38.zip

Default included in the rom:

925mV -NeoPhyTe-2.6.32.28-Halcyon_HAVS.925_CFS_SLQB_VR_v38-> http://neophyte.vipme.com/ftp/_Extra...LQB_VR_v38.zip

For people who have lags and/or reboots:

1000mV -NeoPhyTe-2.6.32.28-Halcyon_HAVS.1000_CFS_SLQB_VR_v38-> http://neophyte.vipme.com/ftp/_Extra...LQB_VR_v38.zip

for this rom u had to apply the a2sdkiller ,so u're ok with that step, but after flashing it u should restart and see if the system boots without any problems...this step goes before flashing the data2sd script
[Desire Android Development] erklat:
Are you sure he has to use a2sdkiller as I don't see any mention of it in the tutorials on the first page?

I thought too he probably flashes multiple things at once, as advised in the AuraxTSense thread.

What if I titanium backup my apps prior to enabling data2sd, and afterwards I batch restore them, where are my apps going to end if half of them was installed to nand and the other half on the fat partition?
[Desire Android Development] Araba21:
I followed this guide:

1. Complete wipe

2. Install any Rom (which satisfies the requirements of Data2SD listed in the OP and recapitulated above) through recovery

3. Once the Rom installation finishes, without leaving Recovery, immediately flash the A2SD Killer flashable zip.If flashed on a non-A2SD Rom, the flash wont do any harm.

4. Now reboot once into Android desktop. (If the system fails to boot at this point, it means that some exotic A2SD script is lurking beneath.). Do NOT, I repeat, DO NOT install any applications on first install. Do not even enter the Android Market!

5. Once you confirm that the Rom boots fine, Reboot into Recovery once again

6. Now flash the Data2SD Installer zip. After it finishes installing, boot into Android and enjoy Data2SD

But I have to install a kernel over the rom?
[Desire Android Development] Araba21:
But you have to unlock your device NAND with AlphaRev?

or not necessary?
[Desire Android Development] erklat:
No, you have the kernel which is compatible with this script if you are using AuraxTSense.

I suggest you skip flashing radio at this moment and flash only rom, killer and data2sd zip, but only one thing at a time booting to os after every step!

No alpharev, most users don't need it but do it nevertheless out of boredom I guess, but at this time you could do more harm than good with it.

If this happens too, it could probably point to SD card malfunction? Have you partitioned it correctly?
[Desire Android Development] rayiskon:
the ROM he flashed has app2sd+ script ,so the killer is necessary

quote: step 3 from droid's guide: Once the Rom installation finishes, without leaving Recovery, immediately flash the A2SD Killer flashable zip.
[Desire Android Development] erklat:
This is not possible. It is the same as if you went and bought a car without an engine. If he flashed AuraxTSense, he has right kernel for the job.
[Desire Android Development] rayiskon:
i forgot he's stuck at the boot screen, he can't see what kernel he has,obviously.

and ya logically he would've got the right kernel with the rom, don't know what i was thinking, guess it's way past my sleep time :D
[Desire Android Development] erklat:
At this point I would repartition my SD card and try again with Starburst. I guess no point in trying to get this running if that failsafe solution can't work either. Make it work first and then switch to AuraxTSense later.
[Desire Android Development] Araba21:
Erklat,

I partitioned the card again, without a wipe.

AuraxTSense ROM installed and restarted.

Everything is OK.

The Kernel is 2.6.32.28-Halcyon NeoPhyTe.x360@SnowLeopard#38
[Desire Android Development] Araba21:
Now reboot and repass in Recovery and install the A2SDKillerV5.zip
[Desire Android Development] Araba21:
after flashed A2SDKiller, appears this inscription:

this is meant to be flashed immediately after flashing an a2sd based rom, even before rebooting.
[Desire Android Development] Araba21:
When you restart crashed again on the screen "HTC"
[Desire Android Development] Araba21:
erklat, speak a little Italian?
[Desire Android Development] erklat:
No, I don't, sorry. :(

How do you partition? Try using gparted or some similar tool. Recoveries are known to generally do poor job at partitioning. Try getting Starburst to run first, use droidzone's guide for that. That way you can rule the SD card out as a potential culprit.
[Desire Android Development] Araba21:
I partitioned with Gprted_live. I tried again to reinstall AuraxTSense, and soon after A2SDKillerV5.zip. I rebooted and it works. Now I have to come in and install DATA2SD recovery.

Let's hope so!
[Desire Android Development] Araba21:
screen freezes on "HTC".

Tips?
[Desire Android Development] Lanbase:
Thanx for your reply Dexter.

cheers

Sent from my HTC Desire
[Desire Android Development] Droidzone:
That's right.

You did it wrong. Flash Aurax, without leaving recovery flash a2sd killer. Now reboot, setup iniitial settings (but not google account)

Now reboot to recovery and install data2sd installer Now reboot again

This is correct
[Desire Android Development] Araba21:
Hangs on the screen "HTC". I have to wait for more than 10 minutes?:o
[Desire Android Development] Droidzone:
Usually you shouldnt need to. I've tested these Roms, and I've never had to wait for more than 2 mins. If you have adb installed, you can make a log, as detailed on my rom's page..

http://starburstrom.wordpress.com/s...w-to-create-an-error-log-for-troubleshooting/

I havent tested with Aurax 8.4. I'm not sure if Neo changed something in the a2sd script. If he's using Darktremor beta, there are bound to be problems. However with 8.3, I had no issues.

I'll test 8.4 too for good measure.
[Desire Android Development] Araba21:
DroidZone,

you test the 8.4?

thank you very much:)
[Desire Android Development] Droidzone:
I tested it out today. Unfortunately the rom doesnt boot after a2sd script is killed by the killer. I wish I had time to investigate why, but right now I dont. Usually it is a matter of removing a2sd scripts from init.d. In darktremor beta, it is usually more. So, currently uploaded scripts do not work on aurax 8.4
[Desire Android Development] sibere:
With so few informations and indications.. no
[Desire Android Development] craig1965:
Hi I want to try an add your data2sd script to teppics Rom which currently supports apps2sd+ ext2 I spoke to teppic he says a module which supports ext4 will do it

Or could I just follow your guide on page 1

What im trying to achieve by doing this is the ability to migrate between teppics Rom and Starburst without having to re partition the SD card every time
[Desire Android Development] Droidzone:
Flash an ext4 kernel over his Rom, then do Sibere's procedure by hand (or zip). That should do it. I dont see why the repartitioning has to be done at all. Btw..both teppic's rom and Starburst are based on 2.29.405. I dont think you will find much difference between StarBurst lite and teppic's stock rom w/o mods (but with ext4 kernel).
[Desire Android Development] teorouge:
Actually, I'm using that... 8.4 DATA2SD enabled (see signature for the files I used).

Coming from 8.3 (DATA2SD enabled already): full wipe (I alwas do that), cache & dalvik wipe, flash rom, flash killer, boot, complete first time config, reboot, flash DATA2SD Installer, reboot, 8.4 running with 1GB ext4! :confused:

I removed some apk's/stuff I didn't need and replaced widget.txt but I don't think that matters... does it?
[Desire Android Development] sibere:
If you read the OP carefully, you'll notice that my rom ATM is teppic's rom so there is a good chance that DATA2SD is gonna work :)

All you need is to follow the OP and get an EXT4 compatible kernel like RichardTrip's kernel. Ext4 must be into the kernel and not as a module (could cause issues)
[Desire Android Development] Droidzone:
Yea, you're right. I've been having weird issues myself lately, where my perfectly working ext4 partition suddenly seems to have been transformed into ext3. Suspect mos likely seems to be the latest CWM. I'm back on ext4 and will get around to some more testing soon.
[Desire Android Development] Droidzone:
Oops..Wrong thread!
[Desire Android Development] sibere:
Imho the besdt and more stable cwm is 2.5.0.7. That's why I don't update it ATM and I recommend to keep that version on your phone if you have it or even to roll back to it.

Sent from my HTC Desire with DATA2SD :)
[Desire Android Development] Droidzone:
Yup. That's my opinion too. That was Koush's last version, and time tested. I though most issues were fixed in Kali's new version, but I have no idea why otherwise my perfectly working ext4 partition one fine morning was transformed into ext3. :)
[Desire Android Development] Kalashnikitty:
Hey guys,

is it possible to implement data2sd in a rom without flashing droidzones zip?

i tried it with my miui-rom but it stuck at boot. but works after pulling battery and flashing the reinstaller.
[Desire Android Development] [deXter]:
Just follow the instructions in the OP.
[Desire Android Development] Droidzone:
I wonder why that kind of request is coming repeatedly. The flashable zips are placed far below the OP, and people should be coming to it only after reading the OP. Wonder why are they still asking if there is code for the zips!
[Desire Android Development] sibere:
Simply because it's easier to click , download, flash , and ask why it's not working or for help instead of reading the OP completely... Laziness and idleness you know ... :/
[Desire Android Development] Kalashnikitty:
I think u did not understand me. I want to build this in my rom cooked it, flashing it. nothing more.. the usually way is working fine. but i didn´t want to flash my naked rom an then do the data2sd stuff. and i have read the OP more then enough :)
[Desire Android Development] sibere:
I this the answer wasn't aim at you ;)

But there should be a way to implement DATA2SD straight into the ROM.

This requires a lot of scripting from the ROM dev
[Desire Android Development] Kalashnikitty:
Oh sry sibere. Ya im working on it with miui 1.2.19 but it fails at boot. :mad:
[Desire Android Development] sibere:
Yep that's why Droidzone came up with ZIPs to flash after the 1st boot because it wasn't working.
[Desire Android Development] ownhere:
MIUI ROM need modify ramdisk to support D2SD/EXT.
[Desire Android Development] sibere:
Thanks for letting us know ownhere :)

This explains why they can't get it running from start.

I can't try each and every SENSE/AOSP ROM to check from compatibility but they must meet at least the requirements posted in the OP.

Obviously if there is no init.d supports, D2SD/EXT can't work.
[Desire Android Development] Droidzone:
But miui does have init.d (Busybox runparts) support. Miui is released as a2sd/d2w editions, both of which have busybox runparts support. I got better results with miui d2w (cleaner with no a2sd) after removing melethron's d2w script.

But I was still unable to integrate d2sd into the initial bootscript. I'll be trying with some modifications over the next few days to 'crack the code' :)

By the way, miui will support d2sd if the 01data is loaded as a service in init.rc. Maybe that's what ownhere meant. We've adding this line to init.rc since CM6. The cm supported zip I uploaded does that.
[Desire Android Development] ownhere:
Offical MIUI ROM 'class_start' no protection.

need modify below line:

class_start default

to:

on property:cm.filesystem.ready=1
class_start default
[Desire Android Development] Droidzone:
Ah I get it..

I was using miui_au which has the solution since it comes with d2w and a2sd.

Thanks, Ownhere.. We did use this solution on my rom once Sibere discovered that it had the same problem..
[Desire Android Development] blowy666:
Hello everybody,

I havbe flashed CyanogenMod 7 Nightly on my Desire, and then flashed the Data2SD from this postv on this thread here:

http://xdaforums.com/showpost.php?p=10692249&postcount=1299

Works like charm...but now I have one "problem":

My ext4 has a size of 1,8GB.

Now I have 611MB left, but I could not install one more app.

Always tzhe message "not installed" when I start an apk...

Is this a known bug?

Is there a way to "fix" this?

Titanium Backup says I have installed 327 User apps on my phone...
[Desire Android Development] kl_arnet:
...sounds familiar. ;) Your Dalvik cache is full. Very common issue to the latest Data2sd script with dalvik2nand mod. ;)

Fix - uninstall some apps, clean dalvik cache or use data2sd without dalvik2nand mod.
[Desire Android Development] blowy666:
Thanks for your answer!

Hmm...is there a zip file with Data2SD WITHOUT this dalvik2nand mod anywhere?
[Desire Android Development] Droidzone:
Only one problem..Dalvik2Nand isnt released here yet!
[Desire Android Development] blowy666:
So the only way is to uninstall apps? :confused: :(
[Desire Android Development] kl_arnet:
... Sorry. I've end up here looking for partitions alignment tips and symptoms were so typical.

Didn't know you and Sibere are so ahead with StarBurst.

Swyped via StarBurst Desire.
[Desire Android Development] [deXter]:
To confirm if it *is* indeed a problem of your dalvik-cache becoming full, I would suggest you do the following:

- post a logcat captured during the installation of an app

- post the output of the following command:

df | grep -i /dev/block/m
[Desire Android Development] blowy666:
When I write this command on the terminal on phone, it says me "can´t find mount point"...

Here is what adb says:
[Desire Android Development] sibere:
You've installed data2ext or a a2sd rom/script don't you?

Your nand is mounted to /system/data_internal which is used by data2ext and is not compatible with data2sd.

Data2sd beta uses /system/data.

Appart from this, your storage is not full :)

Sent from my HTC Desire with DATA2SD :)