yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] Erahgon:
Sorry to point this out, but I'm still trying hard to fully understand:

Isn't this supposed to mean that the gate voltage is higher than the body voltage? Or am I not grasping the point altogether?

Similarly:

That apart:

If I want to clock my CPU to a frequency that was, by default, not possible, does that mean I must keep reducing the body voltage (slice 4) until it works/it's too low to be feasible. What are the practical limits?

On the other hand, say I want to make the slice 3 frequencies more efficient (with regards to power consumption, and consequently lower operational temperature). From what I understand, previously we would just try to achieve a stable lower gate voltage. Now, however, we can also lower the body voltage in order to achieve greater efficiency and stability.

Lastly, how do I achieve all this? My current approach is:

- To get the maximum possible clock speed with stock settings (by simply adjusting the maximum freq threshold in STweaks).

- Undervolt as much as possible on each frequency (i.e. gate voltages).

- Adjust the body voltage for each slice, to best match the RBB and FBB found on each frequency in the given slice by default (tweaking the gate voltages too if need be).

- Find the ideal body voltages to make previously inoperable frequencies work (by lowering the body voltages of the last slice (slice 4).

- Further optimize the slice 3 frequencies, by lowering the gate voltages, in order to increase RBB.

Could you please point out if, and where my understanding is flawed? Any help would be appreciated, as I'm trying really hard to understand for the sake of knowledge, as well as a means to an end.

Sent from the present, which is now in the past.
[Galaxy S III Original Android Development] nfsmw_gr:
[MENTION=4167023]AndreiLux[/MENTION]

I played around a bit with the 3rd slice body voltages and you were right.

I reduced the body voltage from default of 1300mV to 1150mV and i managed to undervolt an additional around -37mV to -50mV in higher frequencies (1300mhz-1600mhz) and no crashes or anything. :) (stress tested each frequency manualy)

Same goes for 1704mhz but body voltage was 1200mV in this case.

One question though regarding the gpu,how low you'd recommend to go on body voltage?

I run 640mhz@1050mv now fully stable but 1300mV body seems a bit too high.

EDIT:Also i could run 1800mhz now for a few seconds before it rebooted!

Before i coudn't run it at all,1704mhz was the absolute max...
[Galaxy S III Original Android Development] istillmyself:
erm noob here hopefully dont flame me :) avs0 - 12 ..i still do not understand the usefulness / the different asv from 0 - 12 ..which one is the best ?
[Galaxy S III Original Android Development] earthtk:
I have that problem too, it shows yellow instead of orange.
[Galaxy S III Original Android Development] STAticKY:
0 worst 12 best...
[Galaxy S III Original Android Development] istillmyself:
thanks ,i have checked and it asv5 .. what's the point difference each ASV? i also still do not understand why every phone so different:confused:
[Galaxy S III Original Android Development] STAticKY:
Well when the chips come out of the manifactur line they get tested and depending on how they perforn they get "binned" at diffrent levels(ASV). So the higher the ASV the better quality the chip and therefor has more potential with overclocking/undervolting. What andrei's new feature does is basically give us binning controll so we can get past the limits/restrictions that was put on your specific chip when it was binned in the factory... mind you not all chips of an ASV level ar equal at all. So to really get the most out of our chips we need lots of time and paientents and balls :P to put our phones through testing... and you could potentially fry your chip if you have no clue what your doing with this new feature.. so be careful
[Galaxy S III Original Android Development] Kaydin:
Same here. And it shows green instead of yellow.
[Galaxy S III Original Android Development] STAticKY:
I can confirm i have this smalll issue too..
[Galaxy S III Original Android Development] orangerot.:
In my case it shows green instead of red..
[Galaxy S III Original Android Development] i9100g user:
Yes it should theoretically, btw if you want to achieve more battery savings then try to keep gate voltage low with RBB.
[Galaxy S III Original Android Development] pistoke:
My bright pink is more like purple and there's no red.
[Galaxy S III Original Android Development] aurelm:
" I don't believe giving the users more choice is a very smart thing to do"

A big lol to that after I opened the STweaks app.

Anyway, probably the best kernel in the world. As an artist/photographer this is the first one that you can use to calibrate the display properly and have natural looking colors without losing the dynamic range of the amoled. After not much tweaking I managed to get a pretty calibrated display that I can now use to show my portfolio without burning out the retinas of the viewers (I already do a lot of saturation and contrast on images so the old settings were a killer).

