yashsingh1/xdaforums huggingface dataset:
[Legend Android Development] intolerance:
Flashed yesterday RC1 #30 and update today (without wipe) on #31. Default 820-830 on Quadrant. Both stable for me and

very

fast. Damn fast. Before that was dark azure (420-430 on Quadrant). The performance difference is palpable.

Now flashed the kernal @844 and got a quadrant score of 1207. Normal flight.
[Legend Android Development] Corra:
I haven't noticed any performance improvement from azure 1.0.1
[Legend Android Development] ryaneu:
correct me if i am wrong but #30 and #31 are RC0 and NOT RC1
[Legend Android Development] Calex93:
Hi, new poster here. I'm already well versed with android though, so I'll get straight to the facts =)

At the moment I'm using nightly build 30 with 787 oc kernel. I still get a respectable 1037 score in quadrant.

Just an enquiry, anyone found the differences between build 30/31 and rc1 yet? Cause it seems that the performance is more or less the same.
[Legend Android Development] CfYz:
RC1 here. Gallery is almost usable now, wow :) .acc still won't playing :(
[Legend Android Development] gyroing:
i couldn't load new build with new boot.img inside .so i should install rom b31-30 and after i forced to use nandroid(advance restore) to restore b26 boot.img that has smaller size and diffrent anyone could help me? what is my problem

in addition i format my boot doesn't help me. and what is diffrent between new boot.img and old one? does it change perfomance? during instalation of b26 i have not any problem.
[Legend Android Development] ali ba:
One word: nonsense.
[Legend Android Development] HpX:
i tried the so-called RC1. everything seemd to be working fine, except all attempt to download from market failed. Tried to flash back to Azure and same thing there. Went back in recovery menu, and i noticed my HBOOT was all f***** up. So i search'd for a solution on google, with not much luck. in the end i just tried to unroot, and do the rooting all over.. HBOOT all good, back on azure ( and staying there ) market is up and running again :)

sorry for the bad English..
[Legend Android Development] StabbingHobo:
So does that mean the 'RC1' that was linked in a previous post is of questionable origin?
[Legend Android Development] Calex93:
Well the link was not from the same site in the first place.. right?
[Legend Android Development] StabbingHobo:
Well captain obvious, I'm fully aware of that. But since nobody seems to be waving their pitchforks high and screaming 'malware' or other such warnings, the question still remains.

If the release is 'nonsense' -- which I'm not trying to refute -- then should others who casually read these threads be warned of any potential threats. So far, I and a couple others have admittedly downloaded this so called release and have yet to report any issues. Thus, do we have cause for concern? If there is cause for concern, should the Mods/Admins be made aware and the link removed?
[Legend Android Development] pfak:
Maybe you guys should use the official nightly builds instead of downloading off of some sketchy Russian site. The buildbot works perfectly fine, don't know why you'd download elsewhere.
[Legend Android Development] Calex93:
Maybe no one waved pitchforks is because there isn't any malware in the first place. Or at the very least not detected by anyone or anything just yet. But seeing that quite a number of people have downloaded it, I don't think there is any sort of malware.

One could not tell the proper diff simply because there is so little difference between the latest nightly build and the aforementioned rc1. Doubts were casted due to the different link of the build.

I scanned the file using multiple AntiVirus programs btw, nothing reported. I guess there's no harm done? Heck, maybe it was a nightly build with some fixes by someone else?
[Legend Android Development] maxonite:
I can't speak for everyone but I was still on azure 1.0.1 and wanted to flash to something new and thought I may as well try this. I must say so far it is good enough to stay on until a 'real' rc1 is released that has the ali ba blessing.

Its fast, stable, and everything I use works.
[Legend Android Development] norashers:
Android is based on the linux kernel with it's own userspace on top. If the russian rom were to contain malicious code (but I don't think so), and if you scanned it from a windows based OS then it is highly unlikely that you would be able to detect any malware. Windows based anti-virus programs will try to search for suspicious files/file-headers and behaviour that targets windows machines. They cannot do anything about linux or android vulnerabilities.

The greatest danger would be if someone wrote a rom that deliberately fried a phone, or ran hidden processes such as key loggers. GNU/Linux has some great security through things such as the user privileges and file permissions, but flashing a rom bypasses all that as you are trusting the source. But that's one of the strengths of open source; the source code is there for all to see, including the source code for this rom, and there is a web of trust stretching out from Linus's git tree down to AOSP, cyanogenmod, and Azure/Dark Azure, and taking in a huge amount of coders along the way.
[Legend Android Development] Kwen:
I think the RC1 might refer to his Russian translation

