[KERNEL][ICS/JB][ExTweaks][All-in-1kernel][DualBoot][Eargasm] SiyahKernel v4.x.x

[Nihil Morari]

Io ho avuto un problema dopo aver flashato il nuovo siyah, anche se non so se dipenda da questo. Ho trovato spento il telefono e l'ho dovuto accendere togliendo e rimettendo la batteria.

[illuminato67]

Io ho avuto un problema dopo aver flashato il nuovo siyah, anche se non so se dipenda da questo. Ho trovato spento il telefono e l'ho dovuto accendere togliendo e rimettendo la batteria.

Grazie x la segnalazione. Teniamolo presente.
Continua il test, con consumi discreti. Per il resto tutto superlativo.

[Ste Oh Yes]

Perchè se metto l' oc a 1500 o a 1600 si impalla sempre ??

[IImanuII]

Ripropongo ciò che ha postato l'ottimo fabrizioo2007 (post 888) che sarà di aiuto a tutti i Siyahiani (in omaggio al grande Alessandro)


PER INSTALLARE UNA NUOVA ROM DIRETTAMENTE SULLA SECOND ROM :
-installare il syahkernel dalla versione 3.2b8 in poi
-come si può leggere dal changelog prima di installare la second rom bisogna fare un format di data e cache a cui si accede da "mount and storage" (no advance Nihil )
-Procedere,una volta terminate le operazioni sopra descritte, ad installare lo zip della rom tramite i comodi comandi nella sezione dual boot options
ECCO DESCRITTA DUNQUE LA MANIERA PIU COMODA E VELOCE PER INSTALLARE LA SECONDA ROM SENZA DOVER FARE IL LENTISSIMO SWIPE TRA PRIMA E SECONDA ROM!!!
METODO APPENA TESTATO E FUNZIONANTE

Allora ê da mettere in 1 pagina

Inviato dal mio GT-I9100 con Tapatalk 2

[illuminato67]

Allora ê da mettere in 1 pagina

Inviato dal mio GT-I9100 con Tapatalk 2

Già proposto ma luca_vivi non si fa vivo

Inviato dal mio GT-I9100 con Tapatalk 2

[Ste Oh Yes]

Qualcuno mi può rispondere ?


Inviato dal mio GT-I9100 usando Androidiani App

[illuminato67]

Guardate cosa ho trovato (si vede che oggi non ho un ... da fare) Buona traduzione!

xda-developers - View Single Post - [REF][ICS] Kernel Stuffs - How is ICS Kernel Different | updated may-13-2012

Pegasusq Governor

Let's see what is pegasusq governor which claims to be a multi core aware governor.

Some Basics to Remember Before Reading On:
Some patience is required to understand a governor.
Pegasusq is basically an ondemand based governor which also controls hotplugging.
Run Queue: We know mutiple processes can run at once on our device. These active processes are placed in an array called a run queue along with their priority values. (Priority is used by the task scheduler to determine which process is to run next) To ensure each process has a fair share of resources, each one is run for some time period then paused and placed back into the run queue. When a program is stopped to let another run - the program with the highest priority in the run queue is then allowed to execute.
Talking w.r.t to Android O.S and GS2 CPU, each core is given a run queue, which maintains both an active and expired array of processes. The scheduler selects the next process from the active array with highest priority. When a process' time period expires, it is placed into the expired array with some priority. When the active array contains no more processes, the scheduler swaps the active and expired arrays.
Wall Time is the total up time of CPU. Idle Time is the total idle time of the CPU. The difference (wall time-idle time) gives you the CPU Busy Time. And load on CPU is calculated as percentage of Busy Time on Up Time. (Doesn't it make a lot of sense)
Governor doesn't scale CPU but tells the CPU driver to do so.
Sampling means to evaluate load.
Smooth scaling is also done by CPU driver, not by governor.
Switching to pegasusq will deactivate Stand Hotplug since the governor's hotpluggging logic can conflict with that.
Switching to a different governor from Stand hotplug will re-activate Stand Hotplug since you need a logic to control hotplugging.
Use scripts or SetCpu to change tunables.
Gokhanmoral modified pegasusq (originally authored by Samsung for quad core devices) in Siyah kernel to be dual core friendly.



1) sampling_rate - Measured in uS and actual meaning being Sampling Interval, this factor is used to determine how often the governor should poll for CPU usage in terms of frequency and load percentage to make scaling decisions - either scale CPU Up or scale it Down.

2) up_threshold - Measured as percentage, this is the load on CPU at which governor scales CPU Up. Lower value - early scale up, and viceversa.

