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

[bullhead_II-v2.1]

== Kernel ==

>> Common <<

- mdss: Fix wrong EXPORT_SYMBOL

>> M <<

- Revert "msm: mdss: trigger frame timeout when recovery is in progress"

(This makes timeout error sometimes when turning on the screen.)

== Recovery ==

- jolla-kernel_bullhead_II-v2.1 applied

[bullhead_II-v2.0]

== Kernel ==

- Faster and smooth performance, Increase battery life time

>> Common <<

- Linux 3.10.101

- msm_hotplug: Fix some bugs and disable by default

(In several test, we don't need hotplugging for our bullhead and recent devices.

It shows faster and smooth performance with long battery's life time without hotplugging.)

- arp: Applied lastest Linux Kernel master's branch changes

- arp_project applied (ARP Spoofing Attack Protecting Project. Will update continuously.)

- arp_project: Ignore reply when request not proceeded or sip is differ with requested tip

- kcal: Add yellow screen fix option

- f2fs: Applied lastest stable branch's changes

- sched: Applied default values in kernel side

- bullhead_defconfig: Add missed conservative governor

- sound: Use franco's sound control driver

- mdss: fb: enable backlight dimmer

- fingerprint: Do sched boost when fingerprint sensor touched

- PM / devfreq: Applied some msm-3.10 changes

- others: Applied some msm-3.10 changes

- Applied some fixes from CyanogenMod/android_kernel_nextbit_msm8992

>> M <<

- Applied marshmallow-mr2 changes

- wlan: Applied N Preview 3's wlan driver

- sdcardfs support

- Applied some changes from N Preview 3

>> N <<

- Applied N Preview 3's changes

== AIO ==

- updater-script: Add missing init.d support when sovc_auto_off_delay value changed

- bullhead: Fix max_comp_streams not get applied

- ramdisk: init.bullhead.rc: Do not turn off/on msm_hotplug (Disabled by default)

- Add kcal_fix_yellow on/off option

- f2fs: Update f2fs-tools

- ramdisk: Add devfreq tweaks from franco

== Recovery ==

- jolla-kernel_bullhead_II-v2.0 applied

※ TWRP Attention ※

- Decryption failed with N (Do 'fastboot format userdata')
[Nexus 5X Original Android Development] djibril13:
Can I flash N preview as secondary ROM or it works only if I have N as main ?
[Nexus 5X Original Android Development] XMoDuLeSx:
Epic update Thanks :)
[Nexus 5X Original Android Development] jollaman999:
Someone said it is possible.

1. Install N as main.

2. Finish booting and setting.

3. Swap or copy main to secondary.

4. Install rom what you want to main. (Do system data cache wipe first.)

Store your M's vendor image and N's vendor image to your device.

If you want to boot main M rom, flash M's vendor image in recovery. (There is a option at top of install screen.)

Flash N's vendor image when you want boot secondary N rom.

You can't upgrade with ota when factory image is copied to secondary.
[Nexus 5X Original Android Development] HesThatGuy:
Thanks for the update [MENTION=5996255]jollaman999[/MENTION] I'm flashing it now and will update you on how well it performs.
[Nexus 5X Original Android Development] XMoDuLeSx:
I cant get the recovery boot At N preview
[Nexus 5X Original Android Development] bostonirishguy13:
Is there a way to flash a vendor.img to a secondary rom? I see the option under the install button, but believe that's for the primary. I don't see the option to flash an .img file when in multirom/secondary rom, just "flash zip."
[Nexus 5X Original Android Development] Topse:
Secondary ROM use vendor from primary ROM .
[Nexus 5X Original Android Development] sireangelus:
Can we have a more detailed changelog?
[Nexus 5X Original Android Development] gorilla p:
It looked pretty detailed to me.
[Nexus 5X Original Android Development] jollaman999:
[MENTION=889200]bostonirishguy13[/MENTION]

