yashsingh1/xdaforums huggingface dataset:
[Legend Android Development] nafnist:
SpeedLegend 0.6 using 787mhz oc

38,6 fps in Neocore with sound

503 in Quadrant

3.4 mflops in linpack
[Legend Android Development] dumfuq:
Install a kernel with a lower frequency :). One extra frequency per kernel.
[Legend Android Development] qzem:
dumfuq sorry to bother you, but have you any idea, why the oc kernel v2.2 with frequency 768 works on my phone, but the version v3.1 with same highest frequency (768 mhz) stucks at boot animation and only reboots phone constantly... Would appreciate some advice :).
[Legend Android Development] lwiss:
now with version 3.5 / 844 mhz ....

very very fast !?!?

lwiss
[Legend Android Development] tonper:
Azure overclocking

I did ran a few benchmarks on my Legend the other day. It's loaded with Froyo Azure CM6. I decided to run these benchmarks to see if the Overclocking would do any difference. I do not have any benchmarks of the original rom in this list, but w/o overclocking I did score around 450 in Quadrant Advanced.

So here are the scores I got from all my benchmarks with the

different overclocking frequenzens in Quadrant Advanced.

806MHz

1st. 500

2nd. 526

3rd. 531

825MHz

1st. 550

2nd. 487

3rd. 539

4th. 533

5th. 527

6th. 532

7th. 526

8th. 534

844MHz

1st. 533

2nd. 546

3rd. 475

4th. 538

5th. 543

6th. 515
[Legend Android Development] Corra:
Did you disable sound in neocore? I'm running azure+825Mhz kernel and I am just above 40fps
[Legend Android Development] agustrionopj:
Hi

I'm new here :D

mine is: 458 using quadrant (Azure 1.0.1; no OC)

still try how to take a snapshot in my phone

thx :D
[Legend Android Development] lwiss:
for make an screenshoot search in the "market": shootme

"hide it" and make the bench-test then finaly shake your phone....

the pic is in the "shootme-folder" in the sd-card.

lwiss
[Legend Android Development] agustrionopj:
Thx, already done it what you suggest

here come the results :D

I've tried now with dumfuq's kernel v3.5, oc-ing my proc to 768 MHz (left) and 806 MHz (right)

I still had no luck with 825 MHz and above, they gave me random freezes and reboot
[Legend Android Development] snakehult:
Ali ba does it again!

Azure nightly 0927
[Legend Android Development] qzem:
I just have to share this one...

Azure 9/27 nightly + oc768-legend-kernel-v3.5 from dumfuq

P.S.: too bad my phone can't handle higher frequency :rolleyes:
[Legend Android Development] Corra:
Linpack?
[Legend Android Development] TheGrammarFreak:
On my phone (overclocked, 787MHz) with Dark Azure Linpack is consistently in the 10's
[Legend Android Development] qzem:
My highest score in Neocore was 41,6 FPS. And here is the screenshot of linpack test.
[Legend Android Development] agustrionopj:
I just tried Nightly Build 7/29 w/ Azure 1.0.1, o/c-ed @806 MHz

Quadrant gave me 1102 :D (see attached file)

