[Kernel][23/04] Perseus alpha 36.1

[myreality]

Herzlich Willkommen beim Perseus Kernel!
Ich dachte mir das wäre ein toller Name bezüglich der ganzen Galaxy/Universe/Pegasus Themes.

Ich versuche diesen Kernel so gut wie möglich aktuell zu halten. Im Gegensatz zu anderen Kernels und Philosophien deren Entwickler,
bin ich der Meinung, dass es nicht besonders klug ist dem Benutzer (zu) viele Einstellungsmöglichkeiten zu geben.
Deshalb werdet ihr hier keine dutzend verschiedene Governors oder zich verschiedene Einstellungsmöglichkeiten finden.
Es gibt eine optimale, oder zumindest, annähernd optimale Einstellung, bei der unser Gerät performant arbeitet und aber auch Akku sparend ist.
Für den gewöhnlichen Benutzer wird dieser Kernel viel Nutzen in Akkulaufzeit, Display Verbesserungen,
Geschwindigkeit und Soundoptimierung bringen, ohne viele Einstellungen vorzunehmen.

Fortgeschrittene Benutzer sind natürlich willkommen die Scaling Mechanismen von PegasusQ zu modifizieren - Ich empfehle SetCPU 3-.
CPU undervolting ist kompatibel mit den meisten Undervolting Apps. Für alles andere empfehle ich scripts.

Keine Sorge wegen der Alpha Bezeichnung des Kernels, ich nenne ihn nur deshalb so, da "alpha" traditionell für Feature-Entwicklung steht,
"beta" wäre dann die Feature-Vollständigkeit, and Final würde ich den Kernel nennen, wenn ich die Entwicklung komplett einstelle.
Der Kernel ist sehr stabil und irgendwelche Bugs wurden in den Hotfix Versionen gefixt (alpha x.y)

Diesen Kernel gibt es außerdem auch für das I9305 (S3 LTE), N7100 (Note 2) und N7105 (Note 2 LTE).


Features / changelist:

Perseus alpha36 (22/04):

