Develop Bugs

[Q] (SOLVED!) Overclock the Defy?

*SOLVED*
Milestone Overclock - a free download from the marketplace does now support the Defy. Quadrant shows promising figures for sure.
Just wondering whether anyone has gotten the Defy to Overclock?
I've been trying some Droid Overclock apps as well as purchasing Set CPU.
I've successfully rooted my phone which is a requirement for enabling overclocking features. Set CPU won't even start.
None of the apps I've tried have been working properly.
Any tips?

in developement
Look on the milestone overclock googlecode page, its on the todo list

good to know

Yepp, thanx a lot. Since the chipset has clear OC potential this will be very interesting. Especially if the Defy has an omap3630 core, we'll see.

dave79 said:
Yepp, thanx a lot. Since the chipset has clear OC potential this will be very interesting. Especially if the Defy has an omap3630 core, we'll see.
Click to expand...
Click to collapse
I'm pretty confident that it does indeed have a 3630: http://forum.xda-developers.com/showpost.php?p=9540564&postcount=34
Not only because of the screenshot from windows, but look at how close it is to the Droid X, running a 1ghz 3630.

Wow! and getting that benchmark score while running on 800MHz is quite impressive. I've got good hopes that a ported Milestone Overclock will unleash the raw power the phone truly possess.

And this is not the best defy can do. Actually 1117 has been reported from 2 users (one is me).

Im not sure how this phone is so amazing, and so cheap at the same time
umm yeah anyways, just wanted to say i got quadrant scored of around 1110 to 1118 ish i think- after task killing
Really hoping for some custom 2.2 roms in the near future, like some others said it will make this probably -one of- the best androids out there

xdaid said:
And this is not the best defy can do. Actually 1117 has been reported from 2 users (one is me).
Click to expand...
Click to collapse
My personal best is 1104

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Whoa, nice one, Higgsy!

Sorensiim said:
Whoa, nice one, Higgsy!
Click to expand...
Click to collapse
weeeeell to be fair there was a little cheat there, that was with JIT enabled. But JIT by the standard method wasn't stable, at first it was fine but then after ab out an hour I started to get random force closes, so I reverted. Its a little insight to what can be achieved with JIT. IMO I'll take JIT over a 1GHZ overclock.

Could anyone of you guys share your benchmark results after running Milestone Overclock? I'm now running on 1.2GHz and it's stable

xdaid said:
And this is not the best defy can do. Actually 1117 has been reported from 2 users (one is me).
Click to expand...
Click to collapse
My first benchmark result was in mid 1000 but after a restart I got that score too.

To use JIT is better wait for froyo because have it in native form. There are a appl called JITTER in the market but I think that isn't reliable. (I don't know about other appl similar than)
Now I use the Milestone Overclock beta4 and configure the oc at 1000/56
Someone have better configuration to use? Can explain why?

Hey guys.. Overclocked my Defy with the Milestone Overclock. 1200/66
Got a 1438 benchmark on Quadrant Standard. Putting the vsel any lower got my Device to reboot.
After trying it out I switched back to 1000/52 because some users said that running on 66vsel could damage the CPU.
Main effect I had: Launcher runs very smooth, My battery life went down to 24 hours (37h before).
With 1000/52 I still get a benchmark around 1247
Works for me because I´m saving battery and still got enough power to have a smooth launcher.
But: Can anyone please tell me what the standard settings are ? *lol* Forgot them 800Mhz an vsel=???
Thx in advance.
Daniel (from germany)

Daniel.Stevens said:
Hey guys.. Overclocked my Defy with the Milestone Overclock. 1200/66
Got a 1438 benchmark on Quadrant Standard. Putting the vsel any lower got my Device to reboot.
After trying it out I switched back to 1000/52 because some users said that running on 66vsel could damage the CPU.
Main effect I had: Launcher runs very smooth, My battery life went down to 24 hours (37h before).
With 1000/52 I still get a benchmark around 1247
Works for me because I´m saving battery and still got enough power to have a smooth launcher.
But: Can anyone please tell me what the standard settings are ? *lol* Forgot them 800Mhz an vsel=???
Thx in advance.
Daniel (from germany)
Click to expand...
Click to collapse
Someone in the other thread was running 800/38, I haven't tried it because like you 1000/52 gives me better battery life than stock and more power on top.