That goes for sound too but I did not have any issues in general and I consider myself an audiphile.

I started switching kernels and roms recently as I noticed my battery goes down like crazy without having any strange wakelocks and rogue apps. If I turn out wi-fi and 3g it's ok in standby, but with screen on I barely can make 3 hours (even with this kernel). I saw a lot of videos where guys tested battery life and got 8-9 hours of play time and I wonder if there's something wrong with my setup, my battery or the fact that I use custom kernels that don't have the best toolchains in compiling or just have tweaks that are battery draining. Anyone could help ? The phone is allready almost one year old but I did not expect the battery to die out so fast.
[Galaxy S III Original Android Development] :
[MENTION=4167023]AndreiLux[/MENTION]: Thanks for your nice kernel. Its running fine so far. But what do you think about these features?!?

- ZZmove 0.4 governor

- Wifi driver from I9500

- new Mali drivers from n8000 sources (by rlorange)
[Galaxy S III Original Android Development] yugoport:
I get very good battery life with this kernel, and with realistic use, not like those folks that show a 8 hour screen time but the only thing that they do is to put the screen on and they don't use the phone for nothing else. I start the day at 7h and I have normally 2hours of calls during the day,1.5 hours of browsing , some texts , whatsapps and some time of screen on to take a look in some pdf files, and I reach to 10 pm with 50% of battery and 1h45 of screen on.

This should be a normal usage,3g and autosync always on,and Bluetooth on for at least 4/5 hours.

First check if you really don't have wakelocks, you can use the program wakelock detector, the first thing is to preserve your battery in standby.

Check if you don't have some apps that may be eating your battery life, use the app greenify and hibernate the apps that you don't need to have in background, I greenified all apps except the mail, whatsapp,viber,keyboard and the clock widget,greenifying maps,Google+ and Facebook gave s huge boost in battery life.

Then the screen, if you need battery life reduce the screen brightness to the minimum possible.

Finally, disable location services and GPS, use tasker to turn them on when you use some app that need it.

I can guarantee you a fantastic battery life with this steps and this kernel.

BTW, can you share your screen calibration, I'm curious to see what you have there, I need a good calibration for my screen.
[Galaxy S III Original Android Development] habylab:
He's said no to zzmoove already, and probably Mali drivers.

Okay, thank you!

Sent from my Galaxy S3. Long live the original Galaxy S :)
[Galaxy S III Original Android Development] AndreiLux:
You are correct, typo. I wrote it correctly first time round then edited something and mistakenly changed switched that too.

The LED colour problems are a bit weird, does it happen also when you turn off led fading in STweaks? I changed nothing related to colours, only brightness. It might be that third-party app's colour coordinates are getting overridden.
[Galaxy S III Original Android Development] ktmbikerman:
LED dimming

Not sure if it has been mentioned, but the LED dimming on v36 appears not to be working.
[Galaxy S III Original Android Development] shorty1483:
As far as I see the clean colors like red blue green yellow are working. Just "mix" colors like cyan or orange not. Tested with lightflow.

sent with Samsungs unleashed beast using Tapatalk 2

---------- Post added at 11:56 AM ---------- Previous post was at 11:56 AM ----------

Working well here.

sent with Samsungs unleashed beast using Tapatalk 2
[Galaxy S III Original Android Development] Kaydin:
I don't have any third-party app controlling the LED. It's definitely kernel related, since flashing to version 35 fixes those issues. Tried even deleting the settings. Didn't fix anything.

Yep, happens with LED fading off, too.
[Galaxy S III Original Android Development] tsubus:
Anyone with ASV6 that can share his tuned settings?
[Galaxy S III Original Android Development] RohanAJoshi:
It's hard to understand abb..

But I have few questions, plz ans who understands abb..

.

I have asv2, my cpu body bias voltages are 1000 to all 4 slices.

.

Now tell me that I need to increase them or decrease them for achieving good battery life ?

I don't want to run cpu at higher frequency, hardly max 1.4, no extra oc..

Plz help..
[Galaxy S III Original Android Development] Kyle07:
Glad to see a fellow member from the Motorola Defy section move into the S3 realm!

