Database Develop

Is it safe to overclock Galaxy S to 1.2Ghz?

I already overclock and undervolt my Galaxy S running Darky 8.1 with SUpero Optimize Kernel 4_6_8. But I'm not sure that this clock frequency will be safe for my device.

Hi Luke.
First of all i wouldn't recommend it at all.
Why...???
First of all, this is an expensive mobile phone.
When we put custom ROM's inside we are always doing it with a risk to get our phones ''bricked'' or unresponsive.
For example,
i have OC my PC's proccessor and i did it on purpose, but when you OC it,
your proccessor's life-time is decreasing and the question is...how long will it work!
So it's the same thing for SGS, how long will it work and is your proccessor going to get fried up.
So for me now...i'll stick to the darky's custom rom and nothing else.

LukeSP said:
I already overclock and undervolt my Galaxy S running Darky 8.1 with SUpero Optimize Kernel 4_6_8. But I'm not sure that this clock frequency will be safe for my device.
Click to expand...
Click to collapse
Its up to you. I have it OC. Firstly, Overclocking doesnt mean that the processor is going to run at 1.2Ghz all the time. On the contrary, you can govern the speed of your processor and it runs to 1.2Ghz only when it needs to. For example, after using Voltage tool, use SetCpu and there you can set the mode to conservative or on-demand. Go to Info tab and there you can see for how long certain frequency/CPU speed was used and you will see different values are used, not just 1.2Ghz.
As for the safety part, Putting a custom ROM, Rooting etc is already the way your phone is not supposed to be used, risking the life and warranty.
So, it depends how you look at it. I recommend it.

Essence is its up to you and your choice to take the risk involved .
jje

Charlie Wax said:
Hi Luke.
First of all i wouldn't recommend it at all.
Why...???
First of all, this is an expensive mobile phone.
When we put custom ROM's inside we are always doing it with a risk to get our phones ''bricked'' or unresponsive.
For example,
i have OC my PC's proccessor and i did it on purpose, but when you OC it,
your proccessor's life-time is decreasing and the question is...how long will it work!
So it's the same thing for SGS, how long will it work and is your proccessor going to get fried up.
So for me now...i'll stick to the darky's custom rom and nothing else.
Click to expand...
Click to collapse
theres a reason you can overclock a cpu alot more than stock, fans, coolants etc.
a computer chip needs to work whether its in the hottest climate and the coldest and thats why youve got scope to overclock the ass of the cpu if you got the fans , pipes, water blah blah blah
so the cpu overclock and the phone overclock are totaly different
regards

thebazman said:
theres a reason you can overclock a cpu alot more than stock, fans, coolants etc.
a computer chip needs to work whether its in the hottest climate and the coldest and thats why youve got scope to overclock the ass of the cpu if you got the fans , pipes, water blah blah blah
so the cpu overclock and the phone overclock are totaly different
regards
Click to expand...
Click to collapse
So would you be so kind to explain us the differences between those two things...
From my point of view...it is the same thing, the CPU will not always work at full load, as darky once said there is no need for overclocking or dual-core cpu on mobile phones.
The problem is not in the hardware, it's inside the software.

K to the question.
It is relative "safe" if you know how to do it, but not much point of doing it.
I used to have it Overclocked but saw only the slightest difference.
I think you better off with what you are on mate.
Unless you are bored want to try it out

Charlie Wax said:
So would you be so kind to explain us the differences between those two things...
From my point of view...it is the same thing, the CPU will not always work at full load, as darky once said there is no need for overclocking or dual-core cpu on mobile phones.
The problem is not in the hardware, it's inside the software.
Click to expand...
Click to collapse
if you say theres no difference then fine. ive just explained why you can overclock a pc cpu.
a mobile phone processor and its cooling system is different dont you think?
well if someone says dont overclock your pc cause theres no need, would you follow that instruction ?
regards
btw im not saying your better of overclocking or not, its up to the individual to research or read im just pointing out theres a big difference from pc cpu and phone cpu

