yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] Erahgon:
Sorry for the multiple posts, but I have to confirm:

I have an ASV 3 chip as confirmed in abb_info. By default the values for my CPU ABB slices 1 - 4 are all at a 1000mV.

The GPU tab shows 1000mV for the first, and then 1300mV for the other two.

Are the default values ok?

Also, for memory and SoC ABB voltages, the frequency is mentioned as 110110 or something. Bug?

Sent from the present, which is now in the past.

---------- Post added at 12:53 AM ---------- Previous post was at 12:49 AM ----------

I think it kicks in at 15%. Or rather that's when the notifications appear and the camera (amongst other apps) isn't allowed to be used/ flash gets turned off.

Sent from the present, which is now in the past.
[Galaxy S III Original Android Development] nfsmw_gr:
Hey guys,just wanted to share my voltages too. :)

Runing stable for two days now,stability tested too.

What do you think?

EDIT:It used to be an excel document but i accidentially killed the file. :(

Anyway,hope this seems okay.

EDIT 2:It's mV not Mv,sorry i can't edit the file.
[Galaxy S III Original Android Development] AndreiLux:
Yes.

The MIF and INT frequencies are tied together in MIFINT frequency pairs. 110110 is 110Mhz for both. The Rev 1.1 chips only run at 100100 but I took the Rev 2.0 chip frequencies as the frequency wall since it doesn't really matter as they overlap. Read the changelog again about the bus frequencies.
[Galaxy S III Original Android Development] The Broken:
And how do I find the default? It is not stated in stweaks (got ASV 3)

And what is meant by: "if you changed then to borderline stability values" ?

I only changed the 2nd slice for GPU by 50 mV to get a more positive bias. I didn't change the voltages after that.
[Galaxy S III Original Android Development] pat357:
Could it be that you mean "decreasing the body voltage" instead of "decreasing the body bias" in your first sentence ?

A "body bias" from 900 or 1000 seems a lot .....
[Galaxy S III Original Android Development] papakaliati:
Here goes the excel.

AVS2 is blank but its mine Avs so i upload it for someone to fill it :P
[Galaxy S III Original Android Development] pistoke:
I think you could easily get lower volts at 200MHz. I had stability porblems while testing at 200MHz first, but after I took gps, wlan and mobile data off, I could use lower voltages than before without freezing. I think one of my apps used net and caused bad slowdown. I thought it freezed and booted my phone...
[Galaxy S III Original Android Development] henrybravo:
With all the awesome new features and tweaking control that has been added to this kernel over time (mDNIe control, ABB/voltage control, LED control, ZRam control, audio control, etc, etc, etc) it's probably time to reword or remove these obsolete sentences from the OP. ;)
[Galaxy S III Original Android Development] faithhh:
GPU table first step default body voltage 1000 ? not 1300 ? soo body voltage must be 750 mV for 266 mhz gpu I m right or not ?
[Galaxy S III Original Android Development] AndreiLux:
There's a difference between choice and configuration: I'm giving people configuration options. The sentence is still valid in the sense that I'm not going to allow people to use some unoptimal CPU governor, screw around with CPUIdle modes or some other shenanigans which was "in" during a few months ago. I should reword that sentence since it can be confusing now, but the original point I was trying to make is still valid: I know best what's good for you (Snark snark), so in that regard, you don't have a choice.
[Galaxy S III Original Android Development] nfsmw_gr:
I think it was 1000 on all first slices,though i'm not sure.

About the second part that depends on how low voltage your chip can handle..;)

Anyone has any comment on my settings guys,how do they look to you?

---------- Post added at 01:35 AM ---------- Previous post was at 01:33 AM ----------

Thank you so much man!

Much appreciated! :)
[Galaxy S III Original Android Development] JustArchi:
And that's really cool ;).

I know Andrei that you won't implement zzmove (and you have a very good reason, I totally respect that) but is there any chance to add some "preset" which would act similar? Like automatically tweak pegasusq governor? (You said that it's possible or at least will be to get similar effect :))

