yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] musical_chairs:
New build up:

- GPS should be working out of the box now.

- APN settings are now user-accessible.

- added two minor tweaks to dexopt screen, first boot after flashing should be slightly less annoying.

Please test mobile data connectivity thoroughly. I found something that fixes the issues I was having on toro (no LTE on bootup, mobile data stayed connected even when wifi was connected). If you find mobile data to be worse on this build than on the previous one, edit your builp.prop to disable this line:

ro.telephony.ril.config=setPrefNwTypeOnUnsolConnected

Easiest way is to put a pound sign in front of it to comment it out, like this:

# ro.telephony.ril.config=setPrefNwTypeOnUnsolConnected

(This is based on an open cyanogenmod commit, this build.prop line won't do anything on any other ROM or any other build.)
[Samsung Galaxy Nexus] Max Frost:
Good morning , I've installed the new build . I can report GPS is working out of the box . Mobile is switching off when wifi comes on and 3G data connectivity is working . APN access is also working now . I've tried getting LTE to work trying various known good apn settings . I reflashed both CDMA and LTE radios as well and LTE shows enabled . Just never comes up . Does the Toro also have 2 radios or just 1 ? Something just seems disconnected for the LTE ril somehow . On the bootup annoyance , I'm not sure what that is . It took about 20 minutes to flash but I left the phone alone and it completed fine . Rom is snappy and running good . Thank you !!!!
[Samsung Galaxy Nexus] musical_chairs:
Thanks for the report. I've said this before, but I'm pretty much shooting in the dark trying to get LTE working on toroplus. I have one toroplus activated, but it's hacked onto Page Plus and only gets 1x data. (I never finished the hack to get 3G working, and for how that phone gets used it's not worth it.) I'm not sure when LTE last worked on toroplus, maybe the official CM kitkat builds? I don't remember anybody saying they ever had it working on any Lollipop ROMs, mine or anybody else's. I keep hoping that someday somebody is going to say, "Hey, LTE is working on the latest build!!" but so far that hasn't happened...

The 'bootup annoyance' is that horrid white "optimizing apps" screen and the spinner that goes around, and around, and around... I made the screen dark instead of white, and turned off the spinner, since apparently it uses a fair amount of CPU power, so it shouldn't take quite as long now to optimize apps after a flash.
[Samsung Galaxy Nexus] Max Frost:
Man , you should switch that toroplus to Ringplus . I have 5 phones on it . each one gets 1000 texts , 1000 minutes and 1000 megs of LTE absolutely free . If you don't go over those allocations the bill is ZERO , not even any taxes . Sprint network . You could really work with it then . Super easy to get on an activated .
[Samsung Galaxy Nexus] stickmansgallows:
I couldn't get any Google Apps packages to work with the 20160327 build. Kept popping up with "Unfortunately Google Play Services/Store has stopped". It works fine with the 20160319 build and only flashing 20160327 after setup.

GPS and 3G work fine. No 4G.
[Samsung Galaxy Nexus] musical_chairs:
So flashing 0319, running through setup, then dirty flashing 0327 works fine, but a clean flash of 0327 causes issues with gapps? Interesting...I don't know what i could have done that messed it up, maybe something from CM broke it?
[Samsung Galaxy Nexus] Max Frost:
He is correct . I've spent 3 hours flashing Banks , Open and DHO gapps trying every trick in the book . You just can't ever get past the FC's for Google play services , play store etc . All 3 gapps do work with 03/19 . I just went through it all to see if it was just his issue . I cannot flash this latest build clean . On dirty flash it's ok although there are some problems with apps like Hangouts I've encountered that were not in the previous build . Reflashed 03/19 , zero errors , 03/27 constant FC's . Hope this helps !
[Samsung Galaxy Nexus] musical_chairs:
And, we've got baseband on Lollipop! Thanks to [MENTION=3927368]poo706[/MENTION] for pointing me to the patches I needed.

First cm12 build for toroplus:

https://www.androidfilehost.com/?fid=95887005526787732

