Samsung Galaxy S3 - Perseus Kernel

[Schmiddi1008 203]

Hier der PerseusKernel für das Galaxy S3!

Hier geht´s zum Diskussionsthread

UPDATE

[Kernel][26/02] Perseus

Features / changelist:

Perseus alpha33 (26/02):

Revamped and hopefully final version of mDNIe controls:

The controls work now on two levels: First we have a master sequence that overrides any and all of Samsung's settings; currently this version is released without calibration, however in the next minor version it will be updated with proper professional screen calibration. See the Note 2 thread to see what to expect here too. The master sequence is calibrated to sRGB norms on a precision level equalling and even surpassing the iPad3/4.

The master sequence works as as the calibrated base; for people not wanting to bother further with any more controls, you simply enable this and you're done.

Second part is the register hook, it catches effect values and modifies them by applying delta values available as controls in STweaks and in /sys/class/misc/mdnie/hook_control/.

Leaving both these options will give you Samsung's default values, plus the black crush fix.

The register hook, while used on Samsung's profiles, is not capable to alter effects which are not integrated in that screen profile's value sequence, the "Movie" profile for example lacks some effects present in the "Dynamic" profile. The same is valid when having different scenarios, the "Camera" scenario will use different effects in its base than the "UI" scenario. To fully explore all possible effects, use the Master profile as it integrates all effect values known.

Each control has a master kill-switch which enables or disables the effect. This varies by profile and scenario, so you have control to only "toggle" the switch, whatever its state may be in.

Digital noise reduction - Reduces and flattens out grain. Advanced controls are found in the hook_control folder with the dnr_ prefix.

High dynamic range - A HDR effect which brings out details in dark and extremely bright scenes.

Digital edge enhancement - An edge enhancement effect. What we previously called "sharpening". Divided in controls for radius, amount and threshold. Read the Wikipedia page for more information. More advanced controls found in the sysfs under the de_ prefix.

For the above three effects, scenario consideration is taken into account. You can enable/disable them depending when you want it to be applied. Please be aware only the stock applications trigger the scenarios. I will try to enable at least the video scenario depending on when the hardware decoder is active in the future so that they are enabled also in third-party video players.

Chroma saturation control - Same as in previous version but with fixed labels.

Colour temperature control - By default this is disabled on all profiles, however, if your screen has a tint to it, this is the first control you should try to fix as it alters temperature on all channels.

The SCR controls are colour channel filters working on the Red, Green, Blue, Yellow, Cyan, Magenta, White, and Black channels.

Imagine the controls as manipulating the corners of the RGB cube:

By controlling the RGB coordinates of each corner/channel we can mould the cube into a different shape. At the same time the cube is projected onto a hexagon; the perimeter of the hexagon represents the colour hue, the radius of the hexagon from the middle represents chroma. We can use the chroma saturation controls to "push in" each corner of the cube, while moulding the corner's directions with the RGB controls. The RGB coordinates can be transformed into the HSL space space if needed, however I didn't include this function yet as I don't feel the need for it.

STweaks has controls for the RGBYCMW channels, the K (Black) channel I left out because it makes no sense in altering it, but can be found in the sysfs folder.

Several controls have a "factory setting" switch, this are the burned in-hardware values for some controls, they overwrite the controls themselves.

Additionally to the controls exposed to STweaks, there are several other effects and modifiers exposed in the sysfs interfaces. This also includes the gamma curve controls for levels 0-255 in steps of 16.

There are also some additional unidentified configurables which I wasn't able to properly give a name to or had no effects: Dithering, ABC (Seems to give a gamma brightness boost), SCC, UC, and MCM (Colour temperature) configurables whose exact effect isn't documented.

DOWNLOAD

Perseus-alpha33.1-i9300.tar

Perseus-alpha33.1-i9300-CWM.zip

Changelog alpha29

⇓ Download unter dem Changelog ⇓

Perseus alpha32 (29/01):

Charging control implemented. This is my own version.

