yashsingh1/xdaforums huggingface dataset:
[Nexus 5X Original Android Development] :
? I just tought about this feature a week ago, I was looking at my device charging and wodering "is it fully charged or just 80% ? " , that's a small feature but so usefull.

But is it really linked to the kernel?

Thanks for pointing commit to milouk!!!
[Nexus 5X Original Android Development] jugoslavpetrovic:
Guys, thanks a lot for non-pulsating charging led. It looks better as constant.

Other thing I wanted to say is, as I recall I believe jolla kernel in some of latest builds if not the exactly latest, it had something like hima hotplug included as it acted like that, but I don't remember it took so much attention as maybe it was not explained or even mentioned. It was also working together with any other msm or core control, or both. And I think it was alongside with core control by default.

Hm, my suggestion here could be maybe if you [MENTION=5533673]milouk[/MENTION] manage to get aroma installer for this kernel, you might be able to make choices for hotplug and oc like also for zram and so on, I guess (I just guess here cuz I'm not developer) . So, the template could be for hima to disable other thermals, maybe set the threshold temp and so on. I just think that it might get simpler to make those as one and then just update the core, or maybe also update the choosing parts eventually if some new feature step in.

Sorry for disturbing. Have a great vacation.
[Nexus 5X Original Android Development] nirogu325:
I've just sent a PM to [MENTION=5169465]DespairFactor[/MENTION] asking for guidance regarding that charging screen function when the device is off. Pretty sure it's linked to kernel because whenever I tried another kernel the charging percentage disappeared, leaving only the animated battery icon. I stopped looking for the commit because there are dozens and dozens of pages with commits that go back several years.
[Nexus 5X Original Android Development] milouk:
First of all thanks [MENTION=3059141]nirogu325[/MENTION] for all your effort to help me with this feature. If its a kernel related feature be sure ill find it. If you have any news from [MENTION=5169465]DespairFactor[/MENTION] please do PM me.

Regarding the leds. I didnt know guys you didnt like it. I will be removing it effective immediately and if you change your mind of course i will put it back. If anyone still wants it PM me for a custom build.

Regarding the Aroma Installer. I will be honest it isnt something ive done in the Past. I will have a look at it. Though i still dont see the reason at least for OC. I mean ther kernel ships with stock clocks. Suppose someone wants OC. With Aroma installer he can pick it from there. Without Aroma Installer he will pick it from EXKM and apply on boot. I mean he isnt going to avoid setting it one way or another. Regarding Hima though it does make sense since i will run the script for him through Aroma though manipulating the script yourself makes more sense since you have better control over the tunnables. For example min_cpu_cores etc. Anyway, i will have a look at this one too.

Finally regarding the other Hotplug solution you mentioned. It could be either msm_hotplug or it could be tweaked msm_thermal. The Offline cores could be a result of a tweaked thermal solution that puts cores offline. Not sure how good this could since its dependant on temperature and not cpu load. Though very interesting observation. I will have a look at it too.

Thanks Guys!

Edit: i dont have my laptop with me but i had a look on the commits of Phasma Kernel through my phone and there are many interesting ones. (Still havent managed to find the one for the screen percentage)
[Nexus 5X Original Android Development] sagxiie:
This kernel extended the life of my bootlooped 5X. Flashed Sphinx and then BLOD AnyKernel2 patch and honestly I don't see any performance loss. I also love the latest version of UBER.Kudos to the developer
[Nexus 5X Original Android Development] nirogu325:
Yup, it works wonderfully on another unit I have with BLOD. Be sure to set the minimum frequency to 302MHz for the little cluster so you get a bit more battery with that underclock.
[Nexus 5X Original Android Development] DespairFactor:
I have checked and can't seem to locate one that actually references this, however there could be some changes that enabled it. I am wondering if my kernel still does this, if I was to update it to match AOSP right now.
[Nexus 5X Original Android Development] nirogu325:
Replied to PM. I can't seem to reproduce the feature. Maybe it's not kernel but vendor related. Last time I saw it was with the last Nougat OctOS coupled with your kernel, but something tells me that maybe the Nougat vendor had that...or it could be something else entirely.
[Nexus 5X Original Android Development] jugoslavpetrovic:
I wasn't asking for aroma, it was just as loud thinking that since seems to be different needs, no need for aroma, just I was thinking to give you an idea when you already master the kernel, you might wanna chalange yourself with aroma and to put as many possible options, lol, and with that you would then need to compile only one universal version instead of few. I don't know,maybe it would simplify the matter for you and you would learn few more tricks I suppose.

As for hima, well, I somehow have a believe that it could be useful in therms that the flashing would automatically by choice of user enable the hima with also choice of how many minimum cores and also with that proxess to disable other thermals. So, I guess it should be able to detect which root is used in order to be able to choose location path for scripts to put.

Finally, me personally do not have needs for this, just a suggestion for general flashing experience and as a tip for you if you feel like to be challenged:) as I have that feeling that you do.
[Nexus 5X Original Android Development] nirogu325:
[MENTION=5533673]milouk[/MENTION] - After testing the old vendor alone and coupled with Phasma kernel, I reached the conclusion it could be something in the Nougat ROM I was using before moving to Oreo. Moving on, nothing to see here.
[Nexus 5X Original Android Development] milouk:
My goal is to have an aroma installer sometime. Im working on how to make it happen. Of course i appreciate your feedback and suggestions.

