yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] osm0sis:
Thank you! Summed up "race-to-idle" perfectly! :)

My best guess is the added CM telephony-msim.jar and/or PAC framework-pac.jar to BOOTCLASSPATH makes Vanir angry. That's stupid though, because it doesn't happen on other ROMs that also don't have it.

Yeah.. usually what you see on CM without telephony-msim.jar in the BOOTCLASSPATH. This makes no sense. Can you point me to the exact ROM build you're using? I'll diff these f*ckers again.. :confused:
[Samsung Galaxy Nexus] dbt816:
It was a cruel life-lesson in flashing nightly ROMs and kernels at work and being without a phone :laugh:
[Samsung Galaxy Nexus] wisefreakz:
Latest VanirROM 3/3.
[Samsung Galaxy Nexus] osm0sis:
DHO/Commotio or NuclearMistake?
[Samsung Galaxy Nexus] cmoG530:
Downgrade to 3-01. There hasn't been too many additions, to justify not using this kernel. Unless, you're a crack flasher, then disregard. Lol
[Samsung Galaxy Nexus] wisefreakz:
Nuclear

---------- Post added at 12:37 AM ---------- Previous post was at 12:36 AM ----------

I tried to 3-02 and even without touching the kernel I got same result... Like something higher has gone wrong.
[Samsung Galaxy Nexus] osm0sis:
So.. sounding like Vanir's derp, not ours? I got both DHO's and NM's builds. Going to comb through one more time just to be sure it's nothing on our end I can fix.

Just so everyone understands, having stuff in BOOTCLASSPATH that doesn't exist on your particular ROM should never cause a problem. For example, in f.K back with JB4.3 we already had the telephony-msim.jar and framework-pac.jar changes in for ages (those features are just now making it to KK4.4) and there was no issue with other ROMs from that time up until now.

Also nothing DirtyV does to /system (hostapd, media_profiles.xml) is permanent, an init.d script undoes those as soon as you're not on DirtyV anymore so if you've got an issue before you reflashed DirtyV, that's a ROM issue. I operate on the principle that kernels should be plug-and-play. :)
[Samsung Galaxy Nexus] wisefreakz:
Thanks for clarifying and the support!!!
[Samsung Galaxy Nexus] cmoG530:
The reason I suggested 3-01, is because that has been the last stable nightly. In the G+ community, people across various devices has had the same issues with 3-02 and 3-03, but have been okay with 3-01.
[Samsung Galaxy Nexus] wisefreakz:
Ok... Will report back in a few moment!
[Samsung Galaxy Nexus] cmoG530:
Correct. I'm running the latest Dirty V with Vanir 3-01 and everything's running fine. Dave said that something was wrong with git and that he was working on it.
[Samsung Galaxy Nexus] osm0sis:
In other good news my AnyKernel 2.0 thread is now live:

http://xdaforums.com/showthread.php?t=2670512

:highfive: :good:

Aw f*ck.. actually it is our fault. Sort of. Moreso GitHubs? Not sure. Vanir requires telephony-msim.jar to be in BOOTCLASSPATH, like CM does, so that's why you were seeing that error..

"But os, that only happens when it's not there!" you say! Well.. yup. You're right.

https://github.com/bsmitty83/DirtyV_tuna/tree/DirtyV2/ramdisk-DirtyV

It IS there.. because I put it there.. but not in the ramdisk.

[MENTION=4608636]bsmitty83[/MENTION] Somehow not everything that got commited ended up in the 3.4.14 ramdisk. :confused:
[Samsung Galaxy Nexus] DR3W5K1:
Must be your stubborn Canadian zips again.

:p
[Samsung Galaxy Nexus] osm0sis:
Nah, no zips involved. Should've just been able to pack what was committed on GitHub. :confused:

My stubborn Canadian zips will save our asses if Smitty doesn't feel like doing 3.5.14 tonight. :p
[Samsung Galaxy Nexus] wisefreakz:
[MENTION=2011394]cmoG530[/MENTION] no go with 3-01... Without flashing a diff kernel, still same acore and phone error.

Maybe its time for a clean flash?

Weirdly always when I flash 3-03 all comes to normality.
[Samsung Galaxy Nexus] DR3W5K1:
Just a heads up for anyone that has or had a droid x. They just got cm11 booting on it which is a huge feat considering the last version of android they had hacked up for it was ICS.