but then it froze :(

revert back to 787 MHz
[Legend Android Development] Corra:
Wow! I'm below 10 even at 825MHz with Azure 1.0.1
[Legend Android Development] g0dshead:
same rom/kernel wickedsick bench.
[Legend Android Development] qzem:
Yeah I got once 1067, I think that it depends if other programs are running in the background.
[Legend Android Development] copponex:
I just... omg..
[Legend Android Development] Polobyxa:
Seeing som good results now in Quadrant using Dark Azure 09/27 and dumfuq´s v3.5 844 OC-kernel.

Good ****!
[Legend Android Development] TheGrammarFreak:
That is so unfair. I wish I could use the 844...
[Legend Android Development] Chaotick:
My results (not overclocked Legend Dark Azure Nightly):

Quadrant: 1st run 886 points, 2nd 917 points

Linpack 1st 7.414 MFLOPS 2nd 7.468 MFLOPS

I Don't know if its the placebo effect of these numbers but this ROM fells snappier that AZURE.
[Legend Android Development] zeonism:
Running Dark Azure (0927) and fisrt and second run on Quadrant gives 810 and 901. Linpack gives 6.581 and 6.145. I mean 0927 gives almost 50% extra performance boost than the stable build. Good stuff!

Oh and by the way no OC as well.

Andy
[Legend Android Development] JonasDroid:
Azure 9/27 dumfuq OC 806Mhz (v3.5)
[Legend Android Development] kuklux:
running nightly build
[Legend Android Development] qzem:
Do you use any OC kernel?
[Legend Android Development] xcrew:
i get points in the same range, always 1150 -1250. I to am using the CM nightly build along with dumfaq OC844 kernel so yes, to get those kind of points you need an OC-Kernel.

Edit: Though i seriously doubt quadrant scores. I tried the DPI zip:s (LCD130.zip, as i find the drawer to be more responsive with this setting) posted in this part of the forum. As far as i understand those zip:s only change a single variable, and yet they make the phone think its on azure 0.6 and the quadrant score goes down to ~560p.
[Legend Android Development] greenolive:
Nevermind :)
[Legend Android Development] smartsreenath:
xcrew ,bro i tried with 806 & i got better results.but it is not stable keep on rebooting......what about you ?

FOLLOW ME http://smartsreenath.blogspot.com/
[Legend Android Development] qzem:
It doesn't think it is azure 0.6, the reason why it says 0.6 is in build.prop file, which contains data from that rom. I believe that results are worse bcause the DPI change, bigger resolution means more work for the processor.
[Legend Android Development] kuklux:
yep i use OC kernel 806 v 3.5
[Legend Android Development] xcrew:
Im using the dumfaq OC844 Kernel and i havent noticed any instability. My system never reboots. Im using setCPU with 3 different profiles.

1: screen off 245/245 priotity: 100

2: battery < 100% 844/844 priority: 76

3: charging/full 844/844 priority: 50

having this settings forces the device to always follow one of the profiles. Perhaps this improves on the OC stability as the built in govenor wont be used. I have ran stresstests and it never fails. Also these profiles keeps me from having to "detect the device" in setCPU every time i restart the phone.

So if you havent got setCPU, try it out and see if it improves your stability issues.

this is my Q-score btw. Though it varies some between builds.
[Legend Android Development] randy_khoo:
Wow... You're quite insane...

Below is mine:

Azure CM 6.0.0 With O/C to 768 max, 245 min
[Legend Android Development] xcrew:
One thing i have noticed is that quadrant tend to give lower scores if the cpu frequency isnt set to a static value. So if one is running 245/768 one will get lower scores than 768/768. It seems like setcpu downclocks a couple of times during the benchmark.
[Legend Android Development] JonasDroid:
Still you shouldn't be keeping the processor at 844Mhz at all times. Unless you want to bake an egg or want some firework. I mean for daily use just a quick lock for a benchmark probably won't hurt.
[Legend Android Development] BlaY0:
That's the most stupid assumption I have ever read...

Another one... SetCPU does nothing except setting the lowest/highest limit of certain cpufreq governor - you can do that manually without SetCPU. So governor does actual frequency switching and not SetCPU.
[Legend Android Development] xcrew:
It wasnt an asumption, it was an observation. The phone itself said it had azure 0.6 and quadrant gave me less score. As for setCPU... the point was that the frequency itself changes during the benchmark not what changes it. And the resault was once again an observation. And there is defenetly no need to get rude about it.
[Legend Android Development] BlaY0:
Hey m8, if I sounded rude or disrespectful then I'm sorry. But you said and I quote: "It seems like setcpu downclocks a couple of times during the benchmark.".
[Legend Android Development] xcrew:
What i meant was that the values to use comes from setcpu. And what i meant about rude was "thats the stupidest..." thingi. Thats not exactly constructive criticism :).

