yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] WhiteWidows:
Has anyone got data to work with freedompop? I used the Change APN app to change to freedompops apns instlled the meggaing app, updated prl. No data. Baseband is GA02

##edit##

I got 3g. I take it lte is not working?
[Samsung Galaxy Nexus] musical_chairs:
Right, no LTE. I can't even test LTE on toroplus due to the way mine is activated, so I'm not much help on this one.
[Samsung Galaxy Nexus] SuperGoober:
Any chance of a new build with the latest CM goodies :) ? Actually craving something to flash hehe :eek:
[Samsung Galaxy Nexus] tweak42:
moving on

I'm sad to report my Galaxy Nexus was stolen Saturday (at Disneyland of all places) so I'm unsubing all the Galaxy Nexus threads I followed here.

Before move on I wanted to post a big thank you to musical_chairs for keeping this rom up and running. Was great trying and testing out stuff while it lasted. :highfive:
[Samsung Galaxy Nexus] musical_chairs:
I can probably do a new build before long. I have a few little changes I'd like to apply anyway. And I'd reeeeally like to get marshmallow working...
[Samsung Galaxy Nexus] musical_chairs:
New build up: synced with CM this morning. I also changed the default IO scheduler back to CFQ, with slice_idle set to 0, following Ziyan's recommendation. Performance is almost as good this way, and stability is very much improved. I was lucky to hit 48 hours uptime without a freeze/reboot on BFQ, and I can easily get 200+ hours uptime on CFQ, still performing well. 200 hours uptime is kind of my personal benchmark for ROM stability.

If you really liked the performance on BFQ and weren't bothered by the crashes, use your favorite kernel tweaker app to change it back.
[Samsung Galaxy Nexus] SuperGoober:
Reading your post I didn't realize people were having crashes . Here's a bit of observations and feedback. On the last several builds my phone has stayed up for days and never crashes . In fact the phone had been up for 10 days and was rock solid stable on BFQ . I basically use this phone as a test device more so than a normal phone . I monitor it closely , especially for battery life and stability . It's very controlled where apps and variables are concerned . That being said battery life across all the builds has been incredible . Typical battery life for me has been a solid 4 to 6 days on every full charge . That's right . It gets very few calls and spends 90 % of it's time in airplane mode for mobile signal with wifi active , That being said

With this build the phone used 60 % battery in 23 hours . Nothing has changed in app usage . In fact I prevent all autostarting apps from running with cleanmaster . From 8 am to 10 pm last night it had used 42 % on cfq . I switched back to bfq and from 10 pm to 7am it used 8% . I'm not sure what the orginal slice idle time setting is or where to find it but the phone wakes up and goes to sleep every few minutes . So we really don't know if its the new changes or something in CM at this point . Just wanted to offer this snapshot and feedback for some thought . The only thing about using bfq is another app has to run and battery to consume to keep the changes in affect . Where do I find slice idle time and what was the value before setting it to zero ? Thanks for all you do !
[Samsung Galaxy Nexus] musical_chairs:
That's interesting, because I had been having terrible battery life the last week or so that I was on the previous build, and flashing the new build seems to have fixed that for me. And while I've received almost no reports of crashes on BFQ, I've been seeing regular crashes myself, and multiple users have reported crashes on Ziyan's maguro builds.

In Kernel Adiutor, slice_idle is under I/O Scheduler / Scheduler Tunable. If you use Trickster Mod, I believe you need the paid version to acces the scheduler tunables. I'm not sure what the default slice_idle on CFQ would have been before this, I'm setting it in init, not in the kernel source.
[Samsung Galaxy Nexus] SuperGoober:
I hear ya , maybe it;s the nature of the beast between the two devices . I've not had crash number 1 on bfq , it's ran pretty much flawlessly the whole time . I recharged, switched back to cfq to give it another chance and it's guzzling my battery like never before .I've used almost as much in 5 hours as I normally do in 24 and thats with almost no activity , just letting it sit , no calls or screen time . It's like the difference in night and day . Just giving you honest feedback under very controlled parallel test . If I had to vote I would vote for bfq with the settings from the last build along with the latest CM . If you looked back in this thread you won't find where I've ever had a battery issue . I have actually gotten 6 days on a charge and most always 4 or 5 . Right now it estimates about 1 day left . Thanks !

