yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] conceptxo:
This is due to two things:

1.CM is currently reorganizing settings, including performance settings like those. This makes them occasionally disappear.

2. I am fairly sure they are outright unavailable to us until I build a CM kernel for the ROM.

Coming soon, coming soon...like tonight. I have a lot more time today.
[Samsung Galaxy Nexus] conceptxo:
New build in progress

Build 8/21 in the works. Appears to be building kernel + CM Account addon.
[Samsung Galaxy Nexus] JGillis2391:
Hey guys. I'm new to the GNEX coming from the Evo LTE. I have my device rooted with the 8/19 build of this ROM. Sorry if this isn't in the right section, but is there anything you may suggest to help improve battery life? I know the GNEX has a horrible reputation in this area, but I feel like mine is experiencing horrible battery drain possibly worse than others. Without even using my phone I managed to go from 75% down to about 30% in just a couple of hours. I am not a noob and know general stuff, but is there anything I should know to possibly improve it? Is the battery life no different in this ROM than it is on the stock ROM? I am getting an extended battery in a couple days, but I feel like something isn't right here. Thanks for any suggestions/help.
[Samsung Galaxy Nexus] GoSooners345:
Don't use GPS unless it's necessary. Keep data sync off unless necessary

The boss is here
[Samsung Galaxy Nexus] JGillis2391:
Thanks, will definitely give it a try and see if it helps any.
[Samsung Galaxy Nexus] conceptxo:
Best tips:

-Use wifi instead of mobile data when available

-Disable GPS if un-needed

-Disable LTE if you know you will be in a place you're not going to get it anyway. This turns of the LTE radio, and prevents it from searching all the time for a LTE signal.

Also, have you taken an in-depth look at your Battery break down at Settings > Battery? There could be a culprit in particular doing all the damage.

On an extended battery, I tend to last almost-all-day** to all day, accommodating for the fact that I charge my phone when in the car going places. I'm not in the car that much, though.

**This is more to be expected on heavy usage. A day when my phone lasts all day means nobody bothered to communicate with me.

Also, a side note: The build is nearing completion, but I will be doing some testing before posting the update. I want to ensure that the kernel transition for users isn't going to be jarring and cause some kind of issue before I send it out en-masse.
[Samsung Galaxy Nexus] Shidell:
Following up on my original post (regarding 8/18 build); 8/19 is working much better. Where I previously was unable to switch properly between 3G and 4G, I'm now able to do so. (Sometimes my phone lags and/or drops data for a while, which I'm getting to.) Additionally, on 8/18, my device would get exceedingly hot while driving and charging. I presume this is related to radio switching and problems with that.

8/19 seems to clear all of that up.

There are a few quirks, but Sprint is in the process of rolling 4G out in Milwaukee, and it's starting to show up in new areas at random around the metropolitan area. Thus, I'm not certain what is a "quirk" with my phone's radio and what is a "quirk" with Sprint's network.

All in all, 8/19 seems to be very solid. Looking forward to your continued builds, and testing the CM kernel.
[Samsung Galaxy Nexus] JGillis2391:
Thanks for taking time out to respond and for the work you're doing on this ROM. :)
[Samsung Galaxy Nexus] uplink.cu:
wallpaper issues

Anybody here know how I can set the lockScreen Wallpaper?....

thank.
[Samsung Galaxy Nexus] conceptxo:
While I don't know if this new to 8/21 (due to that as I have said before, CM settings are still being redesigned for CM 10.2, and thus some are missing), I was able to set a custom image from Settings > Lock Screen > Wallpaper just now.

Well everyone, I did it - we are now on CM's kernel. Woohoo, I guess.

