yashsingh1/xdaforums huggingface dataset:
[Nexus 5X Original Android Development] jollaman999:
[bullhead-v9.1]

== Kernel ==

>> Common <<

- Built with UBERTC gcc 7.0.0 20160416

- msm_hotplug: Remove up/down work structure and improve big core up/down

- msm_hotplug: Reduce DEFAULT_BIG_CORE_UP_DELAY

- msm_hotplug: Merge duplicated target_big calculation

- msm_hotplug: Update copyright

- Revert "msm_hotplug: Change HZ to original value"

- lowmemorykiller: adapt to vmpressure

- lowmemorykiller: avoid false adaptive LMK triggers

- lowmemorykiller: Enable adaptive lmk by default

- lowmemorykiller: Tunning

- block: Add Zen I/O scheduler

- block: Add V(R) I/O scheduler

- block: bfq: set IOPS mode by default with slice_idle set to 0

- bullhead_defconfig: Change default io-sched to bfq

- mm: ksm, uksm: Disable by default

- f2fs: check its mapping after get page (Fixed) (Fixed kernel panic correctly.)

- f2fs: Applied lastest dev-test branch patches

- touchscreen: s2w, dt2w, sovc: Change register/unregister informations to debug codes

- touchscreen: s2w, dt2w, sovc: Update copyrights, URL and versions

- Revert power_efficient workqueue changes

- lib: lz4: fixed zram with lz4 on big endian machines

- lib: lz4: cleanup unaligned access efficiency detection

- lib/xz: add comments for the intentionally missing break statements

- lib/xz: enable all filters by default in Kconfig

- Revert "net: sched: Change HZ to 1000 of watchdog time"

- net: sched: Do "* 1000 / HZ" for watchdog_timeo

- bullhead_defconfig: Change default TCP Congestion control to CUBIC

- bullhead_defconfig: Sync wlan configs with Google

- qcacld-2.0: Revert caf wlan driver changes

- qcacld-2.0: Applied N Preview 2's wlan driver

- qcacld-2.0: Fix __queue_delayed_work warning messages

- qcacld-2.0: Disable build debug version

- qcacld-2.0: Be quiet 'first packet after WOW wakeup'

- qcacld-2.0: Be quiet PM runtime messages

- qcacld-2.0: Be quiet resume messages

- power: quickwakeup: initial driver

- msm: lpm-levels: add suspend_again handler

- power: catch wake-up requests in suspend_again

- security: selinux: Remove duplicated codes

- Revert "sched, smp: Correctly deal with nested sleeps"

- Revert "smpboot: use kmemleak_not_leak for smpboot_thread_data"

== AIO ==

- Built with UBERTC gcc 7.0.0 20160416

- f2fs: Update f2fs-tools (Applied lastest dev branch changes)

(Various tools are available: mkfs.f2fs, fsck.f2fs, dump.f2fs, defrag.f2fs, resize.f2fs, sload.f2fs)

- ramdisk: Update sepolicy binary

- multirom: Built with new cm-13.0 sources

== Recovery ==

- Built with UBERTC gcc 7.0.0 20160416

- Built with new cm-13.0 sources

- Applied lastest TWRP patches from omni android-6.0

- jolla-kernel_bullhead-v9.1 applied

※ TWRP Attention ※

- Decrytion working with MHC19J

- Decrytion failed with N
[Nexus 5X Original Android Development] Sid_Sun:
Please Tell me if the kernel has these features:

Ondemand-GPU Governor not simple_ondemand

Zen Decision-Hot PLugging Driver

InteractiveX-CPU Governor

ROW-I/O Scheduler

Thanks.
[Nexus 5X Original Android Development] j.llorente:
I only can say... the best. With 9.0 and PureNexus ROM.

Thanks for your job!
[Nexus 5X Original Android Development] jollaman999:
You can do in Multirom option.

