yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Android Development] apophis9283:
Im not seeing it, but that doesnt mean its not happening. I made changes to powersuspend Ill go back and peek.

Edit: DAMN. Its some cpufreq changes I made. Ill revert the 2 commits and build again. Sorry about that everyone. These are literally the only 2 commits that would cause this.
[Nexus 6 Android Development] TheGrandFinale2001:
I definitely notice an improvement while charging!! :good:
[Nexus 6 Android Development] apophis9283:
Yeah, I had it setting the governor to lightning when on charger. I removed that and didnt force it to use lightning. So it will use whatever governor you are using
[Nexus 6 Android Development] apophis9283:
1.8.3 is up. I reverted the 2 commits I think were causing the issue. Its the only 2 commits Ive merged since TEST-3 that would cause the issue.

Edit: If you all wouldnt mind, would every check and see what there time in states is after awhile.
[Nexus 6 Android Development] Stroky:
Thanks for that really fast update. But my cpu freq is still jumping around.

I will do a clean flash. Maybe on the next weekend. Will report than again.

Gesendet von meinem SGP511 mit Tapatalk
[Nexus 6 Android Development] apophis9283:
I just checked mine. Mine has sat at 98MHz for 21 minutes and 23 seconds

its only been at my max 2649MHz for 8 minutes which is where it needs to be for what I am doing with my phone
[Nexus 6 Android Development] str8str:
Might be rite on the virtual memory setting the snappiness lower I noticed it slowing down over a course of two days with no reboots. Running great just slows after couple days. I was using intel plug and I noticed you updated it. But other than that it's running great with no reboots heating or anything abnormal

I always change mine to like 12 or even 10 as well as dirty ratio to 5 or 6 but line you said that's the beauty of it
[Nexus 6 Android Development] apophis9283:
Ill increase it
[Nexus 6 Android Development] str8str:
You mean decrease?

I'm learning still but shouldn't the swap be lower? Just reading it it says if memory is to aggressively moved to disk can cause lagging so I figured to lower it. We want it to dump more would that be higher or lower
[Nexus 6 Android Development] MrSplaat:
Got any link? The link in OP is down
[Nexus 6 Android Development] str8str:
He's making an edit I believe
[Nexus 6 Android Development] MrSplaat:
Looks like he just uploaded 1.8.4: https://androidfilehost.com/?fid=24713784966774814
[Nexus 6 Android Development] apophis9283:
Its only at 20%. I raised it to 40%. People can dial in any edits they need to. Im about to update the OP. I went through github and anything I thought could cause issues is gone. Test it for awhile and later tonight I can make adjustments if I need to.

Edit: OP updated. Ill be back later tonight if you have any issues
[Nexus 6 Android Development] str8str:
From what I understand by what it says in kernel auditor about swap and what I've read herehttps://www.howtoforge.com/tutorial/linux-swappiness/

Swap should be lower to increase performance to much or to many on swap disk can cause slow downs cause the memory disk is much slower.

On This it depends on your ram. We have 3gb so from what I've read 60 is the default so it's a matter of experimentation but 40 is a good place to start if I notice anything slowing I'll go down from 20 seeing that's where it was prior????
[Nexus 6 Android Development] MrSplaat:
When I'm in KA-mod and got the lightning gov running, I notice that the frequencies are jumping back and forth between min and max despite the load. Should it do this?

And is it okay checking which frequencies a gov uses with KA-mod open and not using the phone? Or should I stick to checking the frequency table after some time instead?
[Nexus 6 Android Development] Stroky:
That's exactly the same behavior I noticed

Gesendet von meinem SGP511 mit Tapatalk
[Nexus 6 Android Development] str8str:
Frequency will fluctuate if your looking at them cause there are apps, services etc in the background that have to run your phone even if your not using it. As long as they aren't locked at max or min they should be fine and just look at the times in state over time to show you what's going on. You can also use os monitor from play store to show you what's using your cpu
[Nexus 6 Android Development] str8str:
Frequencies are looking like they are locked the bars are not moving but the percent readings are and showing different
[Nexus 6 Android Development] str8str:
The bars will show 2808 always even thou the numbers on top are fluctuating.
[Nexus 6 Android Development] str8str:
See here and I'm using smartassv2 su it's not the lightning governor
[Nexus 6 Android Development] MrSplaat:
As it states in the text you linked:

I understand it like the swappiness should be low if you got a lot of RAM, more than 3 GB, and want good performance. The N6 with its 3 GB RAM should have a higher swappiness because of the low RAM amount. If you have the swappiness set to e.g. 10%, I guess you will notice lag because of the low amount of RAM left for other processes. Could be wrong though.

---------- Post added at 21:27 ---------- Previous post was at 21:24 ----------

I started to wonder because I didn't notice this behavior on some of the other governors. Running Chill atm and that seems quite stable, even with KA-mod open. Guess it's based on how the gov is built.
[Nexus 6 Android Development] str8str:
Ya setting it to 10 means it will swap when your memory reaches 90 per and so on as you raise it. 30-40 should be good

---------- Post added at 08:39 PM ---------- Previous post was at 08:36 PM ----------

OK some governor aren't registering. The percentage does but not the bars. Smartassv2 and lightning so far are not. Chill is working haven't tested all

---------- Post added at 08:43 PM ---------- Previous post was at 08:39 PM ----------

This is weird I switched around governor's randomly now lighting is registering correctly but smartassv2 still not. Gonna clean wipe and retry

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

Nope bars are still stuck at max and don't move but the frequency numbers above them move to show the fluctuations the bars do not especially when using smartassv2. Lightning it wonky as well

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

Also frequency won't go above the default max. I set to 2808 but won't go about default

---------- Post added at 09:18 PM ---------- Previous post was at 09:14 PM ----------

OK scratch my last comment frequency is going to where I set it now
[Nexus 6 Android Development] apophis9283:
No, its Lightning governor. I have 1.8.5 but cant get to my PC where I can update OP and all that.

Wipe KA-MOD data and wipe caches. This fixes a few things and makes Kraken the default governor until I can look at Lightning governor later tonight. Not sure why its all wonky.

https://www.androidfilehost.com/?fid=24588232905724613
[Nexus 6 Android Development] MrSplaat:
You're the king when it comes to updates! Gave you a small donation just to show my appreciation of your work. It's not much, but at least it's something :)
[Nexus 6 Android Development] apophis9283:
I thank you very much for that. Just to be honest, I dont even consider most of you users. You're friends. That's why I put so much effort into this kernel. I may not always completely understand why certain things break. I do my best. The friendship and support most of you have given me over the past several months does not go unappreciated. This kernel was built by you all for you all. I just throw together what needs to be thrown together and compile.
[Nexus 6 Android Development] str8str:
OK but when using smartassv2 the bars for frequency just stay maxed and don't move. Your saying lightning governor is causing it all? Tia
[Nexus 6 Android Development] apophis9283:
I havent really looked that deep. This may be governor specific issue. Ill do more testing tomorrow.
[Nexus 6 Android Development] CyberpodS2:
I'm still running 1.8.1 with smartmax and the bars are moving with the numbers but they are not with smartassv2. Maybe see if smartmax works properly on the version you are running??
[Nexus 6 Android Development] str8str:
I'm on the last one he uploaded and it's the same smartassv2 the bars stay maxed smart max works fine as does all of them except smartassv2. Lightning is working the bars are not staying stuck at max.
[Nexus 6 Android Development] apophis9283:
People shouldnt have to settle on a governor they dont want to use. Thats not how I operate. I consider this no small problem and is the absolute highest priority. I will muster all the free time I have tomorrow to fix this.
[Nexus 6 Android Development] str8str:
Are the numbers that show the percentage above the frequency bars supposed to show the percentage of that frequency? Are they supposed to be the as a percentage of what shows on the bars? Cause if so then they are way off on any governor. It will say 6per but the bar will be at max almost. Seems all wonky unless I'm reading it wrong
[Nexus 6 Android Development] biggiesmalls657:
I will have free time the next couple days to test as well. I have used your kernel before and it's top notch. :)

Edit: spelling error
[Nexus 6 Android Development] apophis9283:
Before I head to bed. Can anyone recall possibly when this started? It would help narrowing the issue down
[Nexus 6 Android Development] CyberpodS2:
Oh no you misunderstood my motivation. I thought there was some question as to when the issue with the bars not moving started occurring.
[Nexus 6 Android Development] apophis9283:
Youre fine. I was making a statement
[Nexus 6 Android Development] MrSplaat:
I've noticed that the issue with lightning have occurred on several of your earlier releases, way before 1.8. I don't remember exactly when...
[Nexus 6 Android Development] apophis9283:
im working on it

Edit: As of right now I have no clue whats causing this. This could take a bit to narrow down
[Nexus 6 Android Development] LunaticSerenade:
So, last week I had reported an issue with the max frequency sticking at 960.