Ofcourse i can't find my droid x anywhere.

Neway I'm really excited and hopeful that we will see the next version of android on our tunas.

I know this is a bit ot but what do you guys think? Will we see the next version of android or more importantly next version of dirty v on our tunas?

Keep in mind they accomplished this with a locked bootloader and 512mb of ram.
[Samsung Galaxy Nexus] osm0sis:
The fix is in. Any further problems are definitely your ROM. :p

DirtyV -- Ambien Edition Reloaded:

http://v.ht/osmod or http://d-h.st/users/osm0sis/osmod

DirtyV-R-3.4.14-Fixed

DirtyV-RSR-3.4.14-Fixed

SmittyV-R-NoMeM-3.4.14-Fixed

http://www.google.ca/images?q=ambien+walrus
[Samsung Galaxy Nexus] chainrulez:
Sorry for the question but I couldn't understand the thing here that why we have two versions like in this case RSR & NoMeM? why not RSR as more memory is good. Just wanted to clear my logic as I've read everywhere but I think I couldn't get the other difference than the memory size. :p
[Samsung Galaxy Nexus] hawkstorm:
I downloaded the latest Kernel.. and installed it on a CM11 build. I can't seem to reflash anything now. HELP
[Samsung Galaxy Nexus] lileoja:
Hello friends a question, which version of the kernel is compatible with cyanogenmod 11 nightly ?
[Samsung Galaxy Nexus] cmoG530:
Clean flash, most definitely. I always clean flash every nightly, but that's more of an OCD type of thing.lol

EDIT

Try flashing Osmosis' kernel and see, before reflashing the ROM again.
[Samsung Galaxy Nexus] 3n3rg1c:
Any progress on RAM oc timings??
[Samsung Galaxy Nexus] cmoG530:
It's more memory, but it comes at the cost of having some things broken. Like the YouTube app. It has a really hard time playing videos with supertram. Whereas none at all with regular RAM, or no RAM. I think it affects the camera too, but I can't really recall it. I'm sure someone will explain it better. :p lol
[Samsung Galaxy Nexus] Unzitron:
Just installed 3.4.14 on omnirom toro and it was lagging at everything until I turned off mcps. Now, it fast as always... Weird.
[Samsung Galaxy Nexus] osm0sis:
My version, above, is. Flash away. :)

[MENTION=4335391]hawkstorm[/MENTION], don't panic. Battery pull. Reinsert the battery. Hold down all 3 buttons to get to the bootloader. Go to recovery. Download my zip above to your computer. Connect a USB cable to the computer. adb push the.zip /data/media/0/ then flash it. :good:
[Samsung Galaxy Nexus] chainrulez:
Alright great, that's something useful, thanks a lot :D
[Samsung Galaxy Nexus] wisefreakz:
We have a winner!! [MENTION=4544860]osm0sis[/MENTION] it worked like a charm on the freaking Vanir 3-03

Thanks a Zillion!!!

[MENTION=2011394]cmoG530[/MENTION] thanks for your support as well.
[Samsung Galaxy Nexus] hawkstorm:
ITrying it now. Already tried flashing with CWM 6.0.4.7. it's booting up. But I have to wait to see if it worked :S
[Samsung Galaxy Nexus] osm0sis:
Awesome! Yeah, sorry it took so long to figure out. It never occurred to me that what I committed on GitHub somehow wasn't what made it into the release. :silly:

I'm forcing one more little fix to the media/hostap/powerhal restore onto Smitty's GitHub via a pull request then I'm off to bed. Listen to the Ambien Walrus / Fend fo' yo'selfs suckas! :p