Higgsy said:
Someone in the other thread was running 800/38, I haven't tried it because like you 1000/52 gives me better battery life than stock and more power on top.
Click to expand...
Click to collapse
Thanks for answering ;0)
I just wanted to know the original settings in case I wanted to restore them someday.
Or do I just have to click on "unload module" for that ?!? (I gues that´s it I was just to blind/dumb to see it *lol*)
Thx ;0)

Daniel.Stevens said:
Thanks for answering ;0)
I just wanted to know the original settings in case I wanted to restore them someday.
Or do I just have to click on "unload module" for that ?!? (I gues that´s it I was just to blind/dumb to see it *lol*)
Thx ;0)
Click to expand...
Click to collapse
Yeah just unload module and untick apply on boot and your back to stock

Im currently running 1100MHZ with a 58vsel, seems stable so far and got a quadrant benchmark of 1317. But i am wondering if this setting is safe for long term use, I need my phone to last till the end of this conract

Quadrant Scores:

lets post scores and what we are running to get their to help compare the different options available now for our Droid Incredible 2's
1649 gingerbread (.3.) for another week or so

CM7 Nightly 2. Stock kernel, not overlocked:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Cm7 overlocked to 1497
30 minutes or so later...and yes my crappy digital cameras clock is wrong

Cyanogen 1.8ghz

Underclocked and still better than stock. Runs great at 768mhz. No complaints.

Maximum overclock on stock CM7 kernel (~1.5ghz).

I did some tests with the CM7 Nightly 3. I got some amazing scores:
Stock cpu speed:
1.2GHz:
1.45GHz:
1.6GHz:
1.7 and 1.8GHz gave me lower scores than 1.6GHz, so I guess its safe to say 1.6Ghz is the max stable speed.

can't wait to hit cm7 and push it now !!!

Running miui at 1.49ghtz.
Sent from my Incredible 2 using XDA Premium App

Im running cm7 nightly 3 at 1.8 (and tested at 1.6) I am only around 2800 how are y'all getting up to 3500?
Sent from my Incredible 2 using XDA App

Interestingly, after some tweaking, messing around, and other stuff, I managed to score over 2200 at 768mhz. I'm getting some nice smooth performance out of it while underclocked, and getting it to do things quicker means it'll save that much more battery.

nimdae said:
Interestingly, after some tweaking, messing around, and other stuff, I managed to score over 2200 at 768mhz. I'm getting some nice smooth performance out of it while underclocked, and getting it to do things quicker means it'll save that much more battery.
Click to expand...
Click to collapse
What exactly did you tweak and mess around with? Cause that's sounds pretty nice.

melgibson666 said:
What exactly did you tweak and mess around with? Cause that's sounds pretty nice.
Click to expand...
Click to collapse
I'm not really sure, to be honest. I was mostly tweaking personal preferences, then messing with governors on the CPU. While comparing governors, the number kept climbing until it broke 2200 then fell back to just under 2200. I double checked my CPU clock settings to make sure I was still at 768mhz. I haven't really done any further testing. I suspect part of it may be JIT optimizations, but I'm not sure.

nimdae said:
I'm not really sure, to be honest. I was mostly tweaking personal preferences, then messing with governors on the CPU. While comparing governors, the number kept climbing until it broke 2200 then fell back to just under 2200. I double checked my CPU clock settings to make sure I was still at 768mhz. I haven't really done any further testing. I suspect part of it may be JIT optimizations, but I'm not sure.
Click to expand...
Click to collapse
Yea I was messing around with the different govenors after reading your post and I noticed a big difference between the power saver and ONdemand. Power saver makes the transitions a little sluggish but I guess that's to be expected for what it's trying to do. lol All in all though the battery life on ondemand is leaps and bounds ahead of the stock ROM I'm running a 1.1ghz clock right now and it is like butter with battery life to boot.

