yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Nephilim:
For now try holding the power button until it goes on if you run into that issue. It should eliminate having to press it multiple times.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] Vekhez:
Was the ROM that you were on LiquidSmooth..?
[Samsung Galaxy Nexus] bsmitty83:
Not sure I have a fix for that , my phones waking up very fast . maybe too low of min freq ? Idk , I don't have any lag issues of any kind , no freezes . no boot loops nothing . I wish I could help more . I think its got to be a setting or something like that
[Samsung Galaxy Nexus] Nephilim:
Mind posting your settings for comparison?

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] bsmitty83:
I was hoping to mess around with the newer drivers and get WiFi tether to work before I switched , I can't do it in aroma as it needs a recompile .
[Samsung Galaxy Nexus] bsmitty83:
Not at all gimme a sec ...
[Samsung Galaxy Nexus] Nephilim:
Yep. Which means that even if it works for one rom its not for sure to work on all so if anything it would be better to have a separate kernel with the 3.4 drivers while smitty is still refining DirtyV.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] bsmitty83:
My settings

Min - 525mhz

Max -1.5ghz

Max screen off - 700mhz

Iosched- vr

Governor - hyper

Readahead- 768 KB

Tcp- cubic

Cab-off

Fastcharge-on

Fsync-off

Multi core -0

Temp throttle -on

Temp -75

Gpu-512mhz

Zram-on

Smartreflex- on ,all

Colors

All set to 0

Red -225

Green-225

Blue-325
[Samsung Galaxy Nexus] Vekhez:
I can't remember if I used Wi-Fi tethering (if I did it was open), or USB tethering last night, but one of them worked fine.. [MENTION=2838735]aosp[/MENTION] posted a fix for it too
[Samsung Galaxy Nexus] RajatPatel:
I can confirm that it's minimum frequency due to which the issue is caused. 700mhz or above, screen turns on fine. But any minimum frequency less than 700mhz will make scree wake up late. I'm on your latest SR2....

Other than that your kernel is rock solid nd very responsive. In previous version I was experiencing some strange 5 second(or more) freeze, hasn't happened with this one as yet, will report if it happens.

EDIT : After some more testing with different settings I've found out that on hyper governer it wakes up normally at min freq of 350mhz.
[Samsung Galaxy Nexus] drmxmyt:
im also at hyper goveror with minimum 180mhz and its all fine. so the problem gotta be with interactive governor i think.
[Samsung Galaxy Nexus] Nephilim:
I tried out hyper as well just to test it and lockscreen wakes just fine.

This kernel is fast and it sleeps like a baby.

The only issues I still encounter is lockups occasionally when typing (not so much on hyper) and the screen hangs when hitting the recents button or when swiping to get rid of an app in the recents menu. These issues are persistent regardless of the governor or any other tweaks I've tried with the kernel.

Either way, it seems that with each new update comes a smoother and cleaner experience so I look forward to the next update and I'll be sticking with SRv2 for the time being.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] dezful:
Just flashed SR2 kernel on vanir 19/01. No bootloop so far. will post the review later. good job!
[Samsung Galaxy Nexus] poo706:
I just discovered that my phone wakes up like it should with interactive and GPU bumped up to 512. So it looks like it's just the right combos that have problems.

[poo]

Edit: spoke too soon, problem came back. I'll switch to hyper and try that for a while.
[Samsung Galaxy Nexus] Nephilim:
Okay, so after further running I've encountered 2 SOD's. One while my device was charging and one with my phone just sitting on my lap. Going to up the Mpu voltages from -100 to -50 and see if that helps.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] bsmitty83:
No that's just stock , I haven't changed anything . I just it that there to show all the tunables I guess . i was pumped cause every time I've built 3.4 interactive i would get instant sod , not this time though
[Samsung Galaxy Nexus] Nephilim:
Looks like I'm going to have some new tunables to mess with on Interactive! Nice!

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] pkgnex:
Hmm. That's interesting. I've never seen target loads set to zero before.

At any rate, I'm also pumped that the 3.4 interactive commit AOSP pointed you to is working.:good:
[Samsung Galaxy Nexus] szale9001:
Pretty sure that's a TricksterMod deficiency. It can't show target loads when it is set to a string (i.e. 85 1000000:90 1200000:99 or something). If you cat target loads from adb or a terminal, it'll show you the actual value. Weird, but that is how it goes :p