It depends...on my primary usage of PC.
I'm a photographer, so i need lot of CPU and RAM power, but according to that i have adequate cooling system.
But my point is overclocking is always the same thing, raising your voltage and CPU speed. Mobile phone actually doesn't need OC, the usage of CPU is written inside the program, application, software...you name it.
I agree with you that cooling is different, but c'mon mate, do u really see that big difference.

Charlie Wax said:
It depends...on my primary usage of PC.
I'm a photographer, so i need lot of CPU and RAM power, but according to that i have adequate cooling system.
But my point is overclocking is always the same thing, raising your voltage and CPU speed. Mobile phone actually doesn't need OC, the usage of CPU is written inside the program, application, software...you name it.
I agree with you that cooling is different, but c'mon mate, do u really see that big difference.
Click to expand...
Click to collapse
you keep talking as if iv said ive overclocked my phone , i havnt
i just gave a pov on the differences thats all
regards

I overclocked my SGS to 1.2GHz because of Dungeon Defenders. It was unplayable with many creatures and players. After OC, the difference is huge. No problems with overheating or freezing.

How to OC SGS on Darky's ROM 9.1 with SO Kernel?
Is there any tutorial? Anybody can explain me how to OC to 1.2Ghz?

You can use Galaxy tuner app from market
Sent from my GT-I9000 using XDA App

Overclocking always has risks, except on platforms designed to accommodate it. Don't overclock your phone if you rely on it for everyday use.

I have my phone at 1.3ghz for everyday use. No lagfix, its buttery smooth! I'll never go back.

I don't think its safe
Searching Google for other peoples opinion on this. I have over clocked at times and the difference is small unless you are looking at benchmarks.
I think what people don't realize is that each cpu has an average life span at its given clock speed. When you over clock i can say 100% for certain you are decreasing its life.
The decrease may be so small that the phone is going to be outdated before it dies or it could be great enough that one day in 3 months time your phone just dies and there is not really any way of knowing for sure.
So id say if you are going to over clock just be aware of that as a lot of people seam to think as long as you use profiles and don't let it get over a certain temp its doing no damage =P

martan1981 said:
I overclocked my SGS to 1.2GHz because of Dungeon Defenders. It was unplayable with many creatures and players. After OC, the difference is huge. No problems with overheating or freezing.
Click to expand...
Click to collapse
strange. I have played DD1 & DD2, with standard 1GHz without any problems.

I'm on insanity cm with glitch kernel, @1.4Ghz for everyday use, very smooth, web pages load in a flash, the time it spends at that frequency is tiny, if I was gaming a guide amount I would probably go down to 1.2Ghz to be safe as it would probably warm up a bit, but I monitor everything carefully, time in state, temp, etc........to me it is worth it, but of course there is a risk, but my contract is 2 years, so phone only has to last that, and if it does fry, how are samsung going to know? They will just replace motherboard, and in any event I'm kind of old fashioned, I take responsibility for my mistakes! Do it and enjoy, or don't and forever wonder!
Sent from my GT-I9000 using XDA Premium App

Charlie Wax said:
Hi Luke.
First of all i wouldn't recommend it at all.
Why...???
First of all, this is an expensive mobile phone.
When we put custom ROM's inside we are always doing it with a risk to get our phones ''bricked'' or unresponsive.
For example,
i have OC my PC's proccessor and i did it on purpose, but when you OC it,
your proccessor's life-time is decreasing and the question is...how long will it work!
So it's the same thing for SGS, how long will it work and is your proccessor going to get fried up.
So for me now...i'll stick to the darky's custom rom and nothing else.
Click to expand...
Click to collapse
yeah i agree,i don c the sense of oc,if u c the current market there r phones wiv 1.5ghz,3d chips an all those high fiv hardware.even a 2ghz dual-core is abt to come.the company has given sgs 1ghz ,but neva said its cool to oc it...i had tried oc once but frankly i dint notice any diff..but its as per personnel wish ,if u wanna oc then its right for u....

Its totally safe as long as you don't be ridiculous about it....I.e most people make kernels capable of oc to 1.7ghz but that's just stupid because you'll fry your processor, I'd say Max....1.5ghz.....oh and btw it eats your battery so I suppose theirs good and bad sides to it
Sent from my GT-I9000 using XDA Premium App