Note that my toroplus is no longer in service, so I can't test phone calls, data, etc., at this point. Baseband is working now though, and all the pieces should be in place. But consider this your disclaimer / warning.
[Samsung Galaxy Nexus] yotvb531:
It took a little while longer than normal for the first boot which is probably to be expected on a new OS. I noticed it only has Verizon APNs, not Sprint ones. I could still get 3G data though (I didn't ever end up with LTE).

Thanks for your hard work!
[Samsung Galaxy Nexus] musical_chairs:
Okaaay? Yeah mine has the Verizon APNs now too. Last night it had the Sprint APNs, I even reset them to make sure it would load them correctly. Booted it up this evening, and it's got Verizon APNs. Very well then, I'll have to do some digging...
[Samsung Galaxy Nexus] musical_chairs:
Try flashing this APN fix in recovery:

http://xdaforums.com/showpost.php?p=57890624&postcount=17
[Samsung Galaxy Nexus] musical_chairs:
New build (20150112) added to the OP. Camera works, also HW Video decoding. Also, all the latest CyanogenMod goodness.
[Samsung Galaxy Nexus] Roman20:
Excellent, can you tell me if root access is working.
[Samsung Galaxy Nexus] yotvb531:
It works if you install SuperSU. I couldn't get it to work otherwise.

Other other main issues I'm having are general lagginess and no 4G. Lagginess is improved if I change the performance settings to performance instead of balanced. I haven't found a fix yet for 4G. I've been trying different APN files to no avail.

It's close to the daily driver state for me. I'll see how long I can run it.
[Samsung Galaxy Nexus] jnever1:
same

SuperSU has been the requirement for me on toroplus, grouper, and flo, respective to cm12.

I had to grab it as recovery-flashable from download.chainfire.eu/641/SuperSU/

Could not achieve 4G, even using a self-maintained apn-conf.xml. Multiple attempts to repair using multiple apn-conf.xml sources, including that packaged with the ROM resulted in killing data entirely. Cell service was restored only after full reboot.

I haven't tied the latest build.
[Samsung Galaxy Nexus] musical_chairs:
I agree, it's not nearly as fast as I'd like. I hesitate to mess too much with the kernel at this point, the goal here is to provide something close to stock nightly builds.

Unfortunately, I can't test 4G, so I'm kind of shooting in the dark on that one. Does 4G work on FML?

Root has been working fine for me on CM, though I know a lot of users on maguro and toro report needing to flash SuperSU. Thanks for the report.
[Samsung Galaxy Nexus] yotvb531:
I'm still running it the latest build. It seems like after about 24 hours (probably much sooner, but it's when I noticed) the ROM sped up. I can now use the Balanced mode without major performance problems. I wonder if Google auto backup or something running in the background was causing it to running slowly at first.

Still no LTE. I couldn't ever get it with FML either. Running pretty well other than that. Chrome browser is pretty slow, but using the built-in browser isn't too bad.
[Samsung Galaxy Nexus] musical_chairs:
New build added to op.

It seems that Ziyan has been tweaking the minfree values as well as some other kernel stuff, hopefully the lag will be less on this build. I know things have been very laggy lately, especially browser, GMail, G+, etc. I've been using the 'clear all' button in the app switcher, this helps tremendously with the lag. But hopefully that won't be needed from here on out.

It seems Theme Engine and various other visual changes have landed in this build, so expect a few bugs in that department for the moment.
[Samsung Galaxy Nexus] yotvb531:
Performance is way better and very usable now! Thanks!
[Samsung Galaxy Nexus] yotvb531:
Anyone else have really quiet sounds on this ROM? It seems like this happened when cm10 or cm11 first came out too but got fixed pretty quickly.

I can barely hear my notifications or ringtones, and the sliders are all turned up to the max.
[Samsung Galaxy Nexus] musical_chairs:
I'm thinking I had seen a patch recently to up the volume settings. The changes were much bigger for maguro than for toro or toroplus, so I didn't pick it. Now I can't find it...but I wonder if that wouldn't have helped. I'll keep looking.
[Samsung Galaxy Nexus] PeterFlinstone:
I don't now if I'm the only one with this bug, but using the latest build (01-15-15) neither Google Camera , Whatsapp's camera or the default one will work. Any advice ? I have the logcat, in case you want to check it out.
[Samsung Galaxy Nexus] musical_chairs:
Does it work after a reboot? If the camera crashes, it is typically locked out until a reboot. The easiest way to make the camera crash is to tap the 'torch' tile in the quicksettings dropdown, but I've seen reports that allowing the screen to time out while the camera is active can crash it as well. Also, the camera sometimes crashes after a day or two of uptime, for no apparent reason.