Do 'fastboot format userdata' in command
[Nexus 5X Original Android Development] bobby janow:
I don't know what you're doing but this kernel runs the best for me on my device. Nothing negative to the other 3 out there but this is just by far the best in performance and battery. Everyone has their own usage so this is my experience alone. Thanks.
[Nexus 5X Original Android Development] jollaman999:
Thank you very much.

This kernel has msm_hotplug, adaptive for big and little. So it will increase battery life.
[Nexus 5X Original Android Development] westernmg:
I wonder why there is no core-hotplugging out of the box on our device., really missed it.

Just flashed this kernel and gonna test how its working over the next days.

Why there are apps installed together with the kernel, i did not select anything in the aroma installer.

Also the apps are installed as not-freezable systemapps, had to kill them with Titanium.

Would be nice if you could make the apps optional.
[Nexus 5X Original Android Development] jollaman999:
It seem some of arm64 based devices have no hotplugging.

My friend's device (Note 5) also has no hotplugging.

Also thanks for your advice.

I will modify scripts in next version. Thank you.
[Nexus 5X Original Android Development] gleggie:
Is there a way to disable sweep to wake and double tap to wake? I don't use them and would like to save a little extra battery.
[Nexus 5X Original Android Development] bobby janow:
It's not enabled for me. How did you enable it?
[Nexus 5X Original Android Development] gleggie:
It was enabled by default somehow, but after a reboot it seemed to go away
[Nexus 5X Original Android Development] jollaman999:
When you play music, Screen Off Volume Control and doubletap2wake is temporary enabled by default.

It will disabled after music stopped.

So it will not eat battery when device is suspended.

If you don't want to use this feature please patch the file in [Screen_Off_Volume_Control_Off] folder.

[MENTION=2659927]bobby janow[/MENTION] You can enable it by kernel control apps. (Kernel Auditor, Trickster Mod, etc)
[Nexus 5X Original Android Development] skulldreamz:
[MENTION=5996255]jollaman999[/MENTION] could you please elaborate on how to patch the file, thanks
[Nexus 5X Original Android Development] iamterence:
I'm with Bobby. For some reason Jolla seems to run best on my phone. I don't do a whole lot on my phone, just normal texting and web surfing with the main major social media apps (Facebook, Twitter, Instagram, etc.) but battery and performance seems to be optimal. I'll give Franco kernel some time to settle and get the kinks out, but for now this is my main kernel. Good job, mate.
[Nexus 5X Original Android Development] skulldreamz:
If anyone is interested...

#!/system/bin/sh

echo 0 > /sys/android_touch/scroff_volctr
[Nexus 5X Original Android Development] jollaman999:
To turn off SOVC features. Patch this file in recovery.

http://buf.jollaman999.com/jolla-kernel_AIO-bullhead/Screen_Off_Volume_Control_Off/jolla-kernel_Screen_Off_Volume_Control_Off.zip

To restore SOVC features. Patch this file in recovery.

http://buf.jollaman999.com/jolla-kernel_AIO-bullhead/Screen_Off_Volume_Control_Off/jolla-kernel_Screen_Off_Volume_Control_Restore.zip
[Nexus 5X Original Android Development] skulldreamz:
[MENTION=5996255]jollaman999[/MENTION] quick question, twrp is up to 2.8.7.2 so i was curious as to why your using 2.8.7.0 still. I'm not implying that you should be on 2.8.7.2 as I'm sure you have a good reason for it and as I've only compiled cwm a while ago I'm just trying to learn and gather as much facts and knowledge as i can as I'm getting ready to compile my first kernel for our N5X and want to be as prepared as possible, thanks my dude
[Nexus 5X Original Android Development] jollaman999:
It seems 2.8.7.2 out. But I can't find new source.

There is only 2.8.7.0 in omni and Teamwin Project.

Edit: Sorry, it seems TWRP is up to 2.8.7.2 but recovery says 2.8.7.0.

