yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] musical_chairs:
You're welcome!

TiBu is just being obsessive about root, you can safely ignore that warning. I've never had any issues with using it with the built-in root.

Regarding SuperSU, last time I checked, the builds for Android 6.0 (systemless root) were not with the regular downloads but were in a separate 'testing' section. A quick google turned up this site: http://www.supersuroot.com/

You probably also want to use the pico gapps, as nano is a bit bigger than it was when the Android 6.0 cycle started.

Edit: I just re-read your post. Downloading the SuperSU beta zip and flashing it via TWRP should work; allowing TWRP to install SuperSU on its own does not work, that will definitely break things.
[Samsung Galaxy Nexus] ClintE1956:
OK, just to make double sure I'm getting this straight... I should not allow automatic twrp supersu installation, of course. That's the one where twrp asks on reboot. But, I should be able to install latest systemless supersu beta via twrp without any boot image install, correct? None of the boot images on the supersu beta page are for toroplus, of course. It also says something about installing supersu after stock system install, but that shouldn't apply for this procedure.

And, I've just finished backing up entire system via twrp, so hopefully can go back to existing setup if something goes wrong.

thanks again!
[Samsung Galaxy Nexus] musical_chairs:
Yes, you are correct, that should work as far as I know. The SuperSU zip should automatically modify your boot image. It works on the aosp-based ROMs, I'm not sure if I've ever tried it on cm. But I don't know why it wouldn't work.
[Samsung Galaxy Nexus] ClintE1956:
Works great! All SuperSU functionality is working.

One thing concerns me, however. This phone has not been activated with Sprint for some time, as it's been a spare for us. I'm getting ready to activate it and wipe my daily driver GS3 for my wife's use, as she destroyed her S3's charging port by using the phone while charging, and getting that one fixed will be difficult.

Before flashing this supersu via twrp, I had a strong Sprint cell signal in status bar, even though there is no service currently activated for this phone. Now, the indicator is empty, indicating there is no signal. When I go into system settings -> cellular networks, all options are now ghosted. Could this be a potential problem? I was getting ready to activate the GNex today, as I need to have the good GS3 going by the end of the week for my wife's use. The SuperSU issue was pretty much the last thing to be done before starting daily usage of this phone for myself.

Thanks so much for your help on the holiday, extremely appreciated!
[Samsung Galaxy Nexus] tomm1e:
What's the best way to debug why LTE isn't working?

I tried reflashing the radios but that doesn't do anything, its something to do with the android RIL/data changes made after android 4.4.4

LTE still works on 4.4.4/CM11, but stopped when 5.0.1/CM12.1 was released

Only way I can think of finding out is to have monthly versions compiled ready to install, like from 2013-2014 (4.4.4-5.0.1) to round down which commit in core android caused it to break on toroplus
[Samsung Galaxy Nexus] musical_chairs:
Sounds like the radio isn't getting initialized properly. What does it say under Settings/About phone/Status/Sim status or IMEI information? If those fields are empty (or say N/A) then no, that's not good.

Also, activating the phone on a newer ROM like this one may be an issue. You may need to activate it on stock or a 4.4 or older ROM, then wipe and flash a newer ROM like this one. A wipe will not mess with the radio activation.

