yashsingh1/xdaforums huggingface dataset:
[Moto G Android Development] bharat_goku:
I don't think they are specific cdma blobs ,see to fix dual sim i had to test roughly 214 odd vendor files check dependencies only then did i rebuild my roms around em,it wasn't exactly a dual sim blob i found it was just finding all dependencies related to the ril which i had to figure out which seemed to fix dual sim state ,since it's detecting phone state and getting baseband + also sms +incoming is working it's just a minor bug i have definitely missed it could be a prop or it could be a missing setting somewhere it's very minor for sure just hard to search for it

Thanks to [MENTION=341683]cybertron[/MENTION]™ for the new awesome wallpaper :)
[Moto G Android Development] mightysween:
Part of me still believes this... that if we disable GSM and LTE altogether we should be able to test CDMA and see it work. But the other part knows that Motorola did not release anything specifically for CDMA moto G... there is going to be a RIL release at some point that will make cdma work. In the meantime, we are still looking for a workaround.

Did anyone test those 3-4 props I posted earlier? All attempts to stop LTE

hopefully I can get up and running on XT1031 again today
[Moto G Android Development] dovw:
I'm groping in the dark here beyond my understanding but the guys on the Galaxy S3 thread blamed their problem on this change for L:

// Hack for Lollipop

// The system now queries for SIM status before radio on, resulting

// in getting an APPSTATE_DETECTED state. The RIL does not send an

// RIL_UNSOL_RESPONSE_SIM_STATUS_CHANGED message after the SIM is

// initialized, so delay the message until the radio is on.

and really getting out of my depth it seems that some ROMs have custom code to address the issue:

http://xdaforums.com/showpost.php?p=58016114&postcount=1092
[Moto G Android Development] mightysween:
That is a RAZR thread... a similar issue except we actually dont have a SIM slot at all.

The delay is interesting because I noticed yesterday that kitkat stock has a 5 second delay built in.

More important question for us may be why are we polling SIM at all on a device with no slot?
[Moto G Android Development] dovw:
Only the second thread is a RAZR thread - the Galaxy guys complaining about a very late CM11 build that had incorporated L changes were the first to point to it http://xdaforums.com/galaxy-s3-veri...-968c-info-t2960742/post57379110#post57379110

---------- Post added at 07:20 PM ---------- Previous post was at 07:08 PM ----------

From the Galaxy thread it seems like it might be a CM thing:
[Moto G Android Development] mightysween:
Ahhh... missed the first link. Same idea, though. But again -- why do we need the SIM logic at all (other than to have a multi-variant build)? Those devices have actual SIM slots that need to be bypassed to prefer CDMA. In our case, the RIL seems to believe that this device is SIM capable (either GSM or LTE) so it is a matter of telling otherwise.

In other words, have we reached a point here where the solution may be to test a single variant CDMA build rather than try to accommodate the GSM variants on a SIM-free device?
[Moto G Android Development] dovw:
You may be answering your own question - if on the multivariants CM's L architecture is now "get imsi from sim on vzw variants" and there is no simple workaround in that code then a single variant build may be the better option
[Moto G Android Development] fireball0093:
I have all day tomorrow off from work, so after about 1PM EST I can be a guinea pig for tests for the xt1031. Just throwing that out there :p
[Moto G Android Development] mightysween:
Bunch of really interesting Verizon LTE commits for next nightly... still trying to digest them.
[Moto G Android Development] russ722:
Cool,maybe this is what we've been needing.
[Moto G Android Development] mightysween:
Unfortunately, no. Verizon CDMA on CM12 still means 4g LTE with a sim card.

http://review.cyanogenmod.org/#/c/86568/

