yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] neobuddy89:
Cores going online/offline depends on hotplug method used.

Cores going online/offline on TOUCH also depends on hotplug method used.

CPU-boost only controls the frequencies.So if hotplug turns on CPU3, lets say...

and hotplug boost freq is 1.1 GHz...... CPU3 will be at 1.1 GHz for 10 ms (or whatever duration set by you).

So, you need to let us know what hotplug settings you are using.

You can simply put Touch Boosted CPUs to 1, to disable touch boost.

If you guys, have better settings for profiles then we can discuss same. :good:

EDIT:

Intelliactive governor too got its own touch boost code... i.e. it boosts frequencies on touch. Just heads up.
[Nexus 5 Original Android Development] topgeardave:
I was using msm with interactive, it was too hotplug friendly for my liking so I've just decided to stick with 29th nightly as you rarely see all 4 cores coming online at max speed whilst just using general tasks on the same set up.
[Nexus 5 Original Android Development] Unb0rn:
F2FS

Hey, neobuddy89! How about adding f2fs support? It looks like there are growing amount of recoveries with f2fs migration, so maybe it's a good idea to add f2fs support to your awesome kernel? Thank you!
[Nexus 5 Original Android Development] bosna110:
Can't wait to hear from you guys on your own style of the kernel tweaks!, I'm ready to input everything
[Nexus 5 Original Android Development] unknvvn:
I am having the same issue topgeardave described (touch boosting to max freq when touched) with default settings.

However i disabled touch boost and phone still seems to be working smoothly (no stutters/lags) so I think I'll leave it disabled. It should save some battery as cpu freq mostly stays below 1ghz when touching however things(that i use) are still smooth. :good:
[Nexus 5 Original Android Development] neobuddy89:
As of last update, it is observed that frequency and hotplugging is highly sensitive to foreground/background tasks/load.

This was done by developers intentionally to make device work and perform as it should i.e. increase freq when new load is detected.

However, maxing out of frequency is not what I will agree to and there by, I am fixing issue to prevent maxing out of frequencies and sensitive hotplugging. Let's see...

About F2FS, let's see... hotplugging optimization is current target.
[Nexus 5 Original Android Development] neobuddy89:
Here is new nightly:

Chaos-Kernel_v12.0-[06-01]-[21-47]

* Input Boost and Hotplug Boost are unified to single function in CPU Boost. Added single control to enable hotplug boost to NXTweaks.

* Add option to NXTweaks to turn off load based synchronization for CPU Boost.

* Use conservative load scale for MSM Hotplug so that cores don't go online like crazy.

* Misc fixes from CAF.

Just FYI, whenever touch boosted CPUs is set to 1, touch boost is disabled.

By default, it is disabled for MSM Hotplug but enabled for Intelli Hotplug.
[Nexus 5 Original Android Development] Qret:
Hi, neobuddy89

Your latest kernel completable only with caf roms or completable with aosp roms to?
[Nexus 5 Original Android Development] neobuddy89:
Only CAF ROMs...
[Nexus 5 Original Android Development] willybarca:
there are two options for hotplug boost control, and they seem exactly the same ,
[Nexus 5 Original Android Development] gravedigger76:
Guys

I switched away from CM for a couple of weeks but right before I left there was an issue with charging off car charger. Has that been fixed?

I know there were at least two of us reporting it and my fault I didn't follow up with the last set of logs for the Dev. Had it been fixed?

( [MENTION=2180385]XtraWho[/MENTION] )

Thanks
[Nexus 5 Original Android Development] neobuddy89:
It's just repeated option by mistake. Shouldn't be issue.

