Related
Hello to everyone! I've got a question: everyone knows that galaxy nexus cpu was made to work at 1.5ghz but it's downclocked to 1.2. Developers did a lot of kernels that can increase cpu clock. Now, everyone knows also that overclock brings instability sometimes and may damage permanently the phone. If it's true that our cpu is made to work at highest clock,can we consider it an "overclock" that includes risks like every overclocked kernel do,or it's safer than other phones overclock? Also,(here i appreciate some developer statements) the method used by kernel developer to overclock it's the same used by google own developers? Thanks in advance!
You can oc to 1.5ghz if your phone can handle, there are no more risk than flashing a kernel. But if you try to oc to 2ghz,there are a lot of risk. My phone is okay with 1.5ghz very smooth. If I want to go to 2.0ghz my phone freeze but work after pulling the battery. No fire. Try, and see if it works.
Sent from my Galaxy Nexus using Tapatalk 2
xorob0 said:
You can oc to 1.5ghz if your phone can handle, there are no more risk than flashing a kernel. But if you try to oc to 2ghz,there are a lot of risk. My phone is okay with 1.5ghz very smooth. If I want to go to 2.0ghz my phone freeze but work after pulling the battery. No fire. Try, and see if it works.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I know,eveything works fine up to 1.5 ghz. Even if battery sucks,it's ok! But i want to know: if i'll use everyday my phone overclocked may i damage it?
Inviato dal mio Galaxy Nexus
No, but it depends of the temperature of your phone. If your phone is at 100°c yes it will damage your phone, return to 1.2,but if your phone's temperature is lower than 65°c all the time, no problem.
Sent from my Galaxy Nexus using Tapatalk 2
xorob0 said:
No, but it depends of the temperature of your phone. If your phone is at 100°c yes it will damage your phone, return to 1.2,but if your phone's temperature is lower than 65°c all the time, no problem.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Do you mean battery temperature? For example that showen by spare parts or the radio menu? (*#*#4636#*#*)
Inviato dal mio Galaxy Nexus
Angelakaro said:
Do you mean battery temperature? For example that showen by spare parts or the radio menu? (*#*#4636#*#*)
Inviato dal mio Galaxy Nexus
Click to expand...
Click to collapse
Hi,
No,CPU temperature...
In any case there is a thermal protection for the CPU...The limit depends of the kernel you will use.
Stock is 64°C,some have a limit at 75°C and for others you can disable the thermal protection or set a higher CPU temp limit.
In any case the max CPU temp is 110°C after the CPU shutdown...
If the limit is at 75°C,at above->thermal throttling->lower CPU freq to prevent damage.
There is already some threads about CPU temperature wher you can find what is normal or not.It mainly depends of your CPU settings/usage obviously...
But some phones can't handle some higher CPU freqs...
viking37 said:
Hi,
No,CPU temperature...
In any case there is a thermal protection for the CPU...The limit depends of the kernel you will use.
Stock is 64°C,some have a limit at 75°C and for others you can disable the thermal protection or set a higher CPU temp limit.
In any case the max CPU temp is 110°C after the CPU shutdown...
If the limit is at 75°C,at above->thermal throttling->lower CPU freq to prevent damage.
There is already some threads about CPU temperature wher you can find what is normal or not.It mainly depends of your CPU settings/usage obviously...
But some phones can't handle some higher CPU freqs...
Click to expand...
Click to collapse
Thanks! Another question: how can i monitor CPU temp? Is there an app to do it?
Inviato dal mio Galaxy Nexus
Angelakaro said:
Thanks! Another question: how can i monitor CPU temp? Is there an app to do it?
Inviato dal mio Galaxy Nexus
Click to expand...
Click to collapse
Just take a thermomether LOL
k.janku1 said:
Just take a thermomether LOL
Click to expand...
Click to collapse
Ahahahah
Inviato dal mio Galaxy Nexus
1.5ghz is fine no damage should occur seeing as how the cpu in our phone is meant to run at that speed but was uc to probably save battery
Question. Why was it underclocked to begin with?
To extend battery life, probably
Angelakaro said:
Thanks! Another question: how can i monitor CPU temp? Is there an app to do it?
Inviato dal mio Galaxy Nexus
Click to expand...
Click to collapse
Re,
If you use Francisco/Glados/Morfic's kernel they have their own applications with a ton of features/settings and in this case the CPU temperature->Go to the dev section
In the Play Store System Tuner...Hum...there must be others (though perhaps not that much ),but I don't remember...
While the CPU in the Nexus may be the same as the 1.5 Ghz ones in other devices you have to keep in mind that when a manufacturer knows they will be underclocking you will potentially get the cores that were made for 1.5 but couldnt handle it and therefore used for this application (all about yield and bin rates). So while most phones are likely fine at 1.5 Ghz (phone does get warm) its not a guarantee it will work
I'll try some apps to monitor my CPU and i'll update this thread with my personal experiences after overclocking/switching kernels. Thanks to everyone!
Inviato dal mio Galaxy Nexus
I'm now using aokp build 39 + franco kernel r190,1228 mhz max cpu,384 min,ondemand,384 mhz gpu. During deep sleep the average cpu temp is 42°. Using the phone (wi-fi activated,messagging and xda app) it reaches 55°. The max temp was reached playing nova 3 for about 20 minutes: 72° (overclocking to 1500 mhz and using interactive governor). Are this values normal?
Angelakaro said:
I'll try some apps to monitor my CPU and i'll update this thread with my personal experiences after overclocking/switching kernels. Thanks to everyone!
Inviato dal mio Galaxy Nexus
Click to expand...
Click to collapse
TempMonitor is the one I use.
It'll be fine.. CPU gets throtled if it goes over 63C, unless you're running a custom throtle temp, or your kernel changes it. Shame they gimped these 4460's for more mass produciton and I think they were having stability issues? Regardless, this phone still flies @ 1.2.
I heard there was a problem with stability issues before. Has it been fixed?
Also, do any of you guys feel the need to OC in the first place?
iArtisan said:
I heard there was a problem with stability issues before. Has it been fixed?
Also, do any of you guys feel the need to OC in the first place?
Click to expand...
Click to collapse
I tried OC'ing to 1,4 for a short time, didnt get any instabilities.
Which leads me to question two. No I don't feel the need to OC this phone, it is still good enough to cope with everything i throw at it.
The worst that will happen is that it will run a little hotter than normal. I was running Trinity Kernel on RasCream ROM clocked at 1.5GHz and it was fine, nothing crashed, no reboots, all was well.
Besides; It's a Nexus, it was built for this!
This varies for everyone
Sent from my GT-I9300 using Tapatalk 2
Meh. It all varies. No 2 chipsets are the same. What may work for someone else may not work for you. Trial and error is the only surefire way to find out.
Hi,
I agree with what has been said above, all the CPU's are not equal but actually the progress made by the kernel devs allows all (or almost) phones to run at 1.3* Ghz (1.34/1.35 Ghz, it depends of the kernel) without any issues.I think it's for all, actually I don't remember a user with issues at 1.3* Ghz...
And for most phones 1.5 Ghz is fine.For some others, above 1.5 Ghz is problematic but it depends also of too many factors.
Now it's not like it when the Genx came out, where 1.3 Ghz was the limit of CPU overclock for all the phones.
And many people can run stable at 1.65 Ghz, also it depends of the kernel.
For me for example my max CPU freq usable each day, so stable is 1.72 Ghz with Glados kernel, above (like 1.8 Ghz) it runs fine for 30 mins, sometimes 1 hour, but after always freeze/reboot... maybe my CPU can't reach this CPU freq or maybe my settings are wrong (voltage) ...
I agree, an extreme overclock like 1.72 Ghz is not really necessary for all day (heat, battery life, etc...) but a little overclock like 1.5/1.53 Ghz and you a difference in certain case (openning some apps, general UI, browsing, etc...).
But if we have the ability to test and play...why not... ,in any case for me it's yes, I like overclock and test the possibilities/limits of my phone, different settings...
Everyone does as he wants and it depends on what you want (battery life,a little more power in some situation like playing or a higher bench score ).
Well considering Texas instruments recommended highest clock speed for this processor is 1.5 ghz I'd say your fine. Anything above that is dependent on how well your chip set will handle it. Besides who honestly has needed to OC for anything other than benchmarks?
Sent From My Sprint Galaxy Nexus
I got a little problem:
I can overclock my wildfire to only 710 Mhz if i overclock it to 768 the phone stucks and i can't do anything.
At the moment I'm using Cyanogenmod 9 but i think it isn't because of the ROM 'cause in Rempuzzle ROM i had this bug too.
Should i flash another Kernel or what should i do?
As far as I know, it's a hardware limitation.
It depends on the processor, some processors have high tolerance to overclocking, some don't.
In another words, some processors can handle high speeds. The defualt speed is actually 512-ish so when you increase to 768, it just can't handle the speed so the phone freezes/reboots.
Some wildfires can handle those speeds, luckily mine does
That doesn't mean you have bad or faulty hardware. The processor just can't handle it
Correct me if I'm wrong .
Sent from my HTC Wildfire using Tapatalk 2
I think from my new experience it might be a bit of a combo between the actual chip and the kernel settings, on my s2 with 1 kernel I can only oc to 1300 with both cores on but with another (my favorite one anyway) I can hit 1500 both cores on.
I still think the actual processor has more input than the kernel though, and all the extra strain from not having a gpu can't help either.
EDIT: I'm not saying flashing a new kernel will help you reach 768 though , the lack of resources elsewhere is a huge hinderence to the wildfire.
Sent from my GT-I9100 using xda premium
Well the title says it all ,my phone randomly restarts while i am using it since started using arhd so is there any solutions?
Sent from my HTC One X using Tapatalk 2
Are you overclocking or undervolting?
Michealtbh said:
Are you overclocking or undervolting?
Click to expand...
Click to collapse
i think what i am doing is called underclocking , i am just making max clock speed 1 ghz
that sudden rebooting means you're doing something that crashes your phone... probably the underclocking that causes this.
bit weird though as the hox has many speeds at which it can run, 1ghz being one off them.
Are you sure you didn't also undervolt your hox and that you're using an app that is 100 percent compatible?
Try running the hox at standard speeds to make sure it's not a hardware problem and using an other app to make sure it's not the app causing problems.
Sent from my HTC One X using Tapatalk 2
I am using set cpu ,but i tried to uninstall it and so far so good but whats awkward is i always use set cpu and this problm never happened .. and about the undervolting i dont even know how to do it.
Sent from my HTC One X using Tapatalk 2
strange, but as your not experiencing any problems after uninstalling set CPU it probably has something to do with it... maybe it's a wrong setting / are you sure set CPU is compatible with hox?
Try contacting the programmer of set CPU about this, or try another tool.
undervolting means setting a lower voltage than standard for your hardware, in this case the CPU.
This makes it spend less energy and thus generate less heat. Undervolting can be used as a battery saver (use less energy) just as underclocking.
Sent from my HTC One X using Tapatalk 2
TheJoker79 said:
strange, but as your not experiencing any problems after uninstalling set CPU it probably has something to do with it... maybe it's a wrong setting / are you sure set CPU is compatible with hox?
Try contacting the programmer of set CPU about this, or try another tool.
undervolting means setting a lower voltage than standard for your hardware, in this case the CPU.
This makes it spend less energy and thus generate less heat. Undervolting can be used as a battery saver (use less energy) just as underclocking.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Set CPU doesn't support the hox, system tuner does however.
@vorticalbox tweet me
Hello,
First sorry for my bad English. What is the UV and ExUV? This is harmfull for telephone?
And
Note: If you got boot-loop with ExUV edition try Normal UV because your phone doesnt
supoort Very Low Voltages..
Click to expand...
Click to collapse
Say this in kernel topic. I think all galaxy wonders are same it's wrong? All phones are different?
TheAreS said:
Hello,
First sorry for my bad English. What is the UV and ExUV? This is harmfull for telephone?
And
Say this in kernel topic. I think all galaxy wonders are same it's wrong? All phones are different?
Click to expand...
Click to collapse
UV is simply "Undervolt", which means reducing the voltage of a component, usually the processor, reducing temperature and cooling requirements. Another benefit of undervolting is conservation of battery power. ExUV is Extremely Undervolted. Some phones cannot simply handle too much undervolting resulting to phone unreliability or reboots.
UV = Undervolt
ExUV = Extreme Undervolt
The phones have some different things, there are some Galaxy Ws with LCD panel rev1, rev2 and rev3. Some GWs get bootloop when the boot is overclocked and some GWs can't work with extreme undervolt, just undervolt.
Enviado de meu GT-I8150 usando Tapatalk 4
I want to ask, Undervolt means underclock?