yashsingh1/xdaforums huggingface dataset:
[Moto G Android Development] kmimix:
I tried 20150120 build and I confirm it works nicely on XT1033 (non-gpe):

* both sims are working correctly

* root is working too, by default.

Found just a couple of minor issues, but I guess it's a CM12 issue: no charging animation when the phone is off and the lock screen in non-customizable (ie., the weather icon is permanent as mentioned in a previous post).

Besides that, everything seems to be running smoothly, thanks a lot for enabling Dual SIM on L :)

---------- Post added at 08:27 AM ---------- Previous post was at 07:43 AM ----------

It does work indeed. Removed lockclock.apk from system/app and the weather icon is gone.
[Moto G Android Development] Lucas Eugene:
[MENTION=4125857]bharat_goku[/MENTION] . I am just speculating but maybe you can get cdma ril working with this As the xt1032 brazil 4.4.4 firmware worked with 3g on my xt1031. So maybe the 5.0.2 would have the files that you require for getting ril working. Also those who have the cdma variant may also try installing this ROM. but there are NO guarantees as it was never tested on xt1031
[Moto G Android Development] harisho_0:
My Sim is not working

First of all i must thank [MENTION=4125857]bharat_goku[/MENTION], this is really a great work. I am using this rom from build#39 and it was working good without any issues.

But unfortunately my rom got updated by the official CM12 update. From then my Sim network is not working. I can access the contacts, read the Network Provider name but the network is not working. No Calls & no data - Please help.

I have even tried to switch to stock rom and come back again. But still i i dont get any error. Some body please help me.. :rolleyes:
[Moto G Android Development] jglm4u:
You got 3g working on a CDMA????
[Moto G Android Development] :
I would like to see the build.prop from this, if you actually had 3G.

Edit: Um, isn't this actually converting your XT1031 to a Brazilian XT1032? If so, that's why 3G works and this is UMTS not CDMA.
[Moto G Android Development] mightysween:
Read it again. He is talking about it working on KitKat and maybe those files helping with lollipop...not saying it worked on lollipop.

Shattered the screen on my main XT1031 a few days ago... Still have a couple but can no longer activate them on Verizon MVNO and can not even do an ESN swap.

Will still check in and help out here if I can.

Oh...and look below at the signature on this post. This moto G XT1031 cdma is running XT1032 4.4.4 umts firmware and has perfectly working CDMA on Verizon where it is detected as an XT1028. Not as simple as it seems. :)
[Moto G Android Development] :
I did read it, and I checkout the link for the firmware. It's installing Brazilian 5.0 Lollipop for XT1032, but you need to install 4.4.4 firmware before 5.0. It's converting to XT1302 umts, changing radios. I've installed ROMs made from the same firmware and it doesn't data just like these CM12 builds because the radio is still the same.
[Moto G Android Development] mightysween:
I was just pointing out that he wasn't claiming to have had 3g on CDMA lollipop, which is what the two responses seemed to assume.

For the record, we tried flashing 5.0 with 4.4.4 radios about 7 weeks ago here...old news. It does not work.

But again, it is not as simple as it seems. There is plenty of reason to think that UMTS retail firmwares will work for cdma devices.... mainly because some DO on 4.4.4

Screenshot from XT1028 CDMA running umts firmware:
[Moto G Android Development] Lucas Eugene:
First no I don't have 3G on lollipop but I am just saying that it would work.

I'm sorry that I'm quoting you all. But I beleive that we can still preserve the radio.

If a xt1031 user flashes the 4.4.4 Brazil firmware. The ota update it. And make a nandroid backup using cwm philz recovery. And then goes back to xt1031 4.4.4 firmware. And flash nandroid backup over it. In that case we can preserve the radio.

I would've tried it but I'm not at my home and moto g is the only device I got with me so I can't flash anything till I get back.

Also [MENTION=3683732]mightysween[/MENTION] I see that you did install 4.4.4 Brazil on your phone. We're you successfull in oat updating to 5.0
[Moto G Android Development] xavier666:
Can any one give me the link to the last official CM11 Nightly? https://download.cyanogenmod.org/get/jenkins/97711/cm-11-20150105-NIGHTLY-falcon.zip