Anyways, reupped - Chaos-Kernel_v12.0-[06-01]-[23-50]
[Nexus 5 Original Android Development] paychex:
You're still planning on adding back aulcard right? I liked the option to disable cores while the screen was off
[Nexus 5 Original Android Development] neobuddy89:
I have already implemented turning off all cores for intelli and msm_hotplug (so without any setting, they turn off while device is suspended), let me know if there is any other reason to get back alucard this soon.
[Nexus 5 Original Android Development] paychex:
That's pretty much it. Thanks
[Nexus 5 Original Android Development] or965:
I test your Kernel and all is good ,no more battry drain on idle that I was Experienced in other Kernels ,really good app to change the setting ,only one thing that missing to me ,ondemand governor ,I tried alot of governors and still ondemand give me the best Performance ,Meanwhile I use intelliactive .

I really Thinking to donate to you ,Thank you for do this good Kernel .

I am sorry for my bad english.
[Nexus 5 Original Android Development] topgeardave:
I'm still running the 29th nightly, after a few cycles I'm getting awesome battery life! I think I'll probably stick with this kernel forever!
[Nexus 5 Original Android Development] weihan1102:
Hi , I have a problem ,

I flashed Chaos 11.1 ,I reboot the phone, but it just totally black screen. I tried chaos 9.2 and it is working.
[Nexus 5 Original Android Development] neobuddy89:
Because you are using AOSP Based ROM.

Chaos 10+ onwards this kernel supports on CAF Based ROMs, thats why it is CAF Kernel as in topic name.

CAF Based ROMs are CM11, AOKP and all derivative ROMs which are build using CM11 source.
[Nexus 5 Original Android Development] weihan1102:
Thanks!

Sorry i didn't realized it before :laugh:
[Nexus 5 Original Android Development] fluther:
Hi all

I wonder if anyone can help me. Back on Chaos 10.2, with CM nightlies and M-releases, I used to be able to OC to 2.576GHz with no problem. However, since Chaos 11, doing so gives me a kernel panic immediately. I can go to 2.4xxGHz okay. I know the difference is tiny, but it's still annoying.

Attached is my last kmsg.

Any ideas?

https://docs.google.com/file/d/0B2Gn9NKnHvVFbHBrZEJ1Zl85YTA/edit?usp=docslist_api
[Nexus 5 Original Android Development] topgeardave:
Increase the voltage for the 2.576ghz step by 40mv
[Nexus 5 Original Android Development] fluther:
Just tried that, no dice. Kmsg below. Any other ideas?

https://docs.google.com/file/d/0B2Gn9NKnHvVFSEtqQWYydmFoMUE/edit?usp=docslist_api
[Nexus 5 Original Android Development] fluther:
Hey here's that kmsg again on Dropbox this time. Google drive has been giving me grief.

https://www.dropbox.com/s/6ccy4xg44o42ljz/chaos_last_kmsg
[Nexus 5 Original Android Development] neobuddy89:
I kept trying 2.5 GHz and no panic. The only difference in our setup is I am on latest CM11 nightly and you are on snapshot.

However, I cannot say ROM is reason for this panic.

Here is a test version for you, based on your report:

http://www.androidfilehost.com/?fid=23501681358541714

Report Back!

Others can try as well, apart from above attempt to fix.. it has:

Chaos-Kernel_v12.0-[06-03]-[21-02]

* Some optimizations for MSM Hotplug

[Reverted conservative scale implementation fix and implemented smart fix to enter fast load lane if cpu0 freq >= sync threshold freq]

* Bluetooth fixes (Needs Test)

* Morpheus mode enhancements to prevent suspend as soon as screen is off, add delay of 10 seconds to make sure device is really suspended.
[Nexus 5 Original Android Development] fluther:
No joy with this, same again: https://www.dropbox.com/s/6ccy4xg44o42ljz/chaos_last_kmsg