I'm sure [MENTION=4608636]bsmitty83[/MENTION] will figure out how the wrong files got in there and grab the right ones from the source and we'll be back to business as usual for 3.5.14 tomorrow. :)
[Samsung Galaxy Nexus] hawkstorm:
[MENTION=4544860]osm0sis[/MENTION] it seems like it didn't work. :'( still stuck
[Samsung Galaxy Nexus] Hetalk:
OT

I know the feeling. I got a samsung galaxy sl 9003. Last firmware from sammy was gingerbread with 2.6 kernel. Thanks to an awesome dev, we have a working cm11 with kernel 3.x. BTW, want me to ask him to help us with 3.4 kernel? He's a pretty good with omap devices?

On topic.

I'm running the latest smitty version and phone goes to deep sleep pretty well. Running pretty smooth so far.

Somehow, I don't see any wake-up lag. :cowboy:
[Samsung Galaxy Nexus] wisefreakz:
What's wrong?
[Samsung Galaxy Nexus] hawkstorm:
[MENTION=4544860]osm0sis[/MENTION] It just doesn't flash anything./ I tried flashing a new ROM , factory reset nothing works
[Samsung Galaxy Nexus] wisefreakz:
What is the error?
[Samsung Galaxy Nexus] hawkstorm:
No error. Recovery says that it's flashed. When I boot it still boots the same thing.
[Samsung Galaxy Nexus] wisefreakz:
So you are in bootloop? Google loop or ROM loop? Which ROM?
[Samsung Galaxy Nexus] hawkstorm:
This was on CM11 20140304 nightly. It boots into the ROM. But everything's stuttering and lags like a cow. Kernel doesn't seem to change either

---------- Post added at 02:48 PM ---------- Previous post was at 02:47 PM ----------

Developer menus seem to be missing :(
[Samsung Galaxy Nexus] wisefreakz:
I would suggest to you to switch ROM for a moment... Just to make sure it will refresh things on your SYSTEM partition.

Try SlimKat or VanirAOSP(02-03)

Can you do that?

Edit: do you have Synapse installed? If yes, before you do this ROM switch, try remove synapse, reflash [MENTION=4544860]osm0sis[/MENTION] fixed kernel and see what happens.
[Samsung Galaxy Nexus] hawkstorm:
Tried that... didn't work. Tried flashing CM Remix it didn't take. Tried flashing twrp... didn't take either.
[Samsung Galaxy Nexus] redj12:
Guys can you tell me the stock MPU values ?

Envoyé de mon Galaxy Nexus en utilisant Tapatalk
[Samsung Galaxy Nexus] Vekhez:
The stock voltages on stock kernel? They're crazy different since there's only like 4 frequencies.
[Samsung Galaxy Nexus] redj12:
Stock voltages on Dirty kernel.

Buddy I am using your settings and...no freeze !! It's not a placebo :)

Envoyé de mon Galaxy Nexus en utilisant Tapatalk
[Samsung Galaxy Nexus] Vekhez:
Awesome :D So that's one person, going any lower could cause a freeze, but undervolting will save battery none of the less, so :D Now combine them with [MENTION=2853378]Nephilim[/MENTION]'s settings and my other voltages (in green) on page 49, if still no freeze, that's a good sign, get a few more and it could be streamlined :D

And maybe someone can post the stock mpu voltages with a screenshot, since I can't get em back, im using my settings :P
[Samsung Galaxy Nexus] Nephilim:
So some of you guys may have already done this but I'm just letting you all know that I tried to contact Mpokthws about updating his git so that others can take advantage of his ramspeed optimizations/ram overclocking. Crossing my fingers on a response sometime soon. :)

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] Rushead:
Only Smitty could have a thread that passes 500 posts in a handful of days. :good:

Sent from a flashead cracker.
[Samsung Galaxy Nexus] ahmadairfan:
So here's the stock voltage on SR5 guys.

BTW I'm gonna try your settings Vekhez and Nephilim :good::victory:
[Samsung Galaxy Nexus] Nephilim:
I've thought about it but I still need to seriously upgrade my rig first and foremost and secondly, you all do such an amazing job that I'm quite content making my contributions by testing and reporting my findings for the time being.

Btw, I posted that commit reversal you suggested on the Liquidsmooth thread over on their G+ and Sean Hoyt already took care of it. Now I'm anxiously waiting for a new update so I can test if ART is back to normal again!

Thanks for posting that recommendation!!

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] Vekhez:
Awesome :D Let us (well me anyway :D ) know how they go!
[Samsung Galaxy Nexus] 3n3rg1c:
edit: delete
[Samsung Galaxy Nexus] Vekhez:
Really really really OT.. but that's for your great ROM for the Atrix :D Seems that a few Atrix users (such as myself) have moved to the GNex :P
[Samsung Galaxy Nexus] 3n3rg1c:
[MENTION=5427457]Vekhez[/MENTION] Actually I posted wrong thing here. I mean wrong thread..
[Samsung Galaxy Nexus] Vekhez:
lolol, sorry I was supposed to write thanks, not that's :P
[Samsung Galaxy Nexus] ahmadairfan:
Hey [MENTION=5427457]Vekhez[/MENTION], tried your CPU voltages... Did reboot many times lol guess I have to UV myself eh :p