My LED is working (including fading) but all colours seem to be two-toned to some extent.
[Galaxy S III Original Android Development] ktmbikerman:
Good to see you here too Kyle...

Very strange LED behaviour here... if I increase the "Bright light environment brightness" setting, the notification LED gets brighter, but when the ambient light decreases, the "Low light environment brightness" which I've set really low, does not kick in and dim the LED. Maybe the threshold for the low brightness is a bit high?
[Galaxy S III Original Android Development] flexdog:
My chip has an ASV level of 3, and I'm just curious about the spreadsheet in the OP. I've read the past 10 pages and I'm still not sure what the spreadsheet is about. Currently I'm running 900, 900, 1250, 1000 for the 4 CPU slices (respectively), my max CPU frequency is 1300mhz.

If [MENTION=4167023]AndreiLux[/MENTION] or anyone else could kindly explain what the values on the table mean for me I would be extremely thankful.

EDIT: Wait nvm, found the answer on page 602 by Andrei himself.

Knowing that's the default values for the 4412 Prime in terms of body bias, should I try and match my body bias settings identical to the 4412 prime's?
[Galaxy S III Original Android Development] alirey:
I have also asv2 and 90% of time the cpu is on 200Mhz.

So i see no need to UV the other frequences.

My Slice 1 Voltage is at 850mV an the CPU gate Voltage for 200Mhz is at 750mV --> RBB of -100mV hasn't change

Everything is stable. I am listening music for the last 3 hours with 2%/hour battery drain.
[Galaxy S III Original Android Development] MuertoKo:
You stock 200MHz value was 900mV right? You are doing a -150mV UV O.o

Will start with experiments on my ASV3 if this ABB stuff lets you UV up to -150mV and still gain more battery by increasing the RBB this really sounds promising...

[MENTION=4167023]AndreiLux[/MENTION] , Any tip on how do you want reports about this, or you just need reports from people with special instruments this time?

Edit: Tried to replicate your config on my ASV3 device, all looks good until I entered to mono-core mode at 200MHz, that resulted in a bootloop. You can try to do this testing by lowering max. freq. to 200MHz and force 1 core online. This was the case that made my device bootloop. Careful when testing this things! This config. worked well on every try, until I switched to mono-core :P
[Galaxy S III Original Android Development] tolis626:
Seems most S3s are ASV3.I suppose there aren't many,if any,above ASV6.Anyway,I must say I hate my S3.I can't run 1800MHz it seems.It works for a few seconds,maybe a minute,and then bloop,bootloop.Then I tried undervolting the 1704MHz step a bit more.I've been using 1704MHz max clock with 1325mV for quite a few monhts (Since August or September) and thought that,maybe,25mV less would be possible now.My CPU seemed to agree at first,and ran fine with 1300mV for 3 minutes of stability test with a body voltage of 1200mV.I then tried 1275mV,it rebooted and now it won't work at 1300mV either.Strange stuff...Right now,I'd pay for an ASV7 or higher chip,but patience is the mother of success.Good news is that ABB seems to be working as intended.Even better news is that I've found alpha36 to drastically improve the phone's speed and snappiness,so it seems these new tweaks made the trick.Big thumbs up! :good:
[Galaxy S III Original Android Development] davtse:
I have an ASV07. TBH, it just makes things more complicated. Right now I'm wondering if a small value RBB is more battery efficient or a big RBB value.
[Galaxy S III Original Android Development] AndreiLux:
Version: 36.2:

- User-app notifications: Fixed colour scaling on the LED notifications, and also added brightness scaling. User apps will now also enter lowpower/high-power modes depending on outside brightness, just like the stock notification behaviour. Fixed the erroneous blinking behaviour for user-apps.
[Galaxy S III Original Android Development] squeeish:
I must be blind or something. Where's the download link? I can only see the link for the sources.

EDIT: Ok now I see it. It must have been taken down in the interim.
[Galaxy S III Original Android Development] alirey:
yes. -150mV UV at 200MHz with -100mV RBB. I use Erics Profile without oc and uv. I am a permanent mono-core user ;)

