yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] Slimer777:
If you have a red tint, try to get used to it. If you can't then just add a little green and blue in white. I would try this before touching colour temperature control.

The problem is that we currently only have a single point white control and the original profile for the SGS3 was done in 135 cd/m2 as I can remember (which is about 65-70% brightness). So when you when your brightness goes up or down, you are simply displaying another shade of grey from the RAW standpoint.

---------- Post added at 11:27 AM ---------- Previous post was at 11:24 AM ----------

Please read the reply above.

I am not a 'bright screened' person, but I wouldn't sacrifice correctness for battery life that's for sure. Lowered luminosity should yield higher battery life as the final consumption is lowered.

---------- Post added at 11:29 AM ---------- Previous post was at 11:27 AM ----------

Raise your brightness a little. Grey is good, grey is neutral and that's what we want to achieve! Grey is a shade of white, so power it up to achieve your desired 'white'.

---------- Post added at 11:35 AM ---------- Previous post was at 11:29 AM ----------

Don't be frustrated. How you do think Andrei can develope such an exceptional kernel? The guy has VERY high expectations for everything including the members! I am lucky he hasn't yell at me, yet!:laugh:
[Galaxy S III Original Android Development] tolis626:
Well,I do like my screen being bright,but can live like that,my battery life's pretty lame anyway the wa I abuse the poor phone.My question was purely theoretical. :)

I see your point and that's the counter argument to what I posted.It all comes down to how screen brightness is handled it seems.Hmm...
[Galaxy S III Original Android Development] Slimer777:
You are correct. The Samsung's colour management parameters are vastly different from what's out there in the video world especially the naming of controls.

A word of advice, DON'T change anything except white balance and saturation weight. Unless you REALLY know what you are doing!

---------- Post added at 12:00 PM ---------- Previous post was at 11:50 AM ----------

I don't get as much feedback from this thread. The Note II people just got an update and they seem to like it.

There are ways to give us more 'punch' on the SGS3. The generation 1 profile for the Note II was not as good as the gen1 SGS3 but if we have enough input I guess we can go one step further and make it even better. As the gamma control on the S3 seems to be more reasonable and performs better.......somehow.:confused:

We will wait a couple more days for members to adjust to the new colours before tweaking anything.
[Galaxy S III Original Android Development] jinosong:
I think most S3 users are more content than the Note II guys because our calibration was good from the beginning. Also, a lot of people have moved on from the S3 to the Note II or Nexus 4.
[Galaxy S III Original Android Development] Slimer777:
I happen to have a Nexus 4 too! That is if Andrei feels like working on it. I haven't done measurements on it but it definitely has a low gamma and a blue tint!

Do you guys remember that one user reported back that he has compared the master profile to his HTC OneX and said that they are very close in white? Look at the picture below;

And people say my white balance is too warm.........:eek:You are just so used to the blue, look at the picture with Samsung's original profile.

Like I said before, most cellphone makers would rather make the white bluish than normal as people tends to think blue is cleaner.
[Galaxy S III Original Android Development] jinosong:
OMG a Nexus version would totally rock. I can't believe how blue the S3 is either.
[Galaxy S III Original Android Development] brenogbi:
Re: [Kernel][28/02] Perseus

Do you will make a version of this kernel to sammy 4.2.1 leak?
[Galaxy S III Original Android Development] jinosong:
I don't think they can yet because the base isn't available.
[Galaxy S III Original Android Development] Anakha56:
Well I am not much of a colour expert and am so used to the saturation from the S2 & 3 that I am just super happy to see a better, cleaner colours. So I would have no idea on what feedback to give :).
[Galaxy S III Original Android Development] mamba720027:
Re: [Kernel][28/02] Perseus

I'm using your default calibration at the moment. Maybe my eyes getting used to the change still.

Anyways wance I enable SCR to start trying to add a little more green and blue in white as u suggested I notice that my screen saturation and brightness slightly increased before I evin make the changes. So I didn't bother proceed further and just have master sequence enable since I prefer the correct calibrated colors.

I have every other settings under screen at default.

Sent from my GT-I9300
[Galaxy S III Original Android Development] MuertoKo:
Re: [Kernel][28/02] Perseus

