yashsingh1/xdaforums huggingface dataset:
[Moto G General] tpa-moto:
You may get working data with the second last build and that potentially fixes MMS for you . I suspect you actually need the correct APNs and the dummy ones are breaking mobile data. You shouldn't need to edit the build.prop, so I'm going to look at the differences between your props and the ones currently set by init and fix that.

So you didn't have to set NV or whatever? You got working data and signal right away?

These should be the needed patches (they are 4): http://pastebin.com/raw.php?i=UsPKq0u8

I really don't know. There are few things that need to be fixed properly and I won't have much free time in the next days. The main problem for me is not being able to directly test the changes.
[Moto G General] hhp_211:
Sorry, so excited, I forgot to to say that I did change setting to NV

Yeah I also forgot about the mms app problems with stk app from cm not working. I'll give it another shot with the working app and without the prop edits

and get some logs for you
[Moto G General] tpa-moto:
https://github.com/CyanogenMod/andr...mmit/d41c0417028ce25bbb79b6b0f787ce0cfc104811

So, try to replace

ril.subscription.types=NV,RUIM

with

ro.telephony.default_cdma_sub=1

and then do a data wipe. I hope this will make NV the default option.
[Moto G General] :
That did it. Settings are all selectable and the NV/RUIM option is not there. Calls and SMS work, and MMS works with 8sms but not with stock apk.

Edit: carrier label also still says Boost Mobile (which is correct).
[Moto G General] hhp_211:
Care to share the build? I know I'd like to try it out
[Moto G General] tpa-moto:
Great!

I noticed something interesting in your last log:

12-17 18:30:47.579 D/DCT ( 1750): [0]createAllApnList: selection=numeric = '311870'
12-17 18:30:47.585 D/DCT ( 1750): [0]createApnList: X result=[[ApnSettingV3] Boost Mobile, 1543, 311870, n.boost.ispsn, , <web url omitted>, 68.28.31.7, 80, , -1, default | supl | mms | fota | dun, IPV4V6, IPV4V6, false, 13, 4096, 0, false, 0, 0, 0, 0, , ]

This is new. Too bad this APN gets overwritten by a dummy one.

Here a build that doesn't force dummy APNs: https://mega.nz/#!KcITEZCC!KGSJWVoZ5OgSzhikLRBwrTzfOmkM_8_zZwRnmTcFHSA

"ro.telephony.default_cdma_sub=1" is automatically set by init.

If this works, I'd like to try a bunch of simple changes to see exactly which are the ones we need. I'll simply post flashable zips. However, uploading complete builds is not a problem for me, so if you prefer that, just tell me.
[Moto G General] :
Downloading now. What ever you think is best is fine with me. As long as your sure new builds aren't necessary, I'm fine with that. I'll post a log for this one shortly, I just left work.
[Moto G General] :
[MENTION=6937116]tpa-moto[/MENTION] this time I have no data or MMS, but do have calls and SMS.
[Moto G General] tpa-moto:
Thanks. It looks like we need the dummy APNs after all.

Let's try to preserve the APN and add the dummy one: https://mega.nz/#!jF5RDIBC!N8BYAb0FDGezrARPv-T4z43Gq4qaa_rQd7oQVp95NNI (flashable zip)

EDIT: and here to have the one that worked, in case you want to use this build: https://mega.nz/#!aYRDlRZR!3XnKwz1vqV9G2U6UBNNbU2rM0fapMCmK1eGMqlvlkIk

----------

EDIT2:

I can see in that CM-12.1 log that it's not using any specific APN for MMS, that's strange. I then guess that keeping the APN will not make any difference. So, ignore the above requests and try this: https://mega.nz/#!fUZSBaiY!27zPg_47SjIFbi39kzmcecqQIsCQY8kL-lBqzVhZin4

If this works, I'm going to publish on gerrit all the changes I used for this that are not there yet.
[Moto G General] :
Didn't work. No data, calls or anything, the no sim icon back and settings greyed out again.
[Moto G General] tpa-moto:
Thanks! I published all the changes that we need: http://review.cyanogenmod.org/#/q/topic:cdma-nv + http://review.cyanogenmod.org/#/c/123835/