There may be other ways to reset the camera without doing a full reboot, but a reboot always gets it going for me. But the camera definitely works on my gnex's.
[Samsung Galaxy Nexus] jcruz942:
Can anyone report if the video recording is working on the 1-15-15 build? To my knowledge the only lollipop with video recording working is FML.
[Samsung Galaxy Nexus] PeterFlinstone:
At first I thought that the denisty change was the cause, but I returned it to default and still the same. About the torch solution in QS , I don't have it . On Settings it appears active, but it simply doesn't show.
[Samsung Galaxy Nexus] musical_chairs:
If the camera is locked up, the torch tile won't show. After a reboot, the torch (flashlight) tile should be there, but it is broken and doesn't work, so don't tap on it. If the camera doesn't work after a reboot, then something is messed up. Try clearing data on the camera app.
[Samsung Galaxy Nexus] JerichoKru:
I seem to be lacking the stock camera and the torch tile (since it's broken, doesn't matter).

Google camera won't open.

I got the latest build...so did I mess up somewhere?

EDIT: just noticed the new build appear, testing now.

EDIT-2: Jan 21st build installed, still no camera app; google camera still crashes

color inversion seems to do nothing
[Samsung Galaxy Nexus] musical_chairs:
The Gapps issue was a bug on CM's end, it will be fixed in the next build.
[Samsung Galaxy Nexus] musical_chairs:
A new build is up, the gapps issue should be fixed. I did not test a clean flash, but there are plenty of reports from other devices pointing to a specific date when the problem started, as well as a specific patch that fixed it.

I've also put up a build of TWRP 3.0.1, since one if the changes was a fix for the loooooong flash times.
[Samsung Galaxy Nexus] Max Frost:
Good morning . I cleaned flashed the new build and it was perfect ! Not the first belch or burp . Google account restore of apps and account completed . I'll continue to test for you and report any issue I encounter . I don't think I ever heard back from you on whether the Toro also has 2 radios , cdma and an LTE ? What I mean is if you flash radio does it install a cdma and then an LTE separately ? The Toroplus does that . I have other devices that if I flash a radio it just flashes one and I assume they must be combined . Thank you .
[Samsung Galaxy Nexus] musical_chairs:
Yes, toro also has two radios. The devices are very similar, both in terms of hardware and radio interface layers.
[Samsung Galaxy Nexus] Max Frost:
Oh sorry , I also meant to post earlier the new twrp was much faster . Flashed in normal time like in the past . So its odd that if the two radio setups when compared side by side and both 3G's work but one LTE works and the other doesn't what could be breaking it .

I observed this the other day while trying to get LTE to work . I switch the preferred network to LTE and wait . While I'm waiting theres no 3g or LTE icon lit . Finally after a bit of it trying to establish LTE ( a good 5 minutes and more ) it finally gives up and the 3G icon lights up as if 3G is established . The setting is still on LTE at this point . Now if you try to access the net , load a webpage etc , you find you really can't . Nothing connects as if data is just off . So your phone is showing 3G but in reality it really isn't working . You then switch over preferred network to cdma , 3G pops back up ( about 10 seconds ) and it works fine . This indicates time passing while trying to connect in LTE , it's either trying to get the radio up and going or it is up but relentlessly trying to negotiate a connect . When it does fall back the pathway seems somewhat invalid with 3G lit up but not funtioning . I wish I knew more about roms , maybe this will give some fruit for thought . Toro works but Toroplus doesn't . What bridge is out causing it to stop , almost like switching on the light ( LTE )but the bulb isn't really getting power or not really active . or is it a matter of negotiation breaking down somehow with the carrier . Very puzzling .

Hey , you think if I were to log it we could get somewhere with what's going on with it ? Maybe we could at least determine if its one thing or the other . Hardware setup malfunction or Negotiation setup side .Thank you
[Samsung Galaxy Nexus] musical_chairs:
You can grab some logs, I can't promise I'll be able to make heads or tails of them. The most interesting log would be:

adb logcat -b radio

but a normal logcat might be interesting too. Might as well log it moving through all those steps you mentioned.
[Samsung Galaxy Nexus] Cardcaptor_RLH85:
So, I never got around to trying out either of your March CM 13 builds but, I installed the April 2nd build today and it's running quite well without any of the issues that were reported with the previous builds.

I only have one issue so far (other than the already known issue of no LTE) Marshmallow seems to have removed the ability to change the date format. I use the EN_US locale but I normally use the ISO-8601 date format (YYYY-MM-DD) because, when I have apps that create files with dates in their names, that's the only one that sorts chronologically without changing from sort by name.

