yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Android Development] apophis9283:
I mean as far as it goes, the governors can only act one way, the way they are coded. Which goes for most of the kernel settings.

My bet would be "N" is still in its infancy and the kernel is fine.
[Nexus 6 Android Development] jcrompton:
Still trying to sort through all this in my mind ...

Based on this screenshot shouldn't the 3rd and or 4th core be coming online at this point?

See screenshot
[Nexus 6 Android Development] MrSplaat:
No, thanks to the settings. Dual core on light task, quad kicks in at heavy tasks
[Nexus 6 Android Development] DreamFX:
I think something is wrong with latest version. I can't get more than 2 cores to stay online at once. They disable automatically when I manually tune on more than 2. Switched to performance governor that is supposed to be all 4 on at all times at max clock speed and even that doesn't work.
[Nexus 6 Android Development] MrSplaat:
Try changing hotplug instead.
[Nexus 6 Android Development] DreamFX:
I have everything on default. Blue Hot plug is set to allow more than 2 and they don't fire even under heavy load from games.

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

. Some governors will kick all 4 like zzmove. But performance doesn't. Which makes no sense as that's what performance is. All 4 at their max. Darkness the default won't fire more than 2 under extreme load. Same with performance.
[Nexus 6 Android Development] jcrompton:
This is what I was trying to demonstrate by my screenshot

The default hotplug is set to bring more cores online at 80%. Notice that those two cores are at more than 80 but no response from core 3 or 4

There is definitively something wrong just not sure of it's something in general or just the default hotplug
[Nexus 6 Android Development] DreamFX:
Yea I don't ever mess with hot plugs never did. So I wanted to chime in. Been away from singularity for awhile and decided to try her out again and when I saw you were having same issue I wanted to say something.
[Nexus 6 Android Development] dark2099:
Just had a reboot after exiting KA-MOD. Logs attached.
[Nexus 6 Android Development] MrSplaat:
I notice the same behavior on Mako, but all the others seems to work just fine. Could be an error, or the hotplug is just damn efficient.

---------- Post added at 17:41 ---------- Previous post was at 17:38 ----------

Got the same issue myself, it seems like. I never encountered any problems related to that, so it never struck me as an issue :p
[Nexus 6 Android Development] apophis9283:
So did everyone just download my kernel? Threads been quiet. Did anyone update their ROM? These are the same settings that everyone claimed was stable. Even N users praised it. So I'm struggling with what would cause the masses to all of a sudden have issues. I'm at the hospital, ill look at logs (if you post them) when I get home

The biggest problem right now, is I have no want to flash an N rom. Because IMO they just aren't ready.
[Nexus 6 Android Development] apophis9283:
Cpu 3 is at min frequency
[Nexus 6 Android Development] apophis9283:
Go into blu plug and bump from 2 cores always online to 3 or 4. Problem solved
[Nexus 6 Android Development] apophis9283:
Ill look. Did you change any settings and also did it go back to google boot splash or boot animation
[Nexus 6 Android Development] apophis9283:
Also. If you came from another kernel. Dirty flash your ROM then see if the issue persist
[Nexus 6 Android Development] dark2099:
Only been on your kernel since I flashed the 7.1.1 image, only settings changed are turning on auto hbm, speaker driver leakage, and setting GPU speed back to stock 600mhz.
[Nexus 6 Android Development] apophis9283:
Ok ill peek at your logs
[Nexus 6 Android Development] MrSplaat:
Wasn't quite easy to spot this one. It all seems fine performance-wise, but Mako and blu_plug won't enable the third and fourth core whatsoever. I tested blu_plug by lowering max frequency to 883, it never enabled another core. Most of the other hotplugs works just fine.

Take care!
[Nexus 6 Android Development] apophis9283:
Ill look into it. See if any changes need to be made
[Nexus 6 Android Development] apophis9283:
Mako and blu_plug have issues I am looking into. Like I said the code is what it is. It doesnt change just because you're running M or N.

I did a little test by setting performance governor and going through the Hotplugs. Every hotplug but the 2 listed immediately turned on all 4 cores.

So just need to figure out why these 2 are acting stupid.
[Nexus 6 Android Development] apophis9283:
So far I see nothing wrong. Ill have to dig deeper.
[Nexus 6 Android Development] jcrompton:
This has been my experience as well

Being a bit transparent at first I thought maybe it was normal but after some time and seeing others comment I realized it probably wasn't. And yes mako and Blu plug were the ones I mainly noticed
[Nexus 6 Android Development] rignfool:
Again... I'm not running your kernel... But you did set the respective load thresholds to 0 to see if it kicks em online?