Posible to see a picture like the one above including an S3 with master profile ticked? Just curious...

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] Slimer777:
I ripped it off the web so I guess not.
[Galaxy S III Original Android Development] Kemby13:
It's also important to remember that not every individual s3 is calibrated in the same way. My device for exsample, doesn't have that blueish tone when the background is white, even without enabling the master switch (samsung default in another words). I compared it with a friends one x...
[Galaxy S III Original Android Development] sachilleas:
Re: [Kernel][28/02] Perseus

I have enabled master sequence in stweaks. I restored defaults in stweaks but nothing changed although the master sequence was now unticked!

I had to tick and untick it again and apply changes to get back stock colors. Is this a bug of stweaks?
[Galaxy S III Original Android Development] tisazalay:
It was reported before. You need to manually toggle master sequence, after that everything is normal. Not that much a bug but an annoyance.
[Galaxy S III Original Android Development] Amanoo:
OTG + charge that you're supposed to get by putting a 40.2k resistor between ID and GND doesn't seem to work. I get a few beeps implying that the phone detected that something happened, but no OTG. Even a simple mouse that works in normal OTG mode doesn't do anything. The phone seems to get charged, but that's it. Nothing else. It just charges.
[Galaxy S III Original Android Development] tsubus:
Re: [Kernel][28/02] Perseus

At first, as expected, everything seemed "washed out". After a couple of days my eyes got used to the calibrated colors and everything is much better. Watching soccer videos is an obvious example: the grass looks fluorescent on stock Samsung settings
[Galaxy S III Original Android Development] joeherlev:
Sv: [Kernel][28/02] Perseus

Please Help me to Flash this kernel??

I have tryed many times and very time I end up in bootloop..

Have tryed both zip and tar..many times
[Galaxy S III Original Android Development] privat75:
AW: [Kernel][28/02] Perseus

AOSP, CM and 4.2.x are no supported
[Galaxy S III Original Android Development] skivnit:
Re: [Kernel][28/02] Perseus

Hi Andrei. Are you gonna update this one as well? My s3 now looks weird when put next to my n2 both are running ur kernel :)

Swyped from another galaxy
[Galaxy S III Original Android Development] jimbo77:
Re: [Kernel][28/02] Perseus

I love the new colors... I can't believe how good my eyes feel when looking at the screen, it is just great!

In the other hand I have a heavy lag Mish of the times when waking up the phone from deep sleep, it lags badly and also the sound with an incoming call lags a lot...

Is anyone else having such issues of has any advice on how to solve them?

I'm running stock odexed MR2 + Perseus 33.3, all profiles are default ones
[Galaxy S III Original Android Development] tolis626:
Re: [Kernel][28/02] Perseus

Well,Slimer777 asked for a report,so here you are.On my display,the closest I can get to perfect white is -10 on the reds and +5 on greens and blues.Also you may need to adjust gamma a little.Transitions from dark to light gradients are a little too pronounced.
[Galaxy S III Original Android Development] brenogbi:
Re: [Kernel][28/02] Perseus

This kernel have the sds fix?
[Galaxy S III Original Android Development] MuertoKo:
Re: [Kernel][28/02] Perseus

Epic LOL... Yes, it does... Please read a bit next time, at least you made my day xd

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] nfsmw_gr:
Does this kernel has Samsung Update 8 intergrated?

And yes,this is not in the op.
[Galaxy S III Original Android Development] AndreiLux:
No. Update 8 only changes a few things in a total of about 10 files, biggest being that MMC thing which I can't currently update as I'm using something else.
[Galaxy S III Original Android Development] pat357:
It's not that simple , especially not for the OLED because there is a huge difference in efficiency expressed as [Lumen/W] between the different colours.

Green gives the highest output in Lumen/W, then comes red and finally with an order of magnitude difference, comes blue.

To say it in simple words : a blue plane would require more power [W] than a green plane at the same light output.

Also, the more blue a picture contains, the more power [W] it requires to output the same amount of lumen's as the other colours red or green.

Then you have the difference in sensitivity for the human eye for the different colours., but this would bring us to far away.