Also, loving this kernel bsmitty, thanks for the hard work!!
[Samsung Galaxy Nexus] Grarak:
Here a secrect tip from me https://github.com/Grarak/grakernel-msm8930/commit/033411a3db7d83364b87dace3369986891673737
[Samsung Galaxy Nexus] bsmitty83:
Nice , thanks man . good commit
[Samsung Galaxy Nexus] Hetalk:
Added to FAQs. Hopefully, there won't be any more questions on this.

Status: Running omnimetal (and loving it) with Smitty5.1. :good:

Waiting for an update on both (and liquidsmooth in case [MENTION=2267583]nasty007[/MENTION] decides to share the art-broken build). :D

[MENTION=4608636]bsmitty83[/MENTION] Nice to know you're a family guy, as well. :highfive:
[Samsung Galaxy Nexus] metalspring:
On my part, I might have some interesting builds coming soon

Link time optimization and graphite optimizations anyone? ;)
[Samsung Galaxy Nexus] pattyboi:):
ohhh that sounds good :3
[Samsung Galaxy Nexus] Hetalk:
Sounds tasty. I'll eat it.
[Samsung Galaxy Nexus] pattyboi:):
enhanced flavor omni-kitkats :D
[Samsung Galaxy Nexus] osm0sis:
Bingo. :)

The 3.4 kernel on my N7 2013 uses those strings, looks like it cleverly defines ramping levels at different frequencies. Very cool. :D
[Samsung Galaxy Nexus] Kaemo:
Can't wait for the next update!
[Samsung Galaxy Nexus] milojoseph:
and boom, bootlooped. This kernel is not compatible with SOME 4.3.1 rom. And yes im aware it says 4.4. But people said it can work with 4.3.1.
[Samsung Galaxy Nexus] michierusama:
Is bad to read that. Hope you can fix your Gnex. And this is getting interesting to read as days go by.
[Samsung Galaxy Nexus] pattyboi:):
its such a great thread,just the happiness and work ethic and respect smitty has created in this thread is great,i read it everyday,i actually read it more than my facebook lol
[Samsung Galaxy Nexus] michierusama:
That's true. Obama aproves. :good::cyclops:
[Samsung Galaxy Nexus] aosp:
Good ish bro ;)
[Samsung Galaxy Nexus] kuronosan:
Yes, just ignore what the creator said.
[Samsung Galaxy Nexus] bsmitty83:
Ok V6's are up in the OP ,

removed ondemandplus and added ondemandX

removed Interactive and reintroduced it up to 3.4

reverted RAM oc

can revert to old style fast charge through sysfs

ummm ,,, flash or look at my github if you wanna know more :silly:

[MENTION=4328678]metalspring[/MENTION] -- check DirtyV Defconfig plz , I hope I put logging back in and everything else
[Samsung Galaxy Nexus] michierusama:
Omg there's an update¡¡¡¡ buenooooo
[Samsung Galaxy Nexus] metalspring:
did you flash any other kernels before dirtyv? Some kernels include their own ramdisk which can cause issues with other kernels unless you reflash the rom again first (Like the mpokang kernels for example)
[Samsung Galaxy Nexus] aosp:
[MENTION=4608636]bsmitty83[/MENTION] [MENTION=4443334]Grarak[/MENTION]

You guys might find this tool useful ;)

Linux kernel patch static verification tool

nmenon/kernel_patch_verify · GitHub - http://goo.gl/nUS6Au
[Samsung Galaxy Nexus] bsmitty83:
Pretty cool stuff , I'll be bookmarking that one .
[Samsung Galaxy Nexus] metalspring:
First off, dev host is getting annoying with the stupid app it downloads every time you go there (spam much? Lol)

You ever think of asking [MENTION=4244313]MBQ_[/MENTION] if he could host your downloads? Or use mediafire? (less spam)

Second of all just looking at the dirtyv defconfig it looks like logcat should be back on (android logger)

