yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] melethron:
@all: i think i revert the rebase and use RUU_Ace_HTC_WWE_1.32.405.6 for the next version. Cgroup isn't made for a phone and i don't like the idea of speeding CFS up by using foreground/background groups. BFS is made for slow/few CPUs (well with slow i mean the range between "phone cpu's" and a desktop machine with a "quadcore - with fast cpu i mean hardware the "enduser" will never see ;) ).

Hmm. I only changed the min value from 245 to 128. Not sure if coutts uses Powersave for "default screen off" profile. If yes then its throttled to 128 which can cause stutter on mp3s.

I use set cpu and use screen off profile with "128 min and 256 max" and conservative governor. This way it is 128 if the phone is completly idle (and conservative makes sure the clock doesnt jump to 245 very often) and when more cpu is needed for listening to mp3s then it goes up to 245. I like this profile. It can only lag a little bit if the phone wakes up because its still conservative for a second and the clock doesn't go up fast enough. If you don't like that lag use another setting (128-5xx smartass) for screen off. I can live with that tiny lag and conservative 128-245 gives the same batterylife as powersave 128 but without issues of mp3s then.
[Desire Android Development] paulove:
Where can i get that recovery?

paulove
[Desire Android Development] Lanbase:
What about the 1.72 base being "Amazing" with data2whatever then.?

Utptil now its working good 4 me.

grtz
[Desire Android Development] MATRIKS:
v0.5 won`t boot on JFS is that normal:confused:
[Desire Android Development] Fightspit:
Did you install the kernel (in the post#2) right after installing the v0.5 ROM ?

If no, you must do that.

Anyway, I would like to know if the JFS allows us to restart or shutdown the phone normally without corrupting it ?
[Desire Android Development] MATRIKS:
Yes . Look like no sript suport for JFS then
[Desire Android Development] Fightspit:
Did you try to go in your recovery mode and mount the "sd-ext" ?

If you can't mount it, so that is cause your problem ^^
[Desire Android Development] MATRIKS:
OK so what should i do ? Flash recovery with FS suport but i think i allready do that :confused:
[Desire Android Development] melethron:
2nd post of the thread has all the "mods" ....

I compared that with neo's

cfs

kernel since i didn't have a BFS kernel with the filesystems supported. It is faster then because cgroups.... On BFS cgroups wont run and bfs is directly optimized for interactivity. Using cgroups to speed up CFS is not what cgroup was made for (check documentation: http://www.mjmwired.net/kernel/Documentation/cgroups.txt)...

Con Kolivas wanted to optimize scheduling for slower hardware and made BFS: http://ck.kolivas.org/patches/bfs/bfs-faq.txt

Quote from there:

(underlining by me).

If you read through the 2 text you'll get why i prefer proberly working BFS without cgroups. My phone is not a multiple user server with 200 cpu's that needs some control groups ;)

Using cgroups to give the "foreground" tasks (the app you use) more "power" than the "background tasks" (like syncing or something) is an awful idea imo, because it leads to more overhead. "renice" the priority of task should be enough and a sheduler that is made for interactivity (BFS) is the "direct" and better way.

Yes. v0.5 doesnt support JFS. The issue is this. If the partition doesn't get unmounted (getting a "clean" flag - unmount is something like removing an usb stick "save" if you dont know what that means ;) ) it isn't able to mount that partition without running a filesystem check. v0.5 doesn't have the fsck.jfs binary included and wouldn't run it on boot anyway. You can replace the /system/etc/init.d from 0.5 with the one from 0.6 and copy the additional binaries from /system/xbin/ of v0.6 to the zip BEFORE you flash the rom. Then flash a kernel from the 2nd post. It should work then with v0.5.

This way it should work. I wont edit v0.5 myself and instead rerebase the next version back to 1.32. For the reasons see above.
[Desire Android Development] martino2k6:
Will there be a need to do a full wipe when coming from 0.6?
[Desire Android Development] Fightspit:
New Issues:

Rebooting (or shutting down then starting) the phone with JFS make the apps force closing after you run them (Gmail, Facebook, Titanium backup and etc...)

Edit: Rebooting (or shutting down then starting) the phone into recovery (the one from post#2) makes the sd-ext partition (JFS) unable to be mount.
[Desire Android Development] melethron:
JFS is very reliable considering the journal and is more save than ext3 and one of the safest metadata journaling filesystems ever. Data that is written while the reboot happens is lost in ANY case and even with

full

journaling (= writing all data twice ... its still not there if it is not written at all ;) ). In a stress test the journal replayed fine in over 20 reboots. In one reboot (not a typical one but a stress test reboot) there was a data loss because of an unfinished writing. These is a normal behaviour and also happened on ext3 / ext4 (on ext3 i got a corruption one time - on ext4 there was a zero-length file).

Still it uses different way to create inodes. There is a

really rare

change to corrupt the complete partition but this can happen on most (or even all?) fs.

I talked to snq- if there could be a way to make "clean" reboot but he didnt have an idea yet (reboot is done with a kernel function and shutdown with /system/bin/shutdown - unlike on linux the "shutdown" cant be used to reboot with "shutdown -r"). I still recommend to use only normal shutdown because partition is unmounted nicely. This applies to ALL filesystems with/without LOTE and also applies for non data2sd. Yaffs2 has lower buffering but data can always be missing if no unmount occurs.
[Desire Android Development] Terepin:
Funny, Alex-V HD with your script and database hack is running smoothly.
[Desire Android Development] MATRIKS:
Yes. v0.5 doesnt support JFS. The issue is this. If the partition doesn't get unmounted (getting a "clean" flag - unmount is something like removing an usb stick "save" if you dont know what that means ;) ) it isn't able to mount that partition without running a filesystem check. v0.5 doesn't have the fsck.jfs binary included and wouldn't run it on boot anyway. You can replace the /system/etc/init.d from 0.5 with the one from 0.6 and copy the additional binaries from /system/xbin/ of v0.6 to the zip BEFORE you flash the rom. Then flash a kernel from the 2nd post. It should work then with v0.5.

Still won`t boot :(
[Desire Android Development] Fightspit:
I am not sure Alex use the same version of the script from this ROM.
[Desire Android Development] melethron:
As i said the Partition needs to be "clean" to get mounted. If you do "reboot recovery" it isn't. Do a normal shutdown and start the phone with "power+vol-down". It is unmounted "clean" then and can get mounted.

Same kernel (BFS)? If yes i wonder why.

As i said already v0.6 is the first rom i did from "stock" and i ported it myself (not based on ready custom rom). Im new to cooking and i wanted to make sure that everything works fine. But there where some people that posted something like "no new version yet" ... "any ETA" ..."use this" ... "do that" ..... "1.72 is faster" ..... :p

Then you did something wrong ;)

Its an older version of the script but that shouldn't be the reason for the speed difference.
[Desire Android Development] melethron:
Checked his ROM and compared ext3 and its slower for me. Difference is this:

Kernel is CFS instead of BFS

Scheduler is CFQ instead of Deadline

The reason i made all this config stuff is to make it possible to set it up for every sd-card. If your sd-card cant handle all "i/o" requests from deadline and gets starvatition of requests it causes lags.

So if this ROM has better results you should try CFS kernel (2nd post) and CFQ scheduler (config-file).

I make cfq default in next version to provide greater compatibility but deadline is still recommended if the sd-card can handle the i/o requests.
[Desire Android Development] banhong:
I need some help, Anyone please advise me.

After flash this Rom v0.6, then I want back to A2SD+

But I try several Rom Leedroid, Pays , all is fail........ (previously no problem).

The phone is turn off after HTC white screen.????

But if I re flash this Rom, every things is ok.

Now, how i switch to another rom?
[Desire Android Development] melethron:
YOU ARE MINE NOW ... NO MORE OTHER ROMS .... HAHAHAHAAHA ...

.... just joking XD . Flash the ext3 zip to format your partition with ext3. Make sure you do a full wipe (needed) and then flash the ROM. Maybe you used another filesystem or there issues with dalvik cache.
[Desire Android Development] banhong:
ext3 zip which one? T_T

Thank in advance.
[Desire Android Development] thay:
V5 was fine v6 is faster very good melethron i'm waiting trackball wake patch:)
[Desire Android Development] Terepin:
VR gives me better performance than BFQ.
[Desire Android Development] melethron:
http://files.c0urier.net/melethron/index.php?dir=Avaritia_HD/alignment/

http://files.c0urier.net/melethron/index.php?dir=Avaritia_HD/Mods/

Thats why included to config so every one can set it up like he wants it. But don't only look on Bench nummer. Bench results can be better but "feeling" worse.
[Desire Android Development] Nitin985:
Will it remove anything from the SD card
[Desire Android Development] melethron:
Only formats the 2nd partition (like "wipe sd-ext" in recovery). It doesnt touch the fat partition (/sdcard). Backup is still recommended like for every repartition programm.
[Desire Android Development] Lanbase:
i flashed the trackball zip,

but it is not working, do i have to wipe any cache or data?

grtz
[Desire Android Development] melethron:
... the file works ... thats another issue ... :/

Keys arent accepted while screen is locked ... volume keys also dont work ... :/

Edit: wrong quote
[Desire Android Development] thay:
What file are you mean? is trackpad wake patch ready?
[Desire Android Development] Lanbase:
Ok, and now what :))

