yashsingh1/xdaforums huggingface dataset:
[Moto G Android Development] mitesh05:
i am on xt1033 ... do i need to flash mms.zip fix? ... i am on gsm and not on cdma
[Moto G Android Development] rgnicholas:
MMS App...

Just thought it might be worth noting that if you flash the MMS fix flash file, you will get the old style MMS app, not the newer LP looking app. That's

NOT

a complaint, just an observation... personally, I like the newer look ;)
[Moto G Android Development] starkly_raving:
The MMS is AOSP lollipop ... The CM MMS is their own version. [emoji106]
[Moto G Android Development] rgnicholas:
Gotcha... I have seen suggestions on various threads about MMS alternatives... so far, I usually fall back to Hangouts because it just works, but would anyone like to share a third part app that works god for you for SMS / MMS? Hope this is not too far off topic, if so... PM me with your suggestions. Thanks.
[Moto G Android Development] Shawnsch:
I've been using handcent
[Moto G Android Development] hitesh1:
[MENTION=5337314]CodyF86[/MENTION] currently I am off network so didn't flash after 4-may. Also didn't got time for fastboot.

For me build.prop settings are. Ro.build.home.operator.numeric=40400

After this it shows reliance mobile.

For sms, I use textra , it works very smooth with this ROM.

Also will suggest to ask everyone about removing few components like I dot use animated wall papers , stock browser etc.
[Moto G Android Development] a_gert:
[MENTION=5021949]rgnicholas[/MENTION] Quick question for you! Did this process (flash, fastboot carrier fix, flash) work for you? I'm thinking of dropping over to this ROM to give it a spin for my VZW XT1028 coming from Meticulus 4/8, I just want to confirm before I start wiping again. Thanks!
[Moto G Android Development] ncmz:
GSM = XT1032? If that is so, I own that model device and your ROM works perfectly. Smooth and stable as any stock one.

Cheers.
[Moto G Android Development] CodyF86:
Sweet, Figured it would be fine since the GSM models worked before CDMA, but just wanted to make sure.

I posted 04-11-2015. I messed around with the a few things last night trying to get the signal indicator to work on first boot, but adding the couple of missing lines from the stock build.prop didn't do anything.

Radio is probably coming up too late on a hard boot and the indicator never refreshes after that because it thinks it's down, but on a soft reboot it's already up more or less. Will poke around more tonight see if I can just make the indicator force a refresh after so long on bootup.
[Moto G Android Development] starkly_raving:
Awesome news hopefully you can get that sorted out ... Any thoughts on the "000000" network identifier?

**EDIT**

Saw this SPN commit for tonights upcoming nightly...(CM12) is that worth a look?

http://review.cyanogenmod.org/#/c/94026/
[Moto G Android Development] CodyF86:
Was about to say you use to be able to change it with a build prop setting, but that changed 3/4th of the way through CM-11 / you could only control it now really with decompiling framework-res.apk. Weird thing is they just merged that into cm-12.0 not cm-12.1. Let me see if it does anything really fast.

Mine says roaming indicator off atm.
[Moto G Android Development] starkly_raving:
Yeah...that's what I get on the nightlies. I just decompile stock framework and throw the eri.xml in data chmod 0444...but I think I remember ATTACK baked it in on CM11 and AOSPA.
[Moto G Android Development] CodyF86:
Good news is it cherry-picked into 12.1 / 5.1 so that part of the code wasn't horribly changed between 12.0 and 12.1. Will see what it does in about an hour and a half when it's done. If it works i'll throw it up here, if not will just wait till tonight to see if I can mess around with the signal indicator.
[Moto G Android Development] CodyF86:
Sorry for the back to back.

[MENTION=4658982]starkly_raving[/MENTION]

Redownload from the OP and tell me what yours says now. It changed mine from roaming indicator off to displaying nothing at all. (Which I think is actually on the right track.) I think yours might show something different though if you could oblige me.
[Moto G Android Development] starkly_raving:
Will do, as soon as I can.
[Moto G Android Development] CodyF86:
Err actually on the pull down it says no service under my 3g icon, but I have service. So now I'm really interested to see what yours says, but on the upper left part of screen it displays nothing. Let me know.

Figured it out kind of:

http://review.cyanogenmod.org/#/c/9...l/telephony/cdma/CdmaServiceStateTracker.java

Look at the comment that was removed along with that bit of code // Allow A blank plmn, "" to set showPlmn to true.

