yashsingh1/xdaforums huggingface dataset:
[Moto G General] tpa-moto:
It wasn't there in AOSP nor stock, so I removed it. It's there in the APN list of the Mms apk though, but DcTracker shouldn't use that field, so it shouldn't matter.

Sorry for not mentioning it earlier, but yes, Verizon should be good to go. The problem is Boost Mobile which has that mms APN and needs the dummy profile or an APN of type default with the correct bearer_mask. The changes I posted were taken from AOSP, which is a reliable source, but I can't just change the mask to make things work on falcon. I honestly don't know if there's someone using that APN nor if it's correct. I'd simply remove it, but I can't. I could edit the list at build time, but that seems risky and not a great solution. I'll think of something.

My goal is to have everything working out of the box and everything should go well upgrading from cm-12.1.

Our stock APN list seems to have what we need, but I don't know if Motorola did that to get everything working or the APN is really correct:

<apn carrier="Sprint"
mcc="311"
mnc="870"
type="default,mms,fota"
bearer="8"
protocol="IPV4V6"
roaming_protocol="IPV4V6"
authtype="3"
mmsc="http://mm.myboostmobile.com"
mmsproxy="68.28.31.7"
mmsport="80"
/>

Anyway:

ro.cdma.home.operator.numeric=310004

https://github.com/CyanogenMod/android_device_motorola_falcon/blob/cm-13.0/init/init_falcon.cpp#L100

ro.cdma.home.operator.alpha=Verizon

https://github.com/CyanogenMod/android_device_motorola_falcon/blob/cm-13.0/init/init_falcon.cpp#L99

ro.telephony.default_network=4

https://github.com/CyanogenMod/android_device_motorola_falcon/blob/cm-13.0/init/init_falcon.cpp#L115

ro.gsm.sim.operator.alpha=Verizon

Can't find it in the Android source code, so probably nothing is using this.

ro.gsm.sim.operator.numeric=310004

Same

ro.gsm.operator.alpha=Verizon

Same

ro.gsm.operator.numeric=310004

Same

EDIT: I hadn't merged http://review.cyanogenmod.org/#/c/123835/ yet not to encourage users to try the current nightlies, you need to modify the zip anyway.

EDIT2: Scratch that. You won't have to add the prop manually.
[Moto G General] hhp_211:
I definitely know alot less about this stuff than you.

getprop will shows me those gsm settings, and even though all the edits I include didn't stick there when I run that command, they are still necessary for me to be able to send/receive mms, and I can't explain why it works, but I had to do this on cm12.1 too.

Guess my phone is just weird

Carry on
[Moto G General] :
I don't know if this helps or not, but on a clean install if the last CM13 nightly, I flashed the stock Boost apns-conf.XML and added the prop fix and I have working data and MMS with 8sms. Before this with the last fix zip posted, MMS was not working even with 8sms. It seems the stock APN settings are correct. I attached a log.
[Moto G General] tpa-moto:
Let's see if I can simply get rid of that APN: http://review.cyanogenmod.org/#/c/128754/

Anyway, I was thinking about enabling the APN settings for CDMA, because I think it's disabled right now. In this way you wouldn't rely on entirely on the cm APN list.

You can see now how that would look like. Maybe you can fix the MMS APN from there.

/data/data/com.android.phone/files/carrierconfig-com.android.carrierconfig-XXXXXX.xml # XXXXXX is some number

and add

<boolean name="show_apn_setting_cdma_bool" value="true" />

between the "carrier_config" tags, like this

<carrier_config>
<boolean name="show_apn_setting_cdma_bool" value="true" />
# some other stuff, the order is not important, as long as the line is between the carrier_config tags
</carrier_config>

Then you should restart the device (probably closing the settings apps completely is enough)

I also have another question. Are Verizon and Boost Mobile the only carriers?
[Moto G General] :
I believe Page Plus and Ting are at least two others, but I'm not positive. I'll see if I can find out for sure.

Edit: US Cellular is the only other carrier I can find. I think Page Plus and Ting are only carriers that you can switch activation to if you wanted. I remember hearing of numerous users switching to one of them in the past.
[Moto G General] HandsomeOne:
Ringplus is another mvno for Sprint .
[Moto G General] hhp_211:
Page Plus uses the same as Verizon 310004
[Moto G General] :
I have an empty folder at /data/data/com.android.phone/files/
[Moto G General] :
With what was added yeaterday, data works on the 1-18 nightly with only having to flash the stock apns-conf.XML.