Sent from my HTC Desire
[Desire Android Development] skullz:
Thanks.. I will try that with SetCPU and see how it goes
[Desire Android Development] Terepin:
It would be interesting to see exFAT in action; it was created mainly for flash memories.
[Desire Android Development] fossean:
Thanks Melethron, 0.6 is running really smoothly. I love how configurable it is.

Just ran into a problem after flashing the CFS kernel with config changed to CFQ; hangs at the Alpharev (S-OFF) splash screen. Scuppered my plans to benchmark each scheduler with my mSD card!
[Desire Android Development] melethron:
didn't find a quick fix. Im rebasing atm anyway. If the issue happens on 1.32 also i fix it there. I really want to get rid of the cgroup errors:

E/IPCThreadState( 563): Bad cgroup data {�C��\}
E/dalvikvm( 426): Cannot get policy, owner thread id=430
E/dalvikvm( 426): Cannot get policy, waiter thread id=445
E/dalvikvm( 426): Bad cgroup data {�ūJh��}
E/dalvikvm( 426): Bad cgroup data {�ūJh��}
E/dalvikvm( 426): Cannot get policy, owner thread id=430
E/dalvikvm( 426): Cannot get policy, waiter thread id=431
E/IPCThreadState( 1325): Bad cgroup data {}
E/dalvikvm( 426): Bad cgroup data {���J��_}
E/dalvikvm( 426): Bad cgroup data {���J��_}
E/dalvikvm( 426): Cannot get policy, owner thread id=553
E/dalvikvm( 426): Cannot get policy, waiter thread id=445
E/dalvikvm( 426): Bad cgroup data {�ūJh��}
E/dalvikvm( 426): Bad cgroup data {�ūJh��}
E/IPCThreadState( 563): Bad cgroup data {�C���%}
E/dalvikvm( 426): Cannot get policy, owner thread id=445
E/dalvikvm( 426): Cannot get policy, waiter thread id=446
E/dalvikvm( 426): Bad cgroup data {8ƫJh��}
E/dalvikvm( 426): Bad cgroup data {8ƫJh��}