There will be a new version of TWRP in next version. Thanks.
[Nexus 5X Original Android Development] bobby janow:
I don't have custom recovery, although I do flash it when needed for kernels and mods, so I do like the terminal commands for this. However, in the "restore" patch when extracted doesn't show any commands like the "turn off" one does. Is that my ignorance or is something missing?
[Nexus 5X Original Android Development] skulldreamz:
In the turn_off.sh (shell script) there has to be a place to put the file which is in system/etc/init.d so the system can recognize it and also execute it on reboots. The restore.sh is just doing that (restoring the system as if you never had flashed the turn_off.sh) so it doesn't need a place in /system anywhere because the shell script is just being removed. The script to restore that feature is nested in the update-binary and that's why you don't see anything in a folder because again a script is being removed from system.
[Nexus 5X Original Android Development] bobby janow:
Ok, bear with me here. So the terminal script you posted that actually changes the sys file and the zip file jollaman posted creates a file in init.d folder executed on boot right? If I just wanted to turn it back on in terminal it would be this right?

#!/system/bin/sh

echo 1 > /sys/android_touch/scroff_volctr
[Nexus 5X Original Android Development] toma62:
Thank you so much for your work

, may I ask that the Roma be 13.0 cm Jolla and fix that can be downloaded from its website,

a variant of the CyanogenMod Build?
[Nexus 5X Original Android Development] sireangelus:
He released a 2.1; what changed from 2.0?
[Nexus 5X Original Android Development] rachanta:
Let the great man do his work. Demanding info is easy, looking up:

https://github.com/jollaman999/jolla-kernel_bullhead/commits/cm-13.0

is easier.
[Nexus 5X Original Android Development] jollaman999:
Reverted one of commit because there was a problem sometimes while turning on the screen.

I didn't noticed cause of very little change. Sorry about this. I'll add this change to change log.
[Nexus 5X Original Android Development] keemagray:
headphone volume issues inside.

headphone volume issues inside.

franco driver ?
[Nexus 5X Original Android Development] jollaman999:
Yes, what is the problem?
[Nexus 5X Original Android Development] sireangelus:
Ty say for being pedantic.

Edit : latest release makes the phone run hot even with screen off and idle. Did not happen with 2.0 gonna revert to it.
[Nexus 5X Original Android Development] jollaman999:
True?
[Nexus 5X Original Android Development] sireangelus:
Nope I like to post bugs just so to make the developer crazy looking for a bug that isn't there. (sarcastic)
[Nexus 5X Original Android Development] HesThatGuy:
Update from yesterday's release. [MENTION=5996255]jollaman999[/MENTION] v2.0 is really nice. I've ran with jgcaap's CM13 build and it has been really great :)

Side note: Would it be possible for you to add a part in the setup process of the kernel to choose our i/o scheduler and read-ahead cache?

Thanks again for making an awesome kernel man :laugh:
[Nexus 5X Original Android Development] jollaman999:
Shut up.
[Nexus 5X Original Android Development] rachanta:
[MENTION=4409964]sireangelus[/MENTION] please be courteous and respectful to developers
[Nexus 5X Original Android Development] sireangelus:
I repay being illogical with being illogical, and the phone in my task was overheating doing nothing.
[Nexus 5X Original Android Development] rachanta:
Jolla was just reconfirming I'd say. He is the most active of all bullhead kernel developers and highly skilled. he deserves indulgence and encouragement.
[Nexus 5X Original Android Development] keemagray:
There are problems with headphone gain.

is not displayed kernel adiuter sound setting.

I cannot set the volume is headphone gain.

Volume is very small
[Nexus 5X Original Android Development] Topse:
You know the game, make a logfile.

Or test it on a different ROM

I test 2.1 tomorrow.

With 2.0 no problems
[Nexus 5X Original Android Development] sireangelus:
Cm13... No problems with any other kernel.
[Nexus 5X Original Android Development] gorilla p:
2.1 is working fine on latest purenexus
[Nexus 5X Original Android Development] Topse:
All good with 2.1.

Screw'd Android.