I could believe since the owners of those aren't actively developing them for this device... That load calculation may have changed... Since ever other thing that works seems to need tweaking these days
[Nexus 6 Android Development] MrSplaat:
I did, and even on full load, threshold at 10 and max frequency at 883 Mhz, nothing more than two cores was online with both mako and blu_plug. All the other hotplugs worked like they should.
[Nexus 6 Android Development] apophis9283:
On boot 4 cores are used. On resume, waking the phone, 4 cores show being used. I need to do general maintenance anyway. Everyone just hold on until I get stuff sorted out. Although if it wasn't working properly id imagine you would have had terriblt lag
[Nexus 6 Android Development] aow1980:
I started using your kernel with Twisted Core for N. So far it is extremely smooth with the default settings. Would like to say great work on it.

Now for the problems I had and hope it helps you some.

I had the core 0 sticking at 100% like another user posted. I tried various things to no luck. I saw you had tweaked a few things so did a build with the new tweaks.

Working great and no issues with the core sticking. Though I didn't see any real changes that I thought would impact the cores like that. But maybe entropy does more than

I thought it did.

Mako and Blu have had the issue for awhile (maybe since they were adapted to shamu). I've set Blu to 4 cores min while screen on and it seems to run pretty good that way.

Keep up the great work and though i'm biased I'd recommend Twisted Rom. :)
[Nexus 6 Android Development] apophis9283:
Proof that blu plug is capabale of onlining cores. I did nothing more that turn on the screen
[Nexus 6 Android Development] aow1980:
I just lowered the threshold to 15 and opened various apps. No more than 2 cores came on.

Switched from Darkness to hellsactive and all four cores came on and started plugging. Using BluPlug
[Nexus 6 Android Development] jcrompton:
That's strange isn't it ????
[Nexus 6 Android Development] aow1980:
It is a new one for me lol

If I get time tonight, I will keep looking in to it. Maybe it is with how some governors perform that isn't allowing it time to

hotplug correctly.
[Nexus 6 Android Development] apophis9283:
Im going through some stuff now. Ill let you know when Im done. Gonna take care of some stuff Ive been meaning to take a look at anyways.
[Nexus 6 Android Development] apophis9283:
I have made some fixes. For now I will kill those 2 hotplugs. Im gonna use Intelli_Plug for default. I reverted Msm_Limiter back to V-5.3 (which seems a lot better IMO) And I got rid of that MPdecision toggle in hotplugs which would have never worked anyway because I dont even have the code for it.
[Nexus 6 Android Development] MrSplaat:
Just a funny fact! On v4.1, it seems like blu_plug won't disable cores... :silly:
[Nexus 6 Android Development] rignfool:
Whoa...

Holdup!

Darkness does its own hotplugging... Or used to?
[Nexus 6 Android Development] apophis9283:
Yeah, it claims to be a hotplug but not in the code. Only the insert at the bottom. I couldnt find any hotplugging code in the one I use. But even then, it should tamper with all the hotplugs and not be selective.

Nice how you always have an opinion on everything but you offer XDA nothing other than smartas* comments. Good job. Your life must be filled with friends.
[Nexus 6 Android Development] rignfool:
Whatever... Sorry I'm not kissing your ass... Just attempting to offer something constructive that I read...
[Nexus 6 Android Development] str8str:
I'm in 4.1 and Android n if you look at the frequency table mine shows that indeed all are working just very efficient. Also mako plug if I set the limit to 25per to online all cores they all come on so they are working great. IMO
[Nexus 6 Android Development] MrSplaat:
Yeah, something was up with the rom I used. Just did a reflash of the secondary rom, both blu and mako plugs like a baws now with darkness as governor.
[Nexus 6 Android Development] apophis9283:
Constructive would be nice. The way you say it was uncalled for. I honestly don't understand you. I'm not trying to be an as*. Every thread I see you in usually comes with the comment, " I'm not using this but....". If you aren't using it, how can you give feed back? Look at the way you wrote that out. Tell me I shouldn't have been offended. I usually just write you off and move on. If you're going to be constructive and help, which I always appreciate when people do. Maybe you should pay attention on how you say it.
[Nexus 6 Android Development] apophis9283:
Something is up with the kernel. I don't know what yet. You shouldn't have to go through these hoops to make this stuff work. Give me time and Ill get it figured out
[Nexus 6 Android Development] rignfool:
And maybe you shouldn't have made it personal...
[Nexus 6 Android Development] apophis9283:
So if someone talked down to you, you wouldn't take it personally? Why are you even in these threads. Everytime you state you're not even using the code yet you feel compelled to respond in a smart as* way. What is your purpose? If you really wanted to help, you would just stop. I don't want or need your help. So be on your way and may peace follow you into any other thread you feel like posting in.
[Nexus 6 Android Development] Neo:
Arrrright. Break it up.