Did it work without cfq? If you didn't enable "usb storage" and delete the config file.
[Desire Android Development] fossean:
Did it work without cfq? If you didn't enable "usb storage" and delete the config file.[/QUOTE]

No, tried it with original config (deadline scheduler) and same hang at boot. Re-downloaded the kernel, too.

EDIT: Just tried flashing CFS kernel again with deadline scheduler, this time it worked. Confused... :)
[Desire Android Development] MATRIKS:
i have a little problem here! Can you help me please?

View attachment 493370
[Desire Android Development] fossean:
Just got the CFS kernel working with cfq — apparently, I needed to flash the kernel, reboot, then change the config from deadline to cfq and reboot again. I didn't realize there was a specific sequence required; now I can continue with my benchmarking :)
[Desire Android Development] Fightspit:
Unfortunately, it is not (yet) supported by linux kernel but it is still under development.

But I am wondering why not to use the YAFFS2 which is used in the internal memory ?
[Desire Android Development] martino2k6:
Running fine here on an EXT3 partition. Speed seems decent, sometimes it lags for a few seconds, but not too bad.
[Desire Android Development] Lanbase:
Any results yet? I just flashed the cfs kernel and got rid of the dalvik errors... should i change the scheduler in config from deadline to cfq now or leave it untouched?