[Q] Benefits of OC/UV

What are the benefits of OC/UV (particularly for CM7)?
I know of improved performance due to OC, but what does UV do in regards to performance. Also, how does an OC/UV kernel compare to one without the option?

your processor doesn't need as much voltage as the stock settings--undervolting lets you save battery
personally i want to know.. do you have to UV to OC?

xredjokerx said:
your processor doesn't need as much voltage as the stock settings--undervolting lets you save battery
personally i want to know.. do you have to UV to OC?
Click to expand...
Click to collapse
You can do either or both but don't have to do both. At some point UVing will cause a crash. Right before that point it can cause performance issues. See the link below for instructions on how to find an optimal UV level to maximize battery savings and performance.
http://forum.xda-developers.com/showpost.php?p=10936691&postcount=1102
OCing improves speed but can also cause stability issues. For a captivate this usually isn't a problem until you get past 1.2 ghz. After that, it depends on the kernel but I have yet to find a kernel that is completely stable past 1.2 ghz under stressful conditions. Samsung designed the processor to handle 1.2 ghz and in theory it can go up to at least 1.6.

Like everyone before me has said, OC will make your processor work more (which will eat up more battery, and send the temps a bit higher).
UV is a way to "fix" that problem by controlling the voltage used by each Mhz/Ghz range. The mini guide that QuarkGluonSoup posted is a great way to start off.
Most Captivates start have random errors past 1.2Ghz, but the highest I've seen (stable) are 1.4Ghz.

venomio said:
Like everyone before me has said, OC will make your processor work more (which will eat up more battery, and send the temps a bit higher).
UV is a way to "fix" that problem by controlling the voltage used by each Mhz/Ghz range. The mini guide that QuarkGluonSoup posted is a great way to start off.
Most Captivates start have random errors past 1.2Ghz, but the highest I've seen (stable) are 1.4Ghz.
Click to expand...
Click to collapse
Odd as it sounds, my battery life on CM7 is close to 50% better when it is OC'ed to 1.2 ghz and UV'ed than it was on the froyo ROMs under the same conditions.

That really is odd :S I think I'll try it myself.

Cyanogen8

Cyanogen 8? Is this next? Or is this in the works? Also is 2.3.5 next and would it be numbered a different version when Ice Cream comes out? Also is anything coming from the devs to overclock to 800 yet?

cell2011 said:
Also is anything coming from the devs to overclock to 800 yet?
Click to expand...
Click to collapse
It's been done. So very very few phones are even stable at 800, and those that could generally performed worse in benches at 800 than at lower clocks. Many of these devices bootloop above 700.

Cyanogen 8 will not come out yet since will most likely be ice cream sandwich. I am not even sure is 2.3.5 will even come out and no the devs can not overclock this device to 800mhz because is 768 is the limit of the processor. Most people's phones do not even run that smoothly at 768 anyways. If somehow the dev found a way to overclock it to 800 (impossible btw but this is just a what if kind of statement) since the processor can not handle 800 it would just overheat the thing and cause crashes.

Also, on a side note, this should not be in the Development section. This should be in general or Q&A

This belongs in Q&A for future reference.
CM8 will be next, obviously. It will be based on Ice Cream Sandwich, so no, it won't be in development until ICS is released to AOSP so that the CM team can start using that code. 2.3.5 is an update coming out soon for the Nexus S 4G that fixes wifi and network speed, as well as adding more secure NFC for Google Wallet. It won't really affect us when it is merged into CM7. ICS is expected to be Android 4.0, but it could be 3.5 if Google decides.
There is a kernel that goes over 800Mhz, but anything over 768Mhz can be unstable on some phones. I tried it and there were no real performance gains, but battery life was a lot worse. Performance was actually worse at the highest CPU clock, in my experience. Just stick with 768Mhz. It's stable and chances are that you can get even better performance at a lower clock. I get better battery and performance at 633Mhz. It all depends on each unique phone.

