yashsingh1/xdaforums huggingface dataset:
[Nexus 5X Original Android Development] milouk:
That makes sense i will try to make a test version tonight. Thanks for the tip
[Nexus 5X Original Android Development] dogedoge:
After more than a week of use, i have to say i am very satisfied with your kernel. It provides great idle drain and the battery life is the best as it can be while everything is smooth. The only problem i am facing, that i have faced with other different kernels too on 8.1, that when the phone is asleep and i try to unlock it via fingerprint, it takes sometimes even 2 seconds for it to vibrate, and after that firstly the background light appears and then the homescreen. But if i wake the device first with the power button and then place my finger on the reader, it works rapidly. I tried searching for a solution but couldnt find a proper one. I am on latest LOS 15.1 . This problem did not occur before rooting. Does anyone else experience this or might know a solution to it?
[Nexus 5X Original Android Development] milouk:
Im very happy you enjoy my work . I have implemented fingerprint boost driver which should wake the phone faster when unlocking with the fingerprint so what you say is a bit weird. Maybe if you try a clean install of your rom this will be fixed. And by the way im rooted with magisk and everything works fine this is why i believe that a clean install will fix the issue.
[Nexus 5X Original Android Development] dogedoge:
Thank you for your advice! I actually clean flashed the LOS, and since then dirty flashed the updates on it. I might try to clean install again, but i surely couldnt do that with every update, since it takes annoyingly much time to backup and restore everything.
[Nexus 5X Original Android Development] milouk:
https://www.androidfilehost.com/?fid=962339331458994073 here is a test version for default clocks following [MENTION=6998415]mr.ace[/MENTION] 's advice.
[Nexus 5X Original Android Development] Lughnasadh:
Thanks for the test build. Just flashed it but not allowing me to boot. Just boots back into bootloader. Flashed back to v 2.5 and boots fine.

Logs attached. They were taken after flashing the latest test version and then v. 2.5.
[Nexus 5X Original Android Development] milouk:
A million sorry. My fault copied wrong image. I will be uploading a correct zip in 5'
[Nexus 5X Original Android Development] Lughnasadh:
Lol. No problem :)
[Nexus 5X Original Android Development] milouk:
https://www.androidfilehost.com/?fid=962339331458994073 here you are :fingers-crossed::fingers-crossed:...and dont forget to wipe cache ;)
[Nexus 5X Original Android Development] Lughnasadh:
:cyclops:

On initial flash and boot little core is set at 1440 and big core at 1824 :good: . However, for me at least, it was a seemingly random thing, as I mentioned earlier. Most of the time after a reboot it would be at 1824, but sometimes at 2016. So, for me at least, I'll have to run it a day or two to make sure it sticks.

Others may get conclusive results before me.
[Nexus 5X Original Android Development] milouk:
Yep i understand. According to the changes i made You should not get 2016 at any case.
[Nexus 5X Original Android Development] jugoslavpetrovic:
Test build. First I got 1632 at bigs, and then later when cooled it showed 2016 at bigs. Of course wiped both caches via twrp. I am confused. I mean, I can set as to apply after boot but...
[Nexus 5X Original Android Development] milouk:
The only thing i changed is what mr.ace said which i think too was correct. Im going though to release another test build tomorrow. If that does not work im out of ides. As i said though frequencies are hard to control in Nexus 5X. ElementalX kernel has also issuss handling frequncies.
[Nexus 5X Original Android Development] jugoslavpetrovic:
I understand. What kernel manager do you suggest?
[Nexus 5X Original Android Development] milouk:
Im using EX Kernel Manager but i dont think this is going to change anything. Also i just noticed that ex kernel manager has a note that frequencies are controlled by system processes and thus may not persist.
[Nexus 5X Original Android Development] jugoslavpetrovic:
Ok. With Nexus 5 it very possible but I remember racer kernel for 5X was as well OC and it seems like if added possibility for OC that it will not keep default clocks for some reason. Interesting enough, other tester [MENTION=6530865]Lughnasadh[/MENTION] claims it sticks at stock freq but not on my side. I'm not complaining or anything just trying to figure out and help to dig into it.
[Nexus 5X Original Android Development] milouk:
Since you got the issue mainly i was thinking the scenario that some of your settings are messing up the big cores frequencies. Maybe the fact that you set the thermal throttling threshold at 42? While i and probably the rest of users keep it at 46 .
[Nexus 5X Original Android Development] jugoslavpetrovic:
Well, if that is the point I will remove the script and try.