Let's put the epeens away. We all know Neo's got this here... :silly:

Seriously though.. Constructive criticism is fine, just don't be a smartass about it. We can all get along in here. Let's focus on the changes and improvements made to the source and continue to help the developer improve his kernel to the mutual benefit of he and his users.

I don't want to see any more of the bickering or continue quarrel over this issue.

Thanks,

Neo
[Nexus 6 Android Development] apophis9283:
I went back to 4.1 and still having this issue. But if a clean flash fixes it, maybe I should look into this.

Also. To make it much easier on me. Im thinking about just jumping to N and discontinuing M builds.
[Nexus 6 Android Development] rignfool:
**** you
[Nexus 6 Android Development] Neo:
Enjoy your time off.

Now, back to an on topic discussion.

Everyone, enjoy your day :)

Neo
[Nexus 6 Android Development] MrSplaat:
I still have issues, after all. But I've been doing some more testing.

Mako: Totally fubar! Set the load threshold below 50% and it will constantly run on all 4 cores, . Set the threshold to 50% and above and it will constantly run on two cores.

Blu_plug: Almost same behavior.Seth the up threshold from 0-32% makes three cores enabled while a fourth is kick in and out constantly, despite the load. 33-49% leaves two cores enabled and a third is kicked in and out. 50% and above and it will constantly run on two cores.
[Nexus 6 Android Development] apophis9283:
Yeah. I'm slowly going through everything. I promise as soon as I have something, I will let you know. Sorry for the inconvenience
[Nexus 6 Android Development] MrSplaat:
Take your time :good:

Running Intelli_plug atm, works like a charm!
[Nexus 6 Android Development] apophis9283:
If you dont hear anything from me for the next day or two, please dont feel Im ignoring you. I promise I am slowly working on this as I do day to day things. Hang in there with me. Im betting it one or two commits that were merged recently so I went back and Im adding 2 commits at a time. You know I would never ignore you guys. I also got an email, a user asked me to include something and looks fine to me (its a fix from a well known kernel dev) so I want to get that in too. Thank you for your patience.
[Nexus 6 Android Development] jcrompton:
No worries ..... It's all good

You worry too much and I can tell you take your work personal

I'm on crDroid 2.0 more ..... If you are going to go N try that until Neo gets his next RR build
[Nexus 6 Android Development] apophis9283:
I worry about you guys. Its funny. Its like you guys arent even users anymore. More like friends. So yeah, it's personal.
[Nexus 6 Android Development] aow1980:
I found a strange issue. When trying to stream a podcast on I heart radio app. The app goes haywire. Normal station plays fine. I tried with a different kernel and it streamed fine.

Have you ever seen anything like that before?

I didn't get a log to check. Was driving my truck when I noticed it. Figured I'd ask before trying to get a log

Ok, it seems to be only when connected to bluetooth or to my truck bluetooth. Will keep testing it out.

Just something odd I found.
[Nexus 6 Android Development] MrSplaat:
Going a little OT!

Just wanted to show my homescreen after I finished setting it up :)
[Nexus 6 Android Development] gideonlfc:
How do u get those info on the left of the screen?
[Nexus 6 Android Development] MrSplaat:
Thanks to Stats Monitor :)
[Nexus 6 Android Development] atharwaqas:
That is one dope screen... good work man.. how much time did it took you to do all of that?

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

@apophis9283 i flashed the 4.2 version, which broke the sound as expected, so i have reverted back to 4.1. From reading the threads i see that the issue is with the ROM thing and not the kernel itself. So is it only happening when the ROM based based on 7.1.1.r13 release? Or is it because your kernel blobs are updated on the same r13 release as well so the problem is happening.
[Nexus 6 Android Development] apophis9283:
As far as I understand it, it was from ROM devs trying to update to 7.1.1 before we had official source. In that update they had a commit that needs to be reverted to work with the MR-1.2 kernel source which is official from google.

I think I have a tag on what the heck is causing the issues with the governors.
[Nexus 6 Android Development] jcrompton:
That's good about the governor's ..... Any work around in the meantime that you found good

