yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] melo_mx:
I'm using 1458mhz at 700mv, and it's working fine no problem, however if i set everything below that point to 700mv it crashes and reboots. so i set the min&max to 1458mhz at 700mv. it works fine,

however I need to test this thing out a bit longer, as I think that the voltage is so low that the hardware system resets it to the default mv, without letting you know.

Anyone have any thoughts about this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wavrunrx:
im telling you bro;

you are not running @1458mhz with 700mV.

no.

just no.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] melo_mx:
here's some screenshots
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Un my opinion, if any lower freqs can't run @700mv than there is no way a higher one would. I don't understand yet why this is happening but it isn't logical at all.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Soo yeah.....

KT has said through pm's it's definitely applying.

It's worked at every other voltage it's not line it's a Fluke.

I benchmark and monitor cpu temps and there's like a 5 degree Celsius difference between 700 and 1200mv.

Decide for yourself.......
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Shaddy-Z.:
Holy hell that looks dangerous. I just do Ktoonservative and noop 96-1890 with a screen off at 486, with -100 UV across the board. I don't think I could bring myself to do 700 mV for those frequencies. But if you're getting good battery life and it's stable, more power to you.

@melo and baconator, what's your battery life undervolted that much? Should last pretty damn long.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
You see that he's got 1080MHz running at 1175mv. He's probably not even ribbing at those higher frequencies. He probably has his max MHz set at 1080 & took a screenshot to try to look cool or something! His phone would crash w/ those mv set at those frequencies.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Lol nope.

Here's the temperature differences. Between 700mv and 1200mv. It's in the status bar(on bottom since it's paranoid android)

9 Celsius is a lot

You can see in cool tools on top that it's 1458 with 100% cpu load while running stress tests with stability test. The temp reader in cool tools it's Bayer temp, not cpu

The one with 26 passed runs was @700mv.

Both times it was charging.

Dude phones are different, they have much different build qualities. sorry yours can't undervolt as much
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] endlessevo:
I'm not saying I don't believe, that you believe its undervolting that much. I just don't believe its actually undervolting that much.

There should be an easy way to verify though, set min too 1134 and max to 1512 change voltage to 700mv and hit apply if it actually runs off 700mv between 1134-1512 why would you run any other steps?:confused: Especially at a higher voltage?:confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Because power consumption is not only a function of voltage but also clock speed. So 1134 at 700mv uses much more power than 384 at 700mv.

I think the actual formula was posted in this thread or maybe the kernel thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] endlessevo:
Ok, but if his chip at 1512 can handle 700mv why wouldnt 1080-96? Also why run 1080-96 at stock speeds? I'm still sticking by my feeling that 1512-1134 are defaulting to his stock 1080 speed of 1125mv.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Did you not look at the temperature differences between stuck voltage and 700mv?

The temp difference is the only convincing thing for me.

9 Celsius is a huge difference.

Trust me I've been skeptical too
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Well ktoonsez has stated several times that that is not the case, but everyone is entitled to their own opinions.

I'm no expert or anything but i imagine there must be some lower limit on power consumption built into the processor. So say 1134 mhz at 700mv draws enough power to keep things stable but 384 at 700mv (remember drawing MUCH less power) causes the cpu to think somethings wrong.

again im no expert just speculating.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
For speculation that sounds right. I'm not sure what else controls the cpu but I know there's a herbal regulator that shuts a core down when it gets too hot

Who knows if something controls power consumption....

Very interesting this is
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] endlessevo:
I saw the screenshots but don’t feel like a difference in temperature is proof; I mean what were the starting temperatures? Room temp? Where was the phone? 9 degrees is a good jump but happens fairly easy.

Get a copy of trepn profiler and use it Trepn Profiler it should tell you what your actually running on each core.

Go under preferences/select data points/power sensors I selected all 3 and also added cpu0 and cpu1 frequency too under cpu stats

click profile app select stability test and it will graph individual cpu voltage while running.

Trepn Profiler is a Qualcomm Developer app.

I understand that ktoonsez said that it doesnt/wont default I've just never seen a processer that could run lower voltage on a higher clockspeed with out being able to run the same voltage on lower clockspeeds.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Both room temperature, probably 72 F or something

The 700mv test was with charger on, 19 minutes of stress testing while sitting on my bed while i showered.

I screenshoted then put the 1458 step to 1200mv and started testing again

The second test(1200mv, 11 min) was on the charger will sitting on my desk and i watched the temps climb steadily past the original high point of 51 C all the way to 60 C. I figured that was proof enough. It probably could've gotten hotter if i let it go longer. both times it was on the stability test screen, so only the cpu was being used(theoretically) there weren't any graphical calulations going on...

the cpu and screen should've been the only things making heat.