Turns out Kraken has a max screen off setting, which is set to 960, and it wasn't always taking the DTTW as the screen coming on.

Mystery solved.
[Nexus 6 Android Development] apophis9283:
I just fixed that, Im sorry. I caught it while trying to fix the current major issue.

Edit: Seems like Im always rushing to push updates and I dont always pay attention to what I am doing. Ive always wanted to get GPU to boot with stock frequencies. Ive seen the code a 1000 times but looking at it now I was doing it wrong. Lesson learned. Really have to pay attention to what I am doing........
[Nexus 6 Android Development] str8str:
No rush brother you've done a great job at this especially for your first kernel. I think I speak for everyone when I say that and we would much rather a smooth fast and stable kernel then a ton of updates. Take your time

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

I'm on 185 and using lightning. The graph seems to be working Ok except the numbers above which I mentioned. What other issue is there with it?
[Nexus 6 Android Development] apophis9283:
Yeah I also didnt set the Kraken govenror cpu boost right. Its all fixed now. Flashing a build to see if the issues are solved.
[Nexus 6 Android Development] LunaticSerenade:
Haha, no worries. At least I know I'm not completely insane. :)
[Nexus 6 Android Development] ajslay:
Does this have a GPU over clock as well?
[Nexus 6 Android Development] MrSplaat:
I agree with [MENTION=5201751]str8str[/MENTION], just take your time bro. No need to be rushing these updates. I'll take quality over quantity every day.

I can live with 1.8.5 for a long time because the performance is on top imo :good:
[Nexus 6 Android Development] apophis9283:
To be honest I have no clue why frequencies have gone insane. Im doing my best
[Nexus 6 Android Development] str8str:
We don't doubt it

Straight from the one and only Straight Shooter. ?
[Nexus 6 Android Development] apophis9283:
Im gonna revert back to a safe point where things worked, then add stuff back in at one at a time. Might take a bit but it will be worth it.
[Nexus 6 Android Development] apophis9283:
Yes, stock is 600MHz, this kernel has 650MHz and 700MHz OC.
[Nexus 6 Android Development] Mystique:
Took phone out my pocket..

Found a random reboot..

echo cfq > /sys/block/mmcblk0/queue/scheduler

echo 1024 > /sys/block/mmcblk0/queue/read_ahead_kb

stop logd

echo 63 > /sys/vibrator/pwmvalue

That's all I got..

I do have vibration set to 50% not sure what the 63 is..

1.8.5
[Nexus 6 Android Development] biggiesmalls657:
[MENTION=4392154]apophis9283[/MENTION] you are truly amazing! I love this kernel with beanstowns106's ROM Pure Nexus. Its solid and smooth as heck. I can make some logcats if you want.
[Nexus 6 Android Development] :
That doesn't take a 0-100 value. It takes a 0-124 value or something line that. Hence 50% is around 64.
[Nexus 6 Android Development] apophis9283:
I have reset to a earlier time and I will take my time rebuilding it. See if I cant get it stable again.
[Nexus 6 Android Development] apophis9283:
Nah, not amazing at all. So many people contributed to this kernel its not funny. They are the real heroes. I just try to smash it all together to make it as feature packed as possible.
[Nexus 6 Android Development] str8str:
Not true brother your the one that makes it what it is
[Nexus 6 Android Development] apophis9283:
Well my neck and my a** hurt but I have knocked out most of it. Get all this together and hopefully its not throwing a tantrum anymore. I found so many mistakes I made its hard to list every one.
[Nexus 6 Android Development] str8str:
Lol
[Nexus 6 Android Development] apophis9283:
Going back through everything I was able to shrink my commits by at least 50 commits.

Edit: It doesnt want to boot. Ill have to try and get it figured out tomorrow.
[Nexus 6 Android Development] apophis9283:
I was thinking and thinking about what would cause it not to boot. Then I remembered I killed Alucard hotplug because I added Thunderplug. There seems to be limits on governors and hotplugs.I bet if I kill Alucard hotplug tomorrow it would boot. I bet most people have never had this problem because they've never tried to add that many hotplugs. Ill will test my theory first chance I get tomorrow.
[Nexus 6 Android Development] str8str:
Your a madman. Lol
[Nexus 6 Android Development] DreamFX:
Making the plunge to N. See everyone on the other side.
[Nexus 6 Android Development] apophis9283:
So far this looks promising. I should have something for testing eventually.
[Nexus 6 Android Development] harpin14789:
Safe travels :)
[Nexus 6 Android Development] apophis9283:
If a few of you would test this that would be awesome. See if I have this right or not. Watch time in states and make sure its not staying maxed out. Lightning governor boots by default and I have reverted a few things.

