[KERNEL][GPL][N4] franco.Kernel - r217

[whittikins]

Yes, you should. Ondemand should work fine and I tweaked it a little bit so it should feel as nicely as interactive does. I can't do much more without the phone anyway, sucks to work remotely, but I'm glad everyone seems satisfied by the kernel so far, can't wait for the actual device to be available!!

I haven't had a chance to try your kernel yet, but I wanted to point out what I think is a big issue on stock kernel. I've had the phone a couple days and noticed very fast battery drain while the screen is on. Definitely faster than my galaxy nexus experienced. I then noticed the phone is using 1.5 GHz step pretty aggressively even when I'm just using gmail, reddit, and tapatalk. I've attached a screenshot of it when I've only been doing light tasks like this.

I also noticed that input boost seems to be enabled and locking to the highest clock speed the whole time for 1 core and another core stays between 1 GHz and 1.5 GHz until you release the touch input. I think this is destroying battery, especially for those of us using swipe typing.

Sent from my Nexus 4 using Tapatalk 2

 

[ChongoDroid]

Smartreflex doesn't work like that. It just calibrates the chip internals to use less voltage while maintaining the stability. Its just like doing UV with your favorite app, but it just does it by itself during boot.

I dunno if we can use AVS in here, but I remember thats what mach-msm arch used a while ago on msm7x30 and msm8x25 (if I remember correctly).

Thank you, so in theory a higher min CPU speed won't really effect battery life as the device still gets into deep sleep. (Actually goes to sleep faster if I remember.) I'm gonna play with 486mhz min for a while and see what its like for battery life.

Sent from my One X using Tapatalk 2

 

[kabauterman]

the Stock Kernel clocks the CPU while screen on from 1026 to 1512 all the lower steps are not used.

with ondemand now from build 5 the CPU clocks lower some times but most of the Time it is still over 1 GHz.

I don't understand why the CPU burns so much energy because I think not all 4 Cores are active but the Phone sometimes realy burns..

 

[whittikins]

the Stock Kernel clocks the CPU while screen on from 1026 to 1512 all the lower steps are not used.

with ondemand now from build 5 the CPU clocks lower some times but most of the Time it is still over 1 GHz.

I don't understand why the CPU burns so much energy because I think not all 4 Cores are active but the Phone sometimes realy burns..

That's not what I'm seeing at all in system tuner. I see the CPU idle down to 384 megahertz.

Sent from my Nexus 4 using Tapatalk 2

 

[kn100]

Performance monitoring!


Running build 2:
Quadrant : 4663

Sunspider : 1445
AOSP Browser


Running build 5:
Quadrant : 5000 / (Ran again due to update happening in background) 5188
Sunspider : 1421
AOSP Browser

 

[Testraindrop]

I haven't had a chance to try your kernel yet, but I wanted to point out what I think is a big issue on stock kernel. I've had the phone a couple days and noticed very fast battery drain while the screen is on. Definitely faster than my galaxy nexus experienced. I then noticed the phone is using 1.5 GHz step pretty aggressively even when I'm just using gmail, reddit, and tapatalk. I've attached a screenshot of it when I've only been doing light tasks like this.

I also noticed that input boost seems to be enabled and locking to the highest clock speed the whole time for 1 core and another core stays between 1 GHz and 1.5 GHz until you release the touch input. I think this is destroying battery, especially for those of us using swipe typing.

Sent from my Nexus 4 using Tapatalk 2

Wow thats some useless energy waste

I can only say that my Galaxy S2 is mostly at lowest level (200Mhz) and on touch input is stays on 500Mhz of 1200Mz max. and on only one core.

Those Krait cores should be way faster than what the S2 has, so 2 cores only for touch input and max frequency on one of those is only wasting battery...

Smell some extreme battery improvement there

 

[exadeci]

Just got build 5 out. The only difference for build 4 is that I added the fsync toggle thingy:

Fsync:

echo 1 > /sys/module/sync/parameters/fsync_enabled - to enable

echo 0 > /sys/module/sync/parameters/fsync_enabled - to disable

