yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] bsmitty83:
Its because of the recent interactive changes . I probably re-added the commit that is causing it . so I gotta go through 30+ commits and see if I can fix it .
[Samsung Galaxy Nexus] qtoo941:
What are the changes of V6 on Super Ram version? I see people are talking about wake up delay while i don't have such a bug on V5. Is there any major change in new build?
[Samsung Galaxy Nexus] djtutis:
+1

I have the same issue with interactive on v6...
[Samsung Galaxy Nexus] eternal70:
Getting a sudden reboot. What should i get ? Kernel log or last kernel log ?
[Samsung Galaxy Nexus] JuanG:
I just had a reboot with data lost with Dirty V6. The phone rebooted and started with factory settings. :(
[Samsung Galaxy Nexus] bsmitty83:
Last kmsg
[Samsung Galaxy Nexus] eternal70:
Ah, sorry dude. Didnt't get it. Maybe next time :)
[Samsung Galaxy Nexus] michierusama:
Its not like we are perfectionists. Its just that if we can report that something that was fixed is back maybe can help to track the issue. I don't mind using the kernel with wake up lag. Oh and about that reboot and restarted everything.... Wich rom are you using?
[Samsung Galaxy Nexus] Nephilim:
Updated settings have already been posted. ;)

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] gautam_nexus:
Just checked it out. Can't see any changes. Did you changed it now?
[Samsung Galaxy Nexus] michierusama:
There are lots of changes O. O
[Samsung Galaxy Nexus] Nephilim:
Nope, I decided not to wait until morning and post late last night so the new settings I made after flashing v6 are up. :)

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] aosp:
Test reverting this

rq_stats: add run queue statistic collection to kernel tick scheduler · 2accd35 · bsmitty83/DirtyV_tuna · GitHub - http://goo.gl/2vr3a5

If no luck maybe revert this

cpufreq interactive governor save/restore IRQs around cpumask spinlocks · f41d5f3 · bsmitty83/DirtyV_tuna · GitHub - http://goo.gl/EyKaGT

I'll keep digging ;)
[Samsung Galaxy Nexus] bsmitty83:
Won't be able to get anything done till this evening . but I was kinda headed in the same direction . the rq_stats commit was staging for intellidemand , but I couldn't get it to build , but I left the stats . I'll see what happens lol
[Samsung Galaxy Nexus] Godra:
Does DirtyV v6 works? My phone is not booting for 6-7 minutes already :confused:
[Samsung Galaxy Nexus] aosp:
Yeah that's most likely it and that governor and it's minion's could go in the bin as well ;p
[Samsung Galaxy Nexus] vfmmeo:
Hello.

I've just flashed V6 BigMem and applied Nephilim's settings. Working with the OmniMetal's maguro last build.

Yes, the wake up lag is back here, too. :(

But, i noticed something that may help to trace this issue. If the terminal doesn't enter on deep sleep (i.e. if it's charging, or try to wake up just after lock it) the lag dissapears. So we can say that the lag only appears when the terminal goes into deep sleep.

Another funny thing: If you press another button (i.e. VolDown) at the same time than power button, the little bastard wakes up instantly. lol.

Hope this helps to catch the bug.
[Samsung Galaxy Nexus] sajty:
I would like to take back what i said (wake up lag is not so big). The lag is here and is brutal for me, phone is unusable :D. I had to press power button twice, three times and sometimes even more to wake up my phone. I thought, it's ROM issue, but not.

Hopefully, changing governor to ondemand solved the issue. Not ideal, but it's good temporary solution. Hope for soon fix ;).

Sent from my GN
[Samsung Galaxy Nexus] aosp:
[MENTION=4608636]bsmitty83[/MENTION] should have it fixed in next one but sometimes blood must be shed when you run bleeding cutting edge awesomeness [MENTION=3685904]ak[/MENTION] :thumbup:
[Samsung Galaxy Nexus] Charmacas:
And what was causing it [MENTION=2838735]aosp[/MENTION]?