• 
  Charging currents:
  
  • Charging currents are dictated by input and charging current limits. The input current is the current flowing into the device through the USB port at 5V. The charging current is the current delivered to the battery at usually 4.35V. The device can have a higher charging current than input current because of the voltage differential, usually a 15% discrepancy. You can also have much higher input currents than charging currents, this can be useful when you are using the device in situations like gaming and charging your battery at the same time, provided your charger actually can provide the power.
    
  • There are 3 USB charger type categories: DCP / Dedicated Charging Ports which also includes AC chargers, but also special USB plugs; SDP / Standard Downstream Ports which usually includes almost all data enabled USB ports, and CDP / Charging Downstream Ports which includes also data enabled USB ports but which are designed to provide more power, usually on newer laptops where the USB port has a lightning logo next to it. More info here. - Technical explanation here.
    

  Charging logic:

  • Stable margin removal option. The charger chip is capable of detecting unstable charging sources; it dynamically reduces the input current in 100mA steps until it detects a stable voltage input [We don't have the charger chip datasheet, so the technical explanation is a bit blurry here on how it decides that it's unstable]. It further reduces it by 100mA as a safety margin, you can disable this now.
    
  • Complete disabling of unstable power detection. This simply ignores unstable power sources and leaves the input current limit at its set up value. This will fix charging problems people have been reporting. However, please use it at your own risk, the S3 chargers which have had these symptoms clearly have some issue in their hardware so you might actually kill them with this option enabled as there is no protection from the phone's side anymore.
    
    The actual input current limit can be read out in /sys/devices/platform/samsung-battery/power_supply/battery/current_max, so you can see the real limit there, it's the closest thing we have to the actual charging current on stock values since there is no hardware to read out the live currents.
    

  Voltage control:

  • Hard voltage control: 4.20, 4.35V, and 4.40V charging voltages are available. This is included for anybody running on third-party batteries, whom most of them have a 3.7V battery chemistry as opposed to the 3.8V on the stock battery. These batteries should be charged at 4.2V instead of 4.35V.
    
  • Soft voltage control: As opposed to the hard voltage control which is the voltage which the charger chip provides to the battery while charging, the soft-voltage is the battery voltage itself. 3.7V batteries have a top-off voltage of 4.2V and 3.8V again 4.35V. The default limit on the stock battery is 4.30V before the charger logic stops and considers the battery as full. This is also merely provided for 3rd party batteries which should be charged at lower voltages. If you overcharge your battery beyond these what are safe considered voltages, such as raising the default 4.30 top-off voltage to the design 4.35V or even higher, you are running into the risk of damaging the battery or even causing it to melt-down. Use at your own discretion.
    

  [*]mDNIe sharpness and RGB/YCM chroma saturation control in STweaks:

  I started implementing sharpness control in STweaks and went a bit over-board instead of a simple checkbox; You now have controls over the mDNIe registers as a delta offset value compared to the stock register values. I'm applying the offset to all mDNIe profiles and scenarios which have the specific post-processing effect active in that specific scenario. Meaning, that you start with the default profile; Dynamic / Standard / Natural / Movie and have the delta offset applied on top of that.

  • Sharpness delta. This is what brought most of the quality difference in hardcore's original tweaks. You can now fine-tune it to your own taste, and also take into regard that it produces a different effect for each screen profile while having the same delta - the base values between the profiles are different.
    
  • DE control - I don't know what this actually does and I couldn't discern much difference between the values, but it used to be disabled in hardcore's tweaks.
    
  • Chroma saturation control: This is composed of 2 values for each RGB/YCM channel. See the Munsell color system for a visual representation of the values controlled here. The chroma curve control describes the curve weight based on chroma intensity, the chroma gain is the chromatic gain that is being applied on the respective channel. Chromatic saturation weight is again another multiplier for all channels combined. I have not managed to properly identify the chroma grey threshold and its effects.
    

  Basically this is like an RGB control on steroids, and enables you to tune your screen to your own liking and calibrate it as you wish. Please note that not all scenarios in the profiles have chroma saturation effects, the Movie profile for example has no effect applied to the UI so chromatic control has no effect on it.

  I also want to state that the above are my deductions and theories on the descriptions of these controls, I'm not familiar enough on colour theory to be able to confidently say that these descriptions are correct, and the controls are a work-in-progress for now. Experts are welcome to contribute here.

  [*]Front buffer early suspend delay option for those who have issues with the CRT animation.

  [*]Did some refactoring on the Mali drivers and fixed a bug which may have caused less capable undervolting than the stock implementation.