I'm asking because you know best how it should look like and I think that it's not hard to implement such little feature. Like "preset" option under CPU Governor select.

Thanks.
[Galaxy S III Original Android Development] STAticKY:
Is it possible to use the device on power without charging and without draining the battery?

Sent from my portable powerhouse
[Galaxy S III Original Android Development] tisazalay:
Plug it in and remove battery. Might work.
[Galaxy S III Original Android Development] JustArchi:
I can confirm that.
[Galaxy S III Original Android Development] STAticKY:
Really. All it achieved for me was kill my phone :P are you sure that works? Is it kernel spacific?

Sent from my portable powerhouse
[Galaxy S III Original Android Development] JustArchi:
I'm not quite sure but I can assure you that I can do it through running ArchiDroid with Perseus 35
[Galaxy S III Original Android Development] habylab:
So lower bias is better power wise? I thought a higher bias than what you started with was better for power?

Yep, Samsung just haven't released their charger for it still ( I think).

Sent from my Galaxy S3. Long live the original Galaxy S :)
[Galaxy S III Original Android Development] psyntific:
Can some one tell me if I'm doing this right and if there is a way I can make this more efficient???

Frequency (Mhz)	Default Gate Voltage (mv)	Gate Voltage (mv)	Final Gate Difference (mv)	Default Body Voltage(mv)	Body Voltage(mV)	Final Gate Difference (mv)2	Final Result(mv)	FBB/RBB

1400	1300	1175	-125	1000	1000	0	175	FFB

1300	1237	1137	-100	1000	1000	0	137	FFB

1200	1200	1100	-100	1000	1000	0	100	FFB

1100	1150	1050	-100	1000	1000	0	50	FFB

1000	1100	1000	-100	1000	1000	0	0	RBB

900	1050	950	-100	1000	1000	0	-50	RBB

800	1000	900	-100	1000	950	-50	-50	RBB

700	975	875	-100	1000	950	-50	-75	RBB

600	950	850	-100	1000	950	-50	-100	RBB

500	950	850	-100	1000	950	-50	-100	RBB

400	950	850	-100	1000	950	-50	-100	RBB

300	925	825	-100	1000	950	-50	-125	RBB

200	900	800	-100	1000	900	-100	-100	RBB

Should I keep FBB only for 1400MHz and RBB for everything else?
[Galaxy S III Original Android Development] pistoke:
Lower bias = Less leakage

Main thing achieving lower power consumption is decreasing gate voltage, which decreases bias. (gate voltage) - (body voltage) = (body bias). This is what we did earlier, when we could change only gate voltage. Yes, that was better for power. ;)

Now we can fine tune our settings by changin body voltage. Higher body voltage = Lower bias = Less leakage = Less power consumption = Slower gate switches. It doesn't matter (much) if you have higher or lower bias than when you started, as long as you have changed your gate voltage. Bias can be lower or higher than starting bias, it's not the main thing. It's just fine tuning. I just don't know how fine it is. If I increase body voltage (->lower bias) like 25mV, I'll get faster gate switching and more leakage. Can I lose crucial few seconds more time to call? What is the benefits of getting faster gate switching? Are these things impossible to see without proper machines, which means that I just should forget it?

The main thing in changing body voltage is to be able to change gate voltage even more, which actually gives the less power consumption or the benefits of OV.
[Galaxy S III Original Android Development] psyntific:
Thanks for your amazing work andrei...

Confirmation number: 7XN88908VU2711415.
[Galaxy S III Original Android Development] pistoke:
Calculate your default body bias(fbb/rbb) and try to get close to those values by changing body voltages(slices) after you think you have changed enough gate voltages. Then you can't have badly wrong values. My default biases were all rbb.
[Galaxy S III Original Android Development] omniwolf:
the only thing body bias does for power, is reduce static leakage when you have an RBB situation. If you have FBB, then all it does is allow greater stability in higher clocks. by reducing body voltage, you can reduce gate voltage as well while maintaining a stable FBB, which allows you to have overall less voltage and better battery life.

