yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] tolis626:
You can disable master profile without disabling the register hook if you don't like the calibrated colors.However,you can keep the master profile and just crank up the chroma saturation.The default Samsung colours are plain wrong.Although you do get used to the calibrated colours quite easily.Give it 2 days and you won't go back ;)
[Galaxy S III Original Android Development] jimbo77:
You can punch the Chroma Saturation to match the colors you like in STweaks. THen you will have the benefit of the lower brigthness and the saturation of your liking.

EDIT: Sorry I replied but didn't Refresh the page before doing so, so tolis626 answer was posted before mine...
[Galaxy S III Original Android Development] Fienman:
In the same boat here. I was successfully able to run 1800 mhz once.

I mean i could always get it to start, but it would always crash after like 45 seconds of stress test. After Andrei introduced ABB, i managed to get it stable. I was able to run stress test for 2 mins. But that was a one shot wonder. I cant reproduce that at the same values now.

Also, few months before i actually took my cpu till 1500mv to get it run 1800 mhz. Sadly, i failed. Though i can run 1704 mhz fine all day long.

Makes me wonder if the reason we cant run 1800 mhz is maybe coz of some memory bandwidth starvation or something like that and not voltage??. I tried playing around with internal voltages too.

Also i feel like instead of doing FBB on high frequencies, we should settle with RBB. I think it should be better.
[Galaxy S III Original Android Development] orangerot.:
Well I thought about that too.. But the brigthness only goes down if both is enabled! enabling only the register hook has no effect.. No change until I enable the master sequenz.

Nah impossible :D I tried that, but after a few minutes my eyes hurt and I'm switching back to the dynamic samsung profile.. I like bright colors ;)
[Galaxy S III Original Android Development] teoB_Glar:
Hi,

A noob question here, i've been following this thread for a week (New To galaxy s3) and I was wondering how can I check the ASV version of my phone, just out of curiosity..

Best regards
[Galaxy S III Original Android Development] The Broken:
Tutorial: http://xdaforums.com/showpost.php?p=40662081&postcount=465
[Galaxy S III Original Android Development] mnickkk:
Hello, i just wanted to make sure if I understood everything correctly.

ASV: 5

This means, that samsung stock Bias values were: http://i.imgur.com/ChRTLId.jpg?

Default slices represent these 4 values:

Slice1: 1000mV

Slice2: 1300mV

Slice3: 1300mV

Slice4: 1300mV

freq | voltage | Bias (green-FBB,red-RBB)

1500MHz | 1225mV | (1225mV-1300mV=-75mV) which is 25 lower bias value than stock value, which is bad?

1400MHz | 1175mV | -125mV

1300MHz | 1125mV | -175mV

1200MHz | 1075mV | -225mV <----- slice 3 1600000]

1100MHz| 1025mV | -275mV

1000MHz | 975mV | -325mV

900MHz | 925mV | -375mV

800MHz | 900mV | -400mV

700MHz | 900mV | -400mV

600MHz | 875mV | -425mV

500MHz | 875mV | -425mV <----- slice2 800000]

400MHz | 850mV | -450mV

300MHz | 800mV | -500mV

200MHz | 750mV | -250mV <----slice1 200000]

What I should be doing now is increasing Slice3 value, to get lower RBB at 1500MHz? -250mV for 200MHz is also high value in comparission to samsung stock values, shall I incrase Slice1 value?
[Galaxy S III Original Android Development] sak500:
I'm on ASV 7 and can easily run it at 1800mhz for normal apps but with agressive UV using peter's script it crashes some benchmark apps. Mine's new hardware so probably that's the reason for good quality parts since i got my replacement phone last dec after the first one had SDS, which i had bought in May last year. For day to day use i use 1600mhz using agressive UV scripts by peter who posted it here somewhere and phone's been working fine for last 3 and half days without restart and gives me 1 day + few hours at 2 hours screen.
[Galaxy S III Original Android Development] Fienman:
[MENTION=4252205]sak500[/MENTION]

If you can run it through like 3 cpu passes of stress test then you have got a winner. Or else you are in the same boat as the rest of us.
[Galaxy S III Original Android Development] MuertoKo:
Sorry ment increasing ABB tab! Bad tipo there but I got it, electrical engineer here so this is "practically a mosfet" anyway, same voltage logic.

Will try to play with it for a while but still after searching couldn't find or think about the optimal combo on lowering ABB vs. lowering CPU in terms of consumption