rizdog23 said:
Cyanogen 8 will not come out yet since will most likely be ice cream sandwich. I am not even sure is 2.3.5 will even come out and no the devs can not overclock this device to 800mhz because is 768 is the limit of the processor. Most people's phones do not even run that smoothly at 768 anyways. If somehow the dev found a way to overclock it to 800 (impossible btw but this is just a what if kind of statement) since the processor can not handle 800 it would just overheat the thing and cause crashes.
Click to expand...
Click to collapse
I lol'd at this statement. Did you not read any of the posts above you?

When i began to post there were no posts yet. They must have got posted while i was typing. So seeing as the only post at the time was the op, then yes i did read the post(s) above mine.....

There is a kernel that goes over 800Mhz, but anything over 768Mhz can be unstable on some phones. I tried it and there were no real performance gains, but battery life was a lot worse. Performance was actually worse at the highest CPU clock, in my experience. Just stick with 768Mhz. It's stable and chances are that you can get even better performance at a lower clock. I get better battery and performance at 633Mhz. It all depends on each unique phone.
Click to expand...
Click to collapse
I can confirm that the Godmode kernel was able to push some phones, such as mine, past 800Mhz. Although I had a faster processor speed, my battery would drain incredibly fast as well as overheat. Even though I never hit a bootloop with the kernel, the battery life, overheating, and loss of performance kept me away. Sacrificing too much for having a faster processor speed. Normally I overclock to about 729Mhz and have great battery life, speed and performance in conjunction with a min of 19Mhz and a smartass governor.
Sent from my Hero that never dies! ;D

dastin1015 said:
I can confirm that the Godmode kernel was able to push some phones, such as mine, past 800Mhz. Although I had a faster processor speed, my battery would drain incredibly fast as well as overheat. Even though I never hit a bootloop with the kernel, the battery life, overheating, and loss of performance kept me away. Sacrificing too much for having a faster processor speed. Normally I overclock to about 729Mhz and have great battery life, speed and performance in conjunction with a min of 19Mhz and a smartass governor.
Sent from my Hero that never dies! ;D
Click to expand...
Click to collapse
Thanks. I am glad someone at least confirmed it. I never knew about the godmode kernel as ive only been here for a little bit. Sorry for misinformed post about their not being an 800mhz kernel. As I can see, i was wrong, but also I was correct in saying that the processor can not handle it....sometimes

rizdog23 said:
Thanks. I am glad someone at least confirmed it. I never knew about the godmode kernel as ive only been here for a little bit. Sorry for misinformed post about their not being an 800mhz kernel. As I can see, i was wrong, but also I was correct in saying that the processor can not handle it....sometimes
Click to expand...
Click to collapse
Yup, I'm at 806 - 19 ondemand while posting this and I can already feel it slowing down a little. 729 - 19 on demand is my best setup. I've tested a lot with trying higher setups than that but so far 729 seems to be the best for battery life and performance on every rom I've ever tried
Sent from my HERO200 using XDA Premium App

rubyknight said:
Yup, I'm at 806 - 19 ondemand while posting this and I can already feel it slowing down a little. 729 - 19 on demand is my best setup. I've tested a lot with trying higher setups than that but so far 729 seems to be the best for battery life and performance on every rom I've ever tried
Sent from my HERO200 using XDA Premium App
Click to expand...
Click to collapse
For some reason my phone never works well with higher clock speeds no matter what rom or kernel i use. I get my best results at 710-352 performance.

In before bierce gives birth over ANOTHER question being in the dev section
Sent from my Android using Tapatalk

rizdog23 said:
For some reason my phone never works well with higher clock speeds no matter what rom or kernel i use. I get my best results at 710-352 performance.
Click to expand...
Click to collapse
Correct me if I'm wrong, but from what I've noticed is that newer Hero's that were sold with Eclair as opposed to the original Donut, when I bought mine, are not able to reach those higher processor speeds past 691Mhz.
Sent from my Hero that never dies! ;D

i bought mine at radio shack back in september and it was still on 1.5 and ive never been able to get over 768mhz without it freezing and bootlooping its different with every hero.
i stay at 352-691 ondemand and thats plenty fast for me

Mine was running 1.5 also and it will run fine at 768 but battery life suffers so I usually run at 352/710 and battery and performance are good (depends on rom kernel)
Where can I get the godmode kernel ....
Sent from my HERO200 using XDA App