No heating for now. Tested with antutu and YouTube.
[Nexus 5X Original Android Development] jollaman999:
If you look like the screen shot, you can control with volume gain.

Is it not working?
[Nexus 5X Original Android Development] keemagray:
The item of "headphone gain" is not found.

There was it in a former 1.0 version.
[Nexus 5X Original Android Development] XMoDuLeSx:
No problems here guys :cool:
[Nexus 5X Original Android Development] jollaman999:
Because it uses other driver. Other name, same feature.
[Nexus 5X Original Android Development] keemagray:
my device is CM13, Viper4Android, Dolby+.

why headphone gain only none?

But I am satisfied with other functions.

I check a cause. Thanks!!
[Nexus 5X Original Android Development] jollaman999:
[bullhead_II-v2.2]

== Kernel ==

>> Common <<

- wlan: qcacld-2.0: Use caf driver (LA.BF64.1.2.2-05240-8x94.0)

and applied patches from CyanogenMod/android_kernel_nextbit_msm8992

(No more disconnection issue.)

- bullhead_defconfig: Disable SCHED_FREQ_INPUT

(It seems this makes fingerprint recognizing time extremly slow. So disable it.)

- Revert "bullhead_defconfig: disable NF_TARGET_REJECT_SKERR"

>> M <<

- netfilter: IDLETIMER: fix lockdep warning (from N)

== Recovery ==

- jolla-kernel_bullhead_II-v2.2 applied

※ TWRP Attention ※

- Decryption failed with N (Do 'fastboot format userdata')
[Nexus 5X Original Android Development] Razorless:
What changes does this kernel do regarding thermal management? What do msm_hotplug support and improved thermal engine do exaclty?

On elemental/franco kernel there is an option called core control that only affects the hotplug temp of the big cluster. Another setting, msm_thermal, has no effect. This is because [MENTION=4684315]flar2[/MENTION] doesn't want to edit system settings with a kernel and decided that the thermal-engine-8992.conf in system/etc should do the management. As a result, all other settings, like throttling temp of CPU/GPU/screen can be changed in the thermal-engine.

So I was wondering how this kernel handles the thermals and if the thermal-engine tweaks are compatible with this.
[Nexus 5X Original Android Development] jollaman999:
My source is based on flar2's msm_thermal and it uses core control and freq control.

Core control only handles big cores and freq control handles all of cores.

Stock's msm_thermal drop the freq of cores to the minimum clock. So I just fixed this problem and drop only 3 steps from max freq.

My kernel not use thermal daemon (thermal-engine from Android platform).

This daemon also handles big cores.

With this daemon, there will be duplicated hot-plugging with msm_thermal.

So, I just disabled it.
[Nexus 5X Original Android Development] XMoDuLeSx:
That's why we can reach hight benchmark scores?
[Nexus 5X Original Android Development] Razorless:
Alright, thanks for clarification. So that means that editing the thermal-engine will not work with jolla kernel.
[Nexus 5X Original Android Development] jollaman999:
Yes, it will slightly better than stock.
[Nexus 5X Original Android Development] jollaman999:
You are right :fingers-crossed:
[Nexus 5X Original Android Development] mykenyc:
As far as N and TWRP you can use an earlier version of TWRP and it just won't mount /data afterwards you can sideload the kernel since it doesn't need /data
[Nexus 5X Original Android Development] HesThatGuy:
Hello [MENTION=5996255]jollaman999[/MENTION] is there any way I can tweak the thermal settings you have applied to your kernel? I would like to try [MENTION=1138056]Razorless[/MENTION]' thermal tweaks but I don't know what files to edit for your kernel.

Thank you in advance!
[Nexus 5X Original Android Development] jollaman999:
My kernel not use thermal daemon. Only use built-in kernel's thermal driver.

You can adjust thermal settings with Kernel Adiutor.

