yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Cliff666:
I am still having the sound glitches and stuttering like I had with the last ~5 versions.

Tried Vanir and Liquid Smooth. Art and dalvic. Every setting in trickster I can imagine to be responsible for this...

SmittyV-anykernel-2.23 was the only version which worked perfectly for me.

Here is the dsmsg.log I copied after some stuttering..

https://www.dropbox.com/s/56fk0pkhzmo0cv2/dmesg.log
[Samsung Galaxy Nexus] michierusama:
Like when you lock the phone? And the music stutters but then runs normally?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Cliff666:
No, like when I'm listening music (apollo) and open tapatalk or Chrome. Then the music stutters for about one second.

The stutter when locking the phone i did have on every 4.4 Kernel

Other than that, my maguro is running pretty great.
[Samsung Galaxy Nexus] poo706:
It's Daft Punk!

[poo]
[Samsung Galaxy Nexus] metalspring:
A little off topic here but, wtf gapps??? I swear Google needs to get their gapps fixed from causing something like this

Almost 30,000 wake ups and almost 9 hours keep awake

Btw, I said off topic because this is a gapps issue, not a kernel issue :p
[Samsung Galaxy Nexus] midnightdevil66:
I've been running smittyV 3/2 and no issues at all. Stock setting just changed colors.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] bsmitty83:
Sweet , I like posts' like these .... Lol

No you guys know me , never done . I'm still planning on putting out a new set tonight . just gotta take care of the family first , later tonight I'll have a chance to do everything . still adding things as we speak .

So all the late nighters and non east coast time zone you should have a new kernel tonight :beer:
[Samsung Galaxy Nexus] michierusama:
Oh wow. I think I cannot help you then.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] poo706:
Holy hell! I've never seen anything like that in BBS. I've only had 37 gms wakeups over the last 8 hours.

[poo]
[Samsung Galaxy Nexus] pattyboi:):
*prepares to stare at screen,ready's the F5 finger*
[Samsung Galaxy Nexus] Atento:
I got the same results. Bootloop after restart the phone.

Going back to 0227, because it's perfect for my phone.
[Samsung Galaxy Nexus] milojoseph:
yay early suspenddddddddddddddddddddddddddddddddddddddddd :D
[Samsung Galaxy Nexus] Hetalk:
That counts me in. I'm a far east coaster. It's gonna be day here.

Btw latest smitty version has been running awesome for me since yesterday with LiquidSmooth.
[Samsung Galaxy Nexus] bsmitty83:
Op updated 3/3 , links in the usual spot , I'm

taking my medicine and going to bed lol
[Samsung Galaxy Nexus] pattyboi:):
nighty night smitty! good work as always bro!
[Samsung Galaxy Nexus] DroidOnRoids:
Hmmm, just flashed the 3/3 build and upon entering the Google logo, there are artifacts and graphical glitches all over the place. It sat there for a minute and then rebooted itself again to the Google logo, then bootanimation, and into the system. 3/2 didn't do this to me. Running Shiny Rom.

Update: Just had an SOD after first boot. Pulled the battery and restarted. Seems to be fine in deep sleep now. Will see how this holds up tomorrow.
[Samsung Galaxy Nexus] bsmitty83:
Did it to me too , not sure what its about but It was only on first boot . I thought my battery came out since the cover is off , strange .....
[Samsung Galaxy Nexus] Nephilim:
Not getting deep sleep on 3/3 SmittyV also, uber screen wake lag even with max screen-off set to 700mhz, about a 4 second delay. I recommend ditching early suspend, the last SmittyV's gave great battery without it and had no wake lag.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] bsmitty83:
I was waiting for it , now you know why I didn't want it . its way to slow for me on wakeup . I'll end up reverting it next build .
[Samsung Galaxy Nexus] Nephilim:
Could you do me a favor and link me 3/2 SmittyV for now, I accidentally deleted it.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] metalspring:
It must be your settings, it works perfectly for me with no wake up lag at all. Btw, there shouldn't be ant difference than waking the device up from deep sleep, since early suspend does exactly the same thing only sooner. (Shut down one CPU core then turn it on when screen is turned on)
[Samsung Galaxy Nexus] milojoseph:
Tbis is what I hate.... it works perfectly fjne for me. It helps with battery life. We have enough performance already. Early suspend is that key we need
[Samsung Galaxy Nexus] bsmitty83:
Interactive without it wakes before my finger is even off the button , with it its a good second slower , same settings , same everything
[Samsung Galaxy Nexus] milojoseph:
We are the "dirty" minorties. That battery is the one im worry bout. Smitty has so much optimization I cant believe my phone can handle it. I need my phone to last as well too.
[Samsung Galaxy Nexus] Nephilim:
Well early suspend is the issue for me, if it wasn't then I would have the same wake lag on all the other builds with my settings, which I haven't. I was getting awesome battery with 2/28 without early suspend.