Will test them all soon to see :)
[Samsung Galaxy Nexus] pattyboi:):
please tell me im not the only one not getting a boot up?..
[Samsung Galaxy Nexus] michierusama:
Explain that to me
[Samsung Galaxy Nexus] pattyboi:):
phones not booting lol,boots with v5,but not v6 :P
[Samsung Galaxy Nexus] michierusama:
OMG and I was thinking to flash right now... I'm on maguro... should I wait? :fingers-crossed:
[Samsung Galaxy Nexus] pattyboi:):
i dunno bro,im trying to see if its something on my end,im gonna try SR version and see if it boots or not,maybe its just me :silly:
[Samsung Galaxy Nexus] Nephilim:
Yep, same here. Bricks my device until I revert back to either v4 or v5. Basically it hits the splashscreen the screen goes black and becomes inoperable until you battery pull and boot to recovery.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] michierusama:
??? well let's see. Good luck and report back.

OMG well I think ill wait
[Samsung Galaxy Nexus] bsmitty83:
Smitty is good , I got to fix others brb
[Samsung Galaxy Nexus] KJW979:
V6 not booting for me either, gets to Google screen then shuts down. Have to do battery pull, reboot to recovery reinstall v5, boots up. That's SR version
[Samsung Galaxy Nexus] pattyboi:):
smitty to the rescue again. :)
[Samsung Galaxy Nexus] clnzx2:
I offered him hosting but never got a response :(
[Samsung Galaxy Nexus] bsmitty83:
my bad man , not on purpose , pm me and we'll set somthing up if you dont mind

just been busy as of late
[Samsung Galaxy Nexus] bsmitty83:
I figured it out , bad configs , sorry bout that . gotta build one more then good . I'm running dirtyV-SR now
[Samsung Galaxy Nexus] pattyboi:):
yay :) your the best smitty :) been f5ing like a MF'er lol :P
[Samsung Galaxy Nexus] clnzx2:
Not a problem I will send you a pm

Sent
[Samsung Galaxy Nexus] bsmitty83:
DirtyV6-SR shoud be ok , Link back up ....
[Samsung Galaxy Nexus] fracama87:
One page of comments every hour? That's really gonna be crazy guys. O.o

Edit: I was wrong... 7 pages in 4 hours!

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] michierusama:
Great! Im going to test now. Flashing 02/03/2014 CM11 nightly and Dirty V6 I'll report back.
[Samsung Galaxy Nexus] KJW979:
New V6SR boots up fine. Now to compare to V5, cause that one and latest liquid was fantastic together.
[Samsung Galaxy Nexus] bsmitty83:
DirtyV is back up , Link is good as well

enjoy:good:
[Samsung Galaxy Nexus] metalspring:
I don't know how you manage to build 3 separate only slightly different kernels. I'm sure it helps actually knowing kernel coding but just going through the menuconfig options (which is basically turning on/off all the different kernel features for everyone they doesn't know) is confusion enough, let alone trying to keep the defconfig right though all the different changes (also for those that don't know, the defconfig is just the menuconfig presets so you don't need to go through menuconfig just to build right every time) is confusing enough just for one version of the kernel lol

Basically awesome job [MENTION=4608636]bsmitty83[/MENTION], not many kernel devs would update so often AND offer 3 different versions :)
[Samsung Galaxy Nexus] fracama87:
Yeah 3 different versions are pretty rare but I've never seen so many updates!

I've downloaded just now and I'll flash going to bed :)

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] michierusama:
He loves this man. Just like you do! keep the great work so we can keep on saying devs on XDA are the best!
[Samsung Galaxy Nexus] bsmitty83:
Github helps so much , it wouldmt be possible without . gitk is a great tool , I use it a lot , I basically keep 3 defconfigs , and update them by after a build before checkout of that branch I copy the .config to the defconfig . but somehow 2 of them got FUBAR'd so I had to manually do up 2 . no big deal .

I appreciate the kind words , from everyone , I know how much you guys appreciate it so I do it no problem plus
[Samsung Galaxy Nexus] Nephilim:
V6 is running awesome with the new Interactive. I've already tweaked the new governor control tunables added and they're pretty much perfect in my opinion. I'm going to hold off on posting them until morning though to make sure everything is good. Until then, anyone using my settings keep using the same posted Interactive tunables and leave the new one's on the default settings. :)

(I may post my updated interactive control earlier than morning if things keep running as smooth as they are now and the GF goes to bed early enough.) :p

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] bsmitty83:
I'm running dirtyV right now .. Butter smooth IMBO :sly:
[Samsung Galaxy Nexus] lilz4life:
are you running your personal build ?

