yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] musical_chairs:
New build up! Interesting changes are:

- Low-ram tweaks from Ziyan

- More low-ram tweaks from zzpianoman

(Ziyan's tweaks tell the system we have a low-ram device, and zzpianoman's tweaks turn right around and lie about it to the apps. Seems to work pretty well.)

- Fixes that fix the stagefright fixes
[Samsung Galaxy Nexus] Cardcaptor_RLH85:
I have quick question, what method is used for Super User access in this ROM? I was thinking about installing Chainfire's LiveBoot boot animation (it shows the dmesg/logcat output in the place of a boot animation) but, he says that it doesn't work unless you have SuperSU 2.40 or above installed. I know from experience that switching out an included Super User access method can go badly so I was just trying to figure out what's in use here.
[Samsung Galaxy Nexus] elbi14:
This rom include BLE patch?

Sory for my english
[Samsung Galaxy Nexus] musical_chairs:
This ROM has CyanogenMod's superuser, I have not modified it in any way. It works well for the few things I need root for. Installing SuperSU should work fine, it may be best to flash it via a zip in recovery.

I don't know. What is BLE?
[Samsung Galaxy Nexus] elbi14:
Bluetooth Low Energy, v4.0
[Samsung Galaxy Nexus] zieruchan:
Looks interesting !!

Can this run on maguro ?
[Samsung Galaxy Nexus] clmbflcb:
I just found this ROM, how well do the radios work that come with it? I've had issues in the past and I don't know which radio is best.
[Samsung Galaxy Nexus] musical_chairs:
No, this is for toroplus only. For maguro, try one of these ROMs:

http://xdaforums.com/galaxy-nexus/development/cyanogenmod-12-beta-builds-t2958865

http://xdaforums.com/galaxy-nexus/development/rom-unofficial-cyanogenmod-12-t3062057

The ROM does not include a radio, it leaves that untouched. If you want, radios can be flashed separately; see the sticky thread in this forum.

Be advised that I don't think anyone has figured out how to get 4G working with any lollipop ROMs on the toroplus.
[Samsung Galaxy Nexus] bladerunner993:
Updating from a previous build

If updating from a previous build will anything be lost?
[Samsung Galaxy Nexus] PainFly23:
Nope! Just go ahead and flash it over what you have now. Just remember it's never a bad idea to make a backup.
[Samsung Galaxy Nexus] musical_chairs:
New build up! Lots of changes, so I recommend making a good backup in case something doesn't work.

Changes:

- DEX_PREOPT has been disabled. This will make the first boot take a bit longer. It also makes the ROM smaller, and XPosed might work now. I have not tested XPosed.

- SELinux is now set to enforcing. This is a kernel build change, and I would really like to leave the kernel sources untouched (GPL compliance and all, and me without a github account). If anything doesn't work that used to on previous builds, please attach /data/misc/audit/audit.log to your bug report.

- low_ram flags have been left enabled in this build, but the lowmemorykiller minfree values are now set to their original cm12.1 values. Hopefully this will give us the best of both worlds. Any unusual system thrashing (aka horrible lag when receiving a phone call), or any excessive app killing or homescreen redraws, please report.

*** Special note to users on Sprint's network: I added SELinux policies for Sprint Download Manager (SDM.apk) to allow its actions as far as I can test it. If it doesn't work on this build (but worked on previous builds), please post a copy of /data/misc/audit/audit.log. ***

Happy flashing!
[Samsung Galaxy Nexus] musical_chairs:
Current SELinux policies, for anyone who might care:

(Please let me know if anything looks glaringly wrong here. I don't pretend to completely understand this stuff.

These were generated using the process described here: http://selinuxproject.org/page/NB_SEforAndroid_1#Logging_and_Auditing )

Here is the contents of the SELinux permissions files relevant to toroplus:

/device/samsung/tuna/sepolicy/rild.te (last line is for toroplus)

# rild
allow rild radio_data_file:dir { r_dir_perms setattr };
allow rild system_data_file:dir create_dir_perms;
allow rild system_data_file:file create_file_perms;
allow rild self:process execmem;
allow rild block_device:dir search;
allow rild proc_net:file write;
allow rild sysfs:file write;
allow rild system_data_file:sock_file { unlink create };

/device/samsung/tuna/sepolicy/system_app.te (this file is specific to toroplus)

allow system_app rild:unix_stream_socket connectto;
allow system_app system_app_data_file:sock_file { create write unlink };

And this is the relevant section of BoardConfig.mk:

BOARD_SEPOLICY_UNION += \
genfs_contexts \
file_contexts \
bluetooth.te \
dumpdcc.te \
init.te \
mediaserver.te \
pvrsrvinit.te \
rild.te \
platform_app.te \
system_app.te

(platform_app.te is for toro, system_app.te is for toroplus)
[Samsung Galaxy Nexus] funkypc:
I can confirm Xposed works.

Thanks!
[Samsung Galaxy Nexus] Cltampa89:
I was th linking about putting on my phone jus wondering if u only have to install latest version or flash all
[Samsung Galaxy Nexus] SpideyTheMan:
To install this ROM follow the instructions on post # 1 in this thread. http://xdaforums.com/galaxy-nexus/sprint-develop/rom-unofficial-cyanogenmod-11-0-t2887238
[Samsung Galaxy Nexus] SpideyTheMan:
[MENTION=4531957]musical_chairs[/MENTION] -- the latest CyanogenMod build is very responsive. We have it running on three (3) Sprint Galaxy Nexus phones now and we are very pleased with the build. Thanks again for all of your hard work putting these builds together for us!

I've tried to track down some nuisance items that we noticed which have also been in prior builds and here is what we can see that may need some attention:

1. On a carrier wipe (*#*#72786#*#*) the phone loads a Verizon MNC 00 and shows Verizon APN's in the APN list, even after the Sprint activation runs. When we look at the data programming settings (*#*#DATA#*#*) we can see that the MNC is being truncated to two digits and shows an MNC of 00 for Verizon instead of showing the three (3) digit code 120 for Sprint. Rebooting after Sprint activation doesn't resolve this.

2. Editing the MNC (*#*#DATA#*#*) by supplying the MSL and setting it to 120 does appear to set the MNC correctly. However when you reboot and view the MNC setting again it is truncated to 20. This appears to be a display issue where the firmware is ignoring the first character of the MNC, presumably because Verizon's MNC is only two digits. Fortunately even though only the last 2 digits are displayed in the data settings the MNC still appears to be set correctly to 120 as the APN editor shows Sprint APN's. If you edit one of the Sprint APN's you will also see an MNC of 20 instead of 120. So this app is also suppressing the first character of the MNC.

3. Setting the preferred network type to 3G and checking the phone info with *#*#INFO*#*# shows that the preferred network type is always set to Unknown.

4. Setting the preferred network type to LTE and checking the APN's does not show APN's with an LTE bearer. Instead the APN's with an unspecified bearer are shown.

5. With LTE enabled checking the phone info with *#*#INFO*#*# shows that the preferred network type is Unknown.

6. Initially MMS wasn't working properly so we deleted and recreated the Sprint APN's and now MMS works perfectly.

I think if we can straighten some of this out, we may be able to get LTE working instead of only 3G data.... :good:
[Samsung Galaxy Nexus] musical_chairs:
Thanks for the detailed report! I'm suspicious that these issues all boil down to #1. I've never managed to figure out how the ROM decides on the MNC. I don't think it's set in the ROM build or the overlays, I think it is read by the ROM from the phone. But is it reading nv-ram or the built-in sim? I would love to get to the bottom of this.
[Samsung Galaxy Nexus] musical_chairs:
Just thought of a question for you: Does Sprint activation work properly even on the latest build, with SELinux set to 'enforcing'? If so, that is very good news, I was expecting to run into a few issues there.
[Samsung Galaxy Nexus] SpideyTheMan:
That's a good one. The Google Android docs here say that the MCC/MNC comes from the SIM card. Before the carrier reset my SIM card was showing a MCC/MNC of 310120. After a carrier reset my MCC/MNC resets to 31000 which appears to be the Verizon default. Because this changed it means the code is being programmed into the SIM by the ROM. After carrier reset getSimOperator() returns 31000. So this value was initialized by the ROM's carrier reset app.

Before the Sprint activation starts getSimOperator() returns 31000 but getNetworkOperator() returns 310120. After activation these settings don't change but I did have 3G service after Sprint activation completes. The phone shows that my SIM is miss-programmed but the network that the phone is connected to is Sprint. Opening *#*#DATA#*#* allows me to update the MNC from 0 to 120 and after a reboot getSimOperator() incorrectly returned 31020 but does connect to 3G. So I updated the MNC again using *#*#DATA#*#* from 20 to 120 and rebooted. This time getSimOperator() returns 310120 as it should but if you use *#*#DATA*#*# to view the MNC it displays as 20 again but getSimOperator() is correct. When I opened the APN editor and reset APN's to default none of the Sprint APN's were showning because something about the ROM truncates the MNC to 20 which doesn't match Sprint in the APN database. So I added the APN's below which corrects problems with sending/receiving MMS messages. One other note, the MCC/MNC checker app shows a mccXXX-mncYYY overlay of 310020. So wherever this comes from seems to be the source of the issue.

Name: Sprint

APN: n.ispn

MMSC: http://mms.sprintpcs.com

MCC: 310

MNC: 20

APN type: default,mms,dun

APN protocol: IPv4/IPv6

APN roaming profile: IPv4/IPv6

Name: Sprint EHRPD Internet

APN: n.ispn

MMSC: http://mms.sprintpcs.com

MCC: 310

MNC: 20

APN type: default,mms,dun

APN protocol: IPv4/IPv6

APN roaming profile: IPv4/IPv6

Bearer: eHRPD

Name: Sprint EHRPD OTA

APN: otasn

MMSC: http://mms.sprintpcs.com

MCC: 310

MNC: 20

APN type: fota

APN protocol: IPv4/IPv6

APN roaming profile: IPv4/IPv6

Bearer: eHRPD

Name: Sprint LTE Internet

APN: n.ispn

MMSC: http://mms.sprintpcs.com

MCC: 310

MNC: 20

APN type: default,mms,dun

APN protocol: IPv4/IPv6

APN roaming profile: IPv4/IPv6

Bearer: LTE

Name: Sprint LTE OTA

APN: otasn

MMSC: http://mms.sprintpcs.com

MCC: 310

MNC: 20

APN type: fota

APN protocol: IPv4/IPv6

APN roaming profile: IPv4/IPv6

Bearer: LTE

Name: Sprint MMS

APN: n.ispn

MMSC: http://mms.sprintpcs.com

MCC: 310

MNC: 20

APN type: mms

APN protocol: IPv4/IPv6

APN roaming profile: IPv4/IPv6
[Samsung Galaxy Nexus] musical_chairs:
[MENTION=6425673]SpideyTheMan[/MENTION] I think I found something. Are you comfortable editing build.prop? You need to add this line:

ro.telephony.get_imsi_from_sim=true

It looks like I missed it in the initial bringup to Lollipop, and since I need Verizon's MNC on my phones to get data working anyway, I never noticed. If I add this line to build.prop, save it, and reboot, the APNs menu populates correctly. Try it and let me know if it helps.

Edit: I was doing some digging trying to figure out where that line came from, and it looks like credit goes to [MENTION=1048318]zzpianoman[/MENTION] and this post.
[Samsung Galaxy Nexus] musical_chairs:
OK, I pushed out a new build with that line included. It is definitely an improvement, and I'm very interested in hearing results from anyone with a toroplus active on Sprint or a Sprint-based MVNO.
[Samsung Galaxy Nexus] SpideyTheMan:
[MENTION=4531957]musical_chairs[/MENTION], Thanks for that fix. Yes, I've confirmed that adding this does correct the MNC overlay and now I can see the Sprint APN's in the APN menu.

# Store correct IMSI when retrieved from SIMRecords and use it for Ruim Records
ro.telephony.get_imsi_from_sim=true

The carrier reset works flawlessly and the MCC/MNC shows correct values throughout the entire process. I was hoping that LTE would come on but it still seems like LTE doesn't want to turn up yet. One issue is that several of the Sprint APN's don't have the Bearer set correctly. That was easy enough to fix. I think it may still be some other build.prop fix. Since the one that you found was so effective I may give some others a try to see if we can get LTE working after all. Here are the settings I'm experimenting with. I stared with the other setting cited by [MENTION=1048318]zzpianoman[/MENTION] in the post you reference for the data fix where he adds "datacallapn,signalstrength" to ro.telephony.ril.config such as the one below:

# Invokes parameters for needsOldRilFeature to fix Toro/Toroplus radio
ro.telephony.ril.config=datacallapn,signalstrength,usevoicetechfordata,writeaidonly

Next I see several other settings that might help and could be worth trying such as setting CDMA+LTE/EvDO (auto) as the default network and so on:

# Set default & preferred network to CDMA + LTE/EvDo auto
ro.telephony.default_network=8
ro.ril.def.preferred.network=8

# Set permitted CDMA subscription types
ril.subscription.types=NV,RUIM

# Don't wait the card state for RADIO POWER request
persist.radio.no_wait_for_card=1

# Not LTE on GSM
telephony.lteOnGsmDevice=0

We'll see if any of this helps..... thanks a lot for the super great Lollipop ROM and for help getting the radio straightened out! :highfive:
[Samsung Galaxy Nexus] musical_chairs:
Awesome! Too bad LTE is still not working.

For build.prop items, have a good look at what zzpianoman is currently using in his toro builds:

https://github.com/zzpianoman/android_device_samsung_toro/blob/cm-12.1/system.prop

He has tested this stuff more thoroughly than any of the other devs on here. One line that looked particularly interesting to me was this one. It made no difference in my testing, but it would be interesting to see your results:

# Set CDMA SUBSCRIPTION SOURCE to RUIM in Database for this device
ro.telephony.default_cdma_sub=0

Thanks for your careful, detailed reports!
[Samsung Galaxy Nexus] JohnCorleone:
Maybe try changing the line in the build.prop to

telephony. lteOnCdmaDevice=1

I noticed in the post a few above this that it says

telephony. lteOnGsmDevices=1

Unless you are already past that but I have a Evo 4G LTE I can return to rooted stock to get all of the exact info. The other changes look about right though. I am going to charge up my WiFi only GNex and flash the latest build since the reviews are so positive!

Sent from my EVO using Xparent Gray Tapatalk 2
[Samsung Galaxy Nexus] SuperGoober:
I'm one of the users that pretty much has always had 3G but with this latest build I haven't had any success in getting data working . I went back to the previous build and 3G pops right on in about 3 seconds . Not sure what happened , whether it's coincidental with the change you made or something with CM . Tried everything I know to try with no luck . thanks
[Samsung Galaxy Nexus] mharbudd:
Not sure if this would work for you (or if it's a problem for anyone else...) but since 4G stopped working (Lolli, but was also true when KK 4G wasn't working), I only get data if the LTE is turned off in the Advanced part of the DATA menu (*#*#3282#*#*)

So try turning that off and see if it gets you 3G?

Otherwise this new build is working fine for me. Thanks for all the work you put in Musical
[Samsung Galaxy Nexus] SuperGoober:
Strange , I had already looked at that . It's on with the previous build and I have 3G . It's off by default on this latest build but I don't get 3G with it on or off . I see mnc has changed from 20 on the last build to 0 on the new build .

Edit: I got it going by changing the mnc value to 120 .
[Samsung Galaxy Nexus] musical_chairs:
MNC should now be 120, which is correct for Sprint, instead of 20 which was incorrect. If you're not on Sprint and can't run the carrier activation process, you may need to go into the data menu and set your MNC to 120. See the two posts by [MENTION=6425673]SpideyTheMan[/MENTION] for info on how to change the MNC. Also, check out your APNs and make sure the MNC is set to 120 in those as well, or reset them to default.
[Samsung Galaxy Nexus] SpideyTheMan:
The MNC has been incorrect/truncated on prior builds so neither 20 or 0 are correct. On Sprint the MNC should be 120. The latest build has an update to the build.prop so the Sprint MNC is being correctly pulled from the internal SIM card on the Toroplus. The MNC in the vmram doesn't appear to matter -- the one on the SIM card is what's important.

Perform a carrier wipe (*#*#72786#*#*) on the phone. This will reboot the phone and initiate a Sprint Activation. Once the activation completes bring up your APN menu (through Google Gesture Search app, APN) and make sure that you reset APN's to the defaults. . Once this is done confirm that your mobile data is set to 3G and you should see 3G service again. Just be patient as 3G may take a few moments to come back online after a carrier reset & APN reset. Reboot your phone if needed.
[Samsung Galaxy Nexus] musical_chairs:
Great!

Thanks for your info and help, this is the proper method if your phone is activated on Sprint. If (like me) you're on another carrier (I'm on Page Plus, which uses Verizon settings), Sprint Activation won't work. In that case, you'll need to manually set the MNC and other relevant data settings using the hidden data menu. Once that is programmed properly, reset the APNs to default, then program in any custom APNs you may need for your non-Sprint carrier. If your MNC is not 120, leave it set to 120 in APN settings and use the 'MVNO' settings at the bottom of the APN to set the MNC you need to use. In my case, I set 'MVNO type' to 'IMSI' and 'MVNO value to 310012x' (MCC 310, MNC 012, which happens to be some old settings for Verizon.)
[Samsung Galaxy Nexus] musical_chairs:
There's a new build up. Just synced with CM, no changes on my end this time.
[Samsung Galaxy Nexus] musical_chairs:
New build up, just because. Synced with CyanogenMod yesterday.
[Samsung Galaxy Nexus] Cardcaptor_RLH85:
So, I've noticed that my Nandroid backups haven't been working for a while now (they seem to have stopped working some time in late August actually) but, I haven't changed my Recovery since July so, I don't think that's the issue.

I'm running TWRP 2.8.7.0 and I was just wondering if the ROM could cause either of the issues I'm listing below. I've also posted this in the TWRP thread but, since I don't know if this issue could possibly be caused by the ROM, I'm going to ask here too just to cover my bases. Thanks.
[Samsung Galaxy Nexus] aniket_:
Does anyone know where the source code for this build is ? Any github link ?

toroplus on the Cyanogenmod github does not contain cm12.1
[Samsung Galaxy Nexus] musical_chairs:
I'm going to try getting my stuff up on github, I'll let you know when it's up. For toroplus, there are changes to frameworks/native, as well as the tuna and toroplus device trees. I've also picked a few changes to frameworks/base. It's pretty much all stuff I've picked from other places, I really don't write my own code.

Edit: That was kind of fun! I'm on github now: https://github.com/musical-chairs

To build for toroplus, you'll need:

- toroplus device tree (of course)

- tuna device tree (for SELinux policies, there are some audio fixes there as well but it will work without them)

- frameworks/native (toroplus radio will not work at all without this)

- hardware/ti/omap4 (needed for camera)

- vendor/samsung

My changes in frameworks/base are mostly just for the 'optimizing apps' screen on bootup, so they're not necessary either. And the other stuff is for toro.
[Samsung Galaxy Nexus] aniket_:
Are we supposed to use the unmodified tuna kernel from here ? https://github.com/CyanogenMod/android_kernel_samsung_tuna/tree/cm-12.1
[Samsung Galaxy Nexus] musical_chairs:
Yes, that's the one.
[Samsung Galaxy Nexus] musical_chairs:
New build up. Included is the BFQ scheduler recently added by Ziyan, read his post here for more info.
[Samsung Galaxy Nexus] SuperGoober:
The rom has been running very nicely , [MENTION=4531957]musical_chairs[/MENTION] , Just curious if our resident nexus gurus anticipate us getting Marshmellow on this device ? Thanks
[Samsung Galaxy Nexus] musical_chairs:
Yes. Ziyan already has it running on maguro. The GNex isn't dead yet.
[Samsung Galaxy Nexus] SuperGoober:
[MENTION=4531957]musical_chairs[/MENTION] , Awesome , are you going to turn out any more builds for us before source gets changed ? I noticed your post about the new build for verizon , Just wanted to say I haven;t had any black screen hangs , crashes or reboots at all although certain themes seem to cause that for me . If I revert back to my favorite theme its smooth as butter . I'm having a flash withdrawal is why I asked about new build Lol .

I should have mentioned way back that f2s never worked good for me . I had bad lags , slow boots , apps opening slow and a lot of black screen lags . I went back to ext4 and it's always been smoother and faster for me . I realize that's probably not the norm . In my isolated case it seems to be reversed on performance .
[Samsung Galaxy Nexus] musical_chairs:
Actually I uploaded a toroplus version on 10-05 as well, but have not tested it. I'll keep the CM12.1 sources handy for a bit, I'll play with ZMod 6.0 for a while until things get settled with CM13. ZMod 6.0 isn't buildable at the moment, I tried but I really just need to be patient and let Ziyan get the initial stuff cleaned up a bit.
[Samsung Galaxy Nexus] kel29738:
Youtube videos don't play in 60fps it just freezes. is there a fix for this?
[Samsung Galaxy Nexus] musical_chairs:
While we're all waiting for Marshmallow, there's a new build of cm12.1 up to hopefully help hold everybody over. Most interesting change is, it seems that Ziyan found a way to free up another 10Mb RAM from the 2d tiler. Enjoy!

Speaking of Marshmallow, I do have it booting on toro and toroplus, but so far RIL is still broken - no phone calls or SMS at this point. MWisBest is working on the RILs, and I'll keep building and testing. Stay tuned.
[Samsung Galaxy Nexus] PainFly23:
Awesome to hear! Do you have any plans so far for releasing a test build? Even with the broken RIL, I'd be willing to test since my Gnex is a wifi-only device at this point anyway.
[Samsung Galaxy Nexus] musical_chairs:
If you want that, just flash Ziyan's maguro test build. You'll need to open up the zip and edit com/google/android/updater-script. Change the target device from maguro to toroplus. The device check is in the first line. Make it look like like this:

(!less_than_int(1444389706, getprop("ro.build.date.utc"))) || abort("Can't install this package (Fri Oct 9 13:21:46 CEST 2015) over newer build (" + getprop("ro.build.date") + ").");
getprop("ro.product.device") == "toroplus" || abort("This package is for \"maguro\" devices; this is a \"" + getprop("ro.product.device") + "\".");
[Samsung Galaxy Nexus] kel29738:
Does anybody phone restart or freeze while watching YouTube videos? I can't even watch 60 fps videos on this phone while on kitkat it worked. is there a fix for this?
[Samsung Galaxy Nexus] PainFly23:
I'm not getting any freezes or restarts while watching YouTube, but it does hang at times. 60 fps videos also stopped working completely for some reason semi-recently. I have no idea if it's something on the ROM's end causing it or if one of YouTube's many changes has gone and messed it up though. I don't use YouTube on my phone a lot, but I do know it was working somewhere around one or two builds ago.
[Samsung Galaxy Nexus] kel29738:
Thanks bro you was right, it's youtube making 60 videos unplayable. now that i went back to the 20150906 rom it doesn't even freeze or restart anymore.
[Samsung Galaxy Nexus] musical_chairs:
The freezes / restarts are probably related to the BFQ scheduler. It's faster, but it's not quite as stable. Use one of the many kernel settings apps (Kernel Aduitor is my current favorite) and change the IO scheduler to deadline or CFQ and the freezes should go away.