And I just saw even smalls get to 1632 occasionally. Checked with EXKM and Aduitor. Hmm...

I'm going to remove all changes and reboot, wipe caches and will see
[Nexus 5X Original Android Development] Lughnasadh:
I believe at boot both cores will overclock for just a tiny amount of time until the frequencies are set (in kernels that allow overclocking). I ignore these and usually clear both frequency charts in EX Kernel Manager after the phone cools. Then later on I check the frequencies to see if they've gone above what either the kernel or I have set. In almost every scenario they don't. I think discounting what happens at boot gives a more accurate scenario of what is going on.

Of course, the above is kind of unrelated to our discussion of what the kernel actually sets as the maximum frequency. Just talking about right at boot time when all the values may not have been set yet, if this makes sense.
[Nexus 5X Original Android Development] jugoslavpetrovic:
Now I got 864Mhz on bigs, it does not goes over. And on smalls default.
[Nexus 5X Original Android Development] milouk:
That is completly normal due to the throttling just wait 10 minutes for the phone to cool off or temporarily increase the threshold to something big like 80 just to see the max freq
[Nexus 5X Original Android Development] Lughnasadh:
Yeah, I let the CPU temp to cool down to 36 C or so before checking anything because of thermal throttling.

That is, when thermal throttling is set at 46.
[Nexus 5X Original Android Development] jugoslavpetrovic:
Well...

Temp around 39°C

Thermal threshold at 46
[Nexus 5X Original Android Development] milouk:
Im going to make another test version tomorrow.
[Nexus 5X Original Android Development] Lughnasadh:
Well, bad news. Just did a nandroid and when I rebooted (after cooling down), big core max frequency was set at 2016.
[Nexus 5X Original Android Development] milouk:
I will make another test version later in the day
[Nexus 5X Original Android Development] jugoslavpetrovic:
I am still not sure if it's possible, so maybe for the sake of ppl who would like stock clocks you could build stock clock versions but I also believe it is the chalange for you to make it as what you are trying to make, lol.

So, maybe until that happens you could push some stock clock build:) if that is not much trouble and effort. Just an idea.
[Nexus 5X Original Android Development] milouk:
I can do that. I will release some OCed and a test version
[Nexus 5X Original Android Development] jugoslavpetrovic:
Oh, I meant non-OCed, lol
[Nexus 5X Original Android Development] milouk:
Yeah sorry my mistake. I will release 2 non OCed and a test version
[Nexus 5X Original Android Development] jugoslavpetrovic:
Cool, thanks.
[Nexus 5X Original Android Development] milouk:
https://www.androidfilehost.com/?fid=746163614322266758 this is the final test version. if this fails then im making separate non OCed versions
[Nexus 5X Original Android Development] jugoslavpetrovic:
Damn, you are so fast :)
[Nexus 5X Original Android Development] milouk:
And i already got the non OCed versions ready to be released ;)
[Nexus 5X Original Android Development] jugoslavpetrovic:
Flashed now. I am leaving now for work. If no one else confirm before I will inform later today. Thanks
[Nexus 5X Original Android Development] jugoslavpetrovic:
Well, all default
[Nexus 5X Original Android Development] milouk:
Just uploaded two non OCed versions. Enjoy
[Nexus 5X Original Android Development] milouk:
By the way are you using any Governor Profiles because that might be the reason your big cluster clocks are messed up. I changed my profile to KestrelOC and noticed that the big core clocks changed to 2016 so i was wondering if you use any profiles
[Nexus 5X Original Android Development] Lughnasadh:
Thanks for this. I will test today as well :good:

---------- Post added at 09:42 AM ---------- Previous post was at 08:57 AM ----------

Sorry to report, but after dirty flashing my rom (wiping dalvik/cache/system) and flashing the latest test version, Big cluster max frequency was set to 2016. Little cluster was fine at 1440. I am not using any profiles, thermal throttling hacks or the like.

Despite this, I don't think this is necessarily a bad thing. Many people do like the option to overclock, which this still allows (personally I only overclock the little cluster to 1536 and leave the big cluster alone for fear of the BLOD).

A suggestion:

If you still want to have an overclocked version you can just set the defaults as they were earlier (1632 & 2016). Then users, through any kernel manager, can set the frequencies to their desires if they don't like the 1632 & 2016. However, I do understand that many users would just want stock frequency values and would prefer not having to set frequencies with a kernel manager. This, of course, would mean having an overclocked version and a non-overclocked version.