That said.. i will most certainly be wrong once or twice... and if i am... tell me whats wrong instead of just telling me i said somethig stupid.
[Legend Android Development] TheGrammarFreak:
My LCD changers shouldn't, and on my device don't, have an effect on the performance of the phone. Old versions changed a variable that told the phone what ROM it had, the latest ones don't. So use the latest one. :D

You might loose a couple of points with them, as the CPU has to work a little harder, but nothing like the drop you're experiencing. As for what causes that, I don't know.
[Legend Android Development] xcrew:
Was sure i had the latest one, but obviously i was wrong. Will update asap.
[Legend Android Development] BlaY0:
Oh, c'mon man! Better see what's inside not just flash any zip you can grab. You obviously flashed the wrong build.prop. BTW build.prop is not the place just for editing DPI, it is much more, see for yourself. You better put the original back and edit it via ClockworkMod to set ro.sf.lcd_density property to your desired value. You can even do it on-the-fly using setprop and killing system_server afterwards.

PS: snakehult made DPI changer update that does sed replace of just ro.sf.lcd_density property. You'd be better with it than replacing entire build.prop again.
[Legend Android Development] xcrew:
That was alot of terms i dont uderstand. And i didnt flash something i didnt know what it was. I had used it on a previouse build without problem. Only thing was that i didnt notice that there was an updated version.
[Legend Android Development] TheGrammarFreak:
Snakehult's version is much better.

Swyped from my HTC Legend
[Legend Android Development] BlaY0:
Could you please backup your current build.prop version, put the original back on and then diff both versions to see all the differences. Maybe there are more, since I honestly don't believe that version string would so much influence the end result of the Quadrant bench. Thanks m8.
[Legend Android Development] xcrew:
Cant be arsed to revert everything just to test, since its working now. But the fact is that i installed a fresh copy of cm nightly, got about 1200p i quadrant. Flashed the dpi zip, ran a benchmark, got 560. I repeated the procedure two more times with the same result before giving up on the dpi change. But the phone didnt handle different in terms of speed. The only difference seemed to be benchmark score. In particular i noticed that the H264 compression test was slower with dpi zip.

And i agree that its hard to beleve. I have no idea why this is
[Legend Android Development] BlaY0:
Hey, are we living on the same planet? Nobody asked you to revert everything, just build.prop! If that's too much for you then at least tell me exactly which ROM are you using and exactly which DPI update have you flashed.
[Legend Android Development] xcrew:
No aparently we aint on the same planet. I dont know how to do what your asking me. I got this working perfectly now and im happy with that. And just because i use this rom dosnt mean i know what every subfile does. So if your trying to make some random user understand what your sayin you might wanna be a little more specific. Just a thought.
[Legend Android Development] BlaY0:
Well, first of all, you made appearence here on development forum... that indicated that you were or wanted to be in an Android development business somehow. Then you made false assumptions and stated that maybe you would be wrong once or twice... but you obviously had no clue what you were talking about (not to mention what we were talking about) and had no slightest idea what that DPI update did, what's in it and how did it work, not to mention how did OC kernel update work. What's your point being here? It's like going to seveneleven to buy turbocharger (next to bread and milk) installing it into your brand new car (but you don't even care to read the manuals) and then when something goes wrong, going to your local mechanic to tell him that this turbo charger is a piece of crap and it made your car go slower than before and that it was obviously (you assume) made for some other car model.

I have two words for you... get real. Read something before you stop here, learn something on your own and most important learn how to debug things so you could be of any use to us...
[Legend Android Development] TheGrammarFreak:
Watch it BlaYo, we were all new once. Just drop it now, if they're happy with how it is, then leave it.
[Legend Android Development] ikdegek:
SetCpu problem