Select your second rom in Multirom list and touch flash zip.
[Nexus 5X Original Android Development] jollaman999:
Please read the main thread.
[Nexus 5X Original Android Development] Sid_Sun:
Can't find the features please add them.
[Nexus 5X Original Android Development] j.llorente:
Can you add the ability to configure the backlight dimmer. For me is enabled (I don't know if is about your kernel or about other previous kernel). But the min brightness is often very low when there is darkness in the environment. With Nexus5 I could configure the min brightness about dimmer through kernel adiutor.

Thanks!
[Nexus 5X Original Android Development] Pollie81:
Seriously?
[Nexus 5X Original Android Development] RevUnix:
Recovery not working with N Preview 2 :(
[Nexus 5X Original Android Development] jollaman999:
You should decrypt your data partition.

Reboot to fastboot mode (bootloader).

Than type 'fastboot format userdata' in command line with fastboot tool.
[Nexus 5X Original Android Development] Sid_Sun:
Missing InteractiveX CPU Governor

Zen Decision Hot Plugging

And Also Ondemand GPU Governor
[Nexus 5X Original Android Development] roofrider:
Deal with it.
[Nexus 5X Original Android Development] gorilla p:
After latest 9.1 update, when big cores are set to conservative, I get a message stating that conservative governor settings are not tunable. It still works on LITTLE cores.

Works fine on 9.0
[Nexus 5X Original Android Development] JohnYang1997:
Well, a little suggestion, I find with your kernel the screen is somewhat bluish sometimes. And i would rather use the option in developer options. It feels more right to me to be honest.
[Nexus 5X Original Android Development] roofrider:
I think the swap/copy ROMs function isn't fully functional yet, but I haven't tested it. I have N as secondary, but what I did was install it as primary initially, take a backup of it, and then install the backup as secondary. However, when the time comes to update it to DP3, I doubt I'll be able to flash the OTA zip. Regardless, I'm gonna try updating it via the OTA zip to see what happens.
[Nexus 5X Original Android Development] gorilla p:
User Kernel Audiuter Modand it lets you select from a number of color profiles.

I prefer Obsanity AMOLED

http://xdaforums.com/android/apps-games/kernel-adiutor-mod-singularity-kernel-t3333549
[Nexus 5X Original Android Development] jollaman999:
I also annoying with it.

Cause of msm_hotplug. I always trying to solve this problem. But can't find the solution

...

Just turn off msm_hotplug while you are changing governor settings. And turn on big cores.
[Nexus 5X Original Android Development] jollaman999:
Use M's vendor for cm13 and use N's vendor for N.

I think the problem is related with selinux permission while swap/copying roms.
[Nexus 5X Original Android Development] sireangelus:
Which app should I use to change kernel settings? I just trying this one right now
[Nexus 5X Original Android Development] gorilla p:
http://xdaforums.com/showthread.php?p=66790767

---------- Post added at 04:33 PM ---------- Previous post was at 04:30 PM ----------

Thank you. Your solution worked perfectly.

Thank you for introducing msm hotplug on this device. I love it.
[Nexus 5X Original Android Development] sireangelus:
Another quick question, If I have hotplugging I can't set to have all 6 cores up at the same time. I is that an expected behavior?
[Nexus 5X Original Android Development] gorilla p:
Set min cpus online to 6.

However I have mine set to a minimum of 1 and maximum 4, with conservative governor and have little if any lag.
[Nexus 5X Original Android Development] sireangelus:
What I want to is that the have all six cores online at the same time as a maximum.
[Nexus 5X Original Android Development] jollaman999:
Turn off the msm_hotplug and turn on all of cores.
[Nexus 5X Original Android Development] jollaman999:
Now I figured out that problem.

It will working well with Kernel Adiutor.

I will release v10.0 version when I finish the tests.
[Nexus 5X Original Android Development] sireangelus:
.... Is there a way to have both? I because I've noticed how it won't scale correctly towards the big cluster sometimes even with a little core at max frequency and 100% load since it can't wake up the big cluster to migrate since the in use cores are busy. Could you provide some code change to make this happen? I I think it would go a long way towards maximum performance
[Nexus 5X Original Android Development] rachanta:
[MENTION=5996255]jollaman999[/MENTION], I tried the latest msm_hotplug from your cm-13.0 branch. Geekbench score was around 650 for single as well as multi-core operation. I've reverted to my version of your older plug, which seems to be working well with scores of 1350 / 3750 (best). I haven't taken the fingerprint and dt2w, s2w hooks.
[Nexus 5X Original Android Development] jollaman999:
Check this new commits.

https://github.com/jollaman999/jolla-kernel_bullhead/commits/msm_hotplug
[Nexus 5X Original Android Development] rachanta:
[MENTION=5996255]jollaman999[/MENTION]

Big improvement with your latest (May 17, msm_hotplug branch) commits.

What I like is that now there is no interference with your wake / sovc changes. Also I was not including those commits that modified fingerprint code from your older msm_hotplug. Now I have the whole plug the way you coded it.

First run on geekbench gave me 1200 / 3500 approx. Result from latest run 3-4 minutes after the first run is attached.

Cores are nicely switching on and off. Great work! I hope you get similar similar results in your testing. Thanks again for sharing your work.

Edit: I am still testing. After some time, I find that cores are not switching on. I am allowing phone to sleep for some time, before I check again. I'll continue to test through the day and let you know later.

Edit2: Same problem as in May 15, cm-13.0 branch msm_hotplug commits. Cores are not switching on. May be the initial results were because of some remnant effects of the older plug which was installed before I tried out the plug from May 17 msm_hotplug branch. I have to go back to older msm_hotplug. Please continue this good work that I am following keenly.
[Nexus 5X Original Android Development] Mainak_11:
Will it work on Android N prev 3 ?
[Nexus 5X Original Android Development] jollaman999:
No problem until now with my tests.

Maybe some codes are conflicted with older commits.
[Nexus 5X Original Android Development] jollaman999:
I'll release re-built version later. Keep working.

It will work with N2 with lastest version. I didn't see N3..?
[Nexus 5X Original Android Development] david.degraw54:
Preview 3 was just released yesterday at Google I/O
[Nexus 5X Original Android Development] Mainak_11:
Yeah I can confirm that the last built is working in the latest dev preview
[Nexus 5X Original Android Development] jollaman999:
[bullhead_II-v1.0]

== Kernel ==

>> Common <<

~~~~~ Intoroduce new jolla-kernel_bullhead_II !! ~~~~~

- Rebuilt with lastest Google msm sources.

- Source cleanup.

- Greatly improved battery life and fix battery drain problems.

- Not applied Linux 3.10.y upstream patches.

(It makes sense only apply some patches that we needed.)

- Replace UKSM to KSM.

- Applied some KSM upstream patches.

- Adjust default KSM values for save battery life.

- Correctly resume/suspend KSM

(KSM is enabled by default. It will stop when screen turned off and working again when screen turned on.

This can save battery life when device suspended.)

- Not applied EAS patches and use default sched with some patches.

(Device working smoother without this and it shows better performance.

Instead I applied scheduler and mm patches from franko kernel.)

- Replace f2fs's source to stable branch.

(I used dev-test branch before but it shows errors and battery drain.

No problems after changed to stable.)

- Touchscreen and display panel correctly turned off when music stopped when you using SOVC.

(Before: Display panel remained in resume state and touchscrren not turned off coreectly in some cases.

After: Now I fixed these issues and there is no more battery drain!!)

- Implement Auto Off Touchscreen for SOVC.

(When you pressing the touchscreen for a long time touchscreen will turned off.

It will prevent from wrong touchscreen working and lets you holding the device while walking.

Default value is 4 seconds and you can change this value in aroma-installer.)

- Now, you can change the governor settings for big cores with msm_hotplug working!!

(Finally, I figured out this annoying problem! Working well with Kernel Adiutor.

It will turn on first of big core when you enter the cpu/governor settings in Kernel Adiutor.

It will working normally again after 5 seconds when you exit from cpu/governor settings.)

- Remove suspend/resume works from touchscreen driver and use FB notifier for each drivers.

(There was a huge suspend/resume works in touchscreen driver.

Now suspend/resume works working separately in each drivers.)

- Improved suspend/resume works for Screen Off Volume Control, DoubleTap2Wake and Sweep2Wake.

- Fix race condition in cpu_up work.

== AIO ==

- ramdisk: Update sepolicy binary

- Add sovc_auto_off_delay setting option

- A2DPChecker: Check disconnected state for disable SOVC properly

- ramdisk: init.bullhead.rc: Set min frequency for big cores

- ramdisk: init.bullhead.rc: Turn off msm_thermal while changing governor settings

== Recovery ==

- Applied lastest TWRP patches from omni android-6.0

- jolla-kernel_bullhead_II-v1.0 applied

※ TWRP Attention ※

- Decrytion failed with N (Do 'fastboot format userdata')
[Nexus 5X Original Android Development] ashatter:
I'm flashing a AOSP based rom and the rom already has SuperSU:

1. Do i need to choose the option "use SuperSU in CM"?

2. Can I choose to use lz4 in this case?

Thanks a lot!
[MENTION=5996255]jollaman999[/MENTION]
[Nexus 5X Original Android Development] jollaman999:
1. This option is only for CM with older Super SU. Do not choose it.

2. You said you already installed Super SU. So, Yes.

Thank you, your welcome.
[Nexus 5X Original Android Development] jollaman999:
Emergency fix related with SOVC.

EDIT: Done. Sorry for my mistake..
[Nexus 5X Original Android Development] Mainak_11:
downloading the last one.... why pulled ?
[Nexus 5X Original Android Development] jollaman999:
Re-uploaded. I forgot applying last commit. Sorry for my mistake..
[Nexus 5X Original Android Development] Mainak_11:
No problem :)
[Nexus 5X Original Android Development] Pollie81:
Awesome.. thanks, I'm going to try your latest version!
[Nexus 5X Original Android Development] sireangelus:
After flashing latest update i find myself unable to power up the phone expect in recovery. i'm trying a factory reset. you guys are warned.(i was on N dp3. No problems with 1.0 first revision.

phone is stuck at google screen. not even boot animation

Edit: factory reset did the trick. Strange thing was internal storage was only 10gb instead of 20- had to do a full format by twrp to restore it to its original size.

Edit 2 working fine for now on cm13
[Nexus 5X Original Android Development] jollaman999:
If you have rebooting problem when sound played while screen turned off, please re-download the last version.
[Nexus 5X Original Android Development] Topse:
All fine with New version. No reboot.

Thanks :)
[Nexus 5X Original Android Development] Pollie81:
So far it's running fantastic, smooth and battery seems good.
[Nexus 5X Original Android Development] sireangelus:
Apart from that scare on my, my best kernel for me too so far
[Nexus 5X Original Android Development] willybarca:
since the new update one of the big core never goes offline even on idle, with 9.1 all other cores went offline accept core 1 of the little one,
[Nexus 5X Original Android Development] sireangelus:
I agree on this behavior
[Nexus 5X Original Android Development] Immortalis:
Since the new update my Wi-Fi connection keeps dropping (eg. speedtest or file downloading), regardless if I'm on 802.11ac or n. Rolled back to 9.1
[Nexus 5X Original Android Development] sireangelus:
Reverted back to old kernel version, way too much battery drain with screen off
[Nexus 5X Original Android Development] ashatter:
It seems starts from 9.1 camcorder microphone gain is not working.

