yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
That's what I noticed myself, it's not very optimal. If you can shift up the whole gamma range (that's what you mean?) using this, then that'd be great.

There's two mechanisms independently at play here, I didn't figure out the controller one yet.

The automatic gamma is a problem not only in auto brightness, it changes also on manual and based on APL which can be annoying.

You take a minute to think about what you just said...
[Galaxy S 4 i9500 Original Android Development] Slimer777:
Yes, just tried APL pattern to measure gamma and although it shifts the gamma curve, it does it very linearly. Samsung obviously used full field patterns out of the factory so I will stick to their method and pull the whole curve downward to 2.22 only. This is done.

I am moving on to the color gamut next.

Is there a two points greyscale parameter or even 10 points on the S4?
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
Same story as on the S3/N2. There is, but we can't realistically edit it.
[Galaxy S 4 i9500 Original Android Development] SaNTi285:
So I'm trying to understand.. the occasionally reboots happens in MEA only if i play with settings or when it's untouched at any parameter?
[Galaxy S 4 i9500 Original Android Development] bala_gamer:
2ghz will never be stable and wont be useful too, so regardless of the log you produce(if in case you get it successfully;)) no one is going to check it
[Galaxy S 4 i9500 Original Android Development] Slimer777:
Andrei,

I need the RAW format instead of the clamped down version. Some part of the color gamut needs to be expanded. Color saturation (main) does not work. I would rather start out from scratch because I used part of the non-linearity of particular colors to calibrate the S3 master profile.

You can sent it to me by PM.
[Galaxy S 4 i9500 Original Android Development] jlevy73:
If you are having reboots you need to post a log to help the OP troubleshoot the problem.

adb shell cat /proc/last_kmsg > kmsg.txt
[Galaxy S 4 i9500 Original Android Development] 3c:
sysfs interface - Kernel support

Hello AndreiLux, thanks for your kernel, I'm testing it right now, so far so good.

Got a couple of questions about sysfs interface for you as I'm adding support in my app for your kernel:

- What is the sysfs interface to configure the colors? Is it similar to gamma-controls in Nexus 4 device?

- Is there a way to check the 8 cores configuration, in the default /cpu location I could only find the 4 big CPU cores?

You also mentioned you added multi-core aware scheduling, what does that means? Does it allow all 8 cores to run simultaneously?

You mentioned the voltage table ranging 100-600Mhz is for the A7 cores, corresponding to 200-1.2GHz range, then 800Mhz-2Ghz is for the A15 cores. Does that means the A7 vs A15 cores are selected based on frequency, eg @ 600Mhz, the A7 is on, above that the A15 takes over? So in a way, it's like having only 4 cores at all times, running on different CPU depending on frequencies? Do I get that one right?

How would you recommend I identify this voltage table interface by the way? So that I don't have to rely on the phone model number?