this looks good. try furhter reducing your body voltage at higher frequency steps - it may allow you to further reduce the gate voltage. push the limits :)

as i understand it, slower switching won't lose you speed in use of the phone, it'll just mean that you have less chance that the frequency you're switching at will be stable. Same with faster switching (higher FBB), it won't make your phone faster, it'll just allow a higher level of stability at that frequency. The fact that we can control the bias now potentially allows us to reach higher frequencies with stability.
[Galaxy S III Original Android Development] The Broken:
Can someone tell me his/her default ASV3 voltages?
[Galaxy S III Original Android Development] flexdog:
I read people asking if this kernel really does provide better battery life than other kernels, and I just wanted to share, my results.

The results I'm getting are astonishingly good. 4 hours screen time at about half brightness all day isn't a placebo in my opinion.
[Galaxy S III Original Android Development] chiupc94:
I have 17 hours battery and 4.5 hours on time with auto brightness(minimum), data and wifi on all the time and moderate usage.
[Galaxy S III Original Android Development] MuertoKo:
Thanks for clearing this, so my testing method is still valid? Glad to hear. Will keep the testings today for a little while, just one little question, if due to excesive UV my phone crashes, it should bootloop, stuck on boot logo, do a hot-reboot...? (Just in case it's any app missbehaving due to excesively low frequency or something in case it's posible it happen.

Thanks :D
[Galaxy S III Original Android Development] plakers:
My ASV2 for the moment if it can help a bit, quite stable, need to push these settings a bit (and calculate my real RBB/FBB for my freq. table ;)). But we see some important differences even on same Chip' family

CPU_VOLT_1600=1350000

CPU_VOLT_1500=1250000

CPU_VOLT_1400=1200000

CPU_VOLT_1300=1150000

CPU_VOLT_1200=1100000

CPU_VOLT_1100=1050000

CPU_VOLT_1000=1025000

CPU_VOLT_900=975000

CPU_VOLT_800=925000

CPU_VOLT_700=900000

CPU_VOLT_600=850000

CPU_VOLT_500=850000

CPU_VOLT_400=800000

CPU_VOLT_300=775000

CPU_VOLT_200=750000

BUS_INT_VOLT_100=825000

BUS_INT_VOLT_133=850000

BUS_INT_VOLT_160=900000

BUS_INT_VOLT_200=950000

BUS_MIF_VOLT_100=800000

BUS_MIF_VOLT_133=850000

BUS_MIF_VOLT_160=850000

BUS_MIF_VOLT_267=900000

BUS_MIF_VOLT_400=950000

arm_slice_1_volt=850

arm_slice_2_volt=950

arm_slice_3_volt=1050

arm_slice_4_volt=1050

g3d_slice_1_volt=850

g3d_slice_2_volt=1050

g3d_slice_3_volt=1200

mif_slice_1_volt=900

mif_slice_2_volt=1050

int_slice_1_volt=900

int_slice_2_volt=1050
[Galaxy S III Original Android Development] AndreiLux:
They're getting printed out in the kernel log at boot, it'll depend on the ASV. The Rev 1.1 mappings are relatively very simple with all slices up until and including ASV3 being 1000mV, ASVs beyond that have 1300mV on everything except 200MHz which is still 1000mV.

To be honest it was a mistake to not include the ABB voltages in a controlswitch like the other configurations, I'll have that changed in the next version and also echo out the defaults in the STweaks interface.
[Galaxy S III Original Android Development] The Broken:
Thank you, it took me a while but I found them.

ABB stock voltages for GPU are for me : 1000 - 1300- 1300
[Galaxy S III Original Android Development] Kaydin:
So, in the end, after reading all the posts since version 36 (from the Note 2 & S3 forums), is a higher RBB recommended than having a balanced sort of voltage between gate and body? Or should increasing the slices in STweaks decrease power consumption together with UV to the gate voltage? Should we RBB until the device feels unstable, or should we balance it more?