I also found that VDD restriction cannot be on with temperature throttle. Is it common?
[MENTION=5996255]jollaman999[/MENTION]
[Nexus 5X Original Android Development] jollaman999:
This is just a trick.

http://xdaforums.com/showpost.php?p=66973872&postcount=530

- Now, you can change the governor settings for big cores with msm_hotplug working!!

(Finally, I figured out this annoying problem! Working well with Kernel Adiutor.

It will turn on first of big core when you enter the cpu/governor settings in Kernel Adiutor.

It will working normally again after 5 seconds when you exit from cpu/governor settings.)

You can check with Floating Monitor app or type below lines in command prompt.

adb root

adb shell watch -n 1 cat /sys/devices/system/cpu/online
[Nexus 5X Original Android Development] jollaman999:
I didn't changed related with gain settings but I'll check.

I modified msm_thermal to only working hotpluging for big cores and frequency restriction for all of cores.
[Nexus 5X Original Android Development] jollaman999:
9.1 use N's wifi driver. I'll compare with M's wifi driver and N's wifi driver.
[Nexus 5X Original Android Development] jollaman999:
Did you use default settings?

This is my battery usage.
[Nexus 5X Original Android Development] sireangelus:
I'm used to have a flatline when idling
[Nexus 5X Original Android Development] sireangelus:
The problem is not in the waking up to but in the turning off after being waked up. It should turn off the big cluster and turn up a core in the little one. Problem is, when you have a big cluster up with only one little, the scheduler uses it for low loads increasing energy consumption defeating the purpose of the whole hotplugging and hmp<br />