Official link is not working
[Moto G Android Development] :
I know 4.4.4 umts will have working 3G on XT1031 because I have installed it before. What I'm saying is, if this would work with a XT1031 radio, wouldn't the ROM made from this same firmware that I installed this morning have had working 3G instead of signal bars with an exclamation mark and pretty much the same issues as build 29 of these builds?
[Moto G Android Development] Awesomeslayerg:
http://download.cyanogenmod.org/get/jenkins/98839/cm-12-20150124-NIGHTLY-falcon.zip

Has anyone tried the new nightly about removing hardcoded cdma stuff?
[Moto G Android Development] Lucas Eugene:
This rom is cm it has nothing to do with stock Motorola rom.

You could check my previous post for instructions to install 5.0?
[Moto G Android Development] mightysween:
I have been running the Brazilian 4.4.4 stock base since late last summer. Updating OTA breaks radios of course.

Agree that your method *should* work but similar methods to preserve radio when switching bases have failed. I have tried upgrade/downgrade/nandroid method as well as flashing modems directly. no luck.

Theoretically, restoring CM12 nandroid over working CM11 should preserve radio too. But it ends up no service and soft bricks radio requiring flash of stock NON-HLOS.bin to get them working in 4.4.4 again.

Eventually, i think the problem will be traced to some very basic incompatibility in the lollipop base with msm8226 CDMA chip set definitions
[Moto G Android Development] :
I know this ROM has nothing to do with stock. I'm saying installing a ROM made from the same 5.0 firmware in the link you posted gives the same results as this ROM. No data or calls and full signal bars with 3G and a ! . I'm not trying to be an ass and argue but it doesn't seem like you get what I'm saying.
[Moto G Android Development] :
No problem, I'm all for anyone helping. I just think the result of what you are talking about will be the same as what I did. I am going to try this though for the hell of it, when I finally get the files downloaded. It's a lot of GB's! I'm not to worried about screwing up my phone and I've tried just about everything else there is to try with this phone. Thanks for the info by the way. Has anyone seen the release of 5.0 OTA's for 1st and 2nd Gen. Moto G in US and India I think it was? This looks promising. Hopefully Boost will release an OTA soon.
[Moto G Android Development] mightysween:
FWIW, I have not had to flash over CM11/for a least the past 2-3 weeks and no longer have bootloop issues. Just avoid TWRP (for now) and you should be fine

---------- Post added at 01:15 PM ---------- Previous post was at 01:11 PM ----------

I did see the article about OTA today but figured it was just more misreporting about the soak test. The closer the GSM variant firmware is to complete, the closer we are to having CDMA get some attention, so that would be good news.
[Moto G Android Development] :
I was referring to this: https://motorola-global-portal.cust...prod_answer_detail/a_id/103692/p/30,6720,9050
[Moto G Android Development] russ722:
I talked to boost mobile and Motorola about lollipop update and boost mobile was clueless and said they didn't know if we where gonna get lolipop. So I contacted motoroloa and they said rest assured we will get it eventually as its rolling out in batches.
[Moto G Android Development] merothh:
New CM12 Boot Animation

Wooohooooo, new CM-12 boot animation guys :D..................................

LINK:- http://m.youtube.com/watch?v=3zOLt21ndeA

Always hit the thanks button IF I helped ;):o :D.................................................................
[Moto G Android Development] Sik-1:
Boo, very boring, compared to the old ones they had
[Moto G Android Development] :
That is just as boring as a spinning arrow. The Temasek boot animation is much better.
[Moto G Android Development] harisho_0:
Sorry guys, it seems that i flushed all the radio data (IMEI) using "fastboot erase all".

There is no way to fix it without any backups. If anyone come across repairing Moto G IMEI, pass on the info.

Probably my moto G gonna be as Moto G tablet..
[Moto G Android Development] Awesomeslayerg:
Gonna check todays nightly. Ima try the build props edits because appaerently they fixed the harcoded cdma problem.
[Moto G Android Development] russ722:
Awesome please let us know how it goes.
[Moto G Android Development] Awesomeslayerg:
Appearently, with adding the ro.cdma home operator thingy. It achieved as far as bharat has achived thus far. Incoming calls work and sms is work so no outgoing nor data.
[Moto G Android Development] russ722:
Thanks for the heads up.hopefully OP hasn't given up on CDMA.
[Moto G Android Development] Awesomeslayerg:
Yeah baseband version is showing as well.
[Moto G Android Development] mightysween:
This mainly fixed the roaming menu selections not sticking when changed from menus.