Phone works fine btw.

Sent from my HTC Desire
[Desire Android Development] melethron:
Yaffs2 is for raw nand. Its not a good fs anyway.

Does the rom boot?
[Desire Android Development] martino2k6:
By the way, the trackpad to unlock update doesn't work for the trackpad, but just the four hardware keys.
[Desire Android Development] MATRIKS:
Does the rom boot?[/QUOTE]

Yes working normal:confused:
[Desire Android Development] woti23:
error code 8 = operational error

possible reason: fsck on mounted filesystem

cannot replay journal

exit with signal 11, better known as "segmentation fault"

maybe the fsck.jfs is not a good compile.
[Desire Android Development] melethron:
ownhere compiled the files and everything worked so far...

And it isn't mounted before by the script and ...

no idea where the issue lies ....
[Desire Android Development] mani0008:
Great wrok though by the way excellent ROM!
[Desire Android Development] manup85cupra:
some one can post a perfect avaritia-log.txt? :) Tnx
[Desire Android Development] Alex-V:
+++ Your Partition(s) are already aligned and avaritia didn't modify them

with kind regards...Alex
[Desire Android Development] martino2k6:
Is there a way to stop those dalvik cgroup error messages in DDMS? It makes debugging really difficult...
[Desire Android Development] woti23:
no (except for using CFS instead of BFS),

but you can hide them:

adb shell logcat |grep -v cgroup
[Desire Android Development] banhong:
After i have try

- flash alignment-ext3.zip then flash Leedroid -> fail.....

- flash alignment-ext4.zip then flash Leedroid -> fail......

This rom have modify something in internal storage or How i can revert my phone previous back?

Please guide me, melethron.

Thanks.
[Desire Android Development] melethron:
No changes to internal. What recovery did you use to flash the zips? Can yo post the "alignment-log.txt" from sd-card pls.
[Desire Android Development] martino2k6:
I see, thanks.