I would start by getting some good logs of LTE working properly on a few known good older ROMS, then getting some more good logs of LTE not working on 5.1 and 6.0. It would likely require somebody who knows the GNex's ril's pretty thoroughly to figure it out (that's not me btw.)
[Samsung Galaxy Nexus] ClintE1956:
Oh yes, I knew I'd probably have to backup everything then flash a stock rom to activate, as I had issues activating the GS3's until I figured that out. As you guessed, there are no populated fields and all imei info is unknown. I suppose if I have issues getting the Sprint connection working after activating on stock and then restoring the backup, I can just go back to the GS3. I could also restore the backup I made before installing supersu, when I had that cell signal strength meter in status bar, and see how that works.

I'll report back when I've tried out all this, and thanks again!
[Samsung Galaxy Nexus] ClintE1956:
Phone activated on stock KK (had to call Sprint of course, had to do that last time we switched something) and then restored with SuperSU beta installed. Sure enough, no cell signal, nothing in IMEI info etc. Went back to the nandroid backup I made prior to SuperSU beta install, and everything works perfectly.

Evidently something got changed when I flashed the SuperSU beta. Not sure how that would affect cellular connection with Sprint though.

Built-in CM root manager works OK, but I'd rather have SuperSU sometime. Maybe when they're done fixing things for MM...
[Samsung Galaxy Nexus] musical_chairs:
Glad to hear you got it working. I'll have to install SuperSU on my test phone and see if I can reproduce your issue. At the moment, I am trying to get BIP to work properly with SELinux, and it is not cooperating. The SELinux rule for it worked fine on cm12.1, and works fine on toro, but for some reason it gets ignored on toroplus. Once I get that figured out I'll look into what is going on with SuperSU.
[Samsung Galaxy Nexus] musical_chairs:
New build up. I put selinux back to permissive again while I try to iron out one last denial that just won't go away.

Edit: Includes July security patch.
[Samsung Galaxy Nexus] musical_chairs:
Another new build up. SELinux is back to enforcing again, I think I finally have everything straightened out there. Also synced with cm, no other big changes.
[Samsung Galaxy Nexus] musical_chairs:
Official cm13 nightly builds are rolling for the entire Galaxy Nexus family. I'll update the cm12.1 thread to reflect that once I have time. Official builds can be dirty-flashed over my unofficial builds.

You might want to wait until tomorrow's nightly to flash it if your phone is activated. I'm not sure that all the last-minute SELinux fixes made it into today's official build, so there may be RIL issues on this one.
[Samsung Galaxy Nexus] GNAzi:
after flashing off CM13 i had too much radio trouble(lost signal, probably rebooted radio i mean). Why? What can i do? Flash your old firmware upon newer(8/22/2016)?
[Samsung Galaxy Nexus] JohnCorleone:
When i heard that there were still new builds for this device, I knew that it had to be you still making the magic happen! I am excited excited about this device once again!!!

Sent from my Galaxy Nexus using Xparent Gray Tapatalk 2
[Samsung Galaxy Nexus] JohnCorleone:
You might want to try the latest nightly builds...I think they resolved the radio issues including LTE. I can't confirm it as I am no longer on Sprint and I use this device on WiFi only but I did read it in a few places
[Samsung Galaxy Nexus] musical_chairs:
As you saw, a new build is up. I'll add it to the OP directly. The flashlight tile should be fixed now, but if the camera is crashed it won't show up. I'm going to try a clean flash to see if I can reproduce the camera problem.

Edit: Bug confirmed, the camera is broken on a clean install of the latest build. For now, flash the 20150112 build, boot it up and open the camera, (it should show the preview), then go back into recovery and dirty-flash the 20150121 build. Obviously that's an ugly solution, but it'll have to do for now.

Edit 2: Just realized I uploaded the 1-12 build to the wrong folder on anroidfilehost, here's the link: https://www.androidfilehost.com/?fid=95897840722641256
[Samsung Galaxy Nexus] musical_chairs:
Ok, here's the deal with the camera (aka, how I goofed it up on the last two builds): Our devices have camera calibration data stored in them. In the good old days, this was read by a binary called fRom. Enter Lollipop with its added secutiry features, and old binaries (non-PIE binaries) no longer are allowed to run. When MWisBest first got the GNex cameras working with the DDK 1.9 drivers, he used an old camera HAL and it didn't care if it had calibration data or not - sure, the pictures were yellowish on a lot of devices, but hey, it worked. Recently, MWisBest fixed things so the stock camera would work. In the process, he moved to a newer camera HAL. One of the side effects was that now, the camera completely crashes if it can't find its calibration file. On the 1-12 build, I had successfully (with a tip from Ziyan) managed re-enable non-PIE support so fRom could do its thing and read the calibration data for the camera. On subsequent builds, I managed (completely on my own) to break that again.

So, on the 1-12 build, fRom reads the calibration data and writes it to the file system. On a dirty-flash of newer builds, the calibration data is still there, so the camera works. But on a clean flash of the latest build, there's no fRom and no existing calibration data, so there's no camera.

The really good news in all this is, Ziyan has managed to reverse-engineer fRom. Now, we can get our camera calibration data safely and securely and without all that hassle. And, I have an excuse to do another build.
[Samsung Galaxy Nexus] musical_chairs:
New build added to OP. Camera stuff should be fixed now, thanks to Ziyan.
[Samsung Galaxy Nexus] thelgog:
so just flash the newsest build and ill have a working camera
[Samsung Galaxy Nexus] PeterFlinstone:
Has anyone managed to exit of a pinned app? I tried 3 times, but the back + overview touch and hold function won't work. I had to do a soft reboot to get out, Can someone try and see if itll work, or it's only me?
[Samsung Galaxy Nexus] musical_chairs:
I had to google 'pinned app' to figure out what you were talking about...but yes, I did manage to un-pin an app. At first it didn't work, like you described, but then I noticed that the status bar was appearing when I held back and overview. I was able to swipe down on the status bar, and from there, the home button worked. Now that I did that once, pinning and unpinning seems to work correctly.
[Samsung Galaxy Nexus] PeterFlinstone:
Ugh, Appears to be that the problem was only on the 12-01 build , because in the 25-01 it's fixed. The only thing was that in order for me to upgrade, I had to do a Factory reset (CM wouldn't let me pass the WiFi screen) so problem solved , thanks for the quick reply. Cheers!