It stopped working when I was still on nightlies though, so it's a problem with both nightlies and Ms. Is it just my phone?
[Nexus 5 Original Android Development] oo0:
4.4.3 official OTA is out. lots of bugfixes. upgrade, whoever has any issues.
[Nexus 5 Original Android Development] topgeardave:
AFAIK kernel source for N5 isn't out yet.
[Nexus 5 Original Android Development] neobuddy89:
Tell us one thing, how do you OC/UV? Are you using any external app?
[Nexus 5 Original Android Development] fluther:
Nope, just nxtweaks. I also don't mess with voltages.
[Nexus 5 Original Android Development] topgeardave:
Latest nightly, got two random reboots straight after each other https://www.dropbox.com/s/08rkt12pbkgnxxf/kmsg.zip

I've reverted back to 29th nightly

Edit: Think it's to do with me flashing 4.4.3 radio. CM doesn't seem to like it
[Nexus 5 Original Android Development] neobuddy89:
Please update to below new nightly release:

Chaos-Kernel_v12.0-[06-04]-[03-34]

* Some optimizations for MSM Hotplug

[Reverted conservative scale implementation fix and implemented smart fix to enter fast load lane if cpu0 freq >= sync threshold freq]

* Bluetooth fixes

* Morpheus mode enhancements to prevent suspend as soon as screen is off, add delay of 10 seconds to make sure device is really suspended.

* Reduction in kernel size without feature removal.

(IN CASE if you have booting issue, make sure you are on latest recovery version)

* Misc update from CAF for regulator.
[Nexus 5 Original Android Development] fluther:
Still a panic on 2.5! All working beautifully otherwise.

Kmsg: https://www.dropbox.com/s/6ccy4xg44o42ljz/chaos_last_kmsg
[Nexus 5 Original Android Development] JLO155:
Is it possible to OC the GPU?
[Nexus 5 Original Android Development] Android 17:
It's not possible with any of the versions available now, but I've wondered if it's possible to add the capability at some point in the future? Cl3Kener's Uber kernel can apparently be OC'd up to 533 mghz. It's not necessary but having the option would be nice.
[Nexus 5 Original Android Development] topgeardave:
As RD [MENTION=4800121]Sultanxda[/MENTION] put it the other day, 533mhz makes no difference whatsoever

Hey [MENTION=3795148]neobuddy89[/MENTION] got a different reboot compared to before. Phone used to lock up for a few seconds then reboot. Now it just reboots without looking up. https://www.dropbox.com/s/cecytgphtg0vh4g/chaos_last_kmsg
[Nexus 5 Original Android Development] paychex:
No one has seen anything worthwhile doing so on any device i've had
[Nexus 5 Original Android Development] montbazon:
GPU OC is already tested by many devs ago. And they decided that's not worthy.

Very little performance gains, much more heat and battery drain comes.

Gesendet von meinem Nexus S mit Tapatalk
[Nexus 5 Original Android Development] JLO155:
What do the performance CPU/GPU governors in the NIX app do? Do they just lock the CPU & GPU at max frequency or is there more to it?
[Nexus 5 Original Android Development] montbazon:
The governor uses only max clock.

Not recommended in daily use. Mostly it's for higher scoring at benchmark.

Gesendet von meinem Nexus 7 mit Tapatalk
[Nexus 5 Original Android Development] neobuddy89:
Remove UV and check. UV seems to be not suitable.
[Nexus 5 Original Android Development] neobuddy89:
[MENTION=5776992]fluther[/MENTION]:

It is possible that hardware revision of our models might be different.

I remember same was the case with SGS2 and hence, many people had diff voltage sets.

I would like you to try below test version:

http://www.androidfilehost.com/?fid=23501681358542029

Do not touch anything under Voltage control, its disabled and currently WIP.
[Nexus 5 Original Android Development] topgeardave:
No reboots after 40 minutes of usage. But I must say when load based sync is on, the all 4 cores coming online at max freq is one thing I don't like. Turning it off seems to make it not make it hotplug at max freq.
[Nexus 5 Original Android Development] willybarca:
deleted
[Nexus 5 Original Android Development] fluther:
Ta-daaaaa! Ramps up to 2.5 perfectly. What did you do to get it to work?
[Nexus 5 Original Android Development] neobuddy89:
Tap on check voltage button and tell me if voltages you see are same as default voltages mentioned below in NXTweaks.