Well, you can't hide them in Eclipse so I guess I'll go over to CFS :(
[Desire Android Development] banhong:
I use ClockworkMod 2.5.0.7 and here is alignment-log from sdcard
[Desire Android Development] newstar:
How to check this benchmarks ?
[Desire Android Development] thay:
Delete partitions with gparted and create new layout then flash works fine
[Desire Android Development] Semmy7:
melethron, thank you for your work. This ROM has seemed to me very interesting in theory but in practice...

Yesterday I tried this ROM. The first boot took about 15 minutes.

After boot it was so sloooooow on my device (slcd desire + sandisk microSD 8MB class6). Any single action, such as opening a program or menu takes 3-5 seconds.

It was terrible and unbearable. Maybe it was some strange incompatibility.
[Desire Android Development] styr:
I had the same problem yesterday, but after a while, some reboots and activating LOTE the ROM became stable and very smooth.
[Desire Android Development] paul92:
Force kill browser

Hello, sorry for my English,

Thanks for your new release (I never installed the previous one).

I have a problem, I tested with a new full wipe, with or without LOTE.

When I boot I have always a box telling I should wipe data to avoid instabilities (I did it), so I clic on "I'm feeling lucky".

The default browser and apps using it (e.g. STIB) crash on opening but Dolphin HD works.

Could someone help me ?

Thanks !
[Desire Android Development] martino2k6:
I'm not even using LOTE, but opening apps is more or less instant. Even installing from the market is generally pretty decent. Class 2 card here.
[Desire Android Development] thay:
melethron any news about trackball unlock ?

rom works fine and fast for me positive feedback:)
[Desire Android Development] melethron:
log looks fine. Are you sure you did a full wipe. Can you post the recovery log of the failing flash. Its in /tmp/ after flash.

v0.6 is not good ... :/

Im also not happy the way it is. Im rebasing back atm to 1.32.

you need to wipe SD-ext to wipe data (its data2sd-ext ;) ). I think you should do a full wipe reflash the rom.
[Desire Android Development] melethron:
I rebased the rom already. Trackpad works now and cgroup errors are also gone (and its more smooth now). Maybe i can update to 0.7 this evening already.
[Desire Android Development] thay:
Fine waiting for the update :)
[Desire Android Development] Lanbase:
Ok, you can figure out 1.72 "at ease" then ;)

I will try 0.7 and see, v0.6 works at least stable for me and its not lagging yet.

I know it is not how it was ment to work, but certaintly good enough for daily use.

I have now cfs kernel provided in second post , still on reiserfs (gparted live cd align to MiB method), and 100mb swap, no sqlite hack default avarita config, No SetCPU, class4 Sandiskk 16GB.

Chill out with 0.7..... When is ETA!?! :D

Grtz, keep up the good work..

Ps would different scheduler than default be convenient in relation using cfs kernel now?
[Desire Android Development] melethron:
There wasn't much to do for the rebase (i know now how it works so it doesn't need that much time ;) )

Also scripts wont be reworked (but still a bit tweaked).

I also think i change to "cfq" as default for compatibility. Deadline is still recommended in most cases (espacially for reiserfs and jfs).

ETA: most likely today or at least tomorow (if not then "...when it's done" :p )
[Desire Android Development] MATRIKS:
This rom work just fine even with LOTE-off 2400+ on QUADRANT with JFS+Swap partition