As this is your personal kernel that you are kindly sharing with us, that would mean 2 different versions (actually 3 if you count the 3.10.73 version)(I personally prefer 3.10.108) and that may indeed turn this "fun" into a "chore".

But of course you may also get the big core frequency worked out (it is indeed strange that the little core sets fine but not the big). Anyway, just thought I'd throw some ideas out.

Whatever you choose to do, remember, keep it fun. If anything becomes a hassle, don't do it, imo. :)
[Nexus 5X Original Android Development] milouk:
Thanks for the test. Actually there are 4 versions 2 x 3.10.73 and 2 x 3.10.108 and i have already updated the OP to include non OCed versions. Thanks again for the feedback and sorry for the hassle
[Nexus 5X Original Android Development] Lughnasadh:
No hassle whatsoever :good::)
[Nexus 5X Original Android Development] jugoslavpetrovic:
I totally agree with this.

I like my device cooler, and keeping thermal at 44 or 42 which is not really much under 46 and mostly I am fine with it. And of course not only the cooler but also kind of precaution of BLOD which happened to rachanta developer of racer kernel which was playing with some thermals and OC. Not saying that this was the cause but, you know, this device is so gentle about it anyway and came that way from the factory.

Me too, using the 3.10.108.
[Nexus 5X Original Android Development] :
Why you don't do an aroma installer instead of creating lots of versions because if you continue like this you will become crazy when it will comes to include security patches in each version.

Not a critic, just a tip.

Have a nice day / or a good night (depending of your time zone lol)
[Nexus 5X Original Android Development] milouk:
The main issue here is that frequencies for the big cluster do not stick. Having an aroma installer wont change this. Either you pick the prefered freqs from the aroma installer or you just pick them from any kernel manager app and set them on boot its the same. Im not sure if you are following my sceptic. What i want is the kernel to have as default clocks the stock frequencies. Which will not happen in an OCed kernel either the user picks the default freqs from aroma installer either via a kernel manager app. And by the way i currently live in Denmark so good night :p
[Nexus 5X Original Android Development] :
But elementalx kernel is oc with an aroma installer who ask for oc or not, but I'm sure ,as you are saying, that I don't catch what you want but I'm sure that you know what you are doing.
[Nexus 5X Original Android Development] milouk:
ElementalX asks for the user to set his prefered frequency but that does not gurantee it will persist. For example if i set big cores at 1824 (stock values) theu might indeed be at 1824 or in some rare cases might be 2016 even though you picked 1824 because frequencies are managed by system processes. The only way to ensure that the max freq of the big clusters wont go above 1824 is to NOT OC your kernel. So it is inevitable not to have 2 versions one OCed and one non OCed.

Conclusively the aroma installer will just give you the chance to pick in advance settings. But wont change the fact they might not persist. So in my case there is no need for an aroma installer. I hope i made it a bit clearer for you
[Nexus 5X Original Android Development] jugoslavpetrovic:
Not sure about that. When I was using ElementalX kernel I always used stock freqs for both and I don't remember ever getting over it.

But I agree with you that if you don't find the way to control it would not matter of whatever you choose there. So, I guess if you get to the bottom of the case you can then get for Aroma:)

I had different issue with that aroma, whatever I have chosen for IO scheduler always ended up with noop, but that wasn't so much big of deal as the core.

Hm, maybe [MENTION=4684315]flar2[/MENTION] would be kind to point to right direction or advice on this matter.
[Nexus 5X Original Android Development] milouk:
Announcement

Ahoy ladies and gentlemen,

i have an announcement to make.

As of version 2.6 (which will come by the end of the month) i will be no longer using Google's Toolchain BUT i will be using UBER Toolchain which is much more efficient.

For those of you who do not know or heard about UBER Toolchain see here details https://plus.google.com/+ChetKener/posts/YzMJEkzPQgp .

For those who are bored to open the link UBER is based on latest gnu.org changes and patched with aosp and linaro android patches for optimal performance/battery.

Cheers.
[Nexus 5X Original Android Development] jugoslavpetrovic:
I remember some uber kernel for N5. It was kind of not very fluid and soft but very snappy and kind of how to say, harsh. Don't remember the battery but performing fast.
[Nexus 5X Original Android Development] milouk:
Im currently testing v2.5 compiled with UBER and i promise you its buttery smooth, fast and im totally blown away to be honest. Otherwise i would not change it ;) but you ll have to try it to say. If you want a sneak peak pm me.
[Nexus 5X Original Android Development] jugoslavpetrovic:
I can tell you like chalanges. It's a good learning path and is good for improvements.
[Nexus 5X Original Android Development] eurochild:
Private uber tc build is just awesome, keep up the good work my friend [MENTION=5533673]milouk[/MENTION]
[Nexus 5X Original Android Development] milouk:
Ahoy,

