yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] musical_chairs:
I was wondering that too. If you activated your phone/sim on stock or a kitkat ROM, then my guess is that something is up with SELinux. I have been seeing an ril related SELinux denial in the logs, but since radio functions have been working almost perfectly for me, I figured it didn't matter. (If I set SELinux to allow what ril wants to do, it violates the neverallow rules which breaks the build. Samsung - sigh...) If you clean flashed the latest build of this ROM, it's feasible that you could bump into a situation that I might not see since I almost never clean flash.

If you could grab a logcat and a dmesg, that might give some clues.

Another thing you could try is to flash the previous build, where SELinux is still set to permissive: https://www.androidfilehost.com/?fid=24566459652898991

Edit: Or, you could set SELinux to permissive shortly after boot-up and see if that helps your cell signal drop issues.
[Samsung Galaxy Nexus] normanx:
Hello Musical chairs, here is my issue, I was able to install your latest build and its all up and running, but if I install nano gapps and reboot it sits on the blue robot for a bit, then says its optimizing apps, then starting apps, then back to the blue robot...what am I missing? im using cwm touch as my recovery.
[Samsung Galaxy Nexus] quickdraw86:
You should probably be using MC's TWRP at this point, and nano is too large for toro on 6.x unless you modified the open gapps installation with a gapps-config.
[Samsung Galaxy Nexus] normanx:
I got it all working, it's very cool and fast. Thanks for the info
[Samsung Galaxy Nexus] SuperShadow1021:
How is everybody battery life on this? I am just using it as a music streaming device at work currently. And the battery seems to drain way too fast. Also, does this have busybox built in or do i have to install it once i have it running?
[Samsung Galaxy Nexus] AceNJ:
the battery drain seems excessive for me as well but honestly at this point I think it's just the battery age showing. consider how old yours is?
[Samsung Galaxy Nexus] normanx:
The battery drain is fast on mine also, but I'm a heavy user also. I had to install busybox on mine.
[Samsung Galaxy Nexus] wilsonfishk:
I have the same issue (standby with airplane mode "on" is currently clocking >300 mAh). I installed busybox on top too, but doesn't seem to improve battery life. I initially did a dirty flash, but after reading up here, tried clean flashing too. Battery is old, but was giving me at least 2 days on standby (stock android 4.4).

Regardless, heartfelt thanks for your work on this. It's AMAZING that this phone is still being supported and upgraded by the community.
[Samsung Galaxy Nexus] musical_chairs:
cm13 has toybox, which is good enough for most basic purposes. If you need full busybox functionality, you'll need to install it.

Regarding battery life, it is great for me on standby and decent for phone calls, but drains pretty quickly when browsing the web or playing games.
[Samsung Galaxy Nexus] normanx:
Have you played around with trickster mod any? Recommend any good settings?
[Samsung Galaxy Nexus] musical_chairs:
New build up. Includes July security patch. Also addresses a few minor SELinux denials I was seeing. Enjoy!
[Samsung Galaxy Nexus] normanx:
The only thing I have come across on this rom is the way radar images look on two separate radar applications of mine. They look very digital when you zoom in instead of flowing. If that makes any sense.

I went back to CM10 to see if it was something the app developer did and it was perfect.

Any ideas?
[Samsung Galaxy Nexus] musical_chairs:
Another new build is up. It includes some more minor SELinux fixes. Also synced with cm. No other big changes.
[Samsung Galaxy Nexus] kb8no:
This ROM says Toroplus and not Toro. Does that matter?
[Samsung Galaxy Nexus] musical_chairs:
Sorry. Yes it does matter, I accidentally grabbed the wrong one. It's fixed now.
[Samsung Galaxy Nexus] AceNJ:
did a dirty flash update from the june baseline; looks fine so far. thanks!
[Samsung Galaxy Nexus] Theseus718:
Thanks!