There will be no effect with editing the thermal config files.
[Nexus 5X Original Android Development] HesThatGuy:
Is there any way for me to tweak the built-in kernel driver's settings? I'm trying to edit them outside of Kernel Adiutor because I am not rooted. Thanks for the quick replies man.
[Nexus 5X Original Android Development] jollaman999:
No ways without root. Sorry.
[Nexus 5X Original Android Development] Daandofreak:
Your kernel is awesome. I was looking for a kernel like render kernel nexus 6 and found your kernel. Really great kernel, keep up the great work.
[Nexus 5X Original Android Development] HesThatGuy:
Alright thanks again for the quick responses [MENTION=5996255]jollaman999[/MENTION]
[Nexus 5X Original Android Development] Topse:
Can i use 2.2 with N4?

Did not work.

Getting reboots.
[Nexus 5X Original Android Development] HesThatGuy:
Yes v2.2 will work with Dev Preview 4.
[Nexus 5X Original Android Development] jollaman999:
[bullhead_II-v2.3]

== Kernel ==

>> Common <<

- Built with Linaro GCC 5.3.1

- Linux 3.10.102

- touchscreen: dt2w: Fix wrong unregister in dt2w_doubletap2wake_tmp_dump

(Fix the issue for user who are using bluetooth device with both sovc and dt2w are enabled.)

- touchscreen, wcd9330: Also check mic state for dt2w and s2w

(Fix the issue that makes unexpected touch work while using a phone call when dt2w or s2w is enabled.)

- touchscreen: synaptics: Cancel delayed touch_off_work when screen turned on

(Fix the issue that touchscreen not working sometimes after screen turned on.)

- arp: Ignore request when gateway update attempt detected from other hardware address

(Prevent ARP Spoofing from fake request ARP packets.)

- sched: Set sched_upmigrate_min_nice to 9

- sched: avoid unnecessary HMP scheduler stat re-accounting

- sched: fix incorrect wait time and wait count statistics

- sched: Provide a wake up API without sending freq notifications

- cpufreq: interactive: Use wake_up_process_no_notif to wake up tasks

- Fix memset warnings

- compiler.h: add support for malloc attribute

- soc: qcom: rpm: Change driver memory allocation to use GFP_NOFS

- ARM: dts: msm: Enable POPP for MSM8992

- arm/dts: Fix GPU bwmon on msm8992

- msm: kgsl: Applied some patches from CyanogenMod/android_kernel_nextbit_msm8992

- arm64: Applied some patches from CyanogenMod/android_kernel_nextbit_msm8992

- lpm, cpuidle, spm: Applied some patches from CyanogenMod/android_kernel_nextbit_msm8992

- qos: Disable irq notifier when qos request is removed

- net: Send only BIND and LISTEN events

- Revert "timer: Queue timers on least power cpu"

- CPU hotplug, smp: flush any pending IPI callbacks before CPU offline

- irq_work: Remove BUG_ON in irq_work_run()

>> N <<

- wlan: qcacld-2.0: Back to N's default driver

== AIO ==

- multirom: Re-built with Linaro GCC 5.3.1

- f2fs-tools: Applied lastest dev branch patches and built with Linaro GCC 5.3.1

- ramdisk: init.bullhead.rc: Enable retention idle state

== Recovery ==

- Re-built with Linaro GCC 5.3.1 and cm-13.0 lastest sources

- jolla-kernel_bullhead_II-v2.3 applied

※ TWRP Attention ※

- Decryption failed with N (Do 'fastboot format userdata')
[Nexus 5X Original Android Development] jollaman999:
I'll update when 4's sources are opened. Thanks.
[Nexus 5X Original Android Development] HesThatGuy:
That's odd because v2.0 boots just fine on Dev Preview 4, I'm on it right now. I figured a newer version definitely would have been compatible.
[Nexus 5X Original Android Development] Topse:
I don't know.

2.2 works nice .

Smooth and fast.

Next time I look .

Reboot.

Than I play 5 minutes coc.

Reboot.