PS.: CM should do a pure black version of the boot animation …
[Samsung Galaxy Nexus] yotvb531:
I think the MNC might be set incorrectly on the toroplus version. I think it might be set for Verizon, though 3G seems okay with Sprint. I couldn't figure out if there's a place to set that though inside the ROM or if it has to be done before the build.

I tried manually adding a Sprint APN but if I classify it as MNC 120 (Sprint) it disappears in the main APN screen. If I do a Reset to default, usually only one Verizon APN shows up. Although just now a long list of Sprint ones showed up...it's really weird.
[Samsung Galaxy Nexus] musical_chairs:
I think the MNC is read from the radio. If there is a place to set it in the ROM or even before the build, I have never found it. You can, however, use the MVNO settings at the bottom of the APN edit screen to specify an MNC other than default (I used this on KitKat to get MMS working on Page Plus, which needs a Verizon MNC.) But it does seem that something is up with the APN's on toroplus.
[Samsung Galaxy Nexus] poo706:
Does liquid do the same thing?

[poo]
[Samsung Galaxy Nexus] yotvb531:
Yep. I just did a clean flash to check. It seems like the preferred network type menu setting might be partially to blame. Without touching anything in the APNs there was a list of Sprint entries until I selected 3G in that preferred network type menu. Then they switched to Verizon entries.
[Samsung Galaxy Nexus] musical_chairs:
New build added to OP (20150201). Nothing special was added on my end, just synced with the latest CM goodness (and otherwise...)
[Samsung Galaxy Nexus] yotvb531:
Yes, no more flashlight boot animation! :) And more CM settings that I love are starting to show up (expanded desktop, more quick setting toggles).
[Samsung Galaxy Nexus] musical_chairs:
New build added to OP (20150214). Happy Valentine's Day!
[Samsung Galaxy Nexus] SuperGoober:
Hi , any particular recovery you recommend for the Nexus Toroplus ? I'm currently on 6.0.4.3 CWM . Is that suitable for flashing L ? If I need to change recovery I thought I might give TWRP a spin . The only way I know to change recovery on this device is to hook it up to the pc and use wugfresh toolkit unless there's a new easier way . Any comments , suggestions and advice appreciated . Currently running 4.4.4 kk . Thanks.
[Samsung Galaxy Nexus] musical_chairs:
I haven't done any research into recoveries, so I can't make any recommendations. I will say though that I use and like TWRP. I find it easiest to install it using a USB cable and fastboot, as described in the "Download - Recovery Image Method" section on the official page: http://teamw.in/project/twrp2/92
[Samsung Galaxy Nexus] SpideyTheMan:
[MENTION=4531957]musical_chairs[/MENTION]

I installed your Valentines Day build of CyanogenMod 12.0 Beta for Sprint Samsung Galaxy Nexus. I'm amazed at the overall responsiveness of this Lollipop ROM. It's now my daily driver. This build is quite stable and runs all of my usual apps perfectly. Working on enabling LTE but 3G will do for now. I'm simply enjoying Lollipop! Thanks for the effort to get this ROM going!
[Samsung Galaxy Nexus] SpideyTheMan:
Off-Mode Charging does not work in Lollipop

Off-Mode charging doesn't appear to work properly in Lollipop. I've tried all of the current ROM's in development for the Sprint Samsung Galaxy Nexus and noticed the following problem with charging the phone while it is powered off. The usual battery charging animation doesn't show. I see a battery with a lightening-bolt and the phone just stays there and never progresses to the battery animation. Essentially the phone freezes at this point.

Any of the following will recover from this issue:

1. Removing and re-installing the battery with the charging cable removed allows the phone to be powered on and then charged by reinserting the cable.