Quad Standard
mine came in at 2924 thats awesome!

tragedy , mine is between 1250-1500

zozor said:
tragedy , mine is between 1250-1500
Click to expand...
Click to collapse
What Rom
Sent from my Incredible 2 using XDA Premium App

zozor said:
tragedy , mine is between 1250-1500
Click to expand...
Click to collapse
Stock ROM? Mine wasn't even that low stock. Did you run it more than once?
Sent from my Incredible 2 using XDA App

am running this rom
[ROM] Offical Gingerbread 2.3.4 ROM is out via OTA by ChinaTelcom

zozor said:
am running this rom
[ROM] Offical Gingerbread 2.3.4 ROM is out via OTA by ChinaTelcom
Click to expand...
Click to collapse
Damn sorry bro I got a 2900 while on the phone lol
Sent from my Incredible 2 using XDA Premium App

Overclock - 1802mhz CPU, 512mhz GPU

I ran Quadrant Pro at 1802mhz on the CPU and 512mhz on the GPU (Franco Kernel & Jelly Belly ROM)
This was the result.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Did your phone explode? Because I don't see a picture.

And you posted this here..... Why?

Slemhelge said:
I ran Quadrant Pro at 1802mhz on the CPU and 512mhz on the GPU (Franco Kernel & Jelly Belly ROM)
This was the result.
Click to expand...
Click to collapse
thats lousy! id be embarrassed to show that off to people. i suggest a kernel change. anyways, that post does not belong here in development, nor anywhere near development heres trinity at 1728mhz..

simms22 said:
thats lousy! id be embarrassed to show that off to people. i suggest a kernel change heres trinity at 1728mhz..
Click to expand...
Click to collapse
LMAO! Damn you simms

can't beat simms at his own game =P

First off, that's embarrassingly low. I've gotten 4,000+ at 1.6GHz. Second why the hell did you post that in this section? I thought you needed 10 posts to post in a dev forum. Mods please close and OP read the damn rules.

irizwan said:
can't beat simms at his own game =P
Click to expand...
Click to collapse
lol, unfortunately not true though. there are a few that know how.
i just think that anybody running at 1802mhz should know how to propery use it or not be allowed to run that high of an oc. i mean, the op isnt getting any benefit from it unless you call a higher rate of battery loss a benefit. learn how to benefit from a high oc like this, or dont use it. its pointless to show off that youre using a high oc if a slightly oc'd(1344mhz kernel) can run laps around your phone. dont get me wrong, i know that franco kernel is capable, but this does it no justice.

simms22 said:
thats lousy! id be embarrassed to show that off to people. i suggest a kernel change. anyways, that post does not belong here in development, nor anywhere near development heres trinity at 1728mhz..
Click to expand...
Click to collapse
trinity FTW!

Then someone do tell me a good kernel and how to do a proper OC thats stable, efficient etc etc.. Im **** at OC'ing.. i just put franco kernel 512mhz and was allowed the option to go 1802mhz, which ive never seen before..

What development are you doing here?
None? Then why is it posted in development?!!
Thread moved
FNM

Slemhelge said:
Then someone do tell me a good kernel and how to do a proper OC thats stable, efficient etc etc.. Im **** at OC'ing.. i just put franco kernel 512mhz and was allowed the option to go 1802mhz, which ive never seen before..
Click to expand...
Click to collapse
Franco Kernel is a great kernel, yo must be doing wrong. I have achieved that score with franco's at 1.3 OC and Stock JB ROM...

