So I finally overclocked my phone to about 710MHz. I know most ppl are overclocking theirs to about 748, but mine shuts off at this freq, so I just keep it at 710. Anyway, I'm just wondering if I need to worry about this taking a toll on my phone in the long run. I need the power, and I have it set to "on demand", but I don't wanna have it set that high if it's going to make the life of my phone shorter, or cause any other problems. I ask b/c I always read how you have to be very careful when overclocking.
Thanks, guys!
Related
So I just got a brand new D2G and thanks to the info in this forum I rooted it and installed fission rom and FRM...Im loving the phone, its fast, smooth and beautiful but the battery is AWFUL. I have read all the info about how to get the most out of your battery and everything on these forums but mine is waaaay worse than anyone has said before.
For instance, last night my phone was charging oernight, at 6 am when i woke up to pee it was at 100% so I unplugged it and went back to sleep, come 10 am when i woke up my phone was down to 15%!!! From just sitting there with the screen off...
Ive set the network to CDMA/Evduo automatic, installed Jrummy's overclock app...Can anyone explain in detail what exactly the settings in the overclock app mean? "set scaling frequencies at boot, cpu scaling frequencies etc?" for instance if I set scaling frequencies not at boot to ultra low voltage and 1 ghz and lower, do i need to also go into cpu scaling frequencies and make profiles and stuff?
Any information is greatly appreciated, Ive been reading up for days but this stuff is hard to find clear answers on specific issues. Thanks!
This is probably the most basic first thing to ask/do, but have you checked the battery useage to see which apps are using the most power? try doing what you did where you charged, and then let it sit for 4 hrs, and after that see what's using the battery, I bet there is some app that just nonstop uses the gps or 3g data or something wearing your battery life out super fast.
Yeah i looked at that this morning to see and all it said was suspend took up like 90% of the battery...Doesnt make any sense
1. Set at boot isn't what you're thinking. Set at boot means that whatever your current settings are will be set the NEXT time the phone boots. This is used when you have a setting you like. The reason you DON'T want to set at boot is that if you accidentally pick a setting that your phone doesn't like, and it makes it crash, then next time it will boot up with normal settings. Otherwise, you'd be looking at some work doing a recovery with either CWR or RSDLite... There are better ways to spend 30 minutes. Disclaimer: I use SetCPU, but the settings are all essentially the same.
2. For scaling, unless you're a power user (read: Geek) who's really up on his stuff, you should just stick with ondemand. This means your CPU will run at the lowest frequency possible, but will scale its speed up when processes call for it. This is efficient.
3. Yes, you should still make profiles. The setting on the main screen where you choose "Set at Boot" (Again, I'm speaking from SetCPU experience, but it SHOULD be the same) is just the main profile, setting the global minimum and maximum. You should leave the minimum on this at 300. The phones don't like to run much lower than that, even with the screen off; They start not ringing for calls, not waking up, etc. Set the maximum to whatever you want the max to be. You can overclock, which will obviously hurt your battery life. You could underclock and set the maximum to 1GHz, or even 800MHz, which would have a decent effect on battery life with no noticeable performance decrease to the average user. I run mine at the stock 1.2GHz and it's fast enough for my needs.
4. I wrote this thread to help people maximize their battery life. It's pretty detailed, you should give it a thorough read, it works well for me, and seems to work for others. I'm at 32hrs unplugged and my battery has gone from 90% to 20%. That's pretty light use, and I have an extended battery, but I still see over a day on my stock battery when I use it. There's a list of my SetCPU profiles there too, that might be helpful in setting up your own.
Thanks for the info on overclocking, I think I have it figured out now...
I will definitely read through your thread, but is it possible that I just had a bad battery? due to a shipping error, when verizon sent me my phone they sent 2 by accident so I just swapped out the battery for the other one and it seems to be doing much better already...
Is overclocking and underclocking too many times bad? Because usually when i'm not playing a game or traveling I underclock it low to save battery and overclock it when im on constant use. Is it bad to do it too many times?
If it's overheating, YES, ITS BAD, STOP.
Overclocking and underclocking just speed up/down the cpu.
Overclocking: The faster a cpu goes, the more likely it'll glitch (Which will usually cause a freeze or reboot in Android) and the more power it takes (Which increases heat, can melt parts). There are serious risks to overclocking. Luckily, you're more likely to crash than melt something, and if that happens just reflash the rom to get back to a lower speed (Might have to wipe the phone, depends).
Underclocking: There are no bad side effects from underclocking except maybe having a really slow phone. The Sensation is already underclocked to 1.2GHz (from 1.5GHz). Underclocking uses less power and thus drains less battery. Android naturally underclocks when it's not used heavily and every time the screen is dimmed / off.
If you haven't read up on it, though, you shouldn't be messing with it. To answer your question directly, no, constantly speeding up and slowing down the cpu won't hurt it. It does that on its own all the time.
Like the person above me said, 1.5 GHz is native frequency for this CPU. So, it won't hurt the CPU as long as you don't go higher than that.
Swyped from my HTC Sensation
Thanks for that info about what the standard clock is for the Sensation (before HTC changed it).
Now I know I can clock it to 1500 and feel safe about it.
Oh no no not that I already normally set it to 1.7 ghz and its ok.
Thats not how I meant. Let me rephrase it. Is it dangerous to o/c u/c too many times back and forth?
kripwalk said:
Oh no no not that I already normally set it to 1.7 ghz and its ok.
Thats not how I meant. Let me rephrase it. Is it dangerous to o/c u/c too many times back and forth?
Click to expand...
Click to collapse
I got a bit off topic, I know, sorry. Android is always changing its own clock speed. When there are no apps in the foreground, the cpu is underclocked as low as it can go. When the screen turns on, the cpu gets overclocked a bit (and when you play a game, the cpu gets overclocked a lot). There's no harm at all, because Android already goes back and forth. A lot. Boot up SetCPU and just watch the current CPU and you'll see it varies in real time.
What you're doing just changes the min/max values. Change them all you want. It won't hurt anything.
Is overclocking to, let's say, 1.4ghz safe? Won't it break the device and decrease life span?
mmmm as far as i fell for it. People change devices like clothing so to most it wouldn't matter. If you are going to have it for a long time then i would say you can do it but dont over due it to much and you would be fine. If the tablet can't handle it, it will just freeze or shut off and so on. Its relativity safe to do mostly.
Thanks for answering
I know it will obviously shorten battery life (by how much by the way?), but will it damage the CPU or the GPU of the phone?
I know that when overclocking a computer you have to be careful to not let the component get too hot, otherwise it could damage it.
KaiZ51 said:
I know it will obviously shorten battery life (by how much by the way?), but will it damage the CPU or the GPU of the phone?
I know that when overclocking a computer you have to be careful to not let the component get too hot, otherwise it could damage it.
Click to expand...
Click to collapse
probably is some harm. but if you ask my nexus s, that i bought in december, itll say that no harm has been done. all the time that it has spent from 1.4-1.6ghz, and still spends a lot of time there, has just made it want more
but really, every phone is different. some it might never harm, some it might harm right away. but ive have never heard of a nexus s that has actually been harmed from overclock. many phones cant overclock much, some can overclock a whole bunch(my phone), some cant even overclock. your phone will let you know when its been overclocked too much. and if it is too much, you can just overclock less/ and, btw, i still use my original battery, and get better battery life now than i did back when i just bought the phone.
This is my third time typing this... (This website should really have an auto-save draft feature)
I recently installed the application "CPU Tuner" because I've always wanted to utilize my newly rooted phone. The phone is running Cyanogenmod 7.2 Stable, and currently overclocked at 1.5GHz. My main concern is overclocking my phone that high. Now, I didn't really choose that option, SetCPU automatically set it to that when it loaded a configuration. I'm a beginner to overclocking, and this is my first time doing it for anything. I've heard rumors of people melting their processors from overclocking it, so I want to know if it's okay if its overclocked to roughly twice the stock frequency of 800MHz. If it IS safe, then why isn't the phone automatically set to 1GHz to compare to it's twin, the Evo 4G? Or perhaps even 1.2GHz to surpass it? I would definitely be satisfied with 1.2GHz, but I wouldn't mind having 1.5GHz if it was stable and didn't drain the battery. On to the next question, would an OC this high cause instability and/or would it drain my battery? I only overclocked an hour ago, so I haven't experienced any problems whatsoever... yet. On to the profiles... I'd like some suggestions for improving my triggers. Right now, it set everything up to the highest frequency, but looking at the help, it said to not touch the frequency, but experiment with thresholds. In the Help, it doesn't tell you what the thresholds are, and what they do, and more importantly, how they work. It just shows that the highest is the most battery saving. I would have thought the lower the better, but... Anyway, if you could tell me, I'd be highly appreciated it. Finally, the battery temperature... It has an option to enable a setting to change profiles if the battery gets a certain temperature, but I'd like to know what would be considered "Overheating". I get paranoid when the battery temperature gets a little warm at around 36 Celsius... but the profile it switches to is supposed to really slow down the CPU to preserve battery, so I'd really rather not use it unless it's necessary. So, would 45 - 50 Celsius do, or should I set it a bit lower? My battery is 4000+ mV, if that'd help at all. If you know any sources that you can direct me to that would answer my questions, it'd be highly appreciated.
Wow ok . Well first off check out THIS thread. It will explain a lot about Governors, I/O Schedulers, and a bunch of the questions you have. As for people melting CPUs, I've never actually seen it happen, or know anyone who has had it happen on the Shift. That's not to say it's not possible. It may be, just not probable. The Shift processor compared to the OG EVO's is much better. The Shift even at the stock 800mHz out performs the EVO's processor at 1000mHz. That is in part because it is a 2nd Gen processor vs the EVO's 1st Gen Unit. The Battery Temp should try and always be kept below 115-120 Degrees Fahrenheit. I use SetCPU, and have a Profile that kicks in to lower the OC to around Stock should the Battery Temp every reach 110 Degrees Fahrenheit. My setting are 61mHz Min 1516mHz Max, Smartass V2 Governor, and SIO Scheduler. But every device is different, so your going to have to do a bit of experimenting till you find what works for you. If you get a lot of Random Reboots, lower your Max OC setting, or try a different Governor. BTW where did you get a 4000mAh Battery?
prboy1969 said:
Wow ok . Well first off check out THIS thread. It will explain a lot about Governors, I/O Schedulers, and a bunch of the questions you have. As for people melting CPUs, I've never actually seen it happen, or know anyone who has had it happen on the Shift. That's not to say it's not possible. It may be, just not probable. The Shift processor compared to the OG EVO's is much better. The Shift even at the stock 800mHz out performs the EVO's processor at 1000mHz. That is in part because it is a 2nd Gen processor vs the EVO's 1st Gen Unit. The Battery Temp should try and always be kept below 115-120 Degrees Fahrenheit. I use SetCPU, and have a Profile that kicks in to lower the OC to around Stock should the Battery Temp every reach 110 Degrees Fahrenheit. My setting are 61mHz Min 1516mHz Max, Smartass V2 Governor, and SIO Scheduler. But every device is different, so your going to have to do a bit of experimenting till you find what works for you. If you get a lot of Random Reboots, lower your Max OC setting, or try a different Governor. BTW where did you get a 4000mAh Battery?
Click to expand...
Click to collapse
Thanks for the response. It's pretty late, so I've bookmarked the link to read tomorrow. Alright, so 45 degrees Celsius should the maximum then. I've been thinking of switching over to SetCPU, since there are more comprehensive guides than for CPU Tuner (In which no one seems to have heard about), and it doesn't seem that the settings it set will be ideal for the long run. Although, before I switch over to SetCPU, I want to at least give it a shot. I'll change my settings so that the frequency decreases depending on battery level. Also, I don't have much but the basic governors and configurations on CPU Tuner, so I've never heard of Smartass V2 (Prior to skimming through the link you posted). Also, the battery came with it, I knew it seemed a bit different from most other batteries (From what I've seen in searches, most of them had around 2000), but I didn't know it meant that much.
The Governor settings available will depend on the Kernel, not on the CPU Controller. I've always been partial to SetCPU, but that's just me. I would again suggest doing a bit of reading, and experimentation to find your best settings. But defiantly the closer to normal the Battery temperature is the better. When the Battery heats up to much it will in most cases also drain faster. If you can post a Pic of the Battery I would really like to see it. I've never come across a 400mAh Battery for the Shift.
When I first rooted my shift 2 years ago I was very concerned of over-heating. I constantly checked the temperature. After a while I realized it is quite hard to over heat and cause damage, especially with the newest kernels the devs have put out. Just experiment with different settings and see what works best for your phone
Sent from my PG06100 using xda app-developers app