CM-6.1.0-RC1-Legend-20101023-1158-signed.zip is about the same as build 30, dated 2010-10-23 00:36:20
[Legend Android Development] beetlecat:
the 32#is released... what about that???
[Legend Android Development] pfak:
There is only going to be fixes in these builds, afaik since they are in a feature freeze and attempting to do a release of 6.1.0
[Legend Android Development] ryaneu:
anyone managed to get htc_ime to work in the nightly builds? I tried both hi and lo res version 27 but lo res gave me force close and for hi res keyboard won't even appear.
[Legend Android Development] TZC-T1-FX:
You need the 1.5 version of HTC ime mod
[Legend Android Development] ryaneu:
I tried both nightly build #32 and the russian build RC1 .

don't know if its just me but it seems like the russian build RC1 is faster and more responsive than nightly build.

in nightly build, i experience abit of jerkiness when switching between screens but in russian RC1 its smoother and there is no jerkiness.
[Legend Android Development] ryaneu:
do you mean the Low resolution version for Android 1.5 (no voice input)?
[Legend Android Development] JonasDroid:
Yep that's the one.

You can still use your backed up settings and dictionary if you want.

EDIT: Don't forget to install the Clicker.apk first since this is a senseless rom.
[Legend Android Development] andrekua:
Wow, thanks for the tip. I did not realised that the pre 1.5 works.

RC1 seem to work much better. I see that RC1 has better performance due to the difference setting used for Cyanogenmod. When I was using Azure 1.01, surface dithering is on, compcache is off and vm heap size at 16MB. It was quite laggy at times. RC1 had compcache at 18%, surface dithering disabled, vm heap size is at 32MB. Noticed the higher RAM usage but far more responsive than Azure 1.01 overall.

I do have a question with overclocking. Is it okay if I just took any overclocking kernel with the same version number?
[Legend Android Development] Patrick615:
I can't even keep up with the constant update of CM6.
[Legend Android Development] Knight77:
I tried to find a place in which is possible to read the changelog of the NB but nothing...so between the N.26, 31 and 32...what's the difference?
[Legend Android Development] dalerka:
Same q, where we can read changelog? Cm had only 6.0.1 very, but not the nightly

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

Sent via the XDA Tapatalk App
[Legend Android Development] liltbrockie:
I really appreciate the nightly builds but can anyone point me in the direction of the change log for each build? Does one even exist?
[Legend Android Development] ropaisoft:
noticed my mp3 files on SD are not detected. hm... same on b31 & b32
[Legend Android Development] gyroing:
through one month ago i follow russian rom more faster and stable also no problem in wlan that i have problem in nightly i have 1044 quadrant score with russian rom. why you affraid when someone do parallel development. pls see pda.ru for russian developer info.
[Legend Android Development] anran21:
build31 can, used it.
[Legend Android Development] kugel.:
Checkout the sources and run 'git log' or dig through the web interface of github.

If anything important comes up, the CHANGELOG file will be changed, but that won't happen for relatively minor bug fixes.
[Legend Android Development] plicto:
I can't seem to flash any of the nightlies. Even if I wipe everything before flashing I still get stuck on the white HTC bootscreen. It just sits there - I don't get to the Cyanogen splash screen.

I can flash the Azure rom without any issues.

Any suggestions on what might be problem?
[Legend Android Development] xcrew:
Every time i have flashed a nightly build the time spent on the htc bootscreen is greatly extended. How long have you waited before giving up and pulling the battery? It sometimes take up to two mins for me anyway.
[Legend Android Development] plicto:
I've waited up to 15 minutes. I've also tried removing the battery then reinserting it and rebooting - still no go.
[Legend Android Development] xcrew:
Hmm clearly sometimg wrong then, though im afraid im not the one to tell you what.
[Legend Android Development] gyroing:
i have same problem ask but no answer yet. this is a strange problem but i dont know why?

my temp solution:

1-get nandroid backup from b26 or Azure that do boot correctly

2-install zip new rom b30-31 or rc1 all of them dont go to cyanogen screen for me

3- go to nadroid(advance restore) chose only boot restore from backaup of b26 or Azure

