yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Yianaki:
Can't believe Stable KitKat appeared so quickly on good ole Gnex

Thanks so much for this ROM it is nuts, came from MuzzyRom 4.2.2. Totally deserving of daily driver status have been running since Sat with no problems at all. Did a titanium backup and then restored all my user apps, no problem at all for once. Everything works correctly am streaming my tunes from bluetooth via Google Music, SoundCloud, and TuneIn. Just under Sounds make sure you turn off the Lock Sound or it distorts the audio everytime you lock your phone I find.

Battery life is great no complaints at all, very little battery usage when screen off as should be. Nothing weird going on with phone at all. Am pleasantly surprised.

Is a bit laggy or is that just me, like the GPU isn't 100 yet? Data seems to be slower to pull down data, again probably just me. But all around super nice, hope CM adds your great work to their upstream code.

Put the newest public version of TWRP did a wipe then just flashed cm-11-20131125-FML-toro with the pa_gapps-full-4.4-20131126-signed nice. Ran lagfix manually to do a nand cleanup phone seemed much more responsive after that, currently it is half full.
[Samsung Galaxy Nexus] rice923:
I just noticed the "clear all" button for recent apps. I love you
[Samsung Galaxy Nexus] scope666:
Oh snap, didn't even notice ... LOVE that feature!!!!
[Samsung Galaxy Nexus] taz1458:
I tried replying to the Pens Predictor. # was 32620, when it tries to send it force closes.

EDIT: Tried in hangouts and handcent. Says process com.android.phone has blah blah blah. It won't send at all. Any ideas?
[Samsung Galaxy Nexus] Sheetzie03:
I know that stinks, they need to bring back the swipe ASAP

?Beamed out via KK'd Toro?
[Samsung Galaxy Nexus] drmbdrummer:
Are you guys on a different version? You can also just swipe from the left hand side of the screen to pull out the drawer (ala the play store).
[Samsung Galaxy Nexus] Sheetzie03:
I'm talking about swiping between the pages info, tool, specific, general, screen.

The devs took that feature away within the last few updates, have no idea why. Terrible decision.

?Beamed out via KK'd Toro?
[Samsung Galaxy Nexus] kb8no:
Is this functionality now the norm in all KitKat ROMs ?

---------- Post added at 07:16 AM ---------- Previous post was at 07:11 AM ----------

More important and functional would be a fast charge Quick Setting Tile toggle that actually was there and actually worked.
[Samsung Galaxy Nexus] sickopsycho:
Why would you want a quick settings tile to turn it on/off? If the fast charge setting didnt affect usb connectivity to a pc then what advantage would there be to turning it off? Do people like to charge their phones vvvveeeeerrrryyyyyy ssslllooowwwwlllyyyy? =p
[Samsung Galaxy Nexus] afguy0127:
I hate quoting myself, but I didn't see anyone else post about this since.

Also, is anyone else having problems with Wi-Fi connectivity? Since I switched to this ROM I haven't been able to access anything requiring a network connection via Wi-Fi (Facebook, web browser, Tapatalk, etc). I've tried re-flashing radios, have updated the ROM, and still having issues. Think tonight I'll try a complete wipe and try again, just wanted to see if anyone else had issues.
[Samsung Galaxy Nexus] Jodsfk421:
Quick Question-

