yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Android Development] Elektroschmock:
Shamu's original mpdecision doesn't hotplug. It's quit dumb as the only thing it can do is boost to 1,4 GHz for 3 Seconds.

But I just merged some commits in LineageOS with a proper powerhal, which should be compatible with this kernel if you use the interactrive governor
[Nexus 6 Android Development] wavedashdoc:
Is it the mpdecision from the Galaxy Note 4? Have you noticed any improvements with it (smoothness or battery)?
[Nexus 6 Android Development] athulele:
It's definitely smoother. I'll test out battery a bit more. My device is running cooler as well.
[Nexus 6 Android Development] Elektroschmock:
I don't know which devices use it. I grabbed it from the common samsung_apq8084 repository. I think all Galaxy S5 Devices use it.

Well If I didn't think it was an improvment I wouldn't have made it. :D

But Stuff like this is nearly impossible to test. Especially because my two Nexus 6 don't have the same speed. :confused:

Battery drain on idle is down to 0,33 - 0,4 % per hour...at least on my devices.
[Nexus 6 Android Development] jacomail95:
Please, I beg you to do something about the automatic volume normalizer of this device, it's driving me nuts, earphones are ok but speakers are literally softer than they should be. I searched everywhere for a fix, the only thing I found is that rotating the device the max volume briefly goes up like it should be, before going down again because of this f****** normalizer. I've seen 99% of these devices are affected by this problem but no support at all by Moto or Google on what to do (after all it's the hardware firmware which does that I believe). I bought this Nexus 6 exclusively for screen size and loud stereo speakers, so I feel so betrayed when they suggest only to perform a factory reset or changing device, which doesn't solve at all the problem. Please, can't we make the normalizer think we are constantly rotating the device without actually doing it? Or a solution to make the device think the audio focus is changing constantly, other moment in which the audio goes up, with ringtones or things like this... I know it's possible to eliminate or strongly limit this damn behaviour via kernel correction, otherwise the volume wouldn't be for a little time so high as expected by these powerful speakers. Please, try to find a solution... Thanks for the kernel and the support to Shamu you give, have a nice day...

Inviato dal mio Nexus 6 con Tapatalk 2
[Nexus 6 Android Development] adm1jtg:
If you want to post a1. 8 test version of popcorn with these commits I would be more then willing to help test, and I am sure there are many others willing to help as well
[Nexus 6 Android Development] athulele:
Those are device tree side commits.
[Nexus 6 Android Development] runekock:
If you look at the changelog, athulele tackled this problem in version 1.5. Didn't it work for you?

Even without the fix, the volume lowering should only occur at low battery. If you get it with a full battery, it sounds like an different problem than other users have.

Also see https://xdaforums.com/nexus-6/general/nexus-6-speaker-issue-fix-t3813277 and https://xdaforums.com/nexus-6/devs-only/speaker-amplifiers-nxp-tfa9890-research-t3236518
[Nexus 6 Android Development] jacomail95:
Tried everything, just kernel, settings, files on the N6 forum, problem persists, regardless of battery percentage... I use PowerAmp players but that's maybe irrelevant because I tried also Neutron and others... I'll try AEX ROM, maybe the built-in kernel has a better result... I'll update in a day or two
[Nexus 6 Android Development] athulele:
AEX literally has the same kernel, no code changes so you're not gonna notice anything different. Check the value of your battery voltage using accubattery or such when the volume drop occurs. If it is below 3.09v then and only then you're going to have a volume drop. I have tested this extensively.

And I am not going to drop the safeguard voltage below this, as I had problems with device stability below that.
[Nexus 6 Android Development] jacomail95:
Sorry for bothering again and for the consecutive posts, I just think, all the users who have in the past installed the leankernel for N6 claimed that ALL problems with speakers were fixed. Maybe it had some patch somewhere, I just ask you to check it when you have time, here the leankernel sources

https://github.com/imoseyon/leanKernel-shamu

Maybe disabling also the BCL by default could help, I can't turn it off not even with apps or terminal commands, it restarts itself always

EDIT: I read one minute ago your new post, so never mind the BCL part
[Nexus 6 Android Development] Superior Sandbox:
Would it be possible to add over clocking to 2.8 GHz? I used to do this on EX and I loved it.
[Nexus 6 Android Development] athulele:
Overclocking will not be added.
[Nexus 6 Android Development] Superior Sandbox:
Do you know if there is any reason why it won't be added? I actually feel likely it made games run a bit smoother when I had it clocked at 2.8GHz.
[Nexus 6 Android Development] athulele:
Its a very bad performance-stability tradeoff. For barely 1-2% more performance you lost a lot of stability and also make the device run hot.

And when it starts to run hot, CPU freq is automatically reduced so there's no point in OCing in the first place.
[Nexus 6 Android Development] jacomail95:
I switched temporarily to pure zaw kernel for testing purposes, I find the volume drops less frequent and the BCL driver can be disabled, I will compare the two kernels and update eventually a little review, I don't mean any disrespect, it's just testing, [MENTION=4293041]athulele[/MENTION] your kernel is very stable and good

Inviato dal mio Nexus 6 con Tapatalk 2
[Nexus 6 Android Development] Superior Sandbox:
Yeah, I guess so. I've never had those issues though :/
[Nexus 6 Android Development] runekock:
In a way, you can say that it comes overclocked from the factory. The processor in the Snapdragon 805 is essentially the same as in the SD800 where it only ran at 2.26 GHz.
[Nexus 6 Android Development] athulele:
Snapdragon 805 uses Krait 450 cores compared to Krait 400 of Snapdragon 800 and 801.

Snapdragon 801 was essentially the higher clocked version of 800.
[Nexus 6 Android Development] Superior Sandbox:
I'm on LOS with PC 1.7 and when my battery gets under 50% all four core's frequencies are capped at 1.497GHz. Does anyone know how I can disable this?
[Nexus 6 Android Development] glockman4519:
Latest build is off the hook... Awesome work.. Thank you once again for sharing your work and continuing to build for this amazing device.
[Nexus 6 Android Development] athulele:
Popcorn v1.7.1 is up. Really small update.

Changes:

UKSM added (disabled by default, use KA-mod to enable if you want to)

Lineage upstream updates

Toolchain updated to Linaro GCC 7.3.1

DL: https://www.androidfilehost.com/?fid=5862345805528054230
[Nexus 6 Android Development] MiroALG:
thank you Bro ?
[Nexus 6 Android Development] MiroALG:
[MENTION=4293041]athulele[/MENTION] can you make app for your kernel like exkernel manager and franco kernel
[Nexus 6 Android Development] athulele:
Sorry I'm not an app dev and don't have time to get into it. Plus KA-mod does everything the kernel needs.
[Nexus 6 Android Development] athulele:
Sorry I'm not an app dev and KA mod supports all the kernel options. So there's not really any need for another app.
[Nexus 6 Android Development] SteveYoungs:
Enabling UKSM with EX Kernel Manager

It's really easy, you just have to add a new "User Setting". So...

Tools -> User Settings and hit the '+' (bottom right)

The file you want is:

'/sys/kernel/mm/uksm/run'

Change the value to '1' to enable UKSM. The setting will be applied immediately. If you want the setting to persist across reboots tap the grey icon on the right (it'll turn blue to indicate "apply on boot")

Tip:

EXKM uses the filename for the name of the setting you add in "User Settings", so this one will be called "run", which is kinda vague. Luckily there is a way to change it. Look in the directory '/sdcard/ElementalX/custom_settings/' and you'll see a file named 'run'. Simply rename that file to something a little less ambiguous (I renamed mine to 'UKSM').
[Nexus 6 Android Development] rushier.ivan:
Anyone using this with latest aosip rom? :)

EDIT: nvm, just flashed it. Works great. But I wonder how the red tint fix works? I still see red tint on low auto brightness :eek:
[Nexus 6 Android Development] Lagarde:
One reboot on new kernel overnight (had zero on previous version). No logs grabbed, so this isn't super helpful. Monitoring for any other reboots and will submit log if it happens again.

Out of curiosity, what's the value in UKSM? My searches only show it's used on VERY low-memory devices. Is there some advantage to using it on shamu?
[Nexus 6 Android Development] SaberJ2X:
Camera and flash loght dont work in plain lineage os 15.1
[Nexus 6 Android Development] paulmerrill:
Just reboot, usually fixes it for me.
[Nexus 6 Android Development] Elektroschmock:
Yeah, wasted cpu cycles. :p

I tested it a year ago and didn't see any measurable improvement.
[Nexus 6 Android Development] athulele:
That's why I disabled it by default. It's there if someone wants it but not recommended.
[Nexus 6 Android Development] Lagarde:
Thanks to you both. I couldn't find any reason to use it in my research, but figured I might have missed something. :D
[Nexus 6 Android Development] eric4shay:
Anyone know how to get notification light to blink again it's driving me crazy with this kernal it just stays on instead of blinking my room is a validus rom so it's allowed in the rom itself any help would be great.
[Nexus 6 Android Development] runekock:
The N6 doesn't have hardware support for blinking, so the only way to implement it is by waking the main processor every time. That costs a lot of power.
[Nexus 6 Android Development] eric4shay:
But it blinked without this kernal it even has the option in the validus menu for it that's what I don't understand
[Nexus 6 Android Development] ktmom:
You overwrote the stock Validus kernel that enables blinking with popcorn which does not. If you want blinking back, dirty flash your ROM to restore the kernel designed to handle it.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
[Nexus 6 Android Development] paulmerrill:
I'm getting some system crashes, phone just reboots. Can some point me to a process of capturing a log file so I can see what's going on?
[Nexus 6 Android Development] Sky88:
PUBG on laging on my phone need some performance tweak.

Current ROM aoisp.
[Nexus 6 Android Development] eric4shay:
I kinda figured that wish it could be enabled on this kernal to many features I'll miss without it lol thanks for the help
[Nexus 6 Android Development] Sziklián:
Do you have any news about this problem? There must be a way to change this value.
[Nexus 6 Android Development] adm1jtg:
If I read his reply right the value you want to change isn't used in the n6 code thus if it is at 0 or 22 it will have no effect.

Or did I misunderstand the above reply
[Nexus 6 Android Development] Sziklián:
There must be a value, which determines the touchmove sensitivity in the kernel. Maybe its not called movhysti, and located in an other file, but we must find this, and change its value to 0.
[Nexus 6 Android Development] adm1jtg:
Never had a touch sensitivity issue EXCEPT when I turned on smart pixels in the rom I run (aosip). Mind you I am not a gamer, so the issues your having may not show up in my usage patterns.

Also just thinking outloud if you do find and change this value wont that cause a battery hit as moving one pixel at a time would be much more intensive then moving as in your example like 23 at a time, would it not?
[Nexus 6 Android Development] Sziklián:
At normal usage, its not easy to detect this problem. But for example, if you grab an icon on launcher and move it slowly, it won't move for 23 pixels, but after that it jumps away 23 pixes, and just then will move smoothly.

But on some launchers or browsers, you won't see this effect, because the application "hides" this jump by making this 23 pixel movement smooth, not an instant jump. It means, this will just delay the smooth movement, however it should not be delayed if the touchmove sensitivity were set to 0.

You should download this app for testing:

https://m.downloadatoz.com/touch-move/com.tegrak.touchmove/download.html

It would cause only a very minimal battery usage, because it affects just the first 23 pixels of the movement.
[Nexus 6 Android Development] adm1jtg:
I understand but will not load and install an app that is NOT in playstore. Also I would still worry about added battery usage. I will leave it to the powers that are smarter then me to continue this discussion.
[Nexus 6 Android Development] Sziklián:
Then download any multitouch testing application, you will see the same effect.

Or just turn on "Pointer location" at Developer options, you won't be able to make a move less than 23 pixels.

The CPU would just calculate this 23 pixel movement too, not only the next ones. It wouldn't use too much extra power, but it would cause a lagless and delayless movement.

I was wrong about this. The browsers just ignore the first 23 pixel of the movement. For example if you scroll down a webpage by 30 pixels, it will move down just by 7 pixels instead of 30. This also applies to the Settings app, and many other apps which have scrollable content. Thats why the touchmove lag is not detectable with these apps, but there will be an annoying delay.
[Nexus 6 Android Development] runekock:
I assume that the setting is there to make long-pressing easier. Without it, you must keep your finger perfectly still during a long-press, and some people will find that difficult.

I would argue against changing the value in the kernel's defaults - it would need to be something that each user can choose in a settings app.
[Nexus 6 Android Development] athulele:
Hi, I haven't found the datasheet for the touch IC yet, and the code itself is not very clear to me, I'm a novice programmer at best.

If you find anything of help, do let me know.

EDIT: I also don't have much time on my hands these days now that college has started.
[Nexus 6 Android Development] Sziklián:
But on latest Samsung devices, like S6, S7, S8, or A series, its already 0, with no longpress problem, and some of them have same, or even more pixel density. But yes, a setting for this would be the best, as Galaxy S2 also had it with Siyah kernel. If someone has problem, may set it to 3 or 4, but this 22 is ideal for parkinson's diseased people only.

UPDATE: The apps which have an effect for long press, has an additional filter for this, so doesn't matter if the movhysti is 0, it will detect the movement after a few pixels, to make the long press easier. But for apps where there is no function for long press (for example most of games), there is no additional filter, so only the movhysti value will restrict the movement, which is absolutely bad, has no advantage.
[Nexus 6 Android Development] sempot:
Hi guys, what kind of settings do you guys run? Governor and Io wise
[Nexus 6 Android Development] mohdschizo:
Hi.. I use chill governor with maple io. Sometimes it abit laggy when the phone ring..
[Nexus 6 Android Development] paulmerrill:
Interactive and row io for me
[Nexus 6 Android Development] wavedashdoc:
Haha nice, yeah YouTube TV is a great deal. I split it with my friends and family so its like maybe 10 bucks a month for me.

Test kernel 3 running well, other than the Youtube TV reboot issue. As I explained to the dev this error started happening around 3-4 weeks ago as [MENTION=3383960]Elektroschmock[/MENTION] kept updating the kernel source. As reference [MENTION=4684315]flar2[/MENTION] Elementalx 5.18 kernel does not have this issue which is built off of older Lineage kernel updates. But anything past 5.19 and to the current 5.21 does in ElementalX.

[MENTION=8146955]fullofhell[/MENTION] despair test kernel does not have this issue.

Edit: Also this is not a specifically a ROM issue, only kernel as Official Lineage 15.1 has this issue too. In addition when the reboot occurs, tje last kmsg message does not note the reboot or kernel panic, it just ends trying to load the video.
[Nexus 6 Android Development] Cypresshill555:
Please add a MultiROM support?
[Nexus 6 Android Development] athulele:
I'll take a look at kexec patches, I'll PM you with a test zip later on.
[Nexus 6 Android Development] Cypresshill555:
I will wait, thank you!
[Nexus 6 Android Development] Cypresshill555:
This log
[Nexus 6 Android Development] LunaticSerenade:
Thanks for doing this. I've been running test 3 since you put it up, and no issues, including several hours of Pokemon Go. Solid work!
[Nexus 6 Android Development] athulele:
Fourth test up! Changelog in OP.

DL: https://www.androidfilehost.com/?fid=674106145207491115

Note: MultiROM support and YT TV reboots are being looked into.

MultiROM has some really weird bugs so I am looking into getting in touch with the dev of MultiROM.
[Nexus 6 Android Development] giannis_mathiou:
Just flashed on top of latest AOSiP, Netflix seems to work fine. Will test for some days and I'll come back. Nice to see custom kernel that works -easily- on Oreo it's been a long time ago. :P
[Nexus 6 Android Development] II_DiE_4:
Just a suggestion. You should put "shamu" in the file name, so that it gets listed when searching AFH.
[Nexus 6 Android Development] athulele:
Fifth test up! Felt like releasing this because Sound Control and undervolt controls were added.

DL: https://www.androidfilehost.com/?fid=890278863836289569
[Nexus 6 Android Development] wavedashdoc:
Awesome work. Thank you for adding the ability to properly disable MPDecision!
[Nexus 6 Android Development] pinkfloyd3:
Fast charge supported ?

Sorry for my bad english
[Nexus 6 Android Development] wavedashdoc:
Yes it does ?
[Nexus 6 Android Development] athulele:
I think what he means is USB fast charging, which I haven't added yet.

I'll take a look and probably add it in the next release.
[Nexus 6 Android Development] athulele:
I haven't added any MPDecision related patches. Are you talking about the toggle in KA-Mod? That's always been there for me.
[Nexus 6 Android Development] wavedashdoc:
Hmm, well in EX kernel manager the option to disable it was there in Test3 and below, but when trying to disable it, it would still read "enabled". Now this would work to disable it, even though it would still show as enabled. However up until Test4 the setting would not stick after a reboot. It does now and stays off past boot and shows disabled. ?

---------- Post added at 04:11 PM ---------- Previous post was at 03:22 PM ----------

Ah okay, yeah that's something I've really never been concerned about. Really liking this kernel, extremely smooth and responsive ?
[Nexus 6 Android Development] athulele:
Glad to know everything's working well! I completely grateful to neobuddy for the work he's done. Once I'm done adding optimizations from his source, I can work on other features.

I have sent you a PM with a test kernel. Please report back.
[Nexus 6 Android Development] Unreal_Shogo:
Is your camera working with this kernel on CrDroid? Mine doesn't
[Nexus 6 Android Development] athulele:
I have seen the same bug on the LineageOS kernel as well, I'm looking into it.

Meanwhile, simply reboot or run the follwing command in a terminal emulator to fix it:

1. switch to root by

su

2.

killall mm-qcamera-daemon cameraserver

Wait a few seconds and camera should work.
[Nexus 6 Android Development] Unreal_Shogo:
I'll try the command, but the reboot didn't work :(

EDIT: It works after 2 reboots now, thanks
[Nexus 6 Android Development] athulele:
Popcorn v1.8 is out!

Changes:

Merged a few security patches from the August bulletin. I think I missed two of them but I'm not sure if they're applicable to our device.

Unfortunately I didn't have enough time to check backports and git conflicts due to ongoing exams.

DL: https://www.androidfilehost.com/?fid=3700668719832237005
[Nexus 6 Android Development] SteveYoungs:
For those times when more important things in your life, like exams, require your focus we honestly do not mind waiting.

Good luck with those exams, hope you ace them!
[Nexus 6 Android Development] ikramii:
Can anybody teach me how to settings uksm?
[Nexus 6 Android Development] runekock:
[MENTION=4109005]Phrank916[/MENTION]

That's a huge voltage jump you've got after 883 MHz. Indeed you should run it at 883 as much as possible.

My phone's voltage table is entirely different, see the screenshots. The voltage actually decreases at 960 MHz - I didn't think that was possible.

So while your method is sound, we can't just copy your final results, we would have to do the calculations ourselves.

Edit: XDA doesn't seem to like my screenshot. Here is a part of the voltage table:

729 MHz 790 mV

883 810

960 800

1.03 810

1.19 830
[Nexus 6 Android Development] noteness:
[Feature Request] Would be nice if Android-keyboard-gadget is patched to this kernel

It would be nice if you could patch github.com/pelya/android-keyboard-gadget with this kernel :)

(I apparently can't post links, so)
[Nexus 6 Android Development] athulele:
Super small incremental update, just upstreamed to lineage's kernel.

DL: https://www.androidfilehost.com/?fid=1322778262903981395
[Nexus 6 Android Development] saif hussain:
********* REQUEST ********

PLEASE ADD KALI NETHUNTER PATCH IN YOUR KERNEL

COZ THERE NO OFFICIAL OREO KERNEL.

[IMG="nethunter"]https://www.google.com/imgres?imgurl=http%3A%2F%2Fi.imgur.com%2F8KnPs5I.jpg&imgrefurl=https%3A%2F%2Fxdaforums.com%2Flg-g5%2Fdevelopment%2Fkali-nethunter-lg-g5-t3364545&docid=cEzOpW_obDy8PM&tbnid=utWTB2zcB-hD5M%3A&vet=10ahUKEwitqb7Q8_PcAhVXVH0KHXrRB-kQMwhJKBMwEw..i&w=960&h=540&bih=652&biw=1366&q=nethunter%20nexus%206&ved=0ahUKEwitqb7Q8_PcAhVXVH0KHXrRB-kQMwhJKBMwEw&iact=mrc&uact=8[/IMG]

UR KERNEL IS ONE OF THE GR8 KERNEL SO I REQUEST YOU.

NEXUS 6 (shamu)

AICP + Popcorn

**************THANX*************
[Nexus 6 Android Development] Elektroschmock:
You also need to take the current the cpu uses at every freq into account.
[Nexus 6 Android Development] athulele:
It'll depend on the binning of your CPU. And therefore as Elektroschmock said it'll also depend on the current draw. It's hard to come up with one works-for-all config due to this very reason.
[Nexus 6 Android Development] athulele:
Popcorn Kernel v1.8.2 is out!

- Lineage upstream sync (has spectre-v1 and spectre-v2 patches)

DL: https://www.androidfilehost.com/?fid=1322778262903986506
[Nexus 6 Android Development] matchesmalonr:
dumb question but will the kernel force encrypt my device?
[Nexus 6 Android Development] ktmom:
A search on "force encrypt" takes one back to this discussion in the thread.

"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
[Nexus 6 Android Development] athulele:
Popcorn kernel v1.9 is out!

- Lineage upstream sync

DL: https://www.androidfilehost.com/?fid=1322778262904002934
[Nexus 6 Android Development] cujo6801:
Thanks......

I really appreciate you staying at it..
[Nexus 6 Android Development] maksimreder:
Any chance for a kernel for 9.0?
[Nexus 6 Android Development] athulele:
I'll definitely put out a build once ROMs are more stable
[Nexus 6 Android Development] maksimreder:
Thanks, NitrogenOS is worth looking into. Been using it as a daily driver. Solid.
[Nexus 6 Android Development] keselekupil:
i've tried on Pie . and its works smooth
[Nexus 6 Android Development] maksimreder:
Flashed on Pie as well, boots just fine, smooth. But ran into issue that I was not getting any signal bars, and LTE was not showing up. I toggled airplane mode and data came back, happens on every boot up.
[Nexus 6 Android Development] athulele:
I think that's an issue with the pie IMS itself. You can read up on it more the general section thread about pie ROMs