Hi all
I just want to ask
Can someone please OC matrix v12 for
Me
Cpu to 1.8 GHz
Gpu to 5xx MHz
(please don't ask why.... If don't want to help then goodbye)
A) us neo kernel it's based of matr1x and allows overclocking to 1.7 GHz previously it would let you go up to 2ghz. B) The nexus 4 gpu hasn't been successfully overclocked past 487mhz yet, there was a 533mhz overclock but it didn't work and gave the same performance as 487
Sent from my Nexus 4 using xda premium
THEBANDIT420 said:
A) us neo kernel it's based of matr1x and allows overclocking to 1.7 GHz previously it would let you go up to 2ghz. B) The nexus 4 gpu hasn't been successfully overclocked past 487mhz yet, there was a 533mhz overclock but it didn't work and gave the same performance as 487
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Neo development had stopped
And it doesn't support kk
(it can work but with lots of problems)
Related
-0.25mv / 1500Mhz gives more quadranet vs stock 1400 mhz and stock voltage
how healthy to keep it this way? any risk go up to 1600Mhz?
on last Omega JB rom i went from 4000 to 5130 in quadrant using this OC.
Thanks!
Of course higher clocks gives vigher benchmarks. Uv doesn't affect unless you uv to the point that voltage can't keep cpu stable.
Sent from my GT-I9300 using xda app-developers app
johku12 said:
Of course higher clocks gives vigher benchmarks. Uv doesn't affect unless you uv to the point that voltage can't keep cpu stable.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
The question: 1500-1600 levels risky to CPU ?
UV lower is good to keep temp lower...
From my experience, undervolting offers no benefits at all. Temperature remains the same and battery seems to be worse when idling.
with no overclocking and with stock 4.1.1 li7 i have 6300 scores in Quadrant..... with overclocking to 1600 mhz i reached 6700... no sense to overclock it
Sent from my GT-I9300 using xda premium
myname70 said:
with no overclocking and with stock 4.1.1 li7 i have 6300 scores in Quadrant..... with overclocking to 1600 mhz i reached 6700... no sense to overclock it
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Which rom you use ?
+1
Learning time!
-UV provides stability, its not to save battery. Its such a miniscule amount of volatge it wont mess up battery life, but it will help stability of the CPU...
-And when you OC, you need to undertand that it doesnt stay at the max speed on all four cores all the time. It changes to fit the needs of the user.
I think the CPU can reach 2.0GHz easily, i mean my single core Captivate with a Hummingbird 1.0GHz ARM cortex-A8 could reach 1.92GHz and stay stable with -50mV UV.
Sent from my GT-I9300 using xda premium
I wont oc.. it screwed battery on my galaxy tab...
Sent from my GT-I9300 using xda premium
If defy can be OC to 1.1~1.3 GHz from 800 mhz then y can't defy plus be OC to 1.4~1.6 GHz from 1GHz ? Since defy+ has better chip set than defy though CPU n gpu used remains same ...
Sent from my MB526 using xda app-developers app
Hi, 1200mhz vsl60 is enough. Or you want kill the lifetime of your cpu and over this the battery drain empty before the handy is on.
Sent from my MB526 using xda premium
Defy and Defy+ have the same CPU but different kernel (which is software). The kernel limits the clock. Defy+ stock gingerbread kernel adds Clk4 and Vsel4 which are 1 GHz and 58 Vsel by default. I have a Defy+ overclocked to 1.2 GHz Vsel 60. The clock is limited by the kernel and Vsel by the hardware. My hardware at 1.2 GHz is stable at 60 Vsel, yours may be stable at 58 or 62. I know some people OC their Defy at 1.4 GHz but they set a dangerous Vsel to be stable (70 and above). 1.2 GHz is enough.
Sent from my flying overclocked Motorola Defy+ MB526 with CyanogenMod 10 and custom kernel using XDA app
nastys said:
Defy and Defy+ have the same CPU but different kernel (which is software). The kernel limits the clock. Defy+ stock gingerbread kernel adds Clk4 and Vsel4 which are 1 GHz and 58 Vsel by default. I have a Defy+ overclocked to 1.2 GHz Vsel 60. The clock is limited by the kernel and Vsel by the hardware. My hardware at 1.2 GHz is stable at 60 Vsel, yours may be stable at 58 or 62. I know some people OC their Defy at 1.4 GHz but they set a dangerous Vsel to be stable (70 and above). 1.2 GHz is enough.
Sent from my flying overclocked Motorola Defy+ MB526 with CyanogenMod 10 and custom kernel using XDA app
Click to expand...
Click to collapse
Haven't u tried over clicking at 1.4ghz ? coz some say we find optimum vsel will be 68 n anything less than this would be stable ?
Sent from my MB526 using xda app-developers app
Its blocks ma defy + ...go for 1.2
Sent from my MB526 using xda premium
suhasgudmi said:
Haven't u tried over clicking at 1.4ghz ? coz some say we find optimum vsel will be 68 n anything less than this would be stable ?
Sent from my MB526 using xda app-developers app
Click to expand...
Click to collapse
You can try it yourself. The max I've gone to is 1300 MHz/ 68 vsel... battery heat was very high at 68... many others have also tried, and get the same result as I did.
But as they say, experience is the best teacher, so you're welcome to try it out yourself, and let us know.
krushnam said:
You can try it yourself. The max I've gone to is 1300 MHz/ 68 vsel... battery heat was very high at 68... many others have also tried, and get the same result as I did.
But as they say, experience is the best teacher, so you're welcome to try it out yourself, and let us know.
Click to expand...
Click to collapse
So u ve over clocked to 1.4 GHz o reduced to 1.3 GHz ? I really don't understand y defy+ can't be OC more whereas defy can be as it can also reach 1.2~1.3 GHz ...... buying defy would ve been better I guess .....
Sent from my MB526 using xda app-developers app
suhasgudmi said:
So u ve over clocked to 1.4 GHz o reduced to 1.3 GHz ? I really don't understand y defy+ can't be OC more whereas defy can be as it can also reach 1.2~1.3 GHz ...... buying defy would ve been better I guess .....
Sent from my MB526 using xda app-developers app
Click to expand...
Click to collapse
are you really telling me that you find a difference in 1.2 ghz and 1.4 ghz, while you're using your phone? all you're doing is encouraging battery drain and more wear and tear on your cpu..
syllogyking said:
are you really telling me that you find a difference in 1.2 ghz and 1.4 ghz, while you're using your phone? all you're doing is encouraging battery drain and more wear and tear on your cpu..
Click to expand...
Click to collapse
Ofcourse there is a huge difference betwn 1.2 n 1.4 GHz.........its all about processing speed which matters for smartfone users ...... Y would there be 3 ~4k rs difference for an 800 mhz n 1GHz cell phones?
Sent from my MB526 using xda app-developers app
Defy and Defy+ have the SAME CPU, but Defy+ is clocked at 1.0 GHz by default.
Cost difference is also for bigger battery and better camera
Sent from my MB526 using xda premium
I just got my nexus 7 five days ago and before I got it I say it was 1200mhz but when I got it rooted it set it up things in setcpu it says 1300mhz(stock ROM stock kernel) but it doesn't actually work at 1300mhz only 1200. So is it 1300mhz or 1200mhz and if it is 1200mhz is it supposed to be able to go to 1300mhz?
Sent from my Nexus 7 using xda app-developers app
AZA5 said:
I just got my nexus 7 five days ago and before I got it I say it was 1200mhz but when I got it rooted it set it up things in setcpu it says 1300mhz(stock ROM stock kernel) but it doesn't actually work at 1300mhz only 1200. So is it 1300mhz or 1200mhz and if it is 1200mhz is it supposed to be able to go to 1300mhz?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
The Tegra 3 T30L in the Nexus has this info on Wikipedia:
1.2 GHz Quad-core ARM Cortex-A9 (up to 1.3 GHz in single-core mode)
Click to expand...
Click to collapse
So I assume that's why it is getting reported as 1.3GHz.
Hello
my nexus 7 is a bit laggy on games
dead trigger is a little laggy on high settings and ultra high is quite laggy too
my GPU is at 512mhz
and cpu and 1600mhz
is there any kernel with higher OC to 4.2.2?
M-kernel has the capability to oc to 1.7 GHz. But why do you need that then? It'll need a high voltage bump to oc to 1.7 GHz and might get overheating.
Sent from my Nexus 7 using xda app-developers app
And you will barely feel any difference .
Hearmeman said:
Hello
my nexus 7 is a bit laggy on games
dead trigger is a little laggy on high settings and ultra high is quite laggy too
my GPU is at 512mhz
and cpu and 1600mhz
is there any kernel with higher OC to 4.2.2?
Click to expand...
Click to collapse
Dont play it on high.
Sent from my EVO using xda app-developers app
don't think of oc like a thing who delete the games lags.most games lags due to the non-optimized compiling of it,like some gameloft games,there isn't any differences at 1.7 or 1.9 playing games.do a bit of gpu oc and you are good,but repeat you can't delete the lags.the best thing it's the fact of using tegra3 optimized games,they works a little best than others
How high can you over clock your phone? Like is there a limit to it. I know our nexus 4 is clocked at 1.5ghz but is our processor bigger?
Sent from my Nexus 4 using xda app-developers app
Our processor is huuuuuuuge!!!!!
Sent from my Nexus 4 using xda app-developers app
you can overclock it how ever you want, if you build it into the kernel. the real question is how much can your device handle. some can oc to 1836mhz, even less to 1944mhz.
Highest OC I have seen (and tried) was 1.9 GHz. Even then, if more than 2 cores enable at that clock, the phone crashes and does the red light. IMO you don't need to OC the Nexus 4 anyway
Sent from my Nexus 4
lopezk38 said:
Highest OC I have seen (and tried) was 1.9 GHz. Even then, if more than 2 cores enable at that clock, the phone crashes and does the red light. IMO you don't need to OC the Nexus 4 anyway
Sent from my Nexus 4
Click to expand...
Click to collapse
What's the red light?
Sent from my Nexus 4 using xda app-developers app
lopezk38 said:
Highest OC I have seen (and tried) was 1.9 GHz. Even then, if more than 2 cores enable at that clock, the phone crashes and does the red light. IMO you don't need to OC the Nexus 4 anyway
Sent from my Nexus 4
Click to expand...
Click to collapse
Weird. I used faux's kernel to OC up to 1.9 ghz "just for fun". Even made an antutu benchmark. Nothing crashed.
abaaaabbbb63 said:
Weird. I used faux's kernel to OC up to 1.9 ghz "just for fun". Even made an antutu benchmark. Nothing crashed.
Click to expand...
Click to collapse
not a "real" 1.9ghz, the rest of the reply im sending you via pm