-Enabled KSM

-Support UKSM

-Now Compiling with UBER Toolchain 4.9.4

Notes:

1) I stopped building 3.10.73 versions because almost no one wanted them so if anyone still wants it PM.

2) I will be building two versions from now on 3.10.108 with OC and 3.10.108 without OC.

3) For those who don't know what KSM or UKSM are click here https://www.quora.com/What-is-Kernel-samepage-merging-in-Android (UKSM is Ultra KSM).

4)For those bored to click on 3 , KSM is a very good feature for low ram mobile phone that efficiently balances battery/performance. In other words More Ram for a small trade of CPU power.

Enjoy
[Nexus 5X Original Android Development] Lughnasadh:
Thanks for the update. Much appreciated :good: .

I flashed the OC version but it doesn't appear I can set the cores to actually OC. The highest listing in the little core is 1440 and in the big core is 1824. I flashed the non-OC just in case they were accidentally reversed but same thing.
[Nexus 5X Original Android Development] milouk:
Yeah sorry my mistake. Building right now. Should be up in 10'
[Nexus 5X Original Android Development] Lughnasadh:
No problem :good:

Thanks
[Nexus 5X Original Android Development] milouk:
Everything fine. Build is up
[Nexus 5X Original Android Development] Lughnasadh:
Awesome. That was quick. Thanks again...
[Nexus 5X Original Android Development] Lughnasadh:
Smooth as silk :cool:
[Nexus 5X Original Android Development] zurik:
Good kernel but it is messed up with frequencues of BIG.little clusters on OCed version. What values is by default that you set?
[Nexus 5X Original Android Development] milouk:
As i have said before and it is stated in EXKM too under the CPU tab. Frequencies are managed by system processes and thus cannot be handled easily. The default i have set is 1440 Mhz for Little and 1824 Mhz for Big. Though this sometimes works and some not due to a variety of reasons (throttling , cpu governors, system processes etc.) If you Do NOT want OC you can flash the non OC version , otherwise set on Boot your prefered freqs and they should persist.

Morever, if you unzip the flashable zip in ramdisk>sphinx.rc you can see the config for default values.

Also could you be more specific about the frequencies being messed up?
[Nexus 5X Original Android Development] zurik:
May you add the ElementalX governor?
[Nexus 5X Original Android Development] milouk:
As i have already said before too. I don't want to add any more governors. Since there are so many profiles in EXKM to choose from i dont see the point.
[Nexus 5X Original Android Development] jugoslavpetrovic:
Can we add specific parameters to sphinx.rc and zip it back?
[Nexus 5X Original Android Development] milouk:
Im not sure if this is going to work or not. Though if you download the Anykernel2 folder

You can use this command to zip it up "zip -r9 Sphinx-3.10.108.zip * " and zip it
[Nexus 5X Original Android Development] jugoslavpetrovic:
Oh, I thought simple editing file and putting it back should work, as it was presented in for racer kernel.
[Nexus 5X Original Android Development] milouk:
This wont work.
[Nexus 5X Original Android Development] kalashnikov6468:
Where is the file ?
[Samsung Galaxy S7 Edge Questions and Answers] bonegang:
Had the same experience, with the phone hanging on bootup and the same message in the recovery screen.

... so I went the factory reset route .... painful, but I could find no option to recover.