Now I m back on N kernel no problems.
[Nexus 5X Original Android Development] HesThatGuy:
That sounds more like a rogue app problem then a kernel problem. I've never had any spontaneous reboots with any of the custom kernels I've flashed on this 5X. I would advise that you look through your apps and make sure that one of them isn't having compatibility issues with the Dev Preview. :good:
[Nexus 5X Original Android Development] Topse:
No change in my Setup.

3 days with stock kernel no problems.

No problem for me. I wait for the new kernel, and test again.
[Nexus 5X Original Android Development] sireangelus:
Jolla kernel is very largy for me on the n4dp. I don't have such problems with racer.
[Nexus 5X Original Android Development] HesThatGuy:
By largy did you mean to type laggy?

Also can you try to be more descriptive of your problem? Just saying that something is laggy isn't really going to help [MENTION=5996255]jollaman999[/MENTION] find out if there are problems with his kernel. :good:
[Nexus 5X Original Android Development] sireangelus:
The phone hangs regularly especially when woke up from dozing. You can see basic ui reacting but the phone is just stuck. Scrolling with the same ex manager profile is painful, stutters and stops.
[Nexus 5X Original Android Development] roofrider:
It's not exactly meant for DP4 use yet.
[Nexus 5X Original Android Development] Topse:
I have the same with stock kernel (Tupac N4 DP ).

After some days of use.
[Nexus 5X Original Android Development] jollaman999:
No problems here with v2.3 in DP4. I'll test more.

Edit: It seems there are some problems with GPU driver. (So laggy.) I'll check the problems.

Edit2: Can't figure out the problems. We will wait for the next stable release. (Also tested with racer's kernel. Same result.)
[Nexus 5X Original Android Development] sireangelus:
Well if you did not had stuff like whatsapp. Or facebook. Or Instagram. Or xda labs. Or photo or drive or Google now. Than what you suggest could be possible. But you must realize how the phone might have stuff to work on Even with the screen off, stuff you don't know it's doing yet necessary. It's the whole point of dozing. And if you are talking about actual phone usage across a day, most recent phone reviews find how 3h and half of screen on time are a representation of good battery life. To me they are out of their mind but, can't have everything from life.
[Nexus 5X Original Android Development] sireangelus:
The last sentence was meant for the reviewers from sites. Any phone with a scree on time under the 7 hours to me should receive 3/10
[Nexus 5X Original Android Development] gorilla p:
I agree. So many people expect a rom or kernel to work magic, but people have to configure their devices properly if they want optimal battery life.

Check out the optimal battery life document on bit.ly/makostuff. Theres a lot of good info on there.

---------- Post added at 05:20 PM ---------- Previous post was at 05:08 PM ----------
[Nexus 5X Original Android Development] jollaman999:
[bullhead_II-v3.0]

== Kernel ==

>> Common <<

- cpuidle: Back to original driver (It makes battery drain.)

- Revert "gpiolib: add IRQF_ONESHOT flag for shared IRQ"

(It makes touchscreen driver not working properly sometimes when sovc is enabled.)

- arm64: Revert unneeded some changes

- arm64: Applied jump label changes

- wlan: Applied some patches from CyanogenMod/android_kernel_nextbit_msm8992

- cpufreq: impulse: Use wake_up_process_no_notif to wake up tasks

- sync: Permit out-of order sync users

- qos: Register irq notify after adding the qos request

- qos: wake up cores based on the qos updated cpu mask

>> M <<

- wlan: qcacld-2.0: Applied some changes from CyanogenMod/android_kernel_nextbit_msm8992

>> N <<

- Applied N Preview 4 changes

== AIO ==

- init.bullhead.rc: Properly set max_comp_streams of zram

- Revert "ramdisk: init.bullhead.rc: Enable retention idle state"

== Recovery ==

- Applied lastest TWRP patches from omni android-6.0

- jolla-kernel_bullhead_II-v3.0 applied

※ TWRP Attention ※

- Decryption failed with N (Do 'fastboot format userdata')