3) sampling_down_factor - Acts as a mutiplier to sampling interval for re-evaluating the load when CPU is truly busy and is on highest clock frequency (policy max). Setting to 1 makes no difference and causes CPU to immediately scale down from highest frequency. Sampling down factor is not valid for lower frequencies and low load conditions. Note that CPU is scaled up to max frequency when max_load_freq is greater than up_threshold*current frequency. Max_load_freq is an arbitory frequency calculated as the maximum of load_frequencies. Load_frequency is an arbitrary frequency which describes the frequency the device theoretically needs to handle 100% load, calculated as load*average_frequency.

4) down_differential - After spending sampling_down_factor*sampling_rate micro seconds at maximum frequency on high load, governor samples the load again to calculate an approx target frequency to scale-down-to which should not trigger up_threshold in the next sample. (Triggerin up threshold may cause jumping to max frequency again). Down_differential also act as the factor which prevent agressive scale down. Max_load_freq is checked against (up_threshold - down_differential) * current frequency. If found to be smaller, CPU is scaled down to a target frequency as described above.

5) freq_step - Defines how much as a percentage of maximum frequency, governor should increase CPU frequency each time CPU load reaches up_threshold.

6) cpu_up_rate - No of samples to evaluate load to scale CPU Up. After cpu_up_rate samples are finished for a frequency, CPU scale-Up logic is executed. In other words - before scaling Up, cpu_up_rate*sampling_rate micro seconds are spend at a frequency.

7) cpu_down_rate - No of samples to evaluate load to scale CPU Down. After cpu_down_rate samples are finished for a frequency, CPU scale-Down logic is executed. In other words - before scaling Down, cpu_down_rate*sampling_rate micro seconds are spend at a frequency.

8) hotplug_freq_1_1 - Up threshold frequency to turn second core On, when some other conditions is also met. ie If (minimum frequency greater than or equal to hotplug_freq 1 1 and length of average_runque_minimum greater than hotplug_rq_1_1) Hotplug IN Second Core.

9) hotplug_freq_2_0 - Down threshold frequency to turn second core On, when some other conditions is also met. ie If (maximum frequency less than hotplug_freq 2 0 and length of average_runque__maximum less than or equal to hotplug_rq_2_0) Hotplug OUT Second Core.

10) hotplug_rq_1_1 - Threshold run queue length for second core to turn on.

11) hotplug_rq_2_0 - Threshold run queue length for second core to turn off.

12) ignore_nice_load - Setting to 1 causes governor to ignore load resulted by nice processes while making scaling decisions. Nice processes are the one i/o scheuler refers to as low priority process.

13) io_is_busy - Setting to 1 causes treating i/o wait time as CPU busy time. To imporve performance of heavy applications, set this to 1.

14) max_cpu_lock - Calculated as minimum of (its current value and number of possible cpus). If it has a non-zero value and the value is greater than no of online cores, cancels Hotplugging IN the second core. Leave it as default 0.

15) hotplug_lock - Hotplugging second core is cancelled if it's value is greater than zero. The value should be greater than value of max_cpu_lock. Leave it as 1.

16) cpu_up_freq - Calculated as minimum of (its current value and maximum frequency), this tunable is actually not used by the governor.

17) cpu_down_freq - Calculated as maximum of ( its current value and minimum frequency), this tunable is actually not used by the governor.

18) up_nr_cpus - Calculated as minimum of (its current value and num of possible cpus), this tunable is used by the governor to indirectly make Hotplugging decisions, but may not be useful for a 2 core CPU.

19) dvfs_debug - Set to 1 to enable governor logging. If you're an enthusiast, this may be useful to view the impact of the values for governor tunable set by inspecting the log.

[illuminato67]

Perchè se metto l' oc a 1500 o a 1600 si impalla sempre ??

Provo e ti faccio sapere

Inviato dal mio GT-I9100 con Tapatalk 2

[mescal67]

Io ho avuto un problema dopo aver flashato il nuovo siyah, anche se non so se dipenda da questo. Ho trovato spento il telefono e l'ho dovuto accendere togliendo e rimettendo la batteria.

Idem....come rom ho la cm9...ho rimesso il 3.2.2 in attesa di sviluppi.

[Apeiron1984]

Per la prima volta da quando ho installato ICS (più di 4 mesi fa) sono arrivato a sera senza bisogno di caricare il cell.

Siyah 3.2.3 con leggero UV e cm, 13h di accensione e 2h30 min di schermo ON, 46% di carica rimanente

Inviato dal mio GT-I9100 con Tapatalk 2