Metalspring, since you compile custom builds with early suspend I see no reason why the normal one needs it. This way everyone wins. ;)

Now could someone please link me 3/2 SmittyV lol.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] buhohitr:
Let give it a test for at least a few days. I will report back. I flashed the RSR version and boot up fine, next will see how well it sleep and wake.
[Samsung Galaxy Nexus] metalspring:
There is a possible comprise though, there are 2 interactive governors in your kernel (regular interactive and dyninteractive), whoever doesn't find early suspend to work well can just use the other interactive gov. That's one reason I ported the early suspend to dyninteractive :)
[Samsung Galaxy Nexus] Nephilim:
You dont need a couple days to see if there is wake lag or deep sleep. You can find that out within 10 minutes. ;)

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] buhohitr:
Ok, will give it 15min see I have the same issue. BTW, I already download all the roms, so I can just test them out on my time. OP can update as he wishes!
[Samsung Galaxy Nexus] Charmacas:
Thanks for trying out the early suspend thingy [MENTION=4608636]bsmitty83[/MENTION]! Did you use the commit from ak. Did [MENTION=4328678]metalspring[/MENTION] use the same?

And for now I have to say that I do not have this wake up lag by now. I tested it three times now and everything went perfect. It's the same as without early suspend. :)

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] wavedashdoc:
Any chance we can get the ram speed patch from mopkang? :) awesome work man, very stable kernel. Still on SR4 with CM11 1/23.
[Samsung Galaxy Nexus] metalspring:
Unfortunately I think thats one of the commits that never got uploaded to mpokangs source :(

I dont know anything about C/C++ but I didnt recognize any of mpokangs later commits as anything that would improve ram speed (I could be wrong though lol)

Btw [MENTION=2853378]Nephilim[/MENTION], have you ever considered trying to build from source yourself at all (whether it be a full rom or just a kernel)?
[Samsung Galaxy Nexus] clnzx2:
I said I was going to provide a log...not sure why you jump on half the stuff I post...I was at work and just wanted to provide quick feedback that the voltage changes didn't make a difference.

1/11 omnimetal

Dalvik

Freezes are completely random and last a few sec and sometimes result in a fc. Changing kernel settings do not seem to affect anything.
[Samsung Galaxy Nexus] juju2011:
Same issue on carbon unofficiai 01/23 art runtime

https://docs.google.com/file/d/0B2bU0b81_b52UFFtNkhMVjdmb3M/edit?usp=docslist_api
[Samsung Galaxy Nexus] wavedashdoc:
Hmm. There must be a way to contact him to get the source. We could go from 729 to 1180. Even though this kernel is fast I can tell I slight difference with certain things loading between the 2.

Also idk if any of you kept up with Franco Kernel, but he decided awhile ago that Smart Reflex was better off. So, even with Mopkang, would turn that off. And copy and paste certain tunables from his settings as well. Specifically voltage settings. Which got me great results, better more stable OC and battery life.
[Samsung Galaxy Nexus] juju2011:
Hmm my phone has no signal now :/ but WiFi works and few mins ago WiFi didn't work and only mobile data did

https://docs.google.com/file/d/0B2bU0b81_b52QVlvRGp5Vk0xQ3M/edit?usp=docslist_api here's a log
[Samsung Galaxy Nexus] clnzx2:
01-24 00:08:33.451 7091 7091 E IMGSRV : :0: gralloc_register_buffer: Cannot register a buffer twice (ID=6)

01-24 00:08:33.451 7091 7091 W GraphicBufferMapper: registerBuffer(0x1ea31e8) failed -22 (Invalid argument)

01-24 00:08:33.451 7091 7091 E GraphicBuffer: unflatten: registerBuffer failed: Invalid argument (-22)

This is what occurs every time I get a freeze...sometimes those entries repeat a few times
[Samsung Galaxy Nexus] sd3993:
That has nothing to do with the kernel. It's a ROM thing. Use paranoid android beta 3 or my custom built pa(has halo and otg working) or metalsprings omnimetal or slimkat or cm.
[Samsung Galaxy Nexus] fracama87:
Your custom pa on which beta is based?

It's time to came back to home :D

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] sd3993:
latest beta 3. It also includes fixes which are not yet on pa beta 3.
[Samsung Galaxy Nexus] clnzx2:
That's what I figured. It is omnimetal though
[Samsung Galaxy Nexus] sd3993:
if u are on the omnimetal of 1/11/14 then those are not the cause of the freezes :)
[Samsung Galaxy Nexus] 3n3rg1c:
[MENTION=4608636]bsmitty83[/MENTION] take a look on Mpokang there is something which is giving great stability,performance & battery out there I get around 14000 on antutu..
[Samsung Galaxy Nexus] Nephilim:
Have you even been following the thread? Mpokang is one of the kernels this is based off of, we've all been discussing it for some time now. ;)

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] clnzx2:
OK here is another log freeze occurred near the end hopefully this one will be helpful https://docs.google.com/file/d/0B3e55iOoULoOd3JKa25OdmRIWXM/edit?usp=docslist_api
[Samsung Galaxy Nexus] 3n3rg1c:
[MENTION=2853378]Nephilim[/MENTION] I know but most thing are based on vanir I guess.