4- now it works

the size of boot.img in new builds is bigger that old one.

i check the md5 is correct but when do nandroid restore for new boot.img it says error while installing!!!!!!!!!!!!!!!!!!!

so it is a temp solution and i dont know it has effect in perfomance or not?
[Legend Android Development] marclh1992:
I take it that there are no google apps in / for the nightly builds?
[Legend Android Development] jogum:
I have this problem to, same as you gyroing, 26 build work fine all after this it stuck in white htc screen, i have tried formating SD card but all same i have start the root from step1, now i thinking of unroot, but i want to see if someone have solution to this, there must be many other with the same problem i think.
[Legend Android Development] palakgila:
In b31.. the live wallpaper work..
[Legend Android Development] gyroing:
it seems new build has problem in boot.img . because superfroyo for legends boot also works. if you success to install new build after unroot-root pls tell us. i approved there are many guys same us have same problem.

also if you don't like unroot-root my way "using old boot from advance restore in nandroid"also works. but finally i get that the siize of boot.img doesn't affected. the problem should be inside of coding.
[Legend Android Development] liltbrockie:
Anyone tried build 33 yet?
[Legend Android Development] shark812:
same problem here. Tried to flash 29/30 without success, now i'm back to Azure. If anyone find a easy method to unroot, please send the link to me.
[Legend Android Development] tharonald1981:
Same problem here. Nandroid restore worked to update 29. But al settings were corrupted damn. And now my home and search Button wont work. Keytest passed. I tought i was save with nandroid!
[Legend Android Development] maxonite:
I feel sorry for those having trouble with the latest nightly builds, I do think it is funny though that the so called dodgy russian build seems to be working better than the latest nightlys.
[Legend Android Development] maxmax0:
Russian build ftw!
[Legend Android Development] liltbrockie:
I haven't had any problems updating from builds 28-32
[Legend Android Development] CfYz:
Have none problems with b32. Nandroid, than clear data/cache, install b32, titan back all my apps. All I need is to change phone settings by manual - 5 mins and reconfigure my widgets (common issue). That's it. Nandroid was just in case...

Not so stable, as needed, but its nigthly :)
[Legend Android Development] shark812:
I can't flash this rom: http://android.krikun.ru/pub/legend/CM-6.1.0-RC1-Legend-20101023-1158-signed.zip.

I'm the only one?
[Legend Android Development] ikdegek:
No big problems at all with B#33.

Only scolling seems not so smooth anymore. Anyone facing this?? I am running kernel 825.

Yesterday went back from B#31 to Clockwork backup I did 4 days ago. No problem either.
[Legend Android Development] gyroing:
wellcome to our problem not only this but also you couldn't install after b26 of nightly rom.

no develeper answer yet?
[Legend Android Development] BlaY0:
And they won't because you haven't provided them any info except that it doesn't flash.
[Legend Android Development] kugel.:
does adb logcat print anything at this point.

I'm running b31 just fine.
[Legend Android Development] BlaY0:
Nope. ClockworkMod recovery has its own logging mechanism... but you would've known that if you would've read ClockworkMod howto/guiide/readme...
[Legend Android Development] gyroing:
i put new boot.img from zip file to clockwork/backup/newboot and generate md5 for this and put it in the same boot file location after that go to nandroid backup during backup:

go advance restore boot

cheack md5 of boot ok

... error while installing boot

but when i do same action for boot.img in b26

do advance restore boot

install book ok and start ok
[Legend Android Development] tauk2mi:
I have successfully rooted my legend and used azure for some time. I have a unique problem. My organization runs exchange 2007 and I could successfully configure exchange account on the mobile. After the initial sync, the device is not receiving push mails. even if I do a manual refresh, its not downloading any further updates (mails / calendar events). I had even tried nightly builds of cyanogen, but it stops after the initial sync. Any expert advice on resolving this. Thanks in advance.
[Legend Android Development] BlaY0:
But why won't you just install/flash that whole zip file? Why are you trying to flash just boot.img?
[Legend Android Development] shark812:
that's the reason
[Legend Android Development] gyroing:
but if check sum was incorrect had didn't go to installing

i said in clock workwork wrote:

cheacksum ok.

deleting boot ok

restroing boot.img.............

error while installing boot

... so there is no boot and after restart automaticlly go to bootloader

