yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] MWisBest:
I don't see the navigation bar at all with expanded desktop, but if there really is a string of black pixels on the bottom of the screen still it won't burn in anything as if it's a true black (which I'm positive the navigation bar is) the pixels are actually turned "off". That's how the Moto X is able to allow you to look at notifications with the phone's screen off still, as only the pixels receiving any color require power.

I got my Galaxy Nexus in January of this year actually, new-in-box at WalMart. ($0.97! Gave up unlimited data because even if I paid full price I was upgrading to a 4G LTE phone from a 3G phone which results in a loss of unlimited data anyway, and I never went over 1GB/month in the 2 years I had my previous phone lol.) Verizon themselves stopped selling them at around that same time too... so yeah, I haven't seen any burn-in myself yet. Unfortunately it's only the 16GB version, but I've been able to store what I need at least haha.

If you really want to avoid burn-in, get an MHL cable and hook up to an HDTV whenever you can. ;)
[Samsung Galaxy Nexus] Rushead:
I bought my gnex from swappa in near mint condition for less than $150. Switched from 3g and still have unlimited data. Not sure where you got your info.

Sent from a frequent flasher.
[Samsung Galaxy Nexus] MWisBest:
I talked with a few Verizon people and was told that, I'm actually friends with the guy that owns the Verizon store where I live. I'm sure there were ways around it, and I don't think the 3G --> 4G LTE = No Unlimited started right away in June 2012 when they started ripping away unlimited data plans either. But yeah, he had told me that with getting a 4G LTE SIM card without having one previously unlimited data is lost regardless of what you do, the system wouldn't even let him try, however I believe the higher-ups in Verizon (mostly online people) have different abilities regarding what they can and can't do (more freedom than the small-fish store owners).
[Samsung Galaxy Nexus] Rushead:
Sorry for the hijack, MW.

I walked right into a Verizon store in the mall, handed them my gnex, and said I need a sim card. The guy took my phone, popped in the sim card, did some programming, and gave it back. Done deal, no change to my unlimited plan. I don't know anyone at vzw. This was in July.

Sent from a frequent flasher.
[Samsung Galaxy Nexus] MWisBest:
Damn! Maybe I was misinformed or something. :(

And no worries about a "hijack", as long as it's not to link somebody to another ROM and it's at least somewhat related to Android I really don't care! :D

Update on ROM development... still trying to work out kinks with mobile data. I'm going to take hard look at CM's changes that are related to it, as I'm positive that AOSP doesn't have the issue of data completely failing to work. I think CM has improved some parts of it though (not recently... just over CM's history in general), so I need to find the "bad egg" so-to-speak. Anything I've tested tonight hasn't made much if any improvement, and a couple things completely borked it but at least taught me more of the inner-workings of this stuff.

CM has mostly been pretty quiet over the past few days, nothing particularly worthy of a new build, so I'm going to leave the current build up while I continue testing new stuff. If something noteworthy comes into CM or I'm able to really figure out this mobile data stuff I'll throw up a new build, as the current build seems to be doing alright so I don't want to put out something that doesn't work as well as what I have now.

EDIT: It looks like AOKP has been working on updating to Android 4.3 recently. Would anybody be interested in having both an AOKP and CM build? Once AOKP is stabilized on 4.3, of course.
[Samsung Galaxy Nexus] swarlesbarkely:
I would! I personally prefer aokp because its more customizable. I know they have test builds out for a couple phones but I haven't heard how they're doing.

On a side note, didn't cm 10.1 have voltage control built in?
[Samsung Galaxy Nexus] MWisBest:
I'm not sure about CM 10.1 but I know AOKP at one point included a PerformanceControl application by default which allowed adjusting voltages.

Well I had quite a busy weekend at work so I haven't been able to do any updates on the ROM for a bit, apologies about that. I'm going to do a clean build synced with CM's latest changes and upload it later today (09/09/2013) if it tests out OK, going to leave out my work on mobile data for the clean build but I'll see if I can add it in later this week. If that all goes well, I'll see if AOKP is looking alright and maybe get some builds going for that as well!
[Samsung Galaxy Nexus] MWisBest:
New build tested out alright, I did notice that some data issues (notably the complete drop of mobile data, requiring either a restart or airplane mode for a couple minutes to fix) show up (at least more than usual) when LTE is toggled, so it gives me more of an angle to work at with fixing this.

Also, I think I'm going to start uploading to Google Drive along with Dev-Host, as Dev-Host was giving me some fits this morning.

I will update the topic with the new build!
[Samsung Galaxy Nexus] hawkinsandponcho:
I flashed this morning coming from stock rooted Verizon 4.2.2 as I've had wakelock problems for about a month and decided to give 4.3 a try and this looked like a painless flash. I actually didn't read your comments about this being early beta until just now but everything is running smoothly and no mobile data issues. No wakelocks either. Thanks for your work!

EDIT: I'm using the 20130902 v2 build
[Samsung Galaxy Nexus] MWisBest:
Thanks! I appreciate the feedback. Wakelocks were actually problem when I was first started working on this but I was able to get that squared away before I put up the first build thankfully, part of what helped that was using Fancy Kernel so maybe drop by boype's thread for it (it's linked to in the first post here somewhere) and leave him a thank you as well, he's certainly done a fantastic job with it.

Update on ROM development... looks like CyanogenMod may have put CMAccount in builds by default now so I'll probably get a build out tonight with that, I'm also trying out getting AOKP for 4.3 up and running. I don't think I'll put out an optimized build for AOKP at first if/when I get it going, I'd prefer to work out the kinks in it before optimizing it so that I know any screw-ups aren't from the optimizing, otherwise I'd end up having to do twice the work to figure out what might be wrong! ;)

EDIT: Yikes, ended up falling asleep before I could get a new build up! I'll get going on that now, haha.
[Samsung Galaxy Nexus] MWisBest:
New build is up, includes CMAccount! :)
[Samsung Galaxy Nexus] modernbummer:
Thanks, MW. My gnex seems to take to these builds better than others. :good:
[Samsung Galaxy Nexus] sonic147862:
Anyone else on this ROM having google services take up a about %20-30 of their battery?
[Samsung Galaxy Nexus] buildakicker:
I was just coming to comment here. It is so rad to use 4.4 on the gnex! Thanks a bunch for getting this out to us. Yes, it just drills my battery, not with Google Services though... at least according to Settings - > "Battery". I have the extended battery and, with use, get around 2 hours before 3% charge left. eeeekkkk... Any thoughts on this?