[MENTION=4608636]bsmitty83[/MENTION] did you see my post about doubletap2wake?

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] Nephilim:
Guys, I hate to be that annoying broken record here again but… .. I have zero screen wake lag on my device using my [now revised] custom settings on v6, nor did I have any on v5 or v4 for that matter.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] Rushead:
I have a major issue with this kernel... My battery life SUCKS considering I have to spend so much time reading this thread to try to stay current. I have to recharge at least thrice each day.

Also, I keep getting "post action thanks deny" errors ;)

Sent from a flashead cracker.
[Samsung Galaxy Nexus] michierusama:
I didn't have the lag on v5 but now I do. I don't get it. Oh well Im using the neph settings and maguro.
[Samsung Galaxy Nexus] bsmitty83:
I did , I'll take a look at it closer when I'm around my computer
[Samsung Galaxy Nexus] aosp:
Some make the change's for the better while other's hope it just work's ;)
[Samsung Galaxy Nexus] metalspring:
I got it on v5, not all that bad though, just a little slower to wake

Also maybe the issue isn't interactive governor itself but some other part of the source code that interactive relies upon (or utilizes more than other governors). It seems suspicious that the wake up lag is present to some degree in different versions of interactive.

Also, does the same lag apply to the dynamic interactive governor if it's still included? (haven't had a chance to try out v6 yet)
[Samsung Galaxy Nexus] JuanG:
The lag is present for me in v6, not in v5. I think v4 was smoother than v5 and v6.
[Samsung Galaxy Nexus] büscher:
Thats what also my experience.

V4 is the snappiest for my phone. Also no wakup lag with interactive and Neph's settings
[Samsung Galaxy Nexus] bsmitty83:
I believe its origin is in interactive code , if it wasent all the govs would act up . or could possibly be something that it relies upon but all the dmsg I'm getting off my phone are traces of interactive . not any other code . the mutex warning has been present since kernel 2.6 don't think its it . maybe gpio , maybe rcu , idk until I start testing , but in all honesty I get zero lag with screen on , and it fails to wakeup maybe 1 out of 20 . mostly when I get a notification while the screen is off .

Again this is part of the process .I can live with the bug , but I'm still gonna try squashing it
[Samsung Galaxy Nexus] ak:
I think a full revert to original interactive source in this moment is the only solution. Than you can rebase step by step the code with a clean source.
[Samsung Galaxy Nexus] bsmitty83:
Unfortunately I agree ....

Oh well , if it is the 3.4 source that's the issue then I'll revert it , while still keeping interactive as current as possible .
[Samsung Galaxy Nexus] Nephilim:
Can you keep the current interactive governor control tunables please? ;)

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] heXacode:
Since I see discussions of Mpokang kernel here and the complaints of the absence of that dev and no response from him... Why doesn't anybody just clone the kernel and slowly strip away some areas, while testing, and see which areas is what is giving the superram its reputation. Then do a full comparison of what is lacking code-wise between mpokang superram and another kernel using superram that isn't as define as mpokang's superram. Wouldn't that finally yield some answers as how the dev did it?
[Samsung Galaxy Nexus] BestBrd:
Maybe(of sure) i'm wrong but,i think is not possible if he wants to revert to the old interactive,because the tunables were inbuilt with the new one...right?
[Samsung Galaxy Nexus] michierusama:
That sounds like a lot of work to do, doesn't it?
[Samsung Galaxy Nexus] schnob:
I do, it doesn't run the best on the 'ol Gnex but it's too good looking to not use, haha.
[Samsung Galaxy Nexus] heXacode:
Yes it does but without that dev and no response, its going to be even longer to get an answer.
[Samsung Galaxy Nexus] osm0sis:
metalspring's stated it a couple times lately, but the SuperRAM stuff has pretty much already been duplicated by bsmitty83, even the stuff from v10 that still hasn't seen the light of day (...which violates the GPL...). So the real useful thing that's missing would be the 50% RAM speed increase, that only exists in v10, and since v9 is as far as the github source goes, we can't exactly reverse engineer it, either. :(
[Samsung Galaxy Nexus] bsmitty83:
I'm gonna try .....
[Samsung Galaxy Nexus] heXacode:
I know its classified as stalking but you can find mpokwsths playing Battlefield 4 on PC. So if any of you play that on PC then I'm sure you could grab his attention there. Lol.
[Samsung Galaxy Nexus] chainrulez:
I do play Battlefield 4 on pc regularly. Tell me his username I l try to bug him. Is this the same username you mentioned? :P
[Samsung Galaxy Nexus] aliesz:
Hi everybody. The linaro V5 version was very good and had nice performance but linaro V6 has delay when screen power on pressed. I returned to V5.
[Samsung Galaxy Nexus] heXacode:
Yes. Same username as he uses here.
[Samsung Galaxy Nexus] chainrulez:
Ok trying now. Will update. ;)
[Samsung Galaxy Nexus] büscher:
He also has his Gmail address in his profile (g+, hangouts etc.), he was online on xda not long ago.