back to recovery nandroid b26 boot with b31 rom and start .

i check my checksum the generate code in my software as same as in b26 and same az md5.zip file in rc1 (russian on) so chechsum is exactlu correct if you check the size new boot.img is 100 kb bigger?
[Legend Android Development] BlaY0:
Argh... leave that boot.img in that zip file and flash the whole zip file!
[Legend Android Development] gyroing:
when flash whole zip file will stay in white htc screnn (seems boot screen of htc) and get the device warm . and never go to boot animation . so i forced to restore b26 boot.img to go to boot animation . that mean all of rom from new build but boot.img from old bulid rc0-russian or b26 or lower.

pls help us .

i start this bug in froum 4 days ago but nobody pay attention now i see the many people has same problem.

defnetly if i haven't problem with whole zip file i never use old boot.img
[Legend Android Development] BlaY0:
Flash; wipe; power off yr phone; hook it up with PC; fire adb logcat on your PC; power on yr phone...
[Legend Android Development] jussy:
Little help needed

Sorry guys...

Can someone give me a link to the n26 or below?

It isn't available on teamdouche and I'm stuck a htc white screen with newer nightlies.

Thanks a lot.
[Legend Android Development] ali ba:
I don't know why the newer kernels/boot-images might result in a boot loop for some of you. And I won't be able to investigate it further until I get log-files (use something like pastebin.com).

This is really the last time I'm telling anyone of you: Whining about problems doesn't fix them. Provide (proper!) log-files. All further bug reports will be ignored if you can't follow that easy rule.
[Legend Android Development] gyroing:
it is not solved yet.
[Legend Android Development] BlaY0:
Provide ClockworkMod log of flashing process and logcat log...
[Legend Android Development] jussy:
I'lo be glad to provide them, but don't know how.

Can you be so kind to tell it to me.

Many thanks.
[Legend Android Development] greenolive:
Oh, you're gonna get it now :)
[Legend Android Development] BlaY0:
Sure, just go to search option of xda and find ClockworkMod and adb howto/guide. Don't know exact addresses but I'm confident you will find them, there are some.
[Legend Android Development] xcrew:
For those interested, build 33 seems stable. (Dumfuq OC844 3.5 kernel)
[Legend Android Development] ropaisoft:
Confirmed, b33 runs fine so far.

Sent from my Legend
[Legend Android Development] kabler:
plus one here, same problem.
[Legend Android Development] gyroing:
unfortunately it not go to the phases that produce logcat becuse no adb driver could detect devices in this state ??

in other build logcat works but in this boot logcat don't works because no device detected at start
[Legend Android Development] BlaY0:
That's why I said that you also have to provide ClockworkMod log of flash process.
[Legend Android Development] kugel.:
Is anybody else noticing increased battery drain on recent nightlies? b31 seems to be worse than b26 in that regard.
[Legend Android Development] gyroing:
also clockworkmod doesn't make any log!!!

:(
[Legend Android Development] ancdix:
Build 33 runs very stable.

I don't have anymore "wireless-lags"

Everything smooth so far :)

Great work !!
[Legend Android Development] BlaY0:
Sure it does. Just go through menu, U will find it. Make sure U try flashing first so there will be something in that log.
[Legend Android Development] jussy:
Recovery log found.

Thanks.
[Legend Android Development] gyroing:
i find report error option in advance dear . recovery log is attached.

this from russian and i will add b31 too
[Legend Android Development] gyroing:
here is the major problem from recovery.log:

[/tmp/verify_cache_partition_size.sh] with 1 args

mtd: not writing bad block at 0x00140000

write_raw_image: error erasing blocks of boot

write_raw_image: error closing write of boot

wrote boot partition from /tmp/boot.img

script result was [/system]

Install from sdcard complete
[Legend Android Development] deimdos:
yeap, I did too
[Legend Android Development] Sckank:
1186 Quadrant score with 806 3.5 kernel with this ROM. Not bad :)
[Legend Android Development] BlaY0:
@gyroing: I might have an idea what's wrong. Will look into it more closely tomorrow... gotta get sum sleep.
[Legend Android Development] kuklux:
are you using new update of quadrant standard?
[Legend Android Development] pfak:
I can't reproduce this, if anything the battery life has improved.
[Legend Android Development] rajasyaitan:
Anybody tried b34?
[Legend Android Development] gyroing:
I'm waiting for ur kind look to the log.
[Legend Android Development] liltbrockie:
Just flashed it... so far so good.
[Legend Android Development] BlaY0:
OK, here we go. As I said I might have known what was wrong... I'm not 100% sure but 99% would do.

