yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] melethron:
If this is not the log of the

first

boot that is fine.

Error on e2fsck is normal and it is no issue (it only doesn't notice if the partition is unmounted ... but it is and it still does it work). Also the copy errors of dalvik-cache, app, app-private, data and dontpanic are fine... these files aren't there because they are already on sd so these errors are normal. The script tries to copy everytime it boots in case of a ROM update in future. If it can't copy it just tells you that the files aren't there.

Did you try other data2sd scripts (or ROMS with it) and had fewer lags there?
[Desire Android Development] Dave_G7:
first thx all developers for the parts they programed!

this night I repartitioned my sd card (class 6) with gparted, 1gb raiserfs (aligne to Mib, in gparted as easy like scratch some part of ur body... :D )

Full wipe, install worked, took some time to boot, OK, then cooshed the language, and I felt a asleep ... ;) The responsiveness of the phone was like I action per 5 minutes, it crashed, often just a white screen with the green HTC logo was to see...

OK I know that i takes a long time to run... but this way u cant even make the setup... wait 2-3 hours?!?! its a bit crazy...

its cause of the raiserfs or its really the data2ds?!

THX dave

Edit:

PS: where the "bell" can i find the 2.0.1 AmonRA?!
[Desire Android Development] melethron:
Well i skip the whole setup and restore my apps with titanium backup first. Reboot and then i set up the rest. So for me it's smooth from the beginning.

If it downloads like 100 apps after firstboot it will we be laggy. But it shouldn't be THAT unresponsive.

As i said i do get lags on market downloads but thats the case in any data2sd script. I tried everything and nothing really helped on this. But apart from downloads/installs it should be completly smooth.

Amonra 2.0.0.1 can be found somewher inside amonra threads. For some reason he didn't update the main post.
[Desire Android Development] jkond:
I flashed the Avaritia data2whatever rom and its quite charming with the reiserfs partition!! very close to classic a2sd+..

note that i ve tried all version of data2sd-ext before and this one made the difference.

nice work!
[Desire Android Development] melethron:
Lucky that at least some get a speed improvement from the way the layout of the ROM. For me it is also the fastest data2sd solution so far. This seems to be much depended on the microSD card (not the class / mb/s but of the controller).
[Desire Android Development] jkond:
In my case i think its the FS (reiserfs) that made the difference. My microsd is a common class 6 8gb, and all the tests have been done with this card with previous releases of data2ext (ext2,3,4 & fat32 second partition). I also use Gparted (align to MiB) for partitioning.
[Desire Android Development] melethron:
I think alignement is what makes the biggest difference. ReiserFS is a bit faster than ext4 but after i made a proper alignement ext4 was also MUCH less laggy. Thats why i want to make a script (as optional addon) that recreates an aligned partition (if not aligned already) on the first boot. Should be able to do that with fdisk (i already know the way to do that but my scripting skills aren't good enough to make that "automated" ....)
[Desire Android Development] animehq:
any news?

An Avaritia HD v0.4 come?
[Desire Android Development] fossean:
Many thanks Melethron, very nice rom. Fastest/least laggy of the HD roms that I have tried, so I'm going to keep this one on my Desire.

I read with interest your discussions with Ownhere, regarding data integrity versus speed. I share your concerns about SD data corruption; but it is also great to have the option to live dangerously with your 'Life On The Edge' patch :) When I have time, I will try it out...

I hope that the latest Pays-Rom can iron out the bugs so we might see an update in Avaritia. I quickly tried to install pays-rom 1.1 with your data2whatever scripts, but it hung on the homescreen; to be expected I suppose.

This rom deserves a lot more attention, it's really very good!
[Desire Android Development] melethron:
I already made 0.4 but i made some more changes. The next release will be 0.5 and it will have more features. I wanna include all the changes i did to data2whatever first. Also i want to edit the post and make a proper feature list because the ROM will have features that aren't present in other HD Roms like:

- partition alignement on very first install (~20% more speed for data2sd)

- optimized layout for data2sd (system apps on NAND)

- choice between a "loop" mount and a "normal" one (life-on-the-edge)

- ReiserFS support

- swap partition support (HD roms need more RAM than normal ROM - swap helps then)

- "deadline" scheduler instead of cfq/bfq which is better for microSD

Since i also want to explain the features i need a bit time.

Hey, happy you like the ROM. About the risk of data loss. I dont think its a real issue in most cases. I wouldn't mind if loose all my data (i only would need to set up the apps i use again). But some users may have "save games" of games that they would miss. That is the reason i thought i make it optional. Most users backup often anyway because of wipes and the worst case of "life on the edge" would be that you need to wipe sd-ext and data.