I don't think he took that into consideration with the patch I cherry-pick, let me see if I can fix it.
[Moto G Android Development] starkly_raving:
I have the exact same thing as you...on the most recent bootloader/modem.
[Moto G Android Development] CodyF86:
Ok I've figured it out. Currently without that cherry-pick this code is used in the current Android Code:

String plmn = mSS.getOperatorAlphaLong();

The getOperatorAlphaLong() function returns one of two things for CDMA phones either the ERI (Enhanced Roaming Indicator) if it is set. (It is for Boost mobile) That's why I see Roaming Indicator off.

If the ERI is not set (like on PagePlus? what you're using) it displays the ONS (Operator Numeric String), which is as it sounds a string containing your operator number, which is actually weird because it shouldn't be displaying 00000 or whatever.

Look here for my citations. Scroll down to getOperatorAlphaLong() It does something completely different for GSM phones (xt1032+) vs CDMA phones (xt1028/xt1031).

But anyway the point is, previously, in CM-11.0 and before the service info was set in the build.prop. I know in [MENTION=4400604]Meticulus[/MENTION] thread a bit ago you/he thought there could be an issue/bug that is being masked by forcing it to display a certain name, but actually the answer is no. getOperatorAlphaLong() displays the enhanced roaming indicator if it's set or the operator numeric string if the ERI is not set for CDMA phones.

So basically there are three choices.

1. You can have the ERI displayed (If it's set)

2. You can have the ONS displayed (If ERI is not set)

3. You can set the name to a build.prop setting to make it display your service provider name. (With some modified code)

I've been starring at CdmaServiceStateTracket.java and the Android SDK for an hour now to figure that out lol.

edit: and that cherry-pick actually isn't coded correctly / the no service thing is because it didn't take back into account plmn can be "" but not null, so hopefully they don't merge it into cm-12.1 as it is only merged into 12.0 at the current moment...maybe why it wasn't merged to 12.1?
[Moto G Android Development] starkly_raving:
The roaming indicator off has been an issue for us XT1031 users since CM11 any CM, AOSP or AOSPA ROM. We just fixed it by putting the eri from a decompiled stock framework and tossed it in data and set permissions. [MENTION=4427492]ATTACK[/MENTION] just recently compiled a moded framework for AOSPA 4.6 (KitKat) that included the Boost eri which eliminated the roaming indicator off text. Not sure if that's a trick we can apply here.

---------- Post added at 01:19 PM ---------- Previous post was at 01:10 PM ----------

I'll actually be happy when they(CM) deunify the builds moving forward.
[Moto G Android Development] CodyF86:
Honestly the correct way to code it, since the code is in CdmaServiceStateTrack.java (so GSM phones aren't even using it) would just be to read from ro.cdma.home.operator.alpha in the build.prop and set it to that. Can do that pretty easily; will give it a try now real fast. :)

When ERI is changed by decompiling and recompiling you're just telling it what to say instead of it displaying roaming indicator on or off which is what the ERI normally says/displays.
[Moto G Android Development] kijp15:
[MENTION=5337314]CodyF86[/MENTION],

Are you accepting feature requests?
[Moto G Android Development] Ignaciodnb:
i tried to install this rom (with twrp, philz, cwm) but i have bootloop :(
[Moto G Android Development] CodyF86:
Yeah, but I'm not as good of a programmer as I sound sometimes... lol =) / I am slightly time limited, but sure can give anything a shot.

p.s. Going to pull the 04-11-15 build for now, as that cherry-pick was slightly sketch, will throw it back up if this works. (What I'm building now.)
[Moto G Android Development] kijp15:
Well your building great roms as far as I can tell. Haha. Smooth & Fast on my end, seriously. Great work! :)

But can you please throw in Navbar Dimensions?

That would be awesome, Thank You! :)
[Moto G Android Development] CodyF86:
Wipe cache partition and clear dalvik cache in recovery options then flash. If it still loops then you need to do a clean install. It does boot though, but I would use the 4-10 build for now as the 4-11 I just updated, had a wonky cherry-pick for an issue we've been working on and im rebuilding it.

edit:

Sorry for the ninja edit mention but,

[MENTION=4658982]starkly_raving[/MENTION]

I just got done reading through the ERI manager code and you're right. I could use an alternative ERI file to load the name. I could even set a differrent location for the file, so it isn't stored in a compiled apk file, but even then it's only specific to one carrier. Reading from the build prop allows the init to set the name depending on the radio for the CDMA versions of the moto G and doesn't interfere with the GSM phones that work properly reading off the SIM card. Going to see if this works here shortly, almost done.
[Moto G Android Development] Ignaciodnb:
Now I could install successfully :), but I had to restore to stock kk then install another custom rom and then install this

idk what is the problem, but when i restore to stock kk there are several custom roms 5.1 that i can't install, i must to install aosp 5.1 first
[Moto G Android Development] Pinktank:
nice book you bound there. I will flash the recent build tomorrow evening and report any problems (not cdma here though). Do you suggest flashing stock 5.0 before yours or can I just come over from KK by fastbooting the bootloader and recovery, booting to recovery and flashing your zip?
[Moto G Android Development] rgnicholas:
Yes it did... coming from another ROM, I clean wiped twice (yea, I am funny that way), installed this ROM, then got into the bootloader and issued the fastboot command, then reflashed the ROM again, then flashed the Gapps. Verizon is listed as carrier and data and sms / mms work as long as you use Hangouts or another third party app. Also, I have roaming turned off and still have 3G showing up.

I am thankful for this alternative. I am also thankful for all the work other devs have done, but for right now on my phone, this ROM is smoother and snappier than some. Also, I took a look at the resulting build.prop (after this process) and the Verizon entries are not there... so, Cody has worked some magic to lock these things in behind the scenes. If he (or anyone) can fix the native CM MMS app, that will be icing on the cake.
[Moto G Android Development] a_gert:
Perfect! I think I'm going to give this one a go, given the clear support for Verizon, as I already use Hangouts as my default SMS/MMS app; I'll throw some info up if I have any luck messing with the stock MMS. Thanks for the help!
[Moto G Android Development] rgnicholas:
No problem at all... be aware that on the last couple of builds, the switch in settings to turn data on and off is not working but you CAN toggle airplane mode if you need to... I am pretty sure Cody will get this little glitch ironed out soon. Also, for me, the data usage mechanism in settings will not allow me to set a limit for data use. No biggie for me because I am careful and don't do a lot of data heavy stuff.
[Moto G Android Development] ATTACK:
There's no need to, "Flash ROM > Carrier Config > Flash ROM".

All you need to do, is, "Carrier Config > Flash ROM".

It's a boot command not a ROM command.

Sent from my xt1031
[Moto G Android Development] hhp_211:
been using the beta/material version of 8sms,,, mostly because I know it has specific settings capability for MMS

this helps alot in times of transition like we are now with Lollipop

http://8s.ms/download/releases/8sms-1.48.5.apk

8sms-1.48.5.apk 04-Apr-2015

info on their website Material version

http://8s.ms/material-theme-for-8sms

info on play store old version 27-Nov-2014

https://play.google.com/store/apps/details?id=com.thinkleft.eightyeightsms.mms

.
[Moto G Android Development] Pinktank:
Does anyone else have aggressive wifi sleep issues in the last week or so of CM based builds? I keep catching it with wifi off, and it connects automatically after I haver turned the screen on (wifi is set to not sleep)
[Moto G Android Development] classic757:
No, fortunately I have not had that problem with any cm 12-based rom that I have flashed. Are you on kitkat or lollipop bootloader? And does it do that with a specific rom or any cm 12 rom you flash?
[Moto G Android Development] Pinktank:
I am on Loliloader and it happened with mokee when I just tested it out, and then when I went back to official nightlies, I still had it :( There was also someone else who reported it.
[Moto G Android Development] classic757:
Not sure why that happens. First time hearing about that issue on CM 12.
[Moto G Android Development] a_gert:
[MENTION=5222096]classic757[/MENTION] : I noticed you're running an XT1028 on the 41.19 bootloader via the flashable zip. Are you on VZW service? Did you have to flash a VZW radio after updating your bootloader, and if so, is the 4.4.4? Part of me really wants to try to get my bootloader up to Lollipop so I can give an alternate kernel a try to take advantage of battery enhancements while on a CM12.1 variant, so I'm curious what steps another 1028 user took. Thanks!
[Moto G Android Development] classic757:
Yep, I am on VZW service. I flashed the 41.19 bootloader zip successfully via TWRP 2.8.5.0 recovery and then flashed the VZW 4.4.4 radio. Had to flash the radio/reboot about five times before I got mobile data/3g/calls, but eventually it worked.
[Moto G Android Development] rgnicholas:
Thanks... I'll give it a look. :good:

---------- Post added at 02:20 PM ---------- Previous post was at 02:14 PM ----------

Hey... this brings me back to the question I had earlier. What if I have wiped everything completely? If I am sitting there with a blank slate, so to speak... where does the fastboot write to? Sorry to be asking again... I am just trying to be sure I understand the process well. Does the bootloader keep a "verizon" reference? Thanks for being patient with us life-long learners :)
[Moto G Android Development] ATTACK:
fastboot oem config carrier >carrier<, tells your device to use the proper fsg.gz, which is located in a separate partition.
[Moto G Android Development] narithlot:
it happened to me a couple of times, all i did was reboot the phone and everything is back to normal
[Moto G Android Development] CodyF86:
For pageplus since it piggybacks off Verizon I will add a nice touch where you can specify a build prop setting... Say ro. CDMA.carrier.text.override and if you set that to true it will pull carrier text from operator.alpha. also will set up reliance. Reliance will need to do the fastboot thing but reliance instead of Verizon or sprint for tonight.
[Moto G Android Development] CodyF86:
For some reason that isn't actually the case the symlink doesn't change. I'm just using that command to set ro.boot.carrier so. I can do an is match() check against it.
[Moto G Android Development] classic757:
Okay, this is weird. Whenever I try to uninstall an app in the PlayStore I get an instant reboot of my phone. Anyone else experiencing this?
[Moto G Android Development] CodyF86:
Pretty sure it's all within the bootloader. carrier config sets androidboot.carrier (think, some variable like that in the bootloader) to whatever you input then android reads androidboot.carrier and pushes that value to ro.boot.carrier, which I am able to read during init.

Once it's set, it's set until you change it again with that same command.

edit: also [MENTION=5021949]rgnicholas[/MENTION] I don't suppose page plus has a slightly different operator numeric that would still work do they? Would make carrier text for you easier todo. I can do it either way though.

edit: [MENTION=2492839]hitesh1[/MENTION] list the full build.prop additions you add once you flash, including operator.alpha.
[Moto G Android Development] rgnicholas:
Hey, it is my understanding that all the numbers and settings are the same as Verizon, even the voicemail number is the same and when we call in to update roaming, it announces as Verizon ... but I am not an expert on such things. I know that when I want to flash a stock ROM (KK, let's say), it is a Verizon ROM all the way.
[Moto G Android Development] CodyF86:
Can you / someone humor me and change your MCC MNC / operator numeric to 310 012 and tell me if everything still works. Seems there are a few others and if it works then it will make this much easier. Let me know.

Prob can just do it in the build.prop

If not I have a easy work around was just curious.
[Moto G Android Development] rgnicholas:
k... hang on.

EDIT, added... ok, now I get "Roaming indicator off" for the carrier... but sms / mms works still on hangouts
[Moto G Android Development] ATTACK:
Ah, yes - as I recall both Boost and Verizon default to falcon_verizon_3.img.gz.
[Moto G Android Development] CodyF86:
Sweet I can add that ERI overlay if it's still working for you and add it to init. cool will do a build with the changes.

edit: err wait it says mobile network disconnected, do you have data working like that?

Yeah it's weird, that's how they had init setup to begin with, which is why it never worked correctly...always went to _verizon_

--------------

Page Plus you're using 310 012 according to how I have init, unless someone tell me data doesn't work, but ^^^^ makes it sound all good. Doing another build.

Here is the new list.

fastboot oem config carrier verizon (Verizon)
fastboot oem config carrier pageplus (Page Plus)
fastboot oem config carrier reliance (Reliance Mobile)
fastboot oem config carrier sprint (Boost Mobile)
[Moto G Android Development] hitesh1:
[MENTION=5337314]CodyF86[/MENTION] for reliance only one line is sufficient in build.prop, I don't change anything other than cdma.operator.numeric to 40400

ro.cdma.home.operator.numeric=40400
[Moto G Android Development] rgnicholas:
Hang on... didn't test data... I assumed it was ok since MMS worked but let me retest... and are you purposely leaving a space in the digits?

310 012

------------------ added --------------------------------

Ok, I retested with your numbers and data works fine... shows 3G and not roaming for me. I also added it with the space in the numbers just to see if it made a difference.
[Moto G Android Development] Lucas Eugene:
Is there a way by which we could actually see data usage of 3G under data usage, and set data limit, warinings etc. I have a custom carrier flashed on my XT1031.
[Moto G Android Development] hitesh1:
[MENTION=5857550]Lucas Eugene[/MENTION] , same here, xt1031 flashed to different carrier, some times data pane works , sometimes it won't. I use 3rd party app like internet speed meter, but it only shows total data used on mobile data and WiFi. Daily logs are available, monthly limit warning msg can be set.

There are few apps who acts like firewall and can block data uses to particular app.
[Moto G Android Development] Lucas Eugene:
Thanks for the tip. I think I'll search for some 3rd party apps that could do this.

PS if anyone knows a workaround to enable it in the settings pane, I'm flashed to page plus :)

Edit: [MENTION=5337314]CodyF86[/MENTION] the 3G toggle in the mobile networks isn't working in the last build. Seems like a cm issue ( not your build specific)
[Moto G Android Development] hitesh1:
fastboot done

did fastboot oem config carrier reliance after flashing 5-may zip.

fastboot screen shot attached.

it shows Boost Mobile without doing any build.prop edit.

Did build.prop edit as follows

ro.cdma.home.operator.numeric=40400

Now it shows as Reliance Mobile :good:
[Moto G Android Development] CodyF86:
That code isn't in yet until the build I just posted 05-06 :) Flash the one in the OP now and see :)

new build posted check OP.
[Moto G Android Development] hitesh1:
Ok, downloading it :)
[Moto G Android Development] rgnicholas:
Installing the new build (clean flash) with the PagePlus entry... will report on any unusual observations after a few hours of use. :good:
[Moto G Android Development] a_gert:
I went all in this morning and moved my VZW XT1028 over to the 41.19 bootloader via the new flashable zip from SuperR, installed the 5/6 build from here, and I'm giving the Attacked v10 kernel a shot, as well. Everything's running super smooth and snappy thus far!
[Moto G Android Development] hhp_211:
Nice!!

what modem [baseband] did you have? what ROM setup were you coming from?
[Moto G Android Development] rgnicholas:
Yes... be careful. You will likely need to update your modem(s) after that... I know I did because you'll end up with Boost modem(s).
[Moto G Android Development] a_gert:
As of around a week ago, I was running an optimized and rooted stock 4.4.4 plus Xposed on the 41.13 bootloader, but it was time for a wipe and I took a shot with the CDMA CM12.1 builds from Meticulus (while keeping the KK bootloader). Due to some connectivity issues, I'd stayed on the 4/8 build of that until this morning, but I really wanted to give this ROM a try and see what I could do with my battery by getting on a custom kernel.

As per [MENTION=5768732]amarc78[/MENTION] 's request over at Android Forums, SuperR put out a new version of the partition updater that was originally for Boost (I think?) that updates the bootloader without overwriting the 4.4.4 VZW modem, negating the need to reflash the radio back over to get it working: http://androidforums.com/threads/cdma-get-ready-for-otas.897474/page-21

I booted into TWRP, wiped everything, flashed that zip, then installed the 5/6 build of this ROM, gapps, and the Attacked v10 kernel. So, at the moment, I'm running the 41.19 bootloader with the VZW 4.4.4 modem, CM12.1 Linaro 5/6, Attacked v10, and TWRP. So far, seems to be working without issue.
[Moto G Android Development] rgnicholas:
Awesome... thanks for the info! The news about the adjusted ZIP by SuperR will certainly help some folks along the way. Please tell us how the battery life holds up with the different kernel after you've used it a couple of days.
[Moto G Android Development] hitesh1:
[MENTION=5337314]CodyF86[/MENTION] flashed 06-may zip, reliance mobile without build.prop edit.
[Moto G Android Development] classic757:
Great! Glad to know you successfully updated your bootloader and that it's working well for you. :highfive:
[Moto G Android Development] hitesh1:
Wrong charge time left indicator , 21 to 100 in 6min ?

Is it me or ..?
[Moto G Android Development] :
Nice, glad to see it worked as planned. I tested it, but I have Boost. That'll saved lots of troubles and questions.:)
[Moto G Android Development] rgnicholas:
Hmmm... mine looks correct. Maybe yours. Did you install a custom kernel?
[Moto G Android Development] hitesh1:
^^^

I am on codyf86 modified kernel which comes in his ROM . charging indicator issue is only first time when boots , after sometime it is showing normal time
[Moto G Android Development] rgnicholas:
Question...

I have a question for everyone. When I get a phone call and want to hold the phone in my hand, using the speakerphone, sometimes (most of the time) I can't easily press the speakerphone icon, the whole screen blinks on and off as I get my finger near the surface of the screen. I have noticed this on other CM 12 ROMs as well. I wonder if this is a proximity sensor issue or do I need to toggle some setting somewhere? TIA
[Moto G Android Development] hitesh1:
^^^

Same here, it is proximity sensor kicking it. No toggle (I don't find any)
[Moto G Android Development] CodyF86:
05-08 posted. Nothing too notable just did a quick build.