i wana run exactly what the great bsmitty is running on his phone :o
[Samsung Galaxy Nexus] bsmitty83:
Not at this second dirtyV was last tested on my phone haven't reflashed is all . I use smittyV normally
[Samsung Galaxy Nexus] klobkelosh:
V6 indeed. This thing is hauling...Thanks Smitty!
[Samsung Galaxy Nexus] milojoseph:
I know I read it. It say 4.4 only. but majority of the 4.4 kernel work perfectly fine for 4.3.1. Someone recommended me cause he has a 4.3.1 rom and it works. I know smitty wont create one for 4.3. But all I have to say is thqt this is the best kernel . I enjoyed the speed for about 2 day. Thanks to backing up I can try this new update
[Samsung Galaxy Nexus] michierusama:
Cm11 02/03 nightly and dirty v6 and nephe settings. All under control.
[Samsung Galaxy Nexus] garyngkt:
Same here =). So far so good and waiting for Nephilim's new settings update :victory:
[Samsung Galaxy Nexus] Charmacas:
Thanks for the new update!

I noticed two things: Dynamic FSYNC is on again in the default setting and the min screen on frequency is not sticking. It always uses the min one.

And for everything else... We'll see through the day! ;)

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] michierusama:
The wake up lag omg its happening lmao. Well ill try a little more.
[Samsung Galaxy Nexus] Nephilim:
Min screen-on will never be able to go below min.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] lazydognet:
Same here when using Interactive and v6

LDN
[Samsung Galaxy Nexus] Charmacas:
I wrote it goes down TO the min frequency. Not below it. :)

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] furiyk:
Also having wake up lag with interactive
[Samsung Galaxy Nexus] David 617:
Ditto.

Its interesting though. I only get the lag occasionally when I press the power button.

But if I plug in the USB cable it always turns on right away.
[Samsung Galaxy Nexus] alfiemenace:
Weird, I don't have the wake up lag with v6, using nephilim's settings, omnimetal
[Samsung Galaxy Nexus] Nephilim:
I've got no lag on screen wake as usual. Girlfriend is playing Guitar Hero so I'll most likely be posting my updated settings for Interactive Control pretty soon along with possible Fiops I/O tunable controls tweaked as well. (maybe)
[Samsung Galaxy Nexus] raikkoni27:
can the touch wake be modified to double tap to wake?
[Samsung Galaxy Nexus] Nephilim:
This topic is starting to get ridiculous just as it used to on the AK thread.

Touch Wake is available and working in this kernel, if you do not want the single touch, which is what "touch wake" is, then message the developer of another Touch Wake type app like PGM for example and ask him to make it compatible with DirtyV kernel.

Touch Wake is one touch to wake the device as far as the kernel goes, anything else can be accessed by finding a compatible app that does more.

---------- Post added at 12:55 AM ---------- Previous post was at 12:35 AM ----------​

My custom settings for DirtyV have been updated, see my thread for more info.

​

:D
[Samsung Galaxy Nexus] Charmacas:
I think what the poster meant is an own implementation of double touch to wake. I posted some commits in the fancy kernel thread some time ago. I am on my way to work. When I am there I will search for them and post here.

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] Vekhez:
I'm gonna be that guy.. Can we call the thread

[KERNEL] [4.4] [Linaro 4.7.4] **Dirty_V** [V6] ( 02-03-14 )

Just so that it's clear that there's a kernel update, just because when going through at a quick glance, I don't pay attention to the date :P
[Samsung Galaxy Nexus] Charmacas:
Doubletap2wake

Here's the XDA thread: http://xdaforums.com/showthread.php?t=2389022

And here's the commit: https://github.com/flar2/flo-ElementalX/commit/1466cb8f7ec251104818354eb2208f0f395fedcd
[Samsung Galaxy Nexus] ak:
The kernel log posted don't show any problem.

Could be the problem inside the ROM?

AK&4&7
[Samsung Galaxy Nexus] Charmacas:
Thanks for looking in there [MENTION=3951473]AK![/MENTION]

Hmm... I don't know. Maybe I just don't get the right messages. I did not have much time this morning to get the log. :)
[Samsung Galaxy Nexus] ak:
With cable plugged you dont have lag because kernel dont sleep.

AK&4&7

