yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Original Android Development] Mendrake:
Thanks for the release! I'm installing it right now.

Is there a description on how this new Cultivation governor works? I couldn't find it anywhere.
[Nexus 6P Original Android Development] dephsone:
Anyone who tried the new release with Dirty Unicorns?

I did read some comments here that the previous versions ended up with bootloop on DU.
[Nexus 6P Original Android Development] laulau42400:
Hello

No bootloop with DU RC:good:
[Nexus 6P Original Android Development] nathanchance:
Read the commit messages and the comments: https://github.com/frap129/angler/commits/dev/ng-mr2/drivers/cpufreq/cpufreq_cultivation.c
[Nexus 6P Original Android Development] king_david43:
This kernel isn't booting for me on f2fs I just get stuck on the white Google screen
[Nexus 6P Original Android Development] theerachai:
no problem for me

nitrogen rom
[Nexus 6P Original Android Development] king_david43:
Yeah I tried nitrogen yesterday and it worked but my data somehow got reverted back ext 4 is not working for me on any other roms currently I'm on Vanilla
[Nexus 6P Original Android Development] tibere86:
Running this kernel with 8/20 CM13 nightly, smooth as butter. Going to monitor battery performance over next few days. Good work [MENTION=5051294]frap129[/MENTION] :good:
[Nexus 6P Original Android Development] Ofthecats:
https://s.basketbuild.com/devs/frap129

click on your device
[Nexus 6P Original Android Development] adinkwok:
:confused:

:confused::confused::confused::confused::confused::confused:

What's next? A "Creamy Hotplug" also cooked in-house by the man himself..!? :silly::silly::silly:
[Nexus 6P Original Android Development] Bladehawkz:
Any specific reasons for prioritising async over sync for the maple i/o scheduler?

Just theorizing, but is it because async allows further program interaction while the request is ongoing, and we want the programs to 'hang' from sync requests AFTER our touch input async requests?
[Nexus 6P Original Android Development] Ofthecats:
Kernel tweaking apps don't seem to read any frequency usage, and I'm getting slowdowns resuming from sleep.

for now, I disabled hot plug and am trying hawktail interactive governor profile
[Nexus 6P Original Android Development] frap129:
you never know ;)

As much as I would like to give you an answer, I simply don't know. I tested async priority and sync priority for a few days each and simply found that prioritizing async made the UI seem snappier than sync. Your theory does seem to have merit though, so thank you for the speculations.

Please let me know how disabling hotplug and using hawktail affects battery life. If it improves battery life while maintaining performance, I'll run through some of my own testing to see if its worth it to make the switch.
[Nexus 6P Original Android Development] atrix2man:
When waking from deep sleep, phone started freezing up but I noticed Max and min frequency was locked at 302. I had to reset my Max frequency to fix the deep sleep issue.
[Nexus 6P Original Android Development] frap129:
I recently noticed this too, although I dont think it will really be a problem since I'm completely rebasing the kernel for android 7.0 once the source is released. As with the first upload, I will be spending multiple days testing, so it may be over a week until a new release is pushed.
[Nexus 6P Original Android Development] atrix2man:
Sounds good. I'll be willing to help test to speed things up a bit. :good:
[Nexus 6P Original Android Development] frap129:
Good news! Thanks to my pal [MENTION=5037435]REV3NT3CH[/MENTION] debugging the issue as being because of powersuspend, I have reworked chill and maple to use the screen on/off state instead of powersuspend. Should fix your issue in the next update.
[Nexus 6P Original Android Development] xperator:
[MENTION=5051294]frap129[/MENTION] so should I flash or wait for the next version
[Nexus 6P Original Android Development] atrix2man:
If you want less bugs, then I would wait. There's a power suspend issue being worked out.:cool:
[Nexus 6P Original Android Development] Ofthecats:
would this also cause more drain than expected?

with limited testing, I've been seeing significantly more drain on v1 than other kernels.
[Nexus 6P Original Android Development] frap129:
Possibly, although I'm completely starting from scratch for my Nougat kernel, so this shouldn't be an issue
[Nexus 6P Original Android Development] frap129:
No, this project isn't dead. I have a stable kernel that I believe will be the first nougat release up and running, although it is likely that the September security patch will be released this week. Would you guys like a kernel now or wait until the security patch is released so the kernel doesnt leave that out?

Current features are:

Various optimizations throughout

Linux 3.10.103 merged

Random driver from Linux 4.1.31

frandom

Chill governor (Default is Interactive with GlassFish settings)

Wake Gestures

based on Franco Kernel

Power efficient work queues

Adreno idler

Disabled FSync

Arch Power

Linaro 6.1 toolchain

misc more
[Nexus 6P Original Android Development] Ofthecats:
I don't mind waiting for the next security patch.
[Nexus 6P Original Android Development] reas0n:
well, if it's not the problem for You, then why not!
[Nexus 6P Original Android Development] frap129:
New build uploaded! Have fun flashing. I'll try to have a new build out next week with some more features from 6.0 added in
[Nexus 6P Original Android Development] Ofthecats:
Just flashed! Will give it a try ?

Deactivated zram, enabled fsync, UC GPU max 450
[Nexus 6P Original Android Development] drdrewdown:
Thanks for the fresh version. Running well so far.

Not sure why everyone is so crazy about Chill gov it seems very erratic & spends a lot of time at high freqs
[Nexus 6P Original Android Development] laulau42400:
If you have a custom kernel, this may explain the bootloop. Wipe cache and then install the rom again. You must then be able to install and start the new frap129 kernel.

Envoyé de mon Nexus 6P en utilisant Tapatalk
[Nexus 6P Original Android Development] xflowy:
default hotplugging setting would be to change from lazyplug to disabled (in exkm, e. g.), right? if im using lazyplug, as it is default in this kernel, should i be using msm thermal instead of core control?

and: is there any way to prevent the last two cores from getting shut off this early due to thermal throttling?

thanks much! :)
[Nexus 6P Original Android Development] frap129:
Could you follow the bug reporting guide linked in the op? It explains how to capture a log which would help me debug it.

There is no default hotplugging setting, I've disabled it in the source so that it doesnt interfere with lazyplug. Core control should also be disabled, but any thermal driver is fine. If you disable core control the last two cores shouldnt get shut off.
[Nexus 6P Original Android Development] xflowy:
so if i disable lazyplug there will be no hotplugging at all since you disabled the default behaviour?

and msm_thermal should be enabled by default (and core_control disabled)? may i ask why you didnt set this up as default with your kernel then? cause the stock electron setup is with core_control enabled. just asking.
[Nexus 6P Original Android Development] frap129:
I guess I just forgot to disable it. The next release will feature the IntelliThermal driver, which I've configured to be less aggressive than msm_thermal. You can try it out in the next weekly
[Nexus 6P Original Android Development] Mystique:
GZR Tesla Latest 7.1.2

I could never get past the 'Google' screen..

I completely wiped the phone and loaded the rom, gapps, and Electron v10.

I got to the boot animation.. but that's where it ended..

https://hastebin.com/ovehimiguf.vbs

Any suggestions?
[Nexus 6P Original Android Development] frap129:
None of the errors there look kernel related... Could you get a kernel log?

Run

adb shell
cd /sdcard
dmesg > dmesg.electron
exit
adb pull /sdcard/dmesg .
[Nexus 6P Original Android Development] Mystique:
no /sdcard but yes /data/local/tmp

mount output also included..
[Nexus 6P Original Android Development] frap129:
This is a really weird issue. Most likely its a hardware issue, unless you either changed your partition sizes, or have a completely full system partition. I'll look into it incase theres something I can do on my end.
[Nexus 6P Original Android Development] xflowy:
[MENTION=5051294]frap129[/MENTION] v10 prevents the phone from sleeping. im on latest nitrogen rom. flash kernel works just fine, so i assume its your kernel since every other variable stayed the same.
[Nexus 6P Original Android Development] jr67:
Sometimes system or user apps can run amok and prevent your phone from sleeping. Usually rebooting fixes that. If it didn't do you have a log you can provide?

I was on the same setup as you (Nitrogen & Electron) and v10 didn't prevent my phone from sleeping.
[Nexus 6P Original Android Development] xflowy:
That's strange af. Rebooted ofc. Even tried a second time after i tested flash kernel with success and did end up again in the wakelock.

Btw. you on latest nitrogen and using f2fs?
[Nexus 6P Original Android Development] jr67:
On the latest Nitrogen but not using f2fs.
[Nexus 6P Original Android Development] pacods61:
Spectrum not supported?

Can someone help me why when install electron v10 it's says spectrum in not supported?
[Nexus 6P Original Android Development] frap129:
Is your phone rooted?
[Nexus 6P Original Android Development] pacods61:
Yes

It is very odd that this is happening lol
[Nexus 6P Original Android Development] frap129:
Try wiping cache+dalvik/art cache

Go to Settings>Apps>Spectrum>Storage and wipe data and cache for the app
[Nexus 6P Original Android Development] pacods61:
Still nothing

Bah still nothing sorry to bother u I will figure it out lol.
[Nexus 6P Original Android Development] Mystique:
I got the April Angler build.. reset phone back to stock, after first boot loaded twrp (stock latest). Then wiped everything. Made an /sdcard/Install/ copied GZR (tesla), Flash kernel, Gapps Nano, and three magisk audio mods from ahrion. Here we are.

GZR comes with Magisk v12 by default..

I go the further with yours when I wiped system, deleted the magisk.img and stock.img, reinstalled gzr tesla, and your kernel..

but never have I gotten to the desktop..

My 0.02
[Nexus 6P Original Android Development] xflowy:
will try, thanks.

i assume u dont have experienced this issue, even with f2fs!?
[Nexus 6P Original Android Development] frap129:
I haven't experienced any wakelock issues with the kernel. I actually have a few disabled by default.

In other news, v11 has some nice changes on the table so far:

Faux Sound control

RCU improvements

Major fixes and improvements to LazyPlug

PDesire 10.1 Ultra High Quality Audio

IntelliThermal v3 with less aggressive defaults

IOScheduler Switcher driver by SultanXDA

Automatic boot image signing (Thanks to [MENTION=631273]Chainfire[/MENTION])

All of which will be available for testing in the next weekly!
[Nexus 6P Original Android Development] Augustin79:
Looking forward to it! :svetius:
[Nexus 6P Original Android Development] shantam3108:
No wakelock issues can confirm that. About battery I am running on battery mode will test out today :)

Thanks [MENTION=5051294]frap129[/MENTION] for your work :)
[Nexus 6P Original Android Development] shantam3108:
Here Is the bbs stats
[Nexus 6P Original Android Development] xflowy:
you on f2fs?

---------- Post added at 12:22 PM ---------- Previous post was at 12:21 PM ----------

a few of what disabled!? :rolleyes:
[Nexus 6P Original Android Development] fystrified:
am i the only with battery graph and stat looks like this after flashing this kernel?
[Nexus 6P Original Android Development] xflowy:
what do u mean?
[Nexus 6P Original Android Development] fystrified:
no sign of Android system, Android os and app usage data
[Nexus 6P Original Android Development] shantam3108:
No on ext4
[Nexus 6P Original Android Development] shantam3108:
Getting issues with magisk tried installing Dolby atmos module and bootlooping on Google logo. Changing the kernel resolves the problem
[Nexus 6P Original Android Development] frap129:
Wakelocks

Confirmed bug, will be fixed in v11 and probably by the weekly
[Nexus 6P Original Android Development] xflowy:
yeah nah. its not some wakelock which is causing this. its like the phone never goes into deep sleep. probably sth with f2fs and the kernel.
[Nexus 6P Original Android Development] frap129:
What kernel works other than stock? I've experienced this issue, although I dont know what would cause it
[Nexus 6P Original Android Development] Mrcactuseater:
On a clean flash and a dirty flash this kernel won't boot for me without Kylo kernel being flashed beforehand. I'm running F2FS and SAOSP-N and can get a log tomorrow at some point.
[Nexus 6P Original Android Development] king_david43:
You're right this worked for me wasn't able to get it to boot before
[Nexus 6P Original Android Development] shantam3108:
Franco kernel as well as flash kernel both work with Magisk. Currently flashed Franco kernel and all modules are working and no issues of bootloop. Earlier I I used magisk with your kernel and it worked without issues. Franco as I recall made some se policy changes for better compatibility with magisk.

With v10 I can use magisk only for root but as soon as I flash the module it bootloops on Google screen and have to uninstall magisk to get it to work
[Nexus 6P Original Android Development] frap129:
Fixed this, tomorrow's weekly should work fine

This is due to electron requiring the ROM to support f2fs as well. I've fixed this so tomorrows weekly should make all ROMs compatible with f2fs

See what I said above, should be fixed.

General announcement, I suggest testing tomorrows weekly build! I'm satisfied with build I'm running right now, so if this lasts through a few days of testing then tomorrows weekly will most likely be identical to v11
[Nexus 6P Original Android Development] Mrcactuseater:
I'm getting a lock up whenever I try and change the governor on this weeks lately through spectrum or EXKM. Also having some of the init.electron.rc settings not sticking, in particularly the io settings for maple.
[Nexus 6P Original Android Development] Mendrake:
Till now the new weekly build is stable and has less idle drain than v10. However I'm noticing that it introduced quite a long delay for fingerprint unlock to work.