Will play a bit

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] habylab:
Are your slice markers to the right of the frequencies wrong? I thought it was 0-200, 200-800, 800-1600, 1600-?

Sent from my Galaxy S3. Long live the original Galaxy S :)
[Galaxy S III Original Android Development] troyjamz:
Stable @ 1800mhz!

Hey you guys!

I have been messing around with with the ABB settings with the intention of getting my SGS3 (which has a ASV 5 chip) to run stable at 1800 mhz which was impossible for quite some time but I seem to have managed to get it it running stable! For the past 15 minutes my phone has been going through the stability test with 44 successful runs with a batt.temp of 44.5 degrees celsius.

I will post my settings in a minute, needs to be refined though. But atleast I got it running stable! :D

Here are my settings:

CPU

Slice1 1000mv

Slice2 1300mv

Slice3 1300mv

Slice4 1600mv

GPU

Slice1 1000mv

Slice2 1300mv

Slice3 1600mv

MIF

Slice1 1000mv

Slice2 1600mv

INT

Slice1 1000mv

Slice2 1600mv

Everything else in Stweaks are untouched for now just to test this. But atleast it's a start. Thanks AndreiLux!
[Galaxy S III Original Android Development] AndreiLux:
mnickkk, that table shows the bias values of the Rev 2.0 chip, it didn't apply to S3 users. I explicitly wrote that in the OP.

He's marking the groups, they're correctly labelled.

And your description should be 0-200, 300-800, 900-1600, 1600-xxx.

Troyjamz: those are some weird values, you're doing RBB even at 1800?..
[Galaxy S III Original Android Development] troyjamz:
Those values were just trial and error. The logic behind it was simply to increase the mv on the slices responsible for the frequencies over 1600 so I started at max and it worked. Now it's just to fine tune the thresholds since I had no idea where else to start.
[Galaxy S III Original Android Development] tolis626:
Well,my CPU may be a 32nm thick wafer of sh!t,but it seems my GPU isn't.It runs happily with an RBB of 100mV or more even at the highest frequencies (600MHz and even 666MHz).Lower frequencies even more than that.And I managed to sort out a quirk I used to have with some undervolting values.F*ck the CPU!If only we could overclock the memory...Ah!
[Galaxy S III Original Android Development] nfsmw_gr:
[MENTION=4167023]AndreiLux[/MENTION]

I've been stability testing my cpu and saw that after a while cpu clocks down to 1Ghz.

This is caused by thermal throttling right?

At what value does thermal throttling kicks in?

Can this be disabled/how dangerous is to disable it?

EDIT:Sorry for the questions bombardism,lol. :p
[Galaxy S III Original Android Development] tolis626:
Disabling it is far too dangerous.Especiallfly for people who overclock,it could mean frying their devices after a prolonged period of usage.Adjusting the thresholds to make throttling kick in at a little higher temperatures however would be sweet.But maybe it's left untouched.Maybe...

For benchmarking,however,I put the phone in the freezer and it scores as high as it can go.Yes,too far-fetched but it does the trick.Liquid cooling is far from usable on phones :P
[Galaxy S III Original Android Development] STAticKY:
What if we replaced the TIM with a higher quality one like nanodiamond.....

EDIT: would have to put a thin square of copper ontop of it too me thinks as the current TIM is a "pad" rather than a paste that is about 2mm thick

Doing so might alow us to push clocks a little further... pretty extreme i know.. but thats just me ;)
[Galaxy S III Original Android Development] nfsmw_gr:
Thanks man...

I now realise why antutu scores range way too far from one test to the other! :p

(example 12k to 18k+!)
[Galaxy S III Original Android Development] chiupc94:
Reboot for a several times and after each reboot my battery percentage changed from 82 to 77 and then back to 78.
[Galaxy S III Original Android Development] cba1986:
My personal testing showed me that decreasing body bias to 900 (1000 stock, i have an ASV3 device )in the fourth slice cause an immediate lockup and a consequente endless bootloop in the 1800 and 1704 frequencies. In the contrary if i increase it the device become more stabler and allow me to run both 1704 and 1800 steps normally (the 1800 is unusable on stock body bias).

Maybe high frequencies react different that the <1400 steps.
[Galaxy S III Original Android Development] pistoke:
I did some UV with the new kernel. If someone want to have a look at my settings here they are. I have ASV4 and these settings are meant to be really stable. I don't want rebooting phone while I need it... These are under testing and if someone sees possible unstabilities, I'd like to hear it. ;) This new thing took a while to understand, but I think I got it now.

