If you have undervolted your Nexus 7 or any other tegra 3 based device please post the results here so I can throw them into a Excel sheet for development.
Using advanced mathematics and complex formulas I will make a undervolted kernel that's stable for everyone. For that, I need ideally 30 results or more. Less is ok but more or equal is better.
FORMAT 1:
CPU
- [FREQ1] [VOLTAGE1]
- [FREQ2] [VOLTAGE2]
- [FREQ3] [VOLTAGE3]
- ,,,
Click to expand...
Click to collapse
FORMAT 2:
CPU GLOBAL: [OFFSET]
Click to expand...
Click to collapse
I also accept 1 frequency result. You don't have to undervolt everything. I favor the last known voltage that crashes as well if you can send this I am even more happy.
Undervolted mine by 50mv
Sent from my Nexus 7 using Tapatalk 2
djjonastybe said:
If you have undervolted your Nexus 7 or any other tegra 3 based device please post the results here so I can throw them into a Excel sheet for development.
Using advanced mathematics and complex formulas I will make a undervolted kernel that's stable for everyone. For that, I need ideally 30 results or more. Less is ok but more or equal is better.
Click to expand...
Click to collapse
In order to use "advanced mathematics" and "complex formulas".. You might want to provide a format for "the results" you want people to provide.. Without a stream of formatted data to input your "complex formulas" and "advanced mathematics" is impossible..
"Advanced mathematics" and "complex formulas" sounds like you are doing an infomercial.
Pure waffle.
Sent from my GT-I9300 using xda premium
djjonastybe said:
..I will make a undervolted kernel that's stable for everyone
Click to expand...
Click to collapse
ha! good luck. considering some devices arent stable at all when undervolted just a tiny bit, and otbers are stable with a lot of undervolting, you have a tough road ahead of you.
simms22 said:
ha! good luck. considering some devices arent stable at all when undervolted just a tiny bit, and otbers are stable with a lot of undervolting, you have a tough road ahead of you.
Click to expand...
Click to collapse
I actually came back to post exactly this but Simms22 was too quick, as usual!
Sent from my GT-I9300 using xda premium
nodstuff said:
"Advanced mathematics" and "complex formulas" sounds like you are doing an infomercial.
Pure waffle.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I see you went with the more direct and honest approach. I tried being more subtle with my response.. :laugh: But yeah.. Marketing hype for a kernel.
styckx said:
I see you went with the more direct and honest approach. I tried being more subtle with my response.. :laugh: But yeah.. Marketing hype for a kernel.
Click to expand...
Click to collapse
Might as well be honest, set him on the right track early in his dev career rather than him rely on buzzwords and fud like some people do.
These are forums for android devices, not Apple devices, the reality distortion field doesn't work here, fancy marketing terms should be left at the door.
Sent from my GT-I9300 using xda premium
My Galaxy Nexus is proof of undervolting being unstable using software while being stable with manually programming the voltages. So I am going to give this a good shot anyway.
My Galaxy Nexus uses SmartReflex to undervolt.
Look at this table I made:
https://docs.google.com/spreadsheet/ccc?key=0AuqacKmGLKJ6dEdJZG5QTmNtQnoyYk0zbm5IanluMHc#gid=1
You see the core or gpu was already crashing at 974mV, which was the reason why I stopped undervolting using the thread. But don't give up, I tried again using SmartReflex because I felt I should be able to get lower. And now I am at 911mV but I did not try to get lower yet.
I plan on undervolting by actually programming it. I don't know how you guys undervolt for the Nexus 7, since I am fairly new with this device.
READ FIRST POST for formatting
nodstuff said:
"Advanced mathematics" and "complex formulas" sounds like you are doing an infomercial.
Pure waffle.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
http://en.wikipedia.org/wiki/Student's_t-distribution
Using that I can calculate which voltage to take that will work for 90% of us or 99% of us or maybe 100% ?
For that I need some results. The more the better.
The only voltage settings that will work for 100% of people are stock voltages.
you will run into endless problems if you release an undervolted kernel because what works for 75% of people won't work for the rest.
If you adjust voltages to include more people the people that can handle the lower voltages aren't getting the full savings their device can handle. Which defeats the point of releasing an undervolted kernel to save battery.
Undervolting should be up to the individual, just release with stock voltages and make a guide showing people how to undervolt.
Sent from my Nexus 7 using xda premium
nodstuff said:
The only voltage settings that will work for 100% of people are stock voltages.
you will run into endless problems if you release an undervolted kernel because what works for 75% of people won't work for the rest.
If you adjust voltages to include more people the people that can handle the lower voltages aren't getting the full savings their device can handle. Which defeats the point of releasing an undervolted kernel to save battery.
Undervolting should be up to the individual, just release with stock voltages and make a guide showing people how to undervolt.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
^^ Truth
I've done a bit of pc overclocking over the years and we'd always seek out the best steppings to find cpu batches that would give a better clock speed for less volts. What would work on one person's cpu wouldn't work on another sometimes even within the same stepping. (My current machine is getting long in the tooth but it's running a 33% OC below stock volts and stable as a rock.)
When the N7 cpu's are tested the stock voltage is the point where 100% of them will run without issue. Certainly there are many, maybe even most N7's that will run undervolted but until you try it you just won't know. Undervolting needs to be done on a case by case basis.
I uv by 100mv on every step on Franco kernel and I've never had a sod or reboot. Maybe you could release different versions like light, medium and heavy to cater to different users that have sets than can uv more or less. To address all these people naysaying I say just go for it, don't let these people dishearten you from what you want to do. I'm sure there will always be users who are willing to try
sorry to break the fun lol
Opened a thread with undervolting settings in different situation. For now i think its the lowest possible
bervin said:
I uv by 100mv on every step on Franco kernel and I've never had a sod or reboot. Maybe you could release different versions like light, medium and heavy to cater to different users that have sets than can uv more or less. To address all these people naysaying I say just go for it, don't let these people dishearten you from what you want to do. I'm sure there will always be users who are willing to try
Click to expand...
Click to collapse
That's exactly the same as what I have done. 100mV right across the board, and I have also never had a reboot or any other negative effect from doing it. Just a bit more battery life.
I too UV 100mv across the board. Never had an issue. And I OC up to 1.6ghz.
phonic said:
I too UV 100mv across the board. Never had an issue. And I OC up to 1.6ghz.
Click to expand...
Click to collapse
Same here, no issues with 100mv UV on stock speeds. What would happen if we went too low, would it fail to boot at all or is there some safety mechanism that would allow us to boot into boot loader?
davidoff59 said:
Same here, no issues with 100mv UV on stock speeds. What would happen if we went too low, would it fail to boot at all or is there some safety mechanism that would allow us to boot into boot loader?
Click to expand...
Click to collapse
When either OCing or UVing, you should ALWAYS test out the changes prior to saving them as a persistent boot state. This way, if you set something too high/low and it proves to be unstable, if you restart the device it will revert back to normal.
In the event that you OC/UV too much, yes, you would see signs of instability. In some cases it could show up as soon as you applied to change, in other cases it could take a while to notice. For example, some games or other high processing powered activities could FC/crash. Or your tablet might freeze or reboot. But again, as long as you didn't save your changes as a boot setting, it will be fine once it reboots.
In the event that you did save it, and the settings were unstable for your device, you could boot up into recovery and then manually erase them from taking effect. Recovery doesn't use those settings, as it's technically a different OS. But that can be complicated a process for some. So test test test save. Or don't save and just apply them manually.
Two other points:
Yes, most (all?) devices do have safeguards to protect itself against permanent hardware damage from OC/UVing. If it gets too hot, they will often shut down to protect themselves.
And just because one device can handle being OC'd or UV'd to a certain level doesn't mean they all can. Very minor differences in each component can impact one devices ability from another. The manufacturers only test to see if they can handle the published speeds/etc., but in many cases they can go higher if set to. In others, not so much.
Thanks for that phonic. Given the range of ROMs and kernel's available and the improvements already built in, under volting may not help a lot but every bit helps. Eg this screen on time is pretty good.Close to six hours screen on time with iirc 35% battery remaining.
Paranoid android with motley kernel. I don't over clock the nexus 7 as its fast enough. In fact I under clocked it to 1000 MHz max before and it was still fast but the screenshots are at stock volts and speeds.
it's actually plain simple. If everyone posts results. I can make a kernel with voltages that work for 75% of all people or maybe for 95% of all Nexus 7 owners.
It's called mathematics. But to do that I need as much results as possible.
Easy to do if you know what you are doing, right ?
http://en.wikipedia.org/wiki/Confidence_interval
Related
hey everybode!
i wanted to know i have rocket rom and i want to use setcpu to overclock my kernel
and sebastian is max to 1400 is thers good kernel that i can play with it till 1700mghz or 1900?
but it need to be stable
Abyss goes to 1700. My CPU can't take it, sadly
bubu23 said:
but it need to be stable
Click to expand...
Click to collapse
The stability is dependant on your hardware; some chips can only overclock to 1500Mhz and some can overclock all the way to 1900Mhz. It is not something the kernel has a say over.
Don't all of the notes have the same cpu? Why can some be overclocked and others not?
Sent from my GT-N7000 using Tapatalk
kkg720 said:
Don't all of the notes have the same cpu? Why can some be overclocked and others not?
Click to expand...
Click to collapse
They all can be overclocked, but how much is a different thing altogether. It's quite simple really, not every chip manufactured is of equal quality; some chips have more imperfections. The more imperfections the less it can be overclocked before it becomes unstable. It's the same thing as on PCs, too.
Stable is it when you do nothing and use it in originally form. Overcklocking need more Power more power is less time you enjoj your note!
Generally these chips are made to tolerate a certain speed, and because of variability, the manufacturer drops the speed tolerance to ensure overall quality. Some will still be able to manage 1500, 1700, or even 1900 (although rarely, I'd say). Just about all of them tolerate 1400, so very few are defective at the stated tolerance. With 5 million, you will get a few, however.
This is one of those rare occasions when statistics have a benefit in the real world!
jeromepearce said:
Generally these chips are made to tolerate a certain speed, and because of variability, the manufacturer drops the speed tolerance to ensure overall quality. Some will still be able to manage 1500, 1700, or even 1900 (although rarely, I'd say). Just about all of them tolerate 1400, so very few are defective at the stated tolerance. With 5 million, you will get a few, however.
This is one of those rare occasions when statistics have a benefit in the real world!
Click to expand...
Click to collapse
I will keep mine at stock speeds because ignorance is bliss
bubu23 said:
hey everybode!
i wanted to know i have rocket rom and i want to use setcpu to overclock my kernel
and sebastian is max to 1400 is thers good kernel that i can play with it till 1700mghz or 1900?
but it need to be stable
Click to expand...
Click to collapse
There are many out there that will let you overclock. Search the Android development forum.
Like most, I have flashed heaps of times, probably at least four or five times a week when I first got this wonderful Note, but in the last month or so have only been tempted to stray three or four times. Personally Franco 6 is best for me, because I favour battery life and stability rather than overclocking (1400MHz is not bad as a standard!!)
I would encourage you to try a few for a few days, as long as you backup often you should have a great experience!
Are all kernels capable of overclocking?
Is there one that overclocks the best?
How do you tell how high you can go?
Do you jusy keep overclocking until the NOte stops working?
If so, there must be a fine line.
jeffs99 said:
Are all kernels capable of overclocking?
Is there one that overclocks the best?
How do you tell how high you can go?
Do you jusy keep overclocking until the NOte stops working?
If so, there must be a fine line.
Click to expand...
Click to collapse
Stock kernel isn't capable of overclocking.
One way to tell is to download things like SetCPU which detects the range of the clockspeed. Another way is to simply read the description of the kernel thread.
How high your phone can go is an individual thing. You need to overclock in slight increments (say 50mhz at a time) and run a stability test to see if the phone crashes or not.
You DO NOT pull the slider all the way to 1.9 ghz and "see" if anything happens. If you fry your CPU, do not come to us for help.
This is why I don't like overclocking, it's a waste of time to run the stability tests, etc.
In summary, you need to raise it a little bit, and run stability tests and repeat the process until your phone crashes. At that point, you'd know the last safe-stable clockspeed that your CPU can take.
PoisonWolf said:
Stock kernel isn't capable of overclocking.
One way to tell is to download things like SetCPU which detects the range of the clockspeed. Another way is to simply read the description of the kernel thread.
How high your phone can go is an individual thing. You need to overclock in slight increments (say 50mhz at a time) and run a stability test to see if the phone crashes or not.
You DO NOT pull the slider all the way to 1.9 ghz and "see" if anything happens. If you fry your CPU, do not come to us for help.
This is why I don't like overclocking, it's a waste of time to run the stability tests, etc.
In summary, you need to raise it a little bit, and run stability tests and repeat the process until your phone crashes. At that point, you'd know the last safe-stable clockspeed that your CPU can take.
Click to expand...
Click to collapse
Thanks!
What do you recommend for a good stability test?
I'm on franco.kernel v10 and OC to 1600 using Tegrak. Tegrak runs the stability tests automatically and reverts to stock 1400 if unstable or a reboot occurs.
I tried 1700 but Note rebooted after about 2 minutes. Booted right back up at 1400 with no problems. Re-set to 1600 and running smoothly.
kraz
Sent from my Beautiful, White GT-N7000 using xda premium
Set CPU has a CPU stress test
Sent from my GT-N7000 using xda premium
New thread to house the custom kernel built with linaro's gcc 4.7.1 toolchain
This *should* work with any AOSP ics rom.
Just because this kernel is built with the linaro toolchain it does not mean the rom needs to be compiled in a certain way.
Download here: http://tinyw.in/gnOy
I'll add more details when i have some more time.
source: https://github.com/invisiblek/android_kernel_htc_qsd8k
toolchain used: http://tinyw.in/gYmj
General question on this--is this kernel intended to be used with the nightlies in your testing folder only, or are its benefits universal? I'm a little confused by this whole toolkit thing...
Sent from my ADR6300 using XDA
polarimetric said:
General question on this--is this kernel intended to be used with the nightlies in your testing folder only, or are its benefits universal? I'm a little confused by this whole toolkit thing...
Sent from my ADR6300 using XDA
Click to expand...
Click to collapse
Good question. This *should* work with any ics rom.
I tested this out last night (been running mamarley's kernel) and I ended up switching back for two reasons: first, this doesn't appear to have the 128MHz CPU speed - I'm not sure if that's intentional or not. And secondly, my phone apparently couldn't handle this kernel on 1113MHz - I got lots of FCs. And the rating on Nenamark was essentially the same as my baseline on other kernels.
Just some observations - and your mileage may vary! I really appreciate the fact that this is even being worked on, invisiblek.
EDIT: Totally meant AnTuTu, not Nenamark.
stiltzkin said:
I tested this out last night (been running mamarley's kernel) and I ended up switching back for two reasons: first, this doesn't appear to have the 128MHz CPU speed - I'm not sure if that's intentional or not. And secondly, my phone apparently couldn't handle this kernel on 1113MHz - I got lots of FCs. And the rating on Nenamark was essentially the same as my baseline on other kernels.
Just some observations - and your mileage may vary! I really appreciate the fact that this is even being worked on, invisiblek.
Click to expand...
Click to collapse
Great to hear feedback. Thats all im looking for here really.. It doesnt have 128mhz because its the same voltage as 245 hence no real benefit to having it. Plus some devices are unstable there. I never overclock but i can look at the voltages and maybe get 1113 stable
I can say it works on the new ICS TW rom, drains kinda fast although I think its rom related only.
I had only one reboot, got a freeze and then 10 seconds later a reboot. Its the only one I've had since reapplying new settings.
On freeze I was running SAv2 1113 Max/245 Min.
I have now lowered it to 998 and its running fine on that rom.
Other than that, its amazing.
Sent from my ADR6300 using Tapatalk 2
invisiblek said:
Great to hear feedback. Thats all im looking for here really.. It doesnt have 128mhz because its the same voltage as 245 hence no real benefit to having it. Plus some devices are unstable there. I never overclock but i can look at the voltages and maybe get 1113 stable
Click to expand...
Click to collapse
i take this back, 128mhz is 25mV under 245mhz here
never mind
Can you clear up the linaro tool chain for me, I'm confused as to if the ROM currently utilizes it... and if so is there a certain kernel you have to use along side it. Sorry if that's a stupid question...
Sent from my ADR6300 using XDA
Does this have fast charge?
thekendog said:
Does this have fast charge?
Click to expand...
Click to collapse
I think so, based on this commit below I'd say yes:
add smb329.c for fast charging when plugged into usb
I'm getting some pretty great battery life with this kernel and the 6/21 kang. 1 day and 9 hours after moderate use and I'm still at 30%
Sent from my ADR6300 using XDA
I've always been a big fan of undervolting. These are the lowest voltages I can get stable at these common speeds. I found I can underclock the Matr1x kernel further than some others I have tried for some unknown reason. How low have you been able to go? Also, what programs do you use to test stability? So far, I have been running Antutu test completion as a measure of stability. Any suggestions otherwise?
288MHz - 650mv
1.02Ghz - 800mv
1.51Ghz - 1000mv
ROM: Bionic AOSP V3
Kernel: Matr1x 6.5
Noob question~ Why do people undervolt?
WarToilet said:
Noob question~ Why do people undervolt?
Click to expand...
Click to collapse
To increase battery life,
The Long answer is that the CPU has a number of parameters where Clockspeed (MHz) and voltage (mV) are two. Clockspeed, well that is speed. Voltage is related to the amount of energy provided to the cpu, undervolting means that you feed the CPU less juice but demand that it runs at the same clocks. You are essentially starving the CPU,it uses less energy, but can become unstable if the voltage is insufficient to maintain operations. Manufactures always have extra voltage as a safety margin so power users can check their CPU bin (slow, normal, fast or faster) and lower voltages step by step until they crash the phone during a stress test, increase the voltage slightly and boom, your phone uses less battery power while being just as fast.
I undervolt to reduce heat. It makes a significant difference. The battery saving is minimal, but the temperature difference is VERY noticeable.
estallings15 said:
I undervolt to reduce heat. It makes a significant difference. The battery saving is minimal, but the temperature difference is VERY noticeable.
Click to expand...
Click to collapse
Took words from my mouth. This this and this. It reduces heat, which in turn reduces battery use. UV by itself doesn't save a lot of battery, it's the consequences of it. I'm normally not a fan of UV, but with current N4 sw/fw it NEEDS it. It's way too high.
Interesting observation. As of recently my phone jumps up by 3-5c from 37-38 hover. Never used to do it before, not until i got it up to 50c for about half an hour last week. Previously it would stay steadily at 37-38, now it spikes up now and again during use. What's interesting about is that once it goes over 40c battery use increases drastically. So i wonder if people that have really good battery life don't have phones that go over that temp often and vice versa.
I haven't played around with the values too much yet, just a -100mV across the board. This seems to work just fine, so I might experiment some more..
Using Franco test-r69 at the moment.
Sent from my Nexus 4 using xda premium
I undervolt to prevent heating like others say. My Antutu scores drop like a rock when I'm at stock clockspeeds mostly likely due to thermal throttling. Now I can run it repeatedly without having scores drop. It saves battery and runs faster while running games even for very short periods of time, so I am a big fan of undervolting. :good:
Undervolt to reduce power usage, think of the stock voltage as normally being more than is required, think of running for a bus yet you have 2 minutes why waste energy when you can walk and still make it .
Undervolt for less power usage and less heat produced meaning battery performance is better (cooler battery is a more efficient one) and performance is up as you avoid any thermal limits in place .
Great stuff undervolting, I have managed to get -150mV across the board ( 1.5ghz @ 1000mV) and 288mhz is 162.5mV .
I came from a nexus s ... And one member of xda went to amazing lengths to show that undervolting really made very little differences in battery life ... And it def wasn't worth the instability .
He did loads of tests and I mean loads and basically showed that in helped so little that if you had a reboot you would use more power in rebooting then saving via undervolt
However . it is worth it for the heat decrease for sure
Sent from my Nexus 4 using Tapatalk 2
italia0101 said:
I came from a nexus s ... And one member of xda went to amazing lengths to show that undervolting really made very little differences in battery life ... And it def wasn't worth the instability .
He did loads of tests and I mean loads and basically showed that in helped so little that if you had a reboot you would use more power in rebooting then saving via undervolt
However . it is worth it for the heat decrease for sure
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
The more the heat, the faster the battery drains. Since undervolting decreases heat, im sure it should increase battery life. Maybe not for browsing or calling, but playing a heavy 3D game.
is it normal that the higher the frequency the lower the voltage in setcpu?
screenshot: http://db.tt/k6r8c5oI
I'm quite new to nexus 4 undervolting, what's the average amount i can lower the voltages with? (i have a nominal CPU)
sent from my Nexus 4...
zakoo2 said:
how can you guys undervolt? is there an app for that? i bought Franco's kernel updater app, but there's no option to undervolt in there.
edit: just found an app called setcpu, is that it?
sent from my Nexus 4...
Click to expand...
Click to collapse
You can do it from franco kernel updater, from frequencies and voltages - voltages - cpu voltages
But i dont recommend you to undervolt if you dont know what you do.
Sent from my Nexus 4 using Tapatalk 2
aimcr7 said:
You can do it from franco kernel updater, from frequencies and voltages - voltages - cpu voltages
But i dont recommend you to undervolt if you dont know what you do.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I'm familiar with undervolting both on PC and on phone, but i had a Motorola defy before my nexus and undervolting there was a bit different.
sent from my Nexus 4...
zakoo2 said:
is it normal that the higher the frequency the lower the voltage in setcpu?
screenshot: http://db.tt/k6r8c5oI
I'm quite new to nexus 4 undervolting, what's the average amount i can lower the voltages with? (i have a nominal CPU)
sent from my Nexus 4...
Click to expand...
Click to collapse
How are you able to undervolt with SetCPU? I'm not seeing that option using CM10, and Harsh's kernel.
italia0101 said:
I came from a nexus s ... And one member of xda went to amazing lengths to show that undervolting really made very little differences in battery life ... And it def wasn't worth the instability .
He did loads of tests and I mean loads and basically showed that in helped so little that if you had a reboot you would use more power in rebooting then saving via undervolt
However . it is worth it for the heat decrease for sure
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Former nexus s user here, the reason nexus s didn't benefit in battery life much was that it only had 1 core, and used a higher nm manufacturing process, 65nm -> 28nm. Lower voltages in the 28nm means that it multiplies the heat/power savings more than a 65nm, and the 4 cores multiply the savings by up to 4.
FatalityBoyZahy said:
How are you able to undervolt with SetCPU? I'm not seeing that option using CM10, and Harsh's kernel.
Click to expand...
Click to collapse
don't know, it was just there. did you try to reboot after installing the app?
I'm on Franco's kernel btw.
sent from my Nexus 4...
Pls what are the right values for under volting Samsung captivate
Sent from my SGH-I897 using xda premium
I am new to this and my battery goes +40°C when I play simple games... I am running Franco's kernel r71 should I do UV? If so how much? Thanks in advance
Sent from my Nexus 4 using xda app-developers app
xtremer92 said:
Pls what are the right values for under volting Samsung captivate
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
this is the lg nexus 4 forum.
sent from my Nexus 4...
Hi guys!!!!!!!!
I want to know, if i want to overclock my nexus 7 what is the max safe temp i can go?
If my fuzzy memory serves me right stock thermal throttling starts at 85c and thermal shutdown at 100c..
Thanks
Thanks but is not what i asked for i asked for the max SAFE temp for the nexus 7 because i want to overclock the device!!!!
But thanks anyway
If someone wants to put their opinion go head that will help me ALOT!!!!!!!!!!!!!
GumarGamer said:
Thanks but is not what i asked for i asked for the max SAFE temp for the nexus 7 because i want to overclock the device!!!!
But thanks anyway
If someone wants to put their opinion go head that will help me ALOT!!!!!!!!!!!!!
Click to expand...
Click to collapse
Oh boy.. ..... ... What I gave you is EXACTLY what you asked for. I'm going to suggest you don't overclock because it's apparent you have no idea what you're doing or talking about.
I know what i am doing
I overclocked many devices and computers so i know what i am doing but 85 is not a safe temp so if know the max safe temp tell me if you don't stop insulting me and get a life.
GumarGamer said:
I overclocked many devices and computers so i know what i am doing but 85 is not a safe temp so if know the max safe temp tell me if you don't stop insulting me and get a life.
Click to expand...
Click to collapse
Negative bro. Just because you've overclocked "many devices" doesn't mean you know what your talking about. He answered you and your response is get pissed and tell him he's wrong? If you know he's wrong you must know what's right, so why'd you ask!? If the manufacturer sets the the "safe temp" at 85 then yes 85 is safe enough. If you think that's too warm, fine pick a lower temp and go with it.
Sent from my Nexus 7 using xda premium
Sorry
Sorry I overreacted
The question as posed has no answer.
The stock kernel throttles at 95C and shuts down at 100C
Some dev kernels use lower values than this.
The effect of heat is cumulative, and likewise for the number of temperature cycles.
(The point there is that 5 hrs @ 80C could be worse than 1 hr @ 85C)
In general devices that are heavily used experience reliability failures earlier than lightly used devices, whether they are overclocked or not.
Good luck and enjoy your device - while it lasts.
bftb0 said:
The question as posed has no answer.
The stock kernel throttles at 95C and shuts down at 100C
Some dev kernels use lower values than this.
The effect of heat is cumulative, and likewise for the number of temperature cycles.
(The point there is that 5 hrs @ 80C could be worse than 1 hr @ 85C)
In general devices that are heavily used experience reliability failures earlier than lightly used devices, whether they are overclocked or not.
Good luck and enjoy your device - while it lasts.
Click to expand...
Click to collapse
I actually had a post written out going into this perspective also but decided to not even bother. :laugh: Good on ya though for going through with it. Another spin on it is the affect those high temps have on the hardware and chipsets around, or hovering on top of it. This is why I typically don't overclock my devices for anything other than a run through benchmarks. Also, besides using more battery and generating more heat for a longer duration, typical overclocks rarely produce any significant difference the end user can actually notice on these high end devices anyway. Hell, I don't even notice a difference on my single core Nexus S when OCing from 1ghz to 1.4ghz.
I flashed the Franco kernel on my nexus 7 to increase my battery life and performance then when I went into ROM tool box I noticed the min frequicy was 244 megahertz 144 different than stock I went back the the original kernel right after could this have damaged me CPU and shorted the life on my device I only had the kernel for a few hours
Please answer
Sent from my Nexus 7
http://forum.xda-developers.com/showthread.php?t=2121649
I don't see how that helps
Sent from my Nexus 7
No it wouldn't ruin your device. I keep my min CPU at 380 something amnd never had any problems
Sent from my Nexus 7 using xda premium
Thank you I worry to much
Sent from my Nexus 7
Whaleshark345 said:
I flashed the Franco kernel on my nexus 7 to increase my battery life and performance then when I went into ROM tool box I noticed the min frequicy was 244 megahertz 144 different than stock I went back the the original kernel right after could this have damaged me CPU and shorted the life on my device I only had the kernel for a few hours
Please answer
Sent from my Nexus 7
Click to expand...
Click to collapse
No, and the reasoning is nonsense. A processor is not going to be damaged because it is performing too slowly, given that it will (ideally) spend most of its time at ~0MHz anyway (deep sleep). The only way you're going to damage your onboard hardware is if you start messing with the voltage and clock speed in the upward direction.
If you underclock your processor, then your tablet gets slower (obviously). Since the Franco kernel adjusts the minimum frequency, though, this only affects how the tablet behaves when it's idle, but not quite asleep (generally after the screen is dim and you haven't touched it for a while). Keep in mind that the maximum frequency will still be significantly above this, meaning that it's not like the adjusted lower bound is going to make the processor faster than it does during normal use.
If you undervolt your processor, then there's the chance that you'll mess up and the device will power off because it's not getting enough power to run the processor. At that point, the next reboot will generally put voltage settings back to normal (assuming you haven't set your voltage on boot), and even if you did, you can just reflash the kernel (again with no harm to the device).
If you overvolt or overclock your device, battery life will (potentially) get shorter (but not necessarily battery capacity), the device will run a little hotter, and a little faster. You can also fry your board. However, very few kernels get posted here that allow the processor to get anywhere near those states (unless you basically purposefully try to kill your board), and the processor itself has physical safeguards that will shut things down/throttle speed if you're in danger.
Whaleshark345 said:
I don't see how that helps
Sent from my Nexus 7
Click to expand...
Click to collapse
They were suggesting that you wipe your old kernel completely and flash again. Not really that important.
And next time ask questions in the Q&A section. That's what it's there for.
Sent from my Nexus 7 using Tapatalk HD
veeman said:
And next time ask questions in the Q&A section. That's what it's there for.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
And actually use a proper title rather than the lazy and nondescriptive "I have a question." No kidding?!
Sent from my SCH-I545 using Tapatalk 4 Beta