Could this be a side effect of the improvements done to lazyplug?
[Nexus 6P Original Android Development] frap129:
I'll look into the governor issue. The I/O settings not sticking is due to the new IO Scheduler switcher driver, which changes the IO Scheduler to NOOP on screen off to save some more battery, which I'm looking for a fix for as well.

It could be, or it could be the new sleep commits or the new default profile. I'll look into a fix for this.
[Nexus 6P Original Android Development] shadowstep:
I was travelling over the weekend, just caught up with the v10 release & things-to-expect from v11. Just wanted to say thank you to you, [MENTION=5051294]frap129[/MENTION], for being on top of all the issues that have been reported for far & excellent turnaround time when it comes to fixing them. It's definitely not an easy task, so a BIG thank you to you! :)
[Nexus 6P Original Android Development] Mrcactuseater:
[MENTION=5051294]frap129[/MENTION] as judging by the recent releases and current kernel features, it is clear you like the cutting edge. For that, I was wondering if you could implement lz4hc algorithm? It is currently implemented in Jolla kernel, linked here: https://github.com/jollaman999/jolla-kernel_bullhead/find/android-7.1.2?q=lz4hc
[Nexus 6P Original Android Development] frap129:
I'll check it out, but I doubt I'll merge it. Decompression only matters at boot time, and a phone with a modern processor like ours is fast enough with gzip
[Nexus 6P Original Android Development] Mrcactuseater:
Would it not be better for the zram, or is it not meant for that use case?
[Nexus 6P Original Android Development] frap129:
Not really. LZ4HC is faster to decompress, but it takes longer to compress initially. Lz4 would be better for that
[Nexus 6P Original Android Development] frap129:
Thanks for the kind words and being a good user. I wouldn't have a reason to do all of this if it wasn't for people like you :p
[Nexus 6P Original Android Development] carguy303:
The new weekly is working out great for me. I would love to understand what the new changes are.
[Nexus 6P Original Android Development] larryatapproved:
Governors

Thanks for the great kernel! Been running v10 for awhile. Flashed the 5/8 weekly today. Wiped ex kernel manager, flashed the kernel, seems to run really well. I changed the governors from interactive to relaxed and chill. The phone ran for awhile, then shut itself off. Rebooted, phone was frozen. Had to reflash v10, wiped ex kernel manager, and reflashed the weekly. OK again. Happened twice, so it seems like the kernel doesn't like the other governors.
[Nexus 6P Original Android Development] adame09:
Not sure why it says flash kernel still in Spectrum. I reflashed my rom and flashed your kernel after. Is there anything else I need to do?

Do those stock settings look right?
[Nexus 6P Original Android Development] frap129:
No they don't. Remember to always reflash your rom before switching kernels
[Nexus 6P Original Android Development] frap129:
Could you get a log? I haven't been able to reproduce this issue, so I cant do much.
[Nexus 6P Original Android Development] adame09:
That's exactly what I did
[Nexus 6P Original Android Development] frap129:
[MENTION=6842057]The Flash[/MENTION] pointed out the issue to me, will be fixed in v11
[Nexus 6P Original Android Development] Pump Ac7i0n:
Data dropping while tethering, anyone else have this issue? Running great otherwise

Log attached
[Nexus 6P Original Android Development] mamba720027:
Great work on the V10 update,notice improvements in gaming esp UI response time. My device feels brand-new.

Looking forward to support a Pro version of spectrum.

The spectrum defaults and presets are nice and simple btw however I switched back to EXKManager to make small changes like turning off gestures,gamma controls n load my own CPU adjustments.

The upcoming changes sounds like great new improvements n additions. Keep up the great work and thanks for sharing your kernel.
[Nexus 6P Original Android Development] larryatapproved:
Can you tell me how to get the log? I'm not sure exactly what happens, if it turns itself off or just freezes and won't wake up. I did notice that

the battery dropped about 10% in between sleep and freeze up, so it was probably still on and using a lot of juice. With the interactive governors, it

uses very little battery at idle.
[Nexus 6P Original Android Development] frap129:
There is a link in the first post to a guide on getting logs and reporting bugs written by [MENTION=6842057]The Flash[/MENTION]. Has all the information you need
[Nexus 6P Original Android Development] frap129:
Seems like you were right about it being lazyplug. To fix it, I added back lazyplug's input boost but reworked it so that it only looks for fingerprint sensor input. Wakeup should be much quicker in the next build
[Nexus 6P Original Android Development] Mendrake:
Sounds great, looking forward to try the next build! :D
[Nexus 6P Original Android Development] kobos311:
People like him are few and far between now days :crying: I'm working on elementary OS currently but I will jump on board with this on my phone.
[Nexus 6P Original Android Development] infus38:
For me I have flash pure nexus, beans gaps magisk and elecontron kernel but the rom does not boot I just the animation of startup .i use f2fs
[Nexus 6P Original Android Development] frap129:
This is because pure nexus on its own does not support f2fs, and the kernel installation needs to patch the fstab. In the past (up to v10) I chose not to add my own fstab to ensure that rom changes dont get overwriten, however, v11 will include a fix for this
[Nexus 6P Original Android Development] Mrcactuseater:
[MENTION=5051294]frap129[/MENTION] here is a log i was talking about a while ago in regards to the device not waking up after changing the governor. https://docs.google.com/document/d/1VsXp9lnJVg1IfA8gIbS5vcrf9ozP7pso65jDBn05f-I/edit?usp=sharing
[Nexus 6P Original Android Development] larryatapproved:
Thank you! I haven't some time when I don't need the phone to let it freeze, but it looks like someone else posted a log about the same issue. I'll wait and see what that's about.
[Nexus 6P Original Android Development] frap129:
Could you get a dmesg? Logcats arent extremely useful for kernels
[Nexus 6P Original Android Development] Mrcactuseater:
Is this useful?
[Nexus 6P Original Android Development] frap129:
I reverted some changes made to the wireless driver from the O preview. Should fix your issue

I just finished fixing it, will work in the next weekly

Fixed!
[Nexus 6P Original Android Development] Mystique:
So I wiped /system, flashed my rom (GZR Tesla Angler latest build).. I have more progress but no success yet..

(edit) after four reboots.. I am looking at my desktop.. :)

https://pastebin.com/wCFLcNBR

I'll wipe everything again and see what I can do to get a logcat.. but tons and tons of errors..

Wifi works, but nothing registers traffic. EXKM shows charging..

*whew* we're making progress.. Thank you sir.

I spent a little more than two hours on this, this morning.. will try and find more time later to get actual logcats..
[Nexus 6P Original Android Development] frap129:
Glad that progress is being made! not sure if its because of old firmware, hardware, or what, but these are some freaky issues my friend.

In other news, I've made a driver that boosts CPU frequency to max when fingerprint sensor input is received, and made further tweaks to lazyplug to reduce lag. Fingerprint sensor should be as fast as ever in the next build!
[Nexus 6P Original Android Development] Mendrake:
Sounds great, can't wait to try out the next build!
[Nexus 6P Original Android Development] larryatapproved:
Thank you!
[Nexus 6P Original Android Development] carguy303:
Is there any use for the thermal-engine mods on this kernel? They were great on stock kernels but I seem to be getting similar charge speeds on Electron.
[Nexus 6P Original Android Development] shadowstep:
As long as you are satisfied with the charge speeds, I don't see why you should use any thermal mod. Remember, less is more. ;)
[Nexus 6P Original Android Development] blitzkriegger:
Hello [MENTION=5051294]frap129[/MENTION] I hope you are doing well and I thank you for gracing 6p with Electron :). I just tried the latest weekly build (05/15) and got stuck at the white Google screen. Some key details about my set-up are as follows:

Rom:Stock Factory image, May security update

Kernel used prior to flashing Electron:Flash (05/01 build)

Root:MagiskSu

File system:EXT4, Decrypted

Steps taken to encounter the issue:

1.) Reboot to recovery and flash stock factory boot.img

2.) Next flash Electron weekly zip

3.) Flash back Magisk then reboot system

4.) Waited ~ 3 minutes (As some of the magisk modules naturally delay the boot process) but was still stuck

5.) Reboot phone one more time and again waited but still got stuck at the google screen.

6.) Went back to recovery, flashed the log/dmesg/ramoops collector zip then repeated steps 1-3 this time using flash kernel.

7.) Was able to boot back to system

As mentioned in OP its understood that weekly Electron builds have no guaranteed support as those are bleeding edge stuff. Just wanted to drop in the dmesg/ramoops (attached) in case you find something interesting or useful in there.

Thanks and more power :)
[Nexus 6P Original Android Development] Mrcactuseater:
The latest weekly is running smooth as butter and if my battery want shoddy I'm sure it would be great! Thanks for the hard work!
[Nexus 6P Original Android Development] frap129:
Great bug report! I'll take a look at those logs as soon as my exams are over later this week.

I'm in the same boat, battery at 78% health according to AccuBattery