I use MyPhoneExplorer pretty frequently at work. The two most used options are SMS (thru the PC) and a feature called "Control Phone" (Basically you use your mouse and keyboard to control the phone. Anyways, in the 11/25 version the control phone feature worked great but since the 12/2 update it doesn't work. This stopped working with android 4.2 and I am (completely) guessing that it has something to do with security but not sure... any ideas?

Galaxy Nexus Toro / OP Rom (no changes/mods) / latest Android App / PC program

Edit: I just noticed to possibility of usb fast charge being on by default, i'm going to see if turning that off changes anything.

Edit2: Nope.
[Samsung Galaxy Nexus] David 617:
Quick charge has been known to fry the USB port on the phone. Some people may be more cautious than you and prefer it as an option.
[Samsung Galaxy Nexus] deadpixell:
Just tried to install and downloaded everything from here and when I go to install it says this package is for "toro" devices this is a maguro device. Is the download link messed up or something>?'

edit: I guess I need CWM 6.0.4.3..but I've already updated to the latest. Can I just "downgrade" and where do I found the flashable zip for the older version? thanks..
[Samsung Galaxy Nexus] vitokes:
Hey neph I was curious if this foxes video playback from recorded videos? Or just photosphere and gallery. If I missed it I'm sorry but I'm just curious.

Never mind. Flashed and confirmed that video playback is now working! Thanks

Sent from my Immortal Nexus!
[Samsung Galaxy Nexus] tharris297:
I'm using BaNKS standard and it's working just fine.
[Samsung Galaxy Nexus] taz1458:
Anybody else having this issue?
[Samsung Galaxy Nexus] sickopsycho:
Is this a confirmed issue or more of a "I heard someone say that this happens maybe" type thing? I see no reason why it would fry the connect since it simply uses a voltage/amperage that the wall charger uses if the cable will support it instead of the low amp current that a USB normally outputs. Or are you referring to frying the USB on, for example, the PC? I could possibly see that maybe but not likely. Seems like it wouldn't put out more than it could handle...

Sent via Galaxy Nexus Life completely Forked.
[Samsung Galaxy Nexus] MWisBest:
I haven't noticed this at all, can you by chance get a logcat of this? Thanks.

It isn't default functionality, it's an improvement to Fast Charge that was done by [MENTION=2597267]joshua_[/MENTION]

As for a Fast Charge tile, I'll look into it, but for starters I'm going to have it enabled by default in a new build which should be out sometime today.

I haven't had any of these issues, see if a wipe improves it, and if it doesn't, get me a logcat of it. Thanks.

Can you provide any evidence of this? I don't see how it can effect the USB port itself, the charging circuit maybe but that's separate from the USB port.

You have to make sure you don't flash the version of CWM made for maguro, the GSM version of the Galaxy Nexus.

My thoughts exactly.
[Samsung Galaxy Nexus] taz1458:
Can you give me a link for how to do a log cat?
[Samsung Galaxy Nexus] Fluey18:
http://xdaforums.com/showthread.php?t=2251873

I used logcat extreme. Pretty much just get an app from the play store then open and run it, do whatever action gives you the error, then stop the app and it saves a text file of the log for you to share.
[Samsung Galaxy Nexus] skylordusa1:
What is this lagfix you speak of?
[Samsung Galaxy Nexus] lynxznet:
This is.. without a doubt, the best 4.4 ROM currently out. I am VERY impressed with how snappy my phone now is, not to mention fully functioning on 4.4 (finally). This actually feels even better than the old 4.3 ROM that I was running. I did have a few minor issues, but once I reinstalled a few apps it was running like a champ. Thanks so much!
[Samsung Galaxy Nexus] Nephilim:
Lagfix is a placebo that was confirmed to be a placebo on anything beyond 4.2.x roms and has had no verifiable benefit since.

Sent from my Android 4.4 Galaxy Nexus
[Samsung Galaxy Nexus] MWisBest:
Threw up a new build, battery customization (like circle w/ percentage, etc.) is back in CM finally. Tested it with ART as well, no issues there.
[Samsung Galaxy Nexus] sivarticus85:
Are you running the stock kernel? Does the notification pull down lag for you anywhere?
[Samsung Galaxy Nexus] metalspring:
And where was this confirmed to be a placebo???

Fstrim (which lagfix uses) should help any flash memory...

http://fcns.eu/2013/09/12/improve-ssd-performance-with-fstrim/
[Samsung Galaxy Nexus] MWisBest:
TRIM has been enabled by default for quite some time now, lagfix is indeed irrelevant now.

BTW, TWRP has a 2.3.6.2 build out, haven't tested it myself yet but for those who are interested: http://techerrata.com/file/twrp2/toro/openrecovery-twrp-2.6.3.2-toro.img
[Samsung Galaxy Nexus] jrk190:
I get pull down lag quite a bit. On another note, is it safe to dirty flash the new build, or should I wipe system and reinstall?
[Samsung Galaxy Nexus] Nephilim:
Fstrim is part of all 4.3 and on kernels, therefore lagfix does nothing.

Sent from my Android 4.4 Galaxy Nexus
[Samsung Galaxy Nexus] MWisBest:
It should be OK to dirty flash the new build, but if you do have issues just try to reflash with a system wipe that time. As for pulldown lag, are you using ART? If not, I'd suggest to give it a try, it really feels like a completely different phone with it.
[Samsung Galaxy Nexus] sivarticus85:
I'm not using ART. I usually get bad FCs with it, even when trying other gapps packages. Does FCing still occur?
[Samsung Galaxy Nexus] rice923:
I also get some FCs with art. Most notable with whatsapp. Anyone else have whatsapp FC with art?

This is with 1202 build
[Samsung Galaxy Nexus] ba_hamilton:
NIce update. I like the new battery mod options. When you go into About phone it still has the date of 11-20131201.

When the center clock with the am/pm mod gets implemented my phone will do a happy dance.

I am using ART and have not experienced any force closes or any other screen issues. I am using the 11-26_GApps_Standard-4.4 file.
[Samsung Galaxy Nexus] MWisBest:
I don't have any FCs from the recommended GApps, there are some other apps that don't work with it just yet though. Only way to find out is to try it!
[Samsung Galaxy Nexus] MWisBest:
Yeah, the Build Date doesn't change unless it's a completely fresh build, it's been that way since Android's incarnation as far as I can tell.

Fresh Build: all the code is completely recompiled (turned into the 1s and 0s).

Incremental Build: only the code that has changed is recompiled.

Fresh builds can take at least 2 to 3 hours, while incremental builds can be as short as 5 to 10 minutes up to maybe 45 minutes. Incremental builds aren't perfect however, sometimes things change in a way it doesn't quite understand and a fresh build has to be done instead. Usually I try to do a fresh build at least once every 7 days because of this.
[Samsung Galaxy Nexus] kb8no:
Does BaNKS install camera & gallery?
[Samsung Galaxy Nexus] taz1458:
---- Dec 4, 2013 10:31:19 PM ----

12-04 22:30:49.866 676 13533 I ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=scd.lcex/.LogcatExtreme bnds=[360,578][360,578]} from pid 2673