Thanks,
[Galaxy S 4 i9500 Original Android Development] suadt:
+1 :(
[Galaxy S 4 i9500 Original Android Development] mw86:
Quadrant is benching for me at 1.9ghz. The 16k quadrant i posted was at 1.9ghz. I can set 2ghz sometimes on mine and is stable under light load but falters with anything real load at all. But for me 1.9ghz is working. Its not stable as 1.7ghz which is likely the best area for many of us. Personally ive dropped 1.9ghz to 12,375mv from 12,500. For higher heat resistance under load as Stweaks has a note we would need more volt as temps rise. Its interesting how the exynos starts 75mv down on a given frequency and adds it back as heat rises.

Alpha0.1 i posted in the bench thread 31k plus antutu but antutu is useless to run now for comparison as its only 1.4ghz if that specific app is run not related to heat. 1.4ghz gets almost 12k cpu if ran optimil through test but stock potential i was getting almost 13k cpu subscore in antutu.

These are what I've found so far. The - 75mv for the most part has not been too bad but under stress i may settle closer to 50-62.5mv undervolt.

Been running 1.9ghz for daily since the other day OC was added. I can go through phone on the 2ghz max but any real load peak crashes it after awhile.

Users could note stock throttle is better for stability then adding back boost mode which the high temps could actually destabilize a mhz when it was stable at the 90c throttle.

---------- Post added at 12:21 PM ---------- Previous post was at 12:16 PM ----------

Let Andrei Lux's amazing write up educate ypu on the whole chip. Yes it is only a quad core active at one give time.

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

Besides that let Andrei reply as you asked. Just figured if you haven't seen it, it is a good read. Your app btw is excellent tool.

Edited:fixed some typos
[Galaxy S 4 i9500 Original Android Development] 3c:
Thanks, I was actually fully aware of the current software limitations and the so many misconceptions of the 8 cores. :D That said from the link I see a screenshot showing all 8 cores frequencies and online state, which I'm trying to show in my app too ;) Or whatever information there is to show about the 8 cores, if any.

I also found the hook_control directory under /sys, not sure how to map that to the gamma UI I made for the Nexus 4 if possible at all.
[Galaxy S 4 i9500 Original Android Development] jlevy73:
Untill Samsung releases source code for MEA, this kernel will not be compatible (well it is, just that it will break some things...so more accurately it's semi-compatible).
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
Colour control has nothing to do with the Nexus or anything else. It uses an Exynos-only (Except devices with mDNIe-Lite like the Qualcomm S4 one, but we'll see about that in the future) piece of hardware.

I attached an extract of the current interface here for the i9500. sequence_intercept is a boolean for the preset hook. hook_intercept is a boolean for the value hook. brightness_* are controls for the digital brightness reduciton in absolute values 0-255. (doesn't make sense to go that high).

In /hook_control you have the value hooks. All s_* entries are switches for different effects. All the other entries are configurables for the effects as delta values depending on the base given by either stock preset or master sequence, going negative or positive.

The current interface differs to the S3 and N2's in that I'm just outputting a plain value here instead of "delta x" on the older version. There's also some difference in effects. However the functionally overlapping ones for all devices are named the same.

No it doesn't mean 8 cores, it's something regarding the kernel scheduler, it does not concern you.

Voltages: yes, you're correct.

I made the voltage interface compliant with the de-facto standard UV_mV_table which has been around with many phones, there should be no additional work there. I don't see why you would want to identify it.

I'm using my own UV_uV_table for STweaks since it gives finer-grained values in µV, same principle as the UV_mV_table one just that I'm outputting values "<freqMHz> <µV>" for each new line.

I'm just statically multiplying the frequencies (on the app interface level) by 2 at under 700. If you really want to detect it, although I don't see a reason why, use /sys/devices/system/cpu/cpufreq/iks-cpufreq/ .
[Galaxy S 4 i9500 Original Android Development] skivnit:
I dunno if it's kernel related but battery readings are unstable. This morning I had a screen on time of 55 minutes it was at 87prct rebooted the screen on time was at 36min only and battery level at 89..just now screen on time was 3h40 after a reboot it's at 3h06. Wtf
[Galaxy S 4 i9500 Original Android Development] cmd512:
Not kernel related, blame the Samsung magic fairy dust.
[Galaxy S 4 i9500 Original Android Development] 3c:
Thanks, indeed nothing to do with anything I've seen on the Nexus. Probably a lot clearer too. But so many data to set! So far I've identified chroma saturation and the cs values. I have to identify each switch and its values, others don't seem to have the same initials.

It seems cc_channel_strength is a switch for the cs_* values, right? When I turn it on, UI becomes very white, however all cs_* values are set to 0. Anyway, I'm still playing with it to identify each switch/values.

Is there a way to identify which interface is available between the new (on i9500) and old (S3/N2)? I don't have a S3/N2 anymore. Will you update old interface to match the plain value too?

I'd like to identify the voltage interface so I can show the proper frequency (x2) below 700, or maybe split the frequency tables to show each CPU independently. But then when I looked at min CPU frequency, it's also 100, default to 250. Does that mean a real min frequency of 200, default to 500? Same is done for reported frequencies then?

By the way, Is the kernel resetting the min frequency at any times? I've set it to 100MHz, but after a while (or maybe only on reboot) it seems to go back to 250?
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
Uhm you have the device? Then go just read /data/.perseus/customconfig.xml for all the descriptions.

cc are for the gamma curve modifiers.
[Galaxy S 4 i9500 Original Android Development] mw86:
I dont want to get in way of your discussion. I can report setting min mhz with trickstermod to 100mhz or stweaks is sticking when i set it. I once set lock frequencies in trickstermod and forgot and couldn't get changes to stick till i turned that back off. Just some thoughts.
[Galaxy S 4 i9500 Original Android Development] hamdogg:
I can't get it above 1.4ghz

Have tried to set it at a minimum of 1.8ghz and after a few seconds it goes back down to 1.4ghz.

I monitor my frequency with CoolTool.

Temp. haven't gone above 80

Tried using setCPU and have changed it from ondemand to performance... last a few seconds the jumps down to 1.4ghz again.
[Galaxy S 4 i9500 Original Android Development] mw86:
Always have the on demand availability of frequencies below 1.4ghz maybe im wrong but once youve triggered throttle to 1.4ghz it needs to drop down to be abke to go back up. Why not set 1.3ghz min and 1.8ghz max on demand and test again. Use just stweaks for the min and max and clear data on the cpu apps so there's no conflicts??
[Galaxy S 4 i9500 Original Android Development] hamdogg:
It seems that Quadrant will push my frequency higher. Antutu wont go beyond 1.4ghz. (Its a benchmark problem for my device)

1.6Ghz - Quadrant :12421

1.7Ghz - Quadrant :13589

1.8Ghz - Quadrant: FAIL

Antutu : (wont stress higher than 1.4ghz)
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
Delete the TwDVFSApp.apk from /system/app, that's the culprit in this story. It was also setting a minimum frequency on Antutu even by having the app opened and zero load.

That being said, the thermal throttling does take its time to recover after entering a trip. Something to tweak in the future.

Edit: sorry I meant the app folder.
[Galaxy S 4 i9500 Original Android Development] hamdogg:
Was that directed at me?

I don't have any such file in my bin folder.
[Galaxy S 4 i9500 Original Android Development] gdonanthony:
BTW based on what i read ... the new firmware MEA + alpha2 make some things not working e.i Camera .. maybe new update is not compatible ..
[Galaxy S 4 i9500 Original Android Development] hsupi:
The TwDVFSApp.apk and TwDVFSApp.odex files are in the /system/app/.

you can found it in /system/app/.
[Galaxy S 4 i9500 Original Android Development] hamdogg:
yeah i did a search and found it... cheers.
[Galaxy S 4 i9500 Original Android Development] naeib2000:
said from what you read can you please quote your source? So for now it's probably smarter to ride with factory kernel until persus is updated?
[Galaxy S 4 i9500 Original Android Development] gdonanthony:
http://xdaforums.com/showpost.php?p=42453656&postcount=65

and read more of them next page
[Galaxy S 4 i9500 Original Android Development] StoneRoses:
After delete that app. I notice deeper and longer thermal throttle.
[Galaxy S 4 i9500 Original Android Development] Samer Diab:
I love this kernel because battery is ausome on it but on big bug over heat on charging on stand by.....
[Galaxy S 4 i9500 Original Android Development] sak500:
I did update and it broke the camera, also rooting using cofface method broke the camera. Only way to root is through chainfire's auto-cf. Also used philz recovery broke the camera so the new update is very incompatible with the current mods.
[Galaxy S 4 i9500 Original Android Development] Al Gore:
Hope you can make a camera fix asapish.

Stweaks gives me timeout as well.\

Tesla LED doesn't work either.
[Galaxy S 4 i9500 Original Android Development] devserg:
don't confirm! camera perfectly works with philz recovery & CF ;)
[Galaxy S 4 i9500 Original Android Development] hamdogg:
I don't find that at all. No overheating with me, and charging doesn't produce over 40 degrees.

(even wireless charging it doesn't get that hot... the screen just feels slightly hotter)

What are you using to check temps?

** charging wireless for the past 3 hours.. 93%.... 36 degrees ***
[Galaxy S 4 i9500 Original Android Development] Samer Diab:
How about 51* i pulled battery of and leted the phone rest ¿¡¿¡¿¡¿¡
[Galaxy S 4 i9500 Original Android Development] Al Gore:
Tried Antutu, got a very poor score (6k lower than before) but what's weird it said it ran at 2 Ghz - https://www.dropbox.com/sc/mzvex0ml8rrlj9a/xQchMWTamU

I haven't touched STweaks.
[Galaxy S 4 i9500 Original Android Development] matheus_sc:
You madeira something wrong, i test kernel in me1 and now I'm using in mea wanam and None bugs
[Galaxy S 4 i9500 Original Android Development] Al Gore:
ME1 isn't the latest. I9500XXUBMEA is.
[Galaxy S 4 i9500 Original Android Development] jaidev.s:
I flashed it over bmea , but it gave camera error:(
[Galaxy S 4 i9500 Original Android Development] jlevy73:
Try camera and smart scroll. Do those work?
[Galaxy S 4 i9500 Original Android Development] bala_gamer:
its not weird its just showing the maximum possible clock
[Galaxy S 4 i9500 Original Android Development] gun@id:
Smart stay

Smart stay not working.just installed wanam ema + stock and smartstay works,then flash perseus 2, smart stay do not work.do anybody have this too?
[Galaxy S 4 i9500 Original Android Development] jlevy73:
We need new kernel sources. Until then it won't work.
[Galaxy S 4 i9500 Original Android Development] matheus_sc:
Yes in mea Dont work, samsung need realese a kernel source
[Galaxy S 4 i9500 Original Android Development] djigane:
Flashed latest Perseus, coming from Adam kernel, nothing wrong. Battery better than before, no overheating at all, apps and system running smooth, no fc, no lags, until now.

Thanks
[Galaxy S 4 i9500 Original Android Development] gio_b:
hi,doe's bypass dac oversample rate for a 48 khz rate ? we prefer at integer multiples of 44.1 /88,2 176,4 course ,and 24 bit ,and play with it.

bat we have to wait for rom is it ? now stock?

tks gio.
[Galaxy S 4 i9500 Original Android Development] MrPhilo:
Finally get a stable undervolt (I think), no reboot so far.

I have undervolted -75mV for the A15 cores but I am able to undervolt -125mV for the A7's. The phone is soooo cool when just running the A7's even while they're all running max for ages.
[Galaxy S 4 i9500 Original Android Development] leoaudio13:
Very nice man. Tks for the info

Sent from my S4
[Galaxy S 4 i9500 Original Android Development] mw86:
Thank you so much!!!! I knew it wasn't thermal based on temps i was at. I stupidly thought it was part of the changes you needed to make for thermal. Thank you for making everything as it is as I have grown to love the entire setup. Keep up the great work Andrei latest build running strong.
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
Don't misunderstand, the limiting IS caused by thermal, but just that app causes it to behave funky. Monitoring temps with Cool tool is not enough because the polling rate is much higher than that app's display rate.

The 1400MHz limit is triggered by thermal, but it sticks there because the app is screwing with the minimum CPU QoS by setting it higher than the throttling.

Just check the kernel log, the thermal driver likes to spam things.
[Galaxy S 4 i9500 Original Android Development] sorg:
All smart features are working fine in MEA + Perseus.

I've checked all of them.

The only thing you need to do is to replace camera firmware in /system/vendor/ folder to one from XXUAME1 (or XXUAMDK) firmware.
[Galaxy S 4 i9500 Original Android Development] cmd512:
Curious if that will still cause those awful camera crashes that seem to be fixed on MEA as you're effectively rolling back to an older camera F/W. Stock MEA kernel is running well, so I'm going to wait for the next Perseus drop based on updated sources.
[Galaxy S 4 i9500 Original Android Development] StoneRoses:
If I understand correctly the purpose of TwDVFSApp.apk and thermal boost mode is to cheat the benchmark score.

So when AndreiLux disable boost mode the CPU will get throttle a lot during CPU benchmark and when TwDVFSApp.apk running it will lock the clock at 1,400MHz during benchmark.

If we uninstall TwDVFSApp.apk, the CPU will throttle freely to a much lower clock speed.

I think default throttle is too conservative. it drop the clock down to 600MHz and stay there too long, the temp never exceed 80C while in "cheat mode" the clock will be set at 1,400MHz (by TwDVFSApp.apk) and sometime go up to 1,600MHz (thermal boost mode allow this to happen) and CPU temp is around 100C the whole time (too aggressive IMHO)

I'm sure that AndreiLux will find the right balance between performance / battery life and risk of thermal damage in the future release.
[Galaxy S 4 i9500 Original Android Development] GSeeker:
Just replace the /system/vendor/firmware/ folder? Or the whole /system/vendor/ folder?

Thanks bro! This is so smart.:good:
[Galaxy S 4 i9500 Original Android Development] cmd512:
Nooooooooooo, just the camera F/W, should be two *.bin files.
[Galaxy S 4 i9500 Original Android Development] Jimmy34742:
Are the file names "fimc_is_gumi_fw2.bin" and "fimc_is_sec_fw2.bin"?
[Galaxy S 4 i9500 Original Android Development] cmd512:
Yep, those are the ones. If you copy over the ME1 versions, will allow you to use Perseus on MEA.
[Galaxy S 4 i9500 Original Android Development] bean12147:
Can someone upload the camera files?
[Galaxy S 4 i9500 Original Android Development] Al Gore:
MDK doesn't work (better than MEA but still crashes CONSTANTLY, you'll be lucky to take one or two pics). Where can I dl AME1 camera firmware?
[Galaxy S 4 i9500 Original Android Development] raiprashant007:
Can you post the camera firmware files here which needs to be replaced...I love this kernel.
[Galaxy S 4 i9500 Original Android Development] Jimmy34742:
I've attached a rar of the two camera files. It's all working fine for me, camera included (Wanam 3 + Perseus 2 + 2 rolled back camera files).
[Galaxy S 4 i9500 Original Android Development] Al Gore:
Better, but still crashed for me when I switched the camera. Thanks anyway.
[Galaxy S 4 i9500 Original Android Development] raiprashant007:
Worked fantastically for me!! Thanks...no crash...super smooth
[Galaxy S 4 i9500 Original Android Development] :
Can't wait till you release this or someone ports it to the i9500
[Galaxy S 4 i9500 Original Android Development] GSeeker:
It works fine for me! Thanks bro~

XXUBMEA stock firmware + Perseus Alpha 2:highfive:

---------- Post added at 08:49 PM ---------- Previous post was at 08:48 PM ----------

I believe this kernel is exactly made for i9500.:laugh:
[Galaxy S 4 i9500 Original Android Development] :
Also to AndreiLux, the MEA base doesn't fix the smearing issues at all. Samsung thought they were smart and changed the background of the settings app to dark grey. The blacks and darks still smear otherwise. Also the drastic color shift when the keyboard tray is out and such in apps and on YouTube is almost gone in MEA so that might help with gamma control, I believe the biggest problem IS the mdnie which is most likely the cause of most of the black clipping, and the reason being when I flash cm 10.1 on the phone and adjust the screen settings and turn mdnie to bypass mode. The clipping is much less prominent. Just my 2 cents.
[Galaxy S 4 i9500 Original Android Development] diego9016:
So... Flash rom of my choice (XXUBMEA), flash Perseus.Alpha2 and after that, flash this .rar?

Thanks in advance.
[Galaxy S 4 i9500 Original Android Development] dazkyl:
Guys,when flashing this kernal , is it 'screen calibrated ready' or its still like stock screen settings ?
[Galaxy S 4 i9500 Original Android Development] bala_gamer:
You have to choose the screen calibration manually from stweaks
[Galaxy S 4 i9500 Original Android Development] dazkyl:
Fair enough. Can you share your STweaks settings please? Beacause im sure i will not get the best calibration possible if i mess them up without any one's help.

Thanks in advance.
[Galaxy S 4 i9500 Original Android Development] Jimmy34742:
Unrar, and then copy the two files to system/vendor/firmware/
[Galaxy S 4 i9500 Original Android Development] Slimer777:
If I were you, I will wait just a little bit more and wait for AndreiLux to release a minor revision of the current version. Which will include a more accurate master profile.

When you have finished flashing it, simply go to STweak, Screen, and tick 'Master Sequence'. Tell us what you think.;)
[Galaxy S 4 i9500 Original Android Development] dazkyl:
I will wait for sure :) Can i tick 'Master Sequence' with this current version 'Perseus 2' ?

Edit : i just ticket 'Master Sequence' and the display is now with less saturation . Mort like near blk and white. Is this good ?
[Galaxy S 4 i9500 Original Android Development] cmd512:
That sounds awesome!
[Galaxy S 4 i9500 Original Android Development] Slimer777:
Come on, B&W! All the N2 and S3 guys went through this process which makes me think that I should write a guide or something in the general section.

In your case, the 'master sequence' has definitely kicked in. Don't worry about the B&W, stay with it for as long as you can before flashing the updated kernel. Then tell us what you think.

This makes me think you were on Samsung's Standard color profile before this!:eek:

Get your eyeballs ready either by ticking the current 'master sequence' or with Samsung's Movie Profile.
[Galaxy S 4 i9500 Original Android Development] dazkyl:
I will stay with the setting then. And yes , before i was with the 'Dynamic' Samsung setting.
[Galaxy S 4 i9500 Original Android Development] Slimer777:
You were WAY out of the ballpark! Take a picture of yourself with the phone and look in the mirror for justification purpose.
[Galaxy S 4 i9500 Original Android Development] dazkyl:
I guess you're right. I always liked that little bit of saturation , but nothing can beat a natural screen just like i had on my old iPhone.
[Galaxy S 4 i9500 Original Android Development] Slimer777:
[MENTION=346281]Andrei[/MENTION],

Digital Edge Enhancement looks different than the N2 S3 versions. We used to have triggers to activate them and now only three parameters. I read the OP and think maybe they are already triggered with 'master sequence' but I just don't see display changes with the current parameters.

We now have a Threshold default at 88, is this how Samsung has it on the S4? N2 and S3 were on 16 I believe.

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

Don't worry, wait a little and yours will be iPhone like and then some.:good:

---------- Post added at 12:45 AM ---------- Previous post was at 12:18 AM ----------

People are going to have questions about the S4 display calibration, from previous experience, I think we should talk about things that are NOT beneficial to development in This Thread on the General section. ;)

Or if AndreiLux doesn't mind cluttering this thread.