CPU temp works now on gb ...average temp around 110f
battery 93f
app....temp monitor
Sent from my DROID X2 using XDA Premium App
rsswga said:
CPU temp works now on gb ...average temp around 110f
battery 93f
app....temp monitor
Sent from my DROID X2 using XDA Premium App
Click to expand...
Click to collapse
I've Seen Mine Up To 65 ºC / 149 ºF.
rsswga said:
CPU temp works now on gb ...average temp around 110f
battery 93f
app....temp monitor
Sent from my DROID X2 using XDA Premium App
Click to expand...
Click to collapse
I've seen my CPU be hotter after the gingerbread update but that might just be cuz the second core is in use.
anytime im outside phone gets out with little use ..I guess its normal since it's usually 90+ degrees out ..120 in no time
Sent from my DROID X2 using XDA Premium App
diabloking said:
I've seen my CPU be hotter after the gingerbread update but that might just be cuz the second core is in use.
Click to expand...
Click to collapse
The second one is suppose to make cpu temp lower cause ones not doing all the work ..or so I heard.
Related
With CM7 my Batt = 40°C and CPU=53°C is that too hot. It happens after about 20 minutes of normal use. I'm on cm7 beta. i'm running everything default, which I believe is 1100 mhz. Let me know what you guys think.
Seems fine to me. I have setcpu set to lower clock speed at 65C, but rarely get to 60C. I see nothing wrong with your temps.
Assimilated via WinBorg 4G
I think as long as the CPU doesn't go over 60 you're good
Sent from my MB860 using XDA App
IUH1991 said:
I think as long as the CPU doesn't go over 60 you're good
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
That's correct. Its only after you go beyond 60 that you start getting into trouble. You're fine if you're topping out at 53.
The only issue IMO is that above 40 on the battery is that the battery does tend to drain faster...
Sent from my GT-I9000 using xda premium
After an hour of use or so, I got to 63C on the CPU? What should I do?
Sent from my MB860 using XDA App
jake.perkinsr said:
After an hour of use or so, I got to 63C on the CPU? What should I do?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
What were you doing on your phone, which kernel do you have installed, and what radio are you using?
I was just randomly doing stuff, including surfing, Netflix etc. my kernel is 2.6.32.39-mb860-cm7-Karanalmod stock cm7 beta and my radio is N_01.77.30 P
Sent from my MB860 using XDA App
jake.perkinsr said:
I was just randomly doing stuff, including surfing, Netflix etc. my kernel is 2.6.32.39-mb860-cm7-Karanalmod stock cm7 beta and my radio is N_01.77.30 P
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Hmm, try flashing the enhanced 1.0 GHz kernel and try some undervolting. Overclocking, while resulting in increase speed, leads to more heat production as the CPU is forced to do more work. Simply setting the CPU to 1.0GHz on setcpu won't cut it yet as the app only changes the clock speed for the main core. As the second core is switched on, the CPU reverts back to 1.1 (or whatever the highest speed is).
Where do I get that kernel?
Sent from my MB860 using XDA App
Look up faux's thread in the dev section
This may be a dumb question but has underclocking a CPU been shown to damage it at all? Be it longterm or short? I know excessive overclocking can take it's toll on the life of a processor and was just wondering if the opposite was true also.
Sent from my MB855 using xda premium
Well I'll answer with my common sense: I don't see a negative effect on the chip. Underclocking too much could effect your performance and might cause reboots. Best way to go about it is trial and error. Find a stable setting and go from there.
Sent from my MB855 using xda premium
radrian92 said:
Well I'll answer with my common sense: I don't see a negative effect on the chip. Underclocking too much could effect your performance and might cause reboots. Best way to go about it is trial and error. Find a stable setting and go from there.
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
I'm not asking about stability...I'm asking about actual damage. I'm aware of what underclocking does to phone performanne. I'm asking if someone knows either from experience or from information available somewhere if it can physically damage the processor...not just an assumption...but thank you anyhow.
Sent from my MB855 using xda premium
Underclocking does not damage anything hardware wise. In fact all recent processors do it very often for energy efficiency reasons. Your phone its probably doing it right now. It will go to its stock rated speed (1 GHz for photon) when you run a game or something else system intensive and it will clock back down to 216 GHz (lowest stock rated speed) when you quit or anywhere imbetween depending on load.
Sent from my MB855 using xda premium
EDIT: Meant 216 MHz. Sorry.
MultiDev said:
Underclocking does not damage anything hardware wise. In fact all recent processors do it very often for energy efficiency reasons. Your phone its probably doing it right now. It will go to its stock rated speed (1 GHz for photon) when you run a game or something else system intensive and it will clock back down to 216 GHz (lowest stock rated speed) when you quit or anywhere imbetween depending on load.
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
Holy crud, 216 ghz????
Sent from my MB855 using xda premium
You cant underclock below what it was designed for and my regular kernels keep voltage below safe values so.....
Sent from my MB855 using XDA App
MultiDev said:
Underclocking does not damage anything hardware wise. In fact all recent processors do it very often for energy efficiency reasons. Your phone its probably doing it right now. It will go to its stock rated speed (1 GHz for photon) when you run a game or something else system intensive and it will clock back down to 216 GHz (lowest stock rated speed) when you quit or anywhere imbetween depending on load.
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
Now this makes sense...thank you.
Sent from my MB855 using xda premium
magui43212 said:
Holy crud, 216 ghz????
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
Its 216 Mhz...lol
Sent from my MB855 using xda premium
Yeah it shouldn't really have to much of an effect seeing as you are basically allowing it to do less. Just as long as you are not running to much for it to handle at its underclocked speed.... In theory at least.
I run both OC and UC setups depending upon what I'm doing IE "Charging" or "Screen off". And I've yet to see any negative effects.
Well seeing uderclocking makes it so its "walking" instead of "running" so it should be able to keep its "breath" longer.. less stress does usally me longer life. So i would say it helps your phone life overall and battery life longer overall
Sent from my MB855 using xda premium
No its like running with less weight
Damanis1 said:
Well seeing uderclocking makes it so its "walking" instead of "running" so it should be able to keep its "breath" longer.. less stress does usally me longer life. So i would say it helps your phone life overall and battery life longer overall
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
Who prefers LiveOC over the regular OC system?
Just wondering.
Sent from my SCH-I500 using XDA App
I prefer to use voltage control and overclock the ol' fashioned way lol...I have played with nstools and live oc, but its more than I really need.
110%, 1320 mhz, stock voltages
Sent from my SCH-I500 using xda premium
neh4pres said:
110%, 1320 mhz, stock voltages
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
Which governor do you use? GlitchOndemand
Glitchass v2
Conservative
Interactive
Powersave
Performance
Lazy
Smoothass
Sent from my SCH-I500 using XDA App
i use glitchondemand/ fiops overclocked @ 1500mhz with no undervolt.
Enyo. said:
Which governor do you use? GlitchOndemand
Glitchass v2
Conservative
Interactive
Powersave
Performance
Lazy
Smoothass
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Stock..
Sent from my SCH-I500 using xda premium
droidstyle said:
i use glitchondemand/ fiops overclocked @ 1500mhz with no undervolt.
Click to expand...
Click to collapse
No heat?
Is this dangerous? With no overheat, is this dangerous? Are you using this day to day?
Didn't get into oc too much.
neh4pres said:
Stock..
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
thanks so much
Sent from my SCH-I500 using XDA App
Enyo. said:
No heat?
Is this dangerous? With no overheat, is this dangerous?
I've never overclocked this high before. Didn't get into oc too much.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
So.. You never tested 1.9 ghz before you released your kang kernel?
Sent from my SCH-I500 using xda premium
neh4pres said:
So.. You never tested 1.9 ghz before you released your kang kernel?
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
I tested it.
For a day or two.
But using my phone day to day.
Sent from my SCH-I500 using XDA App
enyo... I have tested with glitch kernel at 1.7 ghz and i currently hold the record benchmark for this device on antutu using performance governor. After testing for a half hour at that speed i fell asleep with the phone stuck at that speed. I'm typing this message with that phone now. That was done with glitch v13. The most i ever got from high clock speeds was freezes and reboots.
However, if you get stupid with live oc the story can be very different.
But to give an idea of what my phone handled back then, go to the cm7 glitch thread and check what the gpu/buss speed was at 1.7ghz. But remember that those bus/cpu speeds, and voltages were finely tuned by tk , and you probably won't be able to push that hard with live oc.
Sent from my SCH-I500 using xda premium
neh4pres said:
enyo... I have tested with glitch kernel at 1.7 ghz and i currently hold the record benchmark for this device on antutu using performance governor. After testing for a half hour at that speed i fell asleep with the phone stuck at that speed. I'm typing this message with that phone now. That was done with glitch v13. The most i ever got from high clock speeds was freezes and reboots.
However, if you get stupid with live oc the story can be very different.
But to give an idea of what my phone handled back then, go to the cm7 glitch thread and check what the gpu/buss speed was at 1.7ghz. But remember that those bus/cpu speeds, and voltages were finely tuned by tk , and you probably won't be able to push that hard with live oc.
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
So just overclocking, @ 1.5GHz or 1.2GHz and, monitoring the temp, processor will last just as long as it would non overclocked?
Sent from my SCH-I500 using XDA App
Enyo. said:
So just overclocking, @ 1.5GHz or 1.2GHz and, monitoring the temp, processor will last just as long as it would non overclocked?
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
It's all luck. Chance. Fate. If tk has not burned his phone yet i would say you have a lot of catching up to do to get the mileage he has. I had mine overclocked 1.5ghz for a few months.. And guess what, i have never monitored temp. But hey, i pay an extra couple dollars a month on top of insurance for lifetime warrantee. So i think my phone burning up would fall under that. But anyway, your stressing out to much over it.
Sent from my SCH-I500 using xda premium
neh4pres said:
It's all luck. Chance. Fate. If tk has not burned his phone yet i would say you have a lot of catching up to do to get the mileage he has. I had mine overclocked 1.5ghz for a few months.. And guess what, i have never monitored temp. But hey, i pay an extra couple dollars a month on top of insurance for lifetime warrantee. So i think my phone burning up would fall under that. But anyway, your stressing out to much over it.
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
Thanks so much.
Going to over clock to 1.5, not going to stress about it. Ulcers come like that
Sent from my SCH-I500 using XDA App
no heat and i use it daily...first time i can ever say this when overclocking to 1500. i agree with neh4pres posts...becareful with live oc it can screw your device up quick. most folks will never see any benifit by using live oc imo anyway. part of the reason why i just use vc...
I actually use 10% live oc and 1200mhz step... All voltages stock. Fully stable and it FLIES
Sent from my SCH-I500 using xda premium
I must have every bit of speed. That said here's the setup:
ICS AKOP 25 Glitch 14 B5 for 6.0
1200 step with 118 LOC
Glitch OnDemand with some OV and UV. (see pics)
Live OC is the way to go as you get a boost to your GPU and RAM in addition to the usual CPU bump.
thisguy23 said:
I must have every bit of speed. That said here's the setup:
ICS AKOP 25 Glitch 14 B5 for 6.0
1200 step with 118 LOC
Glitch OnDemand with some OV and UV. (see pics)
Click to expand...
Click to collapse
thx a bunch for this nfo. just used ur voltage settings for my device and was able to overclock into the 1300mhz range from the 1200 step. im impressed since last time it was very unstable at 1200 for me.
thx.
swagooo said:
thx a bunch for this nfo. just used ur voltage settings for my device and was able to overclock into the 1300mhz range from the 1200 step. im impressed since last time it was very unstable at 1200 for me.
thx.
Click to expand...
Click to collapse
with the devil kernel i have been running 102% loc between 200-1000mhz. on glitch i can oc up to 1500mhz with no loc, soon as i add any loc the device freezes. im guessing my leakage is not dialed in correctly for glitch, also i get a bit nervous playing wit arm voltages.
droidstyle said:
with the devil kernel i have been running 102% loc between 200-1000mhz. on glitch i can oc up to 1500mhz with no loc, soon as i add any loc the device freezes. im guessing my leakage is not dialed in correctly for glitch, also i get a bit nervous playing wit arm voltages.
Click to expand...
Click to collapse
Try these i have not had a reboot in over a week
Sent from my SCH-I500 using xda premium
Hi everyone, I'm running houstonn's RootBox w/ his 167MHz kernel. Can someone post a screenshot of their CPU voltages? These are the ones Im using, I'm not sure if they are too low.
Sent from my Optimus G using xda premium
I find that anything under 700000 leads to instability on my phone, but if that works for you, by all means go for it.
wow, im using mystery kernel and i can't set below 800mv, use both kernel tuner and faux clock.
Been using this for a day, everything seems to work fine. I keep my max CPU at 702MHz and max GPU at 325
Edit- I also keep two cores completely offline.
Sent from my Optimus G using xda premium
Tyler44346 said:
Been using this for a day, everything seems to work fine. I keep my max CPU at 702MHz and max GPU at 325
Edit- I also keep two cores completely offline.
Sent from my Optimus G using xda premium
Click to expand...
Click to collapse
... Do you go a week between access to electricity?
Sent via LG E970 with houstonn aokp 4.2.2
Tyler44346 said:
Been using this for a day, everything seems to work fine. I keep my max CPU at 702MHz and max GPU at 325
Edit- I also keep two cores completely offline.
Sent from my Optimus G using xda premium
Click to expand...
Click to collapse
What's the point of max 702MHz? That's slower than my old HTC Aria...
I know to each their own, but that just seems to defeat the purpose of having a quad core smartphone.
Sent from my Optimus G using xda app-developers app
Jank4AU said:
What's the point of max 702MHz? That's slower than my old HTC Aria...
I know to each their own, but that just seems to defeat the purpose of having a quad core smartphone.
Sent from my Optimus G using xda app-developers app
Click to expand...
Click to collapse
I agree. With a decent governor, the device spends very little time at higher frequencies anyway, so there is relatively little additional battery drain... But I would imagine you'd run into a fair bit of lag for those times when the higher frequencies are needed...
Sent from my Optimus G using Tapatalk 4 Beta
dandrumheller said:
I agree. With a decent governor, the device spends very little time at higher frequencies anyway, so there is relatively little additional battery drain... But I would imagine you'd run into a fair bit of lag for those times when the higher frequencies are needed...
Sent from my Optimus G using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yeah, that's what I was thinking. Can't be terribly snappy with that setup.
Sent from my Optimus G using xda app-developers app
Like you guys said, with a great chipset, using low frequencies doesn't really take away from the performance, I only notice a slight difference, but my battery was lasting about 1 day 8 hours with 3-4 hours screen on and WiFi on, one to three bars, so not much battery gain. That's why I only used this for a few days testing. That's the whole reason why I posted this thread, I'm trying different settings.
Sent from my LG-E970 using xda premium
Seeing that I don't see one of these posts on here yet why don't we start a post about what ROM/kernel/and how good your battery life is I'm running beanstalk 4.3.1 and toolchains kernel and get 20 hours of heavy usage !
Sent from my Optimus G using xda app-developers app
mr turtle droid said:
Seeing that I don't see one of these posts on here yet why don't we start a post about what ROM/kernel/and how good your battery life is I'm running beanstalk 4.3.1 and toolchains kernel and get 20 hours of heavy usage !
Sent from my Optimus G using xda app-developers app
Click to expand...
Click to collapse
Post a screen shot of battery usage.
Unfortunatly my og kept crashing and I gave up with that ROM and now my battery's terrible:'(
Sent from my Optimus G using xda app-developers app
I dug into my screenshots and found this/this was a full day (I didn't charge it overnight)
Sent from my Optimus G using xda app-developers app
mr turtle droid said:
I dug into my screenshots and found this/this was a full day (I didn't charge it overnight)
Sent from my Optimus G using xda app-developers app
Click to expand...
Click to collapse
15 hours at 1.0 ghz? Holy cow! You should change the minimum frequency to the lowest setting. You will get waaaay better battery life.
Well I undervolted it by I think by 200 MV?
Sent from my Optimus G using xda app-developers app
MiZrY said:
15 hours at 1.0 ghz? Holy cow! You should change the minimum frequency to the lowest setting. You will get waaaay better battery life.
Click to expand...
Click to collapse
He's better off figuring out what app is keeping the phone awake so much. 14% deep sleep is horrible. Though. 21 plus hours up with that little deep sleep isn't too bad. Mpdecision turned on by any chance? That might explain the min cpu at 1ghz.
Sent from my Optimus G using Tapatalk
Yea mpdecision is on
Sent from my Optimus G using xda app-developers app
with the mpdecision turned off I noticed my battery drains a little faster
Sent From My Liberated E970
mr turtle droid said:
with the mpdecision turned off I noticed my battery drains a little faster
Sent From My Liberated E970
Click to expand...
Click to collapse
I'm assuming you are using 4.4 so battery apps like BBS do not work on 4.4 so it will be a little more difficult to isolate what drains your battery.
Post a sn of the OS battery stats and trickster showing deep sleep time.
Also did you lower you minimum frequency, or are you still running at 1ghz at idle?
Sent from my LG Optimus G using xda app-developers app
I figured out why it was running at 1ghz and im currently running slimbean 4.3.1 build 2 and undervolted by 150 MV with my freq set 384-1512
Sent From My Liberated E970