yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] Tatsuya79:
Lol I can sympathize with that!

I'm going from "Wow that's great!" to "Damn that's so wrong in fact..." and then going back to my old solution with another app and "wait... that's a lot worse.". :silly:

Just spent hours configuring every single color, displaying the same one on my amoled screen and on a PVA screen. (adding a bit of blue in the red, fighting a lot with the magenta...)

Finally getting close to perfection. Still have to fix something with plain blue/cyan.
[Galaxy S III Original Android Development] tolis626:
Thanks for your reply man.I hope you didn't get me wrong.I can't stress how much I appreciate your work.I just don't appreciate AMOLED displays that much nowadays.I used to love them for being so saturated.Turns out that with age comes wisdom. :p

Well,I am comparing the S3 with my HDTV (Which I also use as my monitor).It's a Philips 40PFL5507 which I calibrated somewhat myself and I am very satisfied with the result.Sadly,there is no comparison.I don't own any Apple devices,so it's the best I've got right now.There may be something wrong with my S3's display in particular though.To compare,I just tick "Enable register hook" and "Enable master sequence" and use some images.The ones that dissapointed me most are attached.One is the reason I think my blue sucks completely.I also tested by changing stuff myself.However the results still didn't impess me.Maybe I'm doing something wrong...
[Galaxy S III Original Android Development] AndreiLux:
Edit manually/remove the entries in the default and init .profile files in /data/.perseus/ . They got messed up a few versions ago and you probably still have some trash in those files. I can't fix this without wiping your profiles remotely. It works correctly once it's clean.

The DNA hexagon looks exactly the same on my phone with the calibrated profile as my computer screen which is also using a calibrated profile. Other than the back-light of my monitor getting old, the colours are the same. Did you consider that your HDTV is wrong? Calibrating yourself is ... well not advised, you'll never get it correct just by yourself.
[Galaxy S III Original Android Development] dezeubby:
Re: [Kernel][27/02] Perseus

I think that Andreilux make this kernel worst with this calibration.
[Galaxy S III Original Android Development] MuertoKo:
Re: [Kernel][27/02] Perseus

I tried to search on thread not to feel stupid now, but no solution so... Here it goes, o can't find anything in data/ folder related to Perseus. Not in internal, external, system data/ folder.

Something I missed?

Edit : never used any profiles myself btw, always tweak everything manually from scratch..

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] tolis626:
I don't think it's that far off,but maybe I'm wrong.Does it look vibrant blue or does it have a slight green/cyan tint to it?
[Galaxy S III Original Android Development] habylab:
Re: [Kernel][27/02] Perseus

So what about the factory settings toggles? Enabling them override the corresponding toggles? No? Yes?

Sorry, I'm out of my depth with this.
[Galaxy S III Original Android Development] Anakha56:
Not helpful... :/ You do realize that you can take the calibration off and use the Samsung profiles? Or you could calibrate it on your own? My personal experience is that this calibrated profile is awesome, took me awhile to get used to it but now that I am used to I am really liking the calibrated colours.
[Galaxy S III Original Android Development] Obagleyfreer:
Hi AndreiLux,

Thank you for such an awesome kernel!!

To apply the correct calibrated profile do we simply just tick 'enable master sequence' in STweaks?

Or is there more we must do?
[Galaxy S III Original Android Development] AndreiLux:
They override the value controls for that corresponding effect and the controls are ignored.

Yes..

Getting a bit annoyed with people not reading the change-log and descriptions, so I'll ignore any further benign questions.
[Galaxy S III Original Android Development] Tatsuya79:
Finished my calibration and I know what you mean.

I can't get the blue as deep as it is on my monitor, it stays slightly lighter.

Probably a problem of my amoled screen: it's yellow tinted without mods, guess the blue leds are a bit weak.

Can't push the "blue in blue" farther or reduce the "green in blue" to correct that, they're on max/min.
[Galaxy S III Original Android Development] Infy_AsiX:
Re: [Kernel][27/02] Perseus

Just noticed that when using the colour adjustments, Samsung's negative colours widget doesn't work. Any way to keep it compatible? As it's very useful for saving power and increasing visibility on all white backgrounds. I'm loving my calibrated colours but inverting is a must at times.