Interesting commit for tomorrow's nightly is that radio images will be generated and recognized separately for fastboot flash packages... This, of course merits some retesting of kitkat fastboot radio files with CM12 as it may be the reason they have failed to function. Or not. :)
[Moto G Android Development] Awesomeslayerg:
Appearently they are going to add the Setup Wizard so lets see if that does anything.
[Moto G Android Development] mightysween:
Yeah. unfortunately at this point I think we are just killing time until motorola pushes CDMA blobs/libs or they are leaked to the community.
[Moto G Android Development] merothh:
Looks like low memory killer issue is gonna be fixed in the next nightly:laugh::laugh:.............................................................................
[Moto G Android Development] srisurya95:
I think you have to edit the title :p its 5.0.2 now :P
[Moto G Android Development] Awesomeslayerg:
Okay something interesting in the nightly i havent followed the thread lately but heres what i got from build 25 of the cynogenmod nightly. https://drive.google.com/file/d/0B7lxB9GyHSD1N3BYM1RhSUtzLWc/view?usp=sharing

It appears to detect cdma, i dont know if its because i flashed a non-hlos bin or i falshed one of those stock radio images but yeah. It appeares to detect the network and when i call in, of course we all know it works but there is no audio from incoming calls. The person who is calling can hear but the person who is hearing from the device cant hear anything.
[Moto G Android Development] mightysween:
Won't boot on mine. Can you check *#*#4636#*#* > phone information and see what you have in CellInfo

Did you have to install CM11 first?

---------- Post added at 07:41 PM ---------- Previous post was at 07:31 PM ----------

The LTE issue is what has been killing us since day 1. If anyone has time, research and test some build.prop edits to prevent CM12 from thinking this is an LTE device.

I called it on 12/26/2014 in post #444 and still think that this is the issue.
[Moto G Android Development] RonZR:
Is this thread going to update?

I wanna know that because of the possible fix of the RAM issue. Apps were getting killed to soon con build 42 that is the last that i usted of this ROM
[Moto G Android Development] mightysween:
If you are on 1032/1033 all changes from here were merged into CM some time ago. Best off running a nightly there if you want to stay current.

All that was left here was to get CDMA running... This was never intended to be a build you would run long-term... OP set out to solve dual Sim and CDMA and push his solutions into CM.
[Moto G Android Development] RonZR:
Thanks

Y es i'm on xt1032 . So is better for me to use the last nightly.Thanks for advice
[Moto G Android Development] :
This should do it you would think:

#

# System props for telephony

# System prop to turn on CdmaLTEPhone always

telephony.lteOnCdmaDevice=0

But I did this and a lot of other build.prop edits to that build earlier today, and the only thing I could accomplish was to get Boost to show for carrier and got settings to show the NV/RUIM options so you could select NV. It won't show anything like signal strength, phone number, etc. in phone status like some of these unofficial builds. The no sim icon won't make way for the signal bars either. It seems like we've been much closer to working than this.
[Moto G Android Development] mightysween:
You would think that would work, but we still register with "CellIdentityLTE" instead of "CellIdentityCDMA" (as it does in KitKat with the same flag present...so it is something else)

The SIM is there for the same reason... CM12 is setting this to a "GSM-like" mode as 4g LTE is SIM based even on CDMA.

If we can stop GSM-like mode, the rest will fall into place I think.

As I have said before, we are probably just killing time until Moto releases code that will force cdma mode

---------- Post added at 09:16 PM ---------- Previous post was at 08:52 PM ----------

ro.telephony.default_network=0

What about this one? We can confirm that there are three network modes by looking in *#*#4636#*#*. The first (#0) is the incorrect one (GSM 850).

So until that is fixed this should be set to 1, which corresponds with Cellular 800. But this alone will not fix as we can test it manually.

Is that key even present? I am unable to test right now unfortunately.
[Moto G Android Development] :
Hmm... I'm not sure about that, and you've got me thinking. Maybe I'll try it before I go to bed.
[Moto G Android Development] fireball0093:
I'm going to give this a try but I'm going to replace the Verizon-specifics with Boost Mobile's stuff, I'll report back in about 20
[Moto G Android Development] mightysween:
Yes, I mentioned to do that in step 4. :)

Thanks, I doubt it will work...but at least this includes everything in one spot so we can start trying to see what needs to be added, removed or changed.

Notice, default_network # is 4... No idea why, I only show one band. So the reasoning of number is escaping me... Left it as 4 just because it is working in stock. And it is fairly certain that 0 is not the correct setting :)

---------- Post added at 10:36 PM ---------- Previous post was at 10:30 PM ----------