About the update. I wont change to 1.1. I'll update the apps myself. Since the "base" of 1.1 is a Z rom (and not even a newer one) i dont wanna change to that. The reason that update is delayed is NOT pays rom but my data2whatever script which needs bugfixing to work with as many roms as possible.

Also about the ROM in general. Im sure it WILL get more attention. All i did so far was optimizimg data2sd. I don't even start to optimize the ROM itself. If im happy with data2sd ill take a look at other HD roms and see what improvements i'll include from them. I also plan to remove some stuff from the ROM that isn't needed (most stuff that is available in market).
[Desire Android Development] fossean:
Thanks for all these details, that is very good news!

I look forward to playing with ReiserFS and life-on-the-edge. I'm not too concerned about the tiny risk of data corruption; it happened to me a couple of times (with a different rom) after a bad flash, so I always have a recent backup now.
[Desire Android Development] melethron:
Updated the OP.

All the changes are included now .... data2whatever can wait ... Rom comes first ;)

Please note that "loop" mount (aka life-on-the-edge) only applies to ext2/3/4 atm. I didnt make test with ReiserFS and loop mount yet. Apart from that ReiserFS felt faster then ext4 with loopmount. Ill make some test later and if ReiserFS loopmount is an improvement then ill add this.
[Desire Android Development] Terepin:
How long it suppose to stay in initial htc logo? I'm waiting 10+ minutes and still nothing.

EDIT: ReiserFS -> ain't working at all.

Swap + Ext3 -> Sense won't start -> ain't working.

Ext4: Ditto.

EDIT 2: Actually, it IS working. It just takes 20 minutes from PIN screen to Language screen.

EDIT 3: It's working with life-on-the-edge patch applied.
[Desire Android Development] jkond:
Was already fast with 0.3 and reiserfs...now i will try 0.5+reiserfs+swap...
[Desire Android Development] Terepin:
And don't forget to add new base with FroYo 2.2.1!
[Desire Android Development] jkond:
ok, here is what I noticed:

It is even faster than 0.3+reiserfs

better scrolling between screens with no lag at all

faster boot time

lags a little when synchronizing

no problems with market. (very fast too)

as said i tried 0.5 + reiserfs + swap (made it 100mb)

didnt try without swap, so i cant say if the new rom is faster or the swap makes it.
[Desire Android Development] melethron:
Since your partition was aligned before and you already used reiserfs i think the difference should be the swap. This was ownheres idea. The reason is that HD roms need much ram. If android runs low on ram it will kill stuff. Reopen these needs cpu and read from dalvik cache and opening the apk. If a swap is present (and swap on) the process wont be killed but moved to swap instead. I set a low a swappiness value (20) so that android still prefers ram. I also felt that swap makes thing better in most cases. The only situations it felt a bit worse is after the phone was idle for some time.

I think the next step i will focus on the rom.

I noticed something similar (link) in the data2whatever thread. Some sd-card seem to be horrible slow in sqlite performance. I have no idea how to solve this (and if its even possible to speed up with a filesystem). Did you have issues with other data2sd roms?
[Desire Android Development] fossean:
Any advice on how much swap to allocate? I've just repartitioned with ReiserFS and 64Mb swap, but it was just guesswork!

Will try installing 0.5 in a moment, many thanks for everything.
[Desire Android Development] animehq:
0.5 + reiserfs + swap it's really fast :) GG
[Desire Android Development] melethron:
Im pretty unsure myself. Ill give some recommendations in future.
[Desire Android Development] Terepin:
Nope, ReiserFS isn't working for me at all; Desire won't boot into ROM.
[Desire Android Development] melethron:
Could you post me a logcat from the boot and the "avarita-log.txt" (in /sdcard) would also help.

I have no idea where the issue lies, since it works for others (and me).

My guess is that its either:

a) A problem with the hardware ... some sd-cards are - so to speak - weird ...

b) You made Reiser4 instead of a ReiserFS (3.x) Partition.
[Desire Android Development] Terepin:
Nope, I used ReiserFS. I will try it again, since I formatted my SD card. I can tell that on Ext3 + 128MB Swap with accessing SD card = unresponsive. I will attach log for each setup, here is Ext3.
[Desire Android Development] melethron:
The partitioning work fine and i cant see something from the log.

Can you do a "adb logcat" on boot.
[Desire Android Development] Terepin:
I have absolutely no idea how to do that.
[Desire Android Development] melethron:
SDK is needed for that. Its not that hard to setup and can help greatly in "debugging". http://developer.android.com/sdk/index.html