---------- Post added at 09:07 AM ---------- Previous post was at 09:04 AM ----------

No problem man. ?

AK&4&7
[Samsung Galaxy Nexus] metalspring:
[MENTION=3685904]ak[/MENTION] [MENTION=4608636]bsmitty83[/MENTION] any chance these commits might help with the binder: transaction failed lines in dmesg?

https://github.com/franciscofranco/Tuna_JB_pre1/commit/59bc19226c746f479edc2acca9a41f60669cbe82

https://github.com/franciscofranco/Tuna_JB_pre1/commit/cf2d523ae4847db7f9ed6069afe932678a62a93a
[Samsung Galaxy Nexus] Charmacas:
<4>[ 6739.523956] r8:a095a97c r7:00000000 r6:a08db8dc r5:a08db08c r4:00000001
<4>[ 6739.523986] [<a00b781c>] (disable_nonboot_cpus+0x0/0xfc) from [<a00f3f14>] (suspend_devices_and_enter+0x150/0x2ec)
<4>[ 6739.524017] r8:00000000 r7:a096d3ec r6:a080b1ec r5:00000003 r4:00000000
<4>[ 6739.524047] r3:00000000
<4>[ 6739.524078] [<a00f3dc4>] (suspend_devices_and_enter+0x0/0x2ec) from [<a00f41c8>] (enter_state+0x118/0x144)
<4>[ 6739.524108] [<a00f40b0>] (enter_state+0x0/0x144) from [<a00f4210>] (pm_suspend+0x1c/0x28)
<4>[ 6739.524108] r6:000132bb r5:a096d3f0 r4:a0902b98 r3:00000002
<4>[ 6739.524139] [<a00f41f4>] (pm_suspend+0x0/0x28) from [<a00f520c>] (suspend+0x64/0x198)
<4>[ 6739.524169] [<a00f51a8>] (suspend+0x0/0x198) from [<a00d05f4>] (process_one_work+0x140/0x480)
<4>[ 6739.524200] r8:00000000 r7:d081da00 r6:a095bc20 r5:bb38c000 r4:ccb47580
<4>[ 6739.524230] [<a00d04b4>] (process_one_work+0x0/0x480) from [<a00d0c64>] (worker_thread+0x13c/0x320)
<4>[ 6739.524261] [<a00d0b28>] (worker_thread+0x0/0x320) from [<a00d5d38>] (kthread+0x8c/0x94)
<4>[ 6739.524291] [<a00d5cac>] (kthread+0x0/0x94) from [<a00b93d0>] (do_exit+0x0/0x700)
<4>[ 6739.524322] r6:a00b93d0 r5:a00d5cac r4:bb215ed4
<3>[ 6739.638885] sys_chown: boostpulse error: -2
<5>[ 6739.640686] CPU1: shutdown
<6>[ 6739.641571] Resume caused by IRQ 163, gpio_keys
<6>[ 6739.641571] PD_CORE curr=ON prev=ON logic=ON
<6>[ 6739.641571] PD_L3_INIT curr=ON prev=ON logic=ON
<6>[ 6739.641571] CD_L3_INIT mode=SW_WKUP activity=0x5300
<6>[ 6739.641571] USBPHY mode=AUTO idlest=ON optclk=0x100
<6>[ 6739.641571] DPLL_USB status=locked
<6>[ 6739.641571] Powerdomain (core_pwrdm) didn't enter target state 1 Vs achieved state 3. current state 3
<6>[ 6739.641571] Powerdomain (l3init_pwrdm) didn't enter target state 1 Vs achieved state 3. current state 3
<3>[ 6739.641571] Could not enter target state in pm_suspend
<6>[ 6739.641662] Suspended for 0.688 seconds
<6>[ 6739.641876] Enabling non-boot CPUs ...
<4>[ 6739.658203] CPU1: Booted secondary processor
<6>[ 6739.664062] Switched to NOHz mode on CPU #1
<3>[ 6740.101806] sys_chown: boostpulse error: -2
<6>[ 6740.101959] CPU1 is up
<6>[ 6740.103546] PM: early resume of devices complete after 1.586 msecs
<6>[ 6740.104156] wakeup wake lock: gpio_input
<6>[ 6740.198577] PM: resume of devices complete after 94.665 msecs
<7>[ 6740.200347] PM: Finishing wakeup.
<4>[ 6740.200378] Restarting tasks ... done.
<6>[ 6740.222045] suspend: exit suspend, ret = 0 (2014-02-04 08:33:18.535155272 UTC)
<6>[ 6740.222076] active wake lock KeyEvents
<6>[ 6740.259857] request_suspend_state: wakeup (3->0) at 6740244236878 (2014-02-04 08:33:18.572936050 UTC)
<6>[ 6740.609527] DSSCOMP: dsscomp_late_resume
<6>[ 6740.609588] enable touch controls
<3>[ 6751.713897] init: untracked pid 13591 exited
<6>[ 6751.899078] max17040 4-0036: online = 1 vcell = 3911250 soc = 74 status = 2 health = 1 temp = 320 charger status = 0