Anyway, I hope you got my point as a professional developer after 15 years activity in the lighting business.
[Galaxy S III Original Android Development] AndreiLux:
All of this irrelevant because the OLEDs have different voltages and are calibrated to have the same luminosity.

RGB are all at the same luminosity and power consumption releation between each other isn't interesting to us. If you reduce luminosity they use less power, as simple as that.

Here's an extract in the middle of the voltage tables; hardly "order of magnitude", and actually green is the one with the highest voltages.

<4>[ 0.599524] c0 Gray Level : 208 - R : 2813V G : 2920V B : 2657V

<4>[ 0.599565] c0 Gray Level : 209 - R : 2809V G : 2916V B : 2653V

<4>[ 0.599606] c0 Gray Level : 210 - R : 2805V G : 2911V B : 2648V

<4>[ 0.599647] c0 Gray Level : 211 - R : 2801V G : 2907V B : 2644V

<4>[ 0.599688] c0 Gray Level : 212 - R : 2797V G : 2903V B : 2639V
[Galaxy S III Original Android Development] pat357:
But if you reduce the green and put up the blue (because you think it's needed for correct colours), your screen will consume more power than before at the same luminosity. That was my point.

A colour correction which leads to less luminosity does not always consume less power ; it can even consume *more* power and have less luminosity !

This is especially true for OLED; for not much for LCD because the luminosity is mostly determined by the backlight.

What you say about the voltages is correct, but Power (read battery consumption) is still correlated to [ Voltage x Current ] !
[Galaxy S III Original Android Development] Slimer777:
From my limited experience of Samsung OLED panels, SGS1 , 2 and 3 exhibit the same kind of behavior in greyscale. Too much green and lack a lot of red and a little blue. I am surprise that you need to turn down the reds even further but if it works for you that's what important.

You bring out a good point about gradients transition. From what Andrei could pull out of Samsung, the number of gamma control points are more than one needs but they don't seem to interpolate too well inside the driver, or they don't at all. Andrei can correct me if I am wrong but if that is the case then no matter what you do on the kernel level, you just can't change it. Usually adjusting gamma should not change greyscale so much but in our case it does and the only thing that can correct it is if Andrei can dig out the multi-point greyscale control. There maybe one or there may not to begin with.

Look at the bright side, we are in the ballpark.
[Galaxy S III Original Android Development] AndreiLux:
I think you're mistaking luminosity with colour hue, lowering luminosity will reduce power, there is no scenario where lowering luminosity consumes more power.

It's not that simple anymore, that would have been correct in the first generation devices like the Omnia or the S1, but the current display controllers have advanced colour saving techniques beyond the user's control. That option in the Display settings "Auto Adjust Screen Tone" is actually Automatic Current Limiting which is an advanced power saving technique which reduces actual luminosity without reducing perceived luminosity. On top of that there are several undocumented proprietary methods like Multi Power Saving (MPS) which I have no idea what it physically does.

Read this paper: it describes dynamic voltage scaling on OLED displays, it's I think something very similar to ACL which we have on our phones: http://atrak.usc.edu/~massoud/Papers/OLED-DVS-dac11.pdf Check figure 10 for a quick peek on the advantages. This is completely transparent to our measly calibrations we're doing on the front buffer.

It's vastly more complicated than people think it is.

It is possible to calibrate that but it is an insane amount of work which I don't think we will be able to achieve. Different power savings techniques on the electronics levels are kicking in on the different brightness and gamma levels, and as such it's something much more complicated than simply changing RGB on greyscale levels 0-255.
[Galaxy S III Original Android Development] pat357:
Voltages alone doesn't say anything about power consumption : you also need the currents.: the amount of mA that flows through the OLED.

Remember from school P[W] is determined by [Voltage(V) * Current(A)]
[Galaxy S III Original Android Development] Slimer777:
You are both correct. But the original poster was asking as we have already calibrated the display to a certain level, if he lowers the brightness would he save power. In the case where you have a constant calibration setting, lowering the luminosity of ALL colours will save power.

Of course then if we lower green one unit but raise blue one unit (say to maintain total luminosity), the current consumption on the blue should exceed power saved by lowering green. From what I can remember, blue's luminosity is something like 7% instead of green at around 70%.

The Note 2 has a blue pixel that is doubled the size of red and green, until we can measure how much current the blue pixel draws we will never know how efficient Samsung has made the blue pixel to be.

Well, I guess not a lot of users care about this.:laugh:

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

That would be way too much work for what it's worth then. I don't see anyone complaining except for the 10-20% who simply like the Standard profile better.:)
[Galaxy S III Original Android Development] Obagleyfreer:
I am loving the new calibrated profile! Can't believe I put up with the colours the way were for so long.

