yashsingh1/xdaforums huggingface dataset:
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
[MENTION=4608636]bsmitty83[/MENTION]

totally true. 2.3GHz has proven to be unstable. you can say it isn't overclocking (even though that contradicts your own commit. lmfao), language doesn't matter here, semantics.... the fact still remains that it's unstable and that devs working on the very device/kernel u are referencing, know it... so does google, your user, myself and many other people.... in the context of the pixel, google set it to 2.15GHz, no higher. so yeah, you are overclocking the pixel, ignoring their QA. and as i said; your commit is labelled as overclocking too => why do that, if you are going to argue otherwise?. ... seems like your contradicting yourself.

just because it can clock up, doesn't mean much. manufacturing defects or design issues happen.... it's no different than say; Haswell (Intel) when they introduced tsx, which had instability on many. 4th gen intel cpus.... no one said you made the numbers up, but your assumption as to why Google runs at 2.15GHz is wrong... this issue is well known, old news.... you've also had someone demonstrate in your thread that it's unstable - if you had bothered to ask them for logs at the time, you could have verified things...

no, I don't support clocking above 2.15ghz, since it's known to be unstable on our SOC... and it would be careless to have it enabled by defualt, even if I chose to. why would I do that, given that I know it can be problematic?

antutu may not be great way to determine if a kernel is unstable, but in this case; it is a reliable and reproducible way to get things to crash at the higher clock speed. your user was right to point this out. apparently he/she knows more about this issue than you do....

and FYI, your doing something wrong if antutu just force closes on you.... it runs fine and never crashes on stock kernel or mine, nor on any previous device... maybe, it doesn't work for you, because of something you've been doing since marshmallow? probably.

anyway, pointless to argue. not my problem and you've made it pretty clear that you could care less.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Nick80835:
The OnePlus 3 does not use the MSM8996 pro, it uses the MSM8996, the OnePlus 3T uses the pro variant of the processor. The Google Pixel/Pixel XL on the other hand use neither of those chips, they use the MSM8996pro-AB which is an MSM8996pro with lower clocks to decrease voltage requirements and production costs while increasing yields.

The processors in the Pixel are not meant to clock up to 1.9/2.3/653 like in the MSM8996pro as they don't have that processor. These processors are basically the higher speed chips that lost the silicon lottery which is why clocking them higher isn't as stable or effective when compared to the MSM8996pro at stock clocks.

There are multiple reasons for why this was done. To reduce costs, to increase the supply of the chips, to reduce power draw/heat or some other reason I don't know of.

:confused:

Edit: The MSM8996pro is actually only supposed to go up to 1.6GHz on the little cores, not 1.9.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] bsmitty83:
lol so this commit isn't in your kernel ?

https://github.com/nine7nine/Marlin...493a7af#diff-d28b9d608d0aaef8531401df64e6de33

anyways ......

My kernel runs fine and is stable

bottom line .

call it whatever you like

go back to posting about all the glorious code you have but wont release unless you get paid for it ....lol

no sense in letting someone kang you right ? lol

your a funny guy

you use other peoples commits in your kernel and change the authorship . but complain I dont know how to use git properly

you say you dont support overclocking but the code is in your source .

Anyways I guess if the 5 people who actually use this kernel are happy . I'm happy. my phone runs fantastic . Merry Boxing Day or whatever ......:silly:
[Google Pixel ROMs, Kernels, Recoveries, & Other De] bsmitty83:
The pixel does use msm8996pro files for compiling though. The 1.9ghz is a speed boost freq . It's in the one plus 3T code. I didn't make it up . Just because our device doesn't use the exact same chip , all the other custom kernels out are overclocked to 2.3 GHz. Or the option is there for the user to OC . Idk what the big deal is regarding what I have done .
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Nick80835:
I don't think all the other kernels use 2.3 on the Pixel and the files used for compilation are quite meaningless when the hardware isn't fitting.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] bsmitty83:
Our device is compiled using the msm8996pro.dtsi file . This is straight from Google. They know what device is what . The msm8996pro.dtsi file supports the frequencies I am using . That is all . Maybe all pixels can't support that high freq idk. Does not seem to make sense tho . My temps and the device behavior suggests no where near maxing out . I'm just not understanding what the issue is . You can set the max freq to whatever you want. If the kernel won't even boot , then it would be an issue , but to run those freq for 3 sec till your kernel manager kicks in and sets whatever max freq you want should be fine .
[Google Pixel ROMs, Kernels, Recoveries, & Other De] :
sure, but my kernel isn't running above 1.6 / 2.15GHz... I'm not clocking Up to 1.9 / 2.3. because that would cause instability on some pixel devices...