f=frequency, g=gate, b=body, BB=bodybias

f	gµV	bmV	BBµV
1400	1225000	1250	-25000
1300	1162500	1250	-87500
1200	1125000	1250	-125000
1100	1075000	1250	-175000
1000	1025000	1250	-225000
900	975000	1250	-275000
800	937500	1250	-312500
700	912500	1250	-337500
600	900000	1250	-350000
500	875000	1250	-375000
400	862500	1250	-387500
300	837500	1250	-412500
200	750000	950	-200000

Maybe next some GPU tweaking. Looks like many leave it like it is. At least there's not much conversation about it.
[Galaxy S III Original Android Development] sak500:
AnTuTu stress test passed @ 1700mhz 3 times.. Didn't try 1800 yet.
[Galaxy S III Original Android Development] Fienman:
1800 mhz is the main problem mate.

Also i dont know what app people use to stress test.

I use an app called stability test from playstore. Its better than any stress test app i have ever seen. Give it a spin.
[Galaxy S III Original Android Development] miwanr:
Safest maximum OC is 1600MHz according to http://pdadb.net/index.php?m=cpu&id=a4412&c=samsung_exynos_4_quad_4412
[Galaxy S III Original Android Development] tolis626:
Erm...No,recommended maximum frequency is quite different than the maximum safe overclock,if there is such a thing.Overclocking isn't safe in its nature,so "safe" overclocking doesn't exist actually.However,we all should be able to overclock to 1600MHz,as there are already devices with the same SoC running at that frequency by stock.
[Galaxy S III Original Android Development] MuertoKo:
if I'm right you are decreasing body voltage, not bias (someone pointed this as a mistake on labeling in STweaks? Looks like as well to me actually).

Anyway, I think your testing differs a lot from what is intended to happen... by decreasing body voltage from 1000 to 900 you are increasing the bias value (more positive) you should be able to achieve higher frequencies, and it's going the other way round?

It doesn't follow the explained logic am I right? It should actually work better at same gate voltage if you decrease the body voltage, not the other way round :S

Edit: Not saying that it's not happening, just astonished with the results!
[Galaxy S III Original Android Development] tolis626:
Nope,all's normal,it's just the typo in STweaks.He just increased the FBB for >1600MHz frequencies.He is indeed decreasing body voltage,thus increasing the body bias.
[Galaxy S III Original Android Development] dragon135:
Hello,

I just notice the screen is somehow blurry in the middle part compared to the left part. I just flashed 36.2 and only enabled master sequence.

I attach the screenshot, you can see the left part is more sharp and contrast.

Edit: it seems the screenshot cannot capture this phenomena.

Sent from my GT-I9300
[Galaxy S III Original Android Development] MuertoKo:
Just re-readed his post and still i think he says he first increased body bias by decreasing body voltage to 900 (which should be a higher FBB and so allowing to achieve higher frequencies), and that made his device lock.

Then he did the the other way round and it worked for him :S

Hope he can clarify his steps, as if it's as I understand it it has apparently no sense (should have worked when he did it right at first, and never the other way round :S)

Enviado desde mi GT-I9300 usando Tapatalk 2

---------- Post added at 09:41 AM ---------- Previous post was at 09:40 AM ----------

If it can not be captured by screenshot might it be related to your display itself? Happens with other kernels?

Pd: nice to see my post on the picture lol

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] FD10:
Still same problem...with v.35 when i got a message, led was orange...now, with v36.2 (v.36 & v.36.1 too), led i yellow/green...
[Galaxy S III Original Android Development] pistoke:
I allready thought I'm the onlyone who still have led problems after update to 36.2. ;)
[Galaxy S III Original Android Development] tsubus:
Quick question: the last two ABB slices are split up 800-1600, 1600-x. Which slice is 1600 part of? I am assuming 800-1600 (based on the previous slices), but I just want to make sure.
[Galaxy S III Original Android Development] nfsmw_gr:
Tolis,you were right.

When i cooled the phone it run the benchmarks just fine...when it became hotter my scores decrased...

In conclusion,although my S3 was running rock-solid at 1704mhz cpu and 640mhz gpu,i lowered my voltages and frequencies to 1600mhz and 533mhz.

Now thermal throttling doesn't occur anymore,it runs at 1600mhz without dropping the frequency,and that's more important to me rather than win 100mhz for one or two minutes...

Thanks man. ;)

EDIT: Damn it!It hit thermal throttling again...-.-

EDIT 2: Okay i'm now convinced my cpu hates me.