I think i add more stuff to the log in the next version.
[Desire Android Development] anko184:
Just finished installing Avaritia w/ 1.5 gb ext4. It feels pretty smooth until now in comparison with other HD rom's.

You should definitely check the 1.72.xxx.x base as it feels quicker than 1.32.

PS: First boot took less than 10 minutes.
[Desire Android Development] Terepin:
Now THIS is what I'm calling log! :D

Note: I was waiting 30 minutes.
[Desire Android Development] scoubi_doo:
i test the rom but after booting i arrived on the lock screen

if a unlock the screen a white HTC screen staying.

you can see my log file

thanks for helping

my micro SD is partitioned :

FAT32 :6.7GB

EXT3 : 980 mb

can you help me ?

thanks
[Desire Android Development] Terepin:
I have the same issue, you just have to use live-on-the-edge patch and it will be better.
[Desire Android Development] melethron:
I will rebase the ROM but this may take some time. This is my first ROM and im not really expirienced in making roms yet. But i take a look at a prerooted HD rom and see what i need to do.

EDIT: Your sure 1.72 works on desire ??

Log only does e2fsck when there is an ext partition. So this looks normal. I need to add more stuff to logging for those that have no "adb".
[Desire Android Development] mattiadj:
How can i have the standard dhd theme?
[Desire Android Development] scoubi_doo:
Nothing happend with or without the patch ...sadness !!!
[Desire Android Development] melethron:
Did you test other data2sd roms? At the moment i think this is a issue of the sd-card. But im not 100% sure about that.

You can select it under "personalize". Just select "HTC" instead of "music lover".
[Desire Android Development] azure89:
Hi there! I'm very interested to flash this HD Rom.

Just a question, which partition setup would you recommend for this rom to work proper?
[Desire Android Development] Terepin:
robocik's Z 0.6 is based on it. The base itself is faster. Now, imagine the speed with your ROM...
[Desire Android Development] ciairo:
Hi,

I'm experiencing the same issues that as others had.

I've partitioned the SD card with:

- 1st partition: FAT32 (about 6,5 Gb)

- 2nd partition: ReiserFS (1 Gb)

- 3rd partition: swap (100 Mb)

the ROM installs, the phone boots but when unlocked there is no launcher, only a white screen with the HTC green logo. The phone itself works. e.g. you can connect and execute commands via ADB but no way to overcome the screen unlock.

2nd test: on purpose i did the same partitioning but not aligned to Mb, therefore the install procedure changed the 2nd partition to EXT3.

Again, same issue as before: phone boots, but white screeen.

Log attached. logcat is a bit more difficult as it keeps on updating (cos the phone is actually working)., but I can look for something particular if you guys have any clue on that.

Update: it might be a matter of extreme slowness of the configuring application because if i leave the phone for a while I get the "select your carrier" screen, but again when pressing the "next" button again white htc screen.
[Desire Android Development] melethron:
I test a prerooted stock rom atm. I'll see if i manage to get that to work . If not i'll take a look at robocik's rom.

Did you also have this issue with other data2sd roms?
[Desire Android Development] ciairo:
Nope, I only tried Robicik's one (the HD one I mean, not the Z) and despite of the lags it was working.

I finally got yours working too, it was really a strange delay on the initial setup. Still have to test, but i would say that the normal functioning is quite smooth (I'm on ReiserFS atm). But each time I reboot it takes ages to come back.

So, if it stays like this is definitely something I can live with :), but there could be some little space for improvements on the boot.

Anyway, I find the work you are doing with that amazing. Keep it up, and thanks a lot :)
[Desire Android Development] jkond:
when u see this htc white screen, try to touch the screen....
[Desire Android Development] melethron:
Hmm, a logcat while its stuck would help maybe. If it was the robocik version with loop you could try life-on-the-edge.
[Desire Android Development] Tsuneku:
Same here.

All wipe and SD format before flash, Fat32 + 2giga EXT3 without swap, 15 minutes from the first boot and always on HTC green logo :(
[Desire Android Development] Terepin:
melethron, give me links to benchmarks of which results can help you improving script, please. Consider me as your new stable and official tester. :)
[Desire Android Development] thay:
Tsuneku it's a sd issue tray another card,i tested this rom with many sdhc and have no problems with all my sandisk(class2 and class4)

With kingston sd i can not boot with this rom

D2sd don't work with all sd cards