Link = https://www.androidfilehost.com/?fid=24713784966774970
[Nexus 6 Android Development] LunaticSerenade:
Flashed about 20 minutes ago (slow day at work), will report back after some usage.

But it booted, so there is that! :)
[Nexus 6 Android Development] apophis9283:
I still havent stopped trying to fix stuff. Im not adding any commits this is purely trying to get what I have working in the best possible configuration.

Edit: I remember one of you being disappointed about me killing Alucard hotplug. I was able to keep all the other ones and keep Alucard hotplug. I never forget when people say things like this and I am glad I was able to bring it back.
[Nexus 6 Android Development] apophis9283:
I would like to start doing something different. I would like 2 or 3 volunteers to test builds. That way if there are issues I dont have to work it out with so many people. To be able to test, you have to be on hangouts. Im gonna go with quality over quantity. If interested just inbox me. I normally dont like to turn people away but I think this way will benefit everyone. I will consider people Ive known the longest first. People who have helped me diagnose issues over the last few months will be considered first.
[Nexus 6 Android Development] apophis9283:
So far one tester has got back with me. It seems everything is good except for the smartass governors. I want a day or two of it running well before I release V2. Taking baby steps with this. Hopefully in the end I can deliver a battery friendly, not sacrificing performance kernel.
[Nexus 6 Android Development] klabit87:
Thank you for your great work! I'm glad to be able to come back to your kernel.

It's been a while since I've been able to do much and this was a pleasant surprise!

Thanks again!
[Nexus 6 Android Development] LunaticSerenade:
So far the test has been very stable for me. Very smooth, virtually no lag,
[Nexus 6 Android Development] Mystique:
Virtually no lag?

Or Literally no lag..
[Nexus 6 Android Development] LunaticSerenade:
I have had one instance of lag with the Tapatalk app.

So, technically virtually no lag.
[Nexus 6 Android Development] Mystique:
http://imgur.com/a/jqcRZ

Literally virtual servers? or virtually virtual servers?

;)
[Nexus 6 Android Development] MrSplaat:
Running latest test, stable and no issues so far, besides the lag that appears when I'm multitasking a lot. Gonna play around with LMK and VM.
[Nexus 6 Android Development] LunaticSerenade:
I applaud your smart assery sir. :good:
[Nexus 6 Android Development] nazfalas:
Haven't seen any device handle Tapatalk without lag...so that probably translates to no lag at all. :D
[Nexus 6 Android Development] str8str:
That's why they call it crapatalk
[Nexus 6 Android Development] apophis9283:
I have made some pretty big changes trying to get this crap all sorted out. I have my 3 testers and I am compiling a build now. If the three of them report back later today that all seems well I will release a 2.0 build. I will be sending a link to the testers soon.