There is also a commit to toggle LTE off... but I dont think it will matter because it still is going to be expecting the sim
[Moto G Android Development] russ722:
Damn got me excited :(
[Moto G Android Development] mightysween:
Still worth looking at as it may open up some additional props that may be of use for disabling LTE altogether on xt1038/1031
[Moto G Android Development] Guru.Eclairs:
Two really important Questions-

1. If we update from kitkat to official 5.0 OTA and then flash cm12 (official/unofficial) in that lollipop upgraded phone, then what are chances of bricking the phone?

2. We know that Upgrading from kitkat to lollipop OTA also upgrade bootloader of device. But if we don't upgrade to official update and instead flash cm12, then will the bootloader be upgraded or remain same as kitkat?

Please clarify.
[Moto G Android Development] Sik-1:
You answered #2 in #1 smh
[Moto G Android Development] Guru.Eclairs:
No you didn't understand my questions clearly. Official Lollipop and CM12 are referred as two different terms.
[Moto G Android Development] mbj731:
CM12 will not upgrade the bootloader. Also, I don't know of any problems with flashing CM12 on devices that have received an OTA update.
[Moto G Android Development] Guru.Eclairs:
But upgrading bootloader is very important as it ensures future OTAs. At some time, even cynogenmod will require latest bootloader for furthur nightlies. So is there any other method for flashing lollipop bootloader in CM12?
[Moto G Android Development] OldYellowBricks:
YO HOLD UP...who gave you the idea that cm12 will require newer bootloaders in the future? Receipts please.
[Moto G Android Development] Guru.Eclairs:
Well if you search cyanogenmod forums, then you will find that various samsung and nexus owners could not install newer nightlies due to bootloader and modem being not supported. So cyanogenmod provided them bootloader and radio zip files to flash. I can give you many CM forum links if you want. And I'm not declaring it WILL require newer files, I'm just saying there is a good probability.
[Moto G Android Development] OldYellowBricks:
gatdam!!!!! things just a whole lot more comlicated!!
[Moto G Android Development] mbj731:
Installing an Brazilian or Asian OTA upgrades the bootloader. But it also causes problems on our device from what I understand. So, the best solution is to stay on the old bootloader if you want to install CM12. By the time OTAs come out for all variants in all regions, maybe everything will be compatible with the new bootloader.
[Moto G Android Development] dovw:
If my suspicion is correct that back at the end of December CM's L change in CM11 for the Galaxy S3 to "get imsi from sim on vzw variants" was also made in CM11 falcon builds then:

1) We can open a bug with High Priority against CM11 that the xt1028/xt1031 are broken because they have no SIM at all (unlike the Galaxy S3 which at least has a klooj workaround of putting in a $6 SIM card)

2) CM can't say that CDMA is working for L when they broke 3G CDMA by introducing an incorrect SIM dependency - the US carriers will be upgrading the the xt1028/xt1031 with L and so (unlike the Galaxy S3) these are obviously not legacy devices - if the carriers - Verizon and Sprint are supporting these devices - should CM be any worse than the carriers?

---------- Post added at 04:59 PM ---------- Previous post was at 04:47 PM ----------

To determine whether our issue with the xt1028/1031 in falcon is a "get imsi from sim on vzw variants" change ISTM we would need someone to look at the falcon nightlies and:

1) see if this code is in the falcon builds

2) if so verify when it was introduced

---------- Post added at 05:10 PM ---------- Previous post was at 04:59 PM ----------

3) verify that builds with a base prior to that change work on the xt1028/xt1031 and builds with a base subsequent to the change break
[Moto G Android Development] mightysween:
Only one big problem with all that... CDMA is not broken for falcon in CM11.

The AOSP 4.4.x RIL was updated at some point and fully supported 3g only variants. Eventually this will happen for 5.0.x as well.
[Moto G Android Development] bharat_goku:
Could anyone on my last build add/modify these lines in build.prop for CDMA and report back?

ro.telephony.default_network=8

ro.cdma.subscribe_on_ruim_ready=true

telephony.sms.pseudo_multipart=1

persist.radio.mode_pref_nv10=1

persist.radio.snapshot_enabled=1

persist.radio.snapshot_timer=22

persist.radio.dont_use_dsd=true

telephony.lteOnCdmaDevice=0

ro.ril.set.mtusize=1422

ro.ril.svdo=true

ro.ril.scan.selection.rat=1
[Moto G Android Development] mightysween:
Just got my LCD/digitizer switched over... what a pain in the butt.

Will try this as soon as I can get everything downloaded.

Curious...Why "8" for ro.telephony.default_network?
[Moto G Android Development] :
Didn't seem to make a difference. Here's a logcat and radio log:

https://docs.google.com/file/d/0B4-30E6G5pbIRjRFRngtNFU0emM/edit?usp=docslist_api

https://docs.google.com/file/d/0B4-30E6G5pbIeUk2YURKNkdkd2s/edit?usp=docslist_api

Edit: network 8 is for Boost LTE isn't it?
[Moto G Android Development] russ722:
Not sure but 4 is boost mobile
[Moto G Android Development] mightysween:
grrr... New digitizer isnt working. sorry can't test right now.

