Just got my Note
Want to overclock it badly...had my previous HD2 running at 1.5 and it never had a problem occasionally it would overheat and auto reboot but not often...
How fast have people gotten it up to and what seems to be the safe zones? I found that at 1.35 on the HD2 wouldnt overheat no matter what you thru at it....
Have we found any sweet spot overclock speeds yet?
i have seen in many post. its 1700Mhz..
Dear TopOfNewYork,
We have two kernels for overclock; FM Kernel v1.6 and AbyssNote Kernel v3.0... I prefer AbyssNote since it has much more features and updated often...
For both kernels, 3 choices of overclock speed 1600,1664 and 1704...
I use 1600 @ 1300mV daily and heat can reach up to 50c while charging and playing demanding games... On normal use it is around 36c. @1300 mV my cpu is stable...
I dont use 1664 and 1704 since there will be more heat and instability...
For me, the best is using stock clock speed undervolted 1400 @ 1175 mV. Phone doesnt get hot and performance is still impressive...
Kind regards,
Sent from my GT-N7000 using xda premium
that temp speed balance sounds perfect PROTO I used to try to keep my hd2 under 49C what do you think of going with the highest clock speeds and just setting profiles and governors based on temp and battery levels w setcpu?
or will I still experience instability simply by using the higher clocked kernels, I think no but I dont have that much kernel knowledge when it comes to setting the speeds in the kernel itself, i usually leave that up to experienced & trusted chefs
Dear TopOfNewYork,
I dont use profiles since they can cause deep sleep issues( screen off profile i mean )... I overclock with Voltage Control app...
Phone reaches around 50 c while charging and playing demanding games at the same time @1600 Mhz so overclocking to 1600 can be the best choice when not charging and 1400mhz is best for charging... If u use SetCpu app, u can use charging profile and set the clock to 200-1400 Mhz...
I also did 1664 and 1704 with various voltages but got some stability issues so i revert back to 200-1600 as my default...
Here is my voltage settings:
Rom: 4lph4 n3v3r d135 v1.2.2 http://forum.xda-developers.com/showthread.php?t=1424401
Kernel: AbyssNote v3.0 Final http://forum.xda-developers.com/showthread.php?t=1362424
100 ( dont use - makes phone wake-up slow )
200 - 825 mV
500 - 825 mV
800 - 925 mV
1000 - 1000 mV
1200 - 1075 mV
1400 - 1175 mV
1600 - 1300 mV
1664 ( dont use - stability issues )
1704 ( dont use - stability issues )
These are my numbers that my cpu can do... Values may vary phone to phone , cpu to cpu so it is better to test and find the best value for your phone... Hope these helps...
Kind Regards,
is that a commadore logo avatar! wow sick havent seen that in ages but i like it
I can remember getting a "sprite" to bounce around on the 64 as a pup wonderful day
anyway
good post proto...really helpful, and thanks for the links definitely going to try your load out sounds like you tested it properly will let you know if I find any interesting tweaks
TopOfNewYork said:
is that a commadore logo avatar! wow sick havent seen that in ages but i like it
I can remember getting a "sprite" to bounce around on the 64 as a pup wonderful day
anyway
good post proto...really helpful, and thanks for the links definitely going to try your load out sounds like you tested it properly will let you know if I find any interesting tweaks
Click to expand...
Click to collapse
Dear TopOfNewYork,
Commodore; the soul changed my life... Amiga, my forever girlfriend... Memories... Golden age of computing.... And YESSSS we are getting older...
Kind Regards,
and here i thought that when my phone reaches 50 degrees, it is in overheat mode.
nice to know that such temperatures are well within normal expectations when doing heavy tasks.
Hasseno said:
and here i thought that when my phone reaches 50 degrees, it is in overheat mode.
nice to know that such temperatures are well within normal expectations when doing heavy tasks.
Click to expand...
Click to collapse
Dear Hasseno,
I dont advice to run device long time when it reaches over 50c... I guess around 50c-55c is a little bit risky...
Kind Regards,
Hasseno said:
and here i thought that when my phone reaches 50 degrees, it is in overheat mode.
nice to know that such temperatures are well within normal expectations when doing heavy tasks.
Click to expand...
Click to collapse
I have a profile active that it gives me a warning when it reaches 50, and it will downclock too.
PROTOCHIP,
How do you test stability with 1.4Ghz @ 1175mV?
EDIT:
I tried 1.6Ghz @ 1300mV the phone is just too hot to hold
EarlZ said:
PROTOCHIP,
How do you test stability with 1.4Ghz @ 1175mV?
EDIT:
I tried 1.6Ghz @ 1300mV the phone is just too hot to hold
Click to expand...
Click to collapse
Dear EarlqZ,
To Test Stability:
1- Run 3 times "Antutu Benchmark"
2- Run 3 Times "NeoCore Benchmark"
3- Run 3 times "Nenamark1"
4- Run 3 times "Quadrant Standart"
5- Run 30 minutes "StabilityTest"
6- Play 10 minutes of 1080p TS and MKV movies in SW mode with bsplayer or mxplayer
If all these tests passed and if phone doesnt lock then i confirm the Mhz and mV...
For [email protected] , Yes PHONE MAY REACH over 50c while charging and playing demanding games at the same time... While on mobile, phone temperature is between acceptable ranges around 38-46c when playing demanding games... On idle, temp is around 22-28... Best choice is using phone [email protected] or [email protected] depending on the cpu; test and find out if ur cpu can handle this mV... Hope all these helps...
Kind Regards,
What do you use to monitor CPU temps?
EarlZ said:
What do you use to monitor CPU temps?
Click to expand...
Click to collapse
Dear Earlz,
You can use SetCpu widget or "System Panel" app to observe temps. Day by day, u get more experience and can guess the aprox. temp by touching
Also "StabilityTest" app shows temp while running...
Kind Regards,
I have System Panel app and it only shows battery temps, is that a mislabeled CPU temp ?
EarlZ said:
I have System Panel app and it only shows battery temps, is that a mislabeled CPU temp ?
Click to expand...
Click to collapse
Dear EarlZ,
Actually, we all call it as CPU temp... AFAIK, apps can only measure batt temp but it is a clue for us to determine how hot cpu is...
Kind Regards,
PROTOCHIP said:
Dear EarlZ,
Actually, we all call it as CPU temp... AFAIK, apps can only measure batt temp but it is a clue for us to determine how hot cpu is...
Kind Regards,
Click to expand...
Click to collapse
So its really battery temperature and not direct CPU temp?
EarlZ said:
So its really battery temperature and not direct CPU temp?
Click to expand...
Click to collapse
Dear EarlZ,
I guess so... I think batt. temp is parallel with cpu temp...
Kind Regards,
So i decided to make this video on different benchmarks , Check it out below... i also ran the GLbenchmark, which is the test lots of people said causes the thermal throttling, i didnt tick the triangle tests, and just did the Egypt tests, on and off screen and scores are very good,
Video- http://youtu.be/rimEV1Ou_WU
Iv also attached my glbenchmark scores to this thread as well as the CPU spy and it doesn't look like there was any thermal throttling going on here , The device did get warm, but not HOT , and i actually did the GLbench last , after all the other tests...
Hi N7 fellow users
i get MAX 2600 3D and 350 2D in antutu and quadrant though i'm all the time OC the GPU to 520mhz
is that normal ?? i'm running the latest Paranoid Android rom along the latest Franco kernel.
That is about what I get for 3D. If you go to the developer menu you can improve your 2D performance by checking the "Force GPU rendering" . For what it's worth my 2D for Quadrant went to about 1000 after the checking that option.
Sent from my Nexus 7 using Tapatalk HD
Thanks for your reply
My htc one X was getting 39xx, 1k higher than my nexus
though they use nearly the same gpu.
Homurato said:
Thanks for your reply.
My htc one X was getting 39xx, 1k higher than my nexus
though they use nearly the same gpu.
Click to expand...
Click to collapse
quadrant does not measure gpu, it measures fps. and we are limited to 59fps no matter how much we overclock the gpu. use a benchmark like windmill, or basemark taiji, to test your gpu and what tweaking your gpu does. quadrant is an old, out of date benchmark.
simms22 said:
quadrant does not measure gpu, it measures fps. and we are limited to 59fps no matter how much we overclock the gpu. use a benchmark like windmill, or basemark taiji, to test your gpu and what tweaking your gpu does. quadrant is an old, out of date benchmark.
Click to expand...
Click to collapse
i guess i have to forget about all this paranoia coming from the low benchmark scores since every game works xD
(except horn strangely runs about 25 fps it seems, even though i'm oced to 520mhz)
Low of diminishing returns, if you over clock it doesn't mean ull always get higher scores, after ur GPU gets heated up it start to show lower and lower scores.
GPU is stable @ 446 (beyond that when ever it gets heated up it will cause touch and other issues)
Source: Read kernel Developers OP once a while
I've been playing with the undervolt limit of this phone and it seems to have a large amount of play. Obviously every processor is unique so some of your S6's have a lower tolerance for undervolting. I'm using Hacker v11 with Synapse and I can get my A53 cluster @ 1.5 GHz down to 1000mV though I feel it can go lower. I have the A53 underclocked to 1.2 GHz @ 900mV for now and the A57 running 2 processors @ 1.4GHz and sitting at 825mV (just flashed v11 so Synapse reset the values and I've yet to UV the A57 much). Aside from benchmarking with various apps I notice no lag or slow downs running at the lower clocks and using only 6 cores.
My GPU is OC'd to 852MHz but I haven't UV'd it yet. Before v11 I had it at 856.25mV and still stable. HPM and various busses are going to be UV'd again and they seem to take it very well. I'll update this, hopefully later this evening, with more UV values.
I'd like to put our data together and figure out an average UV this phone can take and also see some more extreme values as well. It should be a good starting reference for anyone wanting to get longer life out of their battery along with the phone itself. While we're at it I'd lie to get some lower limits for the clocks and number of cores while still maintaining a smooth experience.
A53 (Hacker v11, starting w/ highest freq.)
1056
1012
962
918
875
843
806
781
750
725
693
675
650
631
625
A57 (Same as above)
1081
1065
1043
1012
981
943
912
875
943
818
800
775
750
731
718
693
675
662
650
643
637
631
GPU
887
831
787
743
718
675
668
Memory Bus(Lowest to highest)
575
575
581
593
593
600
650
675
725
743
768
800
831
Internal Bus(Lowest to highest)
637
637
643
675
712
737
737
743
743
750
793
800
Image Signal Processor(Lowest to highest)
650
650
700
737
806
These are what I'm using right now. I plan to take them down even more in the near future (I already have on some). Of course dropping the power doesn't count for much if the CPU is running too many cycles to finish a task so I'll be messing with the amount of cores and frequency as well.
I recently was running 7 clicks (which on Hackerkernel in Synapse I think is 6.25mv per click) on the Big cores and 6 clicks on the little ones. I also tapped each step in the gpu and busses down 3 clicks and undervolted the GPU too, at about -3 clicks as well. Seemed pretty stable.
benjmiester said:
I recently was running 7 clicks (which on Hackerkernel in Synapse I think is 6.25mv per click) on the Big cores and 6 clicks on the little ones. I also tapped each step in the gpu and busses down 3 clicks and undervolted the GPU too, at about -3 clicks as well. Seemed pretty stable.
Click to expand...
Click to collapse
The only thing I'm not sure about is the "Apollo HPM voltage margin" and it's exact function. I assume it's the max amount hardware performance monitor will allow the CPU/busses to be undervolted when it feels the demand on the CPU vs. it's clock is below a threshold. I'm sure I'm totally wrong though lol. So I'm going with 1 tick above the 25000 default (31250).
Have you ran a stress test with your setup or just put it through the daily motions to check for stability?
KCRic said:
The only thing I'm not sure about is the "Apollo HPM voltage margin" and it's exact function. I assume it's the max amount hardware performance monitor will allow the CPU/busses to be undervolted when it feels the demand on the CPU vs. it's clock is below a threshold. I'm sure I'm totally wrong though lol. So I'm going with 1 tick above the 25000 default (31250).
Have you ran a stress test with your setup or just put it through the daily motions to check for stability?
Click to expand...
Click to collapse
I think you're probably right. I don't know much about it myself but that sounds like a solid guess to me. I haven't done any major testing other than yeah just daily use and see if it reboots. I couldn't ever get any.ore than about 6 or 7 increments under on either cpu. I read that the big cores need about 25mv more than the little ones to be stable.
Oddly, I got to a point the other day where I realized that i just barely can't make it through 2 full days so I might as well max performance and just accept charging every night even though I usually have 40 to 50% left, but the stanbdy is always so bad that I end up starting the second day with only 40% or less and thus can't make the whole day. Anyway, so I switch from underclocked with less aggressive govs to max clock and more aggressive govs and I think battery life is oddly better now somehow and standby seems unchanged.
benjmiester said:
I think you're probably right. I don't know much about it myself but that sounds like a solid guess to me. I haven't done any major testing other than yeah just daily use and see if it reboots. I couldn't ever get any.ore than about 6 or 7 increments under on either cpu. I read that the big cores need about 25mv more than the little ones to be stable.
Oddly, I got to a point the other day where I realized that i just barely can't make it through 2 full days so I might as well max performance and just accept charging every night even though I usually have 40 to 50% left, but the stanbdy is always so bad that I end up starting the second day with only 40% or less and thus can't make the whole day. Anyway, so I switch from underclocked with less aggressive govs to max clock and more aggressive govs and I think battery life is oddly better now somehow and standby seems unchanged.
Click to expand...
Click to collapse
While it seems odd there's a reason that moving to a higher clock setting can improve battery life though it seems counter intuitive. If you have a task that needs to be done, it's going to request time on the processor. The amount of cycles it takes to complete it will be longer at a lower frequency vs. a higher one. So while it's working at a higher clock rate and drawing more power per cycle its getting the job done much more quickly and overall uses less power. This is the same reason having multiple cores gives us longer battery life. Of course the OS, apps, and phones capabilities have also became more demanding so we don't notice it as much anymore. The trick is finding the lowest frequency we can operate at without diminishing noticeable performance and not increasing the clock cycles needed for tasks by very much. Underclocking can help with this as well if dropping the clock rate by a significant margin isn't feasible.
KCRic said:
While it seems odd there's a reason that moving to a higher clock setting can improve battery life though it seems counter intuitive. If you have a task that needs to be done, it's going to request time on the processor. The amount of cycles it takes to complete it will be longer at a lower frequency vs. a higher one. So while it's working at a higher clock rate and drawing more power per cycle its getting the job done much more quickly and overall uses less power. This is the same reason having multiple cores gives us longer battery life. Of course the OS, apps, and phones capabilities have also became more demanding so we don't notice it as much anymore. The trick is finding the lowest frequency we can operate at without diminishing noticeable performance and not increasing the clock cycles needed for tasks by very much. Underclocking can help with this as well if dropping the clock rate by a significant margin isn't feasible.
Click to expand...
Click to collapse
It is very interesting. I'm now backing off max clock, one increment at a time on both core sets to see where they meet. So far just down to 1500 little and 2000 on the big. Seems to be pretty good.
Hey, kinda late to the party but I recently got an s6 and starting to mess around with undervolting... Problem is I don't know where to start. Where do I get synapse? I'm not familiar with synapse but I did use kernel adiutor in the past.
I'm using this ROM:
https://forum.xda-developers.com/galaxy-s6/development/rom-galaxy-s6-stock-debloated-t3812822
Along with this kernel:
https://forum.xda-developers.com/tm...oc-uc-twsited-kernel-7-0-t-w8-f-flat-t3652139
Any help is appreciated. ?