?????? Galaxy S3 ??????
[Galaxy S III Original Android Development] AndreiLux:
I don't keep track of the negative scenario, I'll make a change in a coming minor revision.
[Galaxy S III Original Android Development] sorg:
"Toggle SCR" switch logic is inverted?

I've spent a lot of time trying to adjust RGB values but it didn't work. Finally i un-tick Toggle SCR and my adjustments have been applied.

I've though marked "Toggle SCR" enables all controls below it. But it's opposite.. Weird..
[Galaxy S III Original Android Development] mamba720027:
Re: [Kernel][27/02] Perseus

The calibrated colors looks great I must say. Actually better than I expected. I'm glad I don't have to touch those color controls anymore lol.Those Samsung screen profiles looks horribly oversaturated when compare with the calibrated profile and chart Andrei posted.

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

If you toggle master profile on then reset stweaks to default the master keeps on although not checked. You need to turn it on, apply and unselect it and apply to have it off.

Perhaps the reset is fine if you reboot the phone.
[Galaxy S III Original Android Development] Slimer777:
Are you sure the profile has kicked in? Why do you say it's not as good as iPad 4? I can be sure that the current profile surpasses all i-devices and on par with iPhone 5 and iPad 4 that is unless our phones have very very different panels. The guys on the Note II thread took a couple days to realize that. Just remember that iPhone 5 has a blue tint to its greyscale which cannot be used as a reference.

Calibration should NOT be done with maximum brightness. The Note II profile was done in 105 nits and the SGS3 profile was done in 14x nits.

---------- Post added at 06:52 AM ---------- Previous post was at 06:48 AM ----------

Loss of brightness is a good question which Andrei already answered. Over 90% of display lose as much as 40-50% of brightness when calibrated correctly. Therefore, when a manufacturer says their display has a brightness of 300 nits, don't believe it. It will burn you eyes with anything over 160 nits.

---------- Post added at 06:57 AM ---------- Previous post was at 06:52 AM ----------

How was your PVA screen calibrated?

The calibration was done with a purpose to counter the non-linearity of different saturations that is inherited in the panel.

Whe you add red in blue, you are lowering saturation of red and at 25-75% saturation you will be undersaturated.

The toughest part of this calibration was to resolve the non-linearity inside the colour gamut.

But as long as you like it, that's what important.

---------- Post added at 07:09 AM ---------- Previous post was at 06:57 AM ----------

Why would you want to meet the blue on your monitor? When you say blue is lighter, what % of saturation are you referring to?

If you think we have low saturation in blue, wait to you compare it to iPhone 4 and iPad2, that's low. They are not even capable to produce the correct saturation of blue.

Having a yellow tint is normal with Samsung's profile. This is much corrected with the new profile. Increasing blue in blue is not giving you more saturation in blue, you are simply throwing blue illuminace out of wack. My calibration already even out the blue luminosity between 0-100% saturation.

Many users are trying to fiddle with the parameters without a spectro, don't do it.

What I would recommend you guys is that if you really like over saturated colors, add two ticks to all color gains and that's it. Don't mess with the Primaries and Secondaries!

As for white, we are already a tad on the cool side! even if we have different panels you are either spot on or on the cool side. You simply can't have reddish white with the current profile.
[Galaxy S III Original Android Development] j0sefuz:
this kernel has good features.

too bad it made my fone slow. :(

and my crt off broken. :(
[Galaxy S III Original Android Development] AndreiLux:
You can just increase the global saturation weight slider and don't mess with the single channels, at least that's what I recommend.
[Galaxy S III Original Android Development] rezapatel:
Re: [Kernel][27/02] Perseus

I finally verified and this is what happens, you may want to test it out.

Hook + Samsung Normal Profile results in the same results as Hook + Master.

Hook + Samsung Dynamic profile results in washed out colors.

Can't give any technical explanation for the above, but I am sure it's happening.

Thanks
[Galaxy S III Original Android Development] AndreiLux:
This does not happen. Unless you messed around with the toggles in the rest of the controls, which you probably did, this is simply not the case. The hook has absolutely no effect on any of the profiles if you leave the controls in their default state (Everything ticked off, everything to 0).
[Galaxy S III Original Android Development] Slimer777:
I am sorry if I confused you, I mean exactly what Andrei said above.
[Galaxy S III Original Android Development] ilos:
any changelog for rev 3 ? :D
[Galaxy S III Original Android Development] :
afaik fixed again 1080p video recording + init.d from rev 2.
[Galaxy S III Original Android Development] ilos:
thanks for the fast reply :)
[Galaxy S III Original Android Development] Chillz88:
Checked camera- burst shot , burst shot , hdr.. --- all working

Change to front camera..front camera shots--- working

Checked video 1080 p working, front video cam..--- working

Reaction when touching on a screen or swiping is instant .. just as instant as the gpu boost on siyah..

1080p videos and other hi def videos work in mx and dice.. but stock player cant play any..i know it wont.. just saying as i test:)