• Adaptive Body Bias control (ABB). (Experimental feature)
  
  Body biasing is taking advantage of transistor body effect for binning the chip depending on its quality. In fact, this is used on the latest Samsung SoCs both for reducing power consumption and validating bad chips by adjusting their electrical characteristics.
  
  The body bias is dictated by the voltage applied to the transistor gate (The usual voltages you're all used to) minus the voltage applied to the transistor body. The resulting bias can change the transistor's electrical characteristics in two possible ways:
  
  Before reading on: A transistor's voltage and operating frequency is defined/limited mostly on its threshold voltage. Wikipedia has a neat visual representation of this; voltage must raise to a certain point for the transistor to be able to switch and operate. This threshold voltage can be highly dependant on temperature, influenced by the body effect, and defined by the manufacturing process. What we're doing nowdays with undervolting is to get as near as possible to the upper bound of this threshold voltage.
  
  With that in mind:
  • Forward Body Bias
    
    A FBB is defined when the bias of the gate voltage minus body voltage is positive, meaning the gate voltage is higher than the body voltage. This has the effect of reducing the threshold voltage. By reducing it, you can achieve lower voltages, or be able to clock the transistor higher. However the side-effect of lowering the threshold voltage is that you are sacrificing power leakage, meaning that the lower the threshold voltage becomes, the higher leakage current in the transistor becomes. This leakage power rises exponentially with a linear lowering of the threshold voltage. This is what is called static transistor leakage.
  • Reverse Body Bias
    
    A RBB is defined when the bias of gate voltage minus body voltage is negative, meaning the gate voltage is lower than the body voltage. it has the direct opposite effect of FBB, it raises the threshold voltage thus you would need a higher gate voltage for switching, but however you also dramatically decrease static leakage.
  What happens is that you want to use RBB when idling, and a reduced RBB, or even FBB at very high clocks.
  
  Samsung currently uses this on top of voltage scaling to bin their chips. Here's an excerpt of the stock body biasing on the 4412 Prime chip (I'm using that one as an example as it has better adjusted ABB values over the Rev 1.1 chips).
  
  
  
  
  To find out your ASV group: You can read out your ASV group in /sys/devices/system/abb/abb_info now.
  
  I have rewritten the ABB scaling logic/driver for CPU, GPU, MIF and INT voltages.
  
  In the current implementation, since it would be insane to have paired-up gate-body voltages divides the frequency range in several slices; even Samsung uses only three voltage ranges on the DVFS scale. I divided the frequency ranges as follows:
  • CPU: Divided into four slices, with frequency ranges of 200], 800], 1600] and [1600 Mhz.
  • GPU: Three slices: 160], 533] and [533 Mhz.
  • MIF and INT: Both only two slices with the bottom frequencies for each as middle-threshold.
  
  As mentioned above, controls can be found in /sys/devices/system/abb/ and the entries are self-explanatory. You can also change the frequency slice limits per sysfs, however in STweaks I only included the voltages for each slice only for now.
  
  Disclaimer
  { And that's about it in that regard. I have tried testing things over last couple of weeks, but I haven't come to a solid conclusion yet beyond what's presented by the stock characteristics: It's up to you people to do some advanced testing on the matter. My limited empirical testing in terms of voltages tells me it works as intended, but if a user with advanced measuring equipment would do similar testing to what I did back on the 4210 it would be perfect. }
• zRAM: Switched over from LZO to Snappy compression algorithm, this provides much faster compression and decompression than the LZO implementation which was in the current kernel. I updated the Snappy libraries to the latest original CSNAPPY implementation, so this is extremely new.
• Some kernel internal updates to speed up hotplugging and improve I/O latencies.
• A correctly (Unlike basically every other kernel out there till now) applied load averaging patch regarding fixing a Moiré pattern in the scheduler load calculations which was floating around.
• Fixed mono and equalizer switches in the sound engine. (Thanks to sorgelig for beating me to it)
• Fixed led controls to behave correctly with user-space apps.
• mDNIe digital brightness reduction:
  
  You can now lower the brightness to basically nothing via this: it uses the mDNIe engine to digitally remove luminance from the RGB channel values, as opposed to reducing brightness via a proper backlight/display driver. The side effect of this is that you lose colour resolution somewhat, but is a practical and working method to reduce the too bright minimum values of our displays.
  
  You have three configurables:
  • A reduction rate which you want to apply, this is the intensity of the darkening you want to achieve.
  • The take-over point; the backlight driver gets fed brightness values from 0-255 (In reality values below 20 have no effect). The take-over point is the point where the digital brightness reduction starts, on a reverse scale. The reduction is applied linearly from 0, (Full reduction taking place), to the take-over point (Zero reduction). The stock slider doesn't go below 20 in the interface, so practically the full reduction rate is never applied unless you use a third-party brightness controller app, just to keep that in mind, but in practice it doesn't matter.
  • Auto-brightness input-delta: This is needed because the stock framework is retarded in the values it forwards to the kernel, you can adjust this to avoid having brightness reduction when you don't want it on auto-brightness.
    
    Somebody needs to edit config_autoBrightnessLevels, config_autoBrightnessLcdBacklightValues in framework-res.apk\res\values\arrays.xml to fix this.
    
    Optionally, if you use a third-party app like Custom Auto Brightness which allows backlight values of down to 0, you can avoid this problem.
  The register hook needs to be enabled to be able to use this function.
• Increased the maximum brightness by 50 candela: the manual controls were limited to 250cd as maximum as opposed to 300cd which was only usable during auto-brightness, and unusable for any third-party apps.
• Unaligned memory access throughout the kernel when applicable.
• Switched over to GCC 4.7.3 Linaro toolchain for compiling.

Vorherige Versionen:

Spoiler

Perseus alpha35 (06/04):

• Further rewrote the in-kernel audio controls:
  • Threw out the old detection methods for something more robust.
  • This particularly enables non-cellular applications such as Skype, Viber, and so on to be detected correctly. A "calling" state now includes any and all use-cases where the audio is outputted via the phone's earpiece. This fixes microphone levels for such apps to correctly use the calling sensitivity value.
  • Added microphone level for camera use, this state is enabled whenever a camera stream is active. It should give more options into adjusting things to your likings.
  • By now the sound engine has only little similarities to Boeffla, any bugs and feedback now go directly to me.
• Developers only: MHS: Added a new small tool for tracking media use and reporting it to other in-kernel drivers. Capable of detecting video recording, decoding and camera streams for now. See commit for more info.
• mDNIe control changes:
  • Removed several controls in STweaks simply because people misunderstood them or misused them, or they simply had no rational use.
  • Video detection, now with the help of MHS, is no longer limited to the stock video player. Any video players using hardware decoding will now be able to make use of edge enhancement, HDR and DNR, this includes any web-based players and the YouTube app.
• Custom LED controls implemented; Exposed most variable controls for the notification LED via sysfs and STweaks (LED tab). :
  • Control LED brightness. Currently the OS dictates, depending on brightness detected by the light-sensor, wether to run the LED in a low-power mode or in a high-power mode, you can now set brightness for both.
  • Blinking control, this is basically the shape of the wave-pattern that the LED blinks in, you have several controls, best described the data-sheet description:
    
    
    
    
    The fade-in time period is TT1 in the graph, while the fade-out period is TT2.
    Slope (1/2/3/4) detention time represents DT1,2,3,4 in the graph, it controls how "steep" the four different curves are.
  • The LED fading checkbox simply switches between having the detention times controlled by the sliders to having them to 0 (Stock blinking behaviour).
• Increased default zRAM size to 400mB. This won't override your STweaks setting, so only new users will see the new value. Others should please adjust the value manually to your liking.

Perseus alpha34 (22/03):

• Updated sound engine. Based on Boeffla (Andip71)sound but custom fork with rewritten system interface and some other code re-factorings.
  • Should fix all FM Radio issues.
  • Brings us saturation prevention for the equalizer.
  • Privacy mode.
  • Microphone level control
  • You now have control over the speaker equalizer via sysfs, please visit /sys/class/misc/wolfson-control/ the controls are self-explanatory.
  • I removed the equalizer pre-sets from STweaks, if you want, set them manually:
    
    Bass-extreme: 12 8 3 -1 1
    Bass and Treble: 10 7 0 2 5
    Treble: -5 1 0 4 3
    Classic: 0 0 0 -3 -5
    Pleasant for ears: 4 3 2 3 1
    Eargasm: 12 8 4 2 3
• Enabled ZRam by default with disk size of 200mB and swappiness of 90%.
  
  The ZRam control is found in the I/O Tab in STweaks. Set it to 0 to turn it off completely, any other value to turn swap on. Changing value takes about ~10-20 seconds depending how loaded the disk is with swap pages so don't piss your pants if it doesn't react immediately.
• Applied a requested patch which allows PCs to be booted off from the phone storage.

Perseus alpha33.2 (27/02):

Master profile is correctly calibrated.

Detailed calibration report: Download
Advanced colour management report: Download

All thanks goes to Slimer777 for his excellent work.

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:
    
    
    
    (Credit to Wikipedia for the graphic)
    
    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.

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.

Perseus alpha31 (09/01):

• Removed my own security fixes and replaced them with the official Samsung one. I guess it can now be disclosed: exynos-mem was only one of multiple entry-points for the memory exploit. We discovered the s5p-smem exploit ourselves back in December but kept it quiet, I fixed that one back in version 29.2 without mentioning. Nobody was secure from a smart exploiter up until then, SuperCurios or Chainfire's software fixes are also just patching a single hole in what is a Swiss cheese. Kernels >v31 and beyond stock LLA are now the only truly protected ones.
• Samsung's fix for the sudden death syndrome (SDS) included. It is caused by eMMC failure on phones with VTU00M internal memory chips with revision 0xF1. You can check your phone with the "eMMC Brickbug Check" in the Play Store (Ignore the message if it says you're not affected, the type and revision is what matters). The patch is a firmware soft-patch that is applied on every boot and MMC resume, it is not a permanent fix. You will need to stay forever on kernels which include the patch, this also will include updated recoveries.
• Some other minor MMC changes extracted from Update 7 sources.
• Harmonized some mif/int max voltages with the Note 2 limits.