---------- Post added at 11:51 PM ---------- Previous post was at 11:38 PM ----------

Wow I've been sitting in a poor cell service area for the last hour with crDroid N and it's native kernel. It's amazing how put service reeks havoc. My phone has suddenly reboot probably 10 times in an hour!!
[Nexus 6 Android Development] apophis9283:
For the time being just use a different governor.
[Nexus 6 Android Development] dark2099:
So the issue with 4 cores not onlining with Mako and Blu plug is the darkness governor, and not the hotplugs?
[Nexus 6 Android Development] apophis9283:
Try using something like Hellsactive. It seems to work fine.

Im not rushing this. Ive done a few things here and there. Still trying to figure out exactly where sh*t hit the fan. Since this seems to have gone undetected (I am not sure if thats a good or bad thing seeing has not even me noticed it was running on 2 cores) I dont have a definitive place to look.
[Nexus 6 Android Development] garywojdan81:
[MENTION=4392154]apophis9283[/MENTION] just an FYI, Yoinx & Beanstown just posted a speakerphone fix for 7.1.1 r13.

File:

https://www.androidfilehost.com/?fid=385035244224412577
[Nexus 6 Android Development] :
Don't get on XDA much, but I'm running an oms build of RR, and as always this kernel is a beast, and as far as the issues with hotplugs,and governors, I'm running lionfish, with zen decision and having great results with combo....No issues at all!!
[Nexus 6 Android Development] apophis9283:
Look to be ROM side. But thats awesome. People can flash the zip and/or ROM devs can simply fix it.
[Nexus 6 Android Development] apophis9283:
Yeah, the entire kernel isnt broken. In fact it runs really well, I just need to figure out what breaking the ability to online cores under certain circumstances
[Nexus 6 Android Development] MrSplaat:
Thanks! I think I've used around a week, been trying different layouts and style, before I ended up with this.

I also found this totally random cat widget, which I just had to add for fun.
[Nexus 6 Android Development] jcrompton:
Thanks ..... Is that more of a performance combo or battery?
[Nexus 6 Android Development] str8str:
What's the r13 for
[Nexus 6 Android Development] :
I'd say its balanced, the Lionfish gov. Idles great and doesnt jump around,but I get great performance, smooth, snappy, and I average at least 5hrs sot. And that's pretty good for Running a 7.1 cm rom.
[Nexus 6 Android Development] jcrompton:
On the newest version of ROM s there is a terrible echo or squel for the listener when you are on speakerphone. My kids started telling at me ..... Take me off speakerphone dad

It seemed to be one more by product of whatever Google did different that also lead to no sound with kernel / ROM mismatch
[Nexus 6 Android Development] garywojdan81:
Revision level?
[Nexus 6 Android Development] apophis9283:
Completely off topic,

but if you guys havent seen Pantera Vulgar Videos you are missing out.

I havent seen it in forever, just sat down to watch it.

**WARNING NOT FOR EVERYONE... and you may not want to watch it with anyone under 18.. lol**
[Nexus 6 Android Development] apophis9283:
I have a build ready, M is done, N needs to be done. So hopefully tomorrow Ill have a release

Killed Blu_Plug and Mako for the time being. I did update a few governors. Added back Alucard Hotplug. Made Interactive and Intelli_Plug default. (I may add back Alucard governor for those who like to run then in pairs.) Other than that the kernel seems great to me so don't see a point in screwing around with it.
[Nexus 6 Android Development] bigmarv31:
Sweet,I can help test for N if you need any, your kernel is amazing I have been using it since I got my N6 Thanks!
[Nexus 6 Android Development] apophis9283:
I edited my post. If you look at it again, it tells you what Ive done.
[Nexus 6 Android Development] :
Saw them in 97...to this day Still the loudest concert I've seen, and believe me I've seen quite a few, nothing has come close.. Back on topic, What are the chances of adding state helper back in? No biggie if its not feasible, just like to give it a try again.
[Nexus 6 Android Development] apophis9283:
Quite high actually. If you would like it added. There's a ton of really small things I have to do for this release. Most little things, request from some of the users
[Nexus 6 Android Development] :
Awesome!!! Thank you for everything!!
[Nexus 6 Android Development] apophis9283:
Working on wrapping up V-4.3 for testing. Both "M" and "N".
[Nexus 6 Android Development] :
sounds good!! Can't wait to give it a spin!!
[Nexus 6 Android Development] apophis9283:
[MENTION=6257457]baw580[/MENTION]