Ciao tsuneku :)
[Desire Android Development] thay:
@melethron is this rom deodexed?
[Desire Android Development] anko184:
Yes it is!
[Desire Android Development] Tsuneku:
Right, its only a question of patience: after 20 minutes in white and green htc logo, set the default value without sync, first reboot of 15 minutes its run smoth and fast, very impressive. I have try dhd, rcmix, baanewz and z rom, but none was fast like Avaritia. Now try to restore with titanium the app.
[Desire Android Development] nickislauw:
720p record works? Its not at the issue list ^^
[Desire Android Development] Tsuneku:
In this moment you can't find an HD rom where the 720p work in native htc sense app, and with a good sd card you cant find a rom fast like Avaritia :) .
[Desire Android Development] nickislauw:
ok tnx. Well i got a 8gb class 6. So it will be speedy?
[Desire Android Development] Tsuneku:
The problem isn't about the write or read speed, the problem is the number of (little) files that data2ext write (sqllite). Sandisk, in my experience, never gives problems, I have a transcend 16gb class 6 and with this rom work very well. Try, is the only road to be sure :)
[Desire Android Development] anko184:
But not a cheap one:D

I bought the other day a transcend like yours, let's hope it's fast with d2we.
[Desire Android Development] ciairo:
well, an immediate finding: on boot the system stucks at:

+++ Checking external Partition:

that means that the blocked commad is:

busybox mount -o noatime,nodiratime,nosuid,nodev /dev/block/mmcblk0p2 /data;

It really takes more than 30 mins to go past that, every reboot.

On this test I had removed the swap partition to check if anything would change. No changes actually.
[Desire Android Development] Tsuneku:
i dont have the swipe partition and I can confirm that every boot is very very slow.
[Desire Android Development] Tsuneku:
With Sd Card speed test I read and write at 11mb, at runtime the rom i very very fast, the problem is only at boot. :(

I hope that melethron can find a solution.
[Desire Android Development] fossean:
I know Quadrant scores can be unreliable, but I just got a score of 2018.

Not bad at all, considering the kernel is running at stock speed.

Running Avaritia 0.5 with 1280 Mb ReiserFS, 64Mb swap.

Kudos to Melethron!
[Desire Android Development] anko184:
When i find some time to change the card, i 'll let you know how quick is my boot or not.

But know with my 8gb sandisk class2 the booting time is around a minute which is really slow in comparison with an a2sd+ rom but it's very quick in comparison with your boot time.:p
[Desire Android Development] melethron:
Hmm. Im pretty unsure what causes this. The only idea i have atm that the cylinder bounderies may be the issue (but i actually would really wonder about this since cylinder are an old relict of floppy disk times).

The overlapping of cylinder shouldnt matter as long as sectors dont overlap.

# fdisk -lu /dev/block/mmcblk0

Disk /dev/block/mmcblk0: 15.9 GB, 15931539456 bytes
255 heads, 63 sectors/track, 1936 cylinders, total 31116288 sectors
Units = sectors of 1 * 512 = 512 bytes

Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 63 27117719 13558828+ c Win95 FAT32 (LBA)
/dev/block/mmcblk0p2 27119616 30107647 1494016 83 Linux
/dev/block/mmcblk0p3 30107648 31116287 504320 83 Linux
# fdisk -l /dev/block/mmcblk0

Disk /dev/block/mmcblk0: 15.9 GB, 15931539456 bytes
255 heads, 63 sectors/track, 1936 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 1688 13558828+ c Win95 FAT32 (LBA)
/dev/block/mmcblk0p2 1689 1875 1494016 83 Linux
/dev/block/mmcblk0p3 1875 1937 504320 83 Linux

as you can see here my partition 2 ends in cylinder 1875 and my partition 3 starts in 1875 but the sectors are fine. The strange thing now is that i dont get this message in fdisk (partition 2 doesnt end at a cylinder boundery).

You could still try if this is the error (but i cant promise it helps). You should repartition the sdcard with recovery (which does align to cylinder). And let the script do the alignment. The endsectors will then be on cylinder boundaries. But as i said im not sure how this could be the issue .... its just an idea....

Quadrant is not a good method to messure actual speed of the rom. "oxygen 2.0" has a much lower score but is faster as any sense rom ever can be ;) .
[Desire Android Development] melethron:
Its normal that it is slower. The script does some more stuff on boot than on app2sd:

- checking alignement with fdsik

- a forced filesystem check

(+remount to check what filestystem is used)

- creating and copying a logfile

- overall 4 seconds of sleep to make sure unmount works

this makes the boot at least 10 sec (maybe 20) slower than app2sd boot. And as i said that is completly normal.