Edit : I'm going to wipe everything and do some more testing to try and provide more information . Anyone else experiencing this battery phenomena ?
[Samsung Galaxy Nexus] kel29738:
Marshmallow?
[Samsung Galaxy Nexus] musical_chairs:
Marshmallow builds will be unified, as in, the same build will work on maguro, toro, and toroplus. At the moment, FML is the most up-to-date, and that's where the action is currently. (Check the FML thread in the maguro forum.) I've been running that on my toro for over a week now, and I know it boots on toroplus. I haven't flashed it on our activated toroplus (that phone belongs to a certain Very Important Family Member) so I can't say for sure that the radio is working on toroplus on Marshmallow yet.

Anyway, if all goes well, I won't need to maintain my own ROMs at all for Marshmallow, other than an occasional build to fill in the cracks..
[Samsung Galaxy Nexus] MonstaDriva:
edit : accidental double post , see below .
[Samsung Galaxy Nexus] MonstaDriva:
Thanks for letting us know @musical_chairs . Does this mean no more Cyanogen builds as in Cyanogen Marshmallow ? Should we hang out in the maguro thread then and report issues or problems here or there ? Will you be working on the toroplus if we have radio troubles ? Sorry for all the questions . Just trying to understand what we're doing so we'll all know . I have always appreciated all you've done in taking care of us with Lollipop . Crossing my fingers we'll get to run MM too . Thanks man .
[Samsung Galaxy Nexus] musical_chairs:
For now anyway, we'll be hanging out in the maguro threads. I'll do what I can regarding the toroplus radios. We should see Cyanogenmod MM for our devices. Ziyan is working on an updated kitkat build at the moment, I'm hoping he will bring up the Cyanogenmod tuna tree to Marshmallow when he's done with that.

For now, if you want to try MM, follow the maguro FML thread, and report any bugs (including toroplus radio issues) there. Though you may want to wait for a new build, there are some fixes that are more recent that the current one.
[Samsung Galaxy Nexus] SuperGoober:
Marshmallow

Sprint users , as musical chairs stated we are to follow a different thread for the unified builds of Marshmallow . I have flashed an early build and am surprisingly pleased with the early results . You can read my report of what's working for me as well as issues spotted so far here .

http://xdaforums.com/galaxy-nexus/d...05-2014-v2-t2764064/post64578255#post64578255

You can flash this safely the same way we've been flashing . I used su265 to get root . You have to reflash it after each system wipe as it doesn't stick yet . Still in beta . If you are ready for MM then refer to musical_chairs post with a link to a build on page 318 . Please ignore my post about 3G not working . It's working great .
[Samsung Galaxy Nexus] toplist:
What file do you flash to try Marshmallow on Sprint Galaxy Nexus? tuna ota zip file?

