> Attention!

We strongly recommend to readRules section "Android - firmware"

New threads need to be created only inroot partition! In the future, they will be processed by moderators.



Samsung GT-I9300 Galaxy S III - Modified and stock cores



Rep: (1630)
Samsung Galaxy S III GT-I9300 - Modified and core stock
PictureSamsung Galaxy S III, SGS3, GT-I9300, m0
Description | Discussion | Accessories | Marriage / Repair | Wi-Fi setup and problems | Power consumption (autonomy) | Modified and stock kernels | Custom recovery | EFS Recovery (IMEI)
Firmware:Official | Custom | MIUI| OpenSource (4.x | 4.4 | 5.x | 6.x-7.x) | Topics for CM12 / 13

Glossary
Core - Spend some time on forums and blogs dedicated to Android, you will see many references to this term. But the core is not something unique, used only in Android. iOS and MacOS, Windows, BlackBerry's QNXVse and other operating systems use it. Since the Android uses the Linux kernel, the more will be discussed is about it.

The Linux kernel, which uses your Android device is different from that use different operating systems. It contains a set of special codes. Manufacturers are also involved in the process, as should issue the driver used for iron under the current version of the kernel. For this reason, independent developers takes some time out to make a new version of the work on the old device without a premium. Drivers written by Gingerbread, may well not work on the core Ice Cream Sandwich. And this is very important, because one of the main functions of the kernel is that it is necessary for iron control. Inside Continuation Android kernel.

For any action of iron and software necessary to the kernel. For example, you click on the Search button on your phone, so you give the command to open the corresponding application. The following occurs: you touch a certain point digitizer, which transmits information about a software touch the screen at certain coordinates. Software knows that when exposed to a certain point it is necessary to open the search window. The core of this situation causes the digitizer to perceive touch, find their location, and to talk about the system of implementation of this action. Ultimately, when the system receives information about the touch from the core (through the driver), she knows what needs to be out on the screen. Software and hardware are connected to the core, which allows the phone to perform the necessary actions. Incoming information on the one hand becomes outgoing and the other leads to action.

Without the nucleus, which sends and receives information, developers would have to create codes for each event and for each element of iron in your device. With the core of it all so much easier. Developers only need to tie all the elements together.

Linux script - as a rule executable file written in the command language shell (shell) linux and having an extension sh. It is a sign of the presence of characters #! / Bin / sh at the beginning of the file. Because in Linux for security reasons the current directory is not considered as such for the executable file, the script is always executed with the prefix of the current directory ./skript.sh. I draw your attention that the script is necessary for him to do exactly so, it must be assigned to an attribute of the executable file "x". In addition Ubuntu for this attribute is the command chmod + x skript.sh. I draw your attention that, in contrast to the many Linux distributions, Ubuntu uses the default shell dash, rather than bash (bourne again shell). For scripting compatibility is sometimes necessary to explicitly register at the beginning of the script #! / Bin / bash.

Bootloader - the operating system loader. We exist a huge number of different downloaders. When any device is activated, the processor must immediately transfer control to some point in accordance with the initial values ​​of the registers. As a result, execution jumps to the boot loader or boot loader, which has already passed certain parameters of the core operating system and load it into memory management transfer. In such SGSIII kernel loader is secondary bootloader (Secondary Bootloader), which is stitched file sbl.bin.

Governor - regulator of processor behavior. Sets the algorithm for which the processor will change the frequency with increasing / decreasing load. There are many different algorithms: conservative, interactive, ondemand, lulzactive, smartass, etc. It is installed either by the program or through a script in some kernels.
Brief description of controls
brazilinawax - while the description is not found. All that is known is based on interactive. Almost the same as Smartass.

ondemand - Available in almost all kernels and in many is default (by default). When the CPU load reaches a certain upper threshold, this control quickly raises the frequency of the processor to respond to the request, then gradually reduces the frequency of the CPU when it is no longer needed.

ondemandX - changed sensitivity and added sleep mode.

conservative - Available in some cores. It is similar to the ondemand regulator, but will increase the frequency of the CPU more gradually (not so fast) to better fit the request. This regulator provides less sharp response, but may save the battery better.