On checkrom v5 with the read ahead sd card init.d script....
[Galaxy S III Original Android Development] :
new leak LI2 has now 833 of free RAM :p LOL
[Galaxy S III Original Android Development] chx:
using 19.3 here. works flawlessly. the only thing I miss is voodoo sound.

fantastic work! thanks and keep it up.
[Galaxy S III Original Android Development] ahac85:
How did you get thT much screen time, im soo jealous lol, what do you mean by my update? Also any chance for a cwm zip for your undervolted values?
[Galaxy S III Original Android Development] AndreiLux:
This is a general question for the voodoo people, I already implemented Gökhan's port into the kernel, but obviously I don't have an app yet. There are ways actually to make the old Voodoo App work on the port, but that is left up to the end user as Supercurio doesn't want compatibility for us custom kernels.

I already gave up on SC to deliver any time soon after waiting a good part of the summer for it, but since we already have a high-enough quality port, that shouldn't pose a problem and as far as I'm concerned it's perfectly fine.

So an option is that I would actually implement STweaks over to the kernel, the only reason I haven't done this yet is because I still find it limiting in terms of interface and what you can do, and have my own ideas going on, but haven't started onto programming that yet.

Personally, I leave the sound pre-set defaults as they are, as they are good enough for me, but some people might not be happy with it. So my question is, do you really need an interface for it, or can you live with scripts (Or use the hack to get the Voodoo App) for several more weeks to a month or two, until I have an alternative?
[Galaxy S III Original Android Development] :
for me pre-set defaults are good enough also.
[Galaxy S III Original Android Development] garyd9:
Any interface would just be a layer on top of sysfs, wouldn't it? If so, is there a difference between an interface existing or just using scripts?

Perhaps it'd be better to phrase the question as: Are the two options mutually exclusive? Seems to me that both are hooks to /sys interfaces.

Take care

Gary
[Galaxy S III Original Android Development] JF-GINO:
Does Perseus alpha19.3 allow you to set the GPU clock/voltage?

I Can't get clock values & voltage to work:

#!/system/xbin/sh

echo "160 333 440 533" > /sys/class/misc/gpu_clock_control/gpu_control

#echo "160 333 440 533" > /sys/devices/virtual/misc/gpu_clock_control/gpu_control < Do Not Use

echo "875000 925000 975000 1075000" > /sys/class/misc/gpu_voltage_control/gpu_control

#echo "875000 925000 975000 1075000" > /sys/devices/virtual/misc/gpu_voltage_control/gpu_control < Do Not Use

What am I doing wrong?

I just need to change the values as I keep having reboots on some games.
[Galaxy S III Original Android Development] chx:
I didn't know that Gökhan's Voodoo port was already implemented in your kernel, that's great!

Off course I'd prefer a full flesh interface to change settings, but I'm OK using scripts for the time being.

The default presets sound a little low and flat for me.
[Galaxy S III Original Android Development] AndreiLux:
I mean I already implemented it into my own newest build, alpha20, of course it's not released yet for you guys yet. Sorry for the misunderstanding.

Yes, they are not exclusive at all, and they're pointing to the same thing. It doesn't matter which one you use.

There is a bug which we haven't tracked down yet which has weird behaviours on GPU voltages not being correctly updated, to be safe, use this version of the script:

#!/system/xbin/sh

echo "875000 925000 975000 1075000" > /sys/class/misc/gpu_voltage_control/gpu_control
#echo "875000 925000 975000 1075000" > /sys/devices/virtual/misc/gpu_voltage_control/gpu_control < Do Not Use

sleep 13