Perseus alpha30 (06/01):

• Internal and memory voltage control. This is the first and only working implementation out there. Memory interface voltage is exactly what it the name implies, the voltage on the chip-to-chip interface from the SoC to the memory chip. Internal voltage is the whole SoC voltage excluding CPU, GPU, and the MIF. This includes all auxiliary function blocks such as the ISP/Image signal processor, camera interfaces, I/O interfaces, display controller and the MFC/Multi function codec hardware video de-/en-coder.
  
  - Internal voltage respectively memory voltage table is found in /sys/devices/cpu/busfreq/ as int_volt_table or mif_volt_table
  - The frequencies are defined as OPP's (Operating performance points), internal frequency and memory frequency (And voltages) together as a pair form an OPP. If you want to change the voltages through the sysfs files, keep in mind how you change them. MIF voltages are stored independently with each OPP step. INT voltages are stored in respect of their frequency key.
  
  - Default OPP steps are: 400200, 267200, 267160, 160160, 133133, 100100. The first three numbers represent the memory frequency, the other three the internal base frequency. For example 267200 means the memory interface is at 267MHz (533MHz DDR) and the internal frequency is 200MHz.
  
  - The voltages in STweaks are sorted out through some magic and are frequency unique, I recommend using that for controlling them.
• Busfreq logic control added into STweaks, this includes all the already available configurables in the stock kernel with added explanations and I supplemented it with a sampling rate parameter.
• Some minor source updates from Samsung regarding some new sensor drivers.
• Replaced pegasusq's runqueue detection logic with a new more superiror and precise in-scheduler collection logic, I found that the real runqueues are much less than what was previously reported. This should help a lot with hotplugging.
• Enabled AFTR by default since we are now running very often in single-core mode. Keep in mind this mode is WFI Idle + LPA + AFTR.
• Fixed a kernel bug which was eating up randomness entropy. This is related to that whole seeder business - please don't use any of those fixes. I also disabled virtual addresss randomization and at the same time disabled entropy generation from the block layer, which should avoid I/O overheads.

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.

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. Read about it here. You don't need to use Chainfire's or Supercurio's fixes, in fact, you shouldn't use them because of the camera.
• 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.
  
  29.1: - Reverted the Wifi drivers back and did some CMA adjustments to see if that fixes some random reboots of people.