(it wasn't that hard anyway)

I did some testing on installation order and etc during my flashing and testing of this build.

We unfortunately still need to flash SuperSU and gapps each time. Sorry everyone.

Speaking of missing settings, we're still missing the Advanced section for our device. It's due to the reorganization, which wasn't fully done when CyberKitsune put his out back on the 6th of this month. That's something we have to wait on CM for.

Major changes in today's build include notable fixes to setting lockscreen shortcuts, many translation additions, a few crash fixes in various CM/Android OS applications, and a small change to CDMA telephony's reading-of-information from the network.

It is uploading now. OP will be updated and I will bump again.
[Samsung Galaxy Nexus] jjhrrsn:
Good news thanks for the builds
[Samsung Galaxy Nexus] conceptxo:
Build 8/21 has been posted. Does not include CMAccount, I had some issues getting it to roll into the build. I will try again with the next one.

Enjoy!
[Samsung Galaxy Nexus] shawn.irwin:
By advanced options do you mean developer options, or is it something else?
[Samsung Galaxy Nexus] conceptxo:
The 'Advanced' menu contains specific tunables for the device like gamma touch calibration and some other stuff. It's being reorganized right now. I actually meant to say that the reorganization hadn't started yet in the post you quoted.
[Samsung Galaxy Nexus] conceptxo:
I think it's important for a lot of people to remember that Sprint's hardware is (unfortunately) in a constant state of flux during the whole rollout process. This can lead to difficulty in determining issues within the radio layer.

8/19 introduced changes to signal handling in CDMA, and 8/21 adds changes to the manner in which CDMA devices query information from the network.
[Samsung Galaxy Nexus] PhazeDelta1:
So any word as to when we'll start getting official CM 10.2 nightlies?
[Samsung Galaxy Nexus] Jimlarck:
Unfortunately that's up to CyanogenMod, sorry :(
[Samsung Galaxy Nexus] JGillis2391:
Will there ever be an OTA implemented to this ROM? Just curious. :P
[Samsung Galaxy Nexus] conceptxo:
Maybe never. Its a grim state. Official support, to my knowledge, requires the device to build automatically within their build tools, and for their to be appropriate blobs relevant to each Android version. Ours, unfortunately, does/has neither. We use blobs, aka drivers, from Android 4.2, and a specific toroplus-only change that breaks compile on other devices, according to gerrit. This change lets us load these radio drivers, which are specific to toroplus, while we load up-to-date drivers for the rest of the board(tuna).

I'm considering it. If time allows then maybe. But it would require me to roll my own OTA thing, or learn the intricacies of goo.im's system, if that's even still running. It would also break my "no kanging" rule but it might be for the greater good.

Stay tuned.
[Samsung Galaxy Nexus] conceptxo:
Addendum: Ensure your device is listed in Android Device Manager

I tried this out today and noticed my device was unlisted.

Users, please test and report if your device is listed without any extra work at http://android.com/devicemanager

If you find your device is unlisted, perform the following steps:

1. Open Google Settings(the green icon from the App Drawer)

2. Tap Android Device Manager, and uncheck "remote wipe".

3. Go to System Settings > Apps > All > Google Play services, and tap "clear data".

4. Go back to Google Settings, check 'remote wipe'.

5. Reboot device.

6. Upon reboot, wait approximately five minutes, then log into Device Manager. Your device should now be listed.

If everyone is getting delisted each day, or if everyone is getting delisted upon moving from another ROM to this one, it needs to be noted. This, I suppose, could be alleviated through CMAccounts, but the point is to have multiple functional options. Because that's what people want.

Thanks all.
[Samsung Galaxy Nexus] Lowen SoDium:
Speaking of drivers, are you using the drivers from this page?: https://developers.google.com/android/nexus/drivers#toroplus

I don't know if those are newer or the same as the ones you are using. The ones at the very bottom are from June of this year.
[Samsung Galaxy Nexus] conceptxo:
We're using radio drivers extracted from Sprint's 4.2 update. These are the basis of the cm_toroplus device folder for CM-10.1. We then use that compatibility shim to load the radio drivers. Then we load the rest of the drivers from 4.3 blobs, from the tuna device tree, which is the common board among maguro, toro, and toroplus.

It's my understanding that the experimental AOSP binaries for toroplus don't actually connect to the Sprint network. They crash, according to JBQ when he spoke about this sometime last year.

Whether the state of those drivers has changed or not(specifically to the June releases) is unknown. I could try to build a copy with those blobs, but it would change the structure of the build a lot, and I assume we would need to remove our toroplus fix. There's a lot of "ifs" there.

But if there is any empirical evidence that points to better performance with those, then I am happy to investigate.
[Samsung Galaxy Nexus] Shidell:
What I'm confused about is how Toro is being supported, whilst Toroplus is mired in the weeds, so-to-speak.

Toro doesn't have any new drivers either, right? So, isn't Toro also using 4.2 drivers in the 4.3 builds? How is that working so well (and being "officially" supported by CM) if they're in the same boat Toroplus is?
[Samsung Galaxy Nexus] GoSooners345:
I'd test a build without the fix and with those blobs on said page. If it works we may be in luck

The boss is here

---------- Post added at 09:44 AM ---------- Previous post was at 09:43 AM ----------

Actually look in the Toro section and it has updated binaries

The boss is here
[Samsung Galaxy Nexus] Shidell:
You're right. That's pretty surprising.

Well, I guess that explains things then.
[Samsung Galaxy Nexus] uplink.cu:
Wallpaper Lock screen problem continues for me on this update.

Thank
[Samsung Galaxy Nexus] conceptxo:
Yeah in literally the strangest twist in the Nexus saga, Verizon provided new binaries for 4.3 for their model. Sprint/Samsung/who the hell ever didn't do so for toroplus. Its a sad state of affairs. My next Nexus will be carrier-free.

How did you move to this ROM? You may need to wipe system and cache and reinstall the ROM. This preserves personal data.

I ask this because I can say without a doubt the feature works. I've attached an example. Its my lock screen with a screenshot of yesterday's build info as the custom background.
[Samsung Galaxy Nexus] uplink.cu:
Ops... I only update because I came from the last one.

Thank for the tips.
[Samsung Galaxy Nexus] tommy1121:
Just wonder, are you guys doing a full format including system and also deleting the android file on the sdcard? Or am I paranoid for always believing it on my own. Or doesn't matter if I delete that or not?
[Samsung Galaxy Nexus] GoSooners345:
Doesn't matter

The boss is here
[Samsung Galaxy Nexus] jesusice:
Coming from a different ROM you should wipe /data but leave the SD alone. I also wipe /system on a fresh install but the ROM zip probably wipes it anyways. Updating night lies just flash right over without clearing anything and then flash Gapps again and SuperSU.
[Samsung Galaxy Nexus] conceptxo:
This is the correct order of operations.
[Samsung Galaxy Nexus] tommy1121:
Thank you for the clearing of the confusion. i have noticed that the built-in SU is working fine with me right now. one of the latest updates fixed it for me. i don't use titanium backup at all i just start from the beginning and start from fresh all the time. so far the only issue i am having is of course the 4g/3g transaction and sometimes i just don't have data so i have to airplane or reboot. tethering is working well but sometimes it does time out and loose internet passthrough, usually reboot fixes that. i have usually 2 bars of 4g and in a speed test @ speedof.me on the computer i get 2.3-3.2 MB down and 800kb - 1 MB up. if anyone has any suggestions to help speeds please let me know ISP said that they will not be out till 8/27. grrr verizon. i have kids that like to watch netflix (we just moved into a place we just bought).

ps. i notice that the android folder on the sd card holds some stuff from the other roms thats why i manually delete just that folder when switching roms. unless im just over thinking the process.
[Samsung Galaxy Nexus] jesusice:
The android folder is used by apps you install, I think just for extra files that they download. Any ROM settings or from system apps would keep their data in /data, I believe. So it may be a good housekeeping to clear out the android folder but not clearing it won't cause any problems when switching ROMs.
[Samsung Galaxy Nexus] conceptxo:
A note:

Noticed some radio issues today, namely the RIL dying and data just never coming back. Doing some work to try to get a better grasp of what can be done going forward to improve our experience on the drivers we've got.

I'll rebuild late tonight or first thing tomorrow, it will pop up within the next 10-12 hours. Thanks for your patience, today was a bit busier on my end again.
[Samsung Galaxy Nexus] tommy1121:
OK. Ty. See this is why I like xda I actually learn something and not always trial and error. :)
[Samsung Galaxy Nexus] GoSooners345:
I had 4g where I normally have 4g today :)