Also forgot to mention I got good performance on cyanfox only but on other I get around 13200... i had this thing on my mind from very long time but came out here today:p
[Samsung Galaxy Nexus] metalspring:
Not a public file?...

You need permission

Want in? Ask the owner for access, or switch to an account with permission
[Samsung Galaxy Nexus] clnzx2:
Sorry I will fix it right now

Should work now
[Samsung Galaxy Nexus] ahmadairfan:
I believe he did it sir, and he struggling hard for it :)
[Samsung Galaxy Nexus] Vekhez:
[MENTION=2853378]Nephilim[/MENTION]

MPU Voltages-

180mhz - 700

230mhz- 720

350mhz- 740

525mhz- 790

700mhz - 890

920mhz- 1030

1.2GHz- 1100 (probably could go lower.. but I don't want to get too low.. since it might be only my phone that can handle that)

1.35GHz- 1140 (this one was kinda finnicky.. going below 1200 just caused a reboot, and above seemed stable, below 1250 seems... 'unsafe'.

1.4GHz - 1240

now I added a bit onto all of these, but I thought that that'd probably make it safer for most devices. If you wanna try these out lemme know how they work. I assume that I don't need to warn you about setting on boot... :P

[MENTION=4608636]bsmitty83[/MENTION] could you add 1036mhz? Since there's a 300mhz jump there..?

---------- Post added at 04:40 PM ---------- Previous post was at 04:37 PM ----------

I think that there was a RAM overclock in Mpokang, it was talked about here, but I think we come to a conclusion of no.
[Samsung Galaxy Nexus] juju2011:
I have no wake up lag but I also have no deep sleep
[Samsung Galaxy Nexus] buhohitr:
After 20min, phone wake up fine, no lag, stills smooth and quick. Will test deep sleep and report back.
[Samsung Galaxy Nexus] milojoseph:
Noob noob noob here...... maybe there is other potential of this early suspend. But one thing that come to mind is that battery life.
[Samsung Galaxy Nexus] Nephilim:
I'm glad you guys have no wake lag, Smitty and I have both noticed it so it exists, at least with Interactive and Early Suspend. I just do not see a big enough battery gain for the lag to be worth it. I'm sure metalspring will keep adding it to his builds so if you want to have it then you can use the metalspring version.

This is all based on if Smitty decides to keep it gone after reverting.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] Charmacas:
You are just arguing for yourself. If some people in here tell you that they have no lag, why are you not even considering changing your setup or see if the culprit is maybe your ROM? I also did that when I had problems.

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] milojoseph:
You are so right........... smitty should just be pure smitty. And early suspend is for pure metalspring. And synapse with ramdisk optimization is for pure omsis. But metal was under the weather and we asked nicely for smitty to add in his build and he did. Majority said no lags whatsoever. So my suggestion temporarily is to revert back to 3/2/14. And call this build smitty MeTal....

