yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] awolbriggy:
almost there

I have tried to install this ROM several times now - and have always reached the same end point...

Have things partitioned and alligned etc,

I flash rom - all good..

reboot...

get first screen

get second animated skater droid

then get what looks like a finished screen lock... coloured background, everything looking good.

Pull down screen lock... and...

white screen with HTC on it...

I have waited an extremely long time, but never progressed passed this...

The top (power) key works and gives the expected power off options for this ROM... and can even turn it off... but reboot just gets back to the same screen... nothing gets me out of that.

It is possible I am just doing something dumb - and I know there cannot be a problem with ROM since others are doing fine... and sorry to annoy people with stupid query (I have read this thread and tried everything that seemed relevant) - but if anyone has any ideas on what i am doing wrong, let me know, I would love to try this one....

thanks
[Desire Android Development] louis47:
Avaritia 0.7 ok

At last 0.7 is working. But, I had in the main time Villain 0.9 And there I had connection with my PC. After installing an other Radio 32.49.00.32U_5.11.05.27.zip.

With 0.7 also no connection with my PC en no bluetooth, the same as 0.6. Even powerled is after 6 min. loading.

Do you have a solution?

Former post:

Maybe offtopic but I even don't have bluetooth, desire will not connecting to PC.

And when I put desire on powercable he started loading after 3 or 4 minuts.

In format boot menu no problems with connecting PC or powerloading.

I think it is on topic. see Avaritia.log
[Desire Android Development] biliskner:
You need to post a logcat.

But on first impressions it seems like it could be your SD Card that's not happy with the set-up... probably try another SDCard see if that works.

Also, which FS did you try (ext, jfs?) And what size are your partitions? Got a swap partition? etc.
[Desire Android Development] awolbriggy:
Good point... I will try again probably tonight or tomorrow and get a logcat.. I was just hoping it was an obvious thing... For what it is worth I have tried with both ext3 and ext4's of 1->1.5G; with and without swaps, and it seems odd (to me), that I always get to the same point...lol (I would be happier if one config gave me a more extreme fail...lol) -- thanks for care.
[Desire Android Development] louis47:
I had the same problems. And then I did partition with Recovery-RA-2.0.0.

Suprise 0.7 works.

16 GB sdcard

ext3 2048 MB

No swap

rest fat32

But for some reason no Bluetooth, no connection with PC. I don't known why. Good luck.
[Desire Android Development] lvnatic:
Well, no bluetooth and "when I put desire on powercable he started loading after 3 or 4 minutes" sounds like a usb-brick, but your SD card shouldn't also be working. Check the symptomps from this thread, you also have the fix there.
[Desire Android Development] Chaqmol:
what is the highest score of this ROM by quadrant?

can someone post it with pictures please?
[Desire Android Development] martino2k6:
2283

But as it has been said already many times, "real-feel" performance is different than numbers from a synthetic benchmark.
[Desire Android Development] rum0s:
so this is my first try :-)
[Desire Android Development] th3:
No boot

I wanted to give this a try since you've put much effort into these things ;)

Full wipes, stock SD card, 600MB Ext 3, 0.7a installed (I can see the apps/dirs made). One I didn't use your alignment zip and once I did (tried twice). Straight after, on reboot, it just gets stuck at the spinning circle with a blue LED on. I've attached a logcat - haven't had time to look into it properly but there seem to be many errors including SD-Ext not mounting.

Logcat is stuck at:

[B] 452 keystore E chdir: /data/misc/keystore: No such file or directory[/B]

Keeps repeating on and on.

Any insight would be appreciated!
[Desire Android Development] lukyjay:
This is incredibly slow at first, but after an hour of syncing, it became faster :) I really like this, good work!
[Desire Android Development] biliskner:
Errors are definitely something with the SD Card not formatted properly.

How did you format your card, gparted or AmonRa? I used AmonRa 1 from last year (very old), and it formatted my card - Fat, Swap, Ext. Then rebooted recovery in clockwork and used Mel's zip align then straight away (no reboot), flashed 0.7. Booted no probs.
[Desire Android Development] biliskner:
I think FAT32 needs to be at the beginning of your sd card, but I don't know since I used AmonRA and not gparted (it will cause problems if you have your FAT32 in the middle or end of the sd card (or wherever it's not supposed to be)).
[Desire Android Development] louis47:
The sdcard works, now! I do the trick with fastboot oem xxx and mtd0.img that brings the phone to life. But non bluetooth and connection.