Is it to be understood that there is a slim chance of getting 4G LTE on android 6.0 for Spring Galaxy Nexus? What I gathered is nobody got 4G working beyond stock 4.3 rom on Sprint Galaxy Nexus. Is it true? I noticed that on official cm 11 (4.4.2) thread, one user reported working 4G on their device (http://xdaforums.com/galaxy-nexus/s...nogenmod-11-0-nightlies-t2449780/post55930462). I haven't tried the build myself though.
[Samsung Galaxy Nexus] SuperGoober:
Sorry , I went back to Lollipop soon after that post . MM runs just fine and seems dependable but my battery was only lasting about 8 hours from a full charge with airplane mode on and wifi and not using the phone or playing with it , hardly any screen time . There's something about the wifi using up the battery for me . Give it a shot . I don't know if LTE works but 3G works fine . MMS worked the one time I tried it . If it wasn't for the battery I would still be on it . I get 4 to 5 days on Lollipop . Hoping the next build might yeild better results ,
[Samsung Galaxy Nexus] musical_chairs:
Yes, use the tuna build, it works for all variants.

Regarding 4G, the chances are very slim of getting it working because AFAIK we haven't had a toroplus dev with 4g Sprint service since about cm4.4.2.
[Samsung Galaxy Nexus] MonstaDriva:
Future maintenance question

[MENTION=4531957]musical_chairs[/MENTION] , hey bud . are you going to be able to drop an occasional new build of 5.1.1 to include the latest security patches , updates and whatever goodies CM has improved upon and added ? Right now as you know the last security level for us is November 1 . Grateful to ya
[Samsung Galaxy Nexus] musical_chairs:
Wow, I didn't realize it has been that long! Sure, I can put up another build. I'm not abandoning cm12.1 just yet.
[Samsung Galaxy Nexus] musical_chairs:
OK, new build up. Things should be running nice and smoothly with the new zram tweaks from the official maguro cm-12.1 build. I'm going to be staying as close as possible to the official builds from now on. This means dex-preopt has been turned back on, I think that breaks xposed.

Link is in the OP. Enjoy!
[Samsung Galaxy Nexus] musical_chairs:
Testers wanted!

I have 'backported' a fix for toroplus that [MENTION=3390093]MWisBest[/MENTION] did for Marshmallow. According to him, toroplus maps android band 7 incorrectly just like toro did. The fix amounts to four bytes changed in libsec-ril_lte.so, if I dissected his work properly.

Here are two flashable zips, one to install the modified lib, and one to revert to the original lib. Both work fine for me on my 1x-only activated toroplus. I'd love to hear how this works on other toroplus's that are activated - or better yet, on a toroplus actually still activated on Sprint.

These should work on any Lollipop-era ROM.
[Samsung Galaxy Nexus] SuperGoober:
ok I can test but I don't quite understand what it's for . I need a reference to look at the before and after . Please explain a little more and tell me what I'm looking for to change .
[Samsung Galaxy Nexus] musical_chairs:
Looking for any changes in data connectivity. How does 3G work? How fast do connections come up? Does LTE work, possibly?

Sorry, I should have been more clear.
[Samsung Galaxy Nexus] SuperGoober:
Ok , I'll do it today . I have noticed 3G on the MM rom pops up about 10x faster , almost instantaneous so maybe your on to something . Will let you know .

Edit: [MENTION=4531957]musical_chairs[/MENTION] . I tested it under a few scenarios and couldn't really see any conclusive difference . Timed each before install and after install until 3G kicked in and seems about the same . Also from Booted up until 3G came on was about 18 seconds for original and 19 seconds for the test .That one second could be a flake , give or take a second for either . That's why I say non conclusive . Works just fine with the test so it doesn't break anything . I'm going to run the test for awhile just to see how it goes . Right now I'm barely on the fringe of coverage so that could be an issue . I'll see when I go to town and do the test again .
[Samsung Galaxy Nexus] SuperGoober:
I'm back on this good dependable rom for now . Running latest version with the lib patch . I should have noted in my last post that while it takes around 15 seconds for 3g to pop up on either lib, from then on if I disconnect data and turn it back on or go from wifi to mobile it pops on much faster , just 2 or 3 seconds . It's only after boot that it takes a bit . Both lib files seem to be the same as far as I can tell . thanks
[Samsung Galaxy Nexus] crhylove:
Does anybody else have their toroplus turn off? Is it the rom, or is something wrong with my hardware, or.... ? Basically, I'll go to wake it up from sleep, and notice it's off, and I need to reboot. Also, I've had no luck yet getting data on Ting. Is there a specific APN I need? Thanks in advance. Pretty cool to have such a new rom running on such an old phone!
[Samsung Galaxy Nexus] SuperGoober:
I haven't had that issue but I'm on the 10-18-2015 build . It seems to have been the smoothest running and best battery lasting build for me . I'm going to flash the latest and run it for a couple of days so I can confirm for you if this issue happens . On the ting question you should not need to change any apn setting to have data on ting . All of the builds including the last has 3g data working fine right out of the box . I've ran the last two builds enough to confirm that . In the meantime you might want to do a clean wipe and try the 10-18 build . If you have trouble on it then you have something else going on because it runs about perfect with super good battery life .
[Samsung Galaxy Nexus] crhylove:
Did a clean flash and all is good. Must've been a dirty flash on my part... Now I just need to get the voice recognition keyboard to work and I'm golden! Sorry fort the lousy report...
[Samsung Galaxy Nexus] musical_chairs:
New build up. Some fun stuff this time:

Android security patch level: February 1, 2016

Fully stock CyanogenMod 12.1 - almost all necessary toroplus code has been upstreamed. **

And last but not least, two long-awaited fixes from Ziyan and the team: (you're not gonna believe this)

http://review.cyanogenmod.org/#/c/131714/ - fixes the occasional camera crashes

http://review.cyanogenmod.org/#/c/131715/ - fixes the purple line on videos (!!!)

And toroplus users get it first, right here!

** One change to vendor/samsung is still pending, look in my github or Ziyan's github before doing your own builds.
[Samsung Galaxy Nexus] PainFly23:
Awesome to hear about the camera fixes! As far as I know those were the biggest problems with Lollipop left to fix.

By the way, any chance you can upload a new build with something other than bfq as the default i/o scheduler? I've heard it works great for some people, but for me and some others it just causes crashes and makes it really difficult to get in and change it. Bfq has only gotten worse for me over time. Now it's to the point where if I even try to change the i/o scheduler it crashes on me, and if I try to put up with bfq it crashes in a minute or two anyway.
[Samsung Galaxy Nexus] musical_chairs:
Hmm, the bfq-related crashes disappeared for me about a month ago, I figured it was fixed for everybody. It does still crash when you try to change the scheduler to something else using an app like Kernel Adiutor or Trickster. Until that bug is fixed, you can change the scheduler by editing build.prop. Look for the key 'sys.io.scheduler=bfq' and change it to '=cfq'. Save build.prop and reboot. (Setting it this way will stick across reboots, though it will need to be re-done after flashing the ROM.) Make sure you disable any 'apply after boot' scheduler settings in Trickster, Adiutor, etc.
[Samsung Galaxy Nexus] PainFly23:
Thanks. Bfq definitely seems a bit weird, especially since its reliability fluctuates so much for everyone. I've got it under control now by running a different kernel, but I'll have to go back and try your suggestion since I'm more of a fan of the stock kernel.
[Samsung Galaxy Nexus] SuperGoober:
I have to agree with Painfly and respectfully request a change . I have tried the last two builds several times but always go back to the 10-18 build because it runs faster and smoother with much better battery life . I don't know positively for sure what it is , but whether i do dirty flash or clean the last two builds are laggy , worse on battery life . An example is maps and navigation . Takes about 5 to 8 times as long to get it up and then it might not even work . I really want to run the new builds but after a couple of days it just gets worse and worse . The 10-18 build works like a charm day after day . Just feedback from the toroplus . on BFQ vs CFQ , maybe something else got merged back in that time period that's produced these symptoms . Back at the time you mentioned this govenor change so maybe we assumed that was the difference . I really can't say and don't know . All I know is something happened . I'll give the build prop edit a spin on a clean flash and let you know how it goes . Thanks for all you do for us .

Edit: [MENTION=4531957]musical_chairs[/MENTION] . Very strange . I've tried 8 times to change bfq to cfq and every time I hit save in buildpropeditor the phone immediately freezes and I have to pull battery . This is on a clean flash after wiping cache, dalvik, data and system . I can change other random settings in buildprop without this happening .

I have now edited the buildprop with a text editor , saved and rebooted and it stuck . I'll see how it does for s few days . Buildprop just can't make the change . Thanks
[Samsung Galaxy Nexus] musical_chairs:
Strange - like it's trying to actually apply the scheduler change right away? Maybe buildpropeditor is trying to be too smart for its own good.

One sure-fire way would be to make the change on a computer using adb. It would go something like this:

adb reboot recovery
adb root
adb remount
adb pull /system/build.prop

(open build.prop in a text editor on your computer, make the change, and save it.)

adb push build.prop /system/build.prop
adb reboot

I usually either do it that way, or in the built-in text editor in Xplore file manager if I'm not at my computer. I like to see what's actually being changed and I don't exactly trust build.prop editors that try to make things too easy.
[Samsung Galaxy Nexus] SuperGoober:
I just edited the file with efs file explorer . Rebooted and it stayed on cfq . Early results are it's running like a different phone . I was almost having to pull the battery to get out of hung up navigation . I had tried on many occasions to use a newer build but never could get the hangs and lags out . I've already been outside testings maps , directions etc and it's working good so far . Hopefully now i can stick with new builds but BFQ seems to be at odds with my toroplus . I never had any instant crashes with BFQ , all my troubles were lag , poor response and freezes . Thats why I always wound up back on 10-18-2015 because it ran perfectly .
[Samsung Galaxy Nexus] MonstaDriva:
Nice build

[MENTION=4531957]musical_chairs[/MENTION] New build is smooth as butta running cfq . I had the same experience as Gooba with bfq but it's like greased lightning now . tnks for the new build with updates and security patch man . We appreciate ya .:good:
[Samsung Galaxy Nexus] SuperGoober:
Update

[MENTION=4531957]musical_chairs[/MENTION] , I wanted to let you know the last build is running fantastic . Thanks for your help on getting cfq going . I think this is best build yet and all issues are gone now . Camera is working great . Your build runs much better than the MM builds I've tried . Hopefully once MM gets going good you might bring us a good CM build forth . Run's awesome !
[Samsung Galaxy Nexus] Max Frost:
L 5.1.1

I have tried a few roms lately and this one is the best I have found yet . Thanks for keeping this old device alive and I'm glad security level is updated . I've had nuttin but trouble with the buggy MM builds . Please keep it going !! TY

Edit: LOL 7 days on the battery life !! Incredible :good:
[Samsung Galaxy Nexus] musical_chairs:
New build up. This time, the change of note is dynamic tiler allocations, for some more free ram. Enjoy!
[Samsung Galaxy Nexus] Max Frost:
New build is nice . Did not include March 1 security patch ? Will you be building CM for 6 MM ? Insanely good battery life !
[Samsung Galaxy Nexus] musical_chairs:
Yes, the March security patch is included, I failed to mention that.

The next build will be cm13. :)
[Samsung Galaxy Nexus] musical_chairs:
A cm13 build is up. It seems to work well here. I am not able to test it on our activated toroplus at the moment; it looks like ril and telephony stuff should be fine, but please let me know if there are any problems. As always, keep a good nandroid handy when flashing new stuff like this.
[Samsung Galaxy Nexus] Cardcaptor_RLH85:
Your first post is slightly confusing (could be that it's 4 AM here though) but, we still have to wipe before flashing from your CM 12.1 build to this new CM 13 build right?

Thanks for keeping up the development on our increasingly ancient device!
[Samsung Galaxy Nexus] musical_chairs:
Sorry about that, OP's aren't my strong point...

I did not test dirty-flashing from cm12.1. In an ideal world that would work. It should be possible at least in theory, but without extensive testing I don't know what might go wrong. So I don't actually know if you need to wipe before flashing from cm12.1 to cm13.0. It's probably better to wipe.

I'm not helping your confusion, am I?
[Samsung Galaxy Nexus] Max Frost:
I did a clean flash because it would be hard to say if any issues were because of the new version rom or the dirty flash . Flashing clean gives a better platform for testing .

Hey , I installed the rom last night and used open gapps nano arm . You were right about the long time it takes for open gapps to install itself . No force closes and for a first build it's doing quite well . 3G and telephony do work . I haven't really tested a lot but can report one issue . Wifi and 3G both stay on together . I've checked under Dev options to make sure cellular data was not set to stay on . When wifi kicks on 3G doesn't turn off . It's looking great so far . Apps , themes and general operation seems smooth . Will report if I encounter any other issues . Thank you !!! :good:
[Samsung Galaxy Nexus] musical_chairs:
Thanks for that report. I will update the OP accordingly.

toro is showing the same behavior for me. The 3G or LTE label in the status bar (again, this is on toro) goes away when wifi is connected, but the label stays on in the pull-down quick settings toggle. When the phone wakes up, often wifi will be off and mobile data on for a second or so, then wifi connects and the 3G indicator in the status bar goes away. I will have to pore through the logs and try to figure out if mobile data is actually staying on or if it is just the indicators being wonky.
[Samsung Galaxy Nexus] Max Frost:
Yesterday my wifi and net were down so I used my phone for a hotspot and it worked great . The rom runs so good it's like not missing a lick going from the last L to M . I'm totally surprised how well it's doing for the first build . I did not flash Supersu , just using privacy guard for rooted apps .

[MENTION=4531957]musical_chairs[/MENTION] Hi , is your GPS working ? Mine is just borked . It's not like it's not picking up birds , it's like that and map and gps app's acting flakey asking over and over for permission to change the device location settings . When I say ok it keeps asking over and over even though high accuracy icon is on . Let me know if yours is alright . thank you .
[Samsung Galaxy Nexus] musical_chairs:
GPS seems to be broken on toroplus. It is working on toro. I probably muffed something in the bringup for toroplus.
[Samsung Galaxy Nexus] musical_chairs:
[MENTION=7031856]Max Frost[/MENTION] can you try flashing this zip in recovery and see if it fixes your gps?
[Samsung Galaxy Nexus] Max Frost:
Good news , I flashed the zip and that fixed it . GPS and related apps are working now . Thank you
[Samsung Galaxy Nexus] SuperGoober:
Great job , the rom is running very nice . GPS fix nailed it .