Download 32.1 - CWM (Klick)

Download 32.1 - Odin (Klick)

Known Problems:

no known problems

Thanks To:

gokhanmoral, netarchy and anybody

TL;DR: before flashing aside from known issues in the second post.

This isn't an AOSP kernel. I won't work with CM and AOSP derivatives.

Alpha >=22 for SAMSUNG JELLYBEAN ROMS ONLY.

bearbeitet February 27, 2013 von chris264

[RichtigerLurch 8]

edit: Handy hat gegeiertt

[Schmiddi1008 203]

Downloadlinks freigegeben.

Viel Spaß

[Subzero1612 113]

Den Kernel habe ich mir heute auch runtergeladen nach dem ich einige Probleme mit dem neusten Siyah hatte. Bin mal gespannt wie der mit Dragons Jelly Bean 4.0 harmoniert.

Im Moment habe ich den Phenomenal4.0Medium drauf. Diesen Kernel werde ich Morgen mal testen.

LG Subzero

[chris264 5.155]

Morgen Schmiddi,

Kannst du den Startpost bitte ein wenig kürzen weil der ist echt verdammt lang und vieles eh Fach Chinesisch

Danke für deine Mühe und Arbeit.

LG

[Schmiddi1008 203]

Moin chris,

habe den Thread gekürzt. Werde ab Sofort nur noch den aktuellen Changelog einfügen.

MfG Schmiddi1008

[chris264 5.155]

:thumbup::thumbup::thumbup:

Es reichen so ca 3Changelogs, sonst fühlen sich die User erschlagen. Zumindest bei solchen langen Texten vom Dev.

Danke für deine Antwort und Arbeit.

Lg

Gesendet mit Tapatalk Hd

[Subzero1612 113]

Hier mein Fazit für den Perseus Kernel in Verbindung mit Dragons Jelly Bean 4.0 .

Der Kernel macht echt ne gute Figur und läuft einwandfrei auf dem Custom Rom.

Auch HD Games und alles andere läuft gut.

Es kommt mir zwar so vor als ob der Phenomenal4.0 medium noch minimal flüssiger auf Dragons Jelly Bean lief. Dennoch kann ich sagen das es ein guter Kernel ist und auch für Dragons Jelly Bean gut geeignet.

LG Subzero:icon_bigg

[maddes1402 1.305]

Alpha 26 ist verfügbar und läuft sehr ansprechend auf meiner darauf getesteten ROM (Maddes Light V2.0).

Odin Version

CWM Version

[chris264 5.155]

Update

[Kernel][14/12] Perseus

Perseus alpha28.2

Perseus-alpha28.2-i9300.tar

Perseus.alpha28.2-i9300-CWM.zip

[Biuman 1]

Update

[Kernel][14/12] Perseus

Perseus alpha28.2

Perseus-alpha28.2-i9300.tar

Perseus.alpha28.2-i9300-CWM.zip

Alpha29 ist draußen. Hat den Security Fix für die aktuelle Lücke enthalten.

[chris264 5.155]

Kernel][18/12] Perseus

Features / changelist:

Perseus alpha29 (18/12):

I'm doing a quick release because of the security fix, not very feature rich.

Fixes the exynos-mem security hole. This is my own fix and will not break camera. https://forum.xda-developers.com/showpost.php?p=35541696&postcount=55

Updated Wifi drivers.

Added GPU utilization control to sysfs and STweaks.