---------- Post added at 12:40 AM ---------- Previous post was at 12:38 AM ----------

That too. Trust me suspend early build is a battery life saver by 10% or less.
[Samsung Galaxy Nexus] osm0sis:
Early suspend hasn't caused wakeup lag on any of metalspring's builds. In fact that can't be the problem with 3.3.14, because it's not even working; the device has 0% deep sleep. ;)

Whatever's keeping the device awake is likely causing your problems too Neph. I'm getting a couple freezes and soft boots and Google Keyboard + GNL FCs.
[Samsung Galaxy Nexus] Charmacas:
[MENTION=4544860]osm0sis[/MENTION] good you said that. I've now also noticed that deep sleep is not working. I've reverted back to yesterday's build and there's the same problem I think.

How long do I usually have to wait until deep sleep kicks in? I've waited twice 3 to 5 minutes and after that the device does not sleep deeply. Also the device was under no load at all.

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] cujo6801:
https://www.dropbox.com/s/t20jexac29qx6b8/SmittyV-NoMeM-3.2.14.zip

Sent from the "DOG" pound

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

Hey neph sorry you had to wait I just read your post...

And people this man has put a lot of time in to make your **** run better.

So i was sad to see that nobody was helping him..

Shame people shame..

Sent from the "DOG" pound
[Samsung Galaxy Nexus] cmoG530:
Vanir 3-01 and 3-03 Big Mem with stock settings. No wakeup lag whatsoever. Tested first as soon as my device booted. Then, I left it to sit in for about 20min. No deep sleep though and I've been having that issue since the 28th build.
[Samsung Galaxy Nexus] aosp:
Anybody flash this? http://www.trysoftcore.com/SmittyV-NoMeM-3.3.14.zip
[Samsung Galaxy Nexus] Charmacas:
[MENTION=2838735]aosp[/MENTION] anything we should test with it?

[MENTION=2011394]cmoG530[/MENTION] good input. Could anyone say the same? Is the problem there since the 28th? I did not look at this.

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] DR3W5K1:
Im still on 27th. Deep sleep should be the first thing checked when flashing a kernel. 28th did not like my phone didn't check deep sleep flashed back before I had the chance. I can say the 27th sleeps like a baby on benadryl.
[Samsung Galaxy Nexus] juju2011:
I will now got 30 min or so before baby wake up for her change and feeding
[Samsung Galaxy Nexus] Hetalk:
Recently, smitty nomem builds are the 1st I flash.

This is the 1st one that's treating me badly. Got a few reboots, freezes, FCs (strange) and what not.

Last couple hours, I've been thinking it's bcos of trickster. Now, I see others have it as well. I've got a log as well, if needed.