The one that creates the dummy APN profile is needed, but there might be a better way to achieve the same. The only issue left is MMS, I hope some other dev with a CDMA phone will look into that, we can't be the only ones with this issue.
[Moto G General] mrfeh:
So - is there an ETA for when these changes will be part of the CM 13 nightlies?
[Moto G General] :
And you said you didn't think you'd do it. Thanks again for your time and effort!

[MENTION=983303]hhp_211[/MENTION] if you haven't already, can you test this? I'm curious to know if you have the correct carrier label or i f you get Boost Mobile. You'll need to flash the ROM, the first flashable fix above, and Gapps all at once or you'll get fc issues.
[Moto G General] n0ts0smart:
If you are looking to 5.1 for an answer to MMS/SMS issues. I think its worth noting that (at least for me) that I haven't been able to send MMS or SMS with the stock CM messaging app in any ROM that had it. However if the rom has the AOSP messaging app I can send both with no issue.

I have a Boost XT1031 and its pretty much the first thing I do is get a third party app that lets you manually set the APN as soon as I flash a ROM.
[Moto G General] tpa-moto:
Not really. The changes must be reviewed and I don't how much this will take.

This shouldn't happen, but at least now everything makes more sense. I couldn't understand how cm-12.1 was able to get working MMSs with a dummy APN profile. However, it's strange that you need a third party app for SMSs, those should work.

Anyway, from what I could find on the internet, CDMA needs APNs only for MMSs. So a _possible_ solution would be excluding 'mms' from the dummy profile and use the real APN for that.
[Moto G General] :
Anyone who can't wait to start flashing CM13 nightlies with working data can use this fix. I'm posting right now on the 12/20 nightly on 3G. You'll need to remove the radio assert in the updater-script, but other than that just flash the ROM and Gapps and boot. Then flash the zip from the first link in post #114 by tpa-moto and the file I attached below to add the necessary line to the build.prop. Be sure to wipe data before rebooting or you'll get f/c's. Enjoy!
[Moto G General] mmims24:
Great work everyone! As soon as they fix CDMA on cm13 nightlies I guess it will be time to close this thread big thanks to [MENTION=6937116]tpa-moto[/MENTION] [MENTION=5768732]amarc78[/MENTION] [MENTION=4785615]inyourface09[/MENTION] [MENTION=3683732]mightysween[/MENTION] !! You guys are all amazing, and I, as well as the rest of the CDMA users out there appreciate the work. I'm happy we could come together yet again to make it happen! :)
[Moto G General] tpa-moto:
Can someone grab a logcat while using nodummy.zip? Probably the log is already somewhere here, but I didn't properly keep track of the changes and I'm not sure which is the right one.

Here workingsolution.zip taken from a previous post.
[Moto G General] :
Here it is.
[Moto G General] tpa-moto:
I've just noticed something that could explain why cm-12.1 could create the dummy profile and cm-13.0 can't: http://review.cyanogenmod.org/#/c/125084/2/, which is a less intrusive change compared to forcing the dummy profile.

New test: https://mega.nz/#!SM5QwKjD!K07e5e0mVRsEOz7NuVjJipJNIs5HZOm8bdHEAdn5-7g

This zip takes care of adding the needed prop if not already available in the build.prop.
[Moto G General] :
I'll try to remember to name these logs to help keep track of them.
[Moto G General] n0ts0smart:
Just a curious question but do these patches break anything for non CDMA phones?
[Moto G General] toasterboy1:
Just to clarify.

I can flash the build from here: http://download.cyanogenmod.org/?device=falcon and Gapps.