I actually got mine two weeks after it came out.....so i mean it could just be that this phone is dead now. I never had a refurb or anything. I got it wet once but it got repaired. I've only had this one the whole time. Do you think that is the issue?

rubyknight said:
Yup, I'm at 806 - 19 ondemand while posting this and I can already feel it slowing down a little. 729 - 19 on demand is my best setup. I've tested a lot with trying higher setups than that but so far 729 seems to be the best for battery life and performance on every rom I've ever tried
Sent from my HERO200 using XDA Premium App
Click to expand...
Click to collapse
Hey rubyknight,
just wondering why 19? Ive seen people do that but can the processor really ever do anything at 19? if so, doesnt it affect stuff like wake. Im trying it now just to see for myself. Ive been playing with a really high min value between 480 and 576 with the high at 748 and it actually doesnt only seems to affect battery life a little, both on the .29 and .35 kernels on jaybobs roms and on OMFGB.
Thanks

chalan30 said:
Hey rubyknight,
just wondering why 19? Ive seen people do that but can the processor really ever do anything at 19? if so, doesnt it affect stuff like wake. Im trying it now just to see for myself. Ive been playing with a really high min value between 480 and 576 with the high at 748 and it actually doesnt only seems to affect battery life a little, both on the .29 and .35 kernels on jaybobs roms and on OMFGB.
Thanks
Click to expand...
Click to collapse
It depends on the cpu governor that you use.
nandroids are for
sissies

ch1naski said:
It depends on the cpu governor that you use.
nandroids are for
sissies
Click to expand...
Click to collapse
so update, ive run it at 19/768 on demand all day and after 11hrs 13 min its at 60% thats not bad for my phone! and there was almost no performance difference. Just the slightest UI lag... this is on jaybobs 7/8 with the .29 kernel, with background data off. And my regular usage which is not a lot. but for me its good. i wish I had tried it ages ago.

chalan30 said:
so update, ive run it at 19/768 on demand all day and after 11hrs 13 min its at 60% thats not bad for my phone! and there was almost no performance difference. Just the slightest UI lag... this is on jaybobs 7/8 with the .29 kernel, with background data off. And my regular usage which is not a lot. but for me its good. i wish I had tried it ages ago.
Click to expand...
Click to collapse
I believe that you can set the ramp up frequency and that may help with the lag. Setcpu, advanced settings, I think?
nandroids are for
sissies

[Q] Undervolted

I've undervolted my device and right now I have
100mhz - 825 mah
200mhz - 825 mah
500mhz - 800 mah
for some reason the 500mhz setting is stable and if I undervolt 100mhz/200mhz even more, I crash.
If I set my minimum processor power to 500mhz would I consume less batter than if I were to use 100mhz/200mhz?

Your phone spends most of its time in the lowest and highest cpu frequencies and just a small amount of time at the intermediate levels. Your undervolt for 500mhz probably isn't stable but it doesn't crash because it's only at that frequency for a very short amount of time. If you set the minimum to 500mhz at that voltage it will probably start playing up.
http:/ /db.tt/iy1bKVoB
graph of my cpu levels

Abit offtopic but what the hell!
I was wondering if there's any risks involved with undervolting?
I don't meen the crashes and freeze ups, but rather more like if there's any risk
to really damage your phone from it?
I have and still do alot of OC in the computer world, and do know what overvolting can do. But i'm still curious about what uv can do to your system.