I just flashed the dirty-v version from today to see how it goes.
[Samsung Galaxy Nexus] paarthdesai:
which version was compatible with touchwake app ? i mean what date's build ?
[Samsung Galaxy Nexus] osm0sis:
I have no issues with deep sleep on my 3.2.14-Synapsed build, and the ramdisk is identical on 3.3 (yay! :)) so it's nothing in that area. The deep sleep issue is only on 3.3 for me.
[Samsung Galaxy Nexus] gohamstergo:
I think the last one was 2/21, which is the one I'm on and the reason I've stayed on it.
[Samsung Galaxy Nexus] Charmacas:
Yeah but [MENTION=4608636]bsmitty83[/MENTION] couldn't extract your zips. And you're using your updated ramdisk. So maybe it's an issue with your old scripts etc. I am going to download your newest zip and flash it over.

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] DR3W5K1:
For anyone that is looking here a link to Osmosis post with his 3.2.14 build.

http://xdaforums.com/showpost.php?p=50771641&postcount=5388

---------- Post added at 02:45 AM ---------- Previous post was at 02:32 AM ----------

^ running like a champ btw
[Samsung Galaxy Nexus] metalspring:
Yeah, that's weird it's not going into deep sleep at all... Even better battery stats isn't picking up any wakelocks keeping it from deep sleeping.

So early suspend is definitely a good thing on the latest build anyway since it is at least forcing one thing that deep sleep does- turning off one CPU core (non boot CPU core).
[Samsung Galaxy Nexus] Charmacas:
I've now tried your last build [MENTION=4544860]osm0sis[/MENTION] and it goes into deep sleep. Then I flashed DirtyV-R from the 3th over it so it and does not go into deep sleep anymore. Hmm...

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] metalspring:
For the no deep sleep issue, this commit looks suspicious

https://github.com/bsmitty83/DirtyV_tuna/commit/6f79e71f5c95e85d1b540a7f0f7b7bbab24a05a0

I'm also having some issues with graphics on some games on the latest build (perhaps the ion and/or gpu commits are to blame?)

The last really great build I have is the 28th, so perhaps mark those versions as a milestone in the op, and keep on going with the newer builds as nightlies until we get another 100% stable, fast build? (Just a suggestion)

Edit: actually if you decide to mark the 28th builds as a milestone build, maybe [MENTION=4544860]osm0sis[/MENTION] can repackage them with the newer ramdisk with updated synapse support
[Samsung Galaxy Nexus] burstlam:
Hi everyone,

I have receive pm from users concerning with PGM/touchwake support for this kernel.

Since touchwake is not compatible with my kernel on latest buid and I have bought PGM only,

that all I can tell is this commit breaks the support of mine (which is based on leanKernel).

Also I have been breaking the support once I have remove tracer support in the kernel

and touch something like upgrading the debug function to 3.4 mainline.

Hope this may help.
[Samsung Galaxy Nexus] bsmitty83:
I am using osm0sis latest ramdisk in 3.3 ,

I'm not seeing any bad GPU performance , 3d in antutu is always 3400+ , so not sure.

But the deep sleep will get figured out . I'll have test zimages going up till it sleeps

heres no 1

https://www.dropbox.com/s/yu1iu9e29hkol4z/TestSleep1.zip
[Samsung Galaxy Nexus] Charmacas:
Cool! [MENTION=4608636]bsmitty83[/MENTION]! :)

Did you make a final decision regarding the early suspend thingy? :)
[Samsung Galaxy Nexus] Hetalk:
Flashed and rebooting. Will report back in few.
[Samsung Galaxy Nexus] metalspring:
The one game I have seems very sensitive to GPU changes for some reason, no idea why though...

The GPU performance is ok, but as soon as I load the game it crashes on the 3/3 builds, but works just fine on 2/28

I'll try to get logs if I can later and see what's up

Then if I feel up to it I might just make a bunch of test builds later to see if any one particular GPU or ion commit is the issue
[Samsung Galaxy Nexus] miesfu:
tired 3.3 smity, got a force reboot, Battery time shows uncorrect. e.g, I change a new battery, after two hours, the battery shows only 27Minutes...

