Basically... does an overclocked kernel help flash frame rates?
psufan5 said:
Basically... does an overclocked kernel help flash frame rates?
Click to expand...
Click to collapse
Yes, I think so. I am on GB's kernel. When its at its default 1280, in Quadrant last test, I see frame rates at 50+. But when capped at 1000, I see frame rates around 40.
diablo009 said:
Yes, I think so. I am on GB's kernel. When its at its default 1280, in Quadrant last test, I see frame rates at 50+. But when capped at 1000, I see frame rates around 40.
Click to expand...
Click to collapse
But thats 3D graphics rendering, flash isnt 3D.
psufan5 said:
But thats 3D graphics rendering, flash isnt 3D.
Click to expand...
Click to collapse
I would apply the same, though not accurate. And relating the same to computers, faster computers support better flash graphics.
Related
Recently, I have seen the undervolted kernel for Nexus One which makes the battery spell longer.
Can anyone modify it for G1?
http://forum.xda-developers.com/showthread.php?t=634587
Look on the app market, dude. There are like 5 apps\widgets to do that EXACT same thing. Nothing has to be ported.
zimphishmonger said:
Look on the app market, dude. There are like 5 apps\widgets to do that EXACT same thing. Nothing has to be ported.
Click to expand...
Click to collapse
They actually don't do the exact same thing... My kernel is undervolted, not underclocked. Theres a difference. Undervolted uses less power at the same speeds, underclocked just drops the clockspeed.
interesting
This is interesting... I'd like to see this happen
EDIT: Forget it...
persiansown said:
They actually don't do the exact same thing... My kernel is undervolted, not underclocked. Theres a difference. Undervolted uses less power at the same speeds, underclocked just drops the clockspeed.
Click to expand...
Click to collapse
So you have one for cliq now or dream?
Ace42 said:
So you have one for cliq now or dream?
Click to expand...
Click to collapse
The one he linked for the Nexus is the one I made.
I don't think its possible for the G1/MT3g/CLIQ unfortunately.
persiansown said:
The one he linked for the Nexus is the one I made.
I don't think its possible for the G1/MT3g/CLIQ unfortunately.
Click to expand...
Click to collapse
In other words all 72XX lack this ability correct?
But the new Armv7 should be capable like the Droid,legend,devour,etc.
You can lower the vdd for 528MHz, but the next jump down makes it so low that the phone would immediately crash.
coolbho3000 said:
You can lower the vdd for 528MHz, but the next jump down makes it so low that the phone would immediately crash.
Click to expand...
Click to collapse
So we can lower it but not up it for the overclock?
Also, can we lower it at the lower speeds? (I have mine set up to underclock when the battery is low, when the screen is off, etc. so a lower VDD (if stable) would be great.
coolbho3000 said:
You can lower the vdd for 528MHz, but the next jump down makes it so low that the phone would immediately crash.
Click to expand...
Click to collapse
How feasible is it to underclock the phone even further than the 128 MHz?
personaly , i dont see a huge advantage to underclocking past what we got now, undervolting.... nah,
@ sleep mine atleast has virtualy no background processes.
and even on a heavy use day, cell standby shows up as my largest drain.
you want much better battery life, id say look into hacking the radio on it.
What I have here is a VERY BETA kernel built from the latest LeeDrOiD git with some ondemand tweaks to make it a bit more responsive, as well as AXI Scaling, an undervolted bottom end at 122mhz, and with a topend of 2016mhz.
Many phones may not run at the full upper-end, but vddsys is implemented as in the LeeDrOiD kernel, so you may increase or lower the VDD by 25 for 20160000mhz to attempt to get it working.
Currently working on getting a github page up with this source. I'm running it on the Unity rom at the moment without issue. 2016mhz should only be used for benchmarks, and not 24/7.
Two way call recording is also included, as well as a startup script to run at 1843mhz ondemand at startup.
Changelog:
June24-Initial Release...Working on Cleanup.
GitHub Page: https://github.com/synergydev
Will work on marking changes shortly. It should also be of note that because my GF's phone seems stable at [email protected], I changed the voltage at 2016 to 1.5 on the git just because it seems my phone likes high voltages.
I've tried 2000 a long time ago on my kernel, but my dhd couldn't handle it. and it handle very very low voltages, so didn't want to release a kernel with the freq that doesn't even work on dev's DHD I've even removed 1980mhz from my kernel because there really isn't any use of that freq rather than frying your DHD
I think that BuzzBumbleBee had 2000 on his kernel once, don't remember right
Good job BTW
edit:
wht is a working voltage on 2000?
I've trid up to 1.5V and it was unstable
LorD ClockaN said:
I've tried 2000 a long time ago on my kernel, but my dhd couldn't handle it. and it handle very very low voltages, so didn't want to release a kernel with the freq that doesn't even work on dev's DHD I've even removed 1980mhz from my kernel because there really isn't any use of that freq rather than frying your DHD
I think that BuzzBumbleBee had 2000 on his kernel once, don't remember right
Good job BTW
edit:
wht is a working voltage on 2000?
I've trid up to 1.5V and it was unstable
Click to expand...
Click to collapse
I'm using 1.525V at 2016, however my DHD could never run the 1.9986 in your kernel without a voltage bump (could undervolt all the way up to 1.8 however though). In this kernel, I needed to up the AXI clock at 2016 to even get it to run, let alone benchmark continuously. I still haven't been able to get it to scale with a minimum under 300mhz.
This is why I recommend reducing the VDD at that speed by 25 if anyone's DHD can't run it.
In response to the first section, I only released this because I'm an enthusiast overclocker when it comes to my desktops (water chilled and vapour phase change cooled), and I wanted my clock to read the magical "2" at the beginning for bragging rights. With AXI clock scaling, we should be able to get slightly better battery life as well at the lower clocks (at least on the N1 it seems they were able to get better battery life with it).
synergye said:
In response to the first section, I only released this because I'm an enthusiast overclocker when it comes to my desktops (water chilled and vapour phase change cooled), and I wanted my clock to read the magical "2" at the beginning for bragging rights. With AXI clock scaling, we should be able to get slightly better battery life as well at the lower clocks (at least on the N1 it seems they were able to get better battery life with it).
Click to expand...
Click to collapse
+1 on that, but don't think you're more enthusiastic when talking about OC
We can argue about that the whole day
looking forward for your git!
I think 1.2G is enough..
@LorD ClockaN: if that's an sense kernel, you know what you have to do
Your 2016 MHz ASOP kernel coming soon?
with friendly greet
starbase64
You will find the 1.8GHz+ frequencies being only theoretical, with no increase in performance with respect to a "speed bump".
I have tested that a few months ago, going as high as 2.2GHz.
The maximum "real" performance boosts only go up to 1.5GHz (I clock my kernels to 1.497GHz).
Run a smartbench, and the results will speak for themselves.
Unless you want to fry your DHD?
Tryng with virtuous sense 3 and it makes lag the sense but for the rest is quiet good
Edit: after some time the lags disappears and all is perfect now
where source code?
u canT post kernels on XDA without source code
m-deejay said:
where source code?
u canT post kernels on XDA without source code
Click to expand...
Click to collapse
He said he's working on the github page to up his source soon.So I think it's already in progress.
Good job by the way mate.Never liked the fact that kernels with the vdd interface restrict us to 1500mV!
m-deejay said:
where source code?
u canT post kernels on XDA without source code
Click to expand...
Click to collapse
What do you need it for?
Just add frequencies in multiples of 19200 to arch/arm/mach-msm/acpuclock-7x30.c
If the newly added frequency locks, add the next multiple and/or up the voltage.
No magic there.
tolis626 said:
He said he's working on the github page to up his source soon.So I think it's already in progress.
Good job by the way mate.Never liked the fact that kernels with the vdd interface restrict us to 1500mV!
Click to expand...
Click to collapse
Mine has voltage till 1.525 via vdd
Sent from Desire HD with CyanogenLordMod!!!
adwinp said:
What do you need it for?
Just add frequencies in multiples of 19200 to arch/arm/mach-msm/acpuclock-7x30.c
If the newly added frequency locks, add the next multiple and/or up the voltage.
No magic there.
Click to expand...
Click to collapse
really?
lol
Why do you explain to me?
m-deejay said:
really?
lol
Why do you explain to me?
Click to expand...
Click to collapse
Oohoo... Dev fight!! LOL
Sent from Desire HD with CyanogenLordMod!!!
wiped devik cache and flashed it to my honeysense rom and tha **** froze on startup lol any tips??
Lizzo said:
wiped devik cache and flashed it to my honeysense rom and tha **** froze on startup lol any tips??
Click to expand...
Click to collapse
Raise min freq to higher[around 1.1GHz+] to prevent voltage spikes which might be causing the freezes, try decrease the distance b/t the 2GHz and the min.
Ace42 said:
Raise min freq to higher[around 1.1GHz+] to prevent voltage spikes which might be causing the freezes, try decrease the distance b/t the 2GHz and the min.
Click to expand...
Click to collapse
uuuggghhhh... how do i raise the min b4 startup?
Lizzo said:
uuuggghhhh... how do i raise the min b4 startup?
Click to expand...
Click to collapse
echo 806400 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
On adb you have to change the min freq while booting up. 800 might work. Or use 1305600 [1.3GHz].
This is madness, yes i know people will post no this is sparta, but seriously, anything over 2ghz i personally wouldn't test
adwinp said:
You will find the 1.8GHz+ frequencies being only theoretical, with no increase in performance with respect to a "speed bump".
I have tested that a few months ago, going as high as 2.2GHz.
The maximum "real" performance boosts only go up to 1.5GHz (I clock my kernels to 1.497GHz).
Run a smartbench, and the results will speak for themselves.
Unless you want to fry your DHD?
Click to expand...
Click to collapse
PMSL Benchmarks mean fuk all tbh do not reflect real world peformance running at 1.8/1.9ghz stuff like Playstation emulator etc run far much smoother and with no slowdowns etc... newbs and benchmarks lol!
Hi
when i run Quadrant on my new One S i only score about 3500, but when i look at reviews they score about 5000? how much do you get?
Edit: Ok i did a restart and now i get 4800 istead.. strange it had such a big impact on the score
This can be because of background processes.
just tried quadrant on my device and got this nice result :
noble8 said:
This can be because of background processes.
Click to expand...
Click to collapse
Well on my first run before the restart i only scored 3000 then i closed all the apps i had running and tried again resulting in 3500.
svejstrup said:
Well on my first run before the restart i only scored 3000 then i closed all the apps i had running and tried again resulting in 3500.
Click to expand...
Click to collapse
thats strange i got my score without closing apps
and just another strange thing, quadrant says that my phone contains the msm8960 chipset.. but the one s is supposed to have the MSM8260A right?
wayne850 said:
just tried quadrant on my device and got this nice result :
Click to expand...
Click to collapse
WOW that's fantastic!
Can you guys try vellamo? I am interested to see how much it gets in the sunspider and ocean flinger tests.
There you go
/edit: And btw, there is my Quadrant score, if anyone wants to compare.
nativestranger said:
Can you guys try vellamo? I am interested to see how much it gets in the sunspider and ocean flinger tests.
Click to expand...
Click to collapse
Sunspider vallamo ~1500, Sunspider browser~1700, flinger tests are all maxed out at 60 fps with 0 framedrops
Quadrant reports 5022 for me, 2410 for velamo (overall score)
svejstrup said:
and just another strange thing, quadrant says that my phone contains the msm8960 chipset.. but the one s is supposed to have the MSM8260A right?
Click to expand...
Click to collapse
Same here. Yeap, that's odd... maybe because they are in the same series? Who knows
donverse said:
There you go
/edit: And btw, there is my Quadrant score, if anyone wants to compare.
Click to expand...
Click to collapse
svejstrup said:
Sunspider vallamo ~1500, Sunspider browser~1700, flinger tests are all maxed out at 60 fps with 0 framedrops
Click to expand...
Click to collapse
Thanks. Is it possible to playback 1080p flash videos smoothly on youtube desktop webpage?
Quadrant is nerfed and isn't 100% correct.
Okay so, my tf700 is running CleanRom 2.5.5 Inheritance with the over clocked kernal
and i keep getting scores around 6000 and under
while in performance mode
am i doing something wrong
Tyler27 said:
Okay so, my tf700 is running CleanRom 2.5.5 Inheritance with the over clocked kernal
and i keep getting scores around 6000 and under
while in performance mode
am i doing something wrong
Click to expand...
Click to collapse
Do you have gpu 2D rendering turned on?
Found under settings/developer options...
Thats OK said:
Do you have gpu 2D rendering turned on?
Found under settings/developer options...
Click to expand...
Click to collapse
i enabled it and disabled it
score went up to 6200
now dropped back to 5600
Any other ideas?
Tyler27 said:
Any other ideas?
Click to expand...
Click to collapse
No idea. Have you tried taking a TBU and (maybe even clean) install 2.6 and 2.6.1 (patch over 2.6)?
PS: what mods did you choose? And how much did you manage to get when in Performance Mode?
Low score... it used to be pretty damn high for the TF700T... times change, I guess
Don't let the benchmarks bother you, tbh.
Tyler27 said:
Any other ideas?
Click to expand...
Click to collapse
Where do you want to be with benchmarks?
Are you wanting high numbers or are you good with smooth stable UE?
its well documented, quadrant can be fooled, you can have a custom rom thats built specifically for quadrant and it will bench much higher than other roms but in real use its much slower. Go for smooth and stable. Basically, just use your tablet and if you like where its at dont complain, quadrant is just a number, theres no FEELING behind it. Higher number does not always mean better experience.
6200 with force GPU rendering on is great! How does it feel to use?
Thanks for the responses guys
I was thinking if i wipe it completely and do a clean install it would be better, sounds like a good idea anyway
i was comparing my scores to what everyone else was saying and what it showed in the thread for that rom
i always ran quadrant in performance mode and made sure i had more than 400mb free of ram
i stayed with some default setting on the DPI and launcher, but i chose clemsyns kernal with the GPU at 700
and i left fsync enabled
Some people said it hit 7000
if it doesn't matter i wont worry about it
but i will say my tablet is much quicker then before, i have a few hiccups that i believe are caused by some apps
is it possible that apps in the background can cause the low scores?
Clemsyn's kernels have the GPU OC'ed to 650
Is this "safe"? 50% OC? What is unsafe for GPU OC? I cannot find any documentation on this subject.
Ti2 said:
Clemsyn's kernels have the GPU OC'ed to 650
Is this "safe"? 50% OC? What is unsafe for GPU OC? I cannot find any documentation on this subject.
Click to expand...
Click to collapse
Yeah, I think it's completely safe I use Clemsyn's 1.8ghz OC kernel on mine with CleanRom 3.2.2 and I love it. It is a less than 50% because stock is 416mhz so a 50% increase I would consider unsafe. The 650mhz is the highest I would go because I think any higher would be breaking that "safe barrier".
lightitwithfire said:
Yeah, I think it's completely safe I use Clemsyn's 1.8ghz OC kernel on mine with CleanRom 3.2.2 and I love it. It is a less than 50% because stock is 416mhz so a 50% increase I would consider unsafe. The 650mhz is the highest I would go because I think any higher would be breaking that "safe barrier".
Click to expand...
Click to collapse
Cheers. Although 150% of 416 = 624
Is that your opinion by the way? Or can you back that up - or point me to some documentation on the matter?
Thanks
Ti2 said:
Cheers. Although 150% of 416 = 624
Is that your opinion by the way? Or can you back that up - or point me to some documentation on the matter?
Thanks
Click to expand...
Click to collapse
Lol sorry, not the brightest when it comes to math!
Also, yes it is my opinion. I'm 80% sure that you will NOT find any documentation concering whats safe and what isnt. It's all up to the users discression.