Pff. That would be a nice feature. Pitty. Hahah
[Nexus 5X Original Android Development] jugoslavpetrovic:
Maybe it is the Assertive Display feature...
[Nexus 5X Original Android Development] milouk:
Still i dont think it a kernel related feature :/
[Nexus 5X Original Android Development] AerogamingHD:
When I flash this rom from TWRP and boot the phone up like normal its goes into a bootloops. It's only on this kernel. How do I fix?

This is how I flash

1. Flash rom

2. Gapps

3. Flash Sphinx Kernel

4. Magisk
[Nexus 5X Original Android Development] milouk:
If you flashed the OC version try this one https://androidfilehost.com/?fid=11050483647474829855 .
[Nexus 5X Original Android Development] j-a-d-z:
I'm always flashing magisk before the kernel.

My way for updating or switching kernel:

1. Flash my rom's stock "boot.img" to reset all kernel related changes back to stock

2. Flash magisk

3. Flash kernel
[Nexus 5X Original Android Development] nirogu325:
That first step is the most important step a lot of people do not do. That and clearing caches.
[Nexus 5X Original Android Development] Lughnasadh:
Yes, it is always best to flash Magisk before kernel so it makes a backup copy of your stock boot.img. However, if you have initially flashed a custom kernel which modifies the /system partition (some do), then re-flashing the stock boot.img before flashing a different custom kernel may not be enough and there still may be conflicts because of the modification of the /system partition.

The best practice from going from one custom kernel to another is to dirty flash your rom (wiping /system/cache/dalvik) and that way you can avoid any potential conflicts....imo

That being said, if you know for sure that the initial custom kernel didn't modify the /system partition in any way, then just re-flashing the stock boot.img, without wiping /system, before flashing the new custom kernel shouldn't be a problem.
[Nexus 5X Original Android Development] nirogu325:
IIRC, I've read the only one that installs modules and touches stuff in the ramdisk is EX Kernel, but I've never had to dirty flash since I got the device in 2015. Just flashing the ROM's original boot.img, then the custom kernel and lastly clearing caches. Never had any issues with stability/battery on my two units.
[Nexus 5X Original Android Development] Lughnasadh:
Actually, I don't believe ELEX modifies the /system partition on Bullhead, but I think it does on Hammerhead, if I remember correctly. I was just saying if you don't know, its good practice to do a dirty flash to avoid conflicts.

Here is the advice from flar2:

"3. Do not flash custom kernels on top of each other

Always reflash your ROM when changing kernels. Reflashing without wiping data (known as a “dirty flash”) is the best way to ensure your new kernel works properly. It is not enough to simply reflash the stock boot.img. Many kernel installers make changes to the /system partition as well, which could prevent your new kernel from working correctly. Many kernels (including most versions of ElementalX) use the existing boot.img as a base (often called the “anykernel” installation method), so it’s very important to have the kernel boot.img that came with your ROM, as this contains scripts necessary for the ROM and kernel to work correctly together. Dirty flashing before you install a new kernel will do the trick."
[Nexus 5X Original Android Development] nirogu325:
I've read developer osm0sis saying it's one of the very few kernels that touch the ramdisk and he himself recommended what I do. His post is in the franco kernel thread if you do a search there. I say it's overkill and unnecessary to dirty flash despite flar2's advice. Again, I've never had issues with stability/battery by just flashing the original boot image and clearing caches for years.