Great work Melethron i`m your fan :D
[Desire Android Development] abumhmmd1:
Avaritia HD v0.6 in my DESiRE

:):)

​
[Desire Android Development] mahmoudxcom:
hi abumhmmd1 can you post the needed file to make this ROM support the Arabic language .

thanks
[Desire Android Development] melethron:
You could try "Any locale" (free) from market.
[Desire Android Development] Alex-V:
maybe this...but untested on hd roms :

All Locale (language and apn´s)

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

with kind regards...Alex
[Desire Android Development] banhong:
No any log file there /tmp, /sdcard/tmp
[Desire Android Development] woti23:
/tmp is gone after reboot

do a:

adb pull /tmp/filename filename

while in recovery
[Desire Android Development] shafez:
Great rom, Thank you very much.

Is it possible to increase the font size ?

Best regards
[Desire Android Development] thay:
Hi melethron any news about new rev of rom?:)
[Desire Android Development] melethron:
Op updated with v0.7:

v0.7

- reverted rebase - Base is now RUU_Ace_HTC_WWE_1.32.405.6

- Cgroup errors on bfs fixed (through rebase)

Note: HTC using cgroup to speed up interactivity on CFS is not the way forward when

a sheduler MADE for interactivity (BFS) - CFS + cgroups is intended for large servers

and not for a phone.

- Dpad to wake / volume keys works now and included (see mods to "unflash")

- Power Notification widget included as default (see mods to unflash)

- Add custom Wallpaper to the default skin

- Fixed bootanimation (2 frames were too bright + made it a bit slower)

- Bluelight "fun" on boot

- Updated apks

- Some tweaks (mostly adopted from ownhere - thx ownhere)

- Some fixes.
[Desire Android Development] melethron:
you asked 5 seconds to fast ... see posting above ;)
[Desire Android Development] thay:
You are soooo fast !!!:)
[Desire Android Development] melethron:
2nd post updated: http://xdaforums.com/showpost.php?p=9896641&postcount=2
[Desire Android Development] alexdoux25:
Hi melethron, thanks a lot for your amazing job.

Sorry for my question, but i havn't found information if possible to use yuor alignment zip having several ext partitions on SD? Are they all will be correctly formated and aligned?
[Desire Android Development] kda2:
Does anyone have bootloop after flashing (v0.7)?
[Desire Android Development] melethron:
No wont work.

The script checks for partition 2 und 3 and aligns the start/end sector. (partition 1, 4,5,.... wont be touched)

After that it will format part 2 with the fs (depending on fs) and makes part 3 a swap device.

You can format partition 3 after that by hand ....
[Desire Android Development] melethron:
Did you do a full wipe?
[Desire Android Development] kda2:
Yes. I'll try one more time and format sd card.
[Desire Android Development] melethron:
Its important that it's a full wipe. The sd-ext partition needs to be wiped also.
[Desire Android Development] MATRIKS:
Melethron

Rom work perfect ;)

It`s too fast :D

Just one thing APN list is empty

BTW did you update RIL

Thanks man
[Desire Android Development] kda2:
I've formated /data, /system, /cache and /sd-ext from ClockworkMOD this time. Now it's installing. I'll post whether it has worked.

Edit: The same as previous. Just vibrates on HTC logo a couple if times.

I'll try flash RCSMixHD (my provious ROM) and check if it works.
[Desire Android Development] melethron:
Speed is getting better and better. But still not fast enough ..... (i have some more ideas already like using cache partition for often used dex files like its done on leedroid .... expect more ;) )

About apn: The one in framework didnt include my apn and i had to modify that all time so i added a "customer" list (system/etc/customer/apns.xml). I didn't know that that list overwrites the one in the framwork-res.apk. I see that i'll add all the apns from there to the customer list.

About RIL. I don't even know HOW to update ril ;) ill look how its done and do that in the next version.
[Desire Android Development] ownhere:
So odex is best solution.

deodex make all system app need a dex file on dalvik-cache, this is location to SD on A2SD/D2SD ROM, so IO and battery life is bad.

the Cache partition is more large more good, you can place system@app@*.dex to /cache, but you will suprise the battery drain. :)

So i alway use odex ROM.hehe
[Desire Android Development] melethron:
Well but i dont get the difference if it the odex file has to be read or the dex file. The decompression of the dex file on first boot is more io. But when they are cached there should be no difference between reading the odex file or the dex file ...

Also i dont see the point why reading dex from nand should be different from reading it from external.
[Desire Android Development] ownhere:
read file from SD need more power. you should know that stock ROM get the best battery life, because stock ROM had NO a2sd/d2sd. in Stock ROM, SD need be drive only when read game data or movie or so on.

so leave odex file on nand will be good on battery.
[Desire Android Development] ownhere:
if you put system@framework@* or system@app@* to /cache, this is another case. Small /cache free space will lead battery drain, I even experience it.

large /cache free space is good for phone, so DHD use 300M for /cache.

EDIT:

Instead of trying to put some dex file to /cache partition, why not stay odex directly to the /system or /data?

If the core file's dex put to /cache, then the equivalent of each core file include two classes in NAND, one in the apk, one is in the /cache.