Load based sync is good development. It is done and implemented in msm-3.10 kernel.

However, if load-based sync doesn't suit us, I will remove all changes done for it.

(Just disabling may not be good, since changes were done in task scheduler as well for this.)

Here is another test version, with completely *removed* load based sync:

http://www.androidfilehost.com/?fid=23501681358542177

Let's get this decided if we need it or not once and for all. :)
[Nexus 5 Original Android Development] fluther:
No, the voltages range from 25-50mV lower than the defaults. Is this gotta or bad?

Also, I quite like load based sync, and I haven't seen much effect on battery life.
[Nexus 5 Original Android Development] myfluxi:
I'm not sure if you understand the nature of load based syncs. All it does is take sync_threshold as a floor sync freq and - if load is very high - give the short boost relative to policy->max. We may even reduce sync_threshold from 1.7GHz because sched takes care of everything.

Use 99% as fastlane_load and spurious onlinings of cpus is gone. Add a counter in the conditional, takes 3 lines of code. And always remember that 250ms uptime is soooooooo cheap compared to the huge advantage.

My impression is, that users have really no idea about what consumes how much energy. With the changes from the last 2 months or so, my device is extremely battery friendly and I never deactivate anything. Ever.
[Nexus 5 Original Android Development] neobuddy89:
Yes, I understand load based sync. I just didn't wanted to get into technical details here and help with user experience.

The issue we are having is when sibling core gets online, it is boosted to 2.26 GHz even after change fast_lane_load to 99.

I am aware cpuboost won't boost further sync threshold, just need to understand where did 2.265 GHz came into picture after this change.
[Nexus 5 Original Android Development] fluther:
None of these! My voltages (the defaults of your most recent test build) are 750-1055mV.

Edit: apologies, I wasn't paying attention: my voltage is pvs3.
[Nexus 5 Original Android Development] neobuddy89:
So, I think this explains your kernel panic. Our hardware is really different.

(Though I ordered and imported when Nexus 5 was released in US)
[Nexus 5 Original Android Development] fluther:
Okay, cool. So are those voltage tables set by device? How will this affect my use of Chaos in the future? Can you now incorporate the changes you made into the main nightlies?

Thanks for all your help, performance is awesome.
[Nexus 5 Original Android Development] neobuddy89:
Yes, this is a critical fix.. it will be incorporated in nightly release.
[Nexus 5 Original Android Development] fluther:
Great! I just wish I'd got my post count above ten earlier so we could've fixed it months ago!

I assume that due to the lower voltages, my device (being later, and also the world, not US, model) is very slightly more power efficient than your day-one device?

And so the original problem was overvolting, rather than undervolting?
[Nexus 5 Original Android Development] neobuddy89:
That's correct. And at 2.5GHz, it wasn't able to handle overvolt. Glad, we fixed this.

I wish to release 12.0 stable before jumping to 4.4.3.

And if time permits, even a non-CAF version 4.4.3 onwards.
[Nexus 5 Original Android Development] fluther:
I'm just glad that the phone is smart enough to shut itself down before the excess voltage fries its brains.
[Nexus 5 Original Android Development] topgeardave:
So all 4 cores are supposed to max out at 2.3ghz upon input? Even if cpu boost is set to 1 core. On interactive it's basically performance governor with idle parameters for when there's no load.

And the latest test kernel is perfect for me, no more insane 4 cores maxing out.
[Nexus 5 Original Android Development] montbazon:
I heard n5 us ver and international ver are the same without coverage bands at first release.

Could be there revision?

Gesendet von meinem Nexus S mit Tapatalk
[Nexus 5 Original Android Development] neobuddy89:
I have merged myfluxi's fast_lane_load modification to below new nightly.

Load based sync is not removed from this nightly version. Let's analyze more before we come to decision.

Chaos-Kernel_v12.0-[06-04]-[22-22]