interactive - it has a different approach. Instead of the CPU to sample at a specific frequency (level), it will raise the rate when the processor exits the idle mode. When the CPU goes from idle timer configured to ensure that run for 1-2 ticks (CPU cycle of operation). If during this time (from the time the output from the processor idle mode to start the timer) is loaded on the CPU 100%, it is considered enough distilled and the frequency rises to a maximum value. If the CPU was not 100% occupied, while the regulator assesses the CPU usage for the last 'min_sample_rate' (default 50,000 ms) to reduce the frequency to the desired level. This control is considered more interactively responds to different CPU. The only configurable parameter - the time during which the processor will remain at a particular frequency before you will start to decline (50,000 microseconds).

interactiveX - supplemented with interactive code that blocks the CPU at the minimum frequency when the device screen is turned off. It has a sleep + wake profile, meaning that you don’t have to manually set the Screen Off profile in SetCPU.

lazy - in ondemand basis min_time_state with an additional parameter to indicate the minimum time during which the CPU is at the frequency before a decrease / increase in the latter. The idea - to remove any instability caused by the rapid change of frequency ondemand. This control state polls more often than ondemand, but changes the frequency by one step only after min_time_state. Screenoff_maxfreq also has a parameter that can be set to determine the maximum frequency of screen-off.

lagfree - quite similar to ondemand in source code and its design and purpose. The difference in its optimization for better stability and "sharpened" in a loaded environment. The frequency delicately decreases and increases, instead of immediately jumping to 100% when speed is needed.

lulzactive - default in the core Lulz. Based on interactive. With the profile of the disabled screen as interactiveX and some features of smartass.
Algorithm (eng):
cpu work load>= 60%
cpu frequency changes from (Lx) to (Lx -1)
up sampling time = 24000us (from smartass governor)
eg)
(L0) 1200 - (L1) 1000 - (L2) 800 - (L3) 500 - (L4) 200
cpu_load = 60%, current frequency = (L2) 800>>frequency = (L1) 1000
cpu_load = 60%, current frequency = (L1) 1000>>frequency = (L0) 1200

cpu work load< 60%
cpu frequency keeps (lx) to (lx + 1)
down sampling time = 49000us (from smartass governor)

screen off
cpu frequency is locked at scaling min freqeuncy.
default min freq of Galaxy S II is 200MHz.
"screen off" profile of SetCPU.
minmax - Conservative adaptation, but with very good performance. A very nice regulator with a good battery life.

performance - Available in some cores. Will keep the CPU at the maximum set frequency all the time. This is more efficient than setting min and max at the same frequency and leaving the ondemand regulator, because the system will not waste resources on checking the CPU utilization rate.

powersave - Available in some cores. Will keep the CPU at the minimum set value all the time.

userspace - Allows a user or program with root rights (works with UID 0 - root) to install the processor at a specific frequency via the file scaling_setspeed in a specific directory.

SavagedZen - while the description is not found. All that is known is based on interactive. Another one is very good and balanced modification Smartass.

smartass - (erasmux @ xda). Fully rewritten interactive control. The CPU spends more time at lower frequencies to improve battery life. Also gives the Screen Off profile, staying at the minimum frequency when the phone is not active (in idle mode).