First my question would be... HOW MANY TIMES YOU GUYS ALREADY FLASHED YOUR GIZMOS?????

The problem you and some of guys have is that boot.img image doesn't fit your mtd boot partition any more (the kernel got bigger in the last few versions, maybe Alex could elaborate this as he is special agent in charge of Legend CM port).

The size of boot partition on NAND flash is exactly 2621440 bytes (2,5 MB). The cell block size of our NAND is exactly 131072 bytes (128 kB). And since you have one cell of your NAND already dead (block at postition 0x00140000 of your mtd boot partition), you have yet only 2490368 bytes left to flash but boot.img is bigger than that so you are basically out of luck bro. One option you have is to use a kernel that is more modularized and less monolith thus smaller (dumfaq's or my versions would fit this profile just fine) but you would have to construct your own boot.img from alternative kernel image and CM's initrd image.
[Legend Android Development] shark812:
mmm i find a log file in clockwork directory and i think that the problem is the same. Can anyone check my file? Thanks
[Legend Android Development] Corra:
:eek: maybe was it defective? I think I'll stop flashing a new version of nightlies every day.......
[Legend Android Development] shark812:
And so our phone are Hardware broken? :(
[Legend Android Development] ali ba:
This is exactly what I thought yesterday after inspecting the logs.

I will try to trim down the kernel today a bit and provide you with an update.zip that you can test. I'm lucky enough to not have bad blocks on my device so I never triggered that error.
[Legend Android Development] gyroing:
my phone didn't flashed more than 10 times all of them was nightly build cm 6.1. ehat is my fault?
[Legend Android Development] midafaya:
b34 seems to include overclocking !

SetCPU gives me all the frequencies between 245 to 864 Mhz
[Legend Android Development] ali ba:
Nope. Only disabled HTC perflock and move to ondemand governor (with default max frequency of 600) which is

not

overclocking.
[Legend Android Development] shark812:
Thanks ale... but there's no way for our blocks to be restored or repaired. I'm right?
[Legend Android Development] BlaY0:
Oh, you definitely have some bad blocks, just not on a boot portion of NAND ;)
[Legend Android Development] gyroing:
what did happened wrong?

we always follow regular rom.zip since we saw b30 and after .

is there any treatment . format boot don't sole adb/fastboot ???

is there any way to clean bad block through update-script??

i could use boot.img b26 with new rom does it make bad performance . my device now works with latest rom b33 with boot from b26 . is it correct or not . what is inside of new boot that make bigger?
[Legend Android Development] BlaY0:
Cells of NAND chips are deteriorating over writes. Too many writes to a certain cell would render it bad. Every NAND chip has several bad cells just right after it leaves the production line, it can't be prevented. You have just been lucky enough to get one that has bad cell right in the middle of a portion where boot.img is to reside. I don't actually believe that this cell went bad while being erased and written to... you will have to overwrite it like at least 10.000 times. Have you been flashing your device so many times?
[Legend Android Development] gyroing:
not more that 20 times.

and why the other guys has same problem in bad block ?!!!

if it caused from my personal trolling of block why the other has same problem !. many of them says we are noob and at the first time after rooting their device encountered this problem.
[Legend Android Development] BlaY0:
Who says it's the same block address? You have portion of 20 cells availabel for boot.img. Any cell of these 20 can be already worn off or can wear off in a process of rewriting.
[Legend Android Development] ali ba:
This is most likely not related to our problem. Normally those cells should take 100.000 rewrites or more.

Bad blocks on your devices they are caused by the manufacturing process itself and were bad even before the first write attempt.

Test boot image attached. Flash latest nightly and this zip afterwards.
[Legend Android Development] BlaY0:
Well I know that, because I wrote that several posts before you ;)

But I wouldn't be so sure that each cell could withstand 100.000 rewrites. This is true for the whole device (let say sdcard of several GB) that has it's own controller and has portion of cells just for the purpose of relocation of bad ones.
[Legend Android Development] BlaY0:
That's why are some of ppl here experiencing faster battery drain.
[Legend Android Development] gyroing:
thx for your attention i will test it now.