12-04 22:30:50.195 676 693 I ActivityManager: Displayed scd.lcex/.LogcatExtreme: +295ms

12-04 22:30:50.210 7166 7166 I dex2oat : dex2oat: /data/data/com.google.android.youtube/cache/ads-1588587044.dex

12-04 22:30:50.241 2673 2673 W IInputConnectionWrapper: showStatusIcon on inactive InputConnection

12-04 22:30:50.265 3134 3146 I art : Heap trim of managed (duration=427.246us, advised=24KB) and native (duration=793.457us, advised=56KB) heaps. Managed heap utilization of 61%.

12-04 22:30:50.273 6836 6836 E SpannableStringBuilder: SPAN_EXCLUSIVE_EXCLUSIVE spans cannot have a zero length

12-04 22:30:50.273 6836 6836 E SpannableStringBuilder: SPAN_EXCLUSIVE_EXCLUSIVE spans cannot have a zero length

12-04 22:30:50.812 7138 7181 I GoogleConversionPing: Pinging: http://www.googleadservices.com/pag...214250&data=screen_name=<Android_YT_Open_App>

12-04 22:30:50.898 7138 7181 E GoogleConversionPing: Error sending ping

12-04 22:30:50.991 7138 7150 I art : Heap trim of managed (duration=2.868652ms, advised=20KB) and native (duration=1.190186ms, advised=0B) heaps. Managed heap utilization of 63%.

12-04 22:30:51.015 7138 7138 D YouTube : apps.youtube.app.prefetch.PrefetchService$DeviceStateReceiver.onReceive:565 Got device state change intent: android.net.conn.CONNECTIVITY_CHANGE

12-04 22:30:51.023 7138 7138 D YouTube : apps.youtube.core.transfer.TransferService.onCreate:108 creating transfer service