The really long boot is another issue and im not sure what causes this. Mount shouldn't take more than 1 sec on ext or reiser (takes longer for the internal yaffs2 partitions ... but thats yaffs2 ... which sucks).
[Desire Android Development] Terepin:
My problem isn't in speed, but in responsivnes. If I run something for the first time, it's practically unusable and it's giving me "stop working" error. Syncing is causing this too. Looping did help. Maybe if I'll increase swap size (currently 128MB).
[Desire Android Development] melethron:
@all: Next update will take a bit more time than i thought.

Ill try to rebase to WWE 1.72.405.3 (ACE not the Z rom) but im a bit stuck at porting it on my own atm. I dont like rotating rosie and prefer a ace rom for a rebase. I hope i manage to get it working (i already asked ownhere for help).

Apart from that some changes for the next release:

- a proper installer

- a bit more logging

- an optional addon which will make a reiserfs partition on first boot (thx to ownhere who compiled the reiser tools for arm)

- fsck for reiserfs (thx again ownhere :) )

- a new kernel based on coutts99 latest HAVS kernel (changes are: reiserfs, btrfs, jfs, nilfs2 and deadline support, a different voltage table with slightly higher values and maybe some changes to scheduler: not sure about cgroup y/n and about cfs/bfs)
[Desire Android Development] melethron:
Im pretty sure that these issue are hardware related. Some cards have a really awfull sqlite performance and i think that is the reason. Loop helps in this cases because it delays the write. Maybe other filesystems may help on this but im out of ideas atm (and i cant do tests myself because my kingston 16gb class 2 card has a really good sqlite performance on almost all filesystems).
[Desire Android Development] Terepin:
Pretty much the same on all FS. Anyway, will increasing swap's size help me?
[Desire Android Development] melethron:
Dont think so because the issue doesnt lie in opening apps but in writes to /data/data.

You can test the sqlite performance on other filesystem if you use neophytes test kernel and make some tests with tap benchmark.
[Desire Android Development] Tsuneku:
I have the same problem, slow boot and some delay:

I don't understand, what is this ?

My benchamark says 2652 with EXT3 and no swap, someone that makes the benchmark for comparison my score?
[Desire Android Development] Terepin:
WOW, this is hardcore! Sync is causing music to chopp!

Gonna run benchmark right now.
[Desire Android Development] melethron:
The overall score is not that important. The important value is "DB writes" in the "detailed results".
[Desire Android Development] Tsuneku:
Well:

Overall performance: 2652(175)

Database performance: 321(19)

FileRead/Write performance: 1323(74)

...

DB writes: 8(5) writes

Thank's for your help :)

@Terepin: please run Tap Benchmark and post your result to compare our devices.
[Desire Android Development] Terepin:
Details of Performance on /data

Iterations: 6 - Single Test Duration: 1000

Timestamp: 20101231T143744

Overall Performance: 2908(128)

Database Performance: 364(7)

FileRead/Write Performance: 1563(57)

StressTest Performance: 981(114)

DB writes: 30(2) Writes/s

DB reads: 238(10) Reads/s

DB deletes: 277(3) Deletes/s

File writes 10k: 3150(39) kB/s

File writes 1M: 7481(1081) kB/s

File reads 10k: 4213(177) kB/s

File reads 1M: 9060(133) kB/s

File write Overhead: 1.838(0.197) ms

File read overhead: 1.27(0.101) ms

StressWrite 1M: 3589(902) kB/s

StressRead 1M: 5620(291) kB/s

StressWrite 10k: 1213(169) kB/s

StressRead 10k: 1788(320) kB/s
[Desire Android Development] Tsuneku:
Details of Performance on /data

Iterations: 6 - Single Test Duration: 1000

Timestamp: 20101231T141522

Overall Performance: 2652(175)

Database Performance: 321(19)

FileRead/Write Performance: 1323(74)

StressTest Performance: 1008(157)

DB writes: 8(5) Writes/s

DB reads: 212(19) Reads/s

DB deletes: 260(21) Deletes/s

File writes 10k: 2328(593) kB/s

File writes 1M: 2375(785) kB/s

File reads 10k: 4698(157) kB/s

File reads 1M: 10043(286) kB/s

File write Overhead: 0.084(1.77) ms

File read overhead: 1.133(0.076) ms

StressWrite 1M: 1936(714) kB/s

StressRead 1M: 6344(163) kB/s

StressWrite 10k: 1195(414) kB/s

StressRead 10k: 2008(375) kB/s
[Desire Android Development] Terepin:
What card you are using?
[Desire Android Development] Tsuneku:
Transcend 16GB class 6.
[Desire Android Development] Terepin:
A-DATA 16GB class 6.

How much it costed you?