Perseus alpha28 (14/12):

28.1: I reverted the striked out changes due to exFat. I changed my mind due to demand. I apologize for the chaos.

• On your SD card showing up as damaged: it is not.
  I made a decision in terms of exFat compatibility; either I advance the kernel with newer upstream Linux versions or stay back and keep compatibility with the exFat modules. While I have nothing against proprietary modules or such, not being able to adapt them to the kernel is not optimal. You can format your cards to FAT32 or ext4 without much issue. Please back up your data and format your card accordingly before flashing v28.
  [*]Updated the block system to Linux kernel 3.3.
• Introduced FIOPSv2, ROWv4, ZEN, BFQv5 as new I/O schedulers;
  
  FIOPS is the new default scheduler, it's a CFQ like fairness scheduler optimized for solid state storage. ROW should be the actual better performer here as it has superior logic, but I didn't set it as default because of some lags when installing applications. ZEN is just a mix of SIO and Deadline and nothing special. BFQ seems to underperform. I recommend the first two over everything else, and added the latter two just for comparison's sake.
• Added dynamic Fsync control (Faux123). It disables Fsync only when the screen is on. Enabled by default (Fsync off).
• Changed some logic on when the adaptive scaling voltages are applied in the kernel init sequence. This fixes GPU voltages not being applied at boot and also fixes the wrong default voltages being displayed in STweaks.
• STweaks tab for I/O with scheduler selection for each device block and also dynamic Fsync.
• New script side feature in the uci.sh framework: When inserting an override.profile file into the profile folder (/data/.perseus), the entries in the override profile will supersede the ones in your default profile. You can use to make CWM zips to turn off set at boot flags or to share targeted settings with others. The override is applied once at boot after which the profile deletes itself.

Perseus alpha27 (02/12):

• Sources updated with various updates from N8000u1 base. Included are following important changes;
• CMA memory allocation has been altered and page handling in the kernel in regard to CMA affected pages has been dramatically improved, this should fix the high load of the "migration" process users have had since initial Jellybean kernels.
• Updated wireless drivers.
• Adds a delay to SD Card host controller power-down, which I assume is to prevent some corruption. There is a specific change to Toshiba 19nm manufactured SD Cards, these are mostly the latest SanDisk 64GB cards. Together this may fix issues users have had.
• Updates the camera interface, Video4Linux and Jpeg2x drivers and this fixes compatibility with 4.1.2 ROMs. Backwards compatibility is retained.
• Other updates which are more transparent to the end-user.
• New PegasusQ logic:
  
  - We now have additional conditionals on the hotplug logic which checks the total load across all cores and is able to bias towards a specified core count if the load is low. This is useful because previously we could have had frequency spikes and lots of low-load threads triggering a hotplug-up while in reality it wasn't needed. The core count is more biased on keeping 2 cores online in most cases now unless really needed.
  
  - The way freq_step is handled has changed. We now take the remainder of load space above the up threshold and dissect it into three slices each having different frequency increase step sizes. The first two slices are each of up threshold differential size, lop-sided towards the lower end of the load scale. We specify the slice size and freq_step delta in regard to the original freq_step.
  
  - A new fast-down scaling logic; if frequency is beyond a certain threshold, we take a heightened up_threshold value solely on the down scaling logic to scale down more aggressively from the higher frequencies.