The only thing is that on my screen the greens look like they are too unsaturated.

I work as a designer and all the Macs in the office are colour calibrated every fortnight using an i1 calibrator. The new profile on my S3 matches the screens pretty much bang on, except the saturation in the greens.

I have tried to use the chroma saturation slider and adjust the green channel but it doesn't seem to change anything........

Can someone please give me advise on how I can just boost the greens saturation while leaving everything else untouched.
[Galaxy S III Original Android Development] Slimer777:
Good eyes! But the most undersaturated green right now is only between 70-75% saturation. 85-100 is actually oversaturated! The under and over saturation of green comes from the inherited panel and driver charateristics that one can only do so much about it. You can try to incease the green saturation but then most of the points on the green will be oversaturated.

Normal calibration only calibrate 7 points on the colour gamut, I tried to even things out for 25 points plus luminance and gamma. You must know how many points are on that piece of pie, that is right 16 millions! And one of the best solution out there only do 17x17x17 on a 3D LUT level with interpolations.

As I said before, do not try to match 100% of any colour to another display device. They will not be exactly the same! The xrite software on Mac or any other is not that accurate either. The cheapest way to make a consumer level monitor close to broadcast level is to add a black box with 3D LUT control and buy some REAL professional calibration software. It's actually pretty cheap, I think you can get by with $3xxx.
[Galaxy S III Original Android Development] mamba720027:
Re: [Kernel][28/02] Perseus

Just to clarify if I understand correctly, so if we lower the green in white and raise the blue in white, you're saying that may yield a result in less power consumption correct?

Sent from my GT-I9300
[Galaxy S III Original Android Development] Obagleyfreer:
Thanks for the info and the speedy response!

I thought I was being a little picky, it is after all a phone. I think we forget that sometimes.

Although with the Perseus kernel and these calibrations it's really transformed.

Thanks for all your hard work on this, it's very much appreciated. I love my screen now.
[Galaxy S III Original Android Development] Slimer777:
NO, this is purely technical and if your intention is to save power then simply lower the brightness!

No one at this moment knows exactly how much it takes to power the green and blue OLEDs, but theoretically say you have a green OLED torch and a blue OLED torch and they give out the same luminosity then the blue torch SHOULD consume more power. Since we are only adjusting the white balance, I don't think the current consumption is going to be significant to a point where we will say that we can save power!
[Galaxy S III Original Android Development] Infy_AsiX:
Re: [Kernel][28/02] Perseus

is ntfs working for anyone? It used to before it was added to the kernel using paragon app. I've only tried again but on a different hard drive since then and a notification says storage damaged please reformat. Is it just this hard drive or the new kernel ntfs?

?????? Galaxy S3 ??????
[Galaxy S III Original Android Development] MBurns2:
guys i'm changing color temperature but nothing happens,why ? ( i have activated toggle colour temperature control). Thanks a lot
[Galaxy S III Original Android Development] AndreiLux:
Re: [Kernel][28/02] Perseus

The register hook also needs to be enabled for the controls to do anything.
[Galaxy S III Original Android Development] Drizzy xS:
Re: [Kernel][28/02] Perseus

Andrei, just wondering is it possible to enable the master sequence on a Aosp rom to get the calibrated colours, like are there any files you can edit? I don't mind how complicated it is I just can't stand cyanogen mod colours.

Cheers
[Galaxy S III Original Android Development] habylab:
Re: [Kernel][28/02] Perseus

How could 3.4 Linux kernel be ported to i9000b but not the s3?!

