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

[faux123]

Once all the cores are shut Intellidemand min frequency seems to be set to 702mhz for CPU0. I am assuming this is normal for this governor?

Minimum single core is set to 702mhz, this is done by design. It's called minimum performance lock. When in multi-core mode, minimum for all cores will be 384 MHz.

Sent from my Nexus 4 using Tapatalk 2

 

[Imppy]

How is 005 compared to 004?

Sent from my Nexus 4 using Tapatalk 2

 

[ceroglu]

Minimum single core is set to 702mhz, this is done by design. It's called minimum performance lock. When in multi-core mode, minimum for all cores will be 384 MHz.

Sent from my Nexus 4 using Tapatalk 2

Thanks man, that is what I thought. Awesome work for the kernel, it seems to be runing pretty good so far!

I have a question, did you have a chance to look at Optimus G kernel to compare with N4? I am curious to know why the same chip and hardware has much better battery life on Optimus G? thanks.

 

[cmikeh2]

How is 005 compared to 004?

Sent from my Nexus 4 using Tapatalk 2

Both feel extremely responsive to me. Benchmark wise the (and remember this coming from no OC to OC) I've gone from 2000 to 2300 in Geekbench.

Sent from my Nexus 4 using xda premium

 

[IAmAN00bie]

I'm loving the new kernel. Has anyone come up with some good color control settings yet?

Sent from my Nexus 4 using Tapatalk 2

 

[Imppy]

What program do you use to set UV?

Sent from my Nexus 4 using Tapatalk 2

 

[Prod1702]

I am using 200,200,255 for color with faux's app its a little more blue on the whites but it feels more like my galaxy nexus screen.

Sent from my Nexus 4 using Tapatalk 2

 

[danielsf]

Minimum single core is set to 702mhz, this is done by design. It's called minimum performance lock. When in multi-core mode, minimum for all cores will be 384 MHz.

Sent from my Nexus 4 using Tapatalk 2

May I ask if you could increase the touch boost for intellidemand to ~1ghz? As I have two nexus 4's on stock the other on 005 and running intellidemand. The stock was smoother on heavier web pages and apps when tracking your finger. After messing around, if I set the min freq to 1ghz then the smoothness difference was none existent between the two nexi even-though the stock was scaling all the way to 1.5ghz when screen was being touched. What do you think please?

 

[cmikeh2]

What program do you use to set UV?

Sent from my Nexus 4 using Tapatalk 2

I don't know about free options but Faux's own program supports undervolting to up to .1 V and it's always nice to support the dev. another option I know of is system tuner which provides a greater range of options. Regardless, use only one app for this sort of thing out you'll have problems.

Sent from my Nexus 4 using xda premium

 

[faux123]

May I ask if you could increase the touch boost for intellidemand to ~1ghz? As I have two nexus 4's on stock the other on 005 and running intellidemand. The stock was smoother on heavier web pages and apps when tracking your finger. After messing around, if I set the min freq to 1ghz then the smoothness difference was none existent between the two nexi even-though the stock was scaling all the way to 1.5ghz when screen was being touched. What do you think please?

Once I create a powerHal for intellidemand 4.0, the touch response will be better. Remember this is without project butter enhancements

Sent from my Galaxy Nexus using Tapatalk 2

 

[djkinetic]

Once I create a powerHal for intellidemand 4.0, the touch response will be better. Remember this is without project butter enhancements

Sent from my Galaxy Nexus using Tapatalk 2

Wow, the kernel is already pretty damn smooth.

 

[0.0]

the 005 kernel seems to have the color of the screen have a faded yellowish color. the screen looks somewhat washed out. i went back to the jellytime kernel, and the yellowish color disappeared. it could just be my phone. anyone else experiencing this? look in "settings" to see the color

 

[loscassapalle]

for me also in built 5, the clock speed go back to the default one after some seconds

 

[Letitflow]

the 005 kernel seems to have the color of the screen have a faded yellowish color. the screen looks somewhat washed out. i went back to the jellytime kernel, and the yellowish color disappeared. it could just be my phone. anyone else experiencing this? look in "settings" to see the color

Its not just you, i experienced exactly the same thing.

 

[Prod1702]

the 005 kernel seems to have the color of the screen have a faded yellowish color. the screen looks somewhat washed out. i went back to the jellytime kernel, and the yellowish color disappeared. it could just be my phone. anyone else experiencing this? look in "settings" to see the color

No problems here. Also you can change the colors using faux's app. This has helped with the color a lot for me.

Sent from my Xoom using Tapatalk 2

 

[faux123]

the 005 kernel seems to have the color of the screen have a faded yellowish color. the screen looks somewhat washed out. i went back to the jellytime kernel, and the yellowish color disappeared. it could just be my phone. anyone else experiencing this? look in "settings" to see the color

I didn't touch the colors
at all. That's weird.

for me also in built 5, the clock speed go back to the default one after some seconds

Its not just you, i experienced exactly the same thing.

Sent from my Nexus 4 using Tapatalk 2

 

[undercover]

Hey Faux. Quick question. Kernel (stock and custom) seems to be using 1ghz as stop over before jumping to full 1.5. What is causing this? And wouldn't less aggressive scaling at top values and no "stop over" at 1ghz perform better? I've monitored cpu for a bit, and it looks like it hardly uses anything in between 1 and 1.5 ghz. I much prefer how Sensation handles it utilising full range of the table. I'm talking about ondemand for both instances.
Any thoughts?

Sent from my Nexus 4 using Tapatalk 2

 

[faux123]

Hey Faux. Quick question. Kernel (stock and custom) seems to be using 1ghz as stop over before jumping to full 1.5. What is causing this? And wouldn't less aggressive scaling at top values and no "stop over" at 1ghz perform better? I've monitored cpu for a bit, and it looks like it hardly uses anything in between 1 and 1.5 ghz. I much prefer how Sensation handles it utilising full range of the table. I'm talking about ondemand for both instances.
Any thoughts?

Sent from my Nexus 4 using Tapatalk 2

1 word, powerHal. Project butter (aka jellybean) uses powerHal to control CPU behaviors from the ROM, but most of the implementations are crappy because they hard coded the frequency jumps and aren't flexible and/or too aggressive (in our case). Until I hack my own powerHal to replace the default one, this is normal stock behavior.

Sent from my Nexus 4 using Tapatalk 2

 

[mastibeta]

So, i definitely am not getting deep sleep with intellidemand governor, any ideas?

 

[ctfrommn]

So, i definitely am not getting deep sleep with intellidemand governor, any ideas?

Did you wipe cache/Dalvik prior to flashing? Definitely is sleeping for me.