• STweaks. This is my custom implementation of the kernel side, based on Gokhan Moral's initial implementation.
  
  - CPU overclocking and voltages interface.
  - Configurables for all CPU governor settings.
  - GPU overclocking and voltage interface.
  - Interface for audio enhancements.

Perseus alpha26 (14/11):

• Updated MTP drivers back to the newest version. Fixes some inconsistencies which some people had.
• Further increased MMC command timeout from Linux default 300ms to 3s in trying to finally squash errors and "unexpectedly removed SD card" after resume.
• Ported Gokhan Moral's mDNIe interface and also added colour tone modes on top of the scenarios. System interfaces are found in /sys/class/misc/mdnie . Input syntax is the same as the output syntax, or, single register-value pairs as a single line in the output format, except 0xFF which is a terminator value.
• Increased default sampling rate down to 30ms from 50ms for a bit more fluidity.
• LTE devices only: Updated some power management functions on the MDM modem from latest sources; this will drastically decrease the amount of wakelocks on mobile data and improve battery life.
  
  26.1
• Disabled net_os_rxfilter_add_remove userspace/ROM filter management in the Wifi driver to prevent the operating system of enabling unwanted pass-through multicast and broadcast filters while in standby.

Known issues

>> Keine


Download

Download alpha36.1CWM.zip (NUR für Sammy JB Roms)

Sudden Death Fix enthalten.





Sources:
https://github.com/AndreiLux/Perseus-S3


Credit and thanks:
gokhanmoral
netarchy
and anybody credited in the commits

Thread @ XDA

 

[Kjetal]

Kernel von AndreiLux , bekannt vom SGS II , zwar nicht durch einen Kernel aber durch ein sehr gutes Fachwissen.

Der Kernel ist noch im Alpha Stadium.


Quelle XDA




Features:

Perseus alpha14 (21/06):

• Only Mali platform changes.
• Remove Samsung integrated checks on in the Pegasus platform that prevented the GPU control interfaces to work. Overclocking, undervolting, and the rest now properly work.
• Removal of the CPU frequency lock to 1200MHz if the GPU is at 440MHz, this is excessive as 3D load heavy applications usually do not tax the CPU that far, and is an unnecessary power consumption burden.
• The thermal control unit temperature throttling causes to fix the voltage to a fixed value when throttling is in place; this is useless considering frequency is not limited, making the whole thing senseless. Thus removed.

Perseus alpha12 (14/06):

• Added enhanced init.d support as per dk_zero-cool's implementation.
• SHA-1 improvements
• Added exception to the module loading logic for the exFat driver module thus making it work. (Credit to gokhanmoral)

Perseus alpha11 (10/06):

• ro.secure=0
• Recovery renamed as busybox in /sbin. I'll compile a proper busybox later on, or remove it alltogether when a recovery with autoinstall is released by CF or somebody else.

Perseus alpha10 (8/06):

• Overclocking up to 1800MHz. Voltages in ASV table are somewhat scaled up until 1600MHz, after that you're on your own and have to optimize yourself.
  Intel claims maximum sustainable safe voltage for 32nm HKMG to be 1.4V, above that may cause electron migration to the silicon and permanently deteriorate your chip. 1700 and above only for avid overclockers and benchmark freaks. Credit to tvanhak for playing lab rat with his phone.
• Samsung frequency limitation removed to scale above 1400MHz, full credit goes to Gokhanmoral fo

Perseus alpha7 (5/06):

• Reduced regulator voltage initialization minimum to 600mV, you can now undervolt that far. Be aware of crashes.
• Added SIO scheduler
• Some network and CRC related patches

Perseus alpha3 (4/06):