Slemhelge said:
Then someone do tell me a good kernel and how to do a proper OC thats stable, efficient etc etc.. Im **** at OC'ing.. i just put franco kernel 512mhz and was allowed the option to go 1802mhz, which ive never seen before..
Click to expand...
Click to collapse
try them all, or a few different kernels at least. every phone is different, and will react differently to different kernels. also, just because you can oc to 1802, doesnt mean that your phone will properly handle it. at this point, it looks like you arent getting any of the gain from this high oc(some loss actually), but are going through your battery like you are. first off, at that high oc, turn off thermal throttling if you are going to benchmark. play with adjusting voltages until you find your sweet spot at that oc. try ocing less too, your phone might not like 1802, or 1700, or 1600.. not many phones do. also, when you benchmark, benchmark with your hiest cpu speed/highest cpu speed(1802/1802) so that you dont scale and actually bench 1802mhz.

simms22 said:
turn off thermal throttling if you are going to benchmark.
Click to expand...
Click to collapse
This is the key point that I believe the OP forgot to do.

IAmAN00bie said:
This is the key point that I believe the OP forgot to do.
Click to expand...
Click to collapse
very likely youre right.

Not even worth overclocking honestly.
Only for benchmark scores, your phone most likely doesn't run that much faster.

I Am Marino said:
Not even worth overclocking honestly.
Only for benchmark scores, your phone most likely doesn't run that much faster.
Click to expand...
Click to collapse
funny, only people that dont overclock say that, i guess they really do believe it for themselves. but in reality, there is a difference. if its a slight overclock, its not that different. when its a big overclock, the difference can be dramatic.

simms22 said:
funny, only people that dont overclock say that, i guess they really do believe it for themselves. but in reality, there is a difference. if its a slight overclock, its not that different. when its a big overclock, the difference can be dramatic.
Click to expand...
Click to collapse
I have overclocked before, I've done it before on the GNex as well.
I mean it was a huge increase of ability to a single core phone and early dual cores but for a phone already seemingly perfect on the software side, the phone already screams as stock clock speeds.
Besides, is it worth the probable loss of battery life? A marginally higher benchmark score? Things opening 1 or 2ms faster?
This is all just my opinion, I have no hard facts behind all this, but at least in my own personal testing and experimenting, there was no obvious benefit.
Provided you might be right, I've never OC'ed past 1.5, but beyond that, what's the effect on the health of the hardware, and like I said, battery life?
I could be totally wrong and I'm not against admitting being wrong.
Just personal preference I guess.

I Am Marino said:
I have overclocked before, I've done it before on the GNex as well.
I mean it was a huge increase of ability to a single core phone and early dual cores but for a phone already seemingly perfect on the software side, the phone already screams as stock clock speeds.
Besides, is it worth the probable loss of battery life? A marginally higher benchmark score? Things opening 1 or 2ms faster?
This is all just my opinion, I have no hard facts behind all this, but at least in my own personal testing and experimenting, there was no obvious benefit.
Provided you might be right, I've never OC'ed past 1.5, but beyond that, what's the effect on the health of the hardware, and like I said, battery life?
I could be totally wrong and I'm not against admitting being wrong.
Just personal preference I guess.
Click to expand...
Click to collapse
agreed. i myself use stock frequencies on franco kernel i've used almost all kernels and roms possible but now i've stuck with aokp n franco smooth even when under-clocked to 1 Ghz. i find no point of oc'ing other than just benchmarking usually get 3.4-3.3K on quadrant with normal freq.

simms22 said:
funny, only people that dont overclock say that, i guess they really do believe it for themselves. but in reality, there is a difference. if its a slight overclock, its not that different. when its a big overclock, the difference can be dramatic.
Click to expand...
Click to collapse
Your phone spends most of its life in the 350/700mhz range.
Signed,
An Overclocker

[Q] Undervolt Settings?

I'm currently on CM10+LeanKernel, and while my battery life is great as it is I was just curious to hear other opinions/settings/etc.
Now, I know this obviously varies greatly across each and every device, but I just wanted to get an idea of what generally works well for everyone?
I would try it out on my own but ever since coming from my Vibrant (It worked great with UV at first, but it would slowly but surely just not take to it anymore and I eventually just had to stick with stock voltage settings), I'm sort of hesitant to get started without others opinions.
Thanks in advance everyone!

Anyone...?