12-04 22:30:51.070 126 126 W art : Could not get current activity

12-04 22:30:51.077 676 13533 I ActivityManager: Start proc com.handcent.nextsms for broadcast com.handcent.nextsms/com.handcent.im.transaction.NetworkStateReceiver: pid=7193 uid=10145 gids={50145, 1028, 1015, 3003}

12-04 22:30:51.093 7193 7193 I art : Turning on JNI app bug workarounds for target SDK version 8...

12-04 22:30:51.109 7138 7138 D YouTube : apps.youtube.app.prefetch.PrefetchService.onStartCommand:167 PrefetchService started at 5 Dec 2013 03:30:51 GMT

12-04 22:30:51.140 7138 7138 D YouTube : apps.youtube.app.prefetch.PrefetchService.p_:245 Download snapshot restored

12-04 22:30:51.140 7138 7138 D YouTube : apps.youtube.app.prefetch.PrefetchService.onDestroy:215 PrefetchService destroyed at 5 Dec 2013 03:30:51 GMT

12-04 22:30:51.890 7218 7218 I auditd : Starting up

12-04 22:30:51.890 7218 7218 E auditd : Failed on audit_set_pid with error: Protocol not supported

12-04 22:30:51.890 7218 7218 I auditd : Exiting

12-04 22:30:52.007 27845 27845 I MusicLeanback: ActionReceiver action:android.net.conn.CONNECTIVITY_CHANGE

12-04 22:30:52.007 27845 27845 D MusicLeanback: Acquired WakeLock

12-04 22:30:52.031 27845 27845 D MusicLeanback: onCreate

---- Dec 4, 2013 10:31:19 PM ----

There ya go. Think I did it right. That was after a complete system wipe and everything.
[Samsung Galaxy Nexus] ba_hamilton:
Thanks for that explanation. You guys that have the passion, knowledge, and desire to do this stuff are amazing.
[Samsung Galaxy Nexus] tharris297:
The standard package does
[Samsung Galaxy Nexus] MWisBest:
I see that you are using ART, can you try using Dalvik instead and see if you're still having the issue? Also, let me know your phone's radio version (the entire contents of Settings --> About Phone --> Baseband Version), and for future reference, most developers (including myself) would prefer you put your logcat on http://pastebin.com/ or something similar to it. Thanks!
[Samsung Galaxy Nexus] taz1458:
I actually started on dalvik and it did the same thing. I switched the art a few hours ago to try and it still did it. I'm on the FK01/FK02 baseband. If you need the other info let me know. Also, i apologize for not doing that. First time I've ever actually used it honestly.
[Samsung Galaxy Nexus] metalspring:
Why not just delete the compiled build.prop to make it add the new build date every build, whether its just a full build or an incremental one?

Just curious

I know I just use a build script modified from PAC rom that automatically deletes the build.prop and kernel_obj/.version so the build dates are up to date

(also automates . /build/envsetup.sh lunch and make with options to add the -j argument, building using pipe (to speed things up) calculates the time it took to build and a few other useful options just to make things simple)

If you want I could message you it?

If not I understand lol
[Samsung Galaxy Nexus] lynxznet:
I dirty flash it myself and had some minor issues with SU and Titanium going ape ****.. but once I reinstalled them the issue went away. I currently have no issues and the phone is incredibly snappy.

Also, I'm using ART.
[Samsung Galaxy Nexus] taz1458:
EDIT: problem solved.
[Samsung Galaxy Nexus] sickopsycho:
Whatsapp apparently is a known issue with ART. Its nothing to do with the runtime, the app needs to be updated. If you can't live without whatsapp for the time being I suggest staying on dalvik runtime for now until its updated. There is a great thread about ART under gnex general development I think, or gnex general. Basically if you enable ART and get a ton of FCs then you most likely aren't using the deodexed gapps. Make sure the gapps you install are DEODEXED or say ART compatible... For example the PA 0day Gapps... They work great. The flashable zip nephilliam posted also flashes fine over the gapps (with ART) to give you full photosphere functionality. Correct me if I'm wrong but I think it also fixes gallery view camcorder video issues as well.