Edit: to the testers please wipe KA-MOD before you flash it. For right now I sent the link through XDA until I can get everyone sorted out with a better way to communicate.
[Nexus 6 Android Development] dannycellestio:
but, but, but.. I wanna be a tester too :( Why 3 when you can have 4 ? :D
[Nexus 6 Android Development] apophis9283:
I wasnt picking and choosing. I just need to start doing things right. Ive known you quite awhile, if you want my testing kernels you csn have them. Im not at home but as soon as I get there I will link you
[Nexus 6 Android Development] Mystique:
Re the Tapatalk app..

Are you using xda labs?

www.xda-developers.com/xda-labs
[Nexus 6 Android Development] str8str:
Not sure who your asking but I am
[Nexus 6 Android Development] apophis9283:
As soon as the other testers get back to me, Ill be able to give and exact time/date for the release of 2.0. So far though, everything seems to be taken care of.

Edit: Aiming for tonight. Its looking good and I HOPE no one has problems. Im gonna have to think of the best way for people to report specific issues.
[Nexus 6 Android Development] apophis9283:
So far the testers are saying everything is fine. I will go back through recent code make sure I give you the best possible kernel when I release 2.0. Not saying a few people may have issues here and there but thats better than everyone having issues
[Nexus 6 Android Development] direwolf1:
Thanks so much for all your hard work (and a shout out to the testers, too!). Really looking forward to the 2.0 release.
[Nexus 6 Android Development] apophis9283:
It will be up soon. Made some quick last adjustments. I didnt rush when I did all this. Took the time to read everything. None of the testers are having issues. Ill probably be updating the OP very soon.
[Nexus 6 Android Development] apophis9283:
And....... OP has been updated with V-2.0. Please clear app data on whatever kernel app you use.

I really hope you guys enjoy it.

Edit: Ill be back on XDA tomorrow. Just want to relax tonight. If you have any issues please still post the issue but I wont be looking at it until tomorrow.
[Nexus 6 Android Development] nodnarb91:
You never said anything about reporting the good thing about the new release...so I'll just do that lol. Been running this since last night on Neo's RR and damn man 2.0 is a winner. The default kraken governor and blu_plug hotplug have been running very well together. Made my shamu super snappy and fast af. Even sleeps like a baby when its not in use. Kudos good sir on this new release. Stay away from XDA longer if you want, no problems on my end.
[Nexus 6 Android Development] apophis9283:
There is actaully some stuff I see issues with. I need to get LMK working better. I added some ZRAM commits as well. Other than that I dont want to go changing too much. Thank you for hanging in there with me while I get the kernel a little snappier.

Edit: Thank you Brandon for the donation. Much appreciated.
[Nexus 6 Android Development] CyberpodS2:
For what it's worth, 2.0 is living in harmony with yesterday's AICP nightly. It slept like a baby over night with 1.8.1 also. Keep up the great work bro!
[Nexus 6 Android Development] apophis9283:
Just a heads up to my testers. You know who you are. Be aware that at some point today I will have another test build. Got some ZRAM changes and LMK changes. You should probably run it for a day or so. Hopefully it kills some micro lag

To keep this simple for now Im not going to mess with Zram. LMK on the other hand looks to be my doing. Some changes I have made. So I went back corrected those mistakes.
[Nexus 6 Android Development] apophis9283:
I have updated the OP to V-2.1.

I know what you're thinking, but apophis you were supposed to put out a test build. Originally I thought that I was going to make big changes to LMK. Thats not the case. I changed 2 variables some time ago that seemed to cause the issues. I simply used the old variables and it seems to be better. I didnt think a test version was needed.

Im trying not to change anything unless its absolutely needed.
[Nexus 6 Android Development] harpin14789:
Updating now, will see of the issues are fixed. :good:
[Nexus 6 Android Development] harpin14789:
Just clean flashed neo's RR rom with 1.3 kernel. Just had a random reboot while restoring apps. Will be on the lookout too see if I get another random reboot.
[Nexus 6 Android Development] apophis9283:
Its just weird. Everything is working great on my end. No heat issues, no random reboots and i mean i havent even had one.
[Nexus 6 Android Development] apophis9283:
Did anyone have issues on V-1.1?
[Nexus 6 Android Development] harpin14789:
Not me, V-1.1 and V-1.0 ran really well without random reboots. I am clean flashing Neo's RR again and will V-1.3 after all my apps/messages are restored. The random reboot between the restore messed up the restore.
[Nexus 6 Android Development] adio201:
I get random reboots I'm running resurrection remix latest build clean install http://cloud.tapatalk.com/s/5789b1dd5afa6/2016-07-15-21-01-07.txt
[Nexus 6 Android Development] :
The bluplug always being enabled is still there...I can delete the startup command, but as soon as I reboot it automatically enables and shows back up in start up commands.
[Nexus 6 Android Development] coremania:
V1.0 - V1.3 no random reboots on krexus, acip and official RR
[Nexus 6 Android Development] rrrrrrredbelly:
On 1.2 now. Haven't had any issues on this or 1.1. Still on PN mod (layers)
[Nexus 6 Android Development] Kris6699:
I have been having the YouTube desync then won't play video issue on 1.3. DeYuS did manage to fix that. Could you incorporate the same fix?
[Nexus 6 Android Development] Mystique:
Keep having soft reboots..

Wiping and reinstalling..

Both /system and /data

Also wiping /data/media/Android

OT, does anyone have a Rom where navigation bar spectrum analyzer works in Spotify.. - Thanks in advance
[Nexus 6 Android Development] bluntman420:
Haven't had any issues yet with v1.3 on chroma ROM. Will keep you posted if any issues arise. Thanks [MENTION=4392154]apophis9283[/MENTION]

---------- Post added at 08:38 AM ---------- Previous post was at 08:37 AM ----------

He needs logs to try and figure out your issue.