yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Original Android Development] HikingMoose:
That is great that you explained one reason why the stats were so good - your usage pattern. Usually when someone comes out of the woodwork with an 8-10 SOT claim, they act like they didn't do anything special to achieve it. They say they just used the phone like normal with data on and whatnot.
[Nexus 6P Original Android Development] moi123:
Would GMS+ be similar to using AppOps to prevent Google Play Services from waking and running in the background ?
[Nexus 6P Original Android Development] Face_Plant:
I saw no point in trying to hide it or lie, so I didn't. It's kind of sad that I could stare at my phone that much in one day, but for medical reasons I was stuck on the couch all day and needed something to pass the time.

I've never used AppOps, so I'm not sure how they would compare.

Doze for GMS basically prevents Google Play Services from being whitelisted in the battery optimization settings so it can be "dozed". The plus version restricts background data for Google Play Services while it's being "dozed". The plus version does save a little bit more data/battery, but push notifications are delayed until I turn on the screen, or sometimes I don't receive them at all, which is annoying. Text messages/calls still work fine since they don't use push notifications, but I'll get emails hours after they've been sent, or notifications from the XDA app will never show up, etc.

There's more information available in the thread for the module:

https://xdaforums.com/apps/magisk/module-enable-doze-google-play-services-t3608783
[Nexus 6P Original Android Development] DEVILOPS 007:
[MENTION=5051294]frap129[/MENTION] Hi there, I've been testing Paranoid Android with Franco kernel and when I reboot my phone the date and time takes a minute to update and usually says 1st January 1980 on your electron kernel but with Franco kernel it updates almost instantly. Any ideas why or if I could get you a log because I'm sure it is something to do with your kernel and date and time updating. Thanks.
[Nexus 6P Original Android Development] frap129:
Electron is not AOSPA compatible, they use a customized kernel in stock
[Nexus 6P Original Android Development] DEVILOPS 007:
Then what does that mean exactly? Do you know what kernels support AOSPA? Thanks.
[Nexus 6P Original Android Development] -Deco-:
It means AOSPA use their own custom kernel - not the stock kernel which exists in other ROMs. (Lineage, AOSP etc).
[Nexus 6P Original Android Development] bobby_digital234:
I wanted to ask if anyone else has random lockups and freezing when using this kernel. It only happens when I use exkernel manager to make changes but I'm curious if I'm the only one. I can pull a log next time it happens if others also feel they have a similar issue. Exapmple would be getting a phone call and screen is unresponsive upon trying to answer along with lag changing from visible to screen off to back on while on call
[Nexus 6P Original Android Development] frap129:
As the first sentence in the OP states

.

As an update: I just need to do some more testing before v15 is ready. Made some more changes today that should help out both performance and battery life. v15 should be up by the weekend if all goes well
[Nexus 6P Original Android Development] ART:
Does choosing which governor for the cores count as tweaking?
[Nexus 6P Original Android Development] frap129:
The kernel does that on its own via the presets and Spectrum. Obviously I'm not going to drop support just because you changed the gov, but yes that does count as tweaking
[Nexus 6P Original Android Development] ART:
So the recommended way to go is to go through spectrum and it's profiles?

I've been using ex manager till now.

Also, which profile uses the electron governor? Is it the battery profile in spectrum? Also, do the profiles stick on reboot?
[Nexus 6P Original Android Development] frap129:
Currently no profiles use the electron gov, so if you want to use it you'll have to set that up yourself. Profiles do stick on reboot.

Also, to anyone who enjoys weeklies, I restarted them now that voltage-control has been abandoned. If you want to help test my latest changes (and likely the final v15), a new build is up and ready to flash!
[Nexus 6P Original Android Development] inimaitimepass:
My suggestion would be, don't use any profiles. This kernel comes with Chill/Relaxed governors as default, but for some reason I found Electron governor to be the best. Just stick with either one of them and forget about profiles.
[Nexus 6P Original Android Development] Face_Plant:
I'm using EXKM with this kernel and experience no issues, even after changing a few things. What sort of things are you changing?
[Nexus 6P Original Android Development] bobby_digital234:
Just govorners to interactive like I said I'm just curious I very well could be the only one with this issue

---------- Post added at 05:20 PM ---------- Previous post was at 05:18 PM ----------

It happens most when I just flash the kernel... It's more like a wake-up issue than anything else
[Nexus 6P Original Android Development] ART:
I don't use profiles like I did with ElementalX. The default seems nice. Also, do you use electron governor on both CPU and CPU (big cluster)?
[Nexus 6P Original Android Development] inimaitimepass:
Yes.
[Nexus 6P Original Android Development] Face_Plant:
Did you install the kernel on top of another custom kernel? When in doubt, try a clean install of the kernel:

1. Extract the boot image from your ROM

2. Clear data for EXKM

3. Reboot into TWRP

4. Select "install"

5. Select "image"

6. Find where you extracted the boot.img from your ROM

7. Select it and when TWRP asks which partition to install it to select "boot"

8. Install Electron

9. Optional: install your root method of choice (Magisk, SuperSU, etc)

10. Wipe cache/dalvik

11. Reboot
[Nexus 6P Original Android Development] bobby_digital234:
Definitely did a clean install. I always clean flash even for room updates I'm picky like that. I'll get a log next time it happens and hopefully it's just an app I'm using or something.
[Nexus 6P Original Android Development] Mrcactuseater:
[MENTION=916904]Frap[/MENTION]123 facing a strange issue with the latest weekly. With sRGB mode on, the screen colours seemingly shift colour when I touch the screen or interact with it. Can provide logs when I get home!
[Nexus 6P Original Android Development] frap129:
I noticed that when messing with kcal as well, I think I know what's causing the problem
[Nexus 6P Original Android Development] Mrcactuseater:
Spot on man, thought I was going nuts and seeing things!
[Nexus 6P Original Android Development] Mrcactuseater:
Double posts oops
[Nexus 6P Original Android Development] HikingMoose:
I'm willing to test it. Just been sitting in a hospital room all week because we had a baby. Get to go home Friday. Bored.
[Nexus 6P Original Android Development] -Deco-:
It will be a gesture that is waking up your device or the fingerprint sensor, ensure no gestures are enabled in EXKM or in your ROM settings. (Wakeblocks can be blocked via EXKM)

I would also recommend to check if it is unlocking upon waking, if it is you can bet its the fingerprint sensor waking up the device.
[Nexus 6P Original Android Development] larryatapproved:
I've been running the latest weekly last night and all day today, no problems, no lag. I have double tap and swipe up to wake, no fingerprint. Wakeblocks are blocked in EXKM and also using Wakeblock. Other settings are exactly as flashed. This kernel seems to have the best battery life also.
[Nexus 6P Original Android Development] frap129:
v15 is up, go wild! This is most likely the last release of electron that will be for Android 7.x, so keep that in mind. Changes in this release include:

August Security Patch

Custom PowerHAL

Shadow Scheduling

FS updates

Reduced CPU Load

Optimized string routines

Improved Input Boost settings

Download: https://www.androidfilehost.com/?fid=673368273298979550
[Nexus 6P Original Android Development] mrcooter:
Does this release have the sRGB fixed? I know you said that you thought you knew what was causing it from the recent weekly.
[Nexus 6P Original Android Development] frap129:
Yep! No issues on my end with sRGB or KCAL
[Nexus 6P Original Android Development] DEVILOPS 007:
Congrats on the baby!
[Nexus 6P Original Android Development] mdfarazb2:
Wow.. Thanks!
[Nexus 6P Original Android Development] infus38:
Hello for me on purenexus, I prefer v14 to v15, all is more fluid on v14 , Thank you for this update ;)

Bye :)
[Nexus 6P Original Android Development] mikeygeer:
Trying to read about what this "Shadow scheduling" is - I am unable to find this anywhere through searching xda and google. Anyone?
[Nexus 6P Original Android Development] Nekromantik:
Anyone else find new v15 battery save profile to be slightly laggy in UI verses v14?
[Nexus 6P Original Android Development] -Deco-:
Documentation for it can be found here: https://drive.google.com/file/d/0BwhYqCitX_UTdERBYWowLWZ0bXM/view?usp=drivesdk
[Nexus 6P Original Android Development] frap129:
darn

It should have more battery savings than before which is resulting in lag, but as always, I still recommend the balance profile.
[Nexus 6P Original Android Development] Nekromantik:
Ah ok.

Does that mean balanced profile also will be more battery friendly then v14?
[Nexus 6P Original Android Development] frap129:
Yep, much better in my testing.
[Nexus 6P Original Android Development] inimaitimepass:
Chill/Relaxed aren't default governors anymore? Just curious, Any reason why Interactive as default instead of Electron?
[Nexus 6P Original Android Development] frap129:
Chill and Relaxed are default, you must have something overriding it
[Nexus 6P Original Android Development] sapphirecoupe:
Still unable to disable fsync...
[Nexus 6P Original Android Development] phantom146:
I am itching to try this.. But I must.. Wait...

Cause I don't wanna mess up my setup.. Not yet... :p
[Nexus 6P Original Android Development] preference:
It's the most reliable kernel I've used, and I've tried 4 so far.
[Nexus 6P Original Android Development] inimaitimepass:
Default Governor?

hmmm.. I was on franco kernel and before flashing electron, I extracted the boot.img from carbon and fastboot flashed it, rebooted and then installed electron. Guess that's not enough, will try flashing the ROM and report back.

Update:

Dirty flashed the ROM, GApps and rebooted then flashed Electron Kernel. Cleared data of EX and FK apps. They both still show Interactive as the default governor. :confused:
[Nexus 6P Original Android Development] phantom146:
We have the same situation. I guess a dmesg could help [MENTION=5051294]frap129[/MENTION] to check the problem.

I also experience low frequency lockups on big cluster. Weird enough is that the lockups disappear when screen off. Have you by any chance used powersuspend instead off screen state for electron?

EDIT: l'd let the kernel settle in for a day and see if the lockup will dissipate. If not, tell me what you need so I can provide you with something to debug this.
[Nexus 6P Original Android Development] -Deco-:
The CPU big cluster's max CPU clock speed is reduced during charging to prevent excessive heat, it works wonders. I've personally set the lowest clock speed to 302MHz and have increased the thermal throttle value to 60 degrees.
[Nexus 6P Original Android Development] HikingMoose:
Carbon doesn't come with electron kernel, so that's why the boot.img from carbon didn't get you what you wanted.
[Nexus 6P Original Android Development] inimaitimepass:
You didn't read my post clear enough I think.

I'm very much aware of it.
[Nexus 6P Original Android Development] Neejay:
What's the difference between thermal throttling and msm_throttling? Due to this being angler, I'm scared to mess up anything related to the battery and heat.
[Nexus 6P Original Android Development] Face_Plant:
The thermal throttling value (a temperature in Celsius) tells msm_thermal when to kick in.

For example, let's say you set thermal throttling to 55. That means when the CPU temperature reaches 55°C msm_thermal will kick in and reduce the CPU speed until it cools down.

Another temperature control algorithm you may have seen is core_control. It shuts down the big cores when the CPU reaches wherever thermal throttling temperature you've selected rather than just reducing its speed.
[Nexus 6P Original Android Development] Dbj.Dhaval:
With the latest update the big core is locked at min frequency no matter which gov I choose
[Nexus 6P Original Android Development] phantom146:
Same
[Nexus 6P Original Android Development] -Deco-:
Really? It shouldn't be, Electron governor seems to act like a mix of chilled and interactive - that is if no heavy tasks are detected the big CPU clusters will be locked to the minimum frequency with the smaller cores ramping up which makes sense.

If I start a heavy duty task the big cluster will automatically scale itself accordingly, it's a rather interesting way of cutting down on battery usage which does the job well.
[Nexus 6P Original Android Development] phantom146:
I already did a clean flash twice to no avail, maybe I need to nuclear flash (back to stock with stock recovery) to see if there's something wrong. I doubt that electron is causing it, [MENTION=5051294]frap129[/MENTION] do you need something to debug this? I'd provide you logs
[Nexus 6P Original Android Development] frap129:
Not a bug, thanks to Shadow scheduling the big cluster is only used under heavy load
[Nexus 6P Original Android Development] HikingMoose:
I've had issues before when no matter what kernel or settings I changed, I kept getting bizzare behavior. It took me a day to clear it up. I had wiped data for exkm, and reset it, I tried uninstalling it after resetting it. Rebooting after uninstall and then reinstall - it somehow kept the settings through all of that. I can't remember if I had to wipe and reflash the ROM or not. I may have wiped app data, uninstalled, and then gone to recovery and wiped dalvik and partition cache, and reflashed stock kernel. Then flashed the custom kernel.

Worth a shot anyway. But as frap just posted, the big cluster should kick on less (but I'm guessing it shouldn't be locked at minimum).
[Nexus 6P Original Android Development] ART:
[MENTION=5051294]frap129[/MENTION] The little and big clusters are supposed to be relaxed and chill respectively right?

Also, have you done anything to the kernel to improve boot times? I've tried Franco, flash and ElementalX and once I flashed this kernel, it boots up quite fast even after a dalvik cache wipe.
[Nexus 6P Original Android Development] Lawlrus:
I've been running V15 off and on since release, and I gotta say it runs pretty damn well. Seems like this build hit a benchmark for how well it runs. It just keeps on getting better, ace work [MENTION=5051294]frap129[/MENTION]
[Nexus 6P Original Android Development] ART:
Electron is an angler specific kernel right ?
[Nexus 6P Original Android Development] Lawlrus:
This thread here? Yes. If you don't see his thread posted in other devices, I would venture to say it's not supported
[Nexus 6P Original Android Development] ART:
Yes I tried searching for it for other devices like the pixel and OnePlus. Unfortunately I couldn't find it.

Also, v15 is more than worthy of being the final build for Nougat! Outstanding stats so far. , I've seen screenshots of stats like these only on current, more efficient flagships like the htc u11 , pixel, op5.
[Nexus 6P Original Android Development] Lawlrus:
Agreed, frap is doing an awesome job.
[Nexus 6P Original Android Development] frap129:
Huh, what's going on here?
[Nexus 6P Original Android Development] frap129:
Sorry for the confusion, only v1 was for marshmallow. Although I will be releasing a nougat rom sometime this week, so if you havent made the switch already you can soon ;)
[Nexus 6P Original Android Development] xSilas43:
I actually just switched back cause my N battery was around half my MM battery life haha but this was before official images finally dropped. I assume this kernel will be baked in? Ill definitely give it a flash though :svetius:
[Nexus 6P Original Android Development] frap129:
Because of the ramdisk changes implemented by Electron, the kernel won't be baked into the rom, that way users can use whatever kernel they want without it being interfered with
[Nexus 6P Original Android Development] frap129:
For anyone who wants to become a tester, the latest test version features MSM Hotplug and some various improvements. Features that *should* be in the next release version are

MSM Hotplug (Hexacore mode)

DragonX Interactive profile instead of GlassFish

KSM (With backports from Linux 4.7)

Misc CAF patches and improvements

Ideas and recomendations are welcome!
[Nexus 6P Original Android Development] xperator:
Sounds cool

Which version of DragonX did you use ? You know it's a kinda experimental profile at the moment so until I make it perfect it might change a lot
[Nexus 6P Original Android Development] frap129:
I havent added it yet, currently I'm testing AlphaBat116, but after reading comments comparing the two and some reviews of DragonX, It definitely looks like the way to go. If you have a different recommendation for moderate use with good battery, I'd be glad to take a look.
[Nexus 6P Original Android Development] xperator:
Excalibur V2 is also worth looking at. It is snappy and has good battery life. But people are so obsessed with battery life that they prefer conservative profiles over these balanced ones.

With DragonX I'm hoping to find the perfect sweet spot between battery and performance that can favor everyone.
[Nexus 6P Original Android Development] frap129:
I'll take a look at Excalibur. Looking forward to that sweet spot with DragonX (once you find it that is)
[Nexus 6P Original Android Development] frap129:
New test version is up! From now on, testing versions will be open to the public through the Google+ Community linked in the OP.

Changes include:

- MSM Hotplug (Hexacore mode)

- Excalibur V2 Interactive Profile

- Disabled wlan Wakelocks

- Backported KSM from Linux 4.7

- Enabled KSM with optimized config

- Disabled swap and ZRAM

- Many CAF patches

Please report the impact on performance and battery relative to release 3! I've noticed slight lag on keyboard popup animations and slightly better battery, a decent tradeoff IMO

https://plus.google.com/+JoeMaples/posts/FwaUiorrwmt4
[Nexus 6P Original Android Development] winxuser:
Cant wait to let this kernel settle down, just flashed it.. but using kernel auditor and ex kernel manager I don't see an option for hotplugging, is that option to chnage it been disabled?? Is msm hotplug defaulted turned on??
[Nexus 6P Original Android Development] nathanchance:
Yes, hotplugging is enabled by default but you should see the option to disable it. Try clearing EXKM data.
[Nexus 6P Original Android Development] winxuser:
Hmm no clearing the data didn't work. No bother though
[Nexus 6P Original Android Development] RollTribe:
For some reason, I can't see the option for wake gestures in EXKM after installing this kernel. Is there another app that I should be using?
[Nexus 6P Original Android Development] nathanchance:
Looks like wake gestures didn't make it back in for N, probably something to add [MENTION=5051294]frap129[/MENTION]

https://github.com/frap129/angler/commits/dev/ng/drivers/input/touchscreen
[Nexus 6P Original Android Development] RollTribe:
Ah okay, I saw it in the OP so that's why I asked. Great kernel nonetheless
[Nexus 6P Original Android Development] frap129:
This kernel doesnt have hotplugging. If you mean the testing version, please keep discussion of that to the google plus community so I know thats what youre talking about.

The kernel doesnt have hotplugging as of v3

[MENTION=6842057]nathanchance[/MENTION] is right, I thought I added that but I must have missed it. Should be added in the next release
[Nexus 6P Original Android Development] frap129:
V4 uploaded! V5 should be out within a week with some interesting changes
[Nexus 6P Original Android Development] jr313:
Will you by chance be adding volume boost changes in your kernel?
[Nexus 6P Original Android Development] Balino:
V4 working correctly on 7.1.1 preview. Photos aren't dark at all

Inviato dal mio Nexus 6XL utilizzando Tapatalk
[Nexus 6P Original Android Development] Upstreammiami:
Where is the link?
[Nexus 6P Original Android Development] shantam3108:
Something confidential :confused:
[Nexus 6P Original Android Development] Neejay:
Carbon ROM Oreo lol
[Nexus 6P Original Android Development] deani77:
[MENTION=5051294]frap129[/MENTION] teasing us with Carbon for Oreo...
[Nexus 6P Original Android Development] ART:
Entirely coincidental that you gave us a glimpse of Carbon Oreo on New Build Tuesday. ?
[Nexus 6P Original Android Development] iamreinvented:
Twinsies
[Nexus 6P Original Android Development] frap129:
I meant to tease Electron for 8.0, but at least you all noticed Carbon
[Nexus 6P Original Android Development] iamreinvented:
Seems to be....... quite a development

And lol. The versionCode was still 15 for electron so it likely went over everyone's head (myself included) due to the hype of Oreo being so close. People forget how important kernels are!
[Nexus 6P Original Android Development] inimaitimepass:
Had a look at the change log. The SystemUI tuner has been enabled by default in CR6.0. But does it have navbar tuner? Coz some users are reporting that navbar tuner is missing with stock Oreo!
[Nexus 6P Original Android Development] frap129:
Yep, it's there. Google disabled navbar tuner for production builds, but it's been readded in Carbon
[Nexus 6P Original Android Development] Neejay:
That's exactly what it was for me. Lol
[Nexus 6P Original Android Development] deani77:
Current v15 work on Android 8.0... I had not try it yet...
[Nexus 6P Original Android Development] frap129:
No, it doesn't. The version number is still the same just because I'm testing. I think it's mostly stable, so as long as battery is better than stock I'll probably release next week!
[Nexus 6P Original Android Development] Neejay:
Sweet. Yeah, I just tried it before seeing this post and I just didn't have cell signal. Booted up and was working though. I look forward to trying the new version!

No testing versions before hand?
[Nexus 6P Original Android Development] frap129:
Well, in an attempted to get more storage space on my server to complete a rom build, I may or may not have deleted my Jenkins configs :eek: so if I get around to rewriting it, I'll push a test build
[Nexus 6P Original Android Development] yung40oz84:
F@#k my life, is source up yet, I'll gladly build me some Carbon and Electron ???

---------- Post added at 07:06 PM ---------- Previous post was at 07:05 PM ----------

Imma build the kernel when I get home see how it's running on big ol' Oreo, lol
[Nexus 6P Original Android Development] Neejay:
I should probably go ahead and do this too. I love building a ROM and kernel at my convenience.

[MENTION=5051294]frap129[/MENTION] is it buildable to the public?
[Nexus 6P Original Android Development] yung40oz84:
I already built the kernel, haven't flashed yet. Branch is dev/or and up to date.
[Nexus 6P Original Android Development] yung40oz84:
Thanks for the love on 8.0!
[Nexus 6P Original Android Development] Neejay:
Meh, guess I'll be waiting. I was trying to adapt the guide from The Flash ( https://github.com/nathanchance/Android-Tools/blob/master/Guides/Building_Flash.txt ) to electron, but I got stuck. Guess I'm more of a n00b than I thought. lol
[Nexus 6P Original Android Development] frap129:
I'm probably going to redo the kernel from scratch (or just [MENTION=6842057]The Flash[/MENTION] base branch). This build was pretty much O merged into my old tree, and I'm not really digging it
[Nexus 6P Original Android Development] yung40oz84:
That's the guide I used as well. Follow that guide and also open up the build file or script in electron and compare, that's what I did.