[Kernel] (ver 041) Mako KK 4.4 (UV/OTG/CPU/GPU OC/Hybrid Linux 3.4+) [08-02-14]

[iamsmallpang]

I'm like a few of the others, my SoC settings can't be changed. The options can be highlighted, and on/off ticker works, but keyboard doesn't show when numbers are clicked

me too

 

[aSquard]

The numbers are a meter to display usage, why would the keyboard need to pop up in that field?

Sent from my Nexus 4 using xda app-developers app

Other people's screenshots show different numbers in those fields. One person asked what settings to use - Faux responded to use the ones from his Twitter post... That's why I'm under the impression the numbers can be changed

Mine Currently Shows (after rebooting)
C0: 103843
C1: 2625
C2: 8071
C3: 12130

Faux's Twitter shows:
C0: 682240
C1: 3236
C2: 0
C3: 21415

 

[itshotinhere]

Other people's screenshots show different numbers in those fields. One person asked what settings to use - Faux responded to use the ones from his Twitter post... That's why I'm under the impression the numbers can be changed

Mine Currently Shows (after rebooting)
C0: 103843
C1: 2625
C2: 8071
C3: 12130

Faux's Twitter shows:
C0: 682240
C1: 3236
C2: 0
C3: 21415

I believe he just meant the 'On' settings.

Sent from my Nexus 4 using xda premium

 

[Ace42]

Other people's screenshots show different numbers in those fields. One person asked what settings to use - Faux responded to use the ones from his Twitter post... That's why I'm under the impression the numbers can be changed

Mine Currently Shows (after rebooting)
C0: 103843
C1: 2625
C2: 8071
C3: 12130

Faux's Twitter shows:
C0: 682240
C1: 3236
C2: 0
C3: 21415

That's cause it's usage meter, as in it measures the activity for the C states, you do not edit those values they are autonomous.

Sent from my Nexus 4 using xda app-developers app

 

[j3di]

Search for each item along with 'Code Aurora' to get an explanation of what they are.

 

[hhyong99]

Try to reboot and see..
It works for me after reboot

 

[Caner092]

Still having crashes, tried clearing app data and uninstall then reboot and install again but cannot make it launch It gives me the crash at the "Setting proper permissions" screen.

P.S I'm using SuperSU

Still I couldn't make it work. Anyone have any idea?

 

[kishke]

First try fixing permissions in recovery.
If that doesnt help try deleting it from supersu list and launch it again.

 

[drharisis]

Do you experience high battery drainage when playing games??

 

[android88]

Do you experience high battery drainage when playing games??

That's normal.

Sent from my Nexus 4 using xda premium

 

[Caner092]

Faux announced Build 74 on twitter. It will fix my FC problem Thanks for your helps!

 

[MrPhilo]

Can already see a difference with the SOC option turned on. Would anyone explain what all 4 option do and what they effect?

Sent from my Nexus 4 using xda app-developers app

 

[mkamal23]

Should i keep all the of the SOC options on?

 

[faux123]

SOC Sleep States demystified! (Corrected for incorrect information thanks for G+ comments!)​

Often times users using many apps like CPU Spy will say post how much time their phone spent in "sleep" and thinking that "sleep" has only 1 state, unfortunately, it is WRONG. For many modern CPUs there are several C-States (sleep states), and the term "sleep" does NOT correctly describe them all.

Just like in real life, there are several stages of "sleep", the shallowest sleep is C0 State. As in real life, C0 state is very easy to wake up from with almost NO latency at all (real life will be like grogginess, so C0 is just like when you first doze off but any little distraction will instantly wake you up). The deeper the sleep, the harder it is to wake up from. It takes longer for CPU to re-initialize itself to a waking state (just like real life where once you enter REM sleep, it's very hard to wake up from it).

For most processors, C3 is the Deepest sleep state. C3 state is ALMOST like turning it off using the absolutely minimum power.

C0 - Shallowest sleep (dozing off) with instant wake up
C1 - slightly deeper sleep with slight latency when waking up
C2 - deeper sleep with longer latency when waking up
C3 - really deep sleep (like REM sleep in real life) with longest latency when waking up

My pyramid (Sensation 4G) kernel has Intellidemand Governor 2.0 (Grand daddy of the Mako's Intellidemand governor) where I disabled ALL hotplugging when screen is on (ie, both cores stays ON the WHOLE TIME) but I enabled C2 state for both processors, so even though at first you think it may draw more battery than hotplugging (turning off the core when not using), many of my users have experienced better battery life than with hotplugging (Hotplugging is VERY expensive, the act of turning cores on/off drains battery as well).

On Nexus 4 (Mako), for some reason, Qualcomm has decided to only allow for C0 state (the shallowest sleep) while idling and so the "sleep" isn't really that deep. With my FauxClock app + my kernel, I give you all the "deeper" sleep states so when idling, you phone can experience deeper sleep. There's a hardware bug for Krait processors where the secondary cores, 1~3, cannot achieve deeper sleep state independently, so hotplugging is still necessary to save power for cores 1~3 but for core 0 (and core 0 is the master CPU and it's NEVER hotplugged) being able to go into deeper sleep state will help to conserve more power.

FauxClock is designed with forward compatibility. With the newer Qualcomm Krait 600/800 series, they have fixed a few of the hardware bugs from the Krait processors, and so for those newer SOCs, you can go into deeper sleep with all cores like the like older 8x60 SOCs.

 

[djvoleur]

what's your rom and theme ? It's nice

Sent from my Nexus 7 using xda app-developers app

Rasbean...default settings

Sent from my Nexus 4 using Tapatalk 2

 

[algarblandom]

Hi Faux, with latest beta (13b11_r2) and latest fauxclock version C2 and C3 options in SOC options dont stay ON after a while with the screen off, even with "set on boot" enabled. Dunno if this is a bug or just the common behaviour.
Thanx for your great job!!

 

[Bluewall]

Awesome Faux. Thank you so much for all those knowledge you share with us. As a tech student it's simply gold.

Big thanks from Switzerland!

Envoyé depuis mon Nexus 4 avec Tapatalk

 

[TylerDurden1999]

Just lemme get this straigh. We should enable just 1 C from those 4 C's?
I enabled 1 and it wont stick. I enabled all of them and they still dont stick.
Btw, we should just turn them or or even enter a value in that line?
And i have 012 tbu kernel. Isnt it compatible with the new soc power management?

 

[Ace42]

Just lemme get this straigh. We should enable just 1 C from those 4 C's?
I enabled 1 and it wont stick. I enabled all of them and they still dont stick.
Btw, we should just turn them or or even enter a value in that line?
And i have 012 tbu kernel. Isnt it compatible with the new soc power management?

Should work with the 13 beta.

Sent from my Nexus 4 using xda app-developers app

 

[TylerDurden1999]

It sticked after i cleared Data but still no1 knows if we should leave all the C on, or just 1 of them?