KERNEL][4.2.x][4.3][4.4.x] Fancy Kernel

[imthedoctor]

quando parlate di moddare volt, vi riferite al voltaggio mpu in trickster mod ?

[CEMT96]

Ho alzato di 50 ma niente... Vabe aspetterò la 33


Inviato dal mio Galaxy Nexus usando Androidiani App

[Alkemix]

Fancy r33 out... torno a lavoro anche io, quindi..

O meglio il download per gli utenti non è ancora disponibile... io sono già al lavoro sul codice sorgente...

Penso che lo caricherà tra qualche ora...

[nexus88gm]

Ciao raga, si può avere il link dell r33? Grazie

[LuCiolla90]

Ciao raga, si può avere il link dell r33? Grazie

Mettiti su questa pagina e aggiorna ogni tanto: Index of /fancykernel
Appena esce la cartella giù r33 scarichi.

[nexus88gm]

Grazie mille

[oleksandr]

quando parlate di moddare volt, vi riferite al voltaggio mpu in trickster mod ?

Esattamente. Ma devi agire con cautela, visto che undervolt può dare vari problemi. C'è una guida qui sul forum, come si fa undervolt. Prova a cercarla

[slv96]

RILASCIATA LA r33!!!

Index of /fancykernel/r33

[oleksandr]

Appena messa su la r33 ext.. Vediamo come va, aspetto ancora il changelog da boype

@Alkemix, amico ti devo fare i miei complimenti, l'ho provato per 2 giorni e devo dire che mi ha dato grandi soddisfazioni! Continua cosi! Quando avrai qualcosa di nuovo, sono sempre disponibile, con la slim girava una favola. :-)

Edit:
r32 >> r33
- updated to Linux 3.0.84
- reverted to Google GCC 4.7 toolchain (reported to be smoother than Linaro)
- optimized LPDDR RAM timings (+ ~10% throughput; check the knowledge base for more info)
- reverted a few commits from TI repo that have been responsible for unusual battery drain apparently
- increased default thermal threshold to 70°C (was 64°C in r32; was 71°C in r31 and earlier; helps with slowdowns)
- added 1344 and 1536 MHz CPU steps (above 1.2 GHz ONLY the chosen maximum overclocking frequency will be used. E.g., if you choose 1420 MHz, 1344 will not be used)
- pulled-in latest interactive governor patches from Google 3.4 kernel source
- implemented io_is_busy function into ondemandplus governor and activated it
- implemented 'timer slack' feature (This will effectively reduce the number of CPU wakeups, saving battery; check the knowledge base for background information)
- added MiHome Launcher to whitelist (com.miui.mihome2)
- few other things

[Pelide]

The surprise feature I was talking about is timer slacking. I'll post more information on this in (literally) a second. I have not tested this too much yet, but it definitly works and will hopefully save power. Thanks to Charmacas for mentioning it via PM and also thanks to Amperific for a commit that pointed me in the right direction.


What does the timer slack feature do?
Timer slacking aims to synchronize applications' and processes' CPU requests. The goal is to wake up the CPU less often in oder to save battery. What you need to know here is the following: waking the CPU up and putting it back to sleep again consumes power. Imagine that four apps wake the CPU up four times each in one second. While without timer slacking the CPU would be woken up 16 times, it is desirable to coordinate the wakeups. If done right, the CPU would wake up less often, effectively allowing power savings and longer sleep periods. This is what timer slacking does.

I have activated timer slacking only for background applications, so that everything else stays as responsive as you know it.

Apple has recently introduced this feature under the name 'timer coalescing' with their Mac OSX Maverick (link).

More information: How Apple does timer slacking ('Timer coalescing') (Scroll a little down to the diagrams)