I see that there is an entry in the recovery menu for a firmware update from the SD card; can anyone suggest how that can be done? (In case there's a next time).
[Samsung Galaxy S7 Edge Questions and Answers] Abo_Moaaz:
Did I can to flash without HomeCSC

Because I am in different country????
[Samsung Galaxy S7 Edge Questions and Answers] shah22:
I flashed via odin, then did factory reset, but the message is still there, but phone works fine and smooth , but with occasional reboots and a strange high cell standby drain. My phone never rebooted even once on marshmallow and nougat.

You have to flash either CSC or home csc, home csc won't wipe your data, but I will recommend flashing normal csc and then factory reset and clear cache too, as to avoid any issues like bootloops etc.
[Samsung Galaxy S7 Edge Questions and Answers] MisterX01X:
How did you flashed on SM-G935FD? Since so far it's only available for SM-G935F and SM-G930F.
[Samsung Galaxy S7 Edge Questions and Answers] shah22:
I flashed through odin, the firmware is same for dual sim models , hence G935F firmware works on G935FD too, just be sure that model number is correct, i.e not to flash a G935FD with a G930F firmware or flashing a snapdragon variant with exynos or vice versa.

But now the btu oreo update have been pulled back from the OTA server, due to bootloops / recovery bugs, its better to wait now for your own region oreo update. If you still want that btu oreo, you can download the corresponding rom for your model from sammobile or updato(for faster speeds). But I suspect oreo update is halted and will be resumed again with these bugs fixed along with may update patch near the end of may globally.
[Samsung Galaxy S7 Edge Questions and Answers] MisterX01X:
I already have installed it on SM-G935F and it works totally fine. The only problem so far I have detected is that when I play a song on Samsung Music with earphones connected, it crashes but it plays normally with phone speaker and secondly this BTU firmware doesn't have Bixby in it.
[Samsung Galaxy S7 Edge Questions and Answers] emilutzzu:
it seems it was a beta nougat for s7 edge ,because the update is not available anymore only on sammobile.....I received notification last week to update to android 8,but I didn't update and now when I check I don't see the notification anymore ,it says like my current version is the latest...
[Samsung Galaxy S7 Edge Questions and Answers] shah22:
It is already mentioned that the update is no more available through OTA because its been pulled back from the server due to bugs in recovery, wait for the resume till the end of the may hopefully :)
[Samsung Galaxy S7 Edge Questions and Answers] Omegastorm:
G935FD w/BTU NO ISSUES

I downloaded the BTU files straight from Sam Firmwares and only flashed AP, HOME CSC and CP with ODIN 3.13.1 and have no issues at all. So fare everything is stable no reboots lags or freezing. That version of ODIN is updated to handle the compression of OREO.
[Samsung Galaxy S7 Edge Questions and Answers] saurabh808:
i hv only one issue

cell standby battery drain as huge as 30%
[Samsung Galaxy S7 Edge Questions and Answers] shah22:
Yes v 3.13.1 handles the latest firmware, but the update had bugs in recovery and some users faced bootloops, I faced auto reboots whenever I rebooted phone and used fingerprint at a faster rate to lock and unlock phone.

Same here, high cell standby drain. Also battery life is a little less compared to last nougat release.
[Samsung Galaxy S7 Edge Questions and Answers] shah22:
Can anyone with the oreo update tried using phone in airplane mode? Or without sim card inserted? See if that cell standby drain still occur in airplane mode or without sim? It may only be a bug or android's wrong report of the battery usage ..
[Samsung Galaxy S7 Edge Questions and Answers] ppihoo:
I am experiencing "Cell standby" battery drain as well. Any solution?
[Samsung Galaxy S7 Edge Questions and Answers] Corduroysack:
I have it too guess we wait till Samsung sends out the update
[Samsung Galaxy S7 Edge Questions and Answers] saurabh808:
I guess even Samsung couldn't figure it out thats y there is delay in ota updates for other regions
[Samsung Galaxy S7 Edge Questions and Answers] ampalos:
Got BTU oreo through ota. No issues whatsoever yet.Phone feels a lot smoother in day to day usage!

I can confirm that there's high cell standby drain.

Battery life is a bit of a letdown as it's a little less compared to last nougat release.
[Samsung Galaxy S7 Edge Questions and Answers] ppihoo:
Is it possible to downgrade same way?

Install nougat again and wait for good oreo?
[Samsung Galaxy S7 Edge Questions and Answers] shah22:
I wouldn't recommend going this route, its better to wait for the next oreo update then downgrading which could brick your device..
[Samsung Galaxy S7 Edge Questions and Answers] shah22:
Cell standby drain for me.. on light usage without any gaming and with every connectivity disabled such as gps, wifi, bluetooth, nearby and auto sync disabled too. Not such a great battery life, little less as compared to last nougat release as I mentioned few posts earlier.
[Samsung Galaxy S7 Edge Questions and Answers] ppihoo:
I got OTA update today. Installing right now. Will update you later.
[Samsung Galaxy S7 Edge Questions and Answers] ampalos:
Got the new ota oreo btu update today.

Will keep you posted about battery drain and performance overall.

One issue that i noticed is that the fps doesn't work when i try to unlock the phone.

Got that after the first oreo update too.

Any thoughts?