Thank you!
[Galaxy S III Original Android Development] jeebspawnshop:
Thanks man! These values work great on my ASV2. With the additional UV achieved with these values, I imagine my phone won't get QUITE as warm in this horrific Mediterranean heat and maybe even a little more battery in the long-run.

:good:
[Galaxy S III Original Android Development] moinakbera:
How to install this on tipo dual
[Galaxy S III Original Android Development] jimbo77:
Unless you can convert your TIPO on a GALAXY S3 INTERNATIONAL i9300 i seriously doubt you can use this kernel.

You are on the wrong section buddy, this is only for Samsung Galaxy S3 International Variant.
[Galaxy S III Original Android Development] cgvelmax:
Hey jimbo you have an ASV2?
[Galaxy S III Original Android Development] davi_ssilva:
Hi Andreilux!

I have a little question that's a bit off topic, but may be important for many users here in a near future: which version of S4 are you intending to get and develop for? The "snapdragon 4g quad core" or the "exynos 3g octacore"?

Enviado de meu GT-I9300 usando o Tapatalk 2
[Galaxy S III Original Android Development] psyntific:
I think he'd mentioned before that it's gonna be the Exynos one when he does
[Galaxy S III Original Android Development] ffolkes:
He'll develop for both, even if we have to buy them for him. :D
[Galaxy S III Original Android Development] salvatore94:
Thanks, working great on my ASV2. But are you undervolting GPU?

Inviato dal mio GT-I9300 con Tapatalk 2
[Galaxy S III Original Android Development] jimbo77:
Nope mine is a ASV5 :D
[Galaxy S III Original Android Development] cgvelmax:
Im asking the same thing.

This are my values

I have another question for the ASV2 users you could handle 1800 step on cpu or 640mhz on gpu?

With the first i have a bootloop and for the second makes artifacts.

Mine is a ASV2. you could send me your user on twitter or g+
[Galaxy S III Original Android Development] amppen:
I guess I could share mine here too (ASV2) :D

I'm attaching it as a picture so the columns won't get messed up.

ABB for slices 1&2 = 900, slice 3 = 1000, slice 4 = irrelevant. My idea was to duplicate the FBB/RBB for ASV2 as seen in the OP's chart and not to UV too much as my phone crashes easily if I get too wild with the UV. Note that the UV for 900 MHz = 0, the importance of this depends on your governor (i.e. how often your governor scales to that freq).
[Galaxy S III Original Android Development] davi_ssilva:
Yeah, I remember it, but it's been a long time since then, so I was wondering if he'd changed his mind

Enviado de meu GT-I9300 usando o Tapatalk 2
[Galaxy S III Original Android Development] jeebspawnshop:
With those ABB values, I have my GPU at -75mV on all steps, and OC to 533.

Works just fine in games and stress tests... so far.
[Galaxy S III Original Android Development] psyntific:
I've gpu at

160MHz - 800mV

266MHz - 850mV

350MHz - 900mV

440MHz - 950mV

533MHz - 1000mV

ABB for gpu

Slice 1 - 850mV

Slice 2 - 950mV

I've been testing it playing need for speed n it seems stable
[Galaxy S III Original Android Development] AndreiLux:
Even if you buy me a 9505, it won't be nearly as feature-heavy as what I can do to the 9500 (Sounds kinky). I prefer to deliver quality on a platform I'm good at rather than deliver a jack-of-all-trades-master-of-none like other devs (faux, franco, etc).

But feel free to donate to offset this package that's arriving on monday:

Date/Time	Activity	Location

- 4/27/2013 - Saturday
8:09 pm	Arrived at FedEx location	ROISSY CHARLES DE GAULLE CEDEX FR
6:35 am	In transit	MEMPHIS, TN
2:36 am	Departed FedEx location	MEMPHIS, TN
12:36 am	Arrived at FedEx location	MEMPHIS, TN