The default_network isn't carrier specific...it defines what radio technology is used by default. 4 is CDMA/EVDO, 5 is just CDMA 1x, 6 is just EVDO.... not sure what 8 is.

Edit: should also note that these numbers vary from device to device... I derived these three from comparing stock KitKat and Cm11 and am assuming they would not deviate I CM12. could be wrong

Wonder why no matter what we set it as, it always ends up the same...
[Moto G Android Development] bharat_goku:
Well 8is for CDMA/evdo/LTE that's why I added the lteoncdma prop to disable LTE wondering if nv gets broken in CDMA/evdo ,there are significant changes in the network types so I'm really confused which prop to utilize for nv platforms last time when I used a custom ril it broke the network settings some device found a work around by including the stock cm12 ril header but I'm worried it might screw up the same for all devices
[Moto G Android Development] dovw:
Yes, I tested both cm-11-20150105-NIGHTLY-falcon and cm-11-20141223-NIGHTLY-falcon on my XT1031/XT1028 and 3G CDMA works on them - obviously no sim dependencies in those builds.

One thing I still do not get though is why we can't have a regression bug against CM12 for 3G CDMA devices that have been broken by the sim dependency
[Moto G Android Development] tzzeri:
Big problem. I have no network on xt1032 (xt1033) firmware. I checked the APN and it didn't list any. I tried adding it manually, but it didn't add. I took the APN config and APN lib files from stock ROM and put it in this one and changed permissions, but that didn't do anything. Anyone know what to do? Edit: whenever I go to apns, it says 'access point name settings is not available for this user [MENTION=4125857]bharat_goku[/MENTION]
[Moto G Android Development] mightysween:
Regressions are for something that WAS working in one CM12 nightly and was broken in the next...CDMA was never working so it doesn't fit the bill.

Of course, CM official site also claims that CDMA is working... So in a way, maybe we CAN file a regression. :)

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

Current builds here are experimenting for XT1028/1031 support. You may be better off on CM nightly which should support xt1032/33 fine
[Moto G Android Development] bharat_goku:
That's not quite possible I'm running it on my phone and it works fine
[Moto G Android Development] dovw:
I am not at all convinced that we needed a working CM12 nightly - as long as we had earlier nightlies that worked - which we did with the last CM11 nightly on January 5th - but I see that we anyway have a different problem. In the Nightlies Project in JIRA they say the following:

Problem for us is that on the status page Falcon was witheld by maintainer at M6 back in May (well over 3 months ago) - so on technical grounds we are OOL on CM support. Practically it makes little difference - no-one else is maintaining falcon within CM so the work anyway needs to be done here.

ISTM though that there may be hope with another active L dev effort for a 3G CDMA only device - the DX:

I had a very difficult time trying to read their commits in their github and though I did see what looked to me like some 3G CDMA specific commits but I have no clue of the significance of those commits, have no idea whether they have advanced far enough or whether they yet know enough at this point to be able to help us

---------- Post added at 08:10 PM ---------- Previous post was at 07:36 PM ----------

[MENTION=3683732]mightysween[/MENTION] you were right about needing a working CM12 - I had not noticed this:
[Moto G Android Development] tzzeri:
I'll try, but i don't see why it should be different. The problem is also on xperience lp (btw, instead of installing over cm11, you can install over xperience)

Do you think it might have something to do with the firmware? Maybe I should flash xt1032 modems since I have a 32? I googled the problem, it seems it's a lollipop problem. Ppl with official nexus 5 ota, and someone with a lp ROM for s3 complained about the problem. Maybe there's a way to search in the code for access point name settings are not available for this user?

---------- Post added at 08:52 AM ---------- Previous post was at 07:54 AM ----------

Tested, still doesn't work
[Moto G Android Development] tzzeri:
Here's the screenshot. I I press the +, then I need to enter the info, but when I click save, I just get back to the same thing shown in the screenshot.
[Moto G Android Development] Jester1614:
I am having this same issue. I am running a sprint note 2 flashed to cricket, running the unofficial l-900 rom 12-20150107 version 5.0.2
[Moto G Android Development] bharat_goku:
Hmmm I'll compile a new build tomorrow
[Moto G Android Development] tzzeri:
I've changed my firmware since yesterday to xt1032 br lollipop, so if I test, it won't be a reflection if it's fixed, but jester probably could test. Just to point out, I didn't have the problem on the xt1032 firmware my phone came with, only xt1033 4.4.4 which I had to flash to get out of a brick.
[Moto G Android Development] Jester1614:
I will be happy to test and report back, might have to wait till sunday to download depending on the file size (3g is my houses internet). Please send me a message when its compiled and loaded if you will.
[Moto G Android Development] russ722:
I can test for CDMA if there will be changes for it.
[Moto G Android Development] mightysween:
I am also back up and running to test XT1028 with the new screen finally.