echo "160 333 440 533" > /sys/class/misc/gpu_clock_control/gpu_control
#echo "160 333 440 533" > /sys/devices/virtual/misc/gpu_clock_control/gpu_control < Do Not Use

The sleep 13 is just some random amount of time that works for sure. I also switched around voltage and frequency, because in our case, we're more interested in overclocking than underclocking, so you're more safe if you first raise the voltage, and later raise the frequency on already high voltage. This is merely to avoid any lock-ups on start-up if you use too high overclock and the default voltages can't satisfy the clock during the inter-setting period. We'll try to find the cause of this.
[Galaxy S III Original Android Development] JF-GINO:
Thank You! I will try that instead.

As for a tweaks front end, I would welcome any app that allows changes.

BTW, great to see such a well working Kernel even in Alpha stage. The extra ram is Boss! Keep up the good work!
[Galaxy S III Original Android Development] chx:
Yes, I thought so, but anyway that you have it already implemented and working in a private version is indeed good news. :good:
[Galaxy S III Original Android Development] evrest:
:laugh: Wow thats very good ! Until some thing comes i can live with scripts for voodoo sound...!!!
[Galaxy S III Original Android Development] eric-filth:
Both question are in my signature.

And i disable all. Led notifications, keys leds...

Enviado do meu GalaxyS3 far far away
[Galaxy S III Original Android Development] ahac85:
Yes they are, but i have no idea how to apply these lol any help us appreciated for a noob

what sort of screen time are you guyz getting on default values?
[Galaxy S III Original Android Development] chx:
six and a half hours on default uv/oc values, with stock LG8 ROM (only bloatware removed), fixed screen brightness at 50%
[Galaxy S III Original Android Development] eric-filth:
My script you apply using CWM (recovery)

And uv your CPU you can use setcpu and UV you GPU using scripts, Andreilux posted above.

Dont ask this things here because OP dont like this type of posts.

Enviado de uma GalaxyS3 far far away
[Galaxy S III Original Android Development] tonyjansen:
Re: [Kernel][27/02] Perseus

Roses are finally red

Violets are true blue

Oh Perseus on Amoled

I love you

(Thanks Andrei)
[Galaxy S III Original Android Development] davibs:
R: [Kernel][27/02] Perseus

There is a Version of this, for cyano?
[Galaxy S III Original Android Development] dezeubby:
Re: [Kernel][27/02] Perseus

How can i make that calibration???
[Galaxy S III Original Android Development] tsubus:
Re: [Kernel][27/02] Perseus

So to use the calibrated profile all I have to do is check the master toggle, correct?
[Galaxy S III Original Android Development] .c0dy:
Pls nobody answer this -.-

Guys. Would you just read the op? And at least the last 3 pages?

Why the f**k is everyone so damn lazy. It gets kinda annoying.

Best developer! Thank you andrei!!
[Galaxy S III Original Android Development] rezapatel:
Re: [Kernel][27/02] Perseus

Really, no other change at all. Don't think this could have impacted but my active profile was Normal when I updated the kernel.

Regardless, I believe I am seeing the colors that you and the other person who worked on the color profiling intended for us users to experience. I have to give hats off, I am loving my phone again.. Thanks!
[Galaxy S III Original Android Development] habylab:
Re: [Kernel][27/02] Perseus

Register hook with Master sequence + CS and SCR looks very vivid to me. Does the register hook make colours uncalibrated?

And CS and SCR are default on Master sequence apparently, yet they make differences when turning them on.
[Galaxy S III Original Android Development] Kemby13:
I see that there is noticeable difference in color representation, but only if i had Dynamic or Standard mode applied. When on Natural it seems to change very little to none at all. Just making an observation, is it possible that Samsung had Natural mode more realistically calibrated and less vivid in colors? I myself like the live and vivid colors even though they are oversaturated as some would say. But i also like all the other options in your kernel :)
[Galaxy S III Original Android Development] Tatsuya79:
My PVA is calibrated by default, it's one of those which aren't too bad (it's this one).

I'm not telling your calibration is bad! I have the feeling some screens are different.

Mine stays really yellowish after I select the master profile. Even if I adjust the white color balance, the red is a bit orange, green still shows itself too much in blue and dark greys.

But anyway, I'm mimicking the blue because I like my monitor rendering!

I'm working on this picture, at 0 saturation weight. (then I use +4 when I'm finished)