Back to topic!
[Nexus 5X Original Android Development] Lughnasadh:
Just trying to pass on some advice from flar2, that's all...nvm
[Nexus 5X Original Android Development] nirogu325:
...and I was just stating my opinion/experience, along with advice from another developer. All points are valid.
[Nexus 5X Original Android Development] milouk:
Guys, I'm back!

I have already merged July's Security patch (sorry for the delay). I'm gonna have a look if i can merge anything else before releasing Version 3.0. In any case i will make the builds by Sunday. (I haven't forgot the LED animation. I'm going to revert it too in this build)
[Nexus 5X Original Android Development] jugoslavpetrovic:
Even though I keep my thermal threshold at 40, with hima sometimes I get very hot device while multitasking after wake up. This morning exkm measured 82°C while checking email and messages, it also was updating apps from store and probably syncing stuff via wifi. Anyway I could felt it is not warm but hot so U checked and was around 80.

Voltage was stock, GlassCannon profile on, stock limits if cpu. I don't know what is causing this.
[Nexus 5X Original Android Development] milouk:
Mm, first of all i have noticed that EXKM manager is not always so accurate. For example my phone is not THAT hot...and it shows 82°C and literallly the next second it shows 64°C. Morever EXKM can display the temp of many things (sensors, cpu's etc) are you sure you have been displaying the correct temp?

Finally, especially the app updating process explains the Heat. I mean after all the heat is causes by excessive CPU usage. Background tasks + Updating Apps is a failproof way to increase the temp of your phone. (Sometimes it can happen overnight (because many apps backup data then) causing also battery drain. For example i lost 6% overnight because whatsapp tried to backup my Data. It still does back up data.) Especially now that its summer you should protect your phone from warm places / surfaces or leaving it exposed to the sun as it can me damaged.Also i have merged a commit in 3.0 that can help with the heat caused be charging overnight.
[Nexus 5X Original Android Development] :
Yeah, that's why the dev of exkm released devcheck available on xda.
[Nexus 5X Original Android Development] milouk:
Im sorry im not aware of what you said. Whatis dev check?
[Nexus 5X Original Android Development] wilq1337:
monitoring app by flar2, shows various temperatures and info about hardware

https://play.google.com/store/apps/details?id=flar2.devcheck
[Nexus 5X Original Android Development] jugoslavpetrovic:
Well, I am not sure about exact reading but I could feel the hi heating. I'm not sure if hima has something to do with it and today I turned it off and left core control to see if it will happen.

There was one thing that I also have like, even if I put minimal cores as 1 I always have at least 1 for each cluster, so 1 small and 1 big, and I guess thatnis how it supposed to be, but then I don't understand how it should behave with minimum 2 cores.
[Nexus 5X Original Android Development] nirogu325:
Have you noticed the online cores loves to stick to high frequencies therefore producing more heat? That's what happened last time I tried Hima Hotplug. How about you?
[Nexus 5X Original Android Development] jugoslavpetrovic:
Well, that would probably be the case but freqs are dynamic so not all the highest all the time. If I could control the bias or let's say ratio of cores to be turned on with some kind of priority in hima, I guess that could make sense for customized experience of performance/battery/heat. I'm not sure if hima has some kind of algorithms for that.
[Nexus 5X Original Android Development] Benik3:
I also noticed it.

Isn't it because Hima is just Hotplug, but no thermal control? So by disabling core control the phone doesn't have thermal control anymore....
[Nexus 5X Original Android Development] milouk:
Version 3.0

New Version is up!!

Version 3.0 is focused more on Security rather than features / performance / battery.

Changelog :

-Merged July's Security Patch (OPM6.171019.030.E1) - sorry for the delay-. see Notes (1)

-Patched almost all the CVEs that emerged the last month. see Notes (2)

Specifically the following CVEs have been patched:

CVE-2018-11232

CVE-2018-10940

CVE-2018-10675

-Fixed a bug while charging. see Notes (3)

-Removed LED Animation while charging.

Notes :

1) For more info on patched vulnerabilities see here : https://source.android.com/security/bulletin/2018-07-01

2) For more details see here : https://www.cvedetails.com/vulnerab...ersion_id-151689/Linux-Linux-Kernel-3.11.html