No way unless he does a version for CM, which I'm not sure will happen.
[Galaxy S III Original Android Development] Erahgon:
Re: [Kernel][28/02] Perseus

I guess the issue is, if I remember correctly, that Samsung doesn't give change logs nor explain in detail the commits to the kernel. Hence, it is much simpler (in a work-benefit ratio sorta sense) to stay in and around the Samsung kernel base, than to migrate to a different one. This is what I have understood from past explanations.

I would be interested to hear what benefits a 3.4 kernel would have.

Hope the next version of android does more to bridge the gap between Linux and Android kernels!

@Andrei: would love to have an AOSP kernel! Any plans to convert the color control into an app and kernel patch which could then be applied to other setups as well?
[Galaxy S III Original Android Development] AndroidGX:
Hey Andrei,

I don't know if you are aware if this, but it looks like the new sharpness (aka digital edge enhancement) is acting weird here : when I activate the toggle for user interface for example, sharpness is way too much (with every stock values of course : 0 everywhere), and when I try to untoggle factory settings : its looks a bit better but always far from stock value.

So I guess somethings wrong with 0 values.

I tried to move and test many various values but can't reach stock ones.

Did you saw this already ?

Many thanks for your future answer when you can :good:
[Galaxy S III Original Android Development] habylab:
Re: [Kernel][28/02] Perseus

Well Perka looked into the update 8 and found they actually updated to .32 instead of the listed .31. Basically, no change. They could of cherry picked, or done nothing.

I'd like to see it updated personally as there are changes that are already done and need to be implemented. Yank integrates it easy because his is so close to stock kernel.
[Galaxy S III Original Android Development] AndreiLux:
Re: [Kernel][28/02] Perseus

Probably because some dev invested his time in it. I wanted to start doing it too and actually moved block to 3.3 but it broke exFat.

Basically. For example right now we'll have some apparent "big" update for 4.2.2 so whatever the changes might be I'll integrate them faster.

I guess you could do an app. You can recompile the Galactic Night app with the calibrated values. Or you can grow a beard and wait for Supercurio.

3.4 and up are interesting because there are some major core changes in the scheduler and power management. It means much lower latency delays in hot-plugging and the ability to use per-entity load tracking which a dev could use to write much smarter governors.

I'm also not doing CM right now because of the mess in the Mali drivers. I'm maintaining the kernel for 9 variants and the reason is plain and simple that I'm to lazy to bother with all those shenanigans and maintaining all of that. I also don't want a separate kernel but an all-in-one. Maybe after 4.2.2.

The current "stock settings" are the Note 2's which had less "Amount" in it. I leave the sharpening off for the interface because it looks horrible, whatever settings you set (unless you really turn it down). Anyway, the controls are there, adjust it how you want it.

Uhm. I don't remember any such thing in Update8.
[Galaxy S III Original Android Development] :
I guess the only thing you need to compare between i9000 and i9300 is the launch date and plataform. Reminding that i9000 was basically a Nexus One... in the i9300 if you change the kernel's name it will break camera, audio, data, wifi, ... (that's not true, but you got it...) At this point, i9100 people are suffering with the plataform, also by the lack of updates since the launch of the i9300. i9000 people are satisfied, using their 4.2.2 freely, updated kernel and stuff. I guess my next device will be (almost) for sure the new Nexus, or even the Nexus 4. I support the idea of Andrei buying a Nexus to develop for it, would be better for him, and better for the community of maybe all other devices.
[Galaxy S III Original Android Development] AndreiLux:
Why? First of all the Nexus devices are boring for me. I'm a hardware enthusiast and Exynos and AMOLED is what excites me the most, if the S4 comes with the Octa + AMOLED it's a guaranteed buy for me.

Secondly, it doesn't really stop anybody. The reason we don't have a 3.8 kernel right now is simply that we nobody is willing to spend the time on it. Bringing /block up to 3.3 myself is as far as I know the first and only attempt to upstream something on Exynos. It's not like it cannot be done, there's enough resources out there in form of the Linaro and Insignal kernels, just somebody needs to invest the time in it instead of just pulling readily available patches. It's just a matter of return-on-investment where the investment is personal time here, and I just don't find it worth it.