Were getting closer. If they would remove that damned radio assert it would be great.

Edit: someone with a carrier other than Boost please try the 1-18 nightly and see what happens for you.
[Moto G General] tpa-moto:
Umm, maybe that file is created only if there's a SIM.

And could you try to apk attached? Just put it in /system/priv-app/CarrierConfig/. It does the same, but from the apk.
[Moto G General] tpa-moto:
Anyway, I was asking about mobile carriers for two reasons.

First, I want to make sure the numeric are set correctly. As of now, init sets two numerics. Either 310004 or 311870.

Init executes

ls -la /fsg/falcon_3.img.gz

and if the output contains "verizon", 310004 is set, 311870 otherwise. So there's a chance things do not work as intended with some carriers.

The second reason is that I want to bypass completely the cm APN list and use one made specifically for you. Given that APNs are critical, that you can't edit them and that you can't just put a random SIM (=> support limited to few carriers), IMO it's not a bad idea.

If the only carriers are Sprint and Verizon (if I'm not wrong, the other carriers you mentioned are just subsidiaries/MVNOs of these two and use their numerics), this list should be enough:

<?xml version="1.0" encoding="utf-8" ?>
<apns version="8">
<apn carrier="Sprint"
mcc="311"
mnc="870"
type="default,mms,dun"
protocol="IPV4V6"
roaming_protocol="IPV4V6"
authtype="3"
mmsc="http://mm.myboostmobile.com"
mmsproxy="68.28.31.7"
mmsport="80"
/>
<apn carrier="Verizon CDMA"
mcc="310"
mnc="004"
type="default,mms,dun"
protocol="IPV4V6"
authtype="3"
mmsc="http://mms.vtext.com/servlets/mms"
/>
</apns>

In any case, if these APNs are not enough, a dummy APN profile will be created.

I took these from stock and slightly modified it: I added dun (tethering) to Verizon, removed fota from Sprint and removed the 'bearer' field to make them work independently on the radio technology.

If the apk I just linked allows you to edit APNs, that would be even better IMO, it would give you more possibilities.

If possible, try the zip attached. It replaces the APN list with the above one and deletes the APN database:

/data/data/com.android.providers.telephony/databases/telephony.db-journal
/data/data/com.android.providers.telephony/databases/telephony.db

PS: the zip doesn't actually use the apns-conf.xml file it contains, it writes it from update-binary. I was too lazy to find a binary to use.
[Moto G General] HandsomeOne:
Thank You, you left "s" off of "mmsc="http://mm.myboostmobile.com" in update-binary and i added Ringplus below .

<apn carrier="RingPlus"

mcc="310"

mnc="120"

type="default,mms,supl,ia,dun"

protocol="IPV4V6"

roaming_protocol="IPV4V6"

authtype="3"

mmsc="http://mms.plspictures.com"

mmsproxy="68.28.31.7"

mmsport="80"

Works great i have 3g on Ringplus now :)
[Moto G General] tpa-moto:
What do you mean exactly?

init will not set that numeric and RIL is not able to get the right numeric from the network, or at least that's what I could see from the logs. So I doubt this APN is used.

Could you guys please post the output of:

cat /proc/cmdline

and

ls -la /fsg/falcon_3.img.gz
[Moto G General] HandsomeOne:
My Mistake your update-binary is correct i added The ringplus to get mms pics on download for text.

<apn carrier="RingPlus"

mcc="310"

mnc="120"

type="default,mms,supl,ia,dun"

protocol="IPV4V6"

roaming_protocol="IPV4V6"

authtype="3"

mmsc="http://mms.plspictures.com"

mmsproxy="68.28.31.7"

mmsport="80"
[Moto G General] tpa-moto:
As I said, init sets the numeric to either 310004 or 311870, so Android will probably not use this APN and use the Boost Mobile one.

Did you try to use just the APNs I posted? Did it work? Or did you add your APN to the list without trying the original one? Could you maybe post some logs so that I can see which APN is used?
[Moto G General] HandsomeOne:
Sorry at work ,could not get back quickly. Yes your zip worked fine for data, but for multi media service on text changed to mmsc="http://mms.plspictures.com" this is also in cm-13 original apns-conf.xml. If you need more info i will get back to you as soon as i can Thanks again
[Moto G General] tpa-moto:
What I'm trying to say is that adding that APN shouldn't matter, because most likely your numeric is 311870 and therefore the Boost Mobile APN should be. I can't be sure of this without logs though.