Just looked in the CM13 zip. Do I remove the whole line that starts with assert(getprop("ro.boot.radio") or just before the pipe || ?

Then flash CM13-prop-fix.zip and dummy-apns.zip or workingsolution.zip

Is MMS working?
[Moto G General] tpa-moto:
Thank you. Don't worry, I'll keep track of them. Hopefully you won't need to take any more logs. The APN hack was the only change I really didn't like, but I can see from your log that the last solution I found is working.

No, they are not affected. In fact, I'm including these changes in my own builds.

Remove:

assert(getprop("ro.boot.radio") == "0x1" || getprop("ro.boot.radio") == "0x4" || getprop("ro.boot.radio") == "0x5" || getprop("ro.boot.radio") == "0x6" || abort("CDMA devices are not supported at the moment."););

And you can just flash the zip I posted here to fix CDMA: http://xdaforums.com/showpost.php?p=64444381&postcount=125

If you are a Boost Mobile user, MMSs will probably not work. As I understand it, MMSs require a proper APN config, but right now no real APN profile is set up, so you'll need to use a third party application that allows to specify APNs.
[Moto G General] tpa-moto:
I really don't understand what's the problem here.

The code queries the database (/data/data/com.android.providers.telephony/databases/telephony.db) which contains all the APNs, but for some reason no APN is found. This is really strange. What does the following command return?

sqlite3 /data/data/com.android.providers.telephony/databases/telephony.db 'SELECT * FROM carriers WHERE numeric=311870'

This is for Boost, change the value of 'numeric' if you want to use this for other carriers, or run

sqlite3 /data/data/com.android.providers.telephony/databases/telephony.db 'SELECT * FROM carriers'

to get all the APNs in the database (they are a lot).

I'd like to also see the output of:

sqlite3 /data/data/com.android.providers.telephony/databases/telephony.db 'PRAGMA table_info(carriers)'

I suspect that the subId in the database is not correct or missing.

EDIT:

I think I found the problem. The operator numeric is not correct, it's initially set to the correct value, but it's then changed to something else.
[Moto G General] tpa-moto:
(Probably ugly) solution for MMS: http://pastebin.com/raw/9jMc9fsw

This is an all in one zip, it includes all the fixes.
[Moto G General] toasterboy1:
Thanks for the response. Tried last night with 12/20 and 12/23 and different combinations of the patches. Could not seem to get wifi to work. It keep dropping and reconnecting. Never was able to connect to cell network at all. Just a no sim icon. I will keep following the progress. Thanks to all of you for your hard work.
[Moto G General] n0ts0smart:
Actually I'm on a LP ROM at the moment but would adding the correct operator numeric value to the build prop be a workaround for this?

And probably a stupid question but could the fix for CDMA work on any ROM based on cm13 or specifically the CM 13 nightlies?

[MENTION=6937116]tpa-moto[/MENTION] you are a beast.
[Moto G General] :
Still no MMS.
[Moto G General] :
It won't work unless a flashable zip is made for each specific ROM. It might work on something almost pure CM like Temasek builds, but I didn't try that one yet.
[Moto G General] Andvark:
Works with Temasek for me, but not the ROM I was really hoping for: Ressurrection Remix M. It boots with continuous "com.android.phone has stopped" errors.
[Moto G General] tpa-moto:
Of course...

And sorry, I forgot to say that I need a generic logcat this time, the radio one doesn't include anything related to MMS.

WiFi is a hit or miss with cm-13.0. Several users reported random disconnections. It's not happening to me, so I haven't really looked into that yet.
[Moto G General] :
Here you go.

That is because the framework is different from pure CM13.
[Moto G General] tpa-moto:
Unfortunately I couldn't find anything useful there, aside from

12-23 15:02:01.499 W/MessagingApp( 2606): canonicalizeMccMnc: invalid mccmnc:null ,null

However, unlike for the framework, the code handling MMS mostly reports failures, so I don't know if the above errors gets resolved later at some point. I'm not sure of this because few lines above that one there's

12-23 15:02:01.651 I/MmsService( 1689): MmsConfigManager loads in background mcc/mnc: 311/870

so it knows the right mcc and mnc and the first error is probably due to the fact that the background thread didn't do its thing yet (these messages are separated by 152ms).

The lack of debug messages makes everything a lot more complicated and not having a CDMA phone to play with is the major issue here.

At least I'm not seeing the errors [MENTION=4785615]inyourface09[/MENTION] posted, but I'm not sure this is good, because those appear when the phone is trying to send an MMS.
[Moto G General] hhp_211:
This may or may not be useful,,, but here is a log taken while using 8sms in debug mode to successfully send an mms

I'm on Broken ROM android 6.0 it's not cm13, but is using your tweaked settings.

View attachment 3587042

Link to 8sms app

http://8s.ms/material-theme-for-8sms
[Moto G General] fireball0093:
I wish I could test but I no longer am on Boost Mobile. I might renew my service for one month if you guys have a potential fix for CM 13. Keep me updated!
[Moto G General] mmims24:
[MENTION=5778309]luca020400[/MENTION] do you have the link to where you added boost Overlays in cm12.1 that could help [MENTION=6937116]tpa-moto[/MENTION] resolve the no eri with 31000 issue.
[Moto G General] :
Could you please upload a copy of the telephony-common.jar from this build you are using?
[Moto G General] hhp_211:
View attachment 3588817

Sure, not much of a Christmas present but I'm sure you enjoy the time spent with it!:D
[Moto G General] n0ts0smart:
I have been watching this thread from the beginning and occasionally checking the cyanogenmod code review but to my surprise the needed commits are still open. Is there anything that might help get them merged or is that just pretty much how it works?

Kind of a shame knowing the fix for CDMA is there and working but not merged yes?
[Moto G General] tpa-moto:
I'll post here when nightlies are available for you. You can also just look at the changelog for falcon, the commit message will probably be something like "falcon: Allow to install cm-13.0 on CDMA variants".

Meanwhile, I left a comment in one of the changes to push for the review, it's been a while now.
[Moto G General] :
Looks like something's happening.

http://www.cmxlog.com/13/falcon/

Edit: maybe not.
[Moto G General] mrfeh:
in CM 13?

Can anybody confirm these changes are in the CM 13 nightlies?

Thanks.
[Moto G General] :
No.
[Moto G General] :
It's confirmed now. The changes will be in the next build.

http://www.cmxlog.com/13/falcon/
[Moto G General] yourrealking:
Does this mean I can install the next nightly build using the update menu, without seeing "CDMA devices are not supported at the moment"?
[Moto G General] :
I would assume so.
[Moto G General] tpa-moto:
Sorry, but one patch is still missing: http://review.cyanogenmod.org/#/c/125084/.
[Moto G General] n0ts0smart:
Thank you [MENTION=6937116]tpa-moto[/MENTION] for the extra efforts to get this merged. Was beginning to think about going to a new phone but not now.
[Moto G General] tpa-moto:
I forgot to say that you can easily use the current nightlies. You just need to remove three APNs from /system/etc/apn-conf.xml and make sure they are not already in the APN database.

Here attached a zip that edits the APN list (and adds the needed prop if missing) and another one that clears the database (this is needed in case you used cm-13.0 once already or forgot to flash the other zip).

You still need to remove the asset manually from the updater-script though.

I hope it won't take another month to review the commit that is missing. This is taking reeeeeeally a lot of time.
[Moto G General] :
Very nice, thank you. I tried the last nightly, but could only get signal bars but no 3G and gave up.

Edit: [MENTION=6937116]tpa-moto[/MENTION] the zips work fine, although I had to revise them. They needed a dummy updater-script to direct to the shell script update-binary. I hope you don't mind I attached a combined, revised zip. I tested it, and it works fine. It has to be flashed before Gapps on first install, and to update flash the ROM, the fix and wipe dalvik/cache.
[Moto G General] tpa-moto:
I don't mind at all and thanks for trying again, I was worried I had to start all over again, because I was quite sure this was all you needed.

I find the updater-script thing weird.

When you install a zip, recovery simply extracts updater-binary and executes it. As long as it's something executable, recovery doesn't care. The updater-binary that you usually find in flashable zips is a binary that parses the updater-script and executes the commands in it. In this case, updater-binary is just a shell script and it doesn't need an updater-script file. Maybe I did something wrong, I think I tried the zips before posting them, but I'm no longer sure.

Anyway, I'd say that wiping the dalvik is almost never needed, Android is pretty smart and understands when it needs to be recreated. Wiping the cache is really unneeded.
[Moto G General] Phrodini:
Great thread. Y'all put in a lot of work on this marshmallow ROM ..can't wait to finally try it when its available
[Moto G General] :
When I mentioned trying the last nightly and only got signal bars, this was before trying your fix. I found if I don't wipe dalvik after updating the ROM, I get FC's with some apps, mainly setup wizard, and other Gapps. This is also why a recommended flashing the fix before Gapps on initial installation. It's a habit to wipe dalvik and cache at the same time, that's why I said that. Thanks again.!

---------- Post added at 03:29 PM ---------- Previous post was at 03:23 PM ----------

Maybe I'll post some hassle free unofficial night lies until everything is merged. I have an idea. Stay tuned.
[Moto G General] :
Here's the 1-11-2016 nightly fixed to just flash away.

https://mega.nz/#!JtYnhKIZ!5tJCQekX4niZej-2D-wTZ1FXABWwjFksIU0PPAz8fWs

Edit: CM 13 sources:

https://github.com/CyanogenMod
[Moto G General] Phrodini:
Thank you..
[Moto G General] mmims24:
[MENTION=5768732]amarc78[/MENTION] everything seems to be working fine here, Google play services FCs but I think that's a gapps issue. [MENTION=6937116]tpa-moto[/MENTION] will the zips you uploaded work on AICP mm or other cm13 based ROMs or just official cm13 nightlies?
[Moto G General] Phrodini:
2.63 root worked for me, was having trouble with 2.52. Thanks for the Rom
[Moto G General] mmims24:
So I flashed AICP 20160111.zip, then flashed the combined zip by [MENTION=5768732]amarc78[/MENTION] of the two posted by [MENTION=6937116]tpa-moto[/MENTION] and then opengapps mini. Works like a charm, so I can confirm modified zip works for AICP and probably all cm13 based roms
[Moto G General] :
Yes, it should work on anything built after 1-10. CyanPop works also. https://mega.nz/#!chAUCaza!9dAETsiwuCf9H9hFYLXeT932pS-Not6SJ3omWtXezPo

Edit: just incase, CyanPop sources https://github.com/CyanPop

https://github.com/CyanPop-Devices
[Moto G General] Phrodini:
thanks for the cyan rom..going to try the modified zip before flashing gapps..was having the FC on google services also
[Moto G General] :
No need to flash the fix zip. It's integrated into the ROM zip.

Edit: Resurrection Remix https://mega.nz/#!4gJHSK4T!AuKjirO3SFEdPktav8coFTpkSKQoUgjgZir2t_oj56M

Sources: https://github.com/ResurrectionRemix

AICP https://mega.nz/#!kpwwQACJ!fXOiunfBLcjwOBkYB4nP9bUF9dp4DTqndF4HKPThGaI

Sources:

Kernel: http://goo.gl/At7Skd

ROM: http://goo.gl/6MoXYN
[Moto G General] mmims24:
Did cm team merge the last patch or is the patch only in cyanpop as of now?
[Moto G General] mmims24:
Or did you integrate it into the ROMs you posted?
[Moto G General] :
I integrated it into the ROMs I posted.
[Moto G General] mmims24:
I appreciate that, cause when I was installing AICP last night I did full wipe only to realize I forgot to edit the updater script ?
[Moto G General] Phrodini:
really appreciate it
[Moto G General] toasterboy1:
Many thanks for this! Running Resurrection Remix on XT1031 flashed to PagePlus. No data left on plan to try anything else but phone and sms work! Thank you guys for your hard work and keeping this cheap little phone alive!
[Moto G General] Phrodini:
Resurrection remix runs great..smooth,no reboots and everything works. Thank you

---------- Post added at 03:30 PM ---------- Previous post was at 03:24 PM ----------

Think its integrated , I tried both
[Moto G General] mrfeh:
Anybody know if I need to do a factory reset if I'm upgrading from CM 12.1?
[Moto G General] :
You can supposedly do a dirty flash to update, but that was with the first CM13 builds. I'm not sure about now, but I say try it and see what happens. Worst thing that can happen is a bootloop and you'll have to do a wipe then.

---------- Post added at 03:47 PM ---------- Previous post was at 03:47 PM ----------

It is integrated, I added it to the updater-script.
[Moto G General] mrfeh:
I can't install the UNOFFICIAL_CDMA_cm-13.0-20160111-NIGHTLY-falcon.zip file. I get:

E: footer is wrong

E: signature verification failed

I tried both sideload and from internal storage. Same result.
[Moto G General] :
Disable signature verification in recovery, the zips aren't signed.
[Moto G General] mrfeh:
Bummer. I'm running cyanogen recovery, and there doesn't appear to be a way to disable signature verification.
[Moto G Q&A, Help & Troubleshooting] RadiNash:
Hi everyone,

First, thanks everyone for all the information I have found in this forum for the past few weeks.

Now my problem : I have a Moto G 4G XT1039 that keep losing signal randomly. The only way to get my signal back to call or receive sms seems to be a reboot of the phone.

I don't remember exactly when it started but I think it was around June. Until a month ago I never tried to root or flash my phone. I just used the official updates from Motorola. I live in France and the phone is perfect for me except this problem.

I read here and there that a lot of people seems to have the issue but I'm surprised nobody seems really pissed of.

I downgraded to 4.4.4 to see if it would solve my problem but it did not. I read that the signal loss could be caused by Android 4.4.2 so should I downgrade further ?

This weekend I flashed a nightly from CM 13, the problem is still here.

What can I do ? The problem seems to be related to the radio firmware, can I downgrade the radio firmware and keep a recent android or CM13 ?

For information my baseband version is m8926_309101.02.03.14r.

I'm not sure I post my problem in the good forum but it could help other people in my situation.

If someone has an idea....

Thanks
[Moto G Q&A, Help & Troubleshooting] lost101:
Firstly try the Stock ROM and Radio Firmware available here: http://xdaforums.com/moto-g/4g-development/rom-stock-motorola-4g-lollipop-rom-t3142816 - follow flashing instructions to the letter - after this you can move on to CM13 if desired.
[Moto G Q&A, Help & Troubleshooting] RadiNash:
Well I have already done that, after I tried the 4.4.4 version.

I was on 5.1 then I downgraded to 4.4.4 then got back to 5.1 then tried CM 13.
[Moto G Q&A, Help & Troubleshooting] lost101:
Did you fastboot flash the Radio Firmware from that thread? Commands are in FAQ.
[Moto G Q&A, Help & Troubleshooting] RadiNash:
Yes I did. I event tried to flash the 5.1 radio firmware while still having the 4.4.4 android.

The baseband version I gave in my opening post is the last one for the EU region I believe.
[Moto G Q&A, Help & Troubleshooting] lost101:
Other Solutions to try:

1) Change SIM card / get a new SIM

2) Fastboot flash the Stock Factory Firmware Image for your phone - http://xdaforums.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795/post64203816
[Moto G Q&A, Help & Troubleshooting] RadiNash:
Thanks, I was going to order a new sim card to try this solution.

I already flashed the latest stock firmware last week but i will try again from scratch to be sure.
[Moto G Q&A, Help & Troubleshooting] lost101:
Provide fastboot logs (copy and paste command prompt) when flashing the firmware image. Fastboot may not provide errors, "okay" can mean total failure.
[Moto G Q&A, Help & Troubleshooting] RadiNash:
Hi,

Just to say that there is apparently no more signal loss with the CM13 nightly from 12/11. I hope it will last.

In the end I didn't flash stock firmware.

Thanks again for your suggestions, I will come back if the problem is back.