* Critical Fix: Disabled Voltage control by default. Read caution before enabling it.

* LZ4 compression update.

* LZMA compression optimization to decompress and boot faster (since we use LZMA for smaller kernel size.)

* BFQ I/O scheduler update to v7r4. This I/O scheduler has several features ported from CFQ and claims to be faster than CFQ.
[Nexus 5 Original Android Development] topgeardave:
Wahay, no more quad core full speed mode on input! Think you've finally fixed load based sync! Kernel is working fine now :D
[Nexus 5 Original Android Development] JLO155:
*Deleted*
[Nexus 5 Original Android Development] zimlokks:
How did you guys check your voltage bin? I've tried before but would come up empty every time
[Nexus 5 Original Android Development] neobuddy89:
4.4.3 kernel sources are released, will be merged soon!! :)
[Nexus 5 Original Android Development] neobuddy89:
Check this post:

http://xdaforums.com/google-nexus-5...-chaos-8-1-app-revamped-t2551441/post53152524

Try with latest nightly.
[Nexus 5 Original Android Development] willybarca:
I can confirm the max freq problem is fixed now, I dont know what load based sync does but the phone runs extremely smooth and battery seems to be good, so everything is fine
[Nexus 5 Original Android Development] topgeardave:
/sys/module/clock_krait_8974/parameters/table_name

Open that and it should tell you your cpu bin like pvs0 which mine is
[Nexus 5 Original Android Development] neobuddy89:
Last nightly with no functional change is now stable release for Chaos 12.0.

Presenting first nightly of Chaos 13.0 with updates from hammerhead kernel source of 4.4.3:

Chaos-Kernel_v13.0-[06-05]-[06-02]

* Lots of Camera fixes (I think they refer to memory leak via camera)

* Device tree updates

* Slimport driver updates (Fix blinking issue)

* HDMI updates

* Enabled DIAG and USB_TABLET options (I am still figuring what are these used for)

* Misc minor fixes

:cowboy:

P.S. Most updates of 4.4.3 were already merged since this is a CAF kernel and we merge CAF updates daily!!
[Nexus 5 Original Android Development] topgeardave:
One question, why is this nightly much smaller than normal? It's 7mb whereas previous ones were 9mb
[Nexus 5 Original Android Development] paychex:
it's on
[Nexus 5 Original Android Development] kong:
IIRC, it’s been reduced to 7MB for the last couple nightlies :highfive:
[Nexus 5 Original Android Development] topgeardave:
Oh I've never realised haha, thanks
[Nexus 5 Original Android Development] Sultanxda:
Using LZMA compression actually increases boot time... LZMA trades off compression & decompression speed in exchange for smaller size. LZMA is only needed on devices where the kernel is too big to fit on the /boot partition. (Though the increased boot time might not be too noticeable since this is a Snapdragon 800)

http://pokecraft.first-world.info/wiki/Quick_Benchmark:_Gzip_vs_Bzip2_vs_LZMA_vs_XZ_vs_LZ4_vs_LZO

Decompression speed for LZMA was measured as ~2x slower than gzip...

Also, I've explained this in more detail here: http://xdaforums.com/showpost.php?p=47400811&postcount=11

Feel free to make any corrections if I'm wrong.
[Nexus 5 Original Android Development] neobuddy89:
Thanks for the heads up. I was talking about this commit:

https://github.com/neobuddy89/hammerhead_kernel_caf/commit/d8bab749e74ca3dc9381ba5cbe9e5e1dfd48c5ba

This tweak is already applied to LZ4, we applied to LZMA. It never hurts to use -Os for decompression.

Regarding trade off of speed, the speed we are talking about is decompression speed which seems to be very very small part of boot speed. Given that kernel features exfat and lot other features we already have larger kernel size compared to stock kernel size. So, unless LZMA really hampers boot speed, we can stick to this.