I haven't yet understood whether you assumed that the RingPlus entry was needed for MMS or you first tried without it, saw that it didn't work and then added it.

Also, are you using the stock messaging app for MMS? Are they working? Because everybody here says that third party apps are needed.
[Moto G General] HandsomeOne:
tpa-moto

Your zip works , and i found that Sprint "boostmobile" is the one thats working for me , i took out "verizon" and the Ringplus that i put in. I check after clean flash and your zip then checked apnconfig.xml only has Sprint. The stock messaging app works fine for text, i tried to add RingPlus for the mmsc="http://mms.plspictures.com" entry to send and receive picture messaging but did not work. I tried messenger app from Google and it does the same. will be off in a few hours, i will stay in touch. Tnx
[Moto G General] :
[MENTION=6937116]tpa-moto[/MENTION] I added the apk posted and flashed the last zip. I can't edit apns, I do have data and only MMS with a 3rd party app. Here's some logs. Sorry for the wait, I had a rough day at work.

Edit: I had to add a dummy updater-script to that zip again by the way.

Edit: sorry, missed something

u0_a76@falcon:/ $ cat /proc/cmdline
console=ttyHSL0,115200,n8 androidboot.bootdevice=msm_sdcc.1 androidboot.console=ttyHSL0 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 vmalloc=400M utags.blkdev=/dev/block/platform/msm_sdcc.1/by-name/utags console=null androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 vmalloc=400M utags.blkdev=/dev/block/platform/msm_sdcc.1/by-name/utags movablecore=160M androidboot.emmc=true androidboot.serialno=XXXXXXXXX androidboot.baseband=msm androidboot.mode=normal androidboot.device=falcon androidboot.hwrev=0x83C0 androidboot.radio=0x3 androidboot.powerup_reason=0x00004000 bootreason=reboot androidboot.write_protect=0 restart.download_mode=0 androidboot.fsg-id= androidboot.secure_hardware=1 androidboot.cid=0x9 androidboot.bootloader=0x411A androidboot.carrier= mdss_mdp.panel=1:dsi:0:qcom,mdss_dsi_mot_cmi_720p_video_v2 mrom_kexecd=1
u0_a76@falcon:/ $

u0_a76@falcon:/ $ ls -la /fsg/falcon_3.img.gz
lrwxrwxrwx 1 root root 23 2015-08-17 12:07 /fsg/falcon_3.img.gz -> falcon_verizon_3.img.gz
u0_a76@falcon:/ $
[Moto G General] Lucas Eugene:
There is Reliance CDMA in India as well.
[Moto G General] tpa-moto:
Thank you!

OK, I need the output of

cat /proc/cmdline

or give me just the following, which is part of the cmdline

androidboot.cid=0xN #where N is a number

I also need the details of your carrier (and possibly the numeric).

EDIT: I'm worried you all have the same value.

The current detection mechanism is completely broken. /fsg/falcon_3.img.gz is always a symlink to falcon_verizon_3.img.gz. init is using this symlink to determine whether one is on Verizon or not. However, this is not working at all, because amarc78 has the correct numeric. What I think is happening is that init tries to read /fsg before it's mounted and therefore it thinks that no one is on Verizon.

[MENTION=983303]hhp_211[/MENTION] this explains why you had to edit the build.prop.

EDIT2: since you are doing that, could you also give me the output of

md5sum /fsg/0.img.gz

I'll probably need to do this to detect the carrier. These are the values I got from some images:

Boost Mobile 5.1: 46ac94a79513898901b3b37cf7d9c3c8
USC 5.1: f8e4cfd380062e643cfb460c15d08a48
Verizon 5.1: 034c470658f4db2302de4266af89a6bd

This is a really ****ty solution, but right now I can't see any other way.
[Moto G General] :
[MENTION=6937116]tpa-moto[/MENTION]

The output of:

md5sum /fsg/0.img.gz

is:

46ac94a79513898901b3b37cf7d9c3c8 /fsg/0.img.gz

This:

androidboot.cid=0xN

is 0x9

I posted the output of:

cat /proc/cmdline

above, but here it is again:

console=ttyHSL0,115200,n8 androidboot.bootdevice=msm_sdcc.1 androidboot.console=ttyHSL0 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 vmalloc=400M utags.blkdev=/dev/block/platform/msm_sdcc.1/by-name/utags console=null androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 vmalloc=400M utags.blkdev=/dev/block/platform/msm_sdcc.1/by-name/utags movablecore=160M androidboot.emmc=true androidboot.serialno=TA9650LLYY androidboot.baseband=msm androidboot.mode=normal androidboot.device=falcon androidboot.hwrev=0x83C0 androidboot.radio=0x3 androidboot.powerup_reason=0x00100000 bootreason=hardware_reset androidboot.write_protect=0 restart.download_mode=0 androidboot.fsg-id= androidboot.secure_hardware=1 androidboot.cid=0x9 androidboot.bootloader=0x411A androidboot.carrier= mdss_mdp.panel=1:dsi:0:qcom,mdss_dsi_mot_cmi_720p_video_v2 mrom_kexecd=1

Carrier details:

Name: Boost_Mobile

APN: Boost_Mobile

Proxy: <Not Set>

Port: <Not Set>

User Name: Boost_Mobile

Password:

Server:

MMSC: http://mm.myboostmobile.com

MMS Proxy: 68.28.31.7

MMS Port: 80

MCC: 311

MNC: 870

Authentication type: <Not Set>

APN type: default,admin,fota,mms,supl,hipri

APN Protocol: <Not Set>

Bearer: <Not Set>

The numeric is 311870.
[Moto G General] tpa-moto:
OK, this is a good sign. I guess I can at least rely on the md5sum if the cid doesn't change depending on the carrier. One question: the last time you used a stock ROM, did you flash a factory image or updated through an OTA release?

Anyway, I just noticed that all the info I need are in the build.prop of stock images. However, I could only find those for Boost, Verizon and US Cellular.

If your carrier is not among those and you want it to be supported, please provide the following props that you can find in the build.prop of your stock firmware, or post the build.prop as is directly, along with the md5sum of /fsg/0.img.gz (see my previous post). This will be needed mostly for MMS:

ro.build.description
ro.build.fingerprint
ro.mot.build.customerid
ro.cdma.home.operator.alpha
ro.cdma.home.operator.numeric

Along with the md5sum of /fsg/0.img.gz.

If you are using one of the above carriers, please check the md5sum of /fsg/0.img.gz and compare it with the values I wrote in my previous post. If you get something different, please post the md5sum and the carrier name.
[Moto G General] tpa-moto:
While I wait for the outputs of the commands, here a test build that I made for myself and that should work out of the box with CDMA devices. It sets all the needed props and uses the correct APN list. It can be flashed without editing the updater-script.

For now the numeric is set only for Boost Mobile, Verizon and US Cellular (but only if /fsg/0.img.gz has a known md5). I need the md5 hashes for the other carriers. Wrong numeric = no MMS mostly. Mobile data should work, but if it doesn't, add

ro.cdma.home.operator.alpha=something_you_should_know_better_than_me
ro.cdma.home.operator.numeric=something_you_should_know_better_than_me

to the build.prop.

I also added a fix that should prevent Android from changing the numeric to 310000. I already tried something similar, but the APN list was wrong the last time, so I'd try it again. This maybe can do something for MMS.

Here the link: https://mega.nz/#!iIJkyJjY!Ul4yMIzhbfHQka8UvY8Ygv7G3sSPxjqwnWITg_rRelw

If possible, a radio logcat would be nice, even if it works.
[Moto G General] :
I've been using eithereither a stock backup from another broken phone that was updated via OTA update or a stock ROM that I made from that same system IMG. I had trouble getting official firmware to flash with fastboot after updating to 5.0.2 with a OTA soak test and gave up. I can try to flash the official 5.1 radio again if you'd like and see if there's any difference.

One thing I noticed and don't know how I missed it before is this prop in the build.prop of CM13 and other 6.0 roms:

ro.build.expect.radio=0x1|0x4|0x5|0x6

Could this be causing problems?
[Moto G General] tpa-moto:
No, that prop is not needed and no, don't flash the official 5.1 radio. I simply wanted to know if the factory images that are here on the forums differ from the images obtained via OTA, but given what you say, they don't, which is good news.
[Moto G General] :
I did have data, but no MMS with the stock app.
[Moto G General] hhp_211:
Wow you've found some really good stuff here. Thanks!

Sorry for any delays, I did not get a notification that you tagged me...

Here is my info::

u0_a92@android:/ $ cat /proc/cmdline

console=null

androidboot.hardware=qcom

user_debug=31

msm_rtb.filter=0x37

vmalloc=400M

utags.blkdev=/dev/block/platform/msm_sdcc.1/by-name/utags

androidboot.selinux=permissive

zcache

androidboot.emmc=true

androidboot.serialno=TA88107IGT

androidboot.baseband=msm