smartassV2 - A lot of customizable parameters. Quickly responding to changes in CPU utilization, based on the idea of ​​interactive. The threshold of the "ideal frequency" is also adjusted (as in lulzactive) and the controller above this frequency behaves more aggressively than in the lower zone. In sleep mode, another, also customizable, “ideal frequency” is used.
Description of the repository with the source (English):
2.7 SmartassV2
+ The CPUfreq governor "smartassV2", like other governors, aims to balance
+ Performance vs battery life by using low frequencies when load is low and
+ Ramping the frequency when necessary, fast enough to ensure responsiveness.
+ The implementation of the governor is roughtly based on the idea of ​​interactive.
+ The idle loop is used to track when the CPU has idle cycles. The idle loop will
+ Set a relatively high rate timer to sample the load when appropriate, the timer
+ Will measure the load since it was set and schedule a work queue task to do the
+ Actual frequency change when necessary.
+ The most important tunable is the "ideal" frequency: this governor will aim
+ For this frequency, in the sense that it will ramp towards this frequency much
+ More aggresively than beyond it - both when ramping up from below this frequency
+ And when ramping down from above this frequency. Still, note, that when load is
+ Low enough the governor should choose the lowest available frequency regardless
+ Of the ideal frequency and similarly when load is consistently high enough the
+ Highest available frequency will be used.
+ Smartass also tracks the state of the screen, and when screen is off (a.k.a
+ Sleep or suspended in the terms of this governor) a different ideal frequency
+ Is used. This is the only difference between the screen on and screen off
+ States. Proper tuning of the awake_ideal_freq and sleep_ideal_freq should
+ Allow both high responsiveness when screen is on and utilizing the low
+ Frequency range when load is low, especially when screen is off.
+ Finally, smartass is a highly customizable governor with almost everything
+ Tweakable through the sysfs.
smoothass - a little more aggressive smartass
Initrd (Abbreviation of the English Initial RAM Disk, the disk in memory for initialization.) - a temporary file system used by the Linux kernel at boot time. Initrd commonly used for initialization before mounting the "real" file system. The Linux Kernel HOWTO (manual about compiling the kernel), write that initrd is intended to solve the problem of chicken and egg for modular kernel: for mounting the file system module is required for the disk and the file system, and requires a file system for reading the module with which the module read.

Initramfs
The Linux 2.6 kernel has a new concept of boot disk Initrd - it is a compressed cpio-archive gzip.

I / O Scheduler - scheduler I / O operations. Responsible for planning the read / write block devices (flash card, hard drive, etc.). Task - the most efficient use of memory. The following schedulers (in order of appearance in the Light): noop (Linus Elevator), Deadline I / O Scheduler, Anticipatory I / O Scheduler, and "fair" scheduler - CFQ - Complete Fair Queuing I / O Scheduler. There are more recent - VВ®, SIO (Simple) and BFQ (Budget Fair Queuing).

Overclocking (OC) - increasing processor frequency limit (acceleration), which causes additional power consumption and heat generation. Degree of acceleration is highly dependent on the cooling and crystal quality.

Undervolting (UV) - lowering the power supply voltage that whatsoever. May refer to the CPU (usually) - CPU, graphics - GPU or system bus. It can significantly reduce the energy consumption of the whole system. The degree of UV stability and secure also depends on the quality of the crystal and is chosen for each telephone individually.


Kernels
Kernel core

Custom kernels
Cores for CM 10.1 / 10.2 / 11/12 / 12.1 / 13/14 / OmniRom / MIUI / LOS 14.1
Kernel for LOS 14.1

Kernel for CM 13

Kernel for CM 12 / 12.1

Kernel for CM 11 / OmniRom / MIUI

Cores for CM 10 / 10.1 / 10.2
Boeffla Kernel
Additional information about the kernel

arter97 Kernel - supported Dualboot
Additional information about the kernel

phenomenal v4.0
Additional information about the kernel
If you use a kernel cleanup script, then after the firmware Phenomenal core to core firmware do wipe cache + wipe dalvik cache

Siyahkernel - CyanogenMod 10.1
Additional information about the kernel

Googy-Max v1.8.0 - Supports Dualboot
Additional information about the kernel
XDA thread
STweaks_2.0_Googy-Max - A program to configure Googy-Max kernel

N.E.A.K. v3.3x



Kernel for Samsung TouchWiz
Kernel for Samsung TouchWiz 4.4.x
MoRoKernel 1.8 - samsung 4.4.4
Additional information about the kernel

Boeffla Kernel - samsung 4.4.4
Additional information about the kernel

arter97 Kernel - samsung 4.4.4
Additional information about the kernel

MoroKernel 2.6 - samsung 4.4.2

arter97 Kernel - samsung 4.4 supported by Dualboot
Additional information about the kernel

AGNi pureSTOCK - samsung 4.4
Additional information about the kernel

Yank555 v4.2a-beta3 - samsung 4.4

Boeffla Kernel - samsung 4.4
Additional information about the kernel