cpu voltage change was the ONLY variable.

Have you used the app? I'm curious to know if it actually works, i'm using system tuner currently. I don't plan on doing any testing tonight but i might, I've got a big test tomorrow....

on a side note if you guys still don't believe me i could record a video showing what i do.

melo_mx confirmed it. maybe he has a super phone also.

if you guys are so skeptical why don't you guys click off set options on boot and slide that voltage bar to the bottom for whatever your max is.... some phones can undervolt more than others. a guy in the kernel dev thread said he couldn't do less than -5 mv.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
You've never seen one b/c there isn't one that is currently being made that can do that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] endlessevo:
I get that every phone is different but what your claiming isn't possible... Can you set all your steps to 700mv? If you could I'd be more inclined to believe your claims... Having a chip that can use less voltage at a higher speed vs lower speeds is unheard of.

Also as for trepn I've played with it a little but will do more testing tomorrow during the day. The app is made by Qualcomm for there chips also anandtech did a review on the MSM8960 chipset I'm sure it works

That's kinda what I was getting at, just doesn't seem physically possible
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
I wouldn't pay any more attention to this guy.

---------- Post added at 12:20 AM ---------- Previous post was at 12:13 AM ----------

If he's doin it, good for him...No since in arguing over it for 5 days. He's got the only superphone that can do it. Leave it at that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
melo_mx was able to confirm 700 mv @1458.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Apocalypse487:
At my current settings, my phone rests at 96 Mhz at 735mV. The temperature stays at 64°F. During heavy use it only gets up to 96°F at 1809Mhz, 1135mV. I don't see the point of lowering the mV to 700. It barely uses anything.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] endlessevo:
I know but if he really is doing it, it shouldn't be hard to prove especially after I posted the Qualcomm developer app used to map power consumption...

He didn't really confirm anything... I can post screen shots of my phone running at 700mv across the board but that doesn't mean it's actually doing it. Download trepn profiler and I'll believe you when I see the results.

I ran one full cycle on stability test's scale test and as you can see my voltage coincides with my clock if your settings are right your higher clocks will show a huge drop in voltage. Also you could export to csv and upload that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
I will look into it tomorrow, i've got a fluids and thermodynamics test to study for. i'll be free to test this weekend. I want to try this. I'll do tests on both stock voltage and 700mv. there should be a difference. If there's not I'll be contacting Ktoonsez again. He's certain it's applying but if not I'll see what he has to say about this.

don't forget, just looking at the screenshot it says it's measuring power which is different than voltage.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] melo_mx:
I just tested it, and it's measuring the CPU power in mA not mV, so it still won't proof it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] endlessevo:
It will show a big difference in ma at 700mv vs 1200mv

Run stress test at stock for 1 min vs 700mv for 1 min

add in load and frequency and screen shot the stats screen after each run.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
Anybody have some good settings for the KT 747 Touchwiz kernel? I'm running the 10-31 build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dankest:
Oc & UC

96mhz-1890mhz

I/O scheduler: Deadline

Scheduler adjustments:

Fifo_batch= 2

front_merges= 0

Read_expire= 250

Write_expire= 2000

Writes_starved= 4

CPU Governor: Abyssplug

Governor adjustments:

Boost_timeout= 5000000

Down_differential= 12

Down_Threshold= 50

Hotplug_in_sampling_periods= 5

hotplug_out_sampling_periods= 15

Ignore_nice_load= 1

io_is_busy= 0

Sampling_rate= 200000

Up_threshold= 85

Touch booster 1st= 1350mhz

Touch booster 2nd= 810mhz

Voltage:

MHz. Voltage

1890. 1220

1809. 1195

1728. 1170

1674. 1145

1512. 1120

1454. 1105

1404. 1100

1350. 1090

1296. 1080

1242. 1070

1188. 1045

1134. 1000

1080. 980

1026. 960

972. 940

918. 920

864. 900

810. 880

756. 860

702. 840

648. 830

594. 820

540. 810

486. 800

384. 790

192. 780

144 770

96. 760

Extra settings:

Screen off profile MHZ= 486mhz

Screen off profile GOV= Adaptive

Can't find anything else that performs better. Credit for adjustments to liltitiz. UV is my own.

AT&T SGS3

ParanoidKangDroid 1.1.0 ROM

KT747 10/31 OC'ed & UV'ed

Medical MJ Supporter
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NYYFan02:
I'm assuming it's ok to run the 10.31 build on the 10.28 AOKP 4.1.2 build? i.e. the kernel date doesn't have to match the ROM build date correct?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] endlessevo:
correct. The 10.31 aosp kernel on the 10.28 aokp will be fine they are 2 separate things.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NYYFan02:
Thanks, I was 99% sure that was the case but just wanted to doublecheck, I'm thinking of flashing it (haven't flashed a kernel before) to see if it helps improve my battery life and lower the heat generated by my phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dankest:
Be sure to wipe caches and fix permissions after install. Good luck!