except when it doesn't and causes kernel panics / crashes, as demonstrated in your thread, by a user of it.

lol. ya, that's how it works sometimes. people get paid for work they do. not all apps are free, nor code. nor should they be... I have a couple of features that I'd like to monetize, not just give away, that aren't pixel specific.... it totally makes sense that I would explore monetization, before ever publishing code.... I've learned my lesson in the past, when someone profited from code that I wrote (unrelated to android), so this time; I'm not allowing that to happen.

if that bothers you (which clearly it does), too bad.

no, I complained because you attributed a commit to me, which I wanted no part in.. and yeah, my binder commits are lumped in and a some other recent commits, to be cleaned up later on my next rebase. not something I have time to go through until the new year, all quickly done for December due to limited time / because I knew I wouldn't have my computer over the holidays....

as for being funny, sure am. you're pretty funny too. hanging off every word or idea I mention in my thread.... it shows.

Merry hoho.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] bsmitty83:
Read this

https://forums.oneplus.net/threads/oneplus-3t-clock-speeds.486668/

What’s perhaps most interesting is that this “boost mode” is the only way in which the OnePlus 3T can achieve the peak 2.19GHz frequency on the little cluster. OnePlus was very conservative in its official specification sheet, as they rightly state that the OnePlus 3T’s little cluster has a peak frequency of 1.6GHz, just like the original OnePlus 3. This much is true for many day-to-day operations, but Qualcomm’s boost framework is designed specifically around ramping up the little cluster frequency of the Snapdragon 821-AC to 2.19GHz when launching applications, as confirmed to XDA by Qualcomm. The chipset maker also informed us that the Snapdragon 821-AB (found in the Pixel and Pixel XL) can also access this “boost mode”, albeit up to a maximum of 2GHz in the efficiency cluster (by default); interestingly enough, the Pixel XL keeps it conservative as even in this scenario, the peak frequencies are 2.15GHz+1.6GHz.

I might not know everything . But I know how to read ...........
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Nick80835:
821-AB is not intended to run at 1.9GHz on the silver cores, 821-AC is not intended to run at 1.9GHz on the silver cores. There's a difference between boosting and scaling to a frequency. Boosting is temporary and less demanding on the hardware. Scaling up to that frequency allows the CPU to stay at it for a much longer time and thus can become less stable over time. :eek:
[Google Pixel ROMs, Kernels, Recoveries, & Other De] bsmitty83:
Where do find where it says that ? No frequency is ran for longer than the CPU requires it to . The power cluster only reached 1.9ghz for a very short period of time , otherwise the max it hits is the normal 1.5gh. So it's boosting itself . Again I didn't write the code , just cherry picked it . The 1.9 freq works as Qualcomm intended it to .
[Google Pixel ROMs, Kernels, Recoveries, & Other De] bsmitty83:
Op updated with R4

- Frontswap and cleancache inline with linux 4.15

- added new zswap allocator "z3fold" can compress 3 pages at once vs 2 for zbud

- can now choose zswap compressor lz4 or lzo

- selinux improvements

- binder is inline with msm-kernel-4.4

- updates to android low memory killer (Adaptive LMK)

- updates to mm/compaction
[Google Pixel ROMs, Kernels, Recoveries, & Other De] bsmitty83:
OP updated :

- Linux 3.18.90

- patched zram to linux 4.4

- some mm updates

More info can be found here
[Google Pixel ROMs, Kernels, Recoveries, & Other De] bsmitty83:
OP updated to R6

-- All behind the scenes changes

- updates to sysfs and arm64

- updated blu_active

- various other updates from Linux 4.x+

-- Every change is posted on github

Enjoy .. Still running well for me
[Google Pixel ROMs, Kernels, Recoveries, & Other De] catmaew:
this kernel error in Portrait Mode in Google camera mod (Camera NX)