Sent via Galaxy Nexus Life completely Forked.
[Samsung Galaxy Nexus] ebb:
Have not had any issues previous to the 12/5 running with PA full and Mpokang, with ART. Dirty flashed (wiped cache and dalvik) the 12/5 and ended up with multiple FC's. Had to go into recovery (CMW) and eventually restore a dalvik backup before I could get things running without bootloop.. Is it necessary when dirty flashing to revert to dalvik first before installing a new build?

I have seen the posts from about week ago when there was some back and forth about this, but I have previously flashed over ART without a problem. Did something change in the 12/5 build to cause this issue?
[Samsung Galaxy Nexus] MWisBest:
No problem about the pastebin thing, I knew it was your first time with logcat, I'm just glad you were able to get the logcat up. One last thing I'd like you to try, even if you have already: Use Hangouts. Make sure it's set as the default SMS app, you can find it under Settings --> More... --> Default SMS App. If it still has problems, get a logcat of it. Thank you!

Just knowing it's as simple as deleting the build.prop and kernel_obj/.version is enough, thank you. :)

Glad to hear things are working alright!

Is this referring to the SMS problem?

I've flashed over ART as well without any issues, however I do wipe /system every time I flash so I'm not sure if that makes a difference with it or not. Not sure what happened with you there.
[Samsung Galaxy Nexus] theskyliesx:
I think this may be a CM issue but the bluetooth still doesn't transfer song title and artist name over to my bluetooth stereo and into my car via bluetooth. I tried a different ROM based off CM11 and had the same issue. just giving a heads up otherwise the rom is great!
[Samsung Galaxy Nexus] ricola1989:
Been running the new build since this morning with ART and haven't had a single fc with com.process.googleapps or whatever it is haha. Running mpoKang Super RAM kernel and banks gapps.
[Samsung Galaxy Nexus] taz1458:
Negative. I'll do the hangouts thing in a second.

EDIT: Tried hangouts. Same dice. Here's a pastebin. http://pastebin.com/1h5QKWGB
[Samsung Galaxy Nexus] sickopsycho:
No issues with bluetooth audio data here. I synced to GMCs intellisync whatever and it was easy peasy. Only issue was a glitchy lock and unlock- when the phone is locked (not screen on, but literally swipe to unlock) the audio gets funky for half a sec but then picks right back up. Audio data for artist name, track title, all works fine. I even have control on the stereo for track change, repeat, etc.

Not really related but call records, text, etc also are transfered fine- when i get a phone call incoming call data displays on stereo as well. Can't use voice functionality (stereo say incompatible-) but i'm certainly not *****ing. Can answer calls with stereo and make calls as well- shows recent calls, etc. I'm happy as hell it works as seamlessly as it does! =)
[Samsung Galaxy Nexus] taz1458:
Tried to completely wipe and still have the issue. Installed the 1205 version and tried and same thing. Very weird.
[Samsung Galaxy Nexus] afguy0127:
Ok, here's a logcat of my bluetooth issues. Once this happens, the car will not recognize the phone for any text messaging functionality. In other news, I got my wifi issue cleared up. I ended up doing a full wipe, cleared everything including storage, and loaded the ROM via ADB sideload.

http://pastebin.com/ifuHXDFf
[Samsung Galaxy Nexus] taz1458:
Just a quick thing mw, I went back to the 1125 version. It sends fine. I wonder if it has anything to do with the pop-up thing that says, handcent(or whatever sms app) is trying to send a text to 36323, which may cost blah blah blah. It doesn't pop-up with the force close. It does on the 1125 and runs fine. I'll stick with this for now.
[Samsung Galaxy Nexus] ebb:
If it helps anyone, after much searching, trial and error, I think it most likely has to do with the default checks in PA gapps full for syncing through the Google account with the AOSP browser and/or Google calendar. Disabling automatic sync for those two seems to stop the FCs. The problem is to get the FCs to stop long enough to get to settings and uncheck those sync boxes. Rebooting in safe mode was the answer.
[Samsung Galaxy Nexus] sickopsycho:
How DO you boot into safe mode? That just doesnt start any apps downloaded from the market, yeah?
[Samsung Galaxy Nexus] ebb:
Hold the power button to get that menu, then press and hold on reboot until the safe mode popup appears. Trick when FC'ing is to cancel the FC message and touch on the power menu fast before another FC appears. :laugh:

Safe mode is just like on a PC as far I can tell. Keeps all unnecessary programs and processes from loading.
[Samsung Galaxy Nexus] dverson:
Noticed an odd issue today. The 'always listening' feature of the GEL seems to be gone. So my searchbar basically looks like the pre-4.4 search bar. I flashed 12/5's build, but no change. The hot keyword setting in google's voice settings is checked. Any ideas?
[Samsung Galaxy Nexus] rice923:
Are you referring to the function of having Google now activate when you say "OK Google" while on any home screen?

If so, mine works perfectly
[Samsung Galaxy Nexus] Nephilim:
It still works, the Say "Okay Google" is meant to go away after using hotword prediction a few times. Google just put it there to help people new to 4.4, its not meant to stay. As long as the mic icon in the searchbar is solid hotword still works. ;)

Sent from my Android 4.4 Galaxy Nexus
[Samsung Galaxy Nexus] ricola1989:
I didn't realize that; that's pretty nifty
[Samsung Galaxy Nexus] rice923:
Try saying "OK Jarvis" to your phone... See what happens ;)
[Samsung Galaxy Nexus] metalspring:
I'm guessing it doesnt do anything but that would be awesome if it could be modified to replace "ok google" with "Jarvis" lol
[Samsung Galaxy Nexus] MBQ_:
no, it responds to that.

You can even say 'ok dildo' and itll respond. lulz
[Samsung Galaxy Nexus] jbag:
not sure where to report bugs but figured this is a good place.

I noticed that when i am streaming music from pandora or the stock music player via bluetooth there is an interrupt in the music when i unlock the device or lock it up. I am setup with a pattern unlock screen.
[Samsung Galaxy Nexus] Rushead:
That happens with standard unlock, too. I get small hiccups with bt every so often. NBD for me.

Sent from a flashead cracker.
[Samsung Galaxy Nexus] jbag:
it sounds like a scratch in the record. i guess it makes me not want to use my phone in the only place i BT connect, my car.
[Samsung Galaxy Nexus] dverson:
Do you have lock/unlock sounds enabled? Turning those off might help.
[Samsung Galaxy Nexus] rice923:
Like MBQ said, it responds. But I just tried "OK dildo"and it really responds to that too haha.

I noticed one small bug that have really been mentioned here. When taking a screen shot, the preview pic is distorted, but the final pic is fine.
[Samsung Galaxy Nexus] MBQ_:
Yep. Super common and now expected problem for us users (well, and developers :p)

But the picture comes out fine so its no big deal, really. ?
[Samsung Galaxy Nexus] bunklung:
I get pull down lag too. I am on stock kernel. I install full PA gapps 11-26. I have some sort of wake lock going on. I haven't install anything.

Any tips to find the root of this problem?
[Samsung Galaxy Nexus] pattyboi:):
clean flash again,then just dont install anything at all and use for atleast 30 mins,then try installing/modding/etc and you could easily narrow it down:)
[Samsung Galaxy Nexus] bunklung:
This is my second clean flash. I have only used gapps stuff and that was limited to Google + mainly.

I installed BetterBatteryStats. We shall see :)

*update. RILJ seems to be the wakelock. I did a search and seems like CM thing. Toggle airplane mode seems to kill/control the problem. I'll report back.
[Samsung Galaxy Nexus] grandzu:
Is this going to get 4.4.1?
[Samsung Galaxy Nexus] hotrodwinston:
Is automatic restore from google play working? Including Wi-Fi passwords? I want to install this on my wife's gnex but want to do a full clean install because I don't want her to call me while i'm at work having issues with her phone.
[Samsung Galaxy Nexus] bunklung:
It did NOT restore for me.