AT&T SGS3

ParanoidKangDroid 1.1.0 ROM

KT747 10/31 OC'ed & UV'ed

Medical MJ Supporter
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dntesinfrno:
Did you bother reading the thread? It is littered with setting including analysis of battery life with screen shots....:confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MColletti12:
Would anyone be kind enough to direct me to a few links where I can learn to undervolt/clock KT747 - LJ7 - KTweaker 10/31. I am on rom AOKP (task and ktoon) 10/31. I've looked but haven't found anything that would begin to explain this process of changing voltages and kernel settings and what not. Any help would be appreciated and thank you in advance!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
There's not much to be explained. No phone will react the same to undervolting or overckocking. You'll have to test it by yourself. Be sure to disable the Set on boot option and lower your voltage until weird things start to happen then you'll know you've gone too far for some frequencies . So, from there, you will have to test each step one by one to find what are their lowest stable voltage. But like I said no phone are the same, some can't under volt 5mv and others will do -200mv across the chart.

If you feel lazy, there are plenty of voltage table and setting posted in this thread, just try them but I can't guarantee your phone will like it. Like I said, disable the set on boot option and you'll be safe anyway. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dankest:
Before you under volt you need a general knowledge of what it does to your phone. I highly recommend this post,

http://xdaforums.com/showthread.php?p=33282284

AT&T SGS3

ParanoidKangDroid 1.1.0 ROM

KT747 10/31 OC'ed & UV'ed

Medical MJ Supporter
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] threshold350:
I'm one of few unfortunate ones who can't undervolt. I get lock ups when using the phone and then it reboots.

So far, I've used Wheatley and sio using Stock voltage table and so far no lock ups or reboots. Battery has been decent. 2-3hrs screen time for 15hrs on WiFi and cell using stock battery.

I also had to lower my clock a step to 1.6 due to 1.7 rebooting even on stock voltage.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jebise101:
I applied the voltages below and added 10 extra mV across the board yesterday and am getting hot boots. KT recommended i RMA my device because it just freezes with ondemand governor i'm not yet ready to RMA. Been using ktoonservative for a few days now and that has been fine but after undervolting yesterday i'm getting random hot boots, I have seen 2 during the 5 hours of being unplugged and who knows how many times it has rebooted since turning on 14 hours ago. Any recommendations to stop the hot boots?

Only reason to undervolt was because of the heat issues and to get better battery.

CPU governor: ktoonservative

I/O: CFQ

No sleep profile

Everything else is default

KT Build 10/28

Voltage:
MHz. Voltage
1512. 1120
1454. 1105
1404. 1100
1350. 1090
1296. 1080
1242. 1070
1188. 1045
1134. 1000
1080. 980
1026. 960
972. 940
918. 920
864. 900
810. 880
756. 860
702. 840
648. 830
594. 820
540. 810
486. 800
384. 790
192. 780
144 770
96. 760
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
Use noop instead of cfq. And raise your voltage. I'd say 25 across. Just to see if that fixes it

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Ok... In response to everyone believing my phone can't apply 700mv. I've taken the time to walk through trepn profiler and stability test with my screen recorder on.

It's paranoid android btw...

Keep in mind my S3 is running stable with 700mv @1458, a screen recorder, and a stability test in the background.

http://www.youtube.com/watch?v=rPBa30QSSjE

It's not very pretty but it's showing what's going on.

There's a difference between current and power and voltage. Trepn profiler won't show power in mW correctly, current in mA is fine, voltage is not in this app. Current is different then voltage, voltage is just the ability/potential to move a given amount of charge through the circuit, current is the amount of charge through the circuit.

Also here's my settings file. It almost definitely crash your phone, but you can see the settings.

http://db.tt/Cd9pZ31Q

Now will you believe me and melo_mx?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jebise101:
Another 25 on top of what i have or another 15 with the 10 from yesterday?

Also why noop over cfq?

Any way to track the hot boots?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
you can use stability test, set max cpu to whatever frequency you are testing the voltage at, if it crashes the app then you need more volatage on that step. it takes awhile but you just keep moving up through the frequencies till you find something stable for each frequency.

IO schedulers don't make too much difference, cfq has worked fine for me. try starting with stock. some phones suck for undervolting. build qualities are different for each phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
This is real guys, I followed his progress thru PM's the last several weeks. NO JOKE HERE!!!!!!!!!! :good: :p :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MColletti12:
Liltitiz and Dank, thank you very much for the information.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dankest:
NP bud, spread the knowledge around :thumbup::thumbup:

AT&T SGS3

ParanoidKangDroid 1.1.0 ROM

KT747 10/31 OC'ed & UV'ed

Medical MJ Supporter
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
I just tested it, I set my min/max to 1458 and dropped the voltage to 700mv and it is stable... :what: I really don't understand this black magic in this kernel....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
I did some more testing last night, I found out that if I set my min/max to the same freq and lower that freq to 700mv everything is stable for every freqs. But if I set my min to 96 and max to 2106 and then lower every voltage to 700mv it crashes. I find it kind of weird...

But for now I lowered everything from 1134 to 1512mhz to 700mv and its running great... I'll do some more testing, I clearly don't understand what is going on... :confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jebise101:
Thanks this helped a lot. Is the phone suppose to be stable at lower frequencies? I set the max to 918/864 and the phone starred to crash and freeze or they need more voltage?

I increased 918 about 20mv and it did become more stable but still had force closes and then it froze after a while.

This is very tedious work so I'm just trying to avoid more testing :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
I also use this app to test the stability of my phone

https://play.google.com/store/apps/details?id=net.bsayiner.benchmark.SuperPi
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Start from stock and work work down. It takes forever if you have a frequency that keeps making you crash when you're not working on that specific frequency.

Like I said start at the top with 1512.

The goal is to make one frequency stable at a time.

Tell it to not set options on boot.

Set the min to 1512 add max to 1512. Once you've done that ( while at stock voltage) start stability test, classic test and go back to ktweaker. Begin slowly lowering the voltage on 1512. Eventually your phone will lock up and crash. You will see on screen before if goes black and reboots what value made it crash. Take that value add maybe 20mv or so and keep testing until that's stable and never crashes.

Once you've got one frequency move the min and max down to 1458 again, you want your phone only to run on 1458. Start the testing all over, being lowering the voltages till it crashes, then raise it.

Keep in mind your chip wasn't designed to run at 96, 96mhz is like for times slower than stock. I've had trouble with the lower frequencies.

I haven't done much testing like this for a while it's what I do when I'm testing though.

But you are correct it's very tedious :p good luck!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] threshold350:
This where in at now, stock values. I'm not sure what is causing my reboots.

384/1512

intellidemand/cfq

stock voltage

594 max sleep

Touch booster stock

I've been running this for a few hours and no lock ups. Before going back to stock, i rebooted 3x this morning with this setup

192/1694

Wheatley/sio

Stock voltage

594 max sleep

Touch booster stock

I'm guessing my phone can't handle the 192. I even up the 192 by 10mv. I'm also guessing that 192 Wheatley muddy not be good for my phone since Wheatley likes to hang at the lower frequency based on CPU Spy.

One thing I did do last night was flash a new splash image. The one before bootanimation. I'm wondering if this kernel doesn't like the image to be replaced cuz when i reflashed 10/31 kernel I got the stock Samsung image back.

Luke others have said, this is a long process to keep the phone stable but i cam deal with it. I just have to keep telling myself, baby steps. I tend to want to change more than one thing due my impatience.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
It's it bad for the processor to only run at 1512mhz??? I am using this right now testing batt life. J/w if it could be real bad for the phone not too scale like it was designed to.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dankest:
Unorthodox? Yes.

Bad for processor? No

I don't see any reason if the phone is stable and running at highest stock value(1512) would be bad at 700mv.

I might even go as far to say it would improve the lifespan of the CPU by generating less heat when charging and such.

AT&T SGS3

ParanoidKangDroid 1.1.0 ROM

KT747 10/31 OC'ed & UV'ed

Medical MJ Supporter
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
Ok. I wanna check out what it does for battery life.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jebise101:
I should correct my statement. I started from 1542 and worked my way down until i got to the frequencies like 918. I used the voltages a few pages back and for the most part they have been stable. I used the stability test on each frequency for 2 passes until i got to the 918 and lower. That is were the phone seems to freeze and force close. What i wanted to know is if its normal that it freezes or should it function normally?

Im thinking of restoring 918 and lower to stock voltages and then work my way down, like you said. If its suppose to function normal at low frequencies.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] melo_mx:
After i did testing of my own, I pretty much got the same results, set on only one frequency increasing the voltage showed no mA change at all, but if i changed frequency to a much lower setting, the mA dropped tons. i'm not sure what that exactly means, since mA is a completely different measuring system than mV

---------- Post added at 05:07 AM ---------- Previous post was at 04:53 AM ----------

Here's my settings config, this one hasn't crashed on me yet. It's worked it off Bacon's config file, just with 1080mhz and lower frequencies modified to a lower stable voltage. this will save you sometime perhaps

https://dl.dropbox.com/s/bcf3zt1npz2ic0g/melo_mx settings v1?dl=1