No doubt, Overclocking is usually dangerous. (overheating and so on)
Many user know that from Desktop-PC, Notebook Range ect.
Permanent OC will decrease lifetime of your hardware.
Also many user know that Intel, AMD/ATI ect. have Safety Devices for too higher OC.
My Question:
Which Safety Device have the SnapDragon from Qualcomm?
AFAIK the GPU is integrate into the CPU.
That doesn't make these things easier.
Greetingz from Berlin/Germany
Most time i think, there is only a short peak of using the Cpu, so it shouldn't damage it,but on Games im not so sure if it doesn't get problems. But when you go on a undervolt Kernel i think is is not so dangerous.
Greetings from Karlsruhe
OC to 1190Mhz interactive mode, hold my phone just now, quite cold
Chris X. said:
No doubt, Overclocking is usually dangerous. (overheating and so on)
Many user know that from Desktop-PC, Notebook Range ect.
Permanent OC will decrease lifetime of your hardware.
Click to expand...
Click to collapse
I don't agree that overclocking is dangerous if you're careful with it. I can't remember the last time I had a PC that wasn't overclocked, and I've never had one fail on me.
As long as you don't put the voltages too high & make sure the temperature is kept cool, it's not very risky or dangerous - it's just taking the hardware above the usually conservative guaranteed fully-stable speed set by the manufacturer.
With the HD2, it shouldn't be too different - as long as it's not overheating, it should be fine.
Also, if it's running stable at 1.1ghz, then that indicates that it's happy running at that speed.
The only possible side effect I could think of it potential data corruption if overclocking the CPU/GPU also overlocks a memory bus or whatever. There is no indication so far that this is happening to those who overclock.
I'm not sure about safety features, but I think the phone would become unstable before safety became a concern.
i agree with davidmc0 but this is in the wrong section as this a personal issue
I can set it as high as 1646. IV looked around and it seems that people use 1504. Is it unsafe to go any higher?
Thanks
Sent from my A501 using XDA App
1400 is safest I run Alexandra iii
if you go up to 1.6 GHZ, you might get SHUTDOWNS...
if you don't run any games, or apps, sure it will work. But not smart to overload it.
If on Custm ROM, Read DEV Notes, usually they'll say (or mention about Kernel changing)
as a rule I keep it on 1.5 Ghz (when 1.6 was max) (have tested on about 8-10 diff roms) (never have had any shutdowns yet)
*** also maybe use a meter app to check TEMPS (like battery TEMP)
Cool Tool - shows battery temp, RAM, Proc Freq, + more in little box on screen all the time (adjust settings)
https://market.android.com/details?id=ds.cpuoverlay
"setCPU for Root users" - underclock to lowest when off, set lower cpu freq if battery gets warmed to ur custom Degrees)
http://www.setcpu.com/
***Some custom ROM's have thier own Freq CONTROLER app (that could clash with prog or have 2 progs do the same thing)
Like humans NO TWO CPU's are equal
All of the above it true with one exception..NOT every cpu is created equal Not all ram chips and so on also live up to this..
Start over clocking your cpu slowly. as you push clocks higher of course lower voltage. This keeps heat down .
Two processors even made on the same casting can be totally different . Where one will take more heat with less errors and corruption and the die next to it will almost crash running its designed clock speeds . Being that extreme is very rare with a few exceptions. most are close as to a common ability. within a few 100 mhz.
So the answer is there is NO TRUE Answer. its trial and error but on the side of caution and testing clock speeds and heat is not a 30 second yes it runs. Do it over a week or so. I know with my dragon cup in cell phone its at its end of life from being over clocked for a few years. some last longer some die quicker.. Its kinda like drinking on your brain the more you drink the more cells you kill.. The hotter your cpu gets the more transistors fail the slower it becomes the more errors you have .
Relax .. go slow.do not expect to get what everyone else is claiming. and you will be fine..
Sorry again for long winded post..
dr mcknight said:
I can set it as high as 1646. IV looked around and it seems that people use 1504. Is it unsafe to go any higher?
Thanks
Sent from my A501 using XDA App
Click to expand...
Click to collapse
Any is unsafe. Higher speed equals heat and heat kills semiconductors. Might work for a while but why risk it
My daughters has been running at 1.6GHz for 2.5 months without any crashing or blowing up.
I say at 1.6, you're starting to enter the "red zone", sort of asking for problems. Why go up that high? I mean, 1.5 shows enough performance improvement over the 1GHz...
My nexus 10 froze two times today ( pretty normal, it usually freezes about 5 times a day) but today, a strange sound came out of it ( "rrrrrrrrrrrrrrrrrr" )
I don't know if it were the speakers or if it came from somewhere inside the tablet... I am very disappointed, I sold my transformer tf101 because it froze 3 times in a week, that was already to much for me. Why can't Google just fix it ? Or are they working on a fix ?
Inse
Sent from my Nexus 10 using XDA Premium HD app
Are you on a custom kernel? That sounds similar to the CPU crashing and hanging, thus the repeated noise
try setting your cpu governor to performance if you have a custom rom or kernel. solved the issues with rebooting for me (for the most part)
Well, you have to determine why the tablet is rebooting. If the device is getting noticeably hot and there is a "slideshow" effect then it is a indicator that it is being thermally throttled. Changing the governor won't necessarily fix this and in some cases can exacerbate it.
If you are indeed on a custom kernel, then then the kernel crashed. If its a reoccurring event then I would look at flashing a different kernel (Ktoonz or another) and seeing if that fixes the issue.
I haven't installed a custom kernel or custom rom, I not even rooted. On the left side of the camera ( when holding in landscape) the tablet gets very hot while playing simple games like pudding monsters. Is that normal ? Happens it to anyone else ?
Send from my lovely Sensation XL,
If I succeed helping you (rare) don't forget to hit the thanks button
There is currently a theory (tested by members and mostly supported by gathered data found in this thread) that the CPU does not have a temperature sensor and instead estimates temperature based on an equation. According to the member who did some testing, the equation is way off from the actual temperatures. This can cause freezing (due to lag from thermal throttling) which would account for the sound or the random reboots as the temperature equation reaches a critical point and reboots the device.
I would pay attention to the KT Manta kernel thread as there's some interesting research going on over there. I can say having used that kernel from day one, 100 MHz to 1.7 GHz and extremely undervolted I haven't experience a single instance of throttling or rebooting. The only reboots I've had were when I was dialing in my undervolts. I tried messing with the GPU voltage, but mine appears to be somewhat picky and I really couldn't undervolt the GPU much. The CPU on the other hand undervolts like a champ.
However, if the theory that Samsung uses an equation to determine temperature and not an actual sensor, undervolting will have zero effect on "temperature" though it will save battery. Having never encountered thermal throttling (even after significant game play and other activities) I can't speak to that issue. Though I can say that with my undervolt settings, the battery lasts a crazy long time and I have absolutely no performance issues.
To the extent that flickering and low charging is related to Sony thermanager, here is the permanent fix for AOSP/CM based roms. While the idea of thermal manager is good and we should credit Sony for doing it, the implementation kind of s*cks. For example, the manager kicks in when CPU/GPU temperature rises to 44 degrees. Also, several triggers are set between 54-56 degrees. This is plain wrong, because 44, 50 and 55-56 are all perfect numbers for an active device and at these temperatures, thermal manager should not be active. I have adjusted trigger numbers so that there will be no mitigation until at least 60 and surprise surprise, all screen flickering is gone away....
Attached is thermanager.xml which should be put in /system/etc/ with 644 permissions. Reboot is required. UNZIP FIRST. Also, backup your current file just in case.
A word of caution on undervolting: keep in mind that when you undervolt on high frequencies, you make your CPU work harder, as it requires more cycles to do the same task. As a result, you have overheating. So, undervolting is counter-intuitive..
Does it also will solve the touch freeze problem on cm12.1?
Gesendet von meinem Xperia Z1
sgspluss said:
Does it also will solve the touch freeze problem on cm12.1?
Gesendet von meinem Xperia Z1
Click to expand...
Click to collapse
Any touch issues related to thermanager kicking in early could be resolved. But lollipop has overheating issues related to art, which can't be solved by thermal management. That's why strictly speaking, lollipop has to be recalled. In my view it can't be fixed.
A little question
Hello optimumpro
I only need put the thermanager in the path system/etc to make it work? or need something else?. Sorry by the queastion I noob an recently I repair de display and touchscreen for my xperia z1 C6902 and a have the flickering problem.
Thanks for your help.
optimumpro said:
A word of caution on undervolting: keep in mind that when you undervolt on high frequencies, you make your CPU work harder, as it requires more cycles to do the same task. As a result, you have overheating. So, undervolting is counter-intuitive..
Click to expand...
Click to collapse
I think you have a misconception about undervolting , undervolting does not make your CPU work harder , instead it makes your CPU unstable .
so no, undervolting does not makes your cpu overheat , only overvolting does.
This works for me!
before flash this file, my Phone only receives 90ma from any changer, and now reciving 1080ma. Thanks a lot!
Room: Ressurection Remix
Android version: 5.1.1, Xperia Z1 C6943
Sent from my Xperia Z1 using XDA Free mobile app
Hi
My phone in stock rom recieves 800ma
Does it normal??
I think it charges late,from 0 to 100 it takes about 3 hours 45 mins
Do i need flash this file??
Does my charger or battery have any problem?!
Thank you so much
Here is my screen shot
Sent from my C6903 using Tapatalk
agha_jo0n said:
Hi
My phone in stock rom recieves 800ma
Does it normal??
I think it charges late,from 0 to 100 it takes about 3 hours 45 mins
Do i need flash this file??
Does my charger or battery have any problem?!
Thank you so much
Here is my screen shot
View attachment 3434889
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
I don't think that app is accurate tbh with the fix it says no higher than 300ma for me and my phone is charging pretty well I'm using 2100ma charger as well
Sent from my Xperia Z1 using Tapatalk
Sorry bro but i don't have this file in system /etc??? Wtf???
ninjasoft said:
Sorry bro but i don't have this file in system /etc??? Wtf???
Click to expand...
Click to collapse
You are probably on kitkat. If that's the case, you don't need thermanager. If you are on lollipop, look again, the files are not necessarily in alphabetical order...
And remember, this one is for custom roms: CM and/or AOSP based. I just looked at your signature, you have stock...
zhuoyang said:
I think you have a misconception about undervolting , undervolting does not make your CPU work harder , instead it makes your CPU unstable .
so no, undervolting does not makes your cpu overheat , only overvolting does.
Click to expand...
Click to collapse
You are wrong. When cpu is unstable, it can't do the job. When it can't do the job it jumps to higher frequencies and then plugs in additional cores, which causes overheating.
optimumpro said:
You are wrong. When cpu is unstable, it can't do the job. When it can't do the job it jumps to higher frequencies and then plugs in additional cores, which causes overheating.
Click to expand...
Click to collapse
Explain why that a phone reboots automatically when you underclock too much, if your concept is correct then it should just run at higher frequencies instead of just reboot.
And also what's the purpose of overvolting?
What's the purpose of per frequency voltage table?
zhuoyang said:
Explain why that a phone reboots automatically when you underclock too much, if your concept is correct then it should just run at higher frequencies instead of just reboot.
And also what's the purpose of overvolting?
What's the purpose of per frequency voltage table?
Click to expand...
Click to collapse
Easy: when you under volt over a certain level, the cpu just shuts down, because it does not have enough energy to jump to higher frequencies. So, in that case, instead of jumping and overheating, it just dies. However, when you under volt to a lesser degree and cpu has just enough (not to die), then you will have jumping and overheating.
There is no purpose in overvolting, other than returning to your prior levels or correcting wrong default values if you don't want to fix those in kernel source.
What's the purpose of per frequency voltage table? If you adjust, you want to do it on global level, because cpu has different frequencies. There is no other way...
However, if you put your phone on performance governor, you won't need per frequency voltage. By the way, in my experience, performance governor causes less noise and overheating, because it does not spend time and energy on jumping, and it could go to idle immediately.
optimumpro said:
Easy: when you under volt over a certain level, the cpu just shuts down, because it does not have enough energy to jump to higher frequencies. So, in that case, instead of jumping and overheating, it just dies. However, when you under volt to a lesser degree and cpu has just enough (not to die), then you will have jumping and overheating.
There is no purpose in overvolting, other than returning to your prior levels or correcting wrong default values if you don't want to fix those in kernel source.
What's the purpose of per frequency voltage table? If you adjust, you want to do it on global level, because cpu has different frequencies. There is no other way...
However, if you put your phone on performance governor, you won't need per frequency voltage. By the way, in my experience, performance governor causes less noise and overheating, because it does not spend time and energy on jumping, and it could go to idle immediately.
Click to expand...
Click to collapse
__________________________________________________________________________________________________________________________________________________________________________
http://bigfatreality.blogspot.com/2012/04/complete-android-undervolting-guide.html
Advantages of undervolting Android
Thank God for Android where we can easily modify and customize our lovely Android devices to the way we want. Being said this, undervolting is one of the biggest attraction for Android! Simply by undervolting an Android you will or might experience:
A longer battery life
More responsive smartphone
Less heat produced by the phone
Super-charge your Android to go further than what it can do (overclocking Android)
Click to expand...
Click to collapse
http://techglen.com/2014/01/16/what-is-undervolting-how-to-undervolt-your-android-phone/
Note: UnderVolting is widely used as a cooling solution and in my opinion more effective than any other cooling solution available for free. Results can will show decrease in the temperature of smartphone. I recommend undervolting to anyone with enough confidence and knowledge to do so. The benefits easily outweigh the risks. I dont see why one shouldn’t do this for a cool and better smartphone experience.Undervolting will NOT compromise performance at all.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1956346
Undervolting is actually a very good thing for your smart phone when you do it correctly. Undervolting has one major positive effect on your CPU: it will extend the life of your processor by allowing it to do demanding things with lower heat generation
Click to expand...
Click to collapse
zhuoyang said:
__________________________________________________________________________________________________________________________________________________________________________
http://bigfatreality.blogspot.com/2012/04/complete-android-undervolting-guide.html
http://techglen.com/2014/01/16/what-is-undervolting-how-to-undervolt-your-android-phone/
http://forum.xda-developers.com/showthread.php?t=1956346
Click to expand...
Click to collapse
Maybe or maybe not. Blogs, especially by those who don't know what they are talking about (isn't it the purpose of blogs anyway? ) is not proof of anything.
However, you asked me to explain myself and I did. Why don't you put cpu info on the screen and experiment (so you can see live frequencies and temperature). You'll be surprised...
The point stands: when your cpu does not have enough juice, it spends more efforts to accomplish the task. If it manages not to shutdown, then it spends more cycles to do the job, thus causing overheating and excessive battery drain. And it does not matter how you call that state: unstable or whatever...
The reason I said it was counterintuitive is that people think if you provide less energy to cpu, there will be less noise and heat. The most energy is spent when cpu jumps back and force or plugs in/out cores and that's exactly what cpu does when you reduce voltage. If it is locked at the highest frequency, you eliminate jumping and extra plugging. When your phone is active, it accomplishes tasks faster. When it is done, it rushes to idle immediately and in idle state it virtually does not make any difference which frequency you are on, especially it does not matter when your phone is in deep sleep. Also, at higher frequencies cpu is often able to do the task using one core, again resulting in battery savings.
optimumpro said:
Maybe or maybe not. Blogs, especially by those who don't know what they are talking about (isn't it the purpose of blogs anyway? ) is not proof of anything.
However, you asked me to explain myself and I did. Why don't you put cpu info on the screen and experiment (so you can see live frequencies and temperature). You'll be surprised...
The point stands: when your cpu does not have enough juice, it spends more efforts to accomplish the task. If it manages not to shutdown, then it spends more cycles to do the job, thus causing overheating and excessive battery drain. And it does not matter how you call that state: unstable or whatever...
The reason I said it was counterintuitive is that people think if you provide less energy to cpu, there will be less noise and heat. The most energy is spent when cpu jumps back and force or plugs in/out cores and that's exactly what cpu does when you reduce voltage. If it is locked at the highest frequency, you eliminate jumping and extra plugging. When your phone is active, it accomplishes tasks faster. When it is done, it rushes to idle immediately and in idle state it virtually does not make any difference which frequency you are on, especially it does not matter when your phone is in deep sleep. Also, at higher frequencies cpu is often able to do the task using one core, again resulting in battery savings.
Click to expand...
Click to collapse
You're the one who don't know what you yourself is talking about.
Someone need to prove your concept right, I can't find anything about saying under clocking makes your cpu overheat.
Try find someone who agree with your concept or at least prove yourself right.
If you're able to prove yourself right I'll do you a favor and submit it to the news portal.
zhuoyang said:
You're the one who don't know what you yourself is talking about.
Someone need to prove your concept right, I can't find anything about saying under clocking makes your cpu overheat.
Try find someone who agree with your concept or at least prove yourself right.
If you're able to prove yourself right I'll do you a favor and submit it to the news portal.
Click to expand...
Click to collapse
"You're the one who don't know what you yourself is talking about"
No need to get personal. And I certainly don't need any "favors" from you.
If you need proof, just do a search anywhere including XDA where it would tell you that there is growing evidence that performance governor where your cpu is set at the highest frequency reduces "race to idle" and therefore causes less noise (jumping) and therefore better on performance and battery.
http://forum.xda-developers.com/nexus-4/development/guide-android-governors-explained-t2017715 That's just one example.
You won't find much more for several reasons: linux does not care about smart phones and only they know enough about kernels, but in the context of PCs they are not concerned about governors. They only have performance and ondemand (for laptops). Google does not deal with kernels (except for nexus) and they have no qualified engineers. Manufacturers do, but they have no incentives to invest more millions in research and development so that you can keep your device longer.
But as I have already said, do it yourself. Set cpu data on screen and experiment with performance vs other governors while watching the temperature. My experience has been that there is obviously no jumping and very little core plugging/unplugging, because 2.2-2.4 core can do a lot alone without extra efforts...
If you can't behave and maintain an intelligent conversation without resorting to personal attacks, then there is no point for me to talk to you. .
optimumpro said:
"You're the one who don't know what you yourself is talking about"
No need to get personal. And I certainly don't need any "favors" from you.
If you need proof, just do a search anywhere including XDA where it would tell you that there is growing evidence that performance governor where your cpu is set at the highest frequency reduces "race to idle" and therefore causes less noise (jumping) and therefore better on performance and battery.
http://forum.xda-developers.com/nexus-4/development/guide-android-governors-explained-t2017715 That's just one example.
You won't find much more for several reasons: linux does not care about smart phones and only they know enough about kernels, but in the context of PCs they are not concerned about governors. They only have performance and ondemand (for laptops). Google does not deal with kernels (except for nexus) and they have no qualified engineers. Manufacturers do, but they have no incentives to invest more millions in research and development so that you can keep your device longer.
But as I have already said, do it yourself. Set cpu data on screen and experiment with performance vs other governors while watching the temperature. My experience has been that there is obviously no jumping and very little core plugging/unplugging, because 2.2-2.4 core can do a lot alone without extra efforts...
If you can't behave and maintain an intelligent conversation without resorting to personal attacks, then there is no point for me to talk to you. .
Click to expand...
Click to collapse
I am not attacking you tbh.
Governors doesn't do anything besides controlling the frequencies of cpu. CPU uses correct amount of voltage according to the voltage table.
If what you're saying is correct, doesn't overvoltage makes your phone cooler? It has more energy to process things and doesn't need to jump to higher frequency right?
Kernel developers implement features for reasons. If your theory is correct, why does voltage control exist? Does kernel developers write a thousand lines of code just to do nothing?
zhuoyang said:
I am not attacking you tbh.
Governors doesn't do anything besides controlling the frequencies of cpu. CPU uses correct amount of voltage according to the voltage table.
If what you're saying is correct, doesn't overvoltage makes your phone cooler? It has more energy to process things and doesn't need to jump to higher frequency right?
Kernel developers implement features for reasons. If your theory is correct, why does voltage control exist? Does kernel developers write a thousand lines of code just to do nothing?
Click to expand...
Click to collapse
"I am not attacking you" Yes you were, I said that some bloggers don't know what they are talking about and you replied that I didn't know what I was talking about. Anyway, I accept your veiled apology.
Neither overvoltage nor undervoltage makes the phone cooler. There is an optimal regime for each cpu and if you go outside of it (in either direction), you are inviting trouble. You are not going to destroy your cpu by either under or over voltage, as there is protection in kernel. The phone runs cooler when cpu works less and the optimal regime causes the cpu work less. If you are reducing juice (voltage), you make cpu work longer, which results in overheating.
I gave you an example of performance governor to make a point that this is counterintuitive: while cpu is set at the higher frequencies, it actually performs the tasks and rushes to idle faster, which results in cooler condition. When the same cpu is set lower (and especially if it is under volted), it works longer, jumps to different frequencies, plugs/unplugs cores, which all contributes to overheating....
What is normal values for this phone ? I have diferent chargers, Samnsung - around 600mA, one HTC - around 400mA and another one with 200mA according to that app. Wich one should i use ? So far i used samsung one because it charges fast...2 hours or less, but the battery dies also fast ....so it may be because of the charger ?
I can remember there was a similar issue happening on nexus 6, where cores were disabled at not that high temperatures.
If I can remember correctly, this was rectified by disabling the bcl driver.
Now, I found the correct path for the bcl driver (/sys/devices/soc.0/qcom,bcl.62/mode) on OPT, but I cannot edit the file, check the the screenshot below.
https://photos.google.com/share/AF1...?key=T2xkcU9mbGRON0dhVkFBTHdBaWs3Vi1Od1ZpOGN3
I even tried a init.d script, unfortunately, even this failed.
If someone can find a way to disable this, I reckon this will make our OPT way faster
hamdir said:
@Lord Boeffla
i just flashed your kernel after having problems with stock kernel, i think its similar to the bug you are tracking the stock kernel shuts down the big cluster at 40c or in low battery BUT also sometimes out of the blue it kills the big cluster never let it back on again another bug about usb charging where it stops charging over usb until reboot, i wrote about it extensively on the OP forums:
https://forums.oneplus.net/threads/to-oneplus-2-software-engineers-you-need-to-hear-this.399790/
you said that you are not sure about the s810 quality but i can assure you on the M9 latest v2.10 software it has killer performance full octa all the time (though the M9 has better thermal release as the s810 is connected to the metal unibody) but the quality of the OP2 stock kernel is really down mediocre, also from my M9 experience the high consume on the s810 is not related to a57 in specific, its the leakage in 20nm so even thee a53 cluster has high usage if its running on top clock, in fact on the M9 full octa LITTLE.big is better for battery as the a57s prevents the device from locking into the a53 full clocks, so really killing the big cluster for battery is counter productive to be honest, the easiest gain i found for battery is to underclock the a53 cluster to 1.2ghz and leave the a57 untouched in quad (which also help in keeping the SoC cold / improve sustainable performance)
i like you kernel because it tries to remain as stock as possible and whatever changes it does are noted, this is how i like custom kernels to be, its easier for the user to track what to change
but your hunt is making me think, is it possible that the users reporting the shut down are facing the exact same bug as stock kernel where the big cluster is killed for no reason? equally if the solution is disallowing min 0 why not make it optional?
finally i wanted to ask although we are setting 2:4 in a57 hot plug, the behaviour is exactly stock, ie: the device never requests more than 2 a57 cores so effectively its a hex configuration
Click to expand...
Click to collapse