I gone back to Root and then my telephone got to repair back to HTC.
[Desire Android Development] th3:
I've had the SD card formatted this way since about 5 months and have 4 different SD Cards: FAT32 -> EXT 3. Formatted through GParted - they all run fine.

There seem to be two errors here. One seems to be caused by the alignment script I ran because after running it, SD-Ext can't be mounted. Before it, it could. I've fixed that so now Ext can be mounted and accessed using other ROMs so will try this flash again to see what goes. Thanks
[Desire Android Development] MATRIKS:
This rom work just fine but need stream fix also downloading from market is too slow

and no apn list
[Desire Android Development] biliskner:
Could try one of the other FSs like BTRFS or JFS, I tried those 2 with Reiser as well and they work fine. I used to get an the SD-Ext cannot be mounted error also, but that was because I didn't run the ZipAlign before ROM install (I'm using the old AmonRA / CWM recovery).
[Desire Android Development] lvnatic:
Whats the advatange of data2sd over data2ext or app2sd? Why did you choose it over those 2? Is it faster/more stable?

Does amon ra support btrfs/reiserfs for nandroid restore/backup? And which one of those is better for a class 6 card? ext3/btrfs/reiser?
[Desire Android Development] lvnatic:
Bump:D

I wanna install the rom tonight and need an answer for the partition type asap.
[Desire Android Development] lvnatic:
tried fat32+1gb ext3 with gparted, wiped all and flashed. It flashed ok, the phone booted but it doesn't start the setup for configurating accounts, time and all that. It stays on htc white screen. Power off or restart works, closing the screen works, it just doesn't go past the white screen. Wiped and went on another ROM, I will wait for a stable version.
[Desire Android Development] biliskner:
Mine took 15 mins on the white screen then it loaded. It is very slow the first time, since it has to create all the databases on your SDCard. How long did you wait?
[Desire Android Development] th3:
Which old version of CWM are you running?

I have a feeling trying to mount SD-Ext in CWM 2.5.x.x after running the alignment scripts is what corrupts it.

Sadly, I won't try BTRFS yet (will give the others a go). Right when the first test cases appeared on here with data2whatever, I was running tests with that FS on my SD card (no ROM, just raw solid state memory tests) and I ended up with an SD card that after formatting (FAT32+BTRFS), wouldn't mount anywhere nor reformat and was giving endless block corruption errors (through phone and PC). It said initial formatting was done fine but I couldn't flash anything because nothing would mount/recognize the card. All my SD card contents had been deleted from both partitions. It all came as a big surprise at a time when my other SD cards weren't free to use. One of the firms I test development NAND devices for produces SSDs and DRAM. They provided me with a test tool they use to check raw memory cell state, reliability and access, booting from a CD. Using that I knew the card itself was fine. Using another of their tool, I was able to raw erase all cell contents and state including the error and bad block stores. It took me 2 weeks to fix from that and get a working phone again. Hence why I'm very cautious with that particular filesystem.

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

- Sent via HTC Desire -
[Desire Android Development] biliskner:
Sounds like the formatting tool really stuffed the sdcard up. I'm on the very first version of CWM (via the update.zip way); I rooted my phone the first week it was released an have found no need to upgrade the recovery tools. But you're right that if i try to wipe my sd-ext it is impossible since that old version of cwm does not recognize the FS, so I just format the ext FS with Mele's zip aligns.

When flashing 0.5 /0.6/ 0.7 I get no issues and it installs fine... not sure why others have issues with it (if it's not the formatting of the sd-ext that fails, then it would be the recovery version that one is using, to mount the sd-ext... presumably.)
[Desire Android Development] lvnatic:
15 minutes stood on the why so serious screen+splash, but the phone was funtioning when I said I was waiting for the white screen to go away. The buttons were glowing, I could turn off/on the screen via power button, if I kept holding the power button I had acces to the power off menu, restart, etc. Even when I plugged it to the PC, the USB menu popped out asking for charge only, disk drive, etc. Its just that it was blocked on the white screen, couldn't acces the menu or configure the phone., nothing. I waited for like 5 minutes and turned it off.
[Desire Android Development] lvnatic:
Maybe I could give it another try but what is better for speed? Ext3 or btrfs? I got class 6 card.
[Desire Android Development] Lanbase:
I presume you guys know that Meletron posted modded cwm recoverys with support for the exotic filesystems hey? its a few pages back just before he released 0.6 .... flash one of those, you will be able to acces/wipe the ext partitions then. also nandroid works with them. sorry i cant search now. i am on my phone

Sent from my HTC Desire
[Desire Android Development] pjm77:
Hi guys! I'd like to ask what is your everyday experience with his ROM? Do high benchmark results translate into significant difference in real-life speed (let's say comparing to other DHD/Z ROMS). Or is it rather for people who want to experiment with D2EXT and file systems? I'll be grateful for any opinions.
[Desire Android Development] lvnatic:
its a dead rom, move to another like insercoin
[Desire Android Development] martino2k6:
Works well for me. Apart from when installing from the Market I don't get any lags.
[Desire Android Development] biliskner:
LOL!