Are you on "N" or "M". Ill send you a link via PM
[Nexus 6 Android Development] :
I'm running N now.
[Nexus 6 Android Development] apophis9283:
Just updated the OP to V-4.3 for both "M" and "N".

You would be wise to wipe KA-MOD data and probably wipe caches.

Enjoy!
[Nexus 6 Android Development] :
guess I was a little late to respond, ha ha!! Flashing now thank you again!!
[Nexus 6 Android Development] apophis9283:
After playing with it for a bit. My screenshot
[Nexus 6 Android Development] jcrompton:
So which ROM did you settle on?
[Nexus 6 Android Development] Dopamin3:
The only ROM that allows you to put a poop emoji at the top left (among tons of others). That ROM is: Resurrection Remix! He's still running M too, I believe his personal build he posted a few pages back.

4.3 running smooth as a baby's butt so far :highfive:
[Nexus 6 Android Development] jcrompton:
Makes sense

I never have complaints about M but one thing I know I like is the Pixel like stuff and mostly that the API said for certain widgets to be added to Quick Settings tiles

Like my HBM widget
[Nexus 6 Android Development] apophis9283:
Im good friends with the dev of stats monitor. Not too long ago he gave me 10 free codes to hand out to my users. I highly suggest supporting him. Its a great app that gives great info
[Nexus 6 Android Development] jcrompton:
I'm in!!
[Nexus 6 Android Development] :
4.3 running great!!! Thanks for adding state helper!!
[Nexus 6 Android Development] apophis9283:
Not a problem. I've started working on the next release. Probably gonna be core stuff only. Its not just adding commits, its reverting stuff that's hurting the kernel. You know, trying to get it as close to perfection as possible while retaining as many features.

I will be taking request, all request may not be granted but it never hurts to ask
[Nexus 6 Android Development] dark2099:
Had a random reboot today, phone was in my pocket, only kernel change is turning on auto HBM.
[Nexus 6 Android Development] apophis9283:
Caused by a watchdog bite.

I see it has to fo with IRQ. I've only seen this in logs from 2 people. You and str8str.

No worries, something must be going on giving you 2 these issues. I've been needing to see if I can't fix it anyway
[Nexus 6 Android Development] apophis9283:
[MENTION=4816406]dark2099[/MENTION]

I doubt I am going to be able to fix the issue with the info provided. BUT, I added a commit. So that watchdog will give me more info in the log when a bite occurs dealing with IRQ. So I kinda need you to flash this build I will send to you via PM. And next time you get a reboot from a bite. It should give me more info on whats causing the bite.

Are you running "M" or "N"?
[Nexus 6 Android Development] HueyT:
Singularity 4.3 for N does not work with ARISE stock rom by Guitaredhero. Just FYI. It just loop on "GOOGLE" splash screen.
[Nexus 6 Android Development] apophis9283:
Dont see why, are you sure you downloaded the N version?
[Nexus 6 Android Development] HueyT:
I'll retry again but the file name says "SINGULARITY-N-V-4.3.zip"

MD5 check matches listing on AFH download page.
[Nexus 6 Android Development] apophis9283:
Maybe hes done something to the ROM. My testers run both AOSP and (CM) based ROMs. No ones had an issue with it booting.

Is it a clean flash? Were you running another kernel?
[Nexus 6 Android Development] HueyT:
I agree as Singularity v4.3 works fine on other roms. He did some mods on sound with Arise, Dolby, etc.
[Nexus 6 Android Development] apophis9283:
Then it has to be some kind of change in the ROM. Without knowing what it is, I wouldnt know how to fix it.
[Nexus 6 Android Development] apophis9283:
Si Ive added some core commits. Changes to Simple_Ondemand GPU governor, Adreno_Idler clean up and use State_Notifier, added a commit to help track down IRQ issues with watch dog (Should give better details in logs). If this runs well for me for a bit Ill go ahead and push the update. Not really just to push an update but more of it would be nice for everyone to be running that watchdog commit so it would give more details when a bite occurs with IRQ.
[Nexus 6 Android Development] dark2099:
I'm running "N", thanks.
[Nexus 6 Android Development] apophis9283:
Im gonna be releasing a new build, with some nice core changes. Biggest thing is the clean up of adreno idler and make it use state notifiers.

Hang in there. V-4.4 is coming.
[Nexus 6 Android Development] dark2099:
I had issues with some apps not working on an older version of his ROM, so might try just a stock rooted and manually flash ARISE.