Was looking at a Setup Wizard merge for SIM detection this morning... it is noteworthy that it appears 3g only models with no SIM cards were not even considered in this logic. It seems that the focus at Cyanogenmod may be on GSM and LTE devices at this time...and not just where falcon is concerned.

http://review.cyanogenmod.org/#/c/8...nmod/setupwizard/setup/CMSetupWizardData.java

This code tests SIM slots but does not account for the fact that "no sim" may mean the device is CDMA.

I believe this is one part of our problem going forward. Regardless of the outcome of this function, CM will try to bring up the radio as either GSM or LTE.
[Moto G Android Development] russ722:
I'm not surprised to be honest. And cynogenmod wants to take android away from Google,but they can't even get our stuff right.
[Moto G Android Development] mightysween:
Unfortunately, the 3g only CDMA variant is only popular in a small segment of the global market...and unusual in its lack of 4g/SIM.

We could certainly submit a patch to CM for the SetupWizard to fork to a device specific setup function...but first we need to figure out where we are forking to. Can we get the radio/modem running right if we simply bypass SIM detection altogether?
[Moto G Android Development] russ722:
I have no idea how to submit a patch,I'll leave that to the advanced people here.
[Moto G Android Development] lucabi1:
Which is the CDMA version? I'm a little bit confused :confused:
[Moto G Android Development] russ722:
Xt1031 and xt1028 are cdma
[Moto G Android Development] lucabi1:
Thank you!
[Moto G Android Development] moso11:
XT1034?
[Moto G Android Development] mightysween:
No, XT1034 is unlocked GSM
[Moto G Android Development] dovw:
This is good progress Mightysween... we have located the first SIM dependency in the CM12 architecture and it confirms entirely your suspicions... any chance we can persuade someone like Quarx who back in November was working on CM12 for the Defy which has a 3G CDMA variant to work on this problem for us?
[Moto G Android Development] mightysween:
The Defy on which CM12 is running is GSM and uses TI OMAP processors...non CDMA.

The Defy XT which is CDMA only is really not the same device. It uses Qualcomm MSM processors just like our XT1028/31.

If someone has cm12 running on a Defy XT then the solution should work here...but I believe it was the GSM variant that got the CM12 love.
[Moto G Android Development] Awesomeslayerg:
Okay guys, just to clear things up, you dont need to flash over cm11 anymore. You can wipe it using CWM and install CM12.
[Moto G Android Development] :
I've tried a couple builds lately that wouldn't boot till I installed TGM kernel.
[Moto G Android Development] mightysween:
This was true for me on XT1028 up until last week or so... now back to not booting unless I install CM11 first.

Strangest part is that I do a FULL wipe each time including data/system/davlik/cache. So it must be something in /persist that is causing the boot issue. A full wipe from stock KK will not boot, but a full wipe from CM11 will. So weird.

---------- Post added at 09:09 PM ---------- Previous post was at 09:00 PM ----------

Speaking of weird, I have been trying the nandroid approach to making radios work (as others have mentioned here before). Basically, installing a fresh cm12 build and making a nandroid backup of it...then fresh install a working firmware (cm11, stock, etc), then wipe and restore the cm12 nandroid.

The idea is that modems are not flashed with a nandroid so it should remain working...but it does not. And a fair amount of the time, the simple act of restoring a CM12 nandroid over a wiped system will soft-brick the device or at least mangle the radios so bad that I have to go back to 4.4.2 to get them up again.

Very odd behavior. I could understand it if I were dirty flashing...but I cant figure out why it happens with fresh/wiped installs
[Moto G Android Development] :
Yes, this is very weird. You would think everything should be wiped, but seems like something is still there causing a problem after wiping stock. It's also not only newer CM11 nightlies that you can install to get CM12 to boot after. I tried a nightly from last May and it worked. What's the likelyhood all three recoveries we have aren't quite wiping everything?
[Moto G Android Development] mightysween:
Well, a wipe actually doesn't wipe everything... just the 3 or 4 partitions we tell it to. My theory is that CM12 is failing to overwrite and then is choking on something left behind by stock KK on a persistent partition.
[Moto G Android Development] Lucas Eugene:
The official factory images have been released. I am going to flash this on my XT1031