Edit: I meant MPU
[Samsung Galaxy Nexus] Charmacas:
I also wrote him some weeks ago. Hopefully he answers.
[Samsung Galaxy Nexus] Vekhez:
Could you add 10 until you get no reboots.. id like to find a UV that most devices can handle, when you let me know I'll change em in my post.
[Samsung Galaxy Nexus] Firewalker1980:
Quick question.

When I use Antutu (or other benchmark tools), I never get the same result twice.

I guess that's inevitable, but is there a way to get more consistent testresults?

Like once it could be 10600 and the next time 12400 and another time 13800, all on the same rom, kernel and battery %
[Samsung Galaxy Nexus] ahmadairfan:
Okay, will report soon :)
[Samsung Galaxy Nexus] Nemed:
[MENTION=4608636]bsmitty83[/MENTION] i'm testing SR5, so far so good. I don't want to speak too soon, but it seems stable even with min core smartreflex set to 830mV. :fingers-crossed: Also, since SR3, i can set the min freq to 180MHz without any kind of issue! So, thanks anyway for the hard work dude!

I'll let you know if freezes and fcs come back
[Samsung Galaxy Nexus] Charmacas:
Min freq set to 180 while the screen is off works fine here. Also I set min SR all down to 800.

I noticed that interactive is missing in SR5. Is that intended or did you forget it [MENTION=4608636]bsmitty83[/MENTION] ? Interactive is still getting the most patches and it evolves, isn't it?

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] wisefreakz:
That's why... Stay away from CM for a while as they all use same commits.

Take a look at my EDIT from the above post.
[Samsung Galaxy Nexus] hawkstorm:
Managed to turn on the Dev options. Now it's in bootloop (Google). Got into bootloader and trying to flash the new KERNEL with a new ROM.
[Samsung Galaxy Nexus] wisefreakz:
Good... Let me know how it goes!!

Don't forget to factory reset, flash gapps then kernel

Edit: 4am here dude... Gotta run.
[Samsung Galaxy Nexus] hawkstorm:
[MENTION=3218463]wisefreakz[/MENTION] OK... flashed the Kernel and Slimkat files but it's still booting CM. :(
[Samsung Galaxy Nexus] wisefreakz:
No way... Can you flash Google image?

Never see this happening!

Or... Try a factory reset from ROM directly... Don't forget to backup data!!
[Samsung Galaxy Nexus] Hetalk:
Do a cwm factory reset, then go to mounts and storage and select "format system".

Then flash slimrom+gapps.

Do all the regular cleaning (cache+dalvik).

This should work.
[Samsung Galaxy Nexus] piterdemon:
On 3.3.14 I have clock freezes anyone have too ?

Wytapatano z Galaxy Nexus LiquidSmooth 4.4
[Samsung Galaxy Nexus] DR3W5K1:
Yes. Lots of people have reported that.
[Samsung Galaxy Nexus] 3n3rg1c:
I feel emmc is fired/dead. This problem occurs when emmc is damaged. It's been reported in other threads..
[Samsung Galaxy Nexus] DR3W5K1:
[MENTION=4608636]bsmitty83[/MENTION] [MENTION=4544860]osm0sis[/MENTION] [MENTION=4328678]metalspring[/MENTION] [MENTION=2838735]aosp[/MENTION] [MENTION=3685904]ak[/MENTION] [MENTION=4244313]MBQ_[/MENTION]

Just wanted to say thanks guys. I'm getting near 3 hours ost with pretty much every build that hasn't been borked. Thanks allot! Best battery life I've ever had on this device.
[Samsung Galaxy Nexus] DR3W5K1:
I'm pretty I see you contributing all the time. Correct me if I'm wrong.
[Samsung Galaxy Nexus] klanistok:
yep
[Samsung Galaxy Nexus] GilGameshn1:
Check [MENTION=4544860]osm0sis[/MENTION] fix few page back ...

Sent From My GNex
[Samsung Galaxy Nexus] aosp:
VanirAOSP users → http://xdaforums.com/showthread.php?p=50831390

