After searching XDA, reddit, and another plethora of forums, I've been unable to get a real hold on cpu temperature reading for the thunderbolt running dream kernel 2.3+ with das bamf sense 3.0. Are there any apps for this set of software that will be able to tell me the cpu temperature?
If not, is there another kernel I could flash to enable it on setcpu or a similar app?
Thanks (and sorry if the answer is in an obscure post I missed).
youarealwaysthereMD said:
After searching XDA, reddit, and another plethora of forums, I've been unable to get a real hold on cpu temperature reading for the thunderbolt running dream kernel 2.3+ with das bamf sense 3.0. Are there any apps for this set of software that will be able to tell me the cpu temperature?
If not, is there another kernel I could flash to enable it on setcpu or a similar app?
Thanks (and sorry if the answer is in an obscure post I missed).
Click to expand...
Click to collapse
SetCPU should do the trick.
Sent from my ADR6400L using XDA Premium App
Is there a way to get setcpu to show the cpu temperature? In system info I can only find battery temperature. And it appears as though the widget shows battery temperature as well.
Thanks.
The battery is a good measuring stick because if the CPU starts getting real hot from over use, the battery will too, since the CPU is gonna be sucking juice. I don't know of anything to measure actual CPU temp though. Sorry.
Message delivered via my BAMF Thunderbolt
youarealwaysthereMD said:
After searching XDA, reddit, and another plethora of forums, I've been unable to get a real hold on cpu temperature reading for the thunderbolt running dream kernel 2.3+ with das bamf sense 3.0. Are there any apps for this set of software that will be able to tell me the cpu temperature?
If not, is there another kernel I could flash to enable it on setcpu or a similar app?
Thanks (and sorry if the answer is in an obscure post I missed).
Click to expand...
Click to collapse
im not 100% sure, but i think there is a widget for setcpu and it will give you the readings you are looking for.
Thank you all. It seems as though the setcpu widget will give the CPU temp, but it is usually near or the same as the battery temp. Either that or the thunderbolt doesn't really have a dedicated sensor (such as the OMAP one).
EFoxwell said:
The battery is a good measuring stick because if the CPU starts getting real hot from over use, the battery will too, since the CPU is gonna be sucking juice. I don't know of anything to measure actual CPU temp though. Sorry.
Message delivered via my BAMF Thunderbolt
Click to expand...
Click to collapse
But there may be cases where the battery is damaged, water or steam damage can occur and it might give a wrong reading (hapened to a cellphone i bought from a friend that was water damaged, got my money back though)
Related
In my neverending attempt to extend my battery life, I installed SetCPU. The underclocking with profiles has extended my battery some, but Id like more.
I know very little about undervolting, its a new concept to me. Could someone elaborate on it, and may've suggest voltages for each speed setting? I hear it can do wonders for battery life.
Sent from my MB860 using XDA App
just experiment, start with small increments (don't save your settings!!!) see if it reboots, if its stable for a day or two, increase it, when it starts crashing dial it back a notch.
Just like overclocking except in reverse and with voltage basically.
note I'm not sure re: kernel requirements, I haven't tried it yet with my atrix, and my current ROM runs stock kernel I think.
its hit and miss, for example on my SGTab I can't undervolt at all or else it crashes all the time, others get away with -100mAh across the board (bastards), but mine is happy on 1.1OC.
WTFsandwich said:
In my neverending attempt to extend my battery life, I installed SetCPU. The underclocking with profiles has extended my battery some, but Id like more.
I know very little about undervolting, its a new concept to me. Could someone elaborate on it, and may've suggest voltages for each speed setting? I hear it can do wonders for battery life.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
If you like cars it seem this will be the best way to explain it
http://forum.xda-developers.com/showpost.php?p=15947019&postcount=643
That is an excellent analogy. Basically, trial and error?
Sent from my MB860 using XDA App
Yes, start conservative.
Another way to use setcpu to improve your battery life is to set a screen off profile to restrict the CPU speed to minimum when the screen is off.
I tried that one, but it kept stalling my phone when turning the screen back on when it was at the bare minimum.
EDIT: For anyone wondering, -75 seems to cause frequent freezes.
Sent from my MB860 using XDA App
mramirezusa said:
If you like phones it seem this will be the best way to explain it
Think of it as tweaking the CPU of a phone to use just enough power to prevent it from failing in order to conserve battery life without affecting it's normal operation.
Click to expand...
Click to collapse
Fixed that for ya!
WTFsandwich said:
That is an excellent analogy. Basically, trial and error?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Any overclocking or underclocking is always trial and error. Rule of thumb is to only ever change one thing at a time in small increments, then test before adjusting again. Your approach should be methodical and not haphazard, i.e. in a PC change cpu clock speed in small increments until you fail to boot or BSOD, then change voltage in small increments until you boot and are stable again. Monitor temperatures all the time, and add cooling if necessary. If you take a methodical approach, and don't rush things, you can achieve surprising results with hardware/software tweaking.
What would be a good way to test once I increment a voltage?
Sent from my MB860 using XDA App
A good test is to just use it as you normally would. If the phone doesn't reboot, you're good to go.
Sent from my MB860 using XDA App
edit: pls delete
So, I had checked off set at boot on the voltage screen. Unfortunately, this has rendered my phone to continually reboot and freeze, as one voltage is too low.
I do have a nandroid backup from right before installing SetCPU, and backups of working voltages, but I can't get the working ones restored before SetCPU starts and freezes my phone.
Is there a way I can default or disable the SetCPU settings without having to reflash the ROM or a backup of it?
WTFsandwich said:
What would be a good way to test once I increment a voltage?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Do something CPU intensive also to see if it crashes, like play a game. You want to stretch the phone to the limits to test it at the most extreme condition you will use it under.
WTFsandwich said:
So, I had checked off set at boot on the voltage screen. Unfortunately, this has rendered my phone to continually reboot and freeze, as one voltage is too low.
I do have a nandroid backup from right before installing SetCPU, and backups of working voltages, but I can't get the working ones restored before SetCPU starts and freezes my phone.
Is there a way I can default or disable the SetCPU settings without having to reflash the ROM or a backup of it?
Click to expand...
Click to collapse
Maybe a factory/data wipe?
Other than that I can't think of anything myself.
ddddddddddddd
you may try to use default stock kernel, on wich overcloking do not work.
re: setcpu, sorry I think you have to reflash... thats why you don't save the settings until you're sure
there is no shortcut way.... you may be fine for a day but next day it keeps crashing. Happened to me on my SG tab when I went to 1.2 for example, I thought it was hunky dory then a few days later crashing galore.
the longer you leave it for the better you are, its really your call to make. Some people prefer the extra speed and will live with a crash or two a week (not me, its my phone not gaming pc lol).
not sure how much stress testing you can/should do. Back when I was OCing PCs I would leave stress tests running overnight, but probably not a good idea to 100% CPU a phone overnight lol
Hey guys, anyone have a good idea of what some safe undervolting values would be? I was just going to play around with them and not set it on reboot so I could just pull the battery, but I am unsure of how irreversible the damage could possibly be, if any.
I am running: Senseless 1.0
dsb's kernel
I actually have it underclocked slightly because I don't play games, and when I do they are something like Angry Birds, or Words when I am bored.
Bump, out of all of you who have undervolted none of you know any good values?
AtLemacks said:
Bump, out of all of you who have undervolted none of you know any good values?
Click to expand...
Click to collapse
Well, since no one will answer, I will
I generally only keep it undervolted -50mV across the board. That's just my usual set up to get a tiny bit more from the battery. The furthest I've gone is -200mV at the top. I didn't keep it like that for long, but everything seemed to run smoothly still. I'm sure I could go much lower, but I'm kind of afraid to until I know more about it.
I'm just starting to work on undervolting today since I found a kernel that works really well. I'll let you know what my phone is stable at.
WasabiWa83 said:
Well, since no one will answer, I will
I generally only keep it undervolted -50mV across the board. That's just my usual set up to get a tiny bit more from the battery. The furthest I've gone is -200mV at the top. I didn't keep it like that for long, but everything seemed to run smoothly still. I'm sure I could go much lower, but I'm kind of afraid to until I know more about it.
Click to expand...
Click to collapse
Cool, I didn't know what was "too much". How much better battery life did you see from -50?
Evo4gLI said:
I'm just starting to work on undervolting today since I found a kernel that works really well. I'll let you know what my phone is stable at.
Click to expand...
Click to collapse
Which Kernel are you running?
At -50mV across all frequencies, it reeeally varies. I never have a "normal" day with this phone. But, the shortest I've had using Ziggy's kernel from 192-1836gHz with on demand governor is around 7 hours. That was pretty heavy usage for me. Some games like Dead Space and Captain America, tons of internet, Pulse, texting, a few phone calls, music, and a little Netflix at night. The longest I've had has been 20+ hours. That's with very little gaming, a little internet, and mostly just texting. Stock battery, bump charged.
I'm really afraid to go too low, though. One time I was just seeing what would happen if I kept lowering it across all of the frequencies and it froze, then crashed. Had to battery pull to get it to work again.
I run DSB Kernel with SmartAssV2 underclocked to 1296, and before undervolting on my OEM battery I got 13 hours with a little over normal usage. Screen was on for about 2 hours total. On my extended battery I got like 27 1/2 hours, but obviously some of that time was overnight.
2 hours later I am still above 90% this is what I like to see! If I can get 15 hours on OEM battery, my extended battery will stay in my truck as my backup!
AtLemacks said:
2 hours later I am still above 90% this is what I like to see! If I can get 15 hours on OEM battery, my extended battery will stay in my truck as my backup!
Click to expand...
Click to collapse
Might mess with this, I am running same kernel same governor. How much did you undervolt in the end? I was gonna push-100 on each and see how it goes...
Sent from my ADR6425LVW using XDA App
I went -50 across the board, using dsb kernel, underclocked to 1028, and everything is stable.
Sent from my HTC Rezound via Tapatalk
nosympathy said:
Might mess with this, I am running same kernel same governor. How much did you undervolt in the end? I was gonna push-100 on each and see how it goes...
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
Just -50, but I updated the kernel and forgot to remove the PH98IMG prior so I set the phone into bootloops. Had to factory reset(after trying everything else) and start over from backups.
Evo4gLI said:
I went -50 across the board, using dsb kernel, underclocked to 1028, and everything is stable.
Sent from my HTC Rezound via Tapatalk
Click to expand...
Click to collapse
See, I don't get the overclocking hype. It isn't hard to overclock when needed, so I feel underclocking is the better choice for battery life. The phone is fast as hell no matter what.
I may try to do some undervolting...but I am running clean rom 1.3 and dsb's smartass kernel, and I have been getting good battery life for what I use my phone for. I do have it overclocked though (on demand).
You won't damage the phone with undervolting. I mean a lockup might be a pain, but it won't damage the phone. Overvolting on the other hand could ruin the phone.
I will probably just stick with -50 across the board for now, I am tempted to pay for the full version just so I can save profiles and not have to set on boot.
Late reply but running AOKP w/ frAnco I UV -100 with no issues at all.
Running -75 on everything with incredikernel
bendirkss said:
Late reply but running AOKP w/ frAnco I UV -100 with no issues at all.
Click to expand...
Click to collapse
You sir must be using a Gnex. LOL
So far I've just been using SetCPU for over/underclocking but have never messed with undervolting. I was wondering what most people use if your main priority is undervolting for better battery life. I'm running Siyah 2.6.7 with SHOstock ROM. Any help/feedback is appreciated.
mpkothari said:
So far I've just been using SetCPU for over/underclocking but have never messed with undervolting. I was wondering what most people use if your main priority is undervolting for better battery life. I'm running Siyah 2.6.7 with SHOstock ROM. Any help/feedback is appreciated.
Click to expand...
Click to collapse
Well, undervolting is very tricky. Each CPU differs in its ability to undervolt, so settings that work for one may not work for others. You'd have to do some testing. I recommend either a.) undervolting one tick and run AnTuTu benchmark multiple times as well as a demanding game/app (Run them for a long time), or b.) undervolting one tick and using your phone normally as per your current usage and if by the next morning it's still running as normal, repeat one tick.
Do NOT set "Set on Boot" to on until you've run these tests and have had no issues.
Hope this helps a little.
Do not worry about 1400,1600 mhz till later since that's when your overclocking.
Bump everything else down by 25mv, run the stress test and a few intensive programs like benchmarks/games.
Keep doing that till you start to notice problems and then revert to the best setting you had. (make sure to backup or not set on boot)
Once you go through all that then you can do it for individual mhz and see which can still be lowered.
This should keep you busy for a hour or so.
I'll share what I posted in another thread. Doing stress tests are fine, but if you test throughout the course of a day or more, you have the opportunity to come across situations you might not think of during testing.
Simba501 said:
Ouch....I think the best way to experiment with undervolting is to use Voltage Control. Save the stock settings as your boot settings (it saves everything - governor, frequencies, etc; so, make sure those are what you want them to be as well), then undervolt (at the beginning of the day). If you make it to the end of the day with typical usage, you can save those as your new boot settings. Undervolt further at the beginning of another day, etc. Once you make it to the point where you get locked up, voltage control will set the previous values at boot and you'll know that those are your limits.
EDIT: If you want to play it extra safe, run values for more than one day.
Click to expand...
Click to collapse
I'm at work right now trying not to get easily distracted by xda since I keep checking whether or not an ICS leak has been ported or something. Thanks guys for your much appreciated input. I've been running with all voltage values knocked down by 50mV with the exception of 1.4 and 1.6 GHz. Those I kept stock since I'm not overclocking. So far so good actually with sio/ondemand and Max 500 Mhz. It's surprisingly smooth and battery of course is doing exceptionally well at these settings. Switched over to voltage control for now.
Sent from my SAMSUNG-SGH-I777 using xda premium
I personally have become very fond of voltage control where as I'd previously been using set-cpu for nearly ever since the H1 and mytouch days. Voltage controls just allows more freedom and tweakability.
Alucardis666 said:
I personally have become very fond of voltage control where as I'd previously been using set-cpu for nearly ever since the H1 and mytouch days. Voltage controls just allows more freedom and tweakability.
Click to expand...
Click to collapse
Right there with you. just "converted" to Voltage Control. (thanks Simba!)
K Rich said:
Right there with you. just "converted" to Voltage Control. (thanks Simba!)
Click to expand...
Click to collapse
Heh, glad I'm not the only defector
Simba501 said:
I'll share what I posted in another thread. Doing stress tests are fine, but if you test throughout the course of a day or more, you have the opportunity to come across situations you might not think of during testing.
Click to expand...
Click to collapse
That's the post I was thinking of, I just honestly couldn't figure out where I saw it or who wrote it.
Many have complained about issues with the kernel in ICS. On any build, it is vital that you not use setcpu or any other cpu scaling app. Don't change the max/min freq, don't change the governer, nothing. Perflock will constantly reset any changes and cause the cpu to run at either full throttle or full min - no in between. Until we get kernel source and custom kernels, this will always be the case. It's something HTC does.
Many cpu monitor apps will do the same. The link in my sig has more info, and a link to a cpu monitor app that is safe to use with our kernel.
Actually when I was on the second ics leak, and setcpu worked fine. I know this because I benchmarked before and after setting frequencies
Sent from my ADR6425LVW using XDA
benchmarking doesn't mean it wasn't running at full tilt when you didn't need it to. unless your kernel magically doesn't include perflock, it was.
also, there are some combinations of setcpu and monitoring that will work. at one point if i used setcpu, cpu monitor, and one other which i forget now, it would work, kind of. definitely not recommended.
Thats why I deaded mine. Phone was constantly overheating
Sent from my ADR6425LVW using xda premium
since i stop fighting with the kernel i've had nothing but great battery life and performance since the first ICS leak.
tsp, what i don't understand is why something like system panel, which shows you scaling (but doesn't let you change it) showed the proper correct scaling between 384 and 1512 and hardly EVER hit full throttle on GB, but on ICS, it's always showing full throttle.
then i installed your widget you showed me, and it showed constantly chagning like system panel used to on GB.
any idea why? which one is rgiht??
tspderek said:
since i stop fighting with the kernel i've had nothing but great battery life and performance since the first ICS leak.
Click to expand...
Click to collapse
Agreed. I had set CPU try to disable perflock and limit to 1200mhz on conservative and it ended up being worse battery and slower overall.
You're exactly right I advise everyone I discuss the topic with to make sure and avoid trying to over ride perflock with a CPU management app. It causes a conflict in my opinion which is a huge battery drain and also causes excessive heat due to the process of fighting for its life.
Sent from my ADR6425LVW using xda premium
I've been saying this I even started a thread to smash this rumor of ICS kernels running bad...apparantely people like to give out wrong information on these forums, reminds me of the news channels.
THERE WAS NEVER ANYTHING WRONG WITH ANY ICS LEAKS. JUST USER FAULT
Sent from my ADR6425LVW using XDA
richii0207 said:
I've been saying this I even started a thread to smash this rumor if ICS kernels running bad...apparantely people like to give out wrong information on these forums, reminds me of the news channels
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
You are correct. I would say upwards of 20% of what I read here is incomplete or straight up wrong.
con247 said:
You are correct. I would say upwards of 20% of what I read here is incomplete or straight up wrong.
Click to expand...
Click to collapse
My favorite part is when they try to sound like a dev, I guess everyone's a dev on here ;-P. At least I only say something I know from EXPERIENCE and not what I read ;-)
Sent from my ADR6425LVW using XDA
jayochs said:
tsp, what i don't understand is why something like system panel, which shows you scaling (but doesn't let you change it) showed the proper correct scaling between 384 and 1512 and hardly EVER hit full throttle on GB, but on ICS, it's always showing full throttle.
then i installed your widget you showed me, and it showed constantly chagning like system panel used to on GB.
any idea why? which one is rgiht??
Click to expand...
Click to collapse
the widget i posted is what you want. it should be scaling up and down, and settling eventually when nothing is really going on. the system panel that you tried clearly affected the perflock in some way. from what i understand, some apps/widgets look at the cpu itself, while others hit up the kernel for status. the ones that hit up the kernel are the issue. i'm not 100% on this, that's just what i've been told. all i know is my experience seems to match this.
tspderek said:
Many have complained about issues with the kernel in ICS. On any build, it is vital that you not use setcpu or any other cpu scaling app. Don't change the max/min freq, don't change the governer, nothing. Perflock will constantly reset any changes and cause the cpu to run at either full throttle or full min - no in between. Until we get kernel source and custom kernels, this will always be the case. It's something HTC does.
Many cpu monitor apps will do the same. The link in my sig has more info, and a link to a cpu monitor app that is safe to use with our kernel.
Click to expand...
Click to collapse
Hmm, that's weird, cause I've been using setCPU with ICS on the Rezound for months and it works great! My CPU scales fine and hits all the frequencies its supposed to. The min and max frequencies do change around seemingly randomly, but anyone can see by watching the current frequency display that it is always somewhere in between the range I selected, and always appropriate for the system load.
I've always had CPU Master installed. I just removed it, we'll see how it goes.
Title says all. If possible, to how much can you overclock it?
Honestly, I don't know why you would overclock for anything other than bragging rights. this thing is fast.
All it needs is for the software to be optimized.
Undervolt is always good too.
Sorry for not really answering your question, but i'm sure it's possible. I mean, if you can undervolt, I'm sure you can overvolt and mess with the multiplier and all that jazz.
http://forum.xda-developers.com/showthread.php?t=2012320
That is what I'm talking about. International only though.
From what I've gathered from reading various posts, it is generally frowned upon as a bad idea for a variety of reasons, ultimately coming down to it will end up damaging your phone one way or another. So, yeah, of course, I'm sure you could find a way to do it, but if it were me I wouldn't(and this is coming from someone who overclocked every modern phone he's had except this one).
Once I see the trusted devs talking about it and saying it's a good idea...that's when I'll try it. Just my 2 cents.
SunnyChrono6 said:
Title says all. If possible, to how much can you overclock it?
Click to expand...
Click to collapse
well - if it behaves like the hox
you should be able to get about +15%
but why you want to do that at all
normally you only underclock this battery eater
Sent from my HTC One X+ using xda app-developers app
Well I haven't found a way. Besides, I think the phone would heat up to much anyways.
sixcarnage said:
Well I haven't found a way. Besides, I think the phone would heat up to much anyways.
Click to expand...
Click to collapse
well - no kernel is supporting it
so it will be hard for you to find a way
Sent from my HTC One X+ using xda app-developers app
Have you ever actually run into a situation where the phone does not have enough cpu power? I know I haven't but there have been many situations where I wished I if more battery Mah, what you really want to overclock is the gpu which is stable running at about 600mhz. The main reason why the cpu might not perform well is due to the cpu getting stuck in single core mode or failing to scale properly, just head over to nik3r's or maxwen's kernel threads and flash the latest version.
ryanjsoo said:
Have you ever actually run into a situation where the phone does not have enough cpu power? I know I haven't but there have been many situations where I wished I if more battery Mah, what you really want to overclock is the gpu which is stable running at about 600mhz. The main reason why the cpu might not perform well is due to the cpu getting stuck in single core mode or failing to scale properly, just head over to nik3r's or maxwen's kernel threads and flash the latest version.
Click to expand...
Click to collapse
Overclocking and people with EOS (Extreme Overclocking syndrome) care little about if they need the extra power for a purpose. There sole mission is to push a CPU as far as they dare without frying it
This is fine with a PC, as PC's have all manner of 3rd party cooling solutions. But I totally agree with everyone that trying to overclock the HOX+ CPU is futile and borderline stupid. It struggles to keep itself cool at the best of times. Putting the CPU through extra thermal stress for no reason and to gain little in the way of performance is not something I would risk....
---------- Post added at 09:57 AM ---------- Previous post was at 09:55 AM ----------
maxwen said:
well - no kernel is supporting it
so it will be hard for you to find a way
Sent from my HTC One X+ using xda app-developers app
Click to expand...
Click to collapse
Without being a ****.... He could just try and compile his own kernel. There are plenty of tuts on the subject and setting up the environment is not too difficult :silly: