yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Android Development] :
So I've been hard at work most of the night moving things around...

Nav Drawer

: Added the image from the OP as the background image. I like how it gives the feel of this kernel.

CPU: Input Boost

- Added an enable/disable switch, hid the options for it based on it's status

Thermal

: Made the thermal stage descriptions dynamically tell you the temps that they'll trigger based on your settings.

Misc

: Moved the wakelocks toggles to their own tab.

Misc

: Made the battery tab "Power and Battery" and moved the power stuff to there... I didn't like how crowded the misc tab was getting.

Downloads

: I had a hack in place for in-app downloads. Fixed this to use proper methods. This means that for the folks that want this to work in "settings" of the roms that include that for K.A., you can use any apk manifest modifying tool to change the package and name back to "com.grarak.kerneladiutor" to force this to be recognized as the official package without breaking anything. (no I wont do that by default....)

Basically, random clean-up changes to make things "feel" better.

I'm still going to be working on this more tomorrow before I do a release... But this is where I'm at so far. Probably more misc cleanup, maybe re-organize the Nav Drawer. I dunno, we'll see where it ends up.
[Nexus 6 Android Development] DigitalPrinceX:
Hello,

After installing this Kernel i found a process named hwrng which is constantly keeping my CPU busy at higher frequencies. I tried to force kill the process but it reappears anyway.

It disappeared when i reflashed stock kernel.

Can anyone explain what it does and how to make it go away if I desire?

I am using Fluence HD 7 rom, previous kernel was stock kernel.
[Nexus 6 Android Development] :
It looks like maybe something that we were trying to use to boost the entropy pool might be misbehaving.

Though, while I have this process, it's CPU time is essentially 0.
[Nexus 6 Android Development] apophis9283:
We just switched hosts, op has been updated as has in app but im about to bump to a newer release
[Nexus 6 Android Development] apophis9283:
OP and in-app downloads have been updated to V-4.4. Enjoy

Using a new host so please report any issues
[Nexus 6 Android Development] RngrYogi:
Hey Guys! This is the second time I am trying to get the Singularity Kernel to work and I keep having problems with my max cpu freq sticking and reverting to around 19xx Mhz after running great for a few mins after install, with 88xxx AnTuTu score. When I try to change the freq back to 2649 Mhz it just reverts. I don't seem to be having any thermal issues and kernel settings in the auidtor app are left at stock or reverted to stock after tinkering with a few things so I am unsure how to get it fixed. Any advice? :confused:

I am on the newest released versions of the kernel and the auidtor.
[Nexus 6 Android Development] apophis9283:
Shut bcl off
[Nexus 6 Android Development] apophis9283:
FYI Antutu is crap and worthless
[Nexus 6 Android Development] RngrYogi:
Ok good info thanks. Rebooting now to test blc off. Removing Antutu. lol Any good bench app out there that can help me test between kernels or roms and there settings to see if they are helping or hurting general user experience?

---------- Post added at 07:38 PM ---------- Previous post was at 07:35 PM ----------

CPU Freq is still instantly reverting to 1958 mhz with bcl off. Happened on the previous version I flashed just about a week ago too. I am on Chroma Rom. Only way to fix it is to reflash chroma which overwrites the kernel and reflash Singularity. Then it only seems to last until I move any setting in the auditor then it begins behaving like this. Only other changes I have made is Aduitor is in dark mode and I tried MSM Limiter but it will not lift the limit of 1958mhz. And as the other fellow said my cpu usage and up clocking seems to be VERY busy. NO cores ever unplug to rest.
[Nexus 6 Android Development] :
It's recommend geek bench if you're trying to get a more reliable number for comparison.

Can you send me the file at

/data/data/com.singularity.kerneladiutor/files/commands.json?

Sent from my Nexus 6

If I've helped you, don't forget to hit thanks!
[Nexus 6 Android Development] LunaticSerenade:
Kernel is running great, however the governor always reverts to interactive_pro on reboot. Any idea what could cause that?
[Nexus 6 Android Development] RngrYogi:
Here Ya go!:highfive:
[Nexus 6 Android Development] :
Yeah, it's the default governor.

At what you want in ka, and tick apply on boot.

If that's not work, read the red text in post #2 of this thread.

Sent from my Nexus 6

If I've helped you, don't forget to hit thanks!
[Nexus 6 Android Development] RngrYogi:
Do you have apply at boot turned on above the page you changed the governor setting on?
[Nexus 6 Android Development] :
I don't see anything in there that looks like it would cause the issue you're having.

You said that its always 1.95ghz?

And that shows as max freq, or just what is scaling to on the bars?

Sent from my Nexus 6

If I've helped you, don't forget to hit thanks!
[Nexus 6 Android Development] RngrYogi:
it is only hitting 1958 max on the current freq bars. untill we can figure it out im going to reflash chroma then try to reflash singularity and not change anything even once in kernel auditor and see how it acts for me. And no I am seeing the max 3.03ghz in the menu but when i change it to anything above the 1958 it reverts instantly.
[Nexus 6 Android Development] apophis9283:
you have input boost on?
[Nexus 6 Android Development] RngrYogi:
Everything there was stock. I did not change any setting there. I did see wake boost was on. but I never turned any other setting on having to do with input boost. So far I have tried a combo of situations having to do with standard kernel adiutor and the singularity moded one and I get the same results.. I now have both adiutors uninstalled and checked freq with adia64 and they seem to be hitting stock max freq fine.. is so wierd.

---------- Post added at 09:12 PM ---------- Previous post was at 09:07 PM ----------

i take that back even with no adiutor installed it still finally reverted right after a geekbench test.
[Nexus 6 Android Development] :
In Aida, you're seeing 300-3033 for the range, then the cpu is getting stuck at 1958?

Can you try changing governors and see if that makes a difference? I'm using umbrellacore and don't have that issue.

Might be something in the governor that we need to look at.

Sent from my Nexus 6

If I've helped you, don't forget to hit thanks!
[Nexus 6 Android Development] RngrYogi:
I am seeing that range yes. Battery has been in 30 to 25% range now while checking. I will try umbrellacore and reboot but i switched it to umbrella a little while ago and it made no difference but I did not reboot at that time. Ahh ok here is some info! when plugged into charger the restriction lifts and it reverts to stock 2649mhz and i can select up to the 3ghz and it sticks. Could a setting be doing this that limits the freq at a low battery level under 40% or so from anywhere else in android?
[Nexus 6 Android Development] :
That, I wouldn't know about. Chroma may have a battery saver function built in, but I don't use chroma so I don't know.

Sent from my Nexus 6

If I've helped you, don't forget to hit thanks!
[Nexus 6 Android Development] RngrYogi:
ok well I appreciate your help thank you for being very responsive and trying to help me out. i will keep looking into the situation and let you know if i find out what's going on.
[Nexus 6 Android Development] LunaticSerenade:
Yeah, I have apply on boot selected.

I switched it to 20 seconds, so we shall see what happens.

In any event, the kernel is still great. :)
[Nexus 6 Android Development] RngrYogi:
Seems limiting the cpu by default after phone dropping to or below 40% battery is a "feature" of Marshmallow.

I'd love to figure out how to edit or disable this to get my max performance if I want it untill the battery is say dead or at 10% i would think 40% is a bit high for a lot of users but I do agree that it offers extended runtime but not being able to control it is pretty disappointing as far as 6.0 goes.

If anyone else happends to experience this please let me know.:highfive:
[Nexus 6 Android Development] apophis9283:
Turning off bcl in the kernel and finding the options for your battery in said rom, should allow you to stop it. I know mine doesnt do any of that
[Nexus 6 Android Development] KonoeKyon:
Actually they removed that in marshmallow, the 40% throttle was in lollipop 5.1 and dropped CPU to 2265MHz. Marshmallow doesn't throttle like that until under 20% now. What you are seeing is the BCL driver kicking in. Which tends to do so a lot more when at lower battery levels. You main issue is benchmarking at a low battery level. The driver is meant to prevent the CPU from drawing more power than the battery can provide, in turn causing the phone to crash or shut down unexpectedly. Next time you benchmark make sure you have 80%+ battery left to prevent that from happening, or turn off BCL and hope you don't get instability from it.

If you want to see what % battery the phone does the throttling you thought you were seeing, check the thermal-engine-shamu.conf file in /system/etc/, in marshmallow it drops to 1728MHz at 19% and unplugs a core at under 15% and another under 8%.
[Nexus 6 Android Development] str8str:
You can also in zen hot plug settings in kernel auditor drop the frequency down a bit I'm battery threshold ignore to like 8 or 10 which can help at lower frequencies so you can still get the extra boost from all cores till the last possible percentage but will use more battery
[Nexus 6 Android Development] LunaticSerenade:
So, just had a random reboot, and with 20 seconds, the governor didn't stick.

I'm not concerned about the random reboot (they happen).

Changed the settings to 40 seconds, so we'll see.

I also think I might clean install with the next kernel update. The ROM is being a little funky, and a clean install fixes everything.
[Nexus 6 Android Development] BeDesireS:
I just faced the same behavior.

First of all, I am only using this kernel since 2 days for the first time and I have to say it's really a fantastic piece of work. Well done guys!

But I just noticed the same cpu frequency limit to 1958 if you go below 40% and 1728 if you get under 20 % battery.

Disabling BCL doesn't help and its not related to the governor. I am using latest AOSiP.

Maybe someone can find a solution for this!?

Anyway, keep up the good work guys!

Send from my AOSiP powered Nexus 6
[Nexus 6 Android Development] :
Id look in your roms battery section, maybe in the 3dot menu.

I really suspect that you guys are seeing some rom side battery saver kicking in.

*edit*

As I don't use the roms that you guys have mentioned, this is what PureNexus's battery saver looks like (accessible from the battery section).

If yours is enabled... Its a rom issue, not kernel.

Sent from my Nexus 6

If I've helped you, don't forget to hit thanks!
[Nexus 6 Android Development] BeDesireS:
Mine is set to turn on at 5% only.

But I disabled it completely now and see how it goes if my phone comes to the 40%. I'll keep you posted.

Thanks for your support!

Send from my AOSiP powered Nexus 6
[Nexus 6 Android Development] str8str:
I double checked mine and I have it set to never and my frequencies perform as they should
[Nexus 6 Android Development] apophis9283:
Brought back the 3.09 frequency as someone had asked for. Arch Power is OFF by default to conserve more battery. GPU can idle at 25MHz now. Raised suspend max frequency to 1190 to conserve battery.
[Nexus 6 Android Development] BeDesireS:
Ok guys. I figured out its really an issue of the battery saver. If you enable it, no matter of what percentage you choose, it starts limiting the frequencies if you go below 40%.

I deactivated it completely and after a reboot everything is fine!

Thanks for help guys! I am really enjoying this kernel!

Send from my AOSiP powered Nexus 6
[Nexus 6 Android Development] :
Yeah, that's what I figured. You should report it in your roms that that is not actually using the value you set it to.

Though, with the aosip team downsize they had recently... It may take a while to get fixed. But at least you narrowed it down.

Just to preempt anymore of these frequency posts...

Sent from my Nexus 6

If I've helped you, don't forget to hit thanks!
[Nexus 6 Android Development] BeDesireS:
I am not sure if it's really a rom bug or just like Google wants it to be. Don't know.

I am a member of the AOSiP test team and already told them. We will see.

Thanks for your support!

Send from my AOSiP powered Nexus 6
[Nexus 6 Android Development] str8str:
Love the pic
[Nexus 6 Android Development] :
The battery saver implemented by Google is likely variable steps like 40%, 20% and 10%.

If the rom has the option to change it to something else and it doesn't actually change it, it's a bug.

Keep in mind that the battery saver didn't just limit freqs. It also disables background data and all sorts of other goodies.

Personally, I just use tasker when I want to do that sort of stuff. It does exactly what I want when I want and only what I want. Sometimes the rom feature is on its own agenda.

Sent from my Nexus 6

If I've helped you, don't forget to hit thanks!
[Nexus 6 Android Development] mwebb34:
Core 2 & 3 & 4 are offline while browsing. Experiencing some lag. How do i fix this