So far, the only solution I've seen was to change the locale to one that uses the date format you prefer. That works for people who want to switch to D-M-YYYY from M-D-YYYY but, there's no locale that uses ISO date formatting. I know this isn't an issue specific to this ROM but, is there any way to fix this at the ROM level or should I try filing a nuisance bug report with CM or AOSP to try to have this change from Lollipop reverted?
[Samsung Galaxy Nexus] musical_chairs:
This seems like the kind of thing that CM should fix. I wouldn't expect AOSP to care too deeply. I could probably revert it too, but for now I want to try to keep from deviating from stock CM more than I have to.
[Samsung Galaxy Nexus] musical_chairs:
New build up. Synced with cm, so the April security patch is included. No other changes on my end.
[Samsung Galaxy Nexus] SpideyTheMan:
Good work as always! Thanks for your efforts to keep the Sprint Galaxy Nexus up to date with Android builds. It's unfortunate that Google doesn't have a better method of keeping all Android phones running with the latest software.
[Samsung Galaxy Nexus] musical_chairs:
New build up.

I cleaned house, removing most of the Sprint proprietary apps. None of the unified tuna builds are using them, and I'm thinking maybe we're at the point where things would work better without them. I kept hiddenmenu.apk (that one is still potentially very useful), but the rest of them are gone (yes, I also removed SDM.apk, the app that automatically tries to activate the phone on Sprint on boot-up.) Please let me know if you see any network or mobile data related changes.

Also, any reports on Sprint's OTA programming behavior are welcome - does this break things completely?
[Samsung Galaxy Nexus] Max Frost:
I'm downloading rom and gapps for a clean flash this morning . Will test and report back . I'm still planning to test LTE stuff for you but I haven't been back in an LTE area yet . When I do I'm taking my laptop so I can adb logcat .

edit [MENTION=4531957]musical_chairs[/MENTION] Build seems fine so far . data works the same . Everything seems about the same . I'll keep checking it out . Not much chance today.
[Samsung Galaxy Nexus] musical_chairs:
Your input is much appreciated. As I think about this more, it seems like we want to keep SDM.apk as that is what does the 'hands-free activation' or whatever Sprint calls it. Users (like me) who are not on Sprint can just delete it. Bonus points for using an addon.d script to automatically delete it every time you flash an update.
[Samsung Galaxy Nexus] Max Frost:
Yeah I'd definitely leave it . I switch around on MVNO's from time to time and each time I have to activate and the activation script comes in handy . It's one of the few devices where you can actually use dialer codes and activate without going back to stock .

edit [MENTION=4531957]musical_chairs[/MENTION] New problem . Wifi disconnects when display goes off as in no wifi with sleep . This is brand new problem . Could it be associated with something you removed . Wifi is set to always on in dev options . Comes back on as soon as you wake the phone . Thanks
[Samsung Galaxy Nexus] musical_chairs:
Well it seems SDM.apk needs BIP.APK... I'm going to bring them all back except for the SymcML stuff, which is definitely not needed.

Regarding the WiFi drops during sleep, I think my toro has always done that on MM. I did a bit of searching, it seems this has been a problem with some combinations of devices and routers ever since MM was released. The workaround has been to enable the legacy DHCP client (in Developer options). Does that make a difference for you?
[Samsung Galaxy Nexus] Max Frost:
[MENTION=4531957]musical_chairs[/MENTION]

On the wifi , mine has stayed on rock solid 24 hrs a day on all of your MM builds until this one . I have to admit I skipped the last one . I'm guessing maybe some of that sprint stuff you removed might be the problem . Wifi disconnects when the screen turns off whether it times out or I press the power key . I'm going to flash the previous build to verify and narrow it down . These aren't random drops at all . 90 % of my calls are via wifi with hangouts . I even ported my number to google way back so wifi is ultra important to me . I will let you know about the other build . Thanks

another edit : [MENTION=4531957]musical_chairs[/MENTION] previous build wifi stays on during sleep . I have cleaned flashed the latest build twice to be sure wifi wasn't a fluke and the previous build clean also . Problem definitely happens with last build .thanks .
[Samsung Galaxy Nexus] SuperGoober:
I'm having the same issue as Max , we've never needed a workaround until now . Maybe some important sprint part got removed . Could be why toro has that problem , something important got stripped out of Toro back whenever ?
[Samsung Galaxy Nexus] musical_chairs:
Thanks for the reports. On toro, I'm only noticing the WiFi drops if mobile data is connected, and that's up in my bedroom where the WiFi signal is a bit weak. I'm checking the toroplus out more thoroughly now to see if I can reproduce the issue. How quickly does WiFi drop after you turn off the screen with the power button? Does it drop when the proximity sensor turns the screen off during a hangouts call?
[Samsung Galaxy Nexus] musical_chairs:
Here's a build that is a few days newer and has the Sprint apps included again (except for the SyncML stuff):

