Question....what is the fastest anybody has been able to overclock, without boot-looping? I know there are a lot of variables involved, but I was just curious. I managed to get 1280mhz out if it, but, not really sure if I can push it higher.
Sent from my MB865 using xda app-developers app
I'm running at 1.25GHz stable with additional ram speed and net speed tweaks, along with a few select build.prop tweaks. Any higher and I get freezes and/or random reboots. It seems to vary from device to device, as some users have been reported to run as high as 1.3GHz or slightly higher, while others have issues running at 1.2GHz or even lower..
Edit: If you'll notice, I've also underclocked to 240MHz which is probably a good idea when running the CPU at 'mot_hotplug' or 'ondemand' settings other than 'performance' so that gives the CPU a lower frequency scale to fall back to, when not running at the full frequency scaling.
{
"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"
}
Sent from my MB865 using xda premium
Thanks....I have it @ 1300 mhz now, with no problems showing up, so far, but I'm going to scale it back to 1150, and underclock it too, dont need it that high for everyday use. I just wanted to see how far I could go.Thanks for the input.
Sent from my MB865 using xda app-developers app
Related
What should be "normal" for Desire? I constantly get around 2000+ with no overclock. On my former Legend oced to 806 Mhz I was hardly getting 1400. I know the processor is better in Desire S but still the difference is big. Could be a bug with Quadrant?
Using CM 7.1 stable, interactive governor, 1024 mhz, standard CM kernel
{
"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"
}
Sent from nowhere over the air...
That's good you should be happy with a higher score... Whats wrong with that
Sent from my HTC Desire S using xda premium
I am happy...there's no doubt about that. I was just wondering if these are the usual values for Desire since in the Legend section there was such a topic with benchmark results and here I couldn't find any.
If values are not resulting from a bug of Quadrant and are correct, it's great. I was just surprised by the difference that's all and wanted to compare the results with other's. I don't see now any reason for which I should overclock the Desire S. Maybe ICS will demand more power, but I think has enough for now. Everything works smooth and fast, no lag, temp does not raise above 35-37 degrees...it's great
Sent from nowhere, over the air...
Yep, no need to OC
Those results are normal for AOSP ROMs, (like cm7)
Sent from my HTC Desire S using xda premium
Hi folks ... I'm havig a problem with the cpu running at 100% alot of the time ... i cnt seem to figure out whats causing it
I was running Prime OC kernel and setcpu running it at 1200 ... thought it might be Setcpu, so uninstalled that ... rebooted and CPU spy shows it still using cpu at full. Installed blades kernel and it shot up to 1504 full CPU usage (even though i flashed the 1.2 default)
Flashed the stock kernel and its now sitting at 100% 1000 !!!!
Unless cpu spy is showing me false results i dont know what i've changed or installed for it to suddenly start doing this .... Head scratching moment ...
Advice welcome
{
"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"
}
P.S. screenie is when i was on prime OC kernel
Have you tired re-flashing your kernal and rom?
Tried 3 kernels ....
I think its due to cpu spy though thankfully... running a cpu load widget now and its results are alot more pleasing to the eye
Cpu spy must have been updated recently i suppose and for some reason its knockedthe results askew.
{
"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 this just me, or is this unusual? I find it hard to believe it can UV -200mv... It's running perfectly stable...
-200mv
-125mv(216mhz) If I undervolt it to -130mv(216mhz) i get sod prob 25% of the time..
Using Kang 7.2.0 12/21 rom
Trinity Kernel 1.56ghz
I just did the same....so far so good
Sent from my LG-P999 using XDA App
Smallsmx3 said:
I just did the same....so far so good
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
I thought my setcpu was glitching. :/
If anyone have the faux kernel, can they post the stock voltage for it?
Edit: seems like I have to use -195mv insteaed of -200mv.. For some strange reason I keep freezing, and getting sod once my battery is below 30%..
Didn't think it could be stable that know thanks! Did this for dragon kernel 1.5.2 and all is well.
My battery drops 2-3% for every 8houf using this undervolh and using screen off profile to limit it to 216mhz.
Different phones have different stability with UV, mine doesn't handle faux kernel too well. I believe his UV kernel is pre-adjusted to -50 across the board.
I was looking at the glitch kernel thread and saw that the max UV for the kernel was -200 for 200mhz, and around -50 for 1Ghz.
Well I'm managing almost -200 for all of the speeds and I haven't faced any issues so far. What's going on? Is my phone not actually undervolted?
Here's a screenshot...
{
"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"
}
(sorry for the horrible image quality).
Silencer96 said:
I was looking at the glitch kernel thread and saw that the max UV for the kernel was -200 for 200mhz, and around -50 for 1Ghz.
Well I'm managing almost -200 for all of the speeds and I haven't faced any issues so far. What's going on? Is my phone not actually undervolted?
Here's a screenshot...
(sorry for the horrible image quality).
Click to expand...
Click to collapse
Undervolting increase battery life at the cost of some performance loss, especially when multitasking
ROMMaker said:
Undervolting increase battery life at the cost of some performance loss, especially when multitasking
Click to expand...
Click to collapse
No -_- it doesn't.
Sent from my SAMSUNG-SGH-I897 using xda premium
Hi.
I've got a Sony Xperia XZ2 recently and this is my first device with built in EAS on 4.9 Kernel and SDM845.
Through testing I found out that if you load more than 7 threads the Thermal Throttling switches from Frequency reducing to current reduction. Meaning all cores stay at max frequency (1700 small, 2800big) but the device only uses 4W instead of 8W.
As seen here...
{
"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"
}
So I've done some more testing... https://forum.xda-developers.com/showpost.php?p=76709836&postcount=6
About task migration, and then some about CPU throttling on a cold device
https://forum.xda-developers.com/showpost.php?p=76719608&postcount=7
(Scroll down to about CPU testing)
Turns out that as soon as the SoC reaches 68°C a current throttling is happening which does NOT affect CPU frequency.
Now then... Anyone knows who the OP6 is handling throttling?
Is what I'm seeing a Sony specific method or the new way EAS is limiting Load to reduce Thermal strain?
You are everywhere my man,
Hope someone more knowledgeable than I can help you. If not, then I would be happy to help if you guide me through.
Sent from my OnePlus6 using XDA Labs