I think he just don't want to contribute anymore, whyever...

Dirty_V is so freaking fast, what would we even get with those 50%+ RAM speed... higher benchmark scores?

I understand the topic about the violation of gpl but he also contributed alot to this community and we schould be thankful for what he did until he left... There has to be a good reason why he does not post anymore...

This were some of his last posts btw:

"Bad news.

My GNex died today. While I was browsing it just died."

"For now back to my ultra - super - blazing fast HTC Touch Diamond."

"Maybe it's time for a GS4 or an LG G2"
[Samsung Galaxy Nexus] heXacode:
I agree. I don't have any interest on pursuing his work and bashing him. Just figured I make a couple suggestions to help figure out the missing puzzle to the 50% ram speed as osm0sis stated.
[Samsung Galaxy Nexus] BestBrd:
This kernel is fast ,very fast...even more than mpokang...but...if this kernel will use this hack...how much fast can become our gnex?

I remember that when i was on v9,mpokang was less fast then fancy kernel...but when v10 came out...mpokang became the best kernel and was still the best until 2 weeks ago..so i think that if a ram hack make a crappy kernel become the best for about 5 months,this hack is very important if we want to improve our gnex performance :)
[Samsung Galaxy Nexus] ScardracS:
Why i can't install your kernel? I recevie status 7 with all six zips

My recovery: cwm 6.0.4.7 touch

My rom: CarbonRom 4.4.2
[Samsung Galaxy Nexus] Shambola:
Terror! After flashing V6 + Neph's settings, my gnex didn't go to deep sleep! Solved (I hope) turning off fast charge, reboot, test (Sweet dreams baby!) and turning on fast charge again)
[Samsung Galaxy Nexus] LeBaldi:
I dont know excetly what MPO did in his kernel... but I remember he comment abou how buit the zimage and how compress in the flash... something like that... but this is in the original threat of his kernel ;)
[Samsung Galaxy Nexus] TheMan0790:
There's a known issue on that version of CWM and flashing kernels. I had the same problem. Just flash 6.0.4.6 again and you will be fine. Osmosis discussed it a bit in his thread.

Break me off a piece of that Kit-Kat ROM!
[Samsung Galaxy Nexus] osm0sis:
Actually [MENTION=4608636]bsmitty83[/MENTION] needs to just fix the zips. ;)

It's a bad command in the ancient AnyKernel zip skeleton everyone is using. Old CWM let it slide; new does not.
[Samsung Galaxy Nexus] bsmitty83:
I thought I deleted the unused line ......

Anyhow I'll fix it in the next zip
[Samsung Galaxy Nexus] Nephilim:
Mpokang thread has just been closed.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] KJW979:
Anyone notice gmail using a lot of battery, first chance to open phone and gmail used up 38% of battery, never had that before. Currently on latest liquid with v6sr and neph's older settings. Haven't had a chance to try new settings. Have auto sync on but have before with no problems. Even force stop doesn't seem to be slowing down.
[Samsung Galaxy Nexus] osm0sis:
Shame it died.. maybe we're lucky we don't have access to the 50% RAM speed increase; maybe he pushed it even further and that's what killed his device? :p
[Samsung Galaxy Nexus] antypas:
:p