btw: I love this kernel :o thx
[Galaxy S III Original Android Development] orangerot.:
As always attached in the first post...
[Galaxy S III Original Android Development] davtse:
Can I just check if you set -100mv RBB because it's the limit of your device stability? Personally I have mine set at around -375 RBB, but am trying to figure out if a larger or smaller value RBB is more battery efficient.
[Galaxy S III Original Android Development] veteran_troller:
I am waiting for you to post the calibration setting:rolleyes:

Please do it

Sent from my GT-I9300

---------- Post added at 07:46 PM ---------- Previous post was at 07:42 PM ----------

Guys reading the recent pages of the thread I get a feeling that this is the most advanced kernel ever ... one thing that I am concerned about is that I am coming from adams kernel which is pretty basic and made for dope battery life...I am that guy who will use this kernel only for the calibration setting. I do not overclock . I do not tweak other settings . Can anyone tell me how to use this kernel with ease ? (By easy I only mean the overclock and ASV stuff going around from v36)

Thanks

Sent from my GT-I9300
[Galaxy S III Original Android Development] cba1986:
This kernel is my favourite by far. I reduced slices 1 and 2 to 900. Now i am testing -150uv in the 200 and 300 steps and -125 in all the freq up to 800. The standard for my device is -100. Lets see how long i can go.
[Galaxy S III Original Android Development] alberber:
I'm trying to understand all about abb and those things but I don't know if I have yet.

I'm on ASV6 and I've always applied an undervolt of -112.5 or - 125 to CPU. Can I undervolt it even more? I see people saying that with this new feature they can run 1.7 and 1.8 GHz but I'm not interested in overclocking.

So I lowered body bias voltages by 100 mV (in the three first slices) and undervolted CPU by 25 mV more, but it boot looped. Then I tried lowering even more bias voltages, by 200 mV and undervolted CPU by 25 mV again, and now it runs allright.

Do you think guys I'm saving battery or it'll be worse than before?

Please I am doing an effort to understand all I can but it's a bit difficult. Any help?
[Galaxy S III Original Android Development] aurelm:
Woo, I did not say I did any extreme professional calibration, I just did one that had the perfect saturation and no sharpness added by the Samsung mdnie.

That is I checked Register Hook and master sequence, left everything alone and changed Chroma saturation weight to 23.

The rest of the settings are very hard to master and perhaps need a Spyder like system to calibrate. Also color temperature can be easily tweaked toward warm or cold but I like it just the way it is.

However S-Amoled displays tend to vary from batch to batch (I have seen huge differences between phones) so my settings might not be ok.

But the default ones plus the little tweaks have been the best combination for me so far in over an year of testing kernels and mdnie tweaks.
[Galaxy S III Original Android Development] cba1986:
It depends on the chip too, not all chips are equals. My configuration could not work on yours even having the same ASV.

My phone for example is ASV3 and If you see my previous post i am doing some massive UV(-150 on 200 and 300 Mhz the i left it -125 up too the 1400 Mhz) and so far (finger crossed) is holding pretty well.

If you have any doubts check this post:

http://xdaforums.com/showpost.php?p=40620503&postcount=6034

It is well explained and easy to understand.
[Galaxy S III Original Android Development] alberber:
I've seen it, and it seems that my body bias (gate voltage - body voltage) is negative in every frequency. However I lowered by 200 mV every slice on abb tab (in CPU). My doubt is if this will save battery or actually drain more than before.

Btw thanks for the reply.

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] veteran_troller:
I turned to colour temperature all the way to 20K .... it made my display look very similar to iPhone? Please tell me I was doing mad **** here?:p

Sent from my GT-I9300
[Galaxy S III Original Android Development] ekie84:
Does perseus have cleaning script zip?thanks
[Galaxy S III Original Android Development] cba1986:
When you UV your phone you are already saving battery. Lowering body bias you can UV even more. And for what i read RBB is good on low and idling frequencies, because you are reducing leakage. Hope that helps.
[Galaxy S III Original Android Development] alberber:
Ok, thank you very much for your help.

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] alirey:
My device crashed at 700mV@200MHz --> 750mV was ok. I reduced body from 1000mV to 850mV to keep the same Bias.

As i understood:

- higher RBB Bias means more leakage.-100mv is better than -375mv for battery efficients

- higher FBB Bias is good for OC.

correct me if i am wrong.

btw. i would analize which cpu frequence your device mostly uses (depends on governor and other things) and only optimize these specific ones.
[Galaxy S III Original Android Development] AndreiLux:
No.