I undervolted heavily and it hits thermal throttling even on stock clocks!

I give up...
[Galaxy S III Original Android Development] Sigray:
I tried some kernel and the Perseus is better than the others in battery life about 20%. Is it real or just "placebo", possible different usage? :confused:
[Galaxy S III Original Android Development] MuertoKo:
Trying to report a little bit in the (hopefully) correct way about my ASV3 chip.. Hope [MENTION=4167023]AndreiLux[/MENTION] can tell me if I'm doing it right:

Tried to raise Slide 1 body voltage to 950 but that ended up in a crashing. Same happened when trying to raise Slide 2 and 3 to 1000 after the UVing.

Does this seem logical? I should have less leackage due to the -100mV UV in all frequencies without any drawback as I was able to achieev a -50mV RBB more than I had at the begining... Am I right this time? Partially right at least?

In case you can't see the image above:

freq	gate default	UV	gate	body	bias

1400	1287500	-100000	1187500	950	237,5

1300	1237500	-100000	1137500	950	187,5

1200	1187500	-100000	1087500	950	137,5

1100	1137500	-100000	1037500	950	87,5

1000	1087500	-100000	987500	950	37,5

900	1050000	-100000	950000	950	0

800	1000000	-100000	900000	950	-50

700	975000	-100000	875000	950	-75

600	962500	-100000	862500	950	-87,5

500	937500	-100000	837500	950	-112,5

400	925000	-100000	825000	950	-125

300	900000	-100000	800000	950	-150

200	900000	-100000	800000	900	-100

PS: I'm aiming for the best battery life posible without any OC, hate my device running hot so that's why I didn't go uper than the stockish 1.4GHz for now unless what I do is anyway helpful for the Dev, if it is I can test anything.
[Galaxy S III Original Android Development] cba1986:
First i want to clarify that my device can handle -100 uv in the 1704 freq without modifying any values. The 1800 freq is barely usable in the launcher and crash in benchmarks.

My test was this:

1)Stock voltages for both 1704 and 1800 freq and 1000(stock)in the fourth slice. All normal. Stability test ran normally.

2) -100uv in 1704, stock voltages for 1800 (i have been using this combination since november) and 1000 in the fourth slice. Stability run properly.

3)Same voltages as step two only this time i decreased slice fourth to 900. Automatic lock of the device and subsequently bootloop.

4)After resetting all values i set the same values as step 2. Only this time increased Slice 4 to 1200. Stability test on both 1704 and 1800 ran properly.

I know that that results are against the logic. But that is how works on my device. Perhaps i am doing something wroing, i don't know.:confused:
[Galaxy S III Original Android Development] MuertoKo:
Then I understood your previous post correctly :D looking forward to an answer on this behaviour

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] STAticKY:
I must say iv had some strange things happen to my phone when messing about with this more indepth control of voltages...

Several times after getting reboots from instability my phone resets its self????? Like it must wipe data/cache or curroupt peices of it... weird ehh

Sent from my portable powerhouse
[Galaxy S III Original Android Development] i9100g user:
I am able to uv without any instability,my settings are :

1400mhz:1050000

1300mhz:1000000

1200mhz: 975000

1100mhz: 975000

1000mhz: 950000

900mhz: 900000

800mhz: 875000

700mhz: 875000

600mhz: 850000

500mhz: 825000

400mhz: 825000

300mhz: 825000

200mhz: 825000

Slice 1 at 600mv

Slice 2 at 700mv

Slice 3 at 1000mv

And my chip is binned asv4.

Edit:900mv at slice 3 is stable too.
[Galaxy S III Original Android Development] MuertoKo:
I'm still not very sure if my values are wrong or not, but imho you are doing something weird there... I mean, on 200MHz freq. you have now a ABB of +225mV, which is just way too much (Andrei said somewhere you'd like to aim to RBB (negative) values on those frequencies, with my config for example I have -100mV here.

I think the aim is not to UV every posible thing (CPU and Body) but to find the balance
[Galaxy S III Original Android Development] tcchuin:
is your internal storage full? or is it close to full?(less than 1.5GB free space).

I had the similar problem before the introduction of the voltage thing, and I solved it by clearing unnecessary files.
[Galaxy S III Original Android Development] gun@id:
i'm no expert in this but it look like your doing FBB in every step cpu freq, does it mean that more power leakage.

i think mr. muertoko is right, maybe all is about balance, or maybe wrong.
[Galaxy S III Original Android Development] STAticKY:
Not at all. It mostly empty. My externalsd on the otherhand has about 512mb free but i dont see how that could affect it