<br />
[Nexus 5X Original Android Development] rachanta:
[MENTION=5996255]jollaman999[/MENTION]

Finally managed to get your latest msm_hotplug and msm_thermal commits into my repo and have built a kernel which seems to be working well. Thanks again for your great work. :good::good::good:

I found that disabling thermal core control was the mistake I was making. If thermal core control is disabled, max_cpus_online gets reduced to 2, and causes all sorts of problems including Kernel Adiutor CPU section not starting up.

It may be a good idea to describe how msm_hotplug is supposed to work for the ordinary user, so that people can compare what they have with what was intended from your end. If this is already there somewhere, please point me to it. I am unclear about the intended behaviour myself.
[Nexus 5X Original Android Development] gorilla p:
I seemed to be having problems with not being able to change hotplug settings. When I did, they would work for a few minutes, then go back to their previous setting.

For example, I accidentally set max cores online=1. I fixed it and set it to max cores online=4. However, after a few minutes, it went back to 1.

Also, conservative governor appears to be missing. Is it being removed?
[Nexus 5X Original Android Development] jollaman999:
It seems settings are not applied immediately sometimes. (Tested with Kernel Adiutor).

I forgot to enable conservative in kernel config file. I'll add it in next version.
[Nexus 5X Original Android Development] rachanta:
[MENTION=5996255]jollaman999[/MENTION] there seems to some issue with the last few thermal commits:

msm_thermal: Go to interrupt mode when device suspended

msm_thermal: Change interrupt_mode_init() to disable_msm_thermal() when go to suspend state

--- and the final msm_hotplug squash.

It causes max_cpus_online to crash to 1 and kernel auditor CPU panel to get stuck while opening. Fingerprint and suspend integration into msm_hotplug needs some repair. I spent a lot of time trying various things, but no success.
[Nexus 5X Original Android Development] MrPhilo:
Is there anyway to change the charging rate? Or customise it
[Nexus 5X Original Android Development] gorilla p:
Max cores online keeps reverting to 1. Removed and reinstalled and never changed max cores. Still goes back to 1.
[Nexus 5X Original Android Development] jollaman999:
Tell me your problem in detail.
[Nexus 5X Original Android Development] jollaman999:
No way to choose manually.
[Nexus 5X Original Android Development] jollaman999:
I'll check where the problem occurs.
[Nexus 5X Original Android Development] rachanta:
[MENTION=5996255]jollaman999[/MENTION], this is the same problem I have. max_cpus_online becomes 1. Also frequency of big core becomes 864MHz after some use, which is same as qcom frequency mitigation freq. Once phone sleeps, max big core freq returns to set value. 864 MHz is also the frequency of big cores soon after boot up. It ramps up to the set max freq value, after phone sleeps for some time. I hope this info is useful to resolve the issue.
[Nexus 5X Original Android Development] jollaman999:
Your source is old and different with mine. Also there is some errors.