and see how it goes ( without the radio parts)
[Moto G Android Development] mbj731:
Using Philz Touch 6.58.7 I have NEVER had to flash over CM11. I can't understand why this is different for different people, even amongst the same phone variants. I've flashed just about every ROM on XDA over the last few months and have done wipes each time. Only one bootloop in probably 25+ flashes.
[Moto G Android Development] :
I use the same recovery and have flashed Lollipop a lot more than 25 times and have had a lot of bootloops on XT1031. What do you normally use for a daily driver that you flash over?
[Moto G Android Development] jglm4u:
How did it went?
[Moto G Android Development] mbj731:
Spirit ROM. And I'm sure I have flashed more than 25 times also. I was just throwing a number out there. :D
[Moto G Android Development] sugarbuger70:
I was wondering if its the bootloader as well. I used to own couple a10 tablets and flashed ROMs via livesuit or cwm. I know this isnt moto g, but here's what I learned then:

That each bootloader was different in its instructions to its kernel. A jellybean bootloader won't work on ICS ROM and vise versa. Yes most phones share the same bootloader. But with a10s as well as a13s, parts were different even though tablets were identical. One may have touchscreen module ssd253z_ts.ko, and another gslx680.ko, and g sensor dmard06.ko or mmx622.ko and so on. So I had to install Ubuntu on my windows 8 PC via vituralbox, then decompile the bootloader so I could modify the hex files to corospond with my component (ko modules) in that bootloader, it tells a lot and looks similar to init.rc so I would insert my modules and location in the bootloader then decompile the kernel and ramdisk so I could modify the init.rc to add my vendor modules. Then the ROM I flashed would work. Any who, wonder if some of this could be done with yalls other tweaks. The bootloader holds commands just like a kernel (least in the all winner tablets)
[Moto G Android Development] :
Well, that's probably why. Some users claim to have installed CM12 based ROMs over Xperience and others rather than CM11 with no bootloops. Try installing over stock and you will most likely get stuck on boot animation.
[Moto G Android Development] sugarbuger70:
Oh if anyone can tell me how to extract the bootloader from this phone, maybe i can get that all setup again to take a looksee at the bootloader for xt1031/28, and compare that to xt1032/33 on stock kitkat, then the bootloader for 5.0 for possible differences
[Moto G Android Development] :
How about the boot loader from the stock firmware.XML?
[Moto G Android Development] sugarbuger70:
And there were camera libs or lines pertaining to cameras in a10 bootloader, not sure on moto g

---------- Post added at 09:31 AM ---------- Previous post was at 09:26 AM ----------

Haven't looked, u mean in the stock ROM thats flashed using stock recovery, that contains a bootloader? U have a link?

---------- Post added at 09:40 AM ---------- Previous post was at 09:31 AM ----------

Only difference now so far is a10 bootloader didn't or did contain radio/ril info depending on the tablet cause some had calling capability usually with a sim. One of mine did and neither tablet had a cell radio nor FM or Bluetooth. But WiFi info, touchscreen, mounts, g sensor, and even GPS info was in the bootloader down to ko location in ROM , permissions, etc so if I succeed in opening this bootloader, I will upload screenshots of its contents b/4 I go changing things so the community can see and maybe catch something I dont

---------- Post added at 09:46 AM ---------- Previous post was at 09:40 AM ----------

An example was say I flashed a cm ROM to the a10. The kernel matches and the ROM is compatible. Cm though puts vendor files or modules in lib/modules but the bootloader tells that the modules are located in /system/vendor/modules. As a result, the tablet wouldn't boot stuck at logo until I change the bootloader files to match cm location of modules. This moto g not booting sometimes on clean wipes reminds me of this. I know bout the twrp incompatibility, but still all parts must work together, no matter the device I would guess
[Moto G Android Development] :
I meant, could you use the boot loader from the stock firmware that you flash with fastboot. I don't believe the recovery flashable zips have the boot loader. I'll upload it from the Boost 4.4.4 stock firmware.XML when I get a chance.

Edit: here you go: https://docs.google.com/file/d/0B4-30E6G5pbITm1hRXdpakpRUEk/edit?usp=docslist_api
[Moto G Android Development] cmrainey:
How did that go? Curious to see if it works.
[Moto G Android Development] russ722:
Same here.