yashsingh1/xdaforums huggingface dataset:
[Nexus 5X Original Android Development] jollaman999:
Hotplugging is not needed for our bullhead.

It only increases latency and power consumption while turning on or off the each cores.

There was no effect for battery life.

It 's same or worse no better.

That's why I stopped to develope msm_hotplug and no more add it.

There was battery drain when added power efficient workqueue. So I just reverted it before.

Thank you for your idea and sorry that I can't give you cool answer.
[Nexus 5X Original Android Development] edoardotavecchio:
You explained me why I was totally wrong and that's the important thing, thanks for your explanation!
[Nexus 5X Original Android Development] :
jolla, please take a look at this commit, its for power-saving! :o
[Nexus 5X Original Android Development] buffer overflow:
Hotplugging in 2017 ? Is completely useless for our dear smartphone. None of kernel "makers" will add this gov, and this is a good thing.
[Nexus 5X Original Android Development] jugoslavpetrovic:
Well, here is the deal. The Flash kernel has it. Its disabled by default and you dont have to use it if so frustrated by it but still its there and some ppl apparently would like to use it. I have tried it but didnt really get into it so much that I could say if it makes sense. It would usually keep half of little and half of big cores together online for lite use and then turn on more by need of use I guess. So it would have like 2 little and 1 big online most of the time. Performance is fluid.
[Nexus 5X Original Android Development] buffer overflow:
I'm not "frustrated", i expressed just my opinion. :silly:
[Nexus 5X Original Android Development] jugoslavpetrovic:
Sorry, it kind of sounded like hard shelled opinion. I know there are some thoughts on that if you shut down some cores of cluster the rest of cores would pull more so there should not be some positive effect on battery drain anyway but me personally have never measured it to tell that. :silly:
[Nexus 5X Original Android Development] mr.ace:
Please search in GitHub before request a commit

https://github.com/jollaman999/jolla-kernel_bullhead/commit/9cfd5784e880d8ddb3c7ef380f96c01036b34a54
[Nexus 5X Original Android Development] :
Sorry, I really was hesitant in commenting it because I thought I saw it before in Jolla's commits. Thanks, btw.
[Nexus 5X Original Android Development] jollaman999:
Already merged. :laugh:

https://github.com/jollaman999/jolla-kernel_bullhead/commits/android-7.1.1/drivers/base/power/main.c
[Nexus 5X Original Android Development] :
Thanks! :)
[Nexus 5X Original Android Development] Javi22:
I flashed last version in Dirty Unicorns rom, but it gave me random reboots frequently, I used default settings

Edit: just found that this kernel isnt compatible yet with lastest vendor, no problem
[Nexus 5X Original Android Development] edoardotavecchio:
Is EAS actually present in this kernel? I've seen some posts months ago about it but, as I understood, it seems to be that it's been removed. Could someone give me a better explanation about this and why would have it been removed? I've already read other devs talking about it here and as I understood it would never been used for 5X kernels. Some days ago I saw that Eliminater74 included it in his nebula kernel for htc10, so I'm asking if could it be possible to be implemented for this device too. [MENTION=5996255]jollaman999[/MENTION] maybe you could give me an explanation (I'm sorry I'm not here to annoy or something similar, just giving suggestions and asking)
[Nexus 5X Original Android Development] Mrcactuseater:
From what I know, the htc10 runs the 3.18 kernel and thus much closer to the Pixel, where Google has done significantly more work. Theoretically it could be ported back, but it may take a lot of work.
[Nexus 5X Original Android Development] zurik:
So this kernel encrypted my n5x.
[Nexus 5X Original Android Development] tassos_chry:
This kernel does not force encrypt the device. Flashing stock boot image does
[Nexus 5X Original Android Development] razrlover:
Yes i would have been shocked this kernel would encrypt your device as i have flashed many times and never happened to me. Other possibilities twrp or rom issue?

I have not flashed latest build but would be very surprised to hear it was the kernel
[Nexus 5X Original Android Development] pepa 77:
Hi I also have the latest vendor and I don't have a problem in this sk great core :D

PixelRom 6.1
[Nexus 5X Original Android Development] jollaman999:
Give up for adding 1.1GHz clock...

I saw all of board dtsi files in arch/arm/boot/dts/qcom and tried so many times. And referenced related docs in Documentation/devicetree/bindings/ folder.

Also other dev's dtsi files.

It looks frequency is not supported by msm8992.

I think there is some reason why Qualcomm not added 1.1GHz between 960MHz and 1248MHz.

I did my best... I also really want 1.1GHz but still... no luck... :(

Here is the commit. Somebody help. :(

https://github.com/jollaman999/jolla-kernel_bullhead/commit/f2b434744a65ff8f7500bba983cd158acd37b051
[Nexus 5X Original Android Development] Mrcactuseater:
In comparison to the overclock commit everything looks fine, but I can't help unfortunately ? have you tried contacting other n5x developers?
[Nexus 5X Original Android Development] jollaman999:
Asked to flar2 wait for response. :)
[Nexus 5X Original Android Development] TW1ST3D1NS4N3:
[MENTION=5996255]jollaman999[/MENTION] would you consider possibly adding Maple I/O governor?
[Nexus 5X Original Android Development] jollaman999:
Sure. :cool:
[Nexus 5X Original Android Development] bobby janow:
I would swear I didn't do anything different other than auto speaker / proximity in Cataclysm settings. But I flashed 4.2 last night again and I'm now seeing mic detected and I'm getting no vibration problems. So my apologies, it is working as designed. I believe that the proximity sensor auto detect to turn on speaker phone is the problem. I also had some other issues with it on Elemental. Nice to be back in the fold.

Thanks [MENTION=5996255]jollaman999[/MENTION]
[Nexus 5X Original Android Development] jollaman999:
That's cool! :good: Thanks. :o
[Nexus 5X Original Android Development] Schrotty35:
I have install but get reboots. Whene i scroll i get wrong collors. How did work Fixed yellow screen and how can i enable this? Which kernel tweak tool is the best for all settings?

Gesendet von meinem Nexus 5X mit Tapatalk
[Nexus 5X Original Android Development] jollaman999:
There is no need to fix yellow screen. It is fixed as default.

You can use Kernel Auditor or Trickster Mod. Also default is the best.
[Nexus 5X Original Android Development] Schrotty35:
With trickster i can not set all cpu. Auditor is very good. Only the wrong colors and reboots whene i set elementary are not good. Hope you can fix this.

Gesendet von meinem Nexus 5X mit Tapatalk
[Nexus 5X Original Android Development] bobby janow:
Can you try that again please? I'm not quite understanding what you are asking. If you are using two kernel managers please disable one or uninstall it. Use kernel adiutor with nothing set on boot and reboot. Under the screen tab you should see different values than the 256 rgb across the board. If you don't like those colors then there is another thread where you can try different settings. But first things first. I've not had a reboot on this kernel yet with default settings.
[Nexus 5X Original Android Development] skulldreamz:
I've haven't had a reboot either using jolla kernel. Also i didn't realize that this was msm_hotplug and 100% agree that someone should never take someone's work and rename it as their own. Sorry, my mistake.
[Nexus 5X Original Android Development] loepen:
Thought the screen off. Touch volume control is enabled by default. I was not able to use I , while playing on google play music. Is there a trick to use it? Do I have to use a special player? Or maybe just my clumsy fingers?
[Nexus 5X Original Android Development] jollaman999:
See how to work.

http://buf.jollaman999.com/jolla-kernel_AIO-bullhead/Screen_Off_Volume_Control.mp4

If you use bluetooth headset, you should install A2DP Checker in the kernel options.
[Nexus 5X Original Android Development] loepen:
Thanks, working now for me. No idea, what I did wrong before. Besides really nice and snappy kernel. :good:
[Nexus 5X Original Android Development] jollaman999:
[bullhead-v4.3]

== Kernel ==

- Built with UBERTC gcc-6.0.0

- Fix for GCC 6.0.0

- Revert "msm_thermal: Disable core control"

- thermal: disable thermal-engine hotplug and poll instead

- power: bcl: Remove hotplug and freq-control

- Revert "ksm: check and skip page, if it is already scanned"

(It seems this makes random reboot. There was an kernel panic cause of NULL pointer dereference in KSM.)

- ksm: use the helper method to do the hlist_empty check

- mm: ksm: Optimize defaults

- msm: thermal: Quiet the threshold logs

- sovc: Remove 'mic detected' log

- proc: Applied some patches

- seccomp: cap SECCOMP_RET_ERRNO data to MAX_ERRNO

- proc: add a reschedule point in proc_readfd_common()

- lowmemorykiller: Applied some patches with rbtree optimization

- ion: Applied some patches

- fs: Applied some patches

- msm: camera: 8992: 8994: delete session if post event failed

- msm: camera: Handling openCamera timeout

- selinux: Improve avc logging

- KEYS: Applied some patches

- include/linux/poison.h: fix LIST_POISON{1,2} offset

- qcacld-2.0: Fix missed error check

- qcacld-2.0: Fix always return failure

- cpufreq: impulse: update to latest from [MENTION=3795148]neobuddy89[/MENTION]

== Recovery ==

- Built with UBERTC gcc-6.0.0

- Built with lastest omni android-6.0 TWRP sources with cm-13.0 as base.

- jolla-kernel_bullhead-v4.3 applied

- f2fs-tools: Applied dev branch patches

== AIO ==

- Update sepolicy binary
[Nexus 5X Original Android Development] westernmg:
why have you removed hotplugging?

Gesendet von meinem Nexus 5X mit Tapatalk
[Nexus 5X Original Android Development] jollaman999:
They are other hotplugging functions.

They are disturbing msm_hotplug to work properly.

Or set lower clocks even if device is not too hot.
[Nexus 5X Original Android Development] aamir123:
Link down
[Nexus 5X Original Android Development] loepen:
Link seems to be working again.
[Nexus 5X Original Android Development] jollaman999:
There was a server error at night.

Working again well. Thanks.
[Nexus 5X Original Android Development] :
Cpu Load is too high; average 50%

Edit: Dt2w work after 3 touch
[Nexus 5X Original Android Development] jokerpoker1:
Kernel for base stock, aosp, cm?

Thanks

Inviato dal mio Nexus 5X utilizzando Tapatalk
[Nexus 5X Original Android Development] loepen:
Should work on either. Flash over kernel that came with your rom.
[Nexus 5X Original Android Development] ulxerker:
its same like zen, if you hear something different its only placebo effect.
[Nexus 5X Original Android Development] TW1ST3D1NS4N3:
Actually it's not, but thanks.
[Nexus 5X Original Android Development] jollaman999:
I will add it. Thanks.

It says zen based. And it looks something different with zen.
[Nexus 5X Original Android Development] mr.ace:
What's your idea about power suspend from flash kernel??

I think flash kernel have deeper sleep than other kernel
[Nexus 5X Original Android Development] jollaman999:
Franco also merged PM patches before. Then reverted. Maybe he said there are some problems with upstream patches.
[Nexus 5X Original Android Development] mr.ace:
Oh thanks I didn't know about this

But what's problem about zen-tune 4.5 that I requested before, description show this can reduce background tasks

So results in better battery life

https://github.com/zen-kernel/zen-kernel/commit/8e64dff0ddc573d4d0832cb572fcaabc0ff48ec2
[Nexus 5X Original Android Development] jollaman999:
I don't know if this is suitable for smart phones.
[Nexus 5X Original Android Development] mr.ace:
frap ported this from zen-kernel so experience should be same on smartphones
[Nexus 5X Original Android Development] poondog:
Google originally introduced the feature to Angler/Bullhead back in a preview branch on their repo or something. Their source was public, but never made it into the shipping version. It seems like it served as experimentation as they worked on fine tuning the pixel.

I have seen a few people experiment with it since Google's original implementation for angler/bullhead. They've vastly reworked it and improved it for pixel, which it sits as default, and backporting it from the pixel would require a lot of work since the kernel differs a great deal.

Looking at the source for Nebula Kernel, its not the same implementation that we used here ever - it looks more like the pixel version, or its from somewhere else. As Mrcactuseater pointed out, the HTC 10 kernel is more similar to the Pixel kernel than the bullhead/angler kernel, making it somewhat easier (but not "easy", because HTC make their changes on top of the base without a commit history) to port. I remember one of the heads at Android's kernel team was saying on twitter how different the boosting and cpufreq of the Pixel was compared with the msm8992/4 we use.

It seems like users are starting to tune EAS to their own liking - it uses pretty simple parameters to adjust its behavior. While it may seem pretty easy to use and fun to adjust with understandable tunables, it would take a massive effort to backport this, as on our kernel the scheduler and cpufreq are quite different - EAS kinda ties them together.

I know I am not the developer of this kernel, but I thought I would clear up some of the differences for some users.

I havent tried it, but the config description suggests that the tuning do the opposite to battery life.

Its designed for desktops, where there is less of a trade-off required between power use and performance

Source and more reading: https://liquorix.net/
[Nexus 5X Original Android Development] jollaman999:
Very cool answer! :cool:

Thanks a lot! :good:
[Nexus 5X Original Android Development] mr.ace:
So when new update will be released? I can't stay on the earth for next update:victory::victory:
[Nexus 5X Original Android Development] Mrcactuseater:
Because you frequent here a lot, you of all people should know never to pester the Dev for ETA's. If you want it now, build it yourself :)
[Nexus 5X Original Android Development] mr.ace:
Not just here I sent too many commits in private message for jolla
[Nexus 5X Original Android Development] mr.ace:
Jolla is really a perfect man other people for requests say "**** you" but Jolla listen to my requests carefully

Thanks jolla

(I can not talk much about my feelings to you because I'm not too fluent in English)
[Nexus 5X Original Android Development] jollaman999:
[bullhead-v49514648]

[bullhead-v49514648]

== Kernel ==

>> Common <<

- msm_thermal: Adjust thermal limit (Jan, 2017)

(When the big cluster is turned off, the device is getting very slower.

So, limit the big cluster further and only turn off the big cluster when the deivce is very hot.

It can also reduce the big cluster's on/off cycles and increase performance.)

- Add Adreno idler and enabled by default.

- adreno_idler: Add display state awareness

- msm_adreno_tz: Add display state awareness

- PM: devfreq: Applied some patches

- Speed up console framebuffer imageblit function

- sched: Some optimization of loop and cpu choice

- Revert "mdss: LiveDisplay to kcal interface"

(It makes race condition. And LiveDisplay working well without this.)

- mdss: Change some functions to static

- mdss, sovc: Prevent race condition when turning on or off the screen after sound played

- slimbus: initial overclocking of slimbus

(It will give best audio quality for the hardware.)

- sdcardfs: Applied Google's android-3.10 changes.

- mm: Per-Process Reclaim

(It will reduce process killing and get more free memory.

Details: https://lwn.net/Articles/548072/)

- mm: process reclaim: vmpressure based process reclaim

- block: Add Maple I/O Scheduler

- block: maple: Check display state when needed

== AIO ==

- ramdisk: Set per-process reclaim parameters

- updater-script: Set selinux contexts when installing apps

== Recovery ==

- Built with lastest LineageOS/cm-14.1 sources (Android 7.1.1_r9)

- Applied lastest omni TWRP changes

- jolla-kernel_bullhead_II-v49514648 applied

== 49514648 ==

* 2.

* ABC.

* Do you like skiing?

** Thanks all! :D **
[Nexus 5X Original Android Development] Mrcactuseater:
**** yeah
[Nexus 5X Original Android Development] neth15:
[MENTION=5996255]jollaman999[/MENTION] Idk if I'm dumb or smth, but it took me like one entire week to figure out how does DT2W in your kernel works. To be 100% sure I will unlock the screen, I have to hold a finger on display for like one second and then double tap. It is not bad, don't get me wrong, but it would be nice if you included some description here/in your AROMA installer.

Otherwise, I'm absolutely in love with your kernel. Good job :)
[Nexus 5X Original Android Development] valeron94:
Out of curiosity: what's behind this new naming scheme? No v12.8?
[Nexus 5X Original Android Development] Saif Suse:
Damn!

Master will you teach me? or make a kernel for the device i use(YU Yureka)? hahahah jk

*Deep down inside i'm not jk :D *
[Nexus 5X Original Android Development] jollaman999:
That is a problem of touch wake functions.

When device is go to deep sleep it needs one more tap.

I don't know why it happens.

It happens in other devices too.

Tried to fix it in other device. But not clearly.

Thank you.
[Nexus 5X Original Android Development] jollaman999:
Guess what! :laugh:
[Nexus 5X Original Android Development] jollaman999:
Donate your phone then I will try. :D
[Nexus 5X Original Android Development] Saif Suse:
Hahahaha :laugh: the shipping and handling will cost me an iphone 7 :D
[Nexus 5X Original Android Development] jollaman999:
[49514648]

About 49 51 46 48

- 8/4 is 2

- A = 10 = 1010

- ABC?

- Ah, skiing is my favorite sport.

- Someone will hate this number.
[Nexus 5X Original Android Development] jollaman999:
:p
[Nexus 5X Original Android Development] Saif Suse:
maybe its too much to ask, but... can you share how did you manage to add all these super features? or provide any link to a beginner's guide for kernel tuning and adding f2fs support/governors/io schedulers/off screen gestures etc?
[Nexus 5X Original Android Development] jollaman999:
I can't help you like this. :confused:

But I can give you some links.

These links will help you.

https://xdaforums.com/showthread.php?t=1748297

https://xdaforums.com/showthread.php?t=1549263

https://xdaforums.com/showthread.php?t=2634271

http://xda-university.com/as-a-developer/adding-features-to-your-kernel
[Nexus 5X Original Android Development] valeron94:
I'm starting to hate it :confused:
[Nexus 5X Original Android Development] jollaman999:
http://www.asciitable.com/mobile/

Decimal to character. Then it will be the version.

I'm sorry if you did not like it. :rolleyes:
[Nexus 5X Original Android Development] :
"13.0", right? :)
[Nexus 5X Original Android Development] jollaman999:
Right. Thanks. :)
[Nexus 5X Original Android Development] Saif Suse:
Thanks a ton bro!
[Nexus 5X Original Android Development] jollaman999:
Your welcome. :)
[Nexus 5X Original Android Development] luckana:
flashed the kernel to test it but how to control it ? should i have selected the jolla kernel updater option in the aroma ? exkm doesn't read/detect any values i'm confused
[Nexus 5X Original Android Development] tassos_chry:
You probably forgot to flash SuperSu after and EXKM can't gain root permissions
[Nexus 5X Original Android Development] khanjui:
Updater is a simple app to update the kernel. You can control the kernel with EX Kernel Manager or Kernel Adiutor without any problem. What you mean with read/detect any values? I think you forgot to root.
[Nexus 5X Original Android Development] luckana:
oh, hadn't realised i didn't have root, thanks bro

Any custom settings worth checking, or leave it default
[Nexus 5X Original Android Development] jugoslavpetrovic:
What you mean personal data los? Not only app data?
[Nexus 5X Original Android Development] ulxerker:
all data and settings are gone, just like factory reset.
[Nexus 5X Original Android Development] jugoslavpetrovic:
Oh, all app data yes, but not personal on internal storage. Thanks(¬‿¬)

---------- Post added at 22:54 ---------- Previous post was at 22:49 ----------

Any advice on gzip vs lz4?
[Nexus 5X Original Android Development] tassos_chry:
Internal storage is a subdirectory of /data, so if you format /data as f2fs internal storage will be formatted too.
[Nexus 5X Original Android Development] leolawliet:
Oh my goodness.. -____-

Once you change the format of data partition, all data is lost.... INCLUDING PERSONAL DATA!! You're not getting it.. you were given a warning about data loss and you're not paying full attention. Formatting data to change the filesystem format will also wipe internal storage as well so be ready to say goodbye to your files. Data partition and internal storage are linked. If you already wiped, please don't go blaming anyone here if you didn't backup your personal data.

Don't go doing things like this if you don't understand what you are doing, unless you are willing to thoroughly read through instructions or deal with the consequences of losing precious data. There are details about this kinda stuff all around XDA.

I was almost compelled to not respond and let you go through with it so you may learn from what happens, but I'd rather not see complaints about it later. Only do this if you have a way of backing up your data.

Edit: I don't mean to come off as being harsh, you just can't expect people to spoon-feed you answer on XDA especially for something you don't understand. It can be a little nerve wrecking to suggest something that a person doesn't understand. This is why users are encouraged to read instructions before asking questions.
[Nexus 5X Original Android Development] nders:
Yep. Learnt it the hard way last week too. Back everything up to the so called internal storage, knowing it is only emulated on data partition. But seeing some people on the Internet said they will be kept safe even with changing data fs. I went on with it and lost them all. How stupid I am to believe it.
[Nexus 5X Original Android Development] leolawliet:
Research is very important :/

I also went through this thinking it wouldn't wipe my personal stuff. Boy was I wrong. But I knew it was my fault, I knew I should've done more reading beforehand. I used an older version of TWRP which didn't support f2fs BUT it showed up as a formating option when I was using the materialized theme for TWRP. I switched to Jolla Recovery and properly formatted everything, and saw that it wiped my internal storage again, it happens every time the format is changed. I'm currently using f2fs on Pure Nexus, I've not run into any issues whatsoever but it also doesn't feel very different from ext4, almost placebo IMO. I would advise others to just stick with ext4 and keep it simple, unless anyone who wants to go through with it has a whole day to themselves cuz the process takes a while depending on what you have to transfer. If you have a massive amount of photos, you're not getting it done quick. If you have a bunch of all files as well, that also slows down the process a whole lot.
[Nexus 5X Original Android Development] hilla_killa:
So f2fs is placebo people always talk about it like its magical or something. Gonna make our phones so fast, i knew was to good to be true and honestly not worth the hassle to me, thanks
[Nexus 5X Original Android Development] :
It's not a placebo. It's a fact that it 'might' make your phone faster. It varies on every device. Take a look at this: https://www.xda-developers.com/diss...s-leveraged-excellent-real-world-performance/ there's a dedicated section about f2fs there.

OEMs just dont make it as a default file system because it's still in development unlike ext4 which is already proven stable enough.