3) Specifically : When charger is online for a long time, such as 12 hour, the battery status changes from charging to full and resumes charging.

The reason is that battery is not full at the first full state. So increse charge time from 30s to 100s when battery status is

near to full. This method will reduce the number of recharging times. https://github.com/milouk/Sphinx-Kernel-Bullhead/commit/454a85b446128630ac1f30d3b2283f676aa01afe

Finally, i would like to thank everyone for your support and especially those who have donated to me. It means a lot!

Enjoy! :highfive::highfive:
[Nexus 5X Original Android Development] Lughnasadh:
Thank you! Your work and time is very much appreciated :cool:
[Nexus 5X Original Android Development] milouk:
You are very welcome my friend ?
[Nexus 5X Original Android Development] mosta00:
Hi THX for u really great job!! :good: so, i have some ramdom reboots on "1708 or 1740 Mhz" Do you have some one idea how i could solution that?
[Nexus 5X Original Android Development] :
That's just your phone that don't support these frequencies .

But you could try to set the voltage of these frequencies a bit higher.
[Nexus 5X Original Android Development] mosta00:
Im on it.. THX again !
[Nexus 5X Original Android Development] Benik3:
Thank you!

BTW is Hima settings included from version 2.9 as you mentioned earlier or we still need to add manually the script?
[Nexus 5X Original Android Development] milouk:
Your cpu might not be able to support it. I would advice as [MENTION=6657029]francos21[/MENTION] said to increase the voltage.

What do you mean "included"? It is included but it's disabled by default. You will have to run the script to enable it.
[Nexus 5X Original Android Development] jugoslavpetrovic:
Thanks for new build.

Can you advice us on particular values for hima?

What are this lines?:

echo 600 > /sys/kernel/hima_hotplug/cpu_nr_run_threshold

echo 0 > /sys/kernel/hima_hotplug/current_profile_no

echo 1500 > /sys/kernel/hima_hotplug/def_sampling_ms

echo 4 > /sys/kernel/hima_hotplug/nr_fshift

I'm trying to figure out how to using hima keeping device cooler. So I am going to try it along msm thermal to control freqs together whit hima unplugging cores, also, to try without wq_power_saving, to see how it is going...
[Nexus 5X Original Android Development] milouk:
Hey my friend!

Im not sure about all these. Im gonna have a look when i get home.

I know for a fact that Hima has 3 profiles -as far as i remember- current_profile_no indicates the profile. Im going to be detailed when i get home and have a look at the code.

Also def_sampling_ms is after how many miliseconds Hima Hotplug checks to see if the load -or other variables- has changed to adapt the cores. The less it is the quicker the adaptation but the more cpu power is consumed.

Regarding the rest im going to tell you for sure later along with the profiles names etc.
[Nexus 5X Original Android Development] Benik3:
Thanks, that's what I mean :)
[Nexus 5X Original Android Development] jugoslavpetrovic:
So far Hima plays nice along msm_thermal. Not heating as much. I understand it works fine because hotplug keeps at least 1 big core even when warmer when thermal lowers freqs. I will reset cpu statistics and run this tommorow all day on the go and post screens.

I also lowered bigs freqs to 1248, a bit modified GlassCannon profile on, also will screenshot modifications. I still experiment with sweet spot with the profile.
[Nexus 5X Original Android Development] milouk:
I had a look at the profiles. So ! Profile number 0 is "balanced" , Profile number 1 is "eco" , Profile number 2 is "Disable" . These profiles have different thresholds which means that the hotplugging behaviour would be different.
[Nexus 5X Original Android Development] Skulltec:
with which kernel management can you change settings for this kernel? I own both elx and franco's manager but i am not sure if those will work on this kernel. i want to try this one :)
[Nexus 5X Original Android Development] milouk:
Hello,

Ex Kernel Manager will work just fine! ;)
[Nexus 5X Original Android Development] Skulltec:
That was a fast reply at such time! Thanks i'm gonna try, if, it's possible with pixel rom, i believe it shouldn't be a problem at all :D
[Nexus 5X Original Android Development] milouk:
Hahahah! I dont think there is going to be an issue. In any case! We are all here to help with any issues you might face. :D
[Nexus 5X Original Android Development] Skulltec:
Yeah, only issue i could face is because i installed the july patch kernel while it seems that pixel mod still is on may. i got it booted so far..