[MENTION=4608636]bsmitty83[/MENTION] Thanks for listening ;)
[Samsung Galaxy Nexus] hawkstorm:
is there anyway to fix it?
[Samsung Galaxy Nexus] DR3W5K1:
Also many thanks to anyone I might have left out. Sorry im new around here finally left the green dying site.

Last but not least thanks to the users without us to test and give feedback this awesome kernel wouldn't be possible
[Samsung Galaxy Nexus] Ashtrix:
Just flashed the osmosis Ambien fixed ed of RSR, it was smooth but when i tested Antutu at the 3d bench the app got an ANR, my settings were stock voltages, Wheatley RAB-1024. and stock clocks & latest weekly (v3.4) of SlimKAT !

Hope that helps, thanks !
[Samsung Galaxy Nexus] Charmacas:
The osmosis fixed DirtyV-R feels slower in multitasking than the versions before. The builds from the 3rd and 2nd ran very fast.

Anyone else +1?

If so we should look at the commits and find out what may causing it. I did not change any setting.

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] GilGameshn1:
Actually I feel it faster ... When I flash it I have some lags ... Very fast battery drain ... I wipe the kernel and flash the new [MENTION=4544860]osm0sis[/MENTION] ... Wipe cache and dalvik ... Have a good experience ... But because of dead battery I can't test it till fully recharge ... And I did not test antutu till now ... Will report more .

And I am sorry that I didn't thanks [MENTION=4608636]bsmitty83[/MENTION] for great work ... Also thanks all the testers and contributors . new kernel is evolving thing truly .

Sent From My GNex
[Samsung Galaxy Nexus] klanistok:
maybe im wrong but i feel same too.
[Samsung Galaxy Nexus] TheMan0790:
DirtyV RSR latest build working great for me. No more clock problems. Now, if those CM11 nightlies were to work properly again....
[Samsung Galaxy Nexus] agreenbhm:
Are the cm nightlies just not working in general or is it only with this kernel? I flashed last night's cm build with this kernel and I kept getting FC's on com.android.phone. The cm build from a few days ago I was running yesterday plus the same build of this kernel did not have issues.
[Samsung Galaxy Nexus] djtutis:
Latest Dirty V is amazing! No more lags or click issues with Nephilim's settings... Smitty could you add Double tap 2 wake feature in your kernel (because TC haven't update the module)?
[Samsung Galaxy Nexus] Shambola:
Can I suggest something?

It's more arrangement than developement....

I recommend often, on other forums (mostly Italian), this kernel and I understand that if someone is not "living here" every day like we do, it's difficult to understand something in OP.

Maybe on a certain day last release is buggy, doesn't sleep or doesn't fit into a rom, and another release have/doesn't have ramdisk, or features like touck2wake, fastcharge etc etc.... And pick the right one in previous versions looks like russian roulette.

[MENTION=4608636]bsmitty83[/MENTION] Would it be better if you'd manage the OP with a kind of "stable version" and many "experimental"? So, the newcomers should come here and pick a full working release and then (when surely they will be passionate about the cause) delve into the thread!

Now, when i recommend this kernel, I must say: go to the thread but don't take the XX version, pick the XY, no, wait, you use ZZ Rom and you want touch2wake so pick the XYZ-recompiled-with-some-voodoo-by-JKYW, but not the last one, two releases before...And they have a nosebleed.

Maybe a big "LATEST STABLE ---> Link" could help!

:)
[Samsung Galaxy Nexus] TheMan0790:
Not to veer this thread off-topic, but in answer to your question...I do believe it is a CM-based problem with any custom kernel at the moment. I'm staying on the build from March 3 for now (last working build for me).

Break me off a piece of that KitKat ROM!
[Samsung Galaxy Nexus] Nephilim:
So I bumped max screen-off to 525mhz on 3/4 and it seems to help wake lag slot after letting my device settle for awhile. Per recommendations from a few of you I will keep max screen-off at 525mhz for my settings to help with battery and music stutter as well. :)

Smitty, sadly the bad news I have is the hit reboots on overnight charge are back. Don't know why, I use my exact same settings. Not sure when the device rebooted but it was sometime between 2am and now while I was asleep and it was on the charger. :(

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] bsmitty83:
If you can grab me the last kmsg . I'll investigate further :D
[Samsung Galaxy Nexus] vfmmeo:
+1 Here. My dying power button will be happy with this.
[Samsung Galaxy Nexus] Nephilim:
Is that even possible when there is no telling when the device actually rebooted over a 5 or 6 hour period of time?