https://www.androidfilehost.com/?fid=24521665358594234

I have not yet been able to reproduce the WiFi drops on either the 4/19 build or this 4/22 build/ with or without the Sprint apps.
[Samsung Galaxy Nexus] Max Frost:
Sorry , I had gotten back on an older build . Wifi wasn't dropping during calls or while using the phone . It would drop within a minute or 2 after turning off the screen and would not come back on until the next time you turn the screen on .I'll try this new build today . I also recieve my calls on wifi and stay in airplane mode with wifi on . When wifi turns off I can't recieve calls . Mobile data is out of the picture and wifi signal very strong . thanks
[Samsung Galaxy Nexus] Max Frost:
[MENTION=4531957]musical_chairs[/MENTION]

Hey , I'm testing the new build , no results yet . Can you please tell me what you did to make the apn settings user accessible and or point me to the commit or whatever ? A friend is building for another device and really needs whatever you did . Its for s3 sprint and it is a cm based rom . thanks
[Samsung Galaxy Nexus] musical_chairs:
It's just an overlay in the device tree:

http://review.cyanogenmod.org/#/c/141520/
[Samsung Galaxy Nexus] musical_chairs:
New build up. Includes May security patch. We are still waiting for the CMA code to be merged to tuna (for more available RAM).

Enjoy!
[Samsung Galaxy Nexus] musical_chairs:
New build up, just because. Synced with CM, no big changes that I am aware of.
[Samsung Galaxy Nexus] Max Frost:
[MENTION=4531957]musical_chairs[/MENTION] Was this merged for the last build or still waiting ? Thanks
[Samsung Galaxy Nexus] musical_chairs:
It will be in the next build, just need to make sure I didn't miss any little details.
[Samsung Galaxy Nexus] musical_chairs:
New build up - now with CMA! What's that? Well, it's a kernel feature that allows memory for things like the camera and video playback to be freed up when it's not needed. The result is .97Gb usable RAM. AOSP tuna ROMs have had this for a little while, now we cm13 users can get in on the fun.

Also, I made some tweaks to the kernel config that may help with using thumb drives over USB OTG. Has that been broken? I don't have an OTG cable to test with. Any reports on that would be greatly appreciated.

Enjoy!
[Samsung Galaxy Nexus] GNAzi:
can u put another BT driver into last firmware because my BT headset(JayBird X2) doesn't work properly( - when i make call - i hear only system sounds like beep etc. but i can't hear my friend. Also he doesn't hear me. On my Moto X headset works correctly.

P.S.: i tried today and voice calls worked normally but my friend hear some noise((( Always
[Samsung Galaxy Nexus] musical_chairs:
New build up. Changes:

- Disabled ZRam. This fixes the 'unable to open camera' errors, and may help with lag over time.

- Set SELinux to enforcing - in preparation for official builds.*

- June security patch

Enjoy!

* Note for toroplus users: It's not unusual for toroplus's RIL to do some weird stuff with regard to SELinux, so radio-related bug reports are welcome.
[Samsung Galaxy Nexus] Cardcaptor_RLH85:
Does this mean that there will be official CM 13 builds for toroplus in the future?
[Samsung Galaxy Nexus] musical_chairs:
That's the plan. See this post. I see no reason why we wouldn't keep in line with maguro.
[Samsung Galaxy Nexus] ClintE1956:
SuperSU issue

First, I would like to thank the devs for making this rom! Looks like there is some life left in the Galaxy Nexus. Excellent job!

Using the built-in superuser, root apps work ok. Titanium Backup gives a message about possible issues, and I haven't had a chance to test that thoroughly yet.

I have read that flashing SuperSU via TWRP works, but I haven't had much luck with that. First I tried to install via Play Store, and got the infinite boot screen. Same after flashing with TWRP. Both attempts were after fresh wipes of everything and clean install of the rom & nano open gapps.

I'd really like to keep using SuperSU, as it's already paid for and I'm familiar with it. Does anyone have any suggestions on how to get SuperSU to work with a 32GB Sprint Samsung Galaxy Nexus?

Thanks to devs again, please keep up the great work!