---------- Post added at 06:13 PM ---------- Previous post was at 06:10 PM ----------

Think i fixed it I had schedualed workquesus on awake enabled, i turned it off. Which cpu governers should i be running?
[Nexus 6 Android Development] apophis9283:
Anyone else feel like spider-man after walking through their house in the dark and not running into anything?
[Nexus 6 Android Development] nazfalas:
I've been testing this for a while now, because I didn't want to post something that was an error on my side or completely a ROM problem and I have the following problem:

During (video) media playback, especially when playing larger files or streaming them over my local network I experience hangs after a while.

This occurs more quickly when skipping through the video more often.

For example when I play a movie (e.g. The Matrix, 1080p, MP4, x264) VLC, MX Player or the regular gallery video player just hang. Status bar stays responsive, but the nav bar becomes almost unresponsive until Android presents an option to close the app.

Afterwards media playback becomes impossible across the system until after a reboot. This happens more readily on larger files, but after a while also on smaller ones when seeking in the video.

The same happens with Twitch when I switch between streams or resolutions.

I have tried this with different kernels (stock, lean, blackbird, hydra) and none of them show this issue. I have only used CM13 based ROMs. The problem goes away with other kernels, though.

Using stock settings except for wake controls (DT2W).

I have tried different governors, schedulers, disabling KSM, ALMK, hotplugs, etc)

Any idea?
[Nexus 6 Android Development] apophis9283:
Well, Ill look at it tomorrow. Seeing the issue, I dont imagine it would be too hard to track down
[Nexus 6 Android Development] rignfool:
It may be crap for quantifying performance... But it is great for stressing the phone while testing kernel settings...

---------- Post added at 09:49 AM ---------- Previous post was at 09:45 AM ----------

That's Dare-Devil...

Not Spiderman...

Now if you walked thru a room with Legos on the floor and didn't step on one... That would be Spiderman ?
[Nexus 6 Android Development] str8str:
Don't know if this will help but I'm still on 4.3 and this version runs like a dear. I hadn't had one reboot battery is great and I have no issues like mentioned above. I don't wantt to change versions. Lol. But could be something implemented after. Just sayin
[Nexus 6 Android Development] BeDesireS:
Beside my little frequencies issue, which was not kernel related, I am fine with 4.4.

No reboot or anything else. Only thing I had was the max set to 3.033 Mhz. but I could solve this by cleaning all data of kernel Adiutor. Maybe some leftover from my old original ka install.

And arch is still activated on stock settings for me.

Beside of this the kernel is running great and battery is fantastic.

Send from my AOSiP powered Nexus 6
[Nexus 6 Android Development] apophis9283:
Uncheck on boot for evry section in KA then reboot. It will go to stock settings
[Nexus 6 Android Development] BeDesireS:
No. It didn't. I tried this method first and booted up with 3.033 Mhz. Only clearing data of KA solved it.

That's why I think it could be some leftover data from the original KA I had installed before.

Send from my AOSiP powered Nexus 6
[Nexus 6 Android Development] str8str:
Yes that will cause it I had to make sure I didn't have the other kernel auditor installed and all data deleted as well cause im on Bliss rom which has it built in
[Nexus 6 Android Development] :
Wrong

Right-ish

Wrong

So. To clear up the confusion here.

The two versions of ka, mine vs official won't affect each other's data or settings at all. They can't, as android only allows each access to its own data directory. If they're both set to apply on boot, that action can cause conflicts.

Unchecking apply on boot doesn't actually delete any settings. It just stops running them. The only time that ka adds, removes, or changes a setting in its database is when you actually change it in the app. I'm thinking of ways to present a list for the user to delete individual things, but my time is getting tied up in rl stuff right now.

The only way to completely remove the stored settings is either clear the app data or delete /files/commands.json in the app data directory.

Sent from my Nexus 6