it take with some blue and red pixel (but can take picture with normal mode)

but this app work fine in stock kernel

link for camera mod

https://xdaforums.com/pixel/themes/google-camera-mod-portrait-mode-enabled-t3728428
[Google Pixel ROMs, Kernels, Recoveries, & Other De] bbender716:
Found this as well. Fwiw, portrait mode works on NoShades kernel
[Google Pixel ROMs, Kernels, Recoveries, & Other De] bsmitty83:
OP Updated to R6.1

Fixed pixelated screen in portrait mode using NX camera app

no other changes
[Google Pixel ROMs, Kernels, Recoveries, & Other De] グリッチ:
Thanks for the quick updates! Also, typo on the zip name.

(Just testing for fun, so it's not necessarily a bug) It's running on my January build and freezing/rebooting a lot and just missing the updates. :)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] bsmitty83:
Lol good eye ... Ya , as soon as I fixed the camera issue , I got the news Google pushed an update . It'll be included next build .
[Google Pixel ROMs, Kernels, Recoveries, & Other De] bsmitty83:
Op updated to R7

- Linux 3.18.91

- Jan 2018 security updates

Happy Crack Flashing lol :p
[Google Pixel ROMs, Kernels, Recoveries, & Other De] bsmitty83:
OP updated to R8

- Added ZZmove governor VR io-scheduler and sociopath TCP controller

- Minor code change to io-schedule switcher

enjoy

i added a link to the op for all the previous releases ( for whatever reason someone might have running an outdated version )
[Google Pixel ROMs, Kernels, Recoveries, & Other De] bsmitty83:
Op updated to R9

- added Adreno Boost parameters to msm-adreno-tz GPU freq governor

- added TCP congestion controllers agileSD and CHINA ( agileSD is supposed to perform well on short-range High bandwidth networks . china is supposed to be experimental and highly aggressive... )

- a few other small commits that should go unnoticed

enjoy.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] bsmitty83:
Op updated to R10

- Linux 3.18.92

- minor updates to fscrypt and ext4 as well as lz4

- flash if you want the latest version or just feel the need to flash something lol
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Jank4AU:
Anyone else have trouble installing this? I've tried on stock ROM using various different TWRP versions and nothing boots for me. This is after a fresh install, so I know I'm on stock boot.img. I hate this Pixel device...I have more trouble flashing stuff than anything I've ever seen. It's ridiculous. I'm so done with this crap phone. The only thing I've ever successfully flashed was Elemental kernel, and that took forever to get right as well. Instructions for everything make it all sound so easy and nothing sticks with this device. I sincerely hope it's not user error but I don't know what else it could be at this point other than a super quirky device. Sorry for the rant. :eek:
[Google Pixel ROMs, Kernels, Recoveries, & Other De] bsmitty83:
OP updated to R11

-- added voltage control for msm 8996 . ( from the z2 device )

-- updated zram to use crypto compression

-- GPU is now overclocked to 729 MHz max

-- added mac randomization from copperhead os . it is set off by default

for those who are worried about the gpu speed ... I have been using it for more than 24 hrs doing everything I can to stress it and I haven't been concerned in the least bit . you can always set the max freq lower if you like . as far as battery taking a hit well of course it will when the max freq is being used but if your playing a game then the battery is gonna drain anyways .

Voltage control is working . I would take caution messing with the voltages especially if you are using the overclock freqs .

so if your ready ... strap em' on and give it a flash ...... lol

ps : is the oc really necessary ? not really . it helps out a lot for benchmarking numbers . 3d games . general fun . my gaming experience with some games I play like MLB perfect inning and War Wings run butter smooth .
[Google Pixel ROMs, Kernels, Recoveries, & Other De] bsmitty83:
OP updated to R12

- Replaced Sched with SchedUtil governor

- no other changes

:highfive:
[Google Pixel ROMs, Kernels, Recoveries, & Other De] clepsy:
Can you share one with stock clock? Would like to try but never got stable
[Google Pixel ROMs, Kernels, Recoveries, & Other De] bsmitty83:
Honestly I have no interest in doing that.

Sorry [emoji26]

If you can't get this kernel to boot , I would suggest trying another kernel .

There are some other very good ones to choose from that don't overclock and will perform well for you .

I like the frequencies how they are , my phone is crazy fast . I hate to disappoint , but I'm going to decline .
[Google Pixel ROMs, Kernels, Recoveries, & Other De] bsmitty83:
OP updated

- R13

- Added Chill governor and re-included sched gov

- Added Thermal Control via sysfs

- updated UKSM ( now works alongside KSM )

- added CAKE net packet scheduler

- added configurable printk ( can be enabled/disabled via sysfs )

/sys/kernel/printk_mode interface

- updated Adreno Idler

- removed powersave governor ( unusable IMO )

- various minor updates

Schedutil has been running well for me . Havent seen a noticeable hit in battery nor have i noticed the boost freq being abused. but I included sched just in case lol .

UKSM will now use ksm's sysfs nodes so you will see both options in a kernel manager app . if you turn one off it turns both off . but you can use all of the tunables
[Google Pixel ROMs, Kernels, Recoveries, & Other De] bsmitty83:
Op updated

- R14

- Linux 3.18.93

- reduced max GPU freq to 710MHz ( from 729MHz )
[Google Pixel ROMs, Kernels, Recoveries, & Other De] bsmitty83:
Op updated

- R15

- February kernel security updates

- Color control

- re-enabled sched governor
[Google Pixel ROMs, Kernels, Recoveries, & Other De] ylovex:
very thanks for your work!

this kernel works well on my device, i can feel it faster and more powersaver.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] bsmitty83:
OP updated

- R16

- Linux 3.18.94

- updated Low Memory Killer

- switched back to Linaro GCC
[Google Pixel ROMs, Kernels, Recoveries, & Other De] bsmitty83:
OP updated

- R17

- updated wake gesture timing for 1000Hz

- removed direct references to Hz in i2c hwmon gsi ipa mdss & fbdev

- updated Adreno Idler tunables

- updated Slimbus overclock ( from poondog )

- few compiler warning fixes

happy flashing :)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] aLPaSLaN07:
Which kernel manager do you guys use? Does it have its own app maybe?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] rubenchu1997:
I have tried to flash this kernel but when I boot up the phone, Google apps start crashing. I have tried to flash it many times and the result was always the same.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] bsmitty83:
I have used just about all of the different apps .

Exkm is what I'm using now.

You can use any of them , I use a root file explorer just as much to edit things via sysfs.

Personally I like synapse , but it's not the most user friendly kernel manager.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] bsmitty83:
Not sure why my kernel would cause gapps to crash. I'll keep an eye out for any of the same behavior but I haven't had anything like what you are reporting.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] ChongoDroid:
Hey man! I just traded my Marlin for a sailfish. My Marlin was a rma and was always kind of weird. It didn't like the OC very much so I'm hoping this phone is a bit more forgiving ?

I don't think there's a way to check cpu bin # on pixels but fingers crossed that this phone likes OC :p

I'd love to have a non OC cpu with all the other optimizations such as gpu boost but I understand it's going to be however it works best for you.

Thanks for the kernel.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] acidspider:
How do.i install this kernel, just flashing in recovery caused bootloop, what other steps do I need to do
[Google Pixel ROMs, Kernels, Recoveries, & Other De] shopealope:
Wanted to try something new and tried out this kernel, I'm pleasantly surprised. It runs very well, great work. And surprisingly my phone worked well with the OC. Thanks for your work!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] acidspider:
Please help how you flashed
[Google Pixel ROMs, Kernels, Recoveries, & Other De] shopealope:
I just flashed like any other kernel, flashed stock boot.img and then flashed the kernel. If it's not working for you, it could be that your phone doesn't like the OC much
[Google Pixel ROMs, Kernels, Recoveries, & Other De] acidspider:
Think it may be not flashing stock boot.img first I'll try that and give a go, do I swap slots in twrp before flashing or anything like that?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] ChongoDroid:
I really don't like background processes chewing up resources (it's an ocd pet peeve of mine) and for some reason everytime I flashed this kernel I would get this constant 25-55% fluctuating CPU load while monitoring in ex kernel manager. So after ruling out apps and other tweaks I have found the culprit.

It is either uksm on its own or uksm and some app I have not playing nice together and the result high CPU load on idle with screen on.

I have gone even further and disabled uksm and zram (takes a while) and I have gotten this CPU idle lower than ever.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] ChongoDroid:
I have a feeling that uksm misbehaving is the reason why some people aren't able to run this kernel or get reboots.

I can't say definitively without more testing but I have a hunch that the phone is spending too much time in the 2342mhz frequency while uksm is doing it's thing (whether it's operating as intended or not, I'm not sure) and that is causing it to overheat and reboot.

I've lowered the thermal throttling to 55 as well as turning off uksm and zram and I'll report back with my findings after more testing.

Cheers and thanks for the kernel, I'm really glad I got this sorted as I love the smooth scrolling from GPU boost. ?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] bsmitty83:
Op updated to R19

- patched up to linux 3.18.98

- I added a non-overclocked version to the Op . Same kernel as the OC version otherwise

- other changes can be found in my github

happy flashing
[Google Pixel ROMs, Kernels, Recoveries, & Other De] ChongoDroid:
I flashed 19 over 18 fine, however it seems some process on bootup triggers a reboot. The screen goes black and is non responsive for X amount of time unless you hold both volume buttons and the power button for what it seems like 10 seconds (reboots when you release the button combo)

iirc there was something like this on the Nexus 5 when temperature reaches a certain level and it enters some kind of safe mode and remains powered off for a while. On the Nexus it would have a red notification light and a lot of users thought they were bricked (since power button long press doesn't do anything for quite some time)

Anyways I'm back on 18 and I'll test more later. Unfortunately I couldn't get a log as it became unresponsive immediately after boot.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] bsmitty83:
[Kernel][8.1.0] NSFW-kernel R19

Also flash the stock boot image before flashing as well . Sometimes I dirty flash the rom , vendor , and boot images before flashing the kernel and root and it helps
[Google Pixel ROMs, Kernels, Recoveries, & Other De] ChongoDroid:
I tried that. I tried without magisk, and then I also tried flashing the February boot image and then flashing over that w/ wiping

---------- Post added at 08:10 PM ---------- Previous post was at 08:09 PM ----------

I tried three combos, the only thing I didn't try is flashing right after a system image which I had to do in the past on the marlin but 18 booted so i don't think it's the same issue.

---------- Post added at 08:12 PM ---------- Previous post was at 08:10 PM ----------

Do you think it's because I had turned zram off? I could turn it back on and let it do it's thing and then I'll flash over it. It's the only thing I've done differently from previous versions. ?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] bsmitty83:
I doubt zram had anything to do with it , but yeah this device is crazy , it could be in my head but sometimes the only thing that will work to boot any kernel besides stock on my phone is to dirty flash the rom and boot images again.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] ChongoDroid:
I know what you mean but usually when I need to flash an image, nothing will boot. Like either nothing boots or it loops to recovery and this isn't that.

Right before it turns off, the CPU temp was in the high 70s to 80s so I wonder if it's some sort of hardware shut off. I'm gonna flash again and try to get some logs.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] ChongoDroid:
What would be the best way to capture a log right after a reboot? I used alog 3 seconds right before it rebooted but I don't know if that's going to help.

I'll see if I can get a kmesg
[Google Pixel ROMs, Kernels, Recoveries, & Other De] ChongoDroid:
Well I turned zram back on and I went to capture a kmsg and voila it stayed on! Albeit it was very warm and the launcher would soft reboot I thought I had fixed it. As I was typing a response in this thread, the dreaded black screen happened.

I even tried putting it on the air conditioner to see if I could grab a log before it crashed and no bueno.

If someone can confirm what I have said then I won't bother flashing a stock image. 18 is running great however on my sailfish.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] ChongoDroid:
I tried to copy my kmsg from proc in recovery and after about 10 minutes I restarted because I thought it had derped out. However on second look it looks like it took and there's a roughly 100kb log... So for what it's worth, here's the (hopefully entire) kmsg from after the black screen of death

Thanks man :)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] shopealope:
I'm having the same issue on R19 so I also went back to 18, would it help adding my logs?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] ChongoDroid:
It can't hurt, I don't know if mine was complete or not.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] bsmitty83:
I looked at the log , it was complete up until the reboot.

What ROM are you using ?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] ChongoDroid:
I'm on stock February