I just broke the screen on my S5, so I'm using my Nexus before my next contract renewal. I couldn't believe the performance increase when I flashed 6.0.1 Cyanogen to it! Major battery increase, no homescreen lag, and many apps run smoother. I wouldn't play any current games on it, but damn this will make my four month wait for my next phone painless! Thanks for developing this mod for such an old phone, you're a hero.
[Samsung Galaxy Nexus] kb8no:
Any links for us? Can't find anything on CM site?
[Samsung Galaxy Nexus] quickdraw86:
http://download.cyanogenmod.org/?device=toro
[Samsung Galaxy Nexus] kb8no:
So has the mantle been passed over to Official CM from this thread and further development will occur there?
[Samsung Galaxy Nexus] musical_chairs:
Yes. All further development will be done through cyanogenmod's gerrit. Unless, of course, something gets badly broken that's not readily fixed in our device trees. But hopefully we are beyond that stage with cm13. I'm not sure yet how I want to structure the threads here for discussion, but things are quiet enough these days that it probably doesn't matter.
[Samsung Galaxy Nexus] kb8no:
So your role has changed to being a developer / contributor to the official CM gerrit? The latest new builds will now be found as CM nighties and not on the OP? For now this is the only discussion thread for the new official CM13 or is there any other place?
[Samsung Galaxy Nexus] alfick3:
So will this new official one also work on Toro?
[Samsung Galaxy Nexus] kb8no:
That's for sure. This Unofficial CM has been merged into the Official CM nighties. Remember to look for Google Galaxy Nexus / Toro build on the CM site. The link is above. (I was looking in vain for Samsung Galaxy Nexus.) Because I like to understand, I'm trying to figure out how musical_chairs ties into this merger and his role with the Official CM. I've been using his builds for a long time.
[Samsung Galaxy Nexus] musical_chairs:
I've been filling that role for quite a while. I'm not an official maintainer, but most of the fixes for toro and toroplus come from me. The latest builds will be the nightlies, not posted in the OP. I hope to get a proper official cm13 thread up this weekend.

Yes, there are official builds for all three variants. Make sure you download the build for toro, the cm builds are not unified like the aosp builds.
[Samsung Galaxy Nexus] musical_chairs:
Ziyan is our official maintainer, and he asked me a while back if I could push my stuff to gerrit so he could turn on official builds for cm12.1. Since then, I've been working mostly using gerrit and less and less using my own github. The only non-cm code remaining in my unofficial builds has to do with the 'optimizing apps' screen - on mine it's dark with no spinner, on cm it's white with spinner. Other than that, the nightlies are identical to my builds.
[Samsung Galaxy Nexus] kb8no:
Anybody. There has been a problem with initiating new Verizon SIM cards with Kitkat and Marshmallow forcing us to install way back versions to get the SIM working on the device. When the SIM is initiated on an old build and is working, then we flash the new current version and everything works again. Is this still an issue on the new official builds? Can the Official CM 13 properly initiate a new SIM?
[Samsung Galaxy Nexus] musical_chairs:
I don't think so, but I don't have any new sim cards to test.

I bumped the cm-12.1 thread to cm-13.0, I guess the nightlies should be discussed there now.
[Samsung Galaxy Nexus] kb8no:
Link please please.
[Samsung Galaxy Nexus] musical_chairs:
http://xdaforums.com/galaxy-nexus/verizon-develop/rom-cyanogenmod-12-1-t3361656
[Samsung Galaxy Nexus] traco1:
Well now I've finally done it .I have been using this Lollipop. Everything was great , then I got an CM update to the 8/12/16 nightly. It has some problems & google services don't work . Tried to go back to restore point & won't let me . I noticed in TWRP the partisans are /dev/ blocked . SU isn't working & now it boots only into recovery & won't do anything .Computer can'y recognize it, so I can't sideload.

Any suggestions????
[Samsung Galaxy Nexus] traco1:
Ok so far I am able to get into the cmupdater recovery but the Rom won't finish a boot .It starts up the apps in optimization the recycles at the boot screen. If I wait long enough it will go back & try to load apps . I think the problem might be with not being able to wipe cash & dalvick but not sure . I have got the JB4.2.2 firm ware & could try that with Odin3 but concerned that might just muck it up worse.

Not sure where to turn ??
[Samsung Galaxy Nexus] musical_chairs:
Is your USB cable or port bad, or are you just unable to communicate with it via adb?

So you used to have TWRP recovery and now you have cmupdater recovery? How did that happen?