Oh, please try it on CM nightly and not older build from here so we have latest base. Rather stick with this thread than start over in CM official
[Moto G Android Development] fireball0093:
I actually just flashed the latest nightly (20150125), so just quick going through setup and then I'm gonna test it out and see if it helps any.
[Moto G Android Development] mightysween:
just removed the quote box on my text... noticed it misformats cut/paste by adding spaces! Make sure it is plain txt, one entry per line, no funky spacing
[Moto G Android Development] fireball0093:
Booting up, here we go! Let's see if it helped at all.

Well, nothing changed sadly after the boot up :/
[Moto G Android Development] bharat_goku:
Build 50

New build up,

Works been a bit tiring haven't been able to compile in a while,finally got time to build today so here it is,

i've made significant changes since last 2 days mostly to frameworks to hopefully fix cdma issues i'm not positive it'll fix cdma state yet,i've pulled somethings from aosp to try and fix cdma for now ,

I may have missed a few lines with respect to cdma to test kindly add the below lines if initial boot attempt doesn't work

ro.telephony.default_cdma_sub=1
persist.radio.calls.on.ims=0
persist.radio.oem_socket=false/true(this is an experimental prop i wanna try in future-try first 2 before u proceed to experimenting with this
[Moto G Android Development] :
Yeah, I tried it too on a couple different builds and no go. I'll try this new build in the AM.
[Moto G Android Development] shadie21:
View attachment radiolog.txt from xt1031 on boost mobile
[Moto G Android Development] bharat_goku:
could u send me a couple of screen shots? i really don't understand what's happening now cos from logs sim state is being set to cdma and boost mobile

Add this line

ril.subscription.types=NV in build.prop along with my older post

Can u confirm CDMA doesn't work? the logs about right >.<
[Moto G Android Development] mbj731:
CDMA doesn't work :/ when first booted, I got the sim icon. Not able to text/call and of course no data. Added your build.prop tweaks you mentioned and got back to the signal bars with exclamation. With that sending text works, calls won't go out and of course no data. I tried many build.prop tweaks in every combo I could and made no progress beyond the signal bars with exclamation.
[Moto G Android Development] manoj36:
latest build stuck on boot animation..need help
[Moto G Android Development] bharat_goku:
what all props did you add?,i'm not sure why but i have a feeling phone is setting to gsm bands instead cdma first and after a while sets to cdma bands ,try sending me a log with the exclamation signal bars?

Kindly check your steps i think you are doing something wrong
[Moto G Android Development] mbj731:
Added these after initial boot didn't work:

ro.telephony.default_cdma_sub=1

persist.radio.calls.on.ims=0

persist.radio.oem_socket=false/true (didn't see that this wasn't needed on first edit..so I'll try without this last line)

Tried these from an edited build.prop you posted for an earlier build.prop you posted:

ril.subscription.types=NV

ro.telephony.get_imsi_from_sim=true

telephony.lteOnCdmaDevice=0

persist.radio.ap.phonetype=2

ro.telephony.default_cdma_sub=1

ro.cdma.home.operator.numeric=311870

gsm.sim.operator.numeric=311870

gsm.operator.numeric=311870

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

gsm.sim.operator.alpha=Boost Mobile

gsm.operator.alpha=Boost Mobile

ro.telephony.gsm-routes-us-smsc=1

ro.ril.svdo=true

Basically I was trying different things just to see if I could get lucky and find a working combination. Haha No real knowledge of build.props, just experimenting and hoping for the best. I'll see if I can get the signal bars with exclamation back without much editing and post a radio log as soon as possible!
[Moto G Android Development] bharat_goku:
Alright just temme when u get signal with log I'll try fixing it in telephony
[Moto G Android Development] manoj36:
I checked everything and done properly.. I unlocked bootloader only to install ur cm12 running rom.. Still stuck on animation
[Moto G Android Development] mbj731:
How long did you wait? First boot can take a while! What recovery are you using? I recommend philz touch 6.58.7 as its always worked for me. Go in to wipe options and "wipe go install new ROM" and then flash CM12 and GApps. Works every time for me.

---------- Post added at 12:25 PM ---------- Previous post was at 12:16 PM ----------

Ok here's what I got. I figured out that a simple edit of the build.prop line persist.radio.apm_sim_not_pwdn=1, changes to 0 gives signal bar with exclamation.(we kind of figured that out in earlier builds) In this state you can send/recieve text and receive calls but not send calls. I did a clean install, promptly edited only that line and pulled this log: https://docs.google.com/file/d/0B-lOZaFdyllSOHRSRTVBS3Z5R2s/edit?usp=docslist_api

With such a simple edit gaining most functionality, it makes me think you're not far off on getting CDMA support. Thanks for your work... And I'm trying to help along the way with my minimal knowledge. :D
[Moto G Android Development] bharat_goku:
hmmmm that change is supposed to save battery on lpm mode that's kinda why my earlier build broke network partially,

in this current build are u able to make calls after making this change and adding the lines i posted earlier?
[Moto G Android Development] mbj731:
I'm not certain that I tried calls with those changes. But any time I've tried to make calls it hasn't worked. Can only receive calls. Text works both ways as long as signal bars are present.
[Moto G Android Development] bharat_goku:
i've modded a few parameters in the cdma prl where excess blank unsols turn up,(found it on the aosp gerrit) to fix issue just give it a shot if it fixes calling
[Moto G Android Development] mightysween:
Yes! Not GSM but a "GSM-like" mode. Verizon/MVNO 4g phones use this mode as they use a SIM card even on CDMA.

CellInfo on working KK builds registers "CelldentityCDMA". On lollipop it registers " CellIdentityLTE" which is a mode that requires a SIM to operate correctly on the network.

---------- Post added at 09:05 AM ---------- Previous post was at 08:53 AM ----------

Also.

I have 100% confirmed that "4" is the correct setting for this build.prop entry... this is the setting for cdma/evdo

ro.telephony.default_network=4

It currently defaults to 0 (correction: wcdma which is hybrid cdma/hspa)

---------- Post added at 09:22 AM ---------- Previous post was at 09:05 AM ----------

Also, this is used on many verizon devices to fix this type of issue:

telephony.rilV7NeedCDMALTEPhone=false

(This one is tricky because normally with a 4g verizon device it would be set to true)

And what about this one:

ro.mot.phonemode.vzw4gphone=false

and this:

persist.radio.lte.mm.disable=true
[Moto G Android Development] russ722:
Same here

ro.telephony.default_network=4. On kit kat rom boost mobile.
[Moto G Android Development] mightysween:
Added a couple more build prop test lines to my last post. Need to swap LCD/digitizer from new G to old so I can start testing. (because cant activate xt1031 esns on VZW anymore!)

[MENTION=4125857]bharat_goku[/MENTION], I know we have a line in build.prop to attempt to set PROPERTY_LTE_ON_CDMA_DEVICE to false.... but how do we ensure that PROPERTY_LTE_ON_CDMA_PRODUCT_TYPE is also being set false? Seems that the product_type will override the cdma_device setting if there is a conflict.
[Moto G Android Development] :
Yes, this should be 4. CM11 was 7. I remember Liquid Smooth had data issues on CDMA and I found changing the telephony.lte.on.CdMaDevice=0, to 1 to get 3G working on that.
[Moto G Android Development] manoj36:
I tried all the exact steps but it still stucks.. Can't keep switched off for long time so had to go back to other rom with single sim cm12.. Ya I was on latest philz recovery..
[Moto G Android Development] moha07:
Guys did anyone know flashing cm12 over a official lollipop will brick the device or not . could someone tell me how to flash cm12 on xt1033

My device is xt1033 dual sim variant and with update boot loader and lollipop installed in it .

Thanks in advance
[Moto G Android Development] dovw:
I have been lurking on this thread for a while - have a Boost xt1031 flashed to vzw and running KK 4.4.4 on PP as an XT1028.

I am relatively new to all of this but it sounds to me like you have this issue https://jira.cyanogenmod.org/browse/CYAN-6020 that the folks using the Galaxy S3 were trying to work on here http://xdaforums.com/galaxy-s3-verizon/help/straighttalk-sch-968c-info-t2960742/

---------- Post added at 05:09 PM ---------- Previous post was at 04:48 PM ----------

To be a little clearer that specific issue was reported for another device - but in essence the problem they describe with their device and the alternatives they are looking for to not have to use a SIM seem to be the same as our issue with the Moto G
[Moto G Android Development] mightysween:
Similar... that was on CM11. There is no CM12 JIRA for "new" bugs yet... and CM claims that cdma IS working on Moto G so we cant file a regression.

I probably sound like a broken record but until we get cdma capable vendor blobs instead of trying to make it work on GSM/WCDMA we are likely just running in circles