Hi, I am running azure 1.01 and installed the various kernels. No problem so far, but the app. SetCpu causes the legend hang for 5-10 seconds after activating the phone and causes ADW or Launcher to FC.

With different settings en kernels, same result. After removing SetCpu, no problem anymore.

Anyone having issues like this?

Thanks, Ik
[Legend Android Development] BlaY0:
Well, hell yeah... now he's satisfied and all is working... but in few days/weeks he will return here again with something like: "My phone was all fine showing 1500 pts in Quadrant but now it is showing only 300. What shall I do? Please help!"
[Legend Android Development] TheGrammarFreak:
Just drop it mate. If he does, I'll deal with it, yeah?

Swyped from my HTC Legend
[Legend Android Development] snakehult:
This is a developmentforum and as I wrote in first post put your benchmarking here with screendump.
[Legend Android Development] xcrew:
Hehe dude chill out. Whats the big fuss? I was only comfused why this was so. I made an observation of what i saw. Yes i said something that turned out to be wrong, and i admited it and was open for beeing corrected. Instead i get "omg omg got damn noob, get out of here". Ever heard of constructive criticism?

Anyway... i dont want to start a big discussion here so im not gona say anything else about it.
[Legend Android Development] snakehult:
Sure, but there so many threads about howto etc so There for I wrote i first post what this thread is about.

Benchmark only. questions to PM or other threads.

Now I pollute my own thread too. :eek:

More benching!
[Legend Android Development] murre87:
[ROM] CyanogenMod 6 nightly builds

Have anyone tried to benchmark CyanogenMod 6 nightly builds
[Legend Android Development] xcrew:
i have. This score is from build 3 or 4. Anyway there have been little difference in score between builds for me.

This resault was done with dumfaq OC844 kernel v3.5 with the freq fixed at 844Mhz
[Legend Android Development] Carveout:
SuperFroyo MVZ Legend 8.2 Quadrants:

OC806 @1123

OC825 @1155,

OC844 not stable...
[Legend Android Development] Caifan09:
CM6 Nightly legend build #33 with 806 Mhz kernel....
[Legend Android Development] HpX:
Azure 1.01 and 768 oc
[Legend Android Development] Krazywrath:
Running Azure 1.0.1 @ 600. Under normal use, killed all services except for SetCPU and Android keyboard.

Pic showing highest result out of 4 tests: (455,446,455,463)

Will finally OC mine in the near future to hopefully get better results :)
[Legend Android Development] el.dizzee:
I know differences in benchmarking results don't necessarily translate well into especially observable differences in performance, but on my legend also running azure 1.0.1 with the 787mhz v3.5 oc kernel I'm getting a score of 557 in quadrant. How is your score so high?
[Legend Android Development] Skardy:
His signature says: ..-''-..-''-..HTC Legend, CM Nightly B39 -> 787Mhz OC..-''-..-''-..

Nobody has those scores on Azure (based on CM6.0)

With CM6.1 nightlies scores range is 800-1250 depending on release and OC :)
[Legend Android Development] el.dizzee:
Ohh ok, yeah in his post he said he was running azure so I wasn't sure. Thanks! Build 39 sounds hella fast :)
[Legend Android Development] HpX:
lol,it was suposed to say....

Azure 1.01 and 768 oc = 498 and with cm39 :p

to much copy, to litle paste .. he he..
[Legend Android Development] el.dizzee:
Oooh haha gotcha, well that makes quite a fair bit of difference! Thanks
[Legend Android Development] Dr.Romca:
I use MoDaco r1 Froyo release (with sense) and Blayo's O.C. Kernel @ 768MHz (can't go higher),

I don't have the pic now, but I got as high as 1108pts in Quadrant :)

I'll upload a pic soon...