Kernel for Samsung TouchWiz 4.1.2 / 4.2.2 / 4.3
XPure Kernel 794 - samsung 4.3

Adam Kernel v3.0 - samsung 4.3

LiteGX v5.1.0 - samsung 4.3

Yank555 v4.2 - samsung 4.3
Additional information about the kernel

Boeffla Kernel - Samsung 4.1.2 / 4.3
Additional information about the kernel

AGNi pureSTOCK - Samsung 4.1.2 / 4.2.2 / 4.3
Additional information about the kernel
Download the latest version: v2.6 for 4.1.2 | v3.2 for 4.2.2 | v3.8.5 for 4.3

Devil2 v2.3.2 - samsung 4.3 - supported Dualboot A warning!

HydR3xtReme v4r97b

GalaxSih v2.0 beta7

Franco.Kernel r20

SpeedMod K2-13

Shark A-21 - samsung 4.1.2

Energy v2.0

yoda v1.8 - samsung 4.1.x

LiteGX v5.8.0 - samsung 4.1.2

N.E.A.K. v3.3x

perseus alpha36.3 - It does not work on 4.2.1
Additional information about the kernel

Googy-Max2 v2.3.2 - samsung 4.3 - supported Dualboot
Additional information about the kernel
STweaks_2.0_Googy-Max - A program to configure Googy-Max kernel

Googy-Max v1.8.0 - samsung 4.1.2 - Supports Dualboot
Additional information about the kernel
XDA thread
STweaks_2.0_Googy-Max - A program to configure Googy-Max kernel

Googy v2.6 - samsung 4.1.2 - Supports Dualboot

SimpleGX v1.7.0 - samsung 4.3

arter97 Kernel - samsung 4.3 supported by Dualboot A warning!
Additional information about the kernel

More core - read the description of the topic onxda

The kernel kCoffee For firmware based on Android 7.x.


Instructions

Scripts and applications
Aroma pack custom kernels for runoff and based on the stock firmware based on Android 4.3
Scriptfor the disposal of tailings cores and systems
Scriptfor the disposal of tailings cores and system Android 4.3
SetCPU- CPU frequency control
Zram & Hard Swap Control
MTweaks


FAQ, testimonials and comments to the nuclei

Voting archive
Attached Image

Attached Image

Attached Image

Attached Image


There is no curator in the subject. If there is a user in the subject who wants to become a Curator and the correspondingRequirements for candidates, he can apply in the topicI want to be curator(after having studied the topic header and all materials for curators).
Prior to the appointment of the curator, on filling caps, please contactmoderatorssection through a button"a complaint"under the messages to which you want to add links.


Post has been editedsnekt - 08.03.18, 23:19
Reason for editing: editing



Rep: (22)
* chefuik,
Good day!
What's the difference in the nucleus? whatcoresuitable for original i9300?



Rep: (510)
* La_master stock



Rep: (22)
* A $ teroid,
I would like to LOS 14.1 core boeffla rolled forward and he closed the site, here looking for traces of ...



Rep: (32)
La_master @ 17.02.20, 09:16*
What's the difference in the nucleus?

Different build (builds), tried last - Boeffla-kernel-6.1-Lineage14.1-i9300-u800-2018-03-28-220527 -anykernel.recovery.zip, is now moved to the Elite-Boeffla-Kernel.
La_master @ 17.02.20, 09:57*
I would like to LOS 14.1 boeffla core to roll

They (the nucleus by reference) just for LineageOS14.1 / CM14.1 and firmware on their basis (difference with the original boeffla collected using linaro tool kit).



Rep: (22)
chefuik @ 17.02.20, 16:58*
Now I moved to the Elite-Boeffla-Kernel.

Here you can read more? I want to understand truly elite boeffla steeper usual boeffla.



Rep: (32)
* La_master,
Yes, I should clarify immediately that thisFashion Elite-Boeffla-Kernel ByOebbler1 ,
set of capabilities;
- much lower brightness can be set than on stock kernel; the display will be almost black on lowest brightness level (maximum possible brightness stays the same)
- You can set a much lower brightness than standard kernel; almost black display is at the lowest luminance level (the highest possible brightness remains the same)