Flansh back to version 2.27, that works best on my Slimkat 3.0 stable version
[Samsung Galaxy Nexus] Hetalk:
No sleep with this one. :(
[Samsung Galaxy Nexus] Cliff666:
Did someone have a look at the log?

I'm back to the 2.23. version because this is a really annoying error.
[Samsung Galaxy Nexus] Ziyan:
02/27th RSR build is pretty awesome, I usually loose between 3 and 8% overnight with 2G, with previous builds, I lost between 30 and 50% while it was in deep sleep :p
[Samsung Galaxy Nexus] pattyboi:):
i dunno if this will be helpful or not,but maybe add in faux's gpu governor system? i added it and ran antutu and got a slight boost,it seems to kinda smooth things out :silly:

got all 5 of the commits some-what towards the bottom of his page :D

https://github.com/pattyboi/kernel_tuna/commits/milestone?page=2
[Samsung Galaxy Nexus] bsmitty83:
I did and low mem killer looks OK , looks like some lost vsync's other than that ,looks OK , no stacks
[Samsung Galaxy Nexus] aosp:
You got a AK2.0 zip with any of the lastest builds?

Stock vanir ramdisk is missing the voodoo you using in the ramdisk zips so newest zImages don't gel with stock vanir I had to flash the last ramdisk zip you uploaded to get my sanity back :/
[Samsung Galaxy Nexus] Cliff666:
Thank you for looking at the log, smitty.

I'll try some other ROMs and trickster settings. Or maybe it's just time for a new phone :(
[Samsung Galaxy Nexus] pvkiniyan95:
Guys I m fed up, went back to smittyvmetal2 with some crazy settings

Min 180

Max 1800

Min screen on 1200

Max screen off 180

Temp lim 60

GPU oc 512

Governed hyper

I/O noop

Other stock settings... [MENTION=2853378]Nephilim[/MENTION] do u think these settings are safe...

Whatever, I m gonna try it....

Obviously performance is great will report battery stats later
[Samsung Galaxy Nexus] Nephilim:
Thats a little insane. First off, 1800mhz is not worth using unless you are looking for a high benchmark score, second, having temp limit set to 60 will throttle the cpu before 1800mhz will ever be useful. I'd be careful. ;)

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] pvkiniyan95:
K...max 1500

BTW for some reasons my benchmark score was always 1500>1800
[Samsung Galaxy Nexus] victor2868:
The latest dirtyv kernel can't seems to compatible with the latest 20140304 cm builds, the phone process is continuously fcing after app optimised
[Samsung Galaxy Nexus] Grarak:
because they need this commit

https://github.com/RomSwitchers/RomSwitcher-tuna/commit/f97217b07c1cbcc9899131f6f9491573beaf5b14
[Samsung Galaxy Nexus] aosp:
Guys if you want flashy just worky I heard stock kernel from Google does the trick but if you want to help [MENTION=4608636]bsmitty83[/MENTION] create awesome and don't mind an occasional oopsie and collecting kernel logs when phone goes crazy coo coo cal bananas ape poo please join in and get some dirt on you're white tee Team Dirty.
[Samsung Galaxy Nexus] pianistaPL:
[MENTION=4699837]pvkiniyan95[/MENTION]

Change sheduler to zen with Nephilims settings:

Zen Control Settings

General I/0 Tunables

add_random: 0

iostats: 0

nomerges: 0

rotational: 0

rq_affinity: 2

I/O Scheduler Tunables

async_expire: 2500

fifo_batch: 0

sync_expire: 304 (won't allow me to set 300, which was my original choice, really don't think there is a difference though lol)
[Samsung Galaxy Nexus] aosp:
That's why zImages bundled with ramdisks should only come from the original ROM and kernel devs should only use AK2.0 from [MENTION=4544860]osm0sis[/MENTION] so any special voodoo can compliment the ROM not bork it dirt diggler style ;)
[Samsung Galaxy Nexus] imjustafq:
am on dirtyv-rsr 3/3.. clock isnt updating.. is it related to kernel?

edit: fixed with a reboot

via my neighbour's forehead
[Samsung Galaxy Nexus] fleckdalm:
Since I flashed this kernel I'm constantly loosing the adb connection to my computer! That's really annoying, any advice?

Thanks,

Regards Fleckdalm
[Samsung Galaxy Nexus] b4u2:
Mine isn't either. Thought it was just me.