boothten said:
I'm currently on CM10+LeanKernel, and while my battery life is great as it is I was just curious to hear other opinions/settings/etc.
Now, I know this obviously varies greatly across each and every device, but I just wanted to get an idea of what generally works well for everyone?
I would try it out on my own but ever since coming from my Vibrant (It worked great with UV at first, but it would slowly but surely just not take to it anymore and I eventually just had to stick with stock voltage settings), I'm sort of hesitant to get started without others opinions.
Thanks in advance everyone!
Click to expand...
Click to collapse
I lower my voltage to reduce the heat being generated. I go about 125 across the board with lean and faux kernel.
And using the stress test feature on SetCPU it goes forever without rebooting so i feel comfortable with stability.

Honestly if you run supercharger scripts, remove bloat, you can keep core clocks to around 1.25max and 485 the lowest without any jitters or pauses, from my recent testing. This was on FreeGS3R6 and Trinity Kernel
I did not however find out what the lowest max clock-speed was before i noticed any slowdowns in user experience....but i will now be looking into this!

xgp0006 said:
Honestly if you run supercharger scripts, remove bloat, you can keep core clocks to around 1.25max and 485 the lowest without any jitters or pauses, from my recent testing. This was on FreeGS3R6 and Trinity Kernel
I did not however find out what the lowest max clock-speed was before i noticed any slowdowns in user experience....but i will now be looking into this!
Click to expand...
Click to collapse
All supercharger does is change minfree values. OOM groupings and things with memory. No CPU tweaks are happening. Just clarifying

I would be very careful with UV as it can cause permanent damage to the chips. I think I undervolted my gs3 too much and ever since then my phone has been laggy no matter what rom I flash.

atikis_maximus said:
I would be very careful with UV as it can cause permanent damage to the chips. I think I undervolted my gs3 too much and ever since then my phone has been laggy no matter what rom I flash.
Click to expand...
Click to collapse
Ive done some research before i started undervolting and this is the first time im hearing of such a claim.
Im running LiquidSmooth with ktoonsez kernel and im smooth without reboots with -125mV across the board.
With faux i was stable to only -100mV

GiZZy said:
Ive done some research before i started undervolting and this is the first time im hearing of such a claim.
Im running LiquidSmooth with ktoonsez kernel and im smooth without reboots with -125mV across the board.
With faux i was stable to only -100mV
Click to expand...
Click to collapse
I agree. I researched as well, and only read that overvolting(to increase performance) was the only thing to cause a chip to loose life cycle. Not performance.

my undervolt settings
Im testing out l.k. for a couple days and thought id sgare my voltages
1900mhz-1280mv
1809-1250
1728-1150
1674-1100
1512-1075
1458-1050
1350-1025
1242-1000
1134-975
1026-925
918-900
810-875
702-825
594-800
486-800
394-800
These were my voltages on ktoonsez kernal and they were completely stable.also on sio.ondemand il post later with my battery results

carhustler said:
Im testing out l.k. for a couple days and thought id sgare my voltages
1900mhz-1280mv
1809-1250
1728-1150
1674-1100
1512-1075
1458-1050
1350-1025
1242-1000
1134-975
1026-925
918-900
810-875
702-825
594-800
486-800
394-800
These were my voltages on ktoonsez kernal and they were completely stable.also on sio.ondemand il post later with my battery results
Click to expand...
Click to collapse
so far your voltages have not given me any issues....i have Trials2 the game which ill be testing in a few hours and see if i have any issues jumping in and outta the game through various tasks and let people know....as far as general use these voltages are working spiffy indeed!
after my game testing ill see if i can drop any of them lower and run the test again. but certainly digging this!
Im on Codename(Android)3.6.6 its DAMN fast rom...