Rep: (22)
chefuik @ 18.02.20, 16:20*
You can set a much lower brightness than standard kernel; almost black display is at the lowest luminance level (the highest possible brightness remains the same)

This is it?boeffla-kernel-4.0-OC_2.0GHz-CM12.1-NG-i9300-by_Oebbler.recovery.zip

And how's it going? PWM at a minimum brightness?



Rep: (32)
La_master @ 18.02.20, 14:33*
This is it?

No that's itelite-boeffla-kernel-6.1.0.2-CM14.1-i9300.recovery.zip
PWM does not know how to find out?



Rep: (22)
chefuik @ 18.02.20, 16:57*
PWM does not know how to find out?

So then there are special devices. I do not know if you can program for the smartphone or via the camera.
Theoretically, the darker the more amoled-PWM.



Rep: (119)
* A $ teroid , Hello. Friend got the phone battery with power on the 4000. I gave him a firmware / e /, and was surprised that the battery holds not much. Now I read the post here
Samsung GT-I9300 Galaxy S III - Modified and core stock (Fasting yslash # 86642267)
Is it true that in the core should be special support of this size battery? Is there a core? If not, it difficult to add this support?



Rep: (510)
Hichohazotso Hezhikohage @ 03/19/20, 17:13*
Is it true that in the core should be special support of this size battery?
Not.
Check autonomy on the other firmware. Desirably okolostokovoy.



Rep: (119)
chefuik @ 18.02.20, 14:20*
Fashion Elite-Boeffla-Kernel By Oebbler1

Since it is not found in the subject line of the core, I put it here to not lose.
Features
- Every feature from official Boeffla-Kernel (6.1 final)
- Support for Synapse (partial) and Boeffla Config (fully)
- CPU overclocking up to 2 GHz
- CPU: 100MHz step added to save power
- Faster boot process due to some internal improvements
- 3 new governors added (adaptive, conservative, interactive)
- CPU voltage can be chosen between 600mV and 1600mV
- full F2FS support (backported from Linux 3.19)
- Charging current can be set up to 2.1 Amps
- Battery percentage never reaches 0%, so the phone will not turn off at low battery
- No overcharge anymore due to an internal improvement
- Early suspend adjustable up to 5000ms
- more undervolting profiles for the GPU
- much lower brightness can be set than on stock kernel; the display will be almost black on lowest brightness level (maximum possible brightness stays the same)
- Configurable kernel logger (turning kernel logger off is not stable on CM and LOS)
- compiled using GCC 7.2.1 by Linaro (Thanks to ZaneZam for publishing the kernel-specific GCC-6-code; this works with GCC 7 as well!)

Changelog
6.0.0.1-beta1
First Release
this kernel includes every feature and bugfix of Boeffla-Kernel 5.1.0.5 (for CM13.0)
Full F2FS support

6.0.0.1-beta2
not published

6.0.0.1-beta3
Sources updated (all changes from CM-Kernel made until 19.12.2016)
Toolchain updated: GCC 6.2.1 Linaro

6.0.0.1-beta4
Sources updated (LineageOS from 05.01.2017)

6.0.0.1-beta5 and 5.3.0.5-F2FS (CM13.0 version)
Sources updated (LineageOS from 10.01.2017)
Busybox updated to 1.26.2 (thanks to Lord Boeffla)
Kernel logger can be controlled again (below Android logger)

6.0.0.1-beta6
Sources updated (LineageOS from 06.02.2017)
UMS and SELinux fixed (SELinux can be controlled again)

6.0.0.1-beta7
Sources updated (LineageOS from 15.02.2017)
Toolchain updated to Linaro 6.3.1

6.0.0.1-beta8
Sources updated (LineageOS from 07.04.2017)

6.0.0.1-beta9
not published

6.0.0.1-beta10 and 5.3.0.7 (CM13.0 version)
fixed charge levels; now they work fine
internal improvements to extend battery life and to avoid overcharge of the battery

6.0.0.1-beta11 and 5.3.0.8 (CM13.0 version)
Sources updated (LineageOS from 04.06.2017; CM14 kernel only)
Display brightness can be set much lower than on stock kernel now (the display will be almost black on lowest brightness level); but maximum possible brightness stays the same

6.0.0.1-beta12
Sources updated (LineageOS from 21.07.2017)
Toolchain updated to Linaro 7.1.1
Busybox updated (version 1.27.1 compiled by Lord Boeffla)
Display brightness slider fixed
Doze mode switch fixed

6.0.0.1
Same as 6.0.0.1-beta12, but better tested

6.0.0.2
Default governor changed to intelliactive
Default I / O scheduler changed to deadline
Fix for Doze mode switch reworked
Busybox updated (version 1.27.2 compiled by Lord Boeffla)
Toolchain updated to Linaro 7.1.1-2

6.0.0.3
not published

6.0.0.4-Synapse
Sources updated (LineageOS from 19.01.2018)
Synapse support added in addition to Boeffla Config support (Synapse apk can be found in / res / synapse after installing this version of Elite-Boeffla-Kernel)
Default governor changed to pegasusq

6.1.0.1-beta5
Default governor changed back to intelliactive
Battery percentage will show 1% instead of 0% iff battery is fully discharged; it is highly recommended to charge the phone immediately when reching 1%!
Added support for mount namespace separation in order to support Magisk Hide

6.1.0.1
not published

6.1.0.2
fixed the LED driver to properly provide the given settings in Boeffla Config and Synapse
fixed some voltages to get a cooler CPU

Tuning Recommendations
Battery saving:

Doze enabled

SELinux strict

Governor: conservative or intelliactive

Scheduler: deadline

File system tweaks: both on

CPU maximum freq: 1300MHz

CPU minimum freq: 100MHz

CPU idle mode: AFTR + LPA

CPU voltage: set it as low as it is stable on your phone

GPU frequency profile: 108/160/200/266/350

GPU voltage: set it as low as it is stable on your phone; typically you can undervolt more than 100mV here

Boeffla sound: configure it by yourself until you get the best sound out of it

LED brightness: 40 or less

Touch boost: disabled or 600MHz

Touch wake: disabled

Early suspend: 10ms (default on my CM14.1 kernel)

MDNIE settings: configure it by yourself until you get the best out of it

Touch key LED: same as MDNIE settings

AC charge current: 2000mA

USB charge current: 500mA

Wireless charge current: 1000mA

Swappiness: no overwrite

Low memory killer: default values

System tweaks: off

zRam: off

TCP congestion: default

Entropy settings: default

Android logger: off; except for debugging

Kernel logger: on


Performance:

Doze enabled

SELinux strict

Governor: intelliactive or ondemand

Scheduler: deadline

File system tweaks: both on

CPU maximum freq: set this as high as it is stable on your phone

CPU minimum freq: 100MHz

CPU idle mode: Idle only

CPU voltage: set it as low as it is stable on your phone

GPU frequency profile: choose either a profile or overclock manually; you can set this as high as it is stable on your phone

GPU voltage: set it as low as it is stable on your phone

Boeffla sound: configure it by yourself until you get the best sound out of it

LED brightness: 0 to 255; choose it as you like it

Touch boost: 1300MHz or 800MHz

Touch wake: can be enabled if you want this feature

Early suspend: 10ms (default on my CM14.1 kernel)

MDNIE settings: configure it by yourself until you get the best out of it

Touch key LED: same as MDNIE settings

AC charge current: 2000mA

USB charge current: 500mA

Wireless charge current: 1000mA

Swappiness: set it as you like it

Low memory killer: default values

System tweaks: off

zRam: set it as you like it

TCP congestion: default

Entropy settings: default

Android logger: off; except for debugging

Kernel logger: on


For a combination of performance and battery saving you can either combine these two profiles or leave the default settings of my kernel. If you do not know what a specific setting does I'd recommend you to leave the default value that came with my kernel.

XDA thread
Attached fileOebbler1-elite-boeffla-kernel-6.1.0.2-CM14.1-i9300.recovery.zip(6.04 MB)


Post has been editedHichohazotso Hezhikohage - Today, 16:42


Full version    

Help     rules

Time is now: 04/05/20, 20:18