Anyone using a different kernel?

Screen 39%

Browser 32%

Android System 6%

TuneIn 7%...

Just moved from CM10.2.x (4.3) to try this out. I really dig the look and feel of KitKat.

I'll keep this installed for a few days and see how it goes.
[Samsung Galaxy Nexus] Rushead:
He said 'rad'!

What's your actual screen-on time?

One thing you could try is Greenify. I'm getting good battery life (probably a little better than 4.3 -) on my new Sprint 2100 (thanks, MW).

Sent from a frequent flasher.
[Samsung Galaxy Nexus] MWisBest:
I just checked my battery stats: Google Search is taking up 43% of it with a 12 hour plus keep awake time. Not sure why this is, and I'm certainly not happy about it. I'll try and track it down to see if the issue is with the ROM or with Google's apps.

EDIT: Seeing other battery stats posted here, the one thing I see in common: The apps using up all the battery all use the browser render engine crap. Can't be a coincidence.
[Samsung Galaxy Nexus] MONKY_1:
I went into the settings of Google now, and disabled "Hot keyword" aka "OK Google." My battery life is normal. Helpful that helped some.
[Samsung Galaxy Nexus] omniatic:
You could also try turning off Location Reporting in Google settings. Might help on the battery drain and awake time.
[Samsung Galaxy Nexus] Enter The Nexus:
I think the GEL is draining Battery Life, especially as Google search is always on...I'd use Nova or any other launcher from now on to conserve battery, unless you don't mind carrying a charger at all times.
[Samsung Galaxy Nexus] Sonicmax2k2:
I couldn't get screenshots before my battery died, but I haven't had the issues you guys are noticing. I'm running Dalvik (though I used ART for a little) and had the following stats.

Running Time: 18 hours

Screen-On Time: 3 hours

Was on WiFi most of the day, and 4G the rest, downloaded some music and did bluetooth playback. I use Nova instead of GEL.

I do have two bugs to report though:

1) The LTE quick toggle does not work

2) When doing bluetooth audio playback, when the screen turns off/on, the music stutters for several seconds before returning to normal. When not doing bluetooth, the music just drops out for a second before returning, but does not stutter.
[Samsung Galaxy Nexus] vitokes:
since i the new 11/21 update i have had insane battery drain. just now i checked and its 29% from google play services. charged all night and then again at work. kept getting an error with google play services not being updated when i was using hangouts. so i installed and updated the services like 3 times. but i thought it could be because i was using ART and i kept getting the service error and then a com.google.gapps not responding. switched back to dalvik and i stopped getting the error. along with the google services error. just thought i shared that. i do love the fix on the web browser but i might go back to non working browser just to get the extra juice i was getting on my battery.
[Samsung Galaxy Nexus] rice923:
Currently running 11/21 and I have to say, it's actually a pretty decent daily driver. The few things I have to report are:

1) Toyota Entune force closes everytime (I know this isn't exactly a commonly used app, but I'll report it anyways)

2) Graphical glitches like previous builds (rotate and lock screen)

3) Titanium Backup does not work properly (could not restore back ups)

I also have a few questions:

A) What is GEL? I'm assuming it stands for Google ______ Launcher

B) What is Dalvik vs. ART?

Anyhow, I'm very satisfied with the overall stability of this ROM. Thanks for building this ROM, but prioritize your school/studies first. If you fail school, you may end up on the streets. If you end up on the streets, you may not be able to build awesome ROMs:eek:
[Samsung Galaxy Nexus] Sonicmax2k2:
GEL is the Google Experience Launcher :)

ART is the new runtime introduced in Android 4.4. App instability is very likely related to ART. I couldn't use TitaniumBackup on ART, but it works fine on Dalvik.
[Samsung Galaxy Nexus] Rushead:
I'm not having the same issues, but I deleted the stock browser & have been running chrome. I'll report back later re: battery. I was exceptionally heavy handed with my phone yesterday.

Sent from a frequent flasher.
[Samsung Galaxy Nexus] Enter The Nexus:
-GEL is the Google Experience Launcher. It takes advantage of Google Now throughout the launcher. In the launcher you get translucent nav and status bars along with the ability to say "OK Google (Now)" in the home screen or swipe far left for a full page of Google Now info. Its really nice.

-I can't explain Dalvik vs ART well but I'll give you the gist of it. they are different runtime options, with ART being noticeably faster, improving lag and performance all around. Here is a video http://www.youtube.com/watch?v=Y1BesOlQb8c&desktop_uri=/watch?v=Y1BesOlQb8c&app=desktop

Hope I helped.

---------- Post added at 11:59 AM ---------- Previous post was at 11:56 AM ----------

Anyone getting FCs when opening incognito tabs on Stock Browser? Using ART, PA mini GApps, and Mpokang 1080 kernel.
[Samsung Galaxy Nexus] taz1458:
I had no issues restoring with Tibu. Go into the preferences and backup location and hit detect to find where they are. That's what I had to do.
[Samsung Galaxy Nexus] rice923:
I found the location of the backups, and I was even able to initiate the backup process. However, it just hangs at 0% forever.

I switched to ART to try things out, but it FC a few crucial apps, so I'm back on dalvik.

I also have the audio issue with Pandora when I lock the screen during music playback (while streaming BT to my car)
[Samsung Galaxy Nexus] taz1458:
Try to restore one at a time. It sometimes works for me. I've had the same thing happen.
[Samsung Galaxy Nexus] agreenbhm:
I've been running this all day (with the latest PA Gapps and Tiny Kernel 5.3.1), and it is fantastic! I ran Shiny a few weeks ago and couldn't deal with the black boxes and reboots. Obviously the black boxes aren't an issue anymore due to the fix, and I haven't had a single freeze or random reboot. Only problem is Titanium Backup force closing when using ART. Running with Dalvik fixes it. Great work on this ROM!
[Samsung Galaxy Nexus] rice923:
Another issue to report. On GEL and dalvik:

1. Camera is sporadically inoperable (launches but screen is black). Reboot will fix this, but randomly stops working again.

2. Like someone else said, LTE toggle doesn't work.
[Samsung Galaxy Nexus] Rushead:
My camera is working flawlessly.

Sent from a frequent flasher.

---------- Post added at 07:04 PM ---------- Previous post was at 06:26 PM ----------

Interesting problem: had a toast pop up saying sim card was removed. Reboot fixed.

On an unrelated note, anyone have their wifi mac address change? Has happened on the last 3 roms I've flashed.

Sent from a frequent flasher.
[Samsung Galaxy Nexus] agreenbhm:
I'll attempt with a poor analogy. Think of apps on your phone as pizza. You have two choices for getting pizza (in this example): you can order one from a delivery place, or you can drive to the store and buy a frozen pizza. ART is Pizza Hut, Dalvik is Digiorno. The delivery pizza will take longer to arrive and cost more money (time spent compiling the app to native code during install or after a cache wipe), but when it arrives, it's 100% ready to eat (app doesn't need to compile from bytecode to native code). The frozen pizza is physically obtained faster and less expensively, since you just hop in the car and drive to the store down the street, getting back in 5 mins (installing a new app or boot-up after a cache wipe, the app gets the bytecode ready, but isn't native code yet), but now that you're ready to eat it, it needs to be put in the oven (app's bytecode needs to be run through the Dalvik virtual machine, starting up and possibly functioning more slowly altogether).