The boss is here
[Samsung Galaxy Nexus] InfDaMarvel:
I've experienced stronger signal. I still see it losing signal going from 4G to 3G. Thanks for the work.
[Samsung Galaxy Nexus] uplink.cu:
When I push home button to exit of some app the phone-desktop apps-icons disappear, but for now is only when I execute Facebook for more than 15 or more minutes. This issues only happen with that app for now... Thank
[Samsung Galaxy Nexus] jesusice:
It's a RAM thing. Facebook is using up so much memory that the launcher has to reload. Happens to me using Chrome Beta.
[Samsung Galaxy Nexus] uplink.cu:
Thanks for the information.
[Samsung Galaxy Nexus] SilentStormer:
Alright so I clean flashed the latest build and if I turn the phone off and then back on it won't boot. It'll boot the first time but after that if I try and restart the phone it just sits there, I've let it sit there with the CM animation going for over and hour and still no dice.

Thankfully I can still get to recovery by battery pulling and then going into fastboot, but I seriously can't get it to boot more than one time per flash. Weird, especially since nobody else seems to have the issue.
[Samsung Galaxy Nexus] InfDaMarvel:
Bad flash, try again. Flash Rom, gapps, superSu.
[Samsung Galaxy Nexus] SilentStormer:
Yep, reflashed twice now. Still the same result.