I only got 1105 now :(
[Legend Android Development] dirtywest:
cyanogenmod nightly 88 @ default mhz

total score 797
[Legend Android Development] BlaY0:
B 0.2 test release 6 at 787 MHz and data2ext in action...
[Legend Android Development] ogo2:
That's double from your first release! :)
[Legend Android Development] BlaY0:
Yeah, but you should know that this is not a public release and it never will be. It is too risky and dangerous. You should expect at max 1500-1600 with B 0.2 but I'm still deciding on data2ext method to use so it might get even lower (but safer)...
[Legend Android Development] TheGrammarFreak:
Woah. That's cool dude. :D

Sent from my GT-P1000
[Legend Android Development] rajasyaitan:
Wow BlaY0. That is an awesome benchmark.
[Legend Android Development] ogo2:
Damn, i almost forget the time when my phone scores 400 pts... :)
[Legend Android Development] snakehult:
What does it do for boot-time ? compare to 0.1
[Legend Android Development] Juicy47:
Impressive, and good work BlaY0!

*N.B. The Desire with the similar hack for Data2EXT is scoring ~8000 in quadrant in comparasin
[Legend Android Development] BlaY0:
Can you point me to some threads?

Sent from my HTC Legend
[Legend Android Development] TheGrammarFreak:
Search. ;)

Jokes

Sent from my GT-P1000
[Legend Android Development] BlaY0:
You mean if boot time is shorter or longer? No difference.

I would but I don't have time for this. If anyone would like to have Legend with 5000 PTS in Quadrant, he/she would have to search for me :D
[Legend Android Development] cryshop:
I/O pts is increased alot, but the point is, does I/O actually run faster?
[Legend Android Development] snakehult:
If it would the boot time might be shorter as well,
[Legend Android Development] BlaY0:
Well shorter it is... for say 2 or 3 seconds... but does that really matter? How many times do you boot your phone? Mobile phone as a device should be stable enough so we wouldn't need to reboot it anyway.

IO itself is important but if I'm frank, Quadrant score doesn't reflect the actual/real performance. Reads/writes can be faster but this is not such an improvement that one would notice a significant boost in device responsivenes.
[Legend Android Development] BlaY0:
OK, this is my latest:

...and I honestly think that Legend can't go much higher.
[Legend Android Development] Bricolo_fr:
what class of sd card are you using? I assume it does matter
[Legend Android Development] BlaY0:
Transcend 8 GB class 6... nothing special.
[Legend Android Development] stiffmast3r:
whats the name of this benchmark?

is it the same like quadrant?
[Legend Android Development] smartsreenath:
its quadrant...
[Legend Android Development] rajasyaitan:
BlaY0 did it again.
[Legend Android Development] Skardy:
It has the "colored bars" because it's the paid version :)
[Legend Android Development] stiffmast3r:
oh ok thx, so, its the same?

points and all of them is the same like quadrant standart?!
[Legend Android Development] snakehult:
yes

10 char
[Legend Android Development] postmaster2:
yes

................
[Legend Android Development] TheGrammarFreak:
CM7, data2ext

This is all well and good, but dalvik-cache is regenerated on every boot... :confused:
[Legend Android Development] snakehult:
Nice :)

Just finish compiling my own cm7
[Legend Android Development] gregnapola:
Just tested on CM7.0 data2sd from Blayo's ROM ...I can't run it! After data2ext --enable and reboot I get stuck on CyanogenMod logo... How did you do that ?:o
[Legend Android Development] BlaY0:
Don't use my data2ext script on any other ROM but mine. It won't work!

Check if there is a link /data/dalvik-cache pointing to somewhere else. If it is, remove it and reboot.
[Legend Android Development] TheGrammarFreak:
If you do it this way I cannot guarantee it will work, assume it won't. I will take no responsibility for anything that you do to your phone. If you copy and paste these commands without giving thought to what they do I will just laugh at you. I will laugh even more if it goes wrong. These steps are what I think I did, off the top of my head

Boot up CM

Connect to PC