So, the delivery pizza is slower initially but 100% ingestible on arrival, whereas frozen pizza is faster to arrive but still needs to be cooked. Plus, delivery tastes better (ART is new and sexy) :laugh:
[Samsung Galaxy Nexus] rice923:
Agreenbhn.... That was.... An absolutely beautiful way of putting it. You shall be thanked!

Fwiw, I am still using dalvik due to stability at the moment
[Samsung Galaxy Nexus] agreenbhm:
Thanks, I appreciate it! If anyone is interested, here is a review of this ROM I posted on Reddit. I address ART and Dalvik (from a "making it work" standpoint), so if anyone is looking to try ART, it may be worth a read: http://www.reddit.com/r/GalaxyNexus/comments/1rcyd0/kitkat_is_sweet_again_a_small_review_of_44_for/
[Samsung Galaxy Nexus] sonic147862:
well I had some friends over and left my phone on my desk for a while I think I left it at like %88 and I checked my phone and it's at %8...

I'm going to attach the pictures I would look at better battery stats but it doesn't work on 4.4 yet. I also didn't make any phone calls in that time so I have no clue why phone is at top.
[Samsung Galaxy Nexus] MWisBest:
I ended up getting the SIM thing as well, but I didn't need a reboot: it ended up fixing itself after about 30 to 45 seconds. Not sure why that is.

What in the hell... what GApps are you using, and are you using a custom kernel?

I'm going to get a new build out either tonight or tomorrow... Elder Scrolls Online Beta was fun this weekend! :D
[Samsung Galaxy Nexus] sonic147862:
I'm running paranoid android gapps Full Complete Package and im on ART if that is affecting anything and no custom kernel.
[Samsung Galaxy Nexus] sonic147862:
also I think it could be a sync error because its saying its not syncing but all of my apps are so I'm going to include some pictures of that.
[Samsung Galaxy Nexus] ricola1989:
Anyone else not able to get OTG to actually mount? I plug in my USB flash drive, it says "preparing mass storage device" in the notification bar, then nothing.