Yeah, mission accomplished; this ROM will stay as so but will die if it's not updated in another few weeks.

RCMix ROM updates like crazy. If you like flashing your ROM weekly, MIUI is hardcore.
[Desire Android Development] lvnatic:
Its not that, if someone asks something they are lucky if their msg is noticed within a week. If you don't have time to provide support for your rom just stay out of tuese things.
[Desire Android Development] lagaba:
LOL! Are you serious!?

Firstly the person you quote is not the maker of this ROM..

Secondly this is a development community, melethron has no obligation to maintain software on your behalf.. he's adding to the community by putting something up here for us to test and try... don't get all shirty if your need to tinker is not satisfied by weekly updates, either stick to stock or to something like cm... or even better, learn how to make updates yourself..

I sincerely hope that people don't take up your advice to "...stay out of these things" if they're not prepared to update regularly...

As far as I'm concerned we should be grateful to anyone who uploads anything on here even if it's crap and doesn't work well. At least they are trying to participate by adding to the community...

... once again, this is a developer community, not an app store or a ROM store...

I would like to submit some of my own workings too, for example the ROM I use at the moment is mix of the Z rom with the layout and scripts from this Avaritia rom...

I am put off doing this by the thought of being pestered by people to tweak the ROM for them and continually provide updates, I am not a software company...

This is why I have such admiration for melethron, robocik, coutts, alex,neo, richard trip and all the others... not just for their technical skills but also for their patience and dedication...

I, for one, salute you melethron.
[Desire Android Development] Lanbase:
Very well said !

Btw, you couldn,t by any chance do a sneaky upload somewhere of your homecooking recipe?? ;)
[Desire Android Development] biliskner:
LOL!

No I'm not the maker of this ROM, but I'm still using it and love it.

Plus the question lvnatic ask has been answered about 200x in this thread, if he/she even bothered to read ANY of it (looks like he/she didn't even read the first post)
[Desire Android Development] lagaba:
Well I'm not gonna be back home till late tonight but I'll try and stick it somewhere tomorrow...

;-)
[Desire Android Development] Lanbase:
Cheers for that !
[Desire Android Development] MATRIKS:
@Melethron

Can you make Avaritia 1.84 Base ROM please

Thanks
[Desire Android Development] qweasdfzxc:
I'm experiencing a bootloop, stuck at the htc screen (the first one, not the quietly brilliant screen). As soon as I can I'll provide a log, for now here what I did:

full wipe/factory reset, wipe cache, wipe dalvik.cache. Flashed the .zip with clockworkmod recovery 2.5.0.7, system reboot

I'm using a htc desire rooted with unrevoked, S-ON. My sdcard is a class 6 8gb card partitioned with a primary fat32 and an ext4 1.4 gb.
[Desire Android Development] manup85cupra:
qweasdfzxc where do you bring this photo? it's impossible that you have the same like me on my phone!!!

non puoi avere la stessa foto che ho sul telefonino... e sei pure un compatriota... non è che me la fregata su facebook?
[Desire Android Development] animehq:
Thi rom is dead for ever?
[Desire Android Development] buzzboy:
Shame, I was loving it.....I hope it continues.
[Desire Android Development] melethron:
For some strange reason this issues occurs when /data/property is moved to sd. The only way to solve it was to store it on internal.

Atm i do some testing of filesystems so i didn't have time to update the script. But i will fix the script soon .

You can also take a look at the script of the rom. There is some ROM specific stuff in but if you can script a bit you'll see what the difference is. The changed parts are this:

# move apps etc from internal memory to sdcard
for i in anr app app-private data dalvik-cache dontpanic drm backup tombstones local;
do
if [ ! -d /data/$i ];
then
mkdir /data/$i;
fi;