If you disable fsync your data integrity will suffer, specially if theres a power cut, it might corrupt. In its counterpart it boosts IO performance by lots.

Nice !! Could you create a small changelog on the first post so we know what you change/add (so we don't have to look at all your posts and you won't need to repeat it
PS: Btw in fsync_enabled there was a N does it works with Y/N too ?

 

[kabauterman]

That's not what I'm seeing at all in system tuner. I see the CPU idle down to 384 megahertz.

Sent from my Nexus 4 using Tapatalk 2

I my case 384 is just used while loading.

If screen on 1026 to 1512

if screen of without loading just deepsleep

all between 384 and 1026 is not used at default with stock kernel here (no CPU changing apps)

I read out with CPU Spy Plus (no root just read states out),
because system tuner changes CPU settings why would you say It's no System tuner setting it it works for you??

if I use System Tuner the Clock jumps pretty heavy every sec no matter if I touch the screen or something else.

 

[Noobla_Khan]

Getting on 2 days here with the various iterations of franco and I think it's safe to say battery life is vastly improved over stock. Came from an SGS2 to N4 and battery life was the only thing I missed about my SGS2 but looks like that's no longer an issue.

Thanks Franco!

 

[lamlux]

Just flashed v5 over and ran Quadrant for whatever reason, scored 5266!
Antutu is 9821
Sunspider is 1900 Chrome
i'll continue testing and test battery life as well.

Last kernel I ran (I think it was 2) I had 20 hours on battery with 32% left... !! :good::good:

 

[Serious_Beans]

I hope Franco can confirm/deny this but I don't think the clockspeed of the phone matters too much for battery life, I've tried many different variations of clockspeeds on my GNex and other Android devices before it and I've never really had vast batterylife improvements lowering clock speeds. Even undervolting isn't too useful.

http://forum.xda-developers.com/showthread.php?t=1478406&highlight=undervolting.

There are more things to improve battery life rather than underclocking and undervolting. I really don't notice a difference doing either of those. Not 100% sure about this but from experience and reading random things here and there about it, don't see a reason to bother with adjusting clock speeds.


Just my 0.2c

 

[hospital349]

Getting on 2 days here with the various iterations of franco and I think it's safe to say battery life is vastly improved over stock. Came from an SGS2 to N4 and battery life was the only thing I missed about my SGS2 but looks like that's no longer an issue.

Thanks Franco!

...and that's before he even receives his device! :good:
The future's looking bright on this thread.

 

[yyz71]

I seriously can't wait till franco gets his device:good:

 

[Martin_Ro]

...and that's before he even receives his device! :good:
The future's looking bright on this thread.

Have had something strange now:
Was writing a text in Whatsapp as the screen suddenly goes black and no reaction to the power on Button. After aprox. 5 sec the power on Button worked and I was back on Lockscreen. After Unlocking I was back to Whatsapp with the message I started writing and all, so no reboot I think.


What was that ?

Have had thad Issue also yesterday but wasn't sure about that. Have had a look into logcat and kmsg but couldn't see anything in it....

 

[b4ifuru18]

What build are you running? I had this happen on build 4 and others had it happen on build 3 and 2.

Sent from my Nexus 4 using xda app-developers app

 

[IAmAN00bie]

Aside from the screen your CPU should be the biggest battery drain. Changing the CPU frequencies makes a big difference in power consumption at least compared to changing the voltages only slightly. You just won't notice the battery savings that heavily because the screen drain is far more in comparison.

Sent from my Nexus 4 using Tapatalk 2

 

[Stretlow]

Just updated Franco's app,

When I look at the freqencies it says max 1512, min 1026.... i that right?

 

[nic85]

Franco can you modify the limit C° for the thermal throttling via kernel?it's too damn low...

http://forum.xda-developers.com/showthread.php?t=2007725

 

[runningwarrior08]

Hey all just flashed test build 5, in my device info it shows franco number 4. Did he start at zero like binary lol ?
Thanks.

 

[Noobla_Khan]

Hey all just flashed test build 5, in my device info it shows franco number 4. Did he start at zero like binary lol ?
Thanks.

Sounds about right since build 4 shows #3.