EDIT: I guess I'lll redownload, maybe something got lost in transmission.
[Samsung Galaxy Nexus] adio201:
Try in recovery fix permissions see if that helps
[Samsung Galaxy Nexus] AndroidUzer:
What recovery are you using?
[Samsung Galaxy Nexus] SilentStormer:
Well. I redownloaded the ROM, gapps and SU zips, fixed permissions and still nothing. It simply won't start up after the first time. I have no idea what the problem is here.
[Samsung Galaxy Nexus] conceptxo:
You need to run a logcat and wait for your device to attach during bootup. Then post said logcat. You're experiencing some kind of edge case, so looking at the fine print is the only way to determine what's wrong.
[Samsung Galaxy Nexus] Jimlarck:
Oh and please, for all of our sake please put it in a spoiler :P
[Samsung Galaxy Nexus] AndroidUzer:
You could try a different recovery? What are you using now?
[Samsung Galaxy Nexus] SilentStormer:
latest TWRP
[Samsung Galaxy Nexus] AndroidUzer:
Last ditch effort...

Not that I have had good luck with it but you could try clockworkmod you will need to flash it using command line while booted to fastboot using adb commands:

"fastboot flash recovery recovery-clockwork-touch-6.0.3.6-toroplus.img"

I have attached the basic adb essentials for Android 4.3. After extracting place recovery-clockwork-touch-6.0.3.6-toroplus.img in the same directory, navigate in command line to the adb43 directory then run the commands above.

p.s. make sure USB debugging is enabled & This is all at your own risk ;)

Good luck!
[Samsung Galaxy Nexus] conceptxo:
This isn't going to help the root issue. Please provide a logcat of a hanging boot.

This is a very peculiar issue.
[Samsung Galaxy Nexus] GoSooners345:
Did you try the drivers on that page

The boss is here
[Samsung Galaxy Nexus] conceptxo:
If you're referring to the experimental blobs for the Sprint Galaxy Nexus listed on Google's Nexus program page, then I have not, because they have never been known to actually connect to the Sprint network. It was an issue that JBQ brought up some time in 2012, in that it was an effort they were working on, but it still hadn't come to fruition. I have heard no reports of the June binaries being any different.

Edit: build 8/23 is now in progress.
[Samsung Galaxy Nexus] Shidell:
Out of curiosity, what are you using to build your images, Conceptxo? There's been a lot on the topic of Android builds growing exponentially in time (and hardware) required.

I've been thinking of setting up an ElementaryOS Luna AMD64 HyperV client for the purposes of dabbling with Android (and more specifically, this Galaxy Nexus radio business) but I'm not sure building Android in a HyperV client would be practical.
[Samsung Galaxy Nexus] conceptxo:
My personal computer. Important specs are 8 GB RAM, and current-gen i7 clocked at 2.1 GHz.

My buildbox is a VirtualBox VM running Ubuntu 12.10, one of the recommended distros for building Android, as listed on Google's "Building Android" page. The VM itself is a fixed size image, about 70GB in size. I think its a bit bigger than it needs to be. But anyhow, its that size with a 16 GB swapfile inside the fixed image. I give the VM itself anywhere from 4 - 6 GB of RAM, depending on my host OS at the moment(Windows or Linux Mint). My source tree + build tools reside on that virtual machine. I have all of the hardware acceleration and visualization options enabled. As you can tell, I don't have enough space in this setup for a CCACHE, so I don't use one.

Builds take anywhere from 1-3 hours, depending on if you're doing a clean build or not.

I'm happy to provide any additional information if needed.
[Samsung Galaxy Nexus] InfDaMarvel:
1-3hours with a i7 and here I am with my lil old i3. It would probably take me 5 hours to build.