Then many of us here in xda should already have a dead device...
[Samsung Galaxy Nexus] Hetalk:
This is why [MENTION=4608636]bsmitty83[/MENTION] is an amazing guy. :good:

Edit: Still running omnimetal build from 30th january by [MENTION=4328678]metalspring[/MENTION] and srv6. Doing a lot of reading on interactive tunables. Hope to improve upon perfection (ie. [MENTION=2853378]Nephilim[/MENTION] 's settings) :)
[Samsung Galaxy Nexus] Nephilim:
Doubtful the ramboost caused it and regardless of if he stopped developing for gnex, he knows we've all tried to contact him and still he ignores everyone. He even ignored the mods pm's and got his thread closed. I feel like you all on bf4 pc should grief the hell out of him for being so rude and disrespectful to the community.

Just my 2cents.

Sent from my Android 4.4.2 Galaxy Nexus

---------- Post added at 02:03 PM ---------- Previous post was at 02:01 PM ----------

You know my settings are always a work in progress when it comes to kernels with this much daily activity. ;)

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] Hetalk:
<advice>

My take on the MPO discussion. Let bygones be bygones.

If there's such a hack that can improve upon this kernel I'm sure we got enough talented devs here who will eventually crack it.

BTW, I've never used mpo kernels, as I was out of commission for about 6 months after [MENTION=3685904]ak[/MENTION] moved to N4.

But, frankly, I'm sure it won't beat the feeling of a community that the AK thread or this thread has created. My phone always feels snappier when I'm browsing this thread.

Bottom line, thread and user has been reported. Thread has been closed. If he replies, well. If he doesn't we still have the always-ready-to-bring-more-awesomeness Brian and there's the awesome Stefano to help him. Also Jeremy's settings would make all kernels feel snappier. Basically, be happy with what we got.

</advice>

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

Everything about linux is always WIP. Perfection is getting improved upon everyday:good:
[Samsung Galaxy Nexus] pattyboi:):
that honest to god gave me a total feel of depression. sorry man. if i had the money i would.
[Samsung Galaxy Nexus] Nephilim:
Dude, it's hard as hell to keep up my settings with how quickly this kernel is evolving! We got a total of 5 developers here including Smitty, AK, osm0sis, Grarak and metalspring and a dude with more damn knowledge of android development then I've ever seen! (AOSP)

This thread IS the AK thread on steroids!

The whole reason I created the G+ Community is so we can keep everyone together no matter what devices we all move to. :)

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] büscher:
I don't want to judge him neither in good nor in bad.

He was just very active before he stopped posting all of the sudden - that's what is strange to me.

nevermind, just wanted to add my 2 cents too ;)
[Samsung Galaxy Nexus] Nephilim:
This is true but when his most recent XDA activity was less than 2 weeks ago it would be nice if he at least explained himself in a response to the large amount of us that pm'd him politely asking for him to share his code. AK hasn't built for Gnex in almost a year but he still shares everything he has done with us.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] Nephilim:
Very well put good sir.

*I accept donations in the form of gold doubloons circa 1734 in case anyone would like to contribute.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] Hetalk:
<advice>

I hope you get out of this "useless" mold quickly. I've been a fan of your work (rom builds/music/apps/memes/etc) since long. I've seen your ups and downs with unofficial builds, and xda issues.

It's disheartening to see talent go waste. I understand your need to learn everything at once. But, at times, life needs you to slow down.

</advice>

Damn, this is my 2nd advice for today. Feels like I'm an old guy. :angel:
[Samsung Galaxy Nexus] osm0sis:
Yeah you're right! Your zips look fine. Not sure what this new problem he's reporting is about. Whoever can reproduce it will have to supply more info than just "Status 7" I guess.. ;)
[Samsung Galaxy Nexus] büscher:
Well it was yesterday.... :cyclops:

I'd appreciate it if he would share the code with us! but if the facebook page I found really is him he now has other things to care about ;) but enough stalkin now! damn me I schould be learning for my exams tomorrow. :(

and [MENTION=4608636]bsmitty83[/MENTION] don't think about releasing a new kernel in the next few hours!

edit

could reproduce this as well, but actully I don't have the time..... must. not. sit. at. computer. .....
[Samsung Galaxy Nexus] pianistaPL:
Latest CM 11 Nightly + Dirty v6 SR

Westwood + noop + hyper

Minfree settings from Nephilim custom settings thread

CPU: 180-1500MHz (i don't know why AnTuTu shows 1800)

GPU: 512MHz

Smart Reflex: all off

Multicore power saving: 0

Fsync: off

rest of settings default

So far 13500-13600 is max score that we can get on Dirty_V. 14000 as on Mpokang is impossible because Mpokang gets around twice more points in RAM Operation and RAM Speed.

Ps. I got also 13619 points on Vanir but i don't remember what i/o and governor i was using ;P
[Samsung Galaxy Nexus] büscher:
nothing is impossible
[Samsung Galaxy Nexus] Hetalk:
I'm unable to get even close to what you guys get.
[Samsung Galaxy Nexus] pianistaPL:
Which version of Dirty did you use? ;) Couple of users say that previous Dirty_V were getting better benchmark results.

[MENTION=4278473]Hetalk[/MENTION] Honestly i don't know why you get so low score... I don't know of this is important but i always run benchmark on clean system. So... I install system, switch to ART, disable couple of apps that i'm not using, installing Trickster and Antutu, set custom kernel settings, reboot, i'm waiting couple of minutes to get phone 100% cold and then i run benchmark.

Edit... I can see now that you are not overclocking CPU, so don't worry about this score ;) Most important is to get smoothly phone in daily using, benchmarks are not important, it's just and empty points :P
[Samsung Galaxy Nexus] AuroEdge:
Same bug I experienced on version 5 as on version 6 SR -- I go to wake phone and the touch digitizer will not recognize any finger input. I think it's attributed to touchwake but I am still unable to recreate it. Seems to come at random
[Samsung Galaxy Nexus] gh0stslayer:
<4
[Samsung Galaxy Nexus] büscher:
I'm still on V4 SR, smoothest one for my phone (tried the others tough)
[Samsung Galaxy Nexus] Hetalk:
Oh. I'm not at all a benchmark fan. I just installed antutu yesterday, as I got curious what exactly would be my score.

My device is absolutely smooth with omnimetal, dirty-sr and neph's settings.

Since yesterday, I've been reading a lot about these tunables. I was just wondering, if there are other tweaks/tips to improve upon this perfection.

---------- Post added at 03:03 AM ---------- Previous post was at 03:02 AM ----------

:good::highfive:
[Samsung Galaxy Nexus] aosp:
Closed until further notice..

@OP, maybe I'll receive a reply now.

Thank you.

Keep it closed like the source :D

Took long enough lol
[Samsung Galaxy Nexus] bsmitty83:
Anyone care to test this kernel for me ? I havent yet but I need someone to see how Interactive runs and more importantly wakes up .

Im running an earlier version and it seems ok , nothing obvious in dmsg , and I need to see if I took it too far so to speak

its SmittyV so fsync and no adj smartreflex jsyk

let me know how it goes , This issue is frustrating because even if i cant reproduce what others are experiencing , they might still be there for others since my phone seems magically resistant to these problems

https://www.dropbox.com/s/p19rur3sm6wo5hk/SmittyV-test.zip
[Samsung Galaxy Nexus] ILA:
ART or Dalvik
[Samsung Galaxy Nexus] pianistaPL:
[MENTION=3317173]büscher[/MENTION]

Can you share your settings? :)

[MENTION=4278473]Hetalk[/MENTION]