• Mali: disable state tracking
• Mali: GPU frequency, scaling and voltage control
• Governor pegasusq: make up_threshold_at_min_freq and freq_for_responsiveness configurable values. This is the reason the Galaxy S3 is so smooth, it has super aggressive scaling values for the governor until default 500MHz.
• Enabled 1500MHz per defconfig and added voltage values to ASV table for it
• Added UV_uV_table for voltage control on the CPU; this is not compatible for any programm which supports undervolting right now, we need UV_mV_table for that and since we have 12.5mV steps being fed to Vdd it's not compatible for now.
• Boot partitions are made visible.

Forthcoming:

• Make it stable and bootable, duh.
• Adapt a UV_mV_table for compatibility with existing programs. This will involve some rounding.
• Increase overclock above 1500MHz, I would appreciate any feedback on APLL and clock divider values for this.
• Make the other *wink wink* hotplugging values from Samsung configurable.
• Implement all those nonsense upstream patches which don't do much on our specific platform, but which people really seem to want.
• Kang any cool features other developers come up with.
• Either make ExTweaks working or develop a more suitable app myself for configuring of the kernel.

Sources: https://github.com/AndreiLux/SGS3-Perseus/

Status :

Online

 

[Scoty]

Und schon getestet?

 

[Kiray1982]

Soll wohl noch Probleme geben, das das WIFI-Modul nicht funktioniert.
Er arbeitet an einem Fix.

 

[walda]

das dürfte immer das selbe leidige problem sein. cm9 am note zu beginn das gleiche.

... tapat*lked

 

[So_ony]

Kernel ist rausgenommen worden weil er zu viele Bugs hat, schade drum. Aber Simeone bringt in ungefähr 2 Tagen den Neak Kernel raus

 

[Kiray1982]

Perseus alpha6 (4/06):

• UV_mV_table support, apps like SetCPU work now.
  If you have a voltage set at for example 1187500µV the output will be rounded up to be displayed at 1188mV. If you set a voltage non multiple of 12.5mV then for example, 1190mV, it will round it to the nearest valid step, being 1187.5mV. UV_uV_table is there for finer grained control but no app suports that yet.

 

[Kjetal]

Perseus alpha7 (5/06):

• Reduced regulator voltage initialization minimum to 600mV, you can now undervolt that far. Be aware of crashes.
• Added SIO scheduler
• Some network and CRC related patches

 

[Scoty]

Werde denn auch mal testen. Wifi geht inzwischen?

 

[Kjetal]

Jo geht

 

[--scorpion11--]

Bringt der schon effektiv was ?

Gesendet von meinem GT-I9300 mit Tapatalk 2

 

[Snake3]

Nach einem 2 Woechigen Test sagen wir ja.

 

[Silene84]

Man kann zwar jetzt ein paar Sachen einstellen, dafür läuft er aber nicht so smooth wie der Stock. Werd erstmal wieder zurück flashen. Aber schön zu sehen das es langsam los geht

Gesendet von meinem GT-I9300 mit Tapatalk 2

 

[Phila]

Ich behalte den hier bis morgen da ja der Siyah released werden sollte aber Persus finde ich besser als Stock!

 

[haris100]

Solange der Kernel meine sdkarte nicht erkennt, macht er für mich keinen Sinn.

Das S3 hat meine 64gb Karte nach dem Einlegen mit extFAT formatiert. Damit scheinen momentan alle custom kernel nicht zurecht zu kommen.
Ich werde noch etwas warten, falls es aber in absehbarer Zeit keine Lösung gibt, werde ich wohl doch eine Umformatieraktion starten.

 

[Scoty]

Also ich weiß nicht was ihr alle habt mit der SD Karte aber meine 32GB Karte habe ich auch normal im S3 formatiert und ich kann sie normal ansprechen im CWM.

 

[Phila]

Jaaaa in CWM Datei Manager ist gemeint.

Gesendet von meinem 4X HD mit Tapatalk 2

 

[Scoty]

Auch da gibt es keine Probleme.

 

[haris100]

Auch da gibt es keine Probleme.

Nach dem Hochfahren bekomme ich eine message dass ich die sdkarte nun entfernen kann. Sprich dass sie entfernt wurde.
wieder "einlegen" geht nicht.

Gesendet von meinem GT-I9300 mit der Android-Hilfe.de App

 

[Phila]

Auch da gibt es keine Probleme.

Screenshot bitte

Gesendet von meinem 4X HD mit Tapatalk 2