adb shell
stop zygote
stop keystore
mkdir /mnt/asec/data
mount --move /data /mnt/asec/data
mount -t ext2 -o nosuid,nodev,noatime,nodiratime /dev/block/mmcblk0p2 /data
chown 1000.1000 /data
chmod 775 /data
cd /mnt/asec/data
cp -a app /data/
cp -a app-private /data/
cp -a backup /data/
cp -a dalvik-cache /data/
cp -a data /data/
cp -a dontpanic /data/
cp -a secure /data/
cp -a tombstones /data/
ln -s /mnt/asec/misc /data/misc
ln -s /mnt/asec/system /data/system
ln -s /mnt/asec/property /data/property
ln -s /mnt/asec/local /data/local
start keystore
start zygote
logcat

Then pray ;)

This is basically what BlaY0's script does, I'm still working out a few kinks with the script for installing it. The logcat command is optional, but I like to know what's going on. With this it is all lost on reboot, but it should give you an idea of what CM is like with data2ext. Anyhoo, I've never scripted anything before, and some of these commands are meaningless to me, but I reckon I'll work it out. :D

TL;DNR:

With great friggin' difficulty. When I've worked it all out I'll post a version for CM ;) And like BlaY0 said, his script won't work on other ROMs

EDIT:

I have now made said zip. Try it at your own risk ;) http://xdaforums.com/showthread.php?t=902395

/EDIT

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

ls -l /data reveals no such links from dalvik-cache.
[Legend Android Development] bjohv052:
Does data2ext increase performance? What class sdcard is needed?
[Legend Android Development] BlaY0:
No, it decreases it so your phone would crawl like a turtle.

And you'll be needing class 17 SD card otherwise it won't work.

Sent from my HTC Legend
[Legend Android Development] bjohv052:
To me it is not obvious that disk read/write is faster to an sdcard than to the internal flash of the phone. My question can't be that stupid. Or?
[Legend Android Development] TheGrammarFreak:
It is both faster and slower. And that is not sarcastic. Sometimes the phone flies, sometime it lags like crazy ;)
[Legend Android Development] HpX:
CM 6.1 Data2ext
[Legend Android Development] TheGrammarFreak:
Was that my zip?
[Legend Android Development] HpX:
Nop..

Just testing things out my self for a change..

I dont know if it works as it shuld, just did it.. But for now it look good :p
[Legend Android Development] TheGrammarFreak:
Fair enough. I'm just trying to determine if it works on CM6. Guess I'll be testing myself :D
[Legend Android Development] HpX:
I downloaded your zip, and looked at your script, as far as i can see, its about the same as mine just minor syntax differences. so i guess it shuld work.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Bo092009:
Hi,

I have the following problem: After I started using android on my german HD2, google maps on windows mobile crashes every time I try to launch it. So I flashed a stock rom and it worked again until i booted android again. Any ideas why this could be? I am using HTC stock rom again and radio 2.08

I like using android but using maps on windows mob. is quicker since android takes a while to boot...

Thanks!
[HD2 Android Q&A, Help & Troubleshooting and Genera] mutou1943:
My problem is not the same.

I can't use google map in android build.

When i switch back to WM,google map works fine for me.

I use mattc's Sense build V1.5 now.

But in some early andriod build it works fine via WIFI.(not mattc's build )

Somebody else have this problem? OR who konw how to deal with this?

Sorry for my poor english.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Fandri:
I've got the same, after using of Android; Google didn't start in Winmo at all.

Any solution how to fix it?
[HD2 Android Q&A, Help & Troubleshooting and Genera] Raudi1:
Perhaps it's a problem with the cache. If I remember correctly, some sense build I used some time ago stored the cache in the same directory as winmo. So you could try to delete the cache via the options, or delete the folder.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Bo092009:
Problem solved

Well, I switched to darkstone's froyo V2 and deleted the contents of /Temp and after a soft-reset and a crash it works again! (Seems weird, though...)

Thanks to all who have tried to help!