- 4/26/2013 - Friday
6:47 pm	Shipment information sent to FedEx
6:13 pm	Left FedEx origin facility	NORTH HILLS, CA
4:44 pm	Picked up	NORTH HILLS, CA

:)
[Galaxy S III Original Android Development] papakaliati:
i9500?? Haven't seen it around on any review site , just the i9500 model , thought it was only out on South Korea or something :o
[Galaxy S III Original Android Development] drakester09:
It's the Exynos variant. Most countries will not get it.
[Galaxy S III Original Android Development] papakaliati:
Course i know what it is, i just thought its not out yet :p
[Galaxy S III Original Android Development] AndreiLux:
If you wait till summer, I have a slight tingling in my butt that says you'll get to enjoy Exynos LTE versions, the i9500 was also scheduled to arrive in Europe on a later date.
[Galaxy S III Original Android Development] Kemby13:
[MENTION=4399452]papakaliati[/MENTION]

There are some tests already out, as always google is your friend :)

http://www.androidauthority.com/galaxy-s4-benchmark-exynos-5-octa-version-gt-i9500-available-179752/

[MENTION=4167023]AndreiLux[/MENTION]

If he or anyone for that matter waits till just after the summer, there is a big chance to get the Exynos version. I'm talking about Eu countries...
[Galaxy S III Original Android Development] t4d73:
That's where the Note line comes in. :D
[Galaxy S III Original Android Development] Kemby13:
The tested unit had the latest firmware up and running, not some prerelease - as it states in the text. Anyway, if u are searching for a gsmarena-like test u'll just have to wait a bit longer...
[Galaxy S III Original Android Development] cba1986:
Without touching any ABB values i can so a rock stable -100UV. Decreasing ABB to 800 i managed to do a 175UV. But i increased 125v Body BIas in all frequencies. My question is: to which values should i pay more atention?

Lower gate voltage or a lower Body bias?

Now, leakage really affect that much bettery life?

EDIT: updated UV values
[Galaxy S III Original Android Development] mattiadj:
I have understand nothing of abb settings! Sorry for my stupidity.... I have asv3. What it means? Which are advantages of tweaking this? How can I tweak these?

Sorry but I'm totally new about this! I have read op... All discussion but I need some better and simply explanation...

Thanks

From universe with my gs3
[Galaxy S III Original Android Development] zenosteam:
+1 :thumbup:

Envoyé depuis mon GT-I9300 avec Tapatalk
[Galaxy S III Original Android Development] tsubus:
Read the discussions again. It has been explained in a very clear way multiple times. It's pointless to repeat the same thing over and over.
[Galaxy S III Original Android Development] mattiadj:
For you mate... I have made what you suggest me... No luck.

Maybe a little summary would help

From universe with my gs3
[Galaxy S III Original Android Development] jeebspawnshop:
Bro... read these! And try searching and reading over-and-over until you understand.

If, after that, you fail to understand then LEAVE IT ALONE.
[Galaxy S III Original Android Development] STAticKY:
I think what alot of people arnt understanding is that unlike generic oc/uv we cannot just use each others profiles as every chip is diffrent... we can get a rough idea of settings that people are using based on our ASV level but in no way will those settings be taylored to your individual device.... they are all diffrent and thats why we have binning otherwise there would be way too many disfunctional devices out there. It allowes the manafacture to use not so good chips in devices and have them still run fine rather than just throwing them away.... some of us are unlucky in that we get the worst ones for uving/ocing... thats just the luck of the draw.... and like everyone is saying. Read... read.. read...

Sent from my portable powerhouse
[Galaxy S III Original Android Development] chiupc94:
Hi, I seem to have an issue with perseus kernel lately. I get bootloops with default setting. At one point the battery monitor shows 35% and then when it got into recovery mode, the battery shows only 17%.
[Galaxy S III Original Android Development] omniwolf:
body bias is a delta, it's not an actual voltage supplied to the chip at any point. Gate voltage is always the one you want to reduce, especially at higher frequencies.