We need to clear up the terminologies here: RBB means negative body bias. FBB means positive body bias. (Again, body bias = gate voltage - body voltage)

- The higher the FBB, the more leakage and faster the transistor can potentially switch. You need less gate voltage than a lower FBB.

- The higher the RBB, the less leakage and slower the transistor can switch. You potentially need more gate voltage than a lower RBB.

If you guys find more easy, just ignore the FBB or RBB terms and just talk about + or - xxx body bias.
[Galaxy S III Original Android Development] Fienman:
So if i can run 200 mhz at 725 mv. How much should i keep my body voltage. I brought it down from 1000 mv to 800 mv.

Shouldnt bringing it down be better???
[Galaxy S III Original Android Development] tsubus:
I think I am beginning to grasp the concept, but please correct me if I'm wrong based on these assumptions:

1) I have ASV6, and I have lowered all 4 ABB slices by 150mV. This means higher body bias, which means faster gate switches, but more leakage = more power consumption.

2) I have undervolted all my CPU frequencies by 125mV. This means lower body bias, which means slower gate switches, but less leakage

3) Overall I have a difference of +25mV body bias compared to the beginning, but having reduced the gate voltages, I should be getting faster gate switching while also decreasing the power consumption

Is this correct or am I totally off track?
[Galaxy S III Original Android Development] MuertoKo:
Quite weird as we have same chip and different results :S

Just to make it clear, a higher RBB (more negative bias) achieved by lowering the ABB tab and not the CPU tab for example, drives to less leakage but potentially more needed voltage on CPU tab?

So it comes to play and try to lower body voltage as much as possible without touching gate, or lowering both bit by bit...?

I mean, you can priorize the lowering on ABB or on CPU tab to achieve stable results, which is better to set lower?

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] AndreiLux:
You are correct.

No. If you are lowering the ABB tab voltages while keeping CPU tab voltages the same that means you are increasing your body bias and has the opposite effect of what you describe.

I'm going to take a break off the explanations and questions from here on: there's plenty of concrete examples both by me and users who got it right. Please re-read it several times from now on.
[Galaxy S III Original Android Development] and8res:
Hi guys

What should I change in Stweaks if I want to have fast ( AC charging ) only ?

+

Is this issue related to the kernel ?

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

Thanks in advance
[Galaxy S III Original Android Development] pistoke:
There's still something wrong with the led colours. For example Light Flow shows pink as cyan or something like it. I tried to update kernel 36.2 twice, just to be sure. It didn't fix the problem.
[Galaxy S III Original Android Development] tolis626:
[MENTION=4167023]AndreiLux[/MENTION]

There seems to be a typo in the ABB tab in STweaks.I think it should be saying body voltage,not body bias in the sliders.Right?
[Galaxy S III Original Android Development] psyntific:
is -100 better than -350 in terms of power efficiency?
[Galaxy S III Original Android Development] habylab:
[MENTION=4167023]AndreiLux[/MENTION], on your explanation on the last page, should "thqn" where it used twice be "when"?

I think it depends on your original value, whether it has increased or not.

Sent from my Galaxy S3. Long live the original Galaxy S :)
[Galaxy S III Original Android Development] tolis626:
So...ABB does indeed work,but it doesn't do miracles.My ****ty CPU can't run at 1.8GHz no matter what.I tried with 1425mV gate voltage (maximum advised for 28/32nm transistors) and all body voltages from 950mV all the way to 1350mV.Nothing.I could at best get it to work for a minute or so.To decrease the gate voltage of the 1.7GHz step from 1325mV to 1300mV I had to drop the body voltage to 1000mV.1275mV is just impossible.So the question rises,is it practical from an efficiency point to drop the body voltage that low for such a small decrease in gate voltage?I can't know right now,but I'd guess that it's not better than my current 1325mV gate/1250-1300mV body voltage.Leakage can be neglected at that high frequencies,but too much of it should be made noticeable soon.What do you guys think?
[Galaxy S III Original Android Development] orangerot.:
Is it possible to use the lower brightness without the register r hook + master sequence enabled? I'd like to have the lower brightness, but I don't like the calibrated profile.. And the brightness setting only has effect if those are enabled :/

Thanks in advance :)