elesbb said:
I lower my voltage to reduce the heat being generated. I go about 125 across the board with lean and faux kernel.
And using the stress test feature on SetCPU it goes forever without rebooting so i feel comfortable with stability.
Click to expand...
Click to collapse
I gave your settings a shot, it worked well for maybe 15 minutes? Left my phone alone for a bit, then turned my screen on again and noticed a MASSIVE amount of lag. Rebooted to get my stock voltage settings.
I'm now at -50 across the board, and seem to be pretty stable.
I've already seen some benefits from just that little UV as well.
Before the UV, I was getting ~20-25 hours on one charge. (Again, for those curious, I'm on CM10+LeanKernel.)
After UV: sitting at 61% and going on 20 hours and 19 min.
This is with Wi-Fi/GPS/sync on, auto brightness, OC at 1.67ghz.
Light-Medium usage, lots of texting, random checking of email/Facebook/instagram.
I'm definitely gonna experiment and see what my thresholds/limits are.
I'm pretty sure I can push it more.
GiZZy said:
Ive done some research before i started undervolting and this is the first time im hearing of such a claim.
Click to expand...
Click to collapse
Yeah, same here lolol
carhustler said:
Im testing out l.k. for a couple days and thought id sgare my voltages
1900mhz-1280mv
1809-1250
1728-1150
1674-1100
1512-1075
1458-1050
1350-1025
1242-1000
1134-975
1026-925
918-900
810-875
702-825
594-800
486-800
394-800
These were my voltages on ktoonsez kernal and they were completely stable.also on sio.ondemand il post later with my battery results
Click to expand...
Click to collapse
Nice man, I'll give these a shot! Thanks!
I'm contemplating making a really simple image/chart with stable under volt statistics, and their respective ROM/kernel combinations.
Sent using buttery goodness.

At the very end, my dumb ass tried adjusting my UV even lower. No idea why, I genuinely wasn't thinking though. But yeah, it crashed on me which is why it randomly drops off like that.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
-
But yeah.
41 hours on a single charge.
Wi-Fi and GPS are both on.
This is on auto brightness. This is also with lots of texting/instagram/facebook/tapatalk.
I forgot to close out of Chrome, which is why it was my main drain.
This is with me overclocking at 1.72ghz, and really light UV at -50mV across the board.
I know for a fact I can go more aggressive while still keeping it stable.

Benchmark too low on custom ROMs.

Antutu benchmark is too low on zuk z2 custom roms ???
Lineage OS with its default kernel- 56k
RR-official - 113k
Lineage OS with UBERTC Kernel - 107k
Can anyone provide fix for this problem.
Tested in antutu 6.2.7.

I don't have that problem - get around 140k on LineageOS with default kernel. Did you do a full wipe before installing?

Why do you care about benchmarks?

Did, even formatted the data but still the same problem.
But this problem is not there on officially ROM.
Does this has to do something with antutu as antutu has some benchmark loss issues.?

Can anyone fix this problem?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

is the phone really hot before you start the benchmark?
to get the best results the phone should be cold (like 30ºC or less) when you start the test. if you try to do a benchmark after another benchmark test, you'll only get worse results than the previous one due to thermal throttling. the same happens after you leave a game and try to do a benchmark.
getting less than 120k is really strange and I disagree with the guy that said "why do you care about benchmark" because getting 70k when you should be getting at least 120k shows a problem. Here on Lineage I was getting 144k with the device cold (24ºC) before the test.

Thought of that too, for that I kept the phone in fridge for some time to cool it down but still the max I could get was 114k.

https://drive.google.com/file/d/0B28Cgdz_tgfucjN4Mm0zX1ktR2s/view?usp=drivesdk
Tested when phone was idle

Did your z2 came with shoprom? If yes what rom did you flashed after shoprom?

No, I bought it from eBay.in and updated it to zui 2.3 on the same day then to zui 2.5.344 when the update was released.
On zui 2.5.344 it scores 134k.

voske15 said:
No, I bought it from eBay.in and updated it to zui 2.3 on the same day then to zui 2.5.344 when the update was released.
On zui 2.5.344 it scores 134k.
Click to expand...
Click to collapse
Did you try to go back to stock with 1.9.044 qpst/qfil no miflash or something, update to latest, unlock bootloader again etc. and then try again with benchmarks?

Since OP isn't getting the point. Benchmarks DON'T MATTER. Why do you care about scores when your phone performs as expected. By complaining like this, you are just discouraging new users

Have a look on kernel adiutor and see what frequencies your CPU is getting. Also check if battery mode is set to Balanced. If not, set it and try again.

Subhrajyoti Sen said:
Since OP isn't getting the point. Benchmarks DON'T MATTER. Why do you care about scores when your phone performs as expected. By complaining like this, you are just discouraging new users
Click to expand...
Click to collapse
Maybe because benchmarks evaluate the performance of the whole system? If he's getting less than the half of the normal score another one gets, theres something not right with his system.
Oh.. oh.. oh.. yeah please dont post if you got problems, new users could be discouraged...
If you have not contributed something useful, go out of this thread. Thanks!

Lacce said:
Maybe because benchmarks evaluate the performance of the whole system? If he's getting less than the half of the normal score another one gets, theres something not right with his system.
Oh.. oh.. oh.. yeah please dont post if you got problems, new users could be discouraged...
If you have not contributed something useful, go out of this thread. Thanks!
Click to expand...
Click to collapse
Not trying to be rude. The benchmarks are highly context dependent. They should ideally be done on a clean installation and on minimal installation. You can make some small changes while Compiling the kernel and benchmarks can be drastically changed even though actual real world performance doesn't seem to differ. And there are already too many users judging custom ROMs by the benchmarks. I've seen first hand how many users are reluctant to use kernels coz someone complained about benchmarks even though they loved the kernel later. That's all I meant. And before you think I'm a forum troll, please so check that I actually help our people and contribute to development too

Reverted back to zui 2.5.334 then benchmarked the phone, 134k. Updated the baseband(2.0.c1.9) then again did the test with same scores. After that installed the latest official RR ROM (090517) with darkmoon kernel v3 longtap then benchmarked again but still the same results.
Gonna try with official rr's stock kernel today, then will report.

Subhrajyoti Sen said:
Not trying to be rude. The benchmarks are highly context dependent. They should ideally be done on a clean installation and on minimal installation. You can make some small changes while Compiling the kernel and benchmarks can be drastically changed even though actual real world performance doesn't seem to differ. And there are already too many users judging custom ROMs by the benchmarks. I've seen first hand how many users are reluctant to use kernels coz someone complained about benchmarks even though they loved the kernel later. That's all I meant. And before you think I'm a forum troll, please so check that I actually help our people and contribute to development too
Click to expand...
Click to collapse
No offence, these were only clear words for your post which help the threadstarter in no case. In first post he said 56k on lineage with default kernel and that's not normal.
Yes, he could do something wrong. But he open the thread to find a solution or whats the mistake of this low benchmarks.
I think everyone would worry about if he gets 56k and others >140k. Wouldnt you think that theres something wrong with your phone?
So help find the error/mistake but with "live with that" you do not
---------- Post added at 05:51 PM ---------- Previous post was at 05:49 PM ----------
voske15 said:
Reverted back to zui 2.5.334 then benchmarked the phone, 134k. Updated the baseband(2.0.c1.9) then again did the test with same scores. After that installed the latest official RR ROM (090517) with darkmoon kernel v3 longtap then benchmarked again but still the same results.
Gonna try with official rr's stock kernel today, then will report.
Click to expand...
Click to collapse
You reverted with qpst/qfil? Changing between custom roms with twrp is no solution qpst/qfil gets deeper into firmware.

Can anyone provide ZUI 2.5.334 qpst/qfile link?

voske15 said:
Reverted back to zui 2.5.334 then benchmarked the phone, 134k. Updated the baseband(2.0.c1.9) then again did the test with same scores. After that installed the latest official RR ROM (090517) with darkmoon kernel v3 longtap then benchmarked again but still the same results.
Gonna try with official rr's stock kernel today, then will report.
Click to expand...
Click to collapse
134K is perfectly normal. That's how much I was getting on RR with stock clocks. OC I'm getting 154K. Also darkmoon v3 is a very good kernel. Tested it with no problems. Remember that a clean flash is always best.

Not on official RR, only 113k with darkmoon kernel