Is there a way to do that?
KernelTasker refuses to go beyond that amount..
AIDA64 however reports clocks up to 2091Mhz.
To answer your question, no.I highly doubt it can go all the was beyond 2ghz. Even with the 1785mhz limitation, its the "safest" clock for the switch. Even on heavy games the CPU temp is around 50 degrees Celcius. High clocks at such heat can permanently damage the switch's CPU. Edit: if you root it with Majisk you can go beyond 1785mhz
BashfulLine3584 said:
To answer your question, no.I highly doubt it can go all the was beyond 2ghz. Even with the 1785mhz limitation, its the "safest" clock for the switch. Even on heavy games the CPU temp is around 50 degrees Celcius. High clocks at such heat can permanently damage the switch's CPU. Edit: if you root it with Majisk you can go beyond 1785mhz
Click to expand...
Click to collapse
Temperature has nothing to do with it. The only reason it is not recommended is because of battery life. Not to mention 50 degrees Celsius is NOT high, it is average at best. High for the X1 would be 70 to 80 degrees Celsius
BashfulLine3584 said:
Edit: if you root it with Majisk you can go beyond 1785mhz
Click to expand...
Click to collapse
I did root with Magisk,
however all programs, even if done with shell itself revert to 1,7Ghz.
Mind explaininghow to go beyond ?
-Rye- said:
I did root with Magisk,
however all programs, even if done with shell itself revert to 1,7Ghz.
Mind explaininghow to go beyond ?
Click to expand...
Click to collapse
There might be a module in majisk somewhere. Other than that I doubt you can go beyond 1.7 ghz
Related
Hi,
I read through approx. 50 pages of text and didn't find an answer:
Is there some kind of prevention to enter numbers like 6000mhz (eg when you meant 600) ?
Same with the voltage: could I enter and apply a critical value ? I tried it with "5" which lead to instant reboot.
Also: I can't find any explanation on what sd card speed fix does ?
Also: What does Jit do ?
THX
Low vsel will really cause reboot as it doesnt getr enough juice to run, on the other hand if you set it to 6000 but didnt change the vsel imo it would again reboot. That is if you accidentally put it, but if you deliberately want to try vsel 1000 @ 6000mhz, that I don't know,run test underwater to prevent meltdown. Good luck
Sent from my MB525 using XDA App
but it would immediately die and would not explode right ?
I think the VSel is limited to a max value of 78, or 80, or the limitation comes from the kernel, something like this.
Also there is a limitation from ARM to prevent hardware damage, there are a lot of failsafe mechanism built inside the hardware, beside the software.
maxi2mc said:
I think the VSel is limited to a max value of 78, or 80, or the limitation comes from the kernel, something like this.
Also there is a limitation from ARM to prevent hardware damage, there are a lot of failsafe mechanism built inside the hardware, beside the software.
Click to expand...
Click to collapse
No max vsel is 90. Max clock thats stable is 1380 MHz.
Sent from my MB525 using XDA App
Ok... so you can't really fry your hardware.
At worst it will die within a few hours/ days/ weeks ?
Flashed Faux123's Kernel acouple days ago and have a question.
Does this Application need to be running for the voltage changes to work? What about for the profiles set?
Thanks.
i don't know the answer because i haven't flashed a kernel. the quickest and best answer is to try yourself. setcpu is in the market.
I know, but it's hard to tell and I really don't want to undervolt too much more because I don't wanna see a crash, although I have yet to experience one. I have it set at
Respectively:
-100
-100
-50
-75
-300
-300
-300
Seems stable with and without SetCPU on while spamming Quadrant standard benches and I cannot tell if the voltages are working or not. Those extra volts being taken away can greatly help my battery life, but if it's not working without the program on there is literally no way to tell. I use Advanced Task Manager a lot and it takes out SetCPU all the time.
Maybe someone with more experience of the program can help me out.
why do people undervolt it? Why wouldn't Faux undervolt when he created it? I don't touch the voltages, but not sure how you test if undervolting would hurt performance.
There is a bunch of responses to undervolting in faux's kernel thread in the dev forum. But long story short u can't have more than 100 m's between jumps when setting your undervolting, or it simply wont apply it. Example.
75
75
75
75
125
200
225
Sent from my MB860 using XDA Premium App
Phalanx7621 said:
There is a bunch of responses to undervolting in faux's kernel thread in the dev forum. But long story short u can't have more than 100 m's between jumps when setting your undervolting, or it simply wont apply it. Example.
75
75
75
75
125
200
225
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Really? I'll adjust my settings. Can you show me where it says that -100 jumps won't be applicable?
Probably going to adjust it to
100
100
75
75
175
275
300
edit: It's stable after around 10 Quadrant runs. I'd still like where you found that information though.
Thanks
Phoneguy589 said:
why do people undervolt it? Why wouldn't Faux undervolt when he created it? I don't touch the voltages, but not sure how you test if undervolting would hurt performance.
Click to expand...
Click to collapse
Well, I've been overclocking computers for years and something I've learned is that the lower your voltage is, the less degraded the processor will be after awhile. Such as, if you overclock the voltage too high, overtime you would need more voltage to obtain the same speed. Same thing applies when overclocking graphics cards.
Edit: Anyways, why are people dodging the main question
no you shouldnt have to keep setCPU running. i believe the app is just changing some sysfs files, so its one and done till the next time you open and change more values.
LivingChampion said:
Really? I'll adjust my settings. Can you show me where it says that -100 jumps won't be applicable?
Probably going to adjust it to
100
100
75
75
175
275
300
edit: It's stable after around 10 Quadrant runs. I'd still like where you found that information though.
Thanks
Well, I've been overclocking computers for years and something I've learned is that the lower your voltage is, the less degraded the processor will be after awhile. Such as, if you overclock the voltage too high, overtime you would need more voltage to obtain the same speed. Same thing applies when overclocking graphics cards.
Edit: Anyways, why are people dodging the main question
Click to expand...
Click to collapse
Probably going to adjust it to
100
100
75
75
175
275
300
Bro, this setting is left 770-470 = 300 or 770 - 300 = 470mv ?
after root... i have installed SetCpu, i have overclock my processor to 1.6ghz.. the question is, can i use this setting for daily use? is it will cause my processor hot or damage??
Depends on the phone. Mine can't run above 1.4ghz stable (but my GPU can overclock easily).
^What he said. Try it for a while, but if you get reboots or freezes, pull it back to 1.4 or 1.2.
if it runs stable then you can no problem
Watch your temp. Might be a phone but it's the same as a computer. That reno gets to high, and you're looking at overheating and possibly causing corrupted files from shut downs or worse, hardware damage.
Correct me of I'm wrong.
Clay
Sent from my SGH-I777 using XDA
emoskremo said:
after root... i have installed SetCpu, i have overclock my processor to 1.6ghz.. the question is, can i use this setting for daily use? is it will cause my processor hot or damage??
Click to expand...
Click to collapse
Just make sure you don't check "Set at boot" until you're sure you can set it at 1.6 with out reboots and crashes...... GL
Why 1.6ghz all the time? 1.4ghz uses MUCH less power (meaning less heat as well) and is 99% as smooth.
Colton127 said:
Why 1.6ghz all the time? 1.4ghz uses MUCH less power (meaning less heat as well) and is 99% as smooth.
Click to expand...
Click to collapse
Very good point....
I underclock to 800 . And phone is just as snappy. Why would ya wanna use 1.6 out of curiosity ?
Sent from my SGH-I777 using Tapatalk 2
Honestly the only reason someone would overclock to 1.6 GHz would be for bench marking, which i find useless. My processor is usually clocked to 800 MHz and i can play games like N.O.V.A. 3 with only slight lags here and there.
I do something similar to a few people here. I keep it at 800 most of the time and bump it up to 1000 when I'm playing certain games. Then back to 800 when I'm done. Responsive enough for whatever I have to do and doesn't overheat.
Wow OP
What a question OP.
I can't believe no one called you out yet.. I will be the first
If you want to kill your phone hardware then keep it at 1600! (which is overclocked too you dummie)
USE SetCPU so that your phone can
1. remain cool when high CPU cycles are needed
2. save battery by making profiles especially for when your phone screen is off
...
ok theres good guides out there. just google it
Hello,
I installed cyanogenmod a few months ago and want to overclock now. Anybody who knows if it is dangerous? Is it possible that your cpu breaks down faster because of the overclocking? which are the acceptable cpu settings?
thanks
Lambo6 said:
Hello,
I installed cyanogenmod a few months ago and want to overclock now. Anybody who knows if it is dangerous? Is it possible that your cpu breaks down faster because of the overclocking? which are the acceptable cpu settings?
thanks
Click to expand...
Click to collapse
It's not that dangerous, but your cpu will wear out faster than normal, because a highter clockspeed means more heat. Acceptable cpu-settings? Depends... most phones seem to handle 691 without problems, anything above that is luck of the draw.
Set your desired cpu-settings (don't use set-on-boot)
If the setting is higher than your cpu can handle you will start experiencing crashes. If you have found a stable frequency for your phone, you can set it on boot so you don't have to think about that every time you restart your phone. If you set an unstable frequency and use set-on-boot, you will get a bootloop.
SmG67 said:
It's not that dangerous, but your cpu will wear out faster than normal, because a highter clockspeed means more heat. Acceptable cpu-settings? Depends... most phones seem to handle 691 without problems, anything above that is luck of the draw.
Set your desired cpu-settings (don't use set-on-boot)
If the setting is higher than your cpu can handle you will start experiencing crashes. If you have found a stable frequency for your phone, you can set it on boot so you don't have to think about that every time you restart your phone. If you set an unstable frequency and use set-on-boot, you will get a bootloop.
Click to expand...
Click to collapse
So the higher the frequency, the faster the cpu will wear out, just because of the heat. I will keep an eye on that.
thanks
Lambo6 said:
So the higher the frequency, the faster the cpu will wear out, just because of the heat. I will keep an eye on that.
thanks
Click to expand...
Click to collapse
When playing high-end games, I always put the cpu-clockspeed to 729 mhz...
I have a super old galaxy nexus that im currently using because i was flashing new rom on my note 3 and killed it.
So i decided to flash franco kernel in this baby to make this underdog fly with 1.8ghz.
The stock is 1.2ghz.
What i did was i set min freq=1.8 max freq=1.8.
Did some stress test, didnt have issues (no reboot or shutdown). But the frequency will drop go 192mhz to 384mhz.
Everytime i stress the phone (games or heavy multitasking), the phone would simply downclock itself even though i DEMAND and LOCKED the frequency to 1.8ghz.
Any ideas? I assume its thermal throttling
If so, how can i get around it? I just want maximum amount of performance
Thanks guys.
PowrtBall2016 said:
Everytime i stress the phone (games or heavy multitasking), the phone would simply downclock itself even though i DEMAND and LOCKED the frequency to 1.8ghz.
Click to expand...
Click to collapse
Don't do that.
Planterz said:
Don't do that.
Click to expand...
Click to collapse
Even if i dont overclock the phone, the galaxy nexus would downclock itself from its 1.2 ghz down to somewhere around 500mhz anyways.
Seems to be aging because literally anything i throw at it, it will overheat regardless.
I just want a usable phone, if its constantly clocked at 500mhz, its literally slow enough for me to certify its a piece of garbage