Running the latest FML, and mpokang 1080.
[Samsung Galaxy Nexus] MWisBest:
Quick update on this: the WiFi MAC Address has some strange bug on certain devices where it just randomly changes. imoseyon, developer of LeanKernel, came out with a fix for this that generates a MAC Address from a unique ID number that is your-device-specific (like, a serial number or something, I can't remember the exact details) on any devices affected by this bug. Nearly every custom kernel out there uses his work for that, but it seems to be missing from the CyanogenMod stock kernel for the Galaxy Nexus. I have just added it, and it'll be in the next build which should be uploaded in the morning.

Unfortunately, I don't have a USB OTG cable to test out USB OTG. I think I'll end up hacking one up from my USB extension cable and a spare micro USB cable so I can figure this out for you, hopefully I can get that done in the next few days.

So, the new build won't be too exciting. I fixed up a couple things in the kernel (the WiFi MAC address bug I talked about above, I added in to the hardware revision table thing an entry for revision 0xa (10), which is the 16GB model of the VZW Galaxy Nexus (and the one I have), few other misc bugs), and synced up to CM's latest changes of course. I didn't want to do too much as it's late and I'm not entirely sure what CM did over the weekend, I'd like to avoid crap hitting the fan here if I do too much at once.
[Samsung Galaxy Nexus] Sheetzie03:
To try a fix for this, did you log out and then back in?

Or sometimes, simply unchecking and then checking each one.

I get that sync error every once in a while and either of these have always fixed it.

Hope this helps.

♦ToroNex-KK°D♦
[Samsung Galaxy Nexus] MWisBest:
NEW. BUILD. UP. Check the changelog, flash, and enjoy. Then again, the biggest thing in the changelog is in the topic title and announcement header, so you can probably skip reading it if you wish lol.

EDIT: Just a little FYI, I'm still not entirely sure what's up with the battery. Today will be the first time since last Thursday that I'll be out of the house for a decent amount of time, so I should be able to track it down better as my phone will get more use than it did this weekend. It might be related to the SIM card thing that was mentioned a little bit ago, Phone is kinda up there on my usage list, and one of the things that includes is "SIM Toolkit" according to the details in the battery usage screen.
[Samsung Galaxy Nexus] Nephilim:
Is the rotation and crt graphics fixes kernel related or a cm fix?

Sent from my Android 4.4 Galaxy Nexus
[Samsung Galaxy Nexus] MWisBest:
It shouldn't depend on any particular kernel, I didn't make any changes in the kernel regarding this fix.
[Samsung Galaxy Nexus] Nephilim:
So CM code fix then?

Sent from my Android 4.4 Galaxy Nexus
[Samsung Galaxy Nexus] MWisBest:
The fix isn't in CM yet, and the version on their gerrit requires changes to all the Galaxy Nexus device repos (one for toro, maguro, etc) versus the one on my GitHub that only changes the android_device_samsung_tuna repo. Everybody can go ahead and use that or what CM might do, I put my work on GitHub so that others can use anything I do, that's the idea behind open-source in the first place in my opinion.
[Samsung Galaxy Nexus] jlvlawrence:
I've noticed this too. Upon a reboot I go into settings and force stop on the phone app. That'll keep it from keeping a wake lock.

Sent from my Nexus 10
[Samsung Galaxy Nexus] MWisBest:
Is this still happening with the 11/25 build? I haven't seen it yet, in fact it's not even in the top list of battery stats.
[Samsung Galaxy Nexus] RoxRedEye:
GREAT JOB!!!!
[Samsung Galaxy Nexus] jlvlawrence:
Let me flash it and I'll report back.
[Samsung Galaxy Nexus] nalanotae:
I have noticed that with every cm based build I have flashed recently I go to use the gesture typing on the aosp keyboard and it force closes.

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] modernbummer:
Are you using Google Keyboard or the one built into CM?
[Samsung Galaxy Nexus] nalanotae:
The aosp that is built in. Had to install Swype for now I have been spoiled to gesture typing guess I'm too impatient for old school typing, other than that and titanium backup wanting to hang up in the middle of a batch restore I am loving this Rom. Excellent work

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] MWisBest:
Yeah, I'm aware of this issue, I was thinking CM would have it sorted out by now but it's been persisting for a few builds now, so I'll dig into it and see what's up.

In the mean time, I would suggest the Google Keyboard on the Play Store. It's basically just the AOSP keyboard, and swiping in it will work fine.
[Samsung Galaxy Nexus] ricola1989:
This ROM is so amazing. I just flashed it, and there are no graphical errors !!
[Samsung Galaxy Nexus] skylordusa1:
I would love to try this ROM out. Can anyone confirm if wifi tether works?
[Samsung Galaxy Nexus] RoxRedEye:
As of this moment, the only issues I've encountered so far are: LTE toggle not working, panorama not working, no photosphere and the camera settings are a bit of a struggle to go through. Force closes upon swyping were resolved by using Google Keyboard. Other than that -- this is damn near flawless. I've been running this ROM all day and enjoying the hell out of it.

---------- Post added at 06:42 PM ---------- Previous post was at 06:17 PM ----------

Working just fine for me.
[Samsung Galaxy Nexus] metalspring:
As a quick fix, I believe the full PA gapps package automatically replaces the aosp keyboard with the Google one

My only issue with it though is it also replaces launcher3 with the GEL launcher but I don't get why they just can't have it just install the GEL launcher and leave the lancher3 there as well
[Samsung Galaxy Nexus] quickstang:
http://xdaforums.com/showthread.php?p=47806352

Try the post above for photosphere

Sent from my iphone killing Galaxy Nexus running whatever kernel & rom I feel like. For the love of everyone on forums READ BEFORE YOU POST.
[Samsung Galaxy Nexus] MWisBest:
Uhh... anybody got $1,500 so I can get Google Glass? :P

NOTE: I'm joking, I don't think I could accept that kind of money from somebody, let alone GET that kind of money lol. I was invited to buy it though.
[Samsung Galaxy Nexus] skylordusa1:
hahahahah thats awesome. Yeah you need to get those hahahaha.
[Samsung Galaxy Nexus] MWisBest:
I'd love to, it'd even add to my OMAP4 collection!: DROID Razr (my dad's phone), Samsung Galaxy Tab 2 10.1 (my dad's tablet), Samsung Galaxy Nexus (my phone obviously). We didn't even plan that out, it just.. happened, lol, none of the mobile devices we use have anything other than an OMAP4430 or OMAP4460 SoC!!