Changed default GPU thresholds to more relaxed values (75/17)

Added block device read-ahead control to STweaks. Additionally set the default read-ahead for internal memory to 256kB and 1mB for SD cards.

Odin Version https://forum.xda-developers.com/attachment.php?attachmentid=1571800&d=1355786215

Cwm Version https://forum.xda-developers.com/attachment.php?attachmentid=1571804&d=1355786401

Lg

[Schmiddi1008 203]

Danke chris.

Wenn ich wieder Luft habe, aktualisiere ich all meine Threads auf den neusten Stand.

MfG Schmiddi1008

[chris264 5.155]

Kein Problem Schmiddi ist doch alles, man muss nur lesen

Lg

Gesendet mit meinem Android Smartphone

[chris264 5.155]

Update Perseus

29.1: - Reverted the Wifi drivers back and did some CMA adjustments to see if that fixes some random reboots of people.

Odin Version: https://forum.xda-developers.com/attachment.php?attachmentid=1576845&d=1355947426

Cwm Version: https://forum.xda-developers.com/attachment.php?attachmentid=1576849&d=1355947613

Lg

Gesendet von meinem A210 mit Tapatalk 2

[Schmiddi1008 203]

Startpost aktualisiert.

Viel Spaß

[chris264 5.155]

Update

[Kernel][24/12] Perseus

Features / changelist:

Perseus alpha29.2 (24/12):

Another minor (major) release due to security. Please update.

I screwed up something touchscreen related in v29 that disabled Flexrate requests, fixed now.

Changed Flexrate requests so that they don't scale down in their sub-samples anymore. This should improve fluidity.

DOWNLOAD

Perseus-alpha29.2-i9300.tar

Perseus.alpha29.2-i9300-CWM.zip

[Schmiddi1008 203]

Startpost aktualisiert.

Danke chris.

Also der Kernel gefällt mir immer besser. Habe nun eine Akkulaufzeit von 1T 2S 27M und habe noch 37% Restakku. - Bild im Anhang.

Folgende Einstellungen habe ich verändert in STweaks:

CPU HOTPLUG:

RUNQUEUE DEPTH FROM 3 CORES TO ONLINE: 275 thread depth

RUNQUEUE DEPTH FROM 4 CORE TO OFFLINE: 175 thread depth

CPU ONLINE BIAS UP THRESHOLD: 85%

CPU ONLINE BIAS DOWN THRESHOLD: 50%

Dies hat ein User im xda Forum gepostet.

Yea I notice it took long to go offline still after I ran some more videos to bring it back online,then I tried set "run quedepth from 3 cores to online" to 275 and "run quedepth from 4 cores to offline" to 175 and goes offline faster now. When the phone sleeps for a minute and I checked it also shows offline. Can try that with the above setting I mention just to see what's up. 


Edit: Forgot to mention I had "cpu online up bias threshold" as 85 and "cpu down bias threshold" 50.

Lg Schmiddi

[rsspeed 45]

Startpost aktualisiert.

Folgende Einstellungen habe ich verändert in STweaks:

CPU HOTPLUG:

RUNQUEUE DEPTH FROM 3 CORES TO ONLINE: 275 thread depth

RUNQUEUE DEPTH FROM 4 CORE TO OFFLINE: 175 thread depth

CPU ONLINE BIAS UP THRESHOLD: 85%

CPU ONLINE BIAS DOWN THRESHOLD: 50%

Dies hat ein User im xda Forum gepostet.

Das habe ich nun auch mal so übernommen und bin mal gespannt, ob ich einen Unterschied feststellen kann

[Schmiddi1008 203]

Habe noch mehr eingestellt. Werde die Einstellungen nachher noch posten. Mein CPU läuft auf 1,7Ghz bis jetzt sehr stabil und das undervolted:).

Eventuell kann ich ja einen Overclocking Thread aufmachen;) - In diesem kann dann jeder User seine Ergebnisse + Benchmarks posten und weitergeben.

MfG