androidboot.mode=normal

androidboot.device=falcon

androidboot.hwrev=0x83C0

androidboot.radio=0x3

androidboot.powerup_reason=0x00004000

bootreason=reboot

androidboot.write_protect=0

restart.download_mode=0

androidboot.fsg-id=

androidboot.secure_hardware=1

androidboot.cid=0x9

androidboot.bootloader=0x4119

androidboot.carrier=vzw

mdss_mdp.panel=1:dsi:0:qcom,mdss_dsi_mot_cmi_720p_video_v2

u0_a92@android:/ $ md5sum /fsg/0.img.gz

bb992807aab0e62fc37870d9595249b6 /fsg/0.img.gz

I have not had Stock on here since gosh knows when, but not an OTA ... i may have had the soak test installed at some point, but I do remember using/undating the with the "partition.zip" that was around

Also my phone is originally an XT1031 Boost, bootloader unlocked and I have at some point ran the command 'fastboot oem config carrier vzw'

Baseband :: MSM8626BP_1032.390.81.01P

I will try your cm build here soon and report back
[Moto G General] tpa-moto:
Awesome! I didn't know it was possible. I just tried to set 'tpa-moto' as carrier on my XT1032 and it totally worked.

fastboot oem config carrier tpa-moto
...
(bootloader) <UTAG>
(bootloader) <name="carrier"/>
(bootloader) <type="str"/>
(bootloader) <protected=false/>
(bootloader) <value>
(bootloader) tpa-moto
(bootloader) </value>
(bootloader) <description>
(bootloader) This will be used to populate androidboot.carrier
(bootloader) </description>
(bootloader) </UTAG>

OKAY [ 0.035s]
finished. total time: 0.035s

I guess I will use androidboot.carrier to determine the carrier and add an entry in the wiki to let users know how to do it. The numeric shouldn't be necessary for mobile data and this will make everything much easier and maintainable.

The last build I posted will not set the correct numeric for you, because the md5 is not in the list. If you try it, please tell me if mobile data works before you manually add the numeric to the build.prop. In this way I'll know whether not having a numeric set is safe or not, because right now init always sets a numeric, even if it's wrong.
[Moto G General] HandsomeOne:
tpa-moto

Mobile data working before adding to build prop my androidboot.cid=0x9 , md5sum /fsg/0.img.gz on your cm13 and got permission denied. Check permissions all ok looks, like the file is empty? thank you
[Moto G General] tpa-moto:
You have to run 'su' before the md5sum command.
[Moto G General] HandsomeOne:
Boy is my face red :_0 90d44ad3446efada2635f1a65354bbff

90d44ad3446efada2635f1a65354bbff /fsg/0.img.gz

Sorry about that.
[Moto G General] tpa-moto:
Good, this hash is not among those init expects, which means everything should work correctly even without the right numeric (except for MMS).

Now I need to just decide the name for the carriers. I saw that spr, vwz, usc are commonly used for Sprint, Verizon and US Cellular. However, I need to add the support for more carriers and some of these are often under the same name (e.g. Sprint and Boost Mobile). I can also use longer strings, that's not an issue. If you have suggestions, just tell me.

[MENTION=1367165]HandsomeOne[/MENTION]

You said you use RingPlus. If you want it to be properly supported, give me the values of the props you can find here: http://xdaforums.com/showpost.php?p=64884365&postcount=234. You have to take them from the build.prop of a stock firmware for RingPlus.
[Moto G General] HandsomeOne:
I believe they are the same as Stock Boost Mobile? I will flash stock Boost Mobile us 5.1 and check build prop.
[Moto G General] tpa-moto:
If you flash the stock Boost Mobile, you'll definitely end up with the ones for Boost Mobile. Besides, there's no need to flash it, I can just download the factory image and see myself and this is actually what I did for Verizon, Boost Mobile and US Cellular.

Unless stock ROMs don't get garbage from RIL and can get the a true numeric from the network. In that case, flashing a stock ROM might be helpful, but I'd need you to grab a radio logcat soon after a reboot.
[Moto G General] HandsomeOne:
Tried to get it as quick as i could 22.14 was quickest
[Moto G General] HandsomeOne:
Also found these in some build.props i had ???

ro.cdma.home.operator.alpha=Sprint

ro.cdma.home.operator.numeric=310120

ro.cdma.home.operator.alpha=Verizon

ro.cdma.home.operator.numeric=310004

ro.cdma.home.operator.alpha=Boost Mobile

ro.cdma.home.operator.numeric=311870