If you have questions, mention me in github. Not here.
[Nexus 5X Original Android Development] rachanta:
[MENTION=5996255]jollaman999[/MENTION].

I was telling the problem I had running Jolla kernel, not my own build.
[Nexus 5X Original Android Development] jollaman999:
Sorry for that.
[Nexus 5X Original Android Development] jollaman999:
Tested several times but in my test, I don't have that problem.

Could you guys tell me step by step how changed the values?
[Nexus 5X Original Android Development] XMoDuLeSx:
I'm using the multirom recovery but every time i make a backup with lockscreen set pattern after the restore it can't unlock the device even if I use the correct pattern. Is this normal or a bug?
[Nexus 5X Original Android Development] rachanta:
[MENTION=5996255]jollaman999[/MENTION]

There is no particular step that leads to the drop in max_cpus_online. I set it to 4 and exit Kernel Adiutor. When I reopen the app max_cpus_online is back to 1. Same situation if i set "Apply on boot" and reboot. Sometimes it works fine and 4 cpus are online, but it I exit and check again, it is back to 1. Sorry to say this here (and not in github as suggested by you), but exactly the same thing happens in my own build with your latest msm_hotplug source along with latest msm_thermal source.
[Nexus 5X Original Android Development] gorilla p:
That would explain the issue im having

"Causes max_cpus_online to crash to 1 in kernel adiuter".

This happened even after removing, reinstalling and not changing any settings.

Previous version doesnt seem to have this issue.
[Nexus 5X Original Android Development] jollaman999:
Got it. I'll compare with previous source. Thanks for reporting.
[Nexus 5X Original Android Development] jollaman999:
It will be normal situation.

Delete these files in screenshot in recovery mode and set your pattern again.

/data/system/
[Nexus 5X Original Android Development] gorilla p:
Do you have Core Control and VDD disabled?

I cant help but wonder of its a thermal setting gone haywire.
[Nexus 5X Original Android Development] j.llorente:
I can't change hotplug settings. Cpu settings yes, big and little I have with despair. For me the best version is old 9.0. I had 3 days battery, 3h screen and 30%. The latest is not better than 9.0. Wifi is disconnected when I don't use the phone a lot of time (cubic congestion) [MENTION=5996255]jollaman999[/MENTION]
[Nexus 5X Original Android Development] HesThatGuy:
Hello [MENTION=5996255]jollaman999[/MENTION] I really enjoy using your kernel. I wanted to know if instead of utilizing msm_hotplugging drivers you could switch to mpdecision drivers as those seem to scale better and have less problems?

Cheers!
[Nexus 5X Original Android Development] gorilla p:
Perhaps it should be an option, but the msm hotplug offers much better control and efficiency.
[Nexus 5X Original Android Development] rachanta:
[MENTION=5996255]jollaman999[/MENTION] thanks for msm_hotplug update, it's working well. Earlier problem of max_cpus_online dropping from 4 to 1 is solved. Also big core max freq doesn't drop to 864 after / during an antutu run, like it used to.

Is one big core alwsys supposed to be on?
[Nexus 5X Original Android Development] jollaman999:
Thanks for using updated source.

It looks like that while you are looking cpu settings in Kernel Audiutor.

Check this post.

http://xdaforums.com/showthread.php?p=67027979