If so, I'll get one if/when it happens again, I already am flashing a test build of LiquidSmooth right now. ;)
[Samsung Galaxy Nexus] bsmitty83:
Yes . as long as you don't pull the battery , the last kmsg will be there .
[Samsung Galaxy Nexus] büscher:
I'm also trying the new smittyV 3/4

I have several issues:

1. after flashing this kernel my phone forgot the wifi pass again, but after that it didn't happen again until now (~6h on this build now)

2. Wifi not reconnecting after getting out of range and it's telling me the signal strength is poor (although I stand right by the router) - Turning off and on the wifi does not solve the problem

I have alooot of these in my dmesg:

<6>[ 1962.241699] CFG80211-ERROR) wl_run_escan : Escan set error (-16)
<6>[ 1962.241912] CFG80211-ERROR) wl_run_escan : error (-16)
<6>[ 1962.242034] CFG80211-ERROR) __wl_cfg80211_scan : Scan err = (-16), busy?-16
<6>[ 1962.242248] CFG80211-ERROR) wl_cfg80211_scan : scan error (-16)

<6>[ 1924.870544] CFG80211-ERROR) __wl_cfg80211_scan : Scan err = (-16), busy?-16
<6>[ 1924.870697] CFG80211-ERROR) __wl_cfg80211_scan : Unusual continuous EBUSY error, 1 0 0 0 0 0 0 0 0
<6>[ 1924.871337] CFG80211-ERROR) __wl_cfg80211_scan : GET BSSID failed with -17

2.1 after a reboot my wifi is "Disabled", I can press "Connect" but nothing happens....

2.2 If i try to forget the network it tells me "failed to forget network"

2.3 disabling and enabling the network again and the passphrase is gone but the wifi works again...

also still have this in my log (altough i changed from CA to Europe):

<4>[ 30.083709] dhd_preinit_ioctls buf_key_b4_m4 set failed -23
<4>[ 30.088531] Firmware version = wl0: Jan 23 2013 17:46:35 version 5.90.195.114 FWID 01-cafa6b3e
<4>[ 30.089050] dhd_wlfc_init(): successfully enabled bdcv2 tlv signaling, 79
<6>[ 30.090362] CFG80211-ERROR) wl_cfg80211_attach_post : p2p0: p2p_dev_addr=XXXXXXXXXXX
<3>[ 30.444702] WLDEV-ERROR) wldev_set_country : wldev_set_country: set country for GB as EU rev 5

3. Rebooted and got google-logo bootloop (batterypull needed)

4. I also have the slight wakup lag @ 700MHz max screen off (but this is a very small issue)

5. I'm not able to take last_kmesg (but that is probably due to my battery pull)

and just curious: why do I find this:

<6>[ 3.920959] OMAP4470 LPDDR interface configuration update for 466 MHz

I thought galaxy nexus are OMAP4460? ->

<6>[ 0.217315] Tuna HW revision: 09 (Maguro 8th Sample), cpu OMAP4460 ES1.1

I'm sorry to throw all these bugs at you smitty ;)

I have to revert to 2/28 for now becuase also battery drain is huuge -> RILJ Wakelocks again...
[Samsung Galaxy Nexus] Nephilim:
If I get another hot reboot I'll take care of it then. I'm hoping it may have been something random conflicting with the last LiquidSmooth build and now that I am testing 3/5 Liquidsmooth it won't happen again. Fingers Crossed :D
[Samsung Galaxy Nexus] aosp:
You upgraded after rebooting ?
[Samsung Galaxy Nexus] paarthdesai:
my power button needs some shoulders too... would be great if double tap to wake is added
[Samsung Galaxy Nexus] bsmitty83:
Not sure with the WiFi , no troubles on my end , last kmsg will be there until you completely discharge the power in the phone ie battery pull

And yes we have omap4460 , but I borrowed an extra ram freq step from 4470 , never changed the printk in the file so that is says 4460 :p
[Samsung Galaxy Nexus] cujo6801:
If so, I'll get one if/when it happens again, I already am flashing a test build of LiquidSmooth right now. ;)[/QUOTE]

Wait.... ^^^^^^^ ^^^^^^^ ^^^^^^^

Did I read that right .....

Num num....

Sent from the "DOG" pound