I don't like warm calibration, I'd rather go 6500K and slightly above. Tastes can be different here.
[Galaxy S III Original Android Development] Frag1le:
Damn AndreiLux and Slimer777 you guys have been busy.

Just installed 33.2 and i have to say:

Ouch, that calibrated profile makes me realize i'm already to used to the over-saturation of the standard screen mode.

Everything has a grey look to it with only the 'master sequence' on, so much grey that pictures i made with the green camera filter won't show any green anymore and are almost all grey. (even with 100% brightness)

I guess the calibrated default profile doesn't work for my SGS3.

Back to work, will play with the screen settings later :)
[Galaxy S III Original Android Development] i9100g user:
Re: [Kernel][27/02] Perseus

Delete
[Galaxy S III Original Android Development] Steve_max:
What is the color temperature in the master profile? Compared to my Sun IPS displays (calibrated weekly by the same team, because a slightly innacurate colour rendering here could mean a loss of quite a few million dollars to the company), there is a clear purple tint. If I set the color temperature to "0 00K" (which means 6500 K) I get much more accurate rendering.

What I believe is the problem here is that not every screen is exactly the same. For example, temperature affects the OLEDs' output, and that would give someone living in 40°C-in-the-shade Amazon very different effects than for people living in -10°C-it's-so-hot-today Siberia. There are other factors, even the build date for the screen will give you some differences. This is why the master profile should NOT work 100% well for everybody, and why we should mess with some settings to make them work. In my case, going to 6500 K colour temperature seemed to make the rendering much better (still some greenish tint on the grays, though).
[Galaxy S III Original Android Development] nfsmw_gr:
I'm not sure about the temprature (not color temprature) but when i compared my uncalibrated S3 to her's uncalibrated S3 both on older same version perseus her whites were better,mine were a bit to the yelowish...:/

Maybe it was because i had it 3-4 months before she got herselft the S3?

I don't know...right now when i compared them again using the calibrated profile and -15 on the white color temp,mine wins hands down(even though she doesn't admit it..:p )
[Galaxy S III Original Android Development] Slimer777:
Natural is under saturated and with a non linear lowered gamma. Try ours for at least two days, then report back.

---------- Post added at 06:34 PM ---------- Previous post was at 06:27 PM ----------

Yes, I am 'the other guy'

If you have a Pinkish screen, go to White Color Balance. Adjust Red in White gradually until you don't see the red tint. Remember, adjust, look at some white paper, adjust, and keep going just so your eyes don't get trained to the current level of red. DON'T adjust Green, I am not going to go into this yet, just don't do it.

Now, use the phone for a couple hours, I don't care what the white point has changed into, all I care is that the red tint has to be gone. You may now have a different tint of color, that's okay as it's not over yet. At this point, you should be thinking..."it's just not white enough...." now, adjust the Blue in White slider until you THINK you get a white that you like and at this point, you should have no color tints on white. At least to your own eyes.

Again, use your phone for a couple hours, games, internet or whatever. If you still think that it is 'washed out', by all means adjust 'Chroma Saturation Weight' by whatever clicks that serve you. DONE.

All that you need to report back is how many clicks of red and blue that you have adjusted and we can continue the experiment.

---------- Post added at 06:36 PM ---------- Previous post was at 06:34 PM ----------

It is supposed to be at 0000k isn't it? Yes, that would mean 6500k.
[Galaxy S III Original Android Development] tolis626:
At what percentage of brightness approximately do you suggest we do this?
[Galaxy S III Original Android Development] Slimer777:
I believe that you see a yellowish tint on white, decreasing the green in white balance until you see a red tint then raise it up until the red tint disappear. Now raise the blue tint to make it white for you. Done.

You should not use your monitor as a reference unless you just like it because it's standard calibration is off standard. You have over saturated red and blue, under saturated green. Your phone can cover all blues of your monitor but they will still look different because of luminosity and saturations on different stimulus.

---------- Post added at 07:05 PM ---------- Previous post was at 07:02 PM ----------

The calibration for the Note II was done in 105nits. Samsung's standard brightness is around 100 nits. Say the brightness bar is 100% and standard is at 50%, just do it between 50 and 70