May this log help with wake up issues?

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] gautam_nexus:
Neph your settings are dope man. Just applied your settings on V6 and my phone seems to be flying. Waiting for your updated settings.
[Samsung Galaxy Nexus] lagendbun:
this thread is going to fast very usefull..i learn a lot about kernel...every hour full 1page with comment... :good:
[Samsung Galaxy Nexus] chainrulez:
yes wake up lag here as well at interactive. Using hyper, working smooth now.
[Samsung Galaxy Nexus] metalspring:
hmm, maybe this will help for this? BUG: scheduling while atomic: kworker/u:5/5624/0x00000002

https://android.googlesource.com/kernel/common.git/+/b903216e8149bc3a226c2c997f803edcb3d0ff7c
[Samsung Galaxy Nexus] gautam_nexus:
I am using force fast charge but its still show USB charging instead of AC in the battery screen. is this expected.?
[Samsung Galaxy Nexus] metalspring:
Yes
[Samsung Galaxy Nexus] lagendbun:
interactive wake up lag? i press power button so many time and i am using [MENTION=2853378]Nephilim[/MENTION] setting.
[Samsung Galaxy Nexus] garyngkt:
I have wake up lag also on interactive running V6 and with Nephilim settings
[Samsung Galaxy Nexus] Vekhez:
Try using the ondemandx settings, that's what I am currently using, and it's working very well.
[Samsung Galaxy Nexus] bsmitty83:
I get the same stacktrace . I don't know what exactly is the issue with it but I'm still looking into it
[Samsung Galaxy Nexus] Sheetzie03:
I just dl v6. I do notice the What everyone is saying about waking up the device, but it's not that bad at all. Instead of lightly pressing the power button like usual and it waking up, all you have to do is hold down the button EVER so briefly, and it wakes up just like it's suppose to. Js

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] flip360:
bsmitty GREAT job with the kernel, V6 running nicely here along with interactive and row, in the last 20 min. i have been trying to reproduce the wake up lag with interactive but as Nephilim said its not there for me, every time i press the power button the device wakes up instantly (tested with pressing power button multiple times in a row and with leaving the device for 2-3 min. to sleep and than waking up). Using the inbuilt performance control on Carbon KK Rom on GSM maguro

Cheers
[Samsung Galaxy Nexus] Charmacas:
What is your Dynamic FSYNC setting?
[Samsung Galaxy Nexus] flip360:
as i am using the inbuilt performance control from the ROM, i have to say stock as i dont have the option to fiddle with it :)
[Samsung Galaxy Nexus] Charmacas:
So that means you have Dynamic FSYNC enabled, which also means your system is more responsive but with the risk of data loss.

[MENTION=4608636]bsmitty83[/MENTION] forgot in the version 6 to disable Dynamic FSYNC on default.

Could you please disable it and check if the wake up problem still does not exist?
[Samsung Galaxy Nexus] gautam_nexus:
Use touch to awake if your facing lag lockscreen lag issue.
[Samsung Galaxy Nexus] sajty:
OMG.Slow down guys,this thread is growing so fast that i am not able to read all posts! :D Here,it looks like AK thread in the halcyon days.

On topic.Wake up delay is here,but nothing special.I had very similar delay with Tiny kernel too.Some people are perfectionists :D
[Samsung Galaxy Nexus] pkgnex:
Yes.

The weird thing is the delay was there on v4, "fixed" on v5, but returned on v6 (all the dirty-V version for me).

I don't know if that narrows anything down for smitty, but I hope so!