Yeah, OmniMetal + Dirty_V is extremaly smooth, i used this combo for few days. Now i have CM and i think even is so smooth as Omni :)

[MENTION=4846659]ilans93[/MENTION] ART
[Samsung Galaxy Nexus] Hetalk:
On it now !
[Samsung Galaxy Nexus] oman0123:
Yessssir

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] büscher:
yep ART

You'll find them here: http://xdaforums.com/showthread.php?p=49894778#post49894778
[Samsung Galaxy Nexus] Hetalk:
Sorry buddy. But, wake up issue persists with interactive on this test kernel.
[Samsung Galaxy Nexus] bsmitty83:
OK gimme a sec .... I'd be doing this BTW but I need my phone on right now , can't reboot . I'll have another shortly
[Samsung Galaxy Nexus] ScardracS:
Something is wrong... My best is with 1080p version, 2° with superram and 3° with [MENTION=4608636]bsmitty83[/MENTION] personal value
[Samsung Galaxy Nexus] Hetalk:
Aye Aye Sir.. I'll be on standby. :good:
[Samsung Galaxy Nexus] bsmitty83:
[MENTION=4278473]Hetalk[/MENTION]

ok try this if you dont mind , this is pre 3.4 and what i have on my phone now , seems ok to me again but i cant be the judge of this one ..

https://www.dropbox.com/s/9b0wep4txakz74m/SmittyV--test2.zip

ot : was looking at my dropbox and I still got ak SLK238 kernel in there ..... bout to load up some JB and run it for inspiration :D
[Samsung Galaxy Nexus] Hetalk:
Downloaded and flashing now.

One time I had almost all of AK builds.I still might have them on my old box.

---------- Post added at 03:56 AM ---------- Previous post was at 03:50 AM ----------

All is well with this version. Screen unlocks at the 1st power button push now. :good: [MENTION=4608636]bsmitty83[/MENTION]
[Samsung Galaxy Nexus] michierusama:
So its related to v3.4
[Samsung Galaxy Nexus] Hetalk:
Well, I guess I spoke too soon. It worked quite well for the 1st 10 minutes. After letting the phone on idle for few minutes, it's back to problematic again.

Again, wake up issue persists.I'll flash liquidsmooth (the one that neph's on) and see if it's related to a ROM. [MENTION=4608636]bsmitty83[/MENTION]

Edit: Sorry for getting hopes high. :(
[Samsung Galaxy Nexus] chinitiw:
Days ago I follow this thread and see how glad they all help in improving this kernel @ bsmitty83 great work and thanks for everyone's efforts.

Sorry for my bad English
[Samsung Galaxy Nexus] Grarak:
I already rewrite some stuff from touch wake. Now it's similar like sweep2wake.

But I can also rewrite it to doupletab2wake.

problem is that trickster mod won't recognize it anymore.
[Samsung Galaxy Nexus] bsmitty83:
No see that's the issue , it isn't consistent enough for me to get a handle on
[Samsung Galaxy Nexus] Hetalk:
As I type, I'm backing up my data and will be flashing liquidsmooth. I'll try out these builds on a new rom before restoring my apps. Lets see if it's something with the ROM or a app. Hope to find something positive here.
[Samsung Galaxy Nexus] michierusama:
Good. Report back. ?
[Samsung Galaxy Nexus] bsmitty83:
I'm looking at some things as well , I get an sleeping function called from invalid context in my dmsg so I'm exploring that... I always find positive . this will get fixed , eventually lol
[Samsung Galaxy Nexus] Hetalk:
Of course. :good:

Every problem gets resolved, eventually.
[Samsung Galaxy Nexus] Nephilim:
Well while you guys are doing that I have been spending the last 45 minutes rigorously researching and reading up on Interactive Governor Tunables and different types of Scheduler Tunables. I'm looking to revamp alot of my settings to squeeze a little more battery but pull a lot smoother performance out of DirtyV.

I'm crossing my fingers that Smitty keeps the current v6 Interactive Control Tunables because this is a real pain in the ass lol.