if [ "$i" != "local" ] && [ "$i" != "dalvik-cache" ]
then
busybox chown 1000:1000 /data/$i;
busybox chmod 771 /data/$i;
fi;
if [ "$i" = "local" ];
then
busybox chown 2000:2000 /data/$i;
busybox chmod 771 /data/$i;
fi;
if [ "$i" = "dalvik-cache" ];
then
busybox chown 0:0 /data/$i;
busybox chmod 771 /data/$i;
fi;

if [ -d /system/data_internal/$i ]
then
echo " +++ Moving "$i" from internal to SD-Card";
busybox cp -a /system/data_internal/$i/* /data/$i/;
busybox rm -rf /system/data_internal/$i;
fi;
done;

# /data/system to internal if on sd
if [ ! -d /system/data_internal/system ];
then
busybox mkdir /system/data_internal/system;
fi;

busybox chown 1000.1000 /system/data_internal/system;
busybox chmod 771 /system/data_internal/system;

if [ -d /data/system ] && [ ! -h /data/system ];
then
echo " +++ /data/property found on sd -> moving to internal";
busybox cp -a /data/system/* /system/data_internal/system;
busybox rm -rf /data/system/*;
fi;

# /data/misc to internal if on sd
if [ ! -d /system/data_internal/misc ];
then
busybox mkdir /system/data_internal/misc;
fi;
busybox chown 1000.9998 /system/data_internal/misc;
busybox chmod 01771 /system/data_internal/misc;

if [ -d /data/misc ] && [ ! -h /data/misc ];
then
echo " +++ /data/misc found on sd -> Moving to internal";
busybox cp -a /data/misc/* /system/data_internal/misc;
busybox rm -rf /data/misc/*;
fi;

# data/property to internal if on sd
if [ ! -d /system/data_internal/property ];
then
busybox mkdir /system/data_internal/property;
fi;
busybox chown 0.0 /system/data_internal/property;
busybox chmod 700 /system/data_internal/property;

if [ -d /data/property ] && [ ! -h /data/property ];
then
echo " +++ /data/property found on sd -> Moving to internal";
busybox cp -a /data/property/* /system/data_internal/property/;
busybox rm -rf /data/property/*;
fi;

# Symlinks
for i in property misc system;
do
if [ ! -h /data/$i ];
then
echo " +++ Creating symlink for $i"
busybox rm -rf /data/$i;
busybox ln -s /system/data_internal/$i /data/$i;
fi;
done;
[Desire Android Development] PaY87:
Nice one, I will try that again :D

Lets see how it goes, but even when its just a little slower its okay, when someone needs space this is okay..

Only hard lags and slowdowns would be bad :)
[Desire Android Development] Jagdish84:
Can we use this data2ext4 on any other rom? or is it optimized for pays rom?!
[Desire Android Development] mahesh_9j:
Screen Shots Please

Hi,

Can I have some screen shots of the ROM Please.

Thanks In Advance.

Mahesh
[Desire Android Development] melethron:
I only do have slight slowdowns on market downloads or other writes . Atm im benching everything and i think i add a "live-on-the-edge" patch which gives the users than the choice between safe and risky mount options.

All the data corruption i found on "risky" mount option was because of snq "power menu". On a "normal" shutdown "/data" gets unmounted safely but not if you do any reboot with snq menu (and i did "reboot recovery" all the time to test). So i will remove the menu since it is like a battery pull for data2sd. The only risk then would be a powerloss and this risk is not as high as a normal reboot.

There is ROM specific stuff in. If you can script a bit you can remove that stuff. If not wait a bit ill update my data2ext4 and data2btrfs thread soon with the changes i did in the ROM.

I'll add one in a minute. All i changed atm was the default skin which you can choose through personalize and the icons + battery which can be changed with "UOT kitchen".

EDIT: just to let you know. Weather and stuff does work. Atm i'm doing benchmarks and for that i haven't setup wifi and disable mobile connection. Just in case you wonder why there is not weather icon at the clock. Ill more screenshots for the next version ill release.
[Desire Android Development] animehq:
the next version was based on pays hd 1.1?
[Desire Android Development] Jagdish84:
Cheers for the quick response mate.
[Desire Android Development] melethron:
Hmm, changelog is this:

-Based on 1.34.405.4 WWE Desire Z
-Circle battery with %
-Apk's updated
-E-Reader removed
-coutts99 kernel updated to 2.6.32.27

1. I use my own customized battery on the ROM so circle battery change will not be included. Also everyone is free to customize with UOT Kitchen.

2. Apks will be updated also.

3. I will not remove the e-reader because i like it and space isn't a problem.

4. Cant use coutts99 kernel because i want ReiserFS support and need neophytes kernel for that. Ill talk to coutts99 about a new kernel.

So all thats left is that he uses Desire Z. Im not sure if i like a rotating rosi but i take look at it (can it be disabled?!). Despite this the next version will be almost the same as pay's 1.1.
[Desire Android Development] melethron:
I tested Pays 1.1 and it has issues. So i will not upgrade it in the next version. I had the same issues as reported in this post here.
[Desire Android Development] melethron:
Op updated by the way.
[Desire Android Development] animehq:
any advantage to switch on reiserFS?
[Desire Android Development] melethron:
Sqlite performance is important for data2sd. The difference between app2sd and data2sd is that /data/data is on sd and this folder contains the sqlite database. This is also what causes the lags. So the focus on a good data2sd solution is to improve sqlite inserts. Well and my own benchmarks confirm the good results of ReiserFS. In benches it is like 10-20% fast than (journaled) ext4. Im using it for 2 days now and it is also a noticeable improvement in daily use.

Ill update my other thread soon with a in-depth analysis of data2sd, the cause of lags and the sqlite benchmarks i made. But may take time ... christmas first ;)
[Desire Android Development] sagaff:
I've just installed v0.3 about an hour ago. Is it normal for it to lag like crazy within the first couple hours. Downloading from market is almost impossible and freezes occurs almost every time?

I did a full wipe. ext4 with 2gb - class4 sd.
[Desire Android Development] anko184:
Unfortuantelly I can't run version 03. It gives me a bootloop showing default android animation.

Any ideas?

first partition is fat32 and second is ext4.
[Desire Android Development] melethron:
Data2sd (any script not just mine) sucks heavy on market downloads and i didnt find a way to fix it. This is espacially hard if the HD Roms autodownload all your apps after the first boot (i skip the setup and restore everything with titanium backup first). Apart from that the dalvik VM builds its cache after a fresh install and that also does some writes to sd. But this will get better fast.

But after some 2-3 hours (and no market download) it should be smooth. You can still try the "life-on-edge-patch" which uses the same type of solution that sibere and ownhere use. But read the info about it in this post first.

I myself can life with lags on downloads traded for more space as long as the rest is smooth. But everyone has to decide on its own.
[Desire Android Development] melethron:
Hmm this seems like it cant acces the internal partition. If you did a full wipe and it still doesn't work i might know where the issue lies. Did you do S-OFF?
[Desire Android Development] anko184:
Yeap i did a full wipe before i try it and no i haven't S-OFF my phone.

Let me know if you need a logcat...
[Desire Android Development] sagaff:
Below is what I see in the logcat :

I//system/xbin/busybox( 71): tune2fs 1.41.6 (30-May-2009)

I//system/xbin/busybox( 71): ext2fs_check_if_mount: Can't check if filesystem

is mounted due to missing mtab file while determining whether /dev/block/mmcblk0

p2 is mounted.

I//system/xbin/busybox( 71): +++ Moving app from internal to SD-Card

I//system/xbin/busybox( 71): cp: can't stat '/system/data_internal/app/*': No

such file or directory

I//system/xbin/busybox( 71): +++ Moving app-private from internal to SD-Card

I//system/xbin/busybox( 71): cp: can't stat '/system/data_internal/app-private

/*': No such file or directory

I//system/xbin/busybox( 71): +++ Moving data from internal to SD-Card

I//system/xbin/busybox( 71): cp: can't stat '/system/data_internal/data/*': No

such file or directory

I//system/xbin/busybox( 71): +++ Moving dalvik-cache from internal to SD-Card

I//system/xbin/busybox( 71): cp: can't stat '/system/data_internal/dalvik-cach

e/*': No such file or directory

I//system/xbin/busybox( 71): +++ Moving dontpanic from internal to SD-Card

I//system/xbin/busybox( 71): cp: can't stat '/system/data_internal/dontpanic/*

': No such file or directory

I//system/xbin/busybox( 71): +++ Moving drm from internal to SD-Card

I//system/xbin/busybox( 71): +++ Moving local from internal to SD-Card

I//system/xbin/busybox( 71): +++ Avaritia HD init script completed

I did a full wipe using AmonRA2.0.1

Device is S-off
[Desire Android Development] melethron:
If you are not S-OFF that is the issue ... but no need to do S-OFF for this ROM ... this is only some stupidity of me and I already fixed it .... but i wanna go to bed now and want to test it first tomorrow if it works ... ill upload the fixed version version tomorrow)