What type if hard drive? SSD?
[Samsung Galaxy Nexus] conceptxo:
Believe it or not, it's either a 5400 or 7200 RPM disk drive.

Build 8/23 uploading now.
[Samsung Galaxy Nexus] conceptxo:
Build 8/23 is now uploaded, and linked in OP. Notable changes to Focal, although we still have the graphics artifacts. Other changes include general bugfixes and translation additions. Please note and report radio performance on this build. Thank you.

Edit: Settings reorganization continues. We have a new area called "Buttons". So again people, fear not, your favorite CM settings are returning, and rapidly. 8/23 is also uploading to Mirror 2 now.
[Samsung Galaxy Nexus] Wickster:
I find Focal more stable (without artifacts) when I got it uninstalled and use the one linked here to install it instead.

Maybe we can try and replacing the one in the ROM build with this one and see if it works better? I could try it with the new build, when I get home from work.
[Samsung Galaxy Nexus] conceptxo:
Interesting. This points to an issue in my build environment. I'll investigate.

Edit: it's a much older build. hmm...

Double Edit: Build 8/23 is now also available on Mirror 2.
[Samsung Galaxy Nexus] Wickster:
I extracted the Focal APK from your 8-23 build and installed on normally to my Gnex which is running your 8-21 build and I still get the artifacts. So I'm guessing that the newer Focal app builds have the artifacts while the older build posted above does not.
[Samsung Galaxy Nexus] Shidell:
Thanks! :) My work machine is slightly older, with a first generation quad i7 and 8Gb. of RAM as well. It works wonderfully in VS, but I imagined that running Linux in a HyperV client coupled with whatever environments Android needs ontop building Android itself would probably put a big strain on it. I do have a Dell server here at home, with four physical processors (dual core each) and 24Gb. of RAM, but I'm pretty clueless when it comes to Android development and Git repos, etc. I can set up Linux and get the Android source and build it, but that's about as far as I can go comfortably.

If it isn't too tough to sync to the server and kick off builds there, that might be a good use of resources.

I've always been interested in learning more about Android dev and trying to port to devices, but the learning curve is steep and that's daunting. Plus, I'm not sure how I feel about the fixed-firmware situation in Android land. Sure, it's great that we can get the latest source for Android, but without compatible binaries, devices are pretty much screwed. Case in point, Toroplus on 4.3. Thankfully, it seems that the changes are fairly minor, and the compatibility shim you mentioned can patch things together.

How long did it take you to get your head wrapped around things? Did you have a linux background before starting?
[Samsung Galaxy Nexus] conceptxo:
Well, I'll start at the end.

I come from nine years of *nix experience, mostly focused in Linux. I have almost four(coming soon!) years under my belt as a developer proper, working with code and projects and whatnot. I spent the last year doing a research project in automated and autonomous robotics built off Arduino and Android hardware platforms. But I have a decently broad knowledge base of languages and build tools and the like.

When I sat down to learn to build Android, I came with plenty of background knowledge I had accumulated from reading about various different things over the two years I've had an Android device. But when I actually sat down to do it and build up for toroplus, it took me about 8 hours, most of which was downloading code. My learning material was Google's Android Building Article and the auto-generated CyangogenMod wiki page for building for our device. The rest was experimentation.

The driver problem is truly a fickle one. Hardware manufacturers need to start getting on board for open-source drivers for hardware. It's just a pain in everyone's ass to keep that code closed, and they're quite frankly serving themselves no good. They're not protecting the secret sauce of their hardware that way, they're just making issues. The Replicant OS project seeks to eliminate that issue by building a fully-free(as in libre) version of Android with open-source drivers. Unfortunately, (and as somewhat to be expected), their hardware support is minimal. But it's no doubt a project worth pursuing.

Your Dell sounds like more than enough of a beast to whip out builds in very short time. You wouldn't even need to make some kind of swap space just for the compile. And I'm assuming with that hardware you've got decent storage media, which means you can even use a CCACHE to speed stuff up.

I won't lie, I'm unfamiliar with HyperV. Cursory Googling implies to me that it's Microsoft's built-in virtual machine solution. Is this correct?

Regardless however, a Linux build environment for Android isn't too heavy. I mean, my virtual machine even runs X and Unity(because I'm stupid and accidentally hit "Ubuntu Desktop" instead of "Xubuntu Desktop" during my netinstall of Ubuntu). I just login to a terminal and start working from there anyway.