I have tried all other compression methods and they generate sizes of 10 MB (GZIP), 11 MB (LZ4) and 9 MB (LZO).

LZ4 is said to be fastest, we can use that for ZRAM compression method feature in NXTweaks where performance matters. :)
[Nexus 5 Original Android Development] omvir:
What's the blinking issue that you refer to that the slimport commits fix? Just asking to expand my knowledge.
[Nexus 5 Original Android Development] neobuddy89:
I can't test without slimport but this

https://github.com/neobuddy89/hammerhead_kernel_caf/commit/73fe7e97e94e9078059941c8611696aa160bc648

mentions fixing some instances where slimport detection fails when no external power available.
[Nexus 5 Original Android Development] myfluxi:
You are confusing things, input has nothing to do with 4 cpus coming up and cpufreq is also totally unrelated.

The fast_lane feature detects > x% load on any cpu and then onlines maximum allowed cpus (4 by default or any value the user wants). Apparently the original values of 95% load was a bit too low but 99% appears to be spot on. No spurious onlinings any more while keeping awesome latencies.

I can only speak for my own, clean implementation, not glued together msm_hotplug, cpu-boost and interactive stuff with obscure patches and settings that may ruin the experience. Better have one very good solution than a lot of junk. If you want me to backup my claims, just message me.
[Nexus 5 Original Android Development] neobuddy89:
I hope your issue is resolved by Chaos's dirty implementation with obscure patches without ruining your experience.

Hope people can keep thread clean like they want their git clean.
[Nexus 5 Original Android Development] giajp:
Best battery ever on this device with your latest nightly. Thank u [MENTION=3795148]neobuddy89[/MENTION]

Sent with my Google Nexus 5
[Nexus 5 Original Android Development] unknvvn:
I am getting system freezes with this nightly.

Must be the disabled voltage control.

With this nightly voltages at the upper end of freq gets lower voltage by default.
[Nexus 5 Original Android Development] neobuddy89:
Load stable nightly and check this path and tell us hw revision:

/sys/module/clock_krait_8974/parameters/table_name
[Nexus 5 Original Android Development] giajp:
Set the UV like the latest nightlies when u were stable... So easy mate.

Sent with my Google Nexus 5
[Nexus 5 Original Android Development] unknvvn:
That is not the question.

Question is why it was made like this in the first place.

And second one is why with CAF i need more voltage than AOSP to have a stable system.

I have a pvs 2.

/sys/module/clock_krait_8974/parameters/table_name shows:

qcom,speed1-pvs2-bin-v0
[Nexus 5 Original Android Development] zimlokks:
Just a quick suggestion [MENTION=3795148]neobuddy89[/MENTION] , would it help to actually disabled the custom voltages sliders in the NXTweaks app and just allow the voltage offset enabled meaning all voltages will be either lowered or raised, reducing the chances of random reboots and allowing everyone to use custom voltages again.
[Nexus 5 Original Android Development] neobuddy89:
I have given voltage table here:

http://xdaforums.com/showpost.php?p=53152524&postcount=2489

It is confirmed stable for pvs0 and pvs3.

Give me stable voltages up to max OC, neither much UV... nor much OC... but a stable one which gives no freezes,

I will modify table and make them default.

Anyone else with pvs2, review please.

All hardware revisions have different voltage settings, and different voltage is needed for stability of particular hardware revision. For example, pvs0 structure was unstable for pvs3.

CAF are ones with technical details of each revision and when they set they set accordingly.
[Nexus 5 Original Android Development] neobuddy89:
All sliders are set for pvs0, if you have pvs0 structure. You can set "custom" and do your thing.

For generalizing, I have to think a way out. Period.

EDIT: pvs1 not pvs0
[Nexus 5 Original Android Development] unknvvn:
These are voltages which are set automatically by the system with earlier stable nightlies:

http://imgur.com/nAIZICo

With these my phone is stable. For example 2265 is stable with 1050mv. While with latest nightly it is being set to 1025mv which causes instability.