If I've helped you, don't forget to hit thanks!
[Nexus 6 Android Development] apophis9283:
I have a 5 year old (apophis jr). He doesnt leave his Legos on the ground anymore. Damn things are like land mines.
[Nexus 6 Android Development] apophis9283:
Just so everyone knows, development hasnt stopped. Its just slowed down a bit.
[Nexus 6 Android Development] ANDR01DN00B:
Hey guys I've had this problem for a while and haven't found a solution. I don't know if this is kernel related or just YouTube but if I play a video longer than 10mins, the playback stops but audio continues, then I am no longer able to start another video. This can all be fixed temporarily with a reboot but I was wondering if anyone is experiencing the same issues and/or has another fix.

Thanks in advance.
[Nexus 6 Android Development] Mr_S:
Being looked at I believe
[Nexus 6 Android Development] apophis9283:
Can anyone give me an idea of when this all started? The whole video thing
[Nexus 6 Android Development] BeDesireS:
I have no problems with video. Just watched a 15 minute hd video on YouTube without problems.

Send from my AOSiP powered Nexus 6
[Nexus 6 Android Development] apophis9283:
Would someone with the video issues test this

https://s3.amazonaws.com/singularity-kernel/Kenrel/SINGULARITY-V-TEST.zip
[Nexus 6 Android Development] TheAceOfSpades:
Holy millions of options [MENTION=4392154]apophis9283[/MENTION]! I'm definitely going to try this out!! Has battery life been improved even with so much crammed into a single kernel?
[Nexus 6 Android Development] DigitalPrinceX:
I really love this kernel and its development.

But unfortunately the hwrng process is killing my battery. I have learned it is a built in rng seeder of this kernel.

I tried with two roms after a clean flash and not a single app installed. Still this process is persistent and will always load my CPU over 60%.

I understand the concept of of seeder. It improves performance. But really in a phone like nexus 6 I rarely notice any sort of lag (if i measure in a full stock rom).

So personally I do not feel the need of seeder, I wouldn't mind if it goes away.

I am kind of forced to change kernel, because battery drained too fast. (Didn't even give 1 hour 30 min SoT during a lecture i attended in university)

It could be my own issue, but I think I eliminated that possibility by testing with stock Chroma rom and stock fluence hd rom.

I would appreciate any help regarding this.
[Nexus 6 Android Development] apophis9283:
Dont leave just yet. Give me 15 minutes and ill have a build for you to try
[Nexus 6 Android Development] :
If you're only getting 1.5 hours sot, it's definitely an issue on your end. I'm fairly certain that I could benchmark for over an hour and a half sot.

The only way that hwrng should be eating up that many cpu cycles to have an effect is if it's unable to talk to the hardware rng in the chipset and the daemon is just running open. The whole idea is to unload cpu cycles from having to handle the rng process.

Apophis is trying to revert some stuff for you to test though.

But honestly , I don't see any significant cpu use from hwrng on my device.

*edit*

Also, what are you using to check the cpu use for the process? There's about a million ways to do it with varying levels of accuracy.

Sent from my Nexus 6

If I've helped you, don't forget to hit thanks!
[Nexus 6 Android Development] apophis9283:
Here is a test build for everyone

https://www.androidfilehost.com/?fid=24411628330025566
[Nexus 6 Android Development] TheAceOfSpades:
I'm limited to 8 thanks per day lol but thanks! Downloaded.
[Nexus 6 Android Development] nazfalas:
Ok tested this build with a multitude of different videos, streams, etc. and everything seems to be in order. Awesome, thx!
[Nexus 6 Android Development] apophis9283:
Good :)
[Nexus 6 Android Development] apophis9283:
Probably gonna be a realease today, just kick back and wait
[Nexus 6 Android Development] str8str:
So was there an issue with video streaming on previous build or not? Not really a definite answer. Just wondering.

---------- Post added at 15:55 ---------- Previous post was at 15:53 ----------

Getting 404 error for link of test build
[Nexus 6 Android Development] apophis9283:
Kenrel version 4.5 is live in OP and in-app. Should fix some stuff also added MSM_SLEEPER. YOU WONT HAVE IT UNTIL YOINX RELEASES HIS SKA UPDATE!
[Nexus 6 Android Development] apophis9283:
Post a screenshot where you are getting these stats from