maybe? hopefully?! we need someone with an electrical engineering background and some voltage measuring tools to do some emperical and controlled tests of battery drain with different body bias values. From my subjective testing it seems to work pretty well. I have a bunch of push accounts running, 4G always on (no wifi), and i got 35hours 100% - 0%, with 6h20m screen on time, but this is on a galaxy note II, so don't get too excited :)
[Galaxy S III Original Android Development] davtse:
I'm getting an increase in my perceived battery life as well. Whether this is a placebo effect or not, only a controlled experiment can tell. But for sure there is an improvement in terms of heat production.

I'm undervolting by up to 175-200mv on some frequencies, and about 125-150 on the rest, on the border of instability. Hopefully someone can do a measured experiment so we can tell how much battery savings we're getting.
[Galaxy S III Original Android Development] shaarky:
With Perseus kernel Sdcard got damaged twice, each time only reformat fixed it.It occurred always after reboot via Widgetsoid widget.With Boeffla kernel it's not happening.Anyone has similar experience?
[Galaxy S III Original Android Development] cgvelmax:
No problem at all, coming from perseus 25 to 36.3 and I have no problem.

Maybe it's boeffla kernel problem.
[Galaxy S III Original Android Development] cba1986:
Thanks for the corrections.

Managed to do a great UV in the [1400..900] range. But I noticed that lower freqs[800..200]are quite unstable even reducing ABB to 800 and using the same UV that higher freq. Particularly i cannot push 200 freq beyond 775 even lowering the ABB value to 800

Here there is a table with the voltages i managed to get stable(ish):
[Galaxy S III Original Android Development] pistoke:
How did you test? Did you have wlan, gps and mobile data off? I got lower volts, while tested without wlan, gps and mobile data. I've been using my phone normally for a while, and no problems.
[Galaxy S III Original Android Development] habylab:
What values in parituclar would help combat micro lag, when scrolling for example? I was on CM10.1 and did not have these issues with Temasek's kernel, is it the kernel or Omega ROM? Thank you :)

Sent from my Galaxy S3. Long live the original Galaxy S :)
[Galaxy S III Original Android Development] Erahgon:
If it gives you problems with Wi-Fi, GPS, and mobile data being on, then it isn't to be regarded as stable.

I look at these ABB voltages as a bell curve (as Andrei mentioned a few pages ago), with there being an optimal setting. It also varies with temperature I presume.

I look at this as a great add-on to the undervolting we were used to (i.e. lowering the gate voltages). To get some extra stability, we can now lower the body voltages too match the ABB correctly.

After this, some additional lowering of the gate voltages can be done (increasing RBB, greater negative ABB) to lower the current leakage, and hence increase power efficiency and thermal stability.

Sent from the present, which is now in the past.

---------- Post added at 01:16 AM ---------- Previous post was at 01:12 AM ----------

I think it's got to do with all stock 4.1.2 ROMs.

I have a hope that when the stock 4.2.2 ROMs come, it'll have some better GPU drivers.

The current CM 10.1 GPU drivers are a combination of reworked drivers from the 4.2.1 leak along with some previous sources, I've heard. Which is why it's so good.

Sent from the present, which is now in the past.
[Galaxy S III Original Android Development] habylab:
Well the leak definitely has a smoother GPU. I really hope so. Things like the loading circle and app opening and much smoother and quicker on CM10.1.

I'm only back on stock to get the best camera available! Hoping 4.2.2 leak is good!

Sent from my Galaxy S3. Long live the original Galaxy S :)
[Galaxy S III Original Android Development] cba1986:
I tested it with this:

http://xdaforums.com/showthread.php?t=2072087

Maybe placebo but i noticed that the phone is somewhat smoother in transitions that before when only used -100uv.