If I were you, (provided your USB port isn't shot), I would boot to fastboot (power off, hold down volume up+volume down+power button), and flash TWRP recovery from there. You can use my unofficial TWRP build, link is in the OP.

fastboot flash recovery name_of_image.img

Then boot into recovery, and you should be able to do what you need to do.

Regarding the Google Play Services issues, did you flash the proper gapps for marshmallow? (opengapps pico or equivalent) Remember, gapps need to be flashed after flashing the ROM but before booting into it due to the permissions layout in marshmallow. Once the permissions get messed up, the easiest way to fix it is to wipe everything and start over. There nay be other ways, but I never had time to dig into that issue.
[Samsung Galaxy Nexus] traco1:
Good Now

When the cm recovery screen came up I had never seen this screen . I usually install with TWRP so didn't know how to use the settings. Did not wipe cash or dalvik . Then the Rom settings looked wrong . After I played with the recovery ( at that point nothing to lose )I figured out how to get back on track . I had managed to download the latest 12.1 before it completely crashed & I installed that.. I did notice as I deleted the nightly downloads that the were for 13 & not 12.1 even though I had been sent the updates ready notice that they were updates for the 12.1 rom .Which is what threw me off. Flashed the pico gapps after it was up & works great now.

I would like to thank you for your response to help me . Much appreciated .
[Samsung Galaxy Nexus] traco1:
I have a question on the Lollipop builds. Latest build on OP is 3/03 yet if I go to the all downloads page I can see there are later builds . I want to make sure I don't have another screw up on my phone so are the builds after 3/03 do not have any major changes that make a difference ? How can I find what changes were made in those files ?
[Samsung Galaxy Nexus] musical_chairs:
Builds newer that 3/03 are Marshmallow. I wasn't doing a very good job of labeling things back then. You should use the official cm12.1 snapshot if you want a newer build of Lollipop. It can be dirty-flashed over my Lollipop builds.

http://download.cyanogenmod.org/?device=toro
[Samsung Galaxy Nexus] traco1:
Hey I have a question. (only asking here because it happened with this rom ) When I reboot into recovery will the CM recovery always boot up or will it boot to TWRP ? Now I have TWRP re-installed ! And if so can I change it so it will boot into TWRP ?
[Samsung Galaxy Nexus] musical_chairs:
It will boot into TWRP, at least it does if you use the 'advanced reboot' option that is turned on through developer options, or if you use 'adb reboot recovery' or some other terminal command option. Just make sure that 'Update Cyanogen recovery' is turned off (it's on Developer options), and you'll stay on TWRP.
[Samsung Galaxy Nexus] traco1:
If every thing is working now on the 13 build. I might have to try it again. Last time I flashed it seemed like it was working hard .The phone was not as smooth as Lollipop build . Even after up for a week or two.
[Samsung Galaxy Nexus] Colen1b8:
Unable to use SIM card

Whenever I flash the ROM to my phone with the gapps, everything run exactly like it should- except when it does see my SIM card it says "No service" and I think I found the problem. I use Page Plus, which runs off Verizon, and I had been downloading Toroplus which is for sprint right? So I thought I just had downloaded the wrong version, and got Toro. But whenever I go to flash it, I get an error message about not being able to flash it because I'm running a toroplus phone.. Could this have to do with me having flashed a toroplus version of the rom first? Also, I'm using TWRP, should I try CWM or something?
[Samsung Galaxy Nexus] musical_chairs:
Please use TWRP, who knows what CWM will do with a marshmallow ROM.

But which phone do you actually have? Toro or Toroplus? Toro has a SIM card slot and it's model number is SCH-i515. Toroplus has a built-in SIM and is model SPH-L700. You seem to have TWRP for toroplus, which would explain why it will only let you flash toroplus ROMs. If you actually have a toro, you'll need to first install TWRP for toro, then you'll be able to flash ROMs for toro.

It is indeed possible to use both toro and toroplus on Page Plus (We have one of each here, both work well). Toroplus took a good bit of hacking to get going on Page Plus, but I did that back in the days before Page Plus had 4G SIM cards.
[Samsung Galaxy Nexus] Colen1b8:
It indeed was me having TWRP toroplus, and I got the toro version (and got 2.1.2 or whatever at first, and that didn't flash cm 13, I had to get 3+) but yeah, I had finally figured it out. Honestly, I wish I had just waited for a response, because it was really such a simple solve but took me so long to fix. However thanks for the response! Loving the XDA forum so far.
[Samsung Galaxy Nexus] hexhead:
OK thanks, I'll give it a try
[Samsung Galaxy Nexus] musical_chairs:
New build added to OP. The flashlight toggle is fixed, though HW video playback may be broken now.
[Samsung Galaxy Nexus] hexhead:
Just flashed it. There isn't a flashlight toggle in my quick settings, and there isn't a built-in camera in the app drawer (although it shows up on settings/apps). Maybe I need to start with an earlier build and dirty-flash to the current?
[Samsung Galaxy Nexus] musical_chairs:
I've been dirty-flashing. Sounds like I need to do a clean flash and see if I can reproduce the problem.

Edit: Confirmed, the camera is buggered on a clean flash of the latest build(s?). It works though if you clean flash the 1-12 build, boot it up, open the camera (you'll see the preview), then go back into recovery and dirty-flash 1-21. Obviously that's a yucky workaround, but it'll have to do til I can figure out what is up.
[Samsung Galaxy Nexus] hexhead:
That did the trick, thanks so much.
[Samsung Galaxy Nexus] hexhead:
So far this ROM is running great. I flashed it just to kick the tires, but everything I've tried works and its very smooth. Looks like I have a new daily driver. Thanks [MENTION=4531957]musical_chairs[/MENTION] for putting this together.
[Samsung Galaxy Nexus] johnston9234:
Any thoughts on the lag for anyone else? I can't use Chrome at all with the way the ROM is working atm. I think it isnt specific to this ROM though, all of the 5.0 roms I have tried are really laggy with Chrome and Google Music.
[Samsung Galaxy Nexus] bsmitty83:
You can mess with chromes settings by typing "chrome://flags" as a URL
[Samsung Galaxy Nexus] musical_chairs:
New build added to OP. Camera stuff should be all fixed up now.

Also included is CyanogenMod's new LP boot animation. If you haven't had an excuse to use 'themes' yet, this will give you one...
[Samsung Galaxy Nexus] christianpeso:
Any reason why the boot animation only appears in the center of the screen and not the whole screen?
[Samsung Galaxy Nexus] musical_chairs:
That would be because of this commit:

https://github.com/Ziyann/android_d...mmit/ad7abf688821d71d871fa629eba135bee11739f1

(Actually, an equivalent local commit in my toro device tree, I don't have a github account)

The boot animation has always been smaller than the screen since we first got Lollipop, it was just black around the edges so we never noticed.

Edit: I haven't actually tested whether or not this commit is necessary, I was just copying Ziyan.
[Samsung Galaxy Nexus] poo706:
With LS, the boot animation is super slow at full screen. I took the height down to 640 just to get it tolerable.

[poo]
[Samsung Galaxy Nexus] zzpianoman:
I just switched mine to stock. Works flawlessly!

EDIT: back when I ran LS on KitKat, I would always change the bootanimation. It was just way too flashy and involved for my tastes. I prefer a more minimalistic approach.
[Samsung Galaxy Nexus] poo706:
Stock LP or CM? I've never had a problem with LS's boot ani's per se, but they've always been jerky on the gnex. It was the only ROM that ever did that to me and I never knew why.

[poo]
[Samsung Galaxy Nexus] zzpianoman:
Stock Lollipop. I think it's pretty cool IMHO. I've switched to a dark theme with the dark cyanogenmod bootanimation and that one looks pretty nice too. I was having issues with the CM bootanimations being jerky as well and the only way I could fix it was by running their half-res script on the 720p bootanimation to get a slightly reduced file size. In the end I just replaced it with the stock bootanimation and called it a day. In my testing, it seems that 1.5MB bootanimazion.zip files are the sweet spot for the GNex. Anything larger than that results in jerky, non-fluid animations.
[Samsung Galaxy Nexus] musical_chairs:
While we're on the subject of boot animations, here's one option for anybody who actually likes the new cm animation and wants it full screen:

http://xdaforums.com/showpost.php?p=58441174&postcount=1257
[Samsung Galaxy Nexus] zzpianoman:
Is it really that white??? Geeze.
[Samsung Galaxy Nexus] Christopher8989:
The vibration on touch is intermittent for me and sometimes it's late to the touch. It also weak despite setting to 90 or 100 with TricksterMod
[Samsung Galaxy Nexus] poo706:
You can crank it up higher than that, it's not a percent.

[poo]
[Samsung Galaxy Nexus] Christopher8989:
Well didn't know thanks
[Samsung Galaxy Nexus] musical_chairs:
20150201 build added to OP.
[Samsung Galaxy Nexus] christianpeso:
Does this ROM support f2fs?
[Samsung Galaxy Nexus] musical_chairs:
No, sorry.
[Samsung Galaxy Nexus] christianpeso:
No prob. Was just curious. Thanks!
[Samsung Galaxy Nexus] musical_chairs:
20150214 build added to the OP. Synced with the latest CM changes.
[Samsung Galaxy Nexus] christianpeso:
Any idea on how to get Trusted Face included to unlock phone with our face?
[Samsung Galaxy Nexus] Zen_Man:
This is due to flashing the Pico modular package. The smallest gapps package that has face unlock is the Micro modular package and we probably don't have the room to flash that one. Probably can do it another way.
[Samsung Galaxy Nexus] Zen_Man:
Thanks for this ROM, I can't wait for your next update!
[Samsung Galaxy Nexus] musical_chairs:
New build is up. Though I gotta say, the 2-14 build ran well enough that I wasn't in a huge hurry to change. Anyway, enjoy the update!
[Samsung Galaxy Nexus] Bstsms:
I am enjoying your work and the cm12 ROM works surprisingly well on my phone. Thanks for the continuing G-Nex support.
[Samsung Galaxy Nexus] past_pluto:
The 2/14 was my daily driver for lollipop roms but something would keep me from deep sleep till I wiped catch. Which is weird cause with liquid lollipop and same apps I didn't have same issue.
[Samsung Galaxy Nexus] ageerdes:
I get no deep sleep when charging via USB. It isn't really an issue, though.
[Samsung Galaxy Nexus] zzpianoman:
This is normal behavior.....the phone can not charge if it is in deep sleep.
[Samsung Galaxy Nexus] ageerdes:
When charging via AC the phone does not remain awake. As I said, not a big deal because this rom is running great and I personally don't care about a USB charging bug as little as I use that particular feature. But, look at battery usage when charging via USB vs AC. Mobile radio active goes nuts too. I've tried and tried to solve it, but don't care anymore so gave up. Too many other things work perfect for me to care. Great work, man.
[Samsung Galaxy Nexus] obsidianchao:
Changelog on new build? 2/14 is running fantastic, just wondering if I should dirty flash ASAP or wait until I get around to it.
[Samsung Galaxy Nexus] musical_chairs:
No special changes on my end, just synced with Cyanogenmod.
[Samsung Galaxy Nexus] Zen_Man:
My mute button isn't working in calls. Anyone else having that problem?
[Samsung Galaxy Nexus] zzpianoman:
I have a fix for the in-call mute problem that I'm in the final stages of testing. Apparently call-waiting doesn't work either, which I actually just found out during my testing procedures.

I guess no one actually uses their phones to make calls anymore, so these bugs don't get noticed right away.
[Samsung Galaxy Nexus] musical_chairs:
I was just getting ready to post that [MENTION=1048318]zzpianoman[/MENTION] is working on this.

And I do use my phone (yes, my toro is my main phone) to make calls, several calls a day actually. Though I never use mute or call waiting.
[Samsung Galaxy Nexus] zzpianoman:
Yeah....call waiting is extremely broken right now.

Android has made some HUGE changes with how the device handles calls - and it's actually making for some pretty frustrating work on my end. A lot of the changes don't even make very much sense to be honest. Instead of having a single app (called Phone) to handle calls, it's actually now broken up into 4 different ones (TeleService, Telecom, inCallUI and Dialer) and each one works differently with the telephony framework. TeleService handles all of the communication between the software phone and the radio, and Telecom handles the actual placing and routing of phone calls - as well as receiving all of the in-call events such as mute and speakerphone.

Mute and speakerphone used to be handled exclusively in TeleService, but it is now handled through Telecom which does NOT have access to the system's hidden RIL interface. Our devices are only able to handle mute requests through the radio, which Telecom does not have direct access to.

So what I have been working on is essentially bringing back the old setMute function in TeleService, so the mute requests can be passed off to the radio where they belong. Everything was on track until I discovered that call waiting doesn't work - so now I'm trying to fix that as well. (All of this stuff is kind of related).
[Samsung Galaxy Nexus] musical_chairs:
Well, a new build is up, just because. Nothing noteworthy to note that I know of, just an update for the sake of an update.
[Samsung Galaxy Nexus] past_pluto:
I'm going to toggle off wake up device on charge and see what that does although the deep sleep issue was happening without charging. I'm back on this rom. Too hard to stay on kk now. Love the design of lollipop!

I'm also using Viper4android too.
[Samsung Galaxy Nexus] obsidianchao:
Still loving the hell out of this ROM. Themed with Antares, icons from Flippy, Nova Launcher, and a good few xposed modules keeping everything the way I like it.
[Samsung Galaxy Nexus] musical_chairs:
New build up! Includes a memory management tweak from Ziyan and Dark Material theme on the 'Android is Upgrading' splash from zzpianoman. Also included is the in-call mute fixes from zzpianoman, except I still haven't gotten them working yet.
[Samsung Galaxy Nexus] Alton (Halo 2):
This rom makes my Gnex new again lol
[Samsung Galaxy Nexus] obsidianchao:
Totally unrelated to the ROM, but do any of you have recommendations for an extended battery? CM12 eats this phone for breakfast and I get like ~6 hours of usage max.
[Samsung Galaxy Nexus] musical_chairs:
That's why I build ROM's - so I can have a 'new' phone as often as I want. :D
[Samsung Galaxy Nexus] chetplease:
thanks

thanks for the work you do. Toro is my only phone too, and kind folks like you are its life support.
[Samsung Galaxy Nexus] Zen_Man:
First off I want to say great work and thanks. I like that now I can tell that mute isn't working because the button doesn't stay pressed like it did before. Progress!