Sent from my portable powerhouse
[Galaxy S III Original Android Development] i9100g user:
Actually i was testing the limits of under volting(both gate voltage and body voltage), btw for normal usage I keep slice 1 at 950mv, 2 at 1000mv and 3 at 1100mv with same gate voltages posted before, which keeps RBB almost same as default settings , but overall gating voltages are lower.
[Galaxy S III Original Android Development] pistoke:
Let it cool down for a longer time. It should help.
[Galaxy S III Original Android Development] cba1986:
Testing -150uv on 200Mhz and 300Mhz with stock ABB. I'am testing how long can uv with standard values and then modify abb values to see if i can uv even more. I have an ASV3 device, so a -150uv without modifying anything it's really outstanding.

Update: -150 with stock abb values is too much uv for the 300Mhz step i will try to decrease abb and continue testing.
[Galaxy S III Original Android Development] alberber:
I undervolted CPU by 150 mV except 200, 300, 800, 1200, 1400 steps (137.5 mV) and I lowered body voltage by 200 mV. It seems stable.

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] ffolkes:
This is to be expected, as you're essentially pulling the plug on the system when you lockup/random reboot. This can lead to corruption, which is why you should ALWAYS nandroid first, then restore it when you're done experimenting.

Also, I'm pretty sure it would be a good idea to make sure dynamic fsync is off while you're experimenting to avoid data corruption.
[Galaxy S III Original Android Development] :
Is it correct that the colour calibration is not applied on the lockscreen? I can notice a big difference between locked or unlocked when using the same image.
[Galaxy S III Original Android Development] cba1986:
Now i decreased abb in the first and second slice to 900. Testing -150 in the 200,300 and 400 frequencies. With 950 abb crashed after 15 minutes of stability test.
[Galaxy S III Original Android Development] tolis626:
Of course it hits thermal throttling even at stock clocks.The phone might not feel hot and the battery temperature might not be that high,but the CPU is producing more than enough heat to make its temperature soar over 50C quite quickly.If you want to benchmark and get the highest possible scores,just let it cool down for a few minutes.Actually,given how hot the weather is getting here,I'd give it a lot of time to cool down as much as possible.Even the fridge is a good idea.The freezer I use is quite extreme,so it's a "don't try this at home" solution.I once forgot it in the freezer and found the phone dead after 10 minutes.It took about another 10 for it to come back to life.

Finally,don't expect undervolting to do miracles.Don't forget that we are talking about millivolts,so even -150mV isn't THAT much.It will lead into less heat radiated,but not make the CPU run cold all of a sudden.Do the math to see what I'm talking about.

EDIT:About these guys that lower the body voltages by too much to achieve somewhat lower gate voltages,don't do it.It's debatable whether it's beneficial to increase FBB by too much for high frequencies in order to achieve lower gate voltages,because leakage at high clocks could,in theory,be neglected.We just don't know how much leakage there is at any given moment,so a verdict is hard to make without proper measuring equipment.In low frequencies though,where leakage is maybe the primary source of power drainage,it's in your best interest to aim towards a high RBB to reduce it.Power used by the CPU to work at,say,200MHz under load is really low,so here it's the other way around than what it was with high frequencies.The decision is yours though.
[Galaxy S III Original Android Development] Handeman707:
After updating the kernel to v36 alpha "stweaks" don't works? It says no root or timeout acces?
[Galaxy S III Original Android Development] ffolkes:
I thought I had a pretty good grasp of this, but something is puzzling me enough to clutter this thread with more questions. I can't sleep. :|

Example (ASV1):

1600MHz

Stock gate: 1312500mv (-750000 default body = +565500 bias, as confirmed in the chart)

Lowest stable gate UV: 1125000mv (-750000 default body = +375000 bias)

Now here's my question: Now that I've hit a wall in this example frequency (I can't do 1100mv even with a 700mv body voltage), shouldn't I now look towards effecting as much of a RBB as possible? That's to say, keep it at 1125mv, but increase the body voltage to reduce the bias and therefore reduce leakage until I hit instability? Is my logic correct?
[Galaxy S III Original Android Development] tolis626:
Yep,it's correct.You've minimized power consumption from the CPU's functioning at that frequency.Now all you have to do is minimize leakage/maximize efficiency.

PS:750mV is too damn low ;)
[Galaxy S III Original Android Development] and8res:
Hi guys

If I want to have fast charging ( with AC charger only )

What should I change ?