2. Holding down the power button for 8-10 seconds with the charging cable removed to force a reboot.

3. Disabling off-mode charging by executing "fastboot oem off-mode-charge 0".

I decided to disable off-mode charging until this issue is resolved. This causes the phone to automatically boot up anytime the power cable is plugged in and the phone is already powered off.

Anyone else notice this issue?
[Samsung Galaxy Nexus] musical_chairs:
Yes, that's unfortunately been an issue from the beginning, it's present on toro and maguro as well. So far nobody has succeeded in tracking it down.
[Samsung Galaxy Nexus] musical_chairs:
New build posted in OP. Enjoy!
[Samsung Galaxy Nexus] SpideyTheMan:
Working well. Thanks. A few things that I can report after using the latest build:

1. I'm seeing the cellular data rate report 1X in the status bar but in the pull-down shows 3G. Actual data rate appears to be 3G so the cellular data rate in the status bar isn't always reported correctly. Minor cosmetic issue. This happened occasional in prior builds.

2. Most apps seem to pause while running in the background. I can see this behavior with Google Play and in general I appear to be missing occasional push notifications from e-mail apps. I've seen this across all of the Lollipop builds. Push notifications seem to be a hand-off issue with a sleeping phone, cellular, and wifi data. Something just isn't going as well as it should to keep apps responding while the phone is sleeping. When transitioning between wifi and cellular I often get a lot of push notifications all at once when cellular data comes online.

3. As with most CyanogenMod and 3rd party ROM builds Netflix just spins forever and Google Play Movies doesn't appear to work and instead generate the error "Playback isn't supported." Trailers on Play Movies work fine.

Nice and fast Lollipop ROM.... the latest Google Chrome Beta even seems to be a little snappier too....
[Samsung Galaxy Nexus] musical_chairs:
A new build is up, just because. It's an update for the sake of an update.
[Samsung Galaxy Nexus] PeterFlinstone:
So, there's only minor bugs with GNex. Sweet
[Samsung Galaxy Nexus] SpideyTheMan:
Thanks for the frequent build updates! I keep running your builds as my daily driver. So far so good....

---------- Post added at 04:47 AM ---------- Previous post was at 04:26 AM ----------

Don't forget to update the "latest build" link as you upload newer builds. The latest build is currently set one build older "cm_toroplus-ota-20150228.zip". To download the most recent build then we go to all builds and select "cm_toroplus-ota-20150301.zip" or whatever is newest at the time...

Thanks again for all of your work on this. We really appreciate it!
[Samsung Galaxy Nexus] musical_chairs:
Well actually the 3-01 build is not completely tested, that's why I didn't post the link to it yet. I attempted to pull [MENTION=1048318]zzpianoman[/MENTION] 's fix for in-call mute. It built okay, but in-call mute doesn't seem to actually work. I haven't had time to play with it since uploading that build. If anybody wants to see if they can get in-call mute to work (maybe wiping data on dialer and related apps), feel free to post back what you find. Otherwise, I'll work on it again next week.
[Samsung Galaxy Nexus] zzpianoman:
Did you remember to add ro.telephony.legacy_mute=1 to build.prop?
[Samsung Galaxy Nexus] musical_chairs:
I think so - you have three commits on your github:

https://github.com/zzpianoman/andro...mmit/1e18c7ca543ad8e109efcaaac18acb660de2ecee

https://github.com/zzpianoman/andro...mmit/9782be6303846d7f5241757d9dcc23d8651c5ebc

https://github.com/zzpianoman/andro...mmit/1602997c0c6f7802f916ba1e1eb6e917fb00d646

...and the third one is the build.prop flag. Like I said I haven't really dug into it, it's being a very busy week.
[Samsung Galaxy Nexus] musical_chairs:
New build is up. It includes a memory management tweak from Ziyan and a dark 'Android is Upgrading' splash thanks to zzpianoman. Also included is zzpianoman's In-Call Mute fix, which I unfortunately still have not gotten working.
[Samsung Galaxy Nexus] SpideyTheMan:
New build is working great for me! I decided to get rid of the Microsoft Outlook app for Android which seems to be where some of my push problems were coming from. I also uninstalled ClockworkMod RomManager which was the source of some slowness I have been seeing recently. Now everything is working well. I'm not seeing any more problems with the radio in the status bar shows 1X instead of 3G on the latest build.... I'll need to run it a few more days though...
[Samsung Galaxy Nexus] musical_chairs:
New build up. Two 'big' fixes this time:

1. In-call mute works, thanks to [MENTION=1048318]zzpianoman[/MENTION]. As he said when he released his rom with this fix:

2. Offmode charging works, thanks to a fix from [MENTION=3390093]MWisBest[/MENTION]. He makes this stuff look so easy...

Note: I know we're all excited to try Android 5.1. [MENTION=3390093]MWisBest[/MENTION] has already released a build of it, and [MENTION=2633638]Ziyan[/MENTION] is feverishly working on it, I've decided to wait a bit. If CyanogenMod is extra-slow in merging it, maybe I'll do a toroplus build of zmod-5.1.
[Samsung Galaxy Nexus] SpideyTheMan:
Many thinks for the work on a solid build! It looks like some of my latest issues were related to me mistakenly installing the SuperSU 2.46 ZIP update on top of CyanogenMod 12. I didn't realize that SU features were already a part of CyanogenMod 12. To say the least it caused all sorts of odd performance issues. I finally wiped /system and only installed the 12 build and pico pa gapps. Fast and responsive again...
[Samsung Galaxy Nexus] SpideyTheMan:
Hey! Netflix and Google Play Movies & TV apps are now working. Off mode charging working perfectly too. In-call mute is good. Your build quality is exceptional. Looks like CyanogenMod 12.0 is never going to reach release and instead work will progress on a CyanogenMod 12.1 release based on Android 5.1.
[Samsung Galaxy Nexus] highzircon:
Been running this as my daily driver with no problems for over a week great job! Thanks man I don't want to let my Gnex go :D :D :D :D
[Samsung Galaxy Nexus] SuperGoober:
Video

Yeah , this rom is running great . nice work .
[Samsung Galaxy Nexus] Cardcaptor_RLH85:
I installed this ROM yesterday and it's been nice to have Lollipop on my Galaxy Nexus except for one major issue. I don't get a mobile data connection at all. No 1xRTT, no 3G and no LTE. I made sure that my Profile and PRL were updated but, still nothing. Is there a particular step that I have to perform with this ROM in order to get mobile data working for me? I'm comfortable rooting about in obscure APN settings but, I do prefer being told what I should be looking for so that I can avoid breaking things.

Thanks for the assistance ^_^
[Samsung Galaxy Nexus] musical_chairs:
New build up. Not much to mention here, just the usual gradually improving goodness. Have fun!

I'm not sure what to say - the toroplus I use for testing isn't activated, and even when it was it was on Page Plus, so data activation wasn't the same anyway. You could maybe try an older build, just in case something in CM's recent changes is causing breakage. If an older build works, try dirty-flashing to the latest build. But those are just guesses. Maybe one of the users who has working data can chime in.
[Samsung Galaxy Nexus] SuperGoober:
I installed for the first time a few days ago , My 3g has worked great and I'm on an mvno . haven't touched the apn's . What carrier are you on ? I don't have access to LTE . Did you come from another rom or straight from stock ? I had data on Vanir 4.4.4 when I flashed this and had data afterward . Your not on Boost are you ?

[MENTION=5516338]Musicalchairs[/MENTION] Hi , Rom has ran superb . I just need to ask you about the Google Play Services keep awake issue that most all of the roms encounterd lately that causes mega battery drain . Does this new build

include theres new cm commits to address the issue ?

http://review.cyanogenmod.org/#/c/91579/ and http://review.cyanogenmod.org/#/c/91021

These mentioned here https://plus.google.com/101904461094056235916/posts/Rt4agpDbmvA

Also I don't know if its just me so if you or anyone else can chime in , My ringer volume seems about half as loud as it should be and I have it turned to full volume but when the phone rings it's not very loud , sounds about like 50 % . Any ideas ? Thanks for your great work in bringing us this rom .
[Samsung Galaxy Nexus] Cardcaptor_RLH85:
I did notice elsewhere in the thread that your dev device wasn't activated so I was hoping to get a response from others but, thank you for your fast response and also for making this ROM. I'm not a big fan of planned obsolescence for smartphones and the ROMming community has helped me keep this one around for a while.

I did come from another ROM (PA 4.4.4 to be exact) but, I had 3G and LTE in that ROM and I completely wiped before coming here from there (I used device encryption so /data had to be completely cleared). Also, I'm a Sprint user and my brothers HTC M8 (also on Sprint) has full 3G and LTE service in the areas that I frequent.