Maskell said:
Your phone spends most of its time in the lowest and highest cpu frequencies and just a small amount of time at the intermediate levels. Your undervolt for 500mhz probably isn't stable but it doesn't crash because it's only at that frequency for a very short amount of time. If you set the minimum to 500mhz at that voltage it will probably start playing up.
http:/ /db.tt/iy1bKVoB
graph of my cpu levels
Click to expand...
Click to collapse
It's been my minimum even before posting this thread. I just started to wonder.
I've been on it for 10 hours now. I have 45% battery life left. Probably due to my 1700mhz being @ 1350mah right now.
I can assure you, it's VERY stable. It's so SMOOTH. Smoother than just having rocketrom and all that stuff. NO LAGS, NO SHUTDOWNS. ALL STABLE.
I can see better battery life, and CPU Spy says it used up 47% 1700mhz and 40% 500mhz. I think it's giving me better battery life.
It's evenly splitted up probably because I was using lulzactive governor.
but then again I didn't log my previous battery life without undervolting.
Some more insight would be nice.
SweCrow81 said:
Abit offtopic but what the hell!
I was wondering if there's any risks involved with undervolting?
I don't meen the crashes and freeze ups, but rather more like if there's any risk
to really damage your phone from it?
I have and still do alot of OC in the computer world, and do know what overvolting can do. But i'm still curious about what uv can do to your system.
Click to expand...
Click to collapse
There are alot of risks. Minor chance that you will cause hardware damage to your phone but I'm saying VERY minor. Just don't be stupid with voltages, like just suddenly overdropping the voltages. Your processor might die.
It's scary as hell, it crashes alot while testing and all that ****.
Feels good when you get it stable though.
TL;DR
Very slight chance to damage your hardware; only if you're very daring.
It should increase your battery life by atleast 20% if you reach the peak of your processors limit.

Bump, are there no other insights on this? Am I like, the only one who undervolted his/her note?
help

clairenix said:
Bump, are there no other insights on this? Am I like, the only one who undervolted his/her note?
help
Click to expand...
Click to collapse
I want to run 1700mhz as permanent and also wanted to undervolt but i wasnt sure how much by and what the risks are. Reason being is my phone gets hot with heavy usage running at 1400mhz so didnt want to go to 1700. I'll watch this thread with interest

kaos_king said:
I want to run 1700mhz as permanent and also wanted to undervolt but i wasnt sure how much by and what the risks are. Reason being is my phone gets hot with heavy usage running at 1400mhz so didnt want to go to 1700. I'll watch this thread with interest
Click to expand...
Click to collapse
I'm running 500-1700mhz.
Indeed it does get hot at 1700mhz, when I'm playing games but I've only at most played for 4 hours straight.
For what reason would you want to run 1700mhz-1700mhz?

clairenix said:
I'm running 500-1700mhz.
Indeed it does get hot at 1700mhz, when I'm playing games but I've only at most played for 4 hours straight.
For what reason would you want to run 1700mhz-1700mhz?
Click to expand...
Click to collapse
No sorry i meant running it at 1700 max, leaving it stock for the min. I just wanted to know how much i can safely undervolt 1700 by.

I actually have a question. I undervolted my note with SetCPU and I read that Tegrak Overclock Ultimate should be used as well together with SetCPU.
What does Tegrak Overclock do? GPU settings?
Would like to learn that part if anyone has any info.

kaos_king said:
No sorry i meant running it at 1700 max, leaving it stock for the min. I just wanted to know how much i can safely undervolt 1700 by.
Click to expand...
Click to collapse
I undervolted mine by about 100mah. I think I can tone it down by about 25mah more but I'm having a hard time getting it to stabilize.
1350 for my device is completely safe though.
Though, all processors are different. Yours could be better than mine and can withstand more UV-ing.
Goodluck!
liutszho said:
I actually have a question. I undervolted my note with SetCPU and I read that Tegrak Overclock Ultimate should be used as well together with SetCPU.
What does Tegrak Overclock do? GPU settings?
Would like to learn that part if anyone has any info.
Click to expand...
Click to collapse
It's basically the same with SetCPU aside from its voltages.
I do not know if it should be used with SetCPU with the note because from what I've researched. It's only a common practice with SGSII.

Tried setting 100 and 200 mhz to 825. Crashed my phone twice in one day using it, gonna revert back to 875

clairenix said:
I undervolted mine by about 100mah. I think I can tone it down by about 25mah more but I'm having a hard time getting it to stabilize.
1350 for my device is completely safe though.
Though, all processors are different. Yours could be better than mine and can withstand more UV-ing.
Goodluck!
Click to expand...
Click to collapse
Many thanks!
I will just experiment then, i didnt want to do that and then cause hw damage. I'll let you know how my processor gets on

Nexus 7 undervolting results - POST HERE

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