I got the non OC version. I want a balanced/battery saving settings. i used to get around 3-4 hours SoT within a day 15-18 hours on franco kernel with battery savings settings. Do you recommend any settings i must change? The phone feels very smooth so i don't think its saving some power here :)

p.s thanks for your job. I think it's pretty neat to create a new kernel while the 5X is sadly, slowly dying. Congrats on the work :victory:
[Nexus 5X Original Android Development] milouk:
The fact that pixel rom has not yet been updated to July's security patch will only affect the "Security Patch" string in settings. Nothing else.

Regarding the battery life it highly depends on your usage, app , signal , settings etc.

Regarding recommended settings. I have suggested some in an earlier post (2.8 release post) but still! You will have to experiment a bit yourself to find that sweet spot.
[Nexus 5X Original Android Development] Skulltec:
Alright! ;) Thanks for the info you're config looks solid. Nice you've added screen shots to make it easier to follow. :good:

I am a light user my self, or well, i use my phone now and then during the day but mostly allo, spotify,chrome, and sometimes the camera :laugh:

Did some changes in the settings, which i think it best for my use. I will report later with results and user experience ;)

Ciao!
[Nexus 5X Original Android Development] jugoslavpetrovic:
Runnung profile 1 of hima, not feeling different so far.
[Nexus 5X Original Android Development] milouk:
Mm although it is very similar. The code is completly different. For me the battery life is better with 1
[Nexus 5X Original Android Development] jugoslavpetrovic:
I am getting convinced that age of the battery on my side is affecting my drain. But as for performance it does not lags.
[Nexus 5X Original Android Development] Benik3:
I just tested this and it works really well!

Hima profile 0, max big core freq: 1248 and msm_thermal active.

Phone is much cooler and what's interesting it lags less! Before I had problems with lags and overheating even with low performance game Opsu :)
[Nexus 5X Original Android Development] Punkiderma:
I read somewhere here in XDA (I think in a big thread regarding performance and throttling on th 5x, but now I can't remember sorry! I will search for it) that on our phone msm_thermal doesn't work, even of it you activate it.

Only core control works for real.

Is that correct?
[Nexus 5X Original Android Development] :
No that isn't actually correct.
[Nexus 5X Original Android Development] jugoslavpetrovic:
I don't think so. You can actually try for yourself and see frequencies are acting or limiting during heating of cpu.
[Nexus 5X Original Android Development] Lughnasadh:
I think you are referring to this thread. In the OP it does state that he believes msm_thermal has no effect on Bullhead. Not stating whether its true or not, just passing along the info... :D

https://xdaforums.com/nexus-5x/general/guide-thermal-throttle-tweaking-t3395681
[Nexus 5X Original Android Development] Benik3:
Or he mean that it has no effect on this settings, not that it doesn't work at all :)
[Nexus 5X Original Android Development] Skulltec:
Hey! [MENTION=5533673]milouk[/MENTION]

Me just reporting back as promised. :)

I have been using your kernel for a couple of days so far, it's been running without any problems on the pixel rom/mod and magisk as expected. I barely feel any difference than stock, however while the performance still rocks, the battery life is not much better than stock i think. around 3 hours SoT. Because touch boost is disabled by default in your kernel, i suppose the battery life is slightly better (also using glassfish1.2, does that even matter?).

I think franco kernel still has a better battery life however, it's performance is less smooth, probably due cpu limitations.

On your kernel right now Idle burns around 1.3-1.5%/hour, screen around 15-16% a hour. Not sure how that was/is on stock. And and all i am pleased with your work :)

I just try to figure out how to get use to other features such as high performance audio, does that work over the speakers or also 3.5mm jack port?
[Nexus 5X Original Android Development] jugoslavpetrovic:
You have excellent battery drain. Screen on 25% would be 4 hours of SOT, and you have 15-16, which is way more then great.
[Nexus 5X Original Android Development] Skulltec:
Yeah i would think so, not to mention, this phone is already more than 2 years old. I remember in the beginning stage i'd have 9-11% on screen drain/hour. i forgot those settings but also new phone, older android version, less play store crap (such as google play services which are crazy those days, Assistant etc).

Might tweak a little bit around but for now i am happy. Also not worth to go crazy on the phone, has already bootlooped once. for now i hope it'll survive till end of the year when i am planning to buy pixel 2/3 :)