yashsingh1/xdaforums huggingface dataset:
[Moto G Android Development] CodyF86:
remove the assert line from the ROMs installer-script file. I'll start manually removing it from now on. At least for another few weeks. It's time to update your modem/bootloader guys. :) and girls. No reason not to now. Look back in this thread a page or two there are links / instructions on how to do it.

New one tonight.
[Moto G Android Development] narithlot:
ok i flashed modem/bootloader, but im getting a roaming instead of Verzion Wireless, also flashed latest build and it worked.. great work!
[Moto G Android Development] Shawnsch:
Same issue here too showing roaming
[Moto G Android Development] narithlot:
they said that its just a visual problem; everything should work as normal
[Moto G Android Development] Shawnsch:
ya i noticed everything was working just found it odd that the build prop edit didnt fix it this time
[Moto G Android Development] hitesh1:
@CodyF86

No sim issue after coming back from Airplane mode is with me only or anyone else is also facing same.

main problem with no sim error is, have to reboot the phone to get back data.
[MENTION=4736776]Shawnsch[/MENTION] [MENTION=6235628]narithlot[/MENTION] check your PRL version in settings - About - status - IMEI Info
[Moto G Android Development] narithlot:
Ok, i updated the PRL by dialing *228 and selecting 2 (takes a few minutes to update) for Verzion and now i can see my carrier again thanks for the suggestion [MENTION=2492839]hitesh1[/MENTION]
[Moto G Android Development] CodyF86:
OOOOPPPPPP Go!
[Moto G Android Development] hitesh1:
^^^

Downloading it...hope airplane mode issue get fixed for me :)
[Moto G Android Development] rgnicholas:
Need help please...

Hey... I am directing this at you but simply asking for help. I guess I got in too big a hurry and have messed up my radio or something. I am on PagePlus (Verizon) and flashed the ZIP you mentioned here: https://www.androidfilehost.com/?fid=95916177934538145 ...I simply flashed this zip in my recovery and it seemed to be successful, Then, I flashed the latest build of the ROM on this thread 05/01 and everything seemed to flash well. Then when I tried to call out, I get a strange new voice saying "please check your 10 digit number and try again." I also tried to update the PRL by dialing *228 and got the same voice telling me that I dialed a wrong command. I am guessing that my problem may be that when I flashed the ZIP to move to the LP bootloader, the radio in the ZIP was for Boost. Does that sound right? Right now I am dead in the water. I'll attach a couple of screen caps to show some of the pertinent info.

PLEASE, any assistance (from anyone) would be greatly appreciated. Thanks.
[Moto G Android Development] hhp_211:
What is your baseband version?

MSM8626BP_1032_390.81.01P

I'd have a copy of the Verizon radio flash XT1028_Verizon_US_CDMA_390.81.01P on my device as well

It may need to be recovery flashed after installing the 1st one...

It's so hard for me to remember exactly what I did when I upgraded to the 4119 bl

but, I'm also on PagePlus/Verizon, and I did flash its version of the radio at some point,

From lost101

https://www.androidfilehost.com/?fid=23681161096071059

.
[Moto G Android Development] rgnicholas:
Thank you VERY much for jumping in here... my baseband is: MSM8626BP_1032.3112.97.00R

The link you quoted is the radio ZIP?

------------------------ edit, more info ------------------------------------------

THANK YOU very much... now, I have service back and I was able to update roaming (*228) successfully. Interestingly enough, this radio version now shows the options for LTE and 2G where before, this was not the case. Now, I must also turn on roaming and automatic system select or I have no data. Is this normal for this ROM? I know many have had the roaming issue from reviewing different threads. I assume this is not really roaming on PagePlus? Don't want to kill my 500mbs too fast ;)
[Moto G Android Development] hitesh1:
[MENTION=5021949]rgnicholas[/MENTION]

Is this xt1031 flash to pageplus ?

Or xt1028 used on Verizon prepaid ?

In both cases first look if your min and mdn are correct and intact.

Then check if PRL version matches to Verizon or its boost prl. (Mostly it is boost as u flashed zip)

Then check for dialer adding 011 or 001 before any number you dial. You can turn this off in phone settings, it is called prefix dialing.

If you know your SPC, you can try updating prl manually thru dfs
[Moto G Android Development] rgnicholas:
I have a Boost phone flashed to PagePlus. After flashing the Verizon KK radio back, I have service again... but I don't think this is the same radio I had before I messed things up. HOPEFULLY, this will help others in my situation avoid the same mistake... since many of these new ROM builds moved up to the LP bootloader... and we were tired of the screen flicker plus having to remove the updater script entry. Sometimes we (me) jump too fast without researching enough. Maybe someone can post a link to a LP bootloader flashable ZIP that doesn't mess with the radios. ;)
[Moto G Android Development] hitesh1:
^^^

After flashing radio did your issue got solved ? If yes then forget about radii version. [MENTION=5337314]CodyF86[/MENTION] flashed 1-may zip, no sim error after coming from airplane mode still there.

And may I know what's new in this zip ? Didn't find anything new ... Help me to find it !
[Moto G Android Development] rgnicholas:
Yes, flashing the Verizon 4.4.4 CDMA radio zip fixed my issue. I found it here: http://xdaforums.com/showthread.php?t=2649763 after hhp_211 pointed me in the right direction.I assume it contains just the Verizon KK radio(s).
[Moto G Android Development] hhp_211:
Great!

Sure thing...

I know how you feel I'm on pageplus too.

One thing I did learn,, If you do have to dial 10 digit number twice to call someone,,, it will work,, but,,, it's a sure sign you are not on proper phone settings and will be charged the PP roaming rate fees.

Yes in the preferred network settings,

Never tried using 2G setting, obviously lte won't work for us...

I've also not tried automatic vs home either I just always used automatic anyway on all ROM's and on KK too,,, of course ymmv but rarely would I ever be in an actual roaming location because of Verizon great coverage.

So it's hard for me to test or comment on

.
[Moto G Android Development] rgnicholas:
Yep... this is the part that makes me a little nervous... BUT I suppose PP would simply stop working if you ran out of money / plan before the next renewal date. I use the Talk and Text 1200 and I have never come close to running through the 500mb... I am on WiFi most of the time and don't do streming music or videos... I just want good basic service, email, maybe GPS now and then. Thanks again for the quick help!
[Moto G Android Development] hhp_211:
There is not yet ( if ever ) a bl specific for Verizon lollipop,,, just have to flash both zips and we're good :thumbup:

---------- Post added at 11:08 AM ---------- Previous post was at 10:59 AM ----------

Yep same things for me. And yes when/if you use all 500mb data it will simply stop working, unless you have extra $$ in you account, which it would them keep on using data until the $$ runs out .

It will work as intended in actual 3G signal display of status bar.

If you run out of data it well no longer show 3G only bars and !

Just as of you tick to toggle off data from settings menu.

.
[Moto G Android Development] rgnicholas:
Actually... all I have now is the "R" in the signal icon. After doing a couple of speed tests, I still get about 1.5mbs to 2.00mbs, so I think I a still good with 3G :)
[Moto G Android Development] narithlot:
update your PRL, i did it in couple posts back
[Moto G Android Development] starkly_raving:
Keeps getting better. Hopefully the native SMS gets sorted out soon and this could definitely be more than "Experimental" (in all reality its a solid beta already) good job [MENTION=5337314]CodyF86[/MENTION] [emoji106]
[Moto G Android Development] rgnicholas:
I did update the PRL (roaming) and still have the "R" but it seems to be ok.

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

Yessir... this is one smooth ROM. I can live with the cosmetic issues but hopefully I can find a way to allow it NOT to seem to be roaming. For you experts out there, for PP / Verizon, doing a *228 programming update should update the PRL, correct?
[Moto G Android Development] CodyF86:
They just merged some code that completely effed what I had done with the ERI overlay files. I told them how I felt about it and am working on fixing it / having them revert it / reverting it myself for the next build. 05/01 is wonked in terms of carrier display.
[Moto G Android Development] rgnicholas:
Ok, for those that have followed my conversation about the radio change, roaming, etc... I have now updated the PRL again and got my 3G indicator back and the phone says it is not roaming. Glad I am and did notice that I have "no" carrier title at all. I am really looking forward to where this ROM goes... it is nice and smooth now but with more enhancements,, it is likely to be a dd for me. :good:
[Moto G Android Development] hitesh1:
^^^

For your carrier title, there are some build.prop settings mention in OP, check them out. [MENTION=5337314]CodyF86[/MENTION] remove that experimental from title, make it RC. :) , except for airplane mode no sim issue and ambient display, everything is working stable now.
[Moto G Android Development] rgnicholas:
Thanks but I do have those build prop additions and still no carrier label but I think CodyF86 mentioned a snafu in a reply a couple of posts back. No sweat though... I am just glad to have this as an alternative to waiting forever for the magical official stock release.
[Moto G Android Development] starkly_raving:
I know its not really relevant to "real world" performance but stock 5.0.2 scores about 4000 points higher on Quadrant standard and 2000 points higher on Antutu ...seems to be mostly in I/O and GPU but there's not noticeable difference in performance as far as how the device "feels" just thought it was worth mentioning.
[Moto G Android Development] CodyF86:
I had to fork frameworks_opt_telephony and revert a commit they just did. I told them they need to revert it, but im the mean time I have my own frameworks_opt_telephony repo in my github now.

Issue is fixed on my end at least...uploading build.
[Moto G Android Development] hitesh1:
^^^

As always will be downloading it !
[Moto G Android Development] CodyF86:
blah I think I may have a fix that won't make me have to have my own fork of frameworks_opt_net. Need to try it in the morning then ill upload sorry for the delay.
[Moto G Android Development] rgnicholas:
Thank you for the due diligence... appreciate your hard work.
[Moto G Android Development] CodyF86:
Well after trying to make it work, I'm back at maintaining my own framework_opt_net with that commit reverted. I was pretty abrasive telling them how I felt about that on the code review lol. I swear no one tested it and it doesn't even work, and it deviates from AOSP by |------------------| much haha.

So building now, just one more repo in my github lol.

Want to try Omni or Beanstalk or something different sometime soon. CM is starting to do silly things, people just merging things on a whim with no actual review other than the person that has the power to +2 it.

Feel free to read my rant in the comments lol: http://review.cyanogenmod.org/#/c/96581/

All those comments are refering to this: https://github.com/CyanogenMod/andr...mmit/b9bf02b3d651a248b8cd692ce921e78c1bee452b

That was just a sup patch still in review, figured best place to rant about it lol.
[Moto G Android Development] hitesh1:
^^^

My vote will be to omni
[Moto G Android Development] starkly_raving:
[MENTION=5337314]CodyF86[/MENTION] how hard would it be to build AOSP for CDMA? I imagine a pure AOSP build would fly on this device. [emoji4]

**Edit**

The other reason I would vote for AOSP is that CM roms as of late since CM9 I guess have indeed become feature rich but performance seems to have been sacrificed... Maybe code bloat can be as bad as OEM/carrier bloat? Just a thought.
[Moto G Android Development] hitesh1:
Strangely from today afternoon data pane started showing activities.

It was not showing any activity even after flashing 1-may build and 3-4 reboots.
[Moto G Android Development] ATTACK:
+2 for straight AOSP/Code Aurora.
[Moto G Android Development] hitesh1:
As far as I heard that asop is not able to work out with cdma ril, those mods are in CM .

(Got this reply in another thread )
[Moto G Android Development] ATTACK:
AOSP will work on CDMA

if

someone is willing to work on it.
[Moto G Android Development] hitesh1:
^^^

That's the IF there !

Asop should work, need someone who knows how to make it work.
[Moto G Android Development] CodyF86:
new build uploading. They are going to revert that change that messed everything up but in the mean time I just forked it.

Will be in OP in 30 min.

I'll start working on AOSP as time permits on weekends.
[Moto G Android Development] starkly_raving:
Yeah I can tell a significant performance difference on AOSP 5.1.X on my N5 versus CM/CM based ROMs. I think features while they enhance the overall user experience they just lend to more issues, things getting broken to fix other things and so on...while the vast majority of users will use few if any of the features in a CM ROM...AOSP however can be customized to the hilt by experienced users through custom kernels their own UI mods etc without additional code bloat and so on. Anyway with Alberto97's build isn't a majority of the work done aside from telephony and other CDMA specific code?
[Moto G Android Development] tarkin88:
+1 AOSP
[Moto G Android Development] ATTACK:
I agree.

I assume so, but I haven't looked at his sources so I cant be sure.
[Moto G Android Development] hitesh1:
After flashing 2nd may zip, not able to toggle data from settings, need to use additional data toggle app.

And data pane stopped showing any activity again, it shows old activity as shown in last screenshot, (right now due to slow internet can't upload new one)

Got carrier label back .
[Moto G Android Development] CodyF86:
I had the same thing happen to me yesterday and it freaked me out. I cleared cache and dalvik cache and reflash and it fixed it. Mine are working atm now; seems it was just something wonky.

edit: whoops nevermind that was wifi I meant. I can't either....weird another CM introduced bug blah... Let me see what happens on tonights build...actually I'll build right now will be 05-03.

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

Some more fun tonight.

https://github.com/codyf86/android_...mmit/318462a75e5da59c9773e2edb17bf2959850f70e

https://github.com/codyf86/android_...mmit/3c69265fcd5dcc81edf2545d0bf0b537743a0318
[Moto G Android Development] hitesh1:
Thanks for update Cody, you saved some work of mine [emoji12]

Will flash new build tomorrow !
[Moto G Android Development] CodyF86:
Alright homies here's the deal. I fixed init_falcon.c... I think, but it requires a step on your part before flashing the next build. I will add this to the OP also.

From the bootloader issue the following commands:

Verizon: fastboot oem config carrier verizon

Boost Mobile: fastboot oem config carrier sprint

then go into recovery and flash the ROM I'm uploading now, will be on the OP in 30 minutes.

THOSE WHO ARE ON VERIZON!!! Please issue from a terminal after flashing getprop ro.cdma.home.operator.alpha and getprop ro.cdma.home.operator.numeric

and tell me what it says...hopefully Verizon and 310004. This will tell us if I'm a hero or a zero..lol.

I can set up Reliance and Page plus also but lets make sure this works first.

Don't worry the fastboot oem config carrier only sets the ro.boot.carrier prop.

it's suppose to change the symlink in the fsg partition but we've already found out that isn't the case.

edit: Not sure why the mobile network toggle is greyed out. Data still works obviously just switches on or off depending on if you have wifi on or off, not sure if intended or a bug will have to look into it.
[Moto G Android Development] Shawnsch:
OK did the fastboot OEM config carrier Verizon but still shows boost
[Moto G Android Development] CodyF86:
Hmmm then there is something else screwing up init when it gets to that check. I'll have to look at it some more. :)

So weird the way it's acting it's defaulting to the else part of the if statement even though the IF should be true for Verizon. I'll try a few other ways to compare ro.boot.carrier.
[Moto G Android Development] Shawnsch:
Just noticed that cm updater shows a new build is it this ROM or another?
[Moto G Android Development] CodyF86:
No that is just the official CM nightly.

I have a few ideas about init. Going to try them one at a time by process of elimination. Gonna need the people who have already done fastboot oem config carrier verizon to help me out. Going to build one as the first attempt.

I think init isn't even running because of some code at the very top that is making it return and fail.
[Moto G Android Development] Shawnsch:
I'll help test anything you need. PS is there a way to try to run script after its fully booted to see where it fails
[Moto G Android Development] CodyF86:
I think this line of code was making it fail. Not sure about if you can or not, but let's try this first. Here is the code that is suspect.

rc = property_get("ro.board.platform", platform);

if (!rc || !ISMATCH(platform, ANDROID_TARGET))

return;

Only place it can return nicely and not work vs error out and not work. Doing 05-04 right now just to see.

Here are the changes so far.

https://github.com/codyf86/android_...mmit/a6dbef20d18261a24d76f7c01abf3e2d15d67c13
[Moto G Android Development] Shawnsch:
I'll flash as soon as it is up and let you know
[Moto G Android Development] Shawnsch:
OK so I didn't notice the 5-3 build till just now. Sorry. I flashed it and it showed Verizon wireless without doing anything
[Moto G Android Development] starkly_raving:
Just in case anyone is curious the MMS.apk works from Alberto's AOSP ROM on [MENTION=5337314]CodyF86[/MENTION] ROM, I requested the apks(MMS/mmsservice) and Alberto posted them. I wonder if we decompiled them and compared if we could find the fix for the native CM MMS.apk?
[Moto G Android Development] Shawnsch:
Can you link the post with the links?
[Moto G Android Development] starkly_raving:
PM'd you the links so as not to get off topic on Cody's thread. [emoji106] [emoji4]
[Moto G Android Development] CodyF86:
Posted 05-04 tell me if init is still worked. Not sure what the deal is.
[Moto G Android Development] :
Meticulus last build has working stock messaging. SMS and MMS.

Edit: on Boost anyway.
[Moto G Android Development] classic757:
[MENTION=5337314]CodyF86[/MENTION],

Flashed the latest build (5/4/15) and after initial bootup the lockscreen said Boost Mobile and I had no mobile data or 3g on my xt1028. Went back into recovery and flashed this zip by [MENTION=4736776]Shawnsch[/MENTION] in this link:

http://xdaforums.com/showthread.php?t=2774325 and now phone says 3g and Verizon Wireless on the Lockscreen and I have mobile data, although mobile network is still greyed out in settings.

BTW, great job on this rom! :good:
[Moto G Android Development] rgnicholas:
Hey... if someone don't mind, please tell me what this does. How can it have an effect before we even flash the ROM? I'm just trying to learn more about all this... thanks!
[Moto G Android Development] CodyF86:
That's so weird. Something is wonky, it may be the gpe check farther up in init_falcon.c. will just have to add Verizon build prop values like we have been for now. Will eventually fix it... Lol

That command sets ro.boot.carrier to Verizon or sprint for the other persons question.
[Moto G Android Development] Shawnsch:
Mine shows Verizon still so all good here!
[Moto G Android Development] rgnicholas:
Hey... did it just show up with NO tweaking on your part? No build prop tweaks? Interesting, I just flashed the latest ROM 05/04 without doing the extra steps requested (sorry) and had to add my typical verizon build prop tweaks to get the carrier label right.
[Moto G Android Development] Shawnsch:
I did the OEM config through fastboot that Cody posted a few posts back now it shows without the build prop edits
[Moto G Android Development] rgnicholas:
Ok... I guess I am dense but can you help me understand this... so, with a wiped phone, you plugged into your computer and did this fastboot command, then flashed the ROM? I suppose this is where I am getting a bit confused... if the phone is wiped and ready to accept a new ROM, but you do this fastboot command, how can it effect anything if the phone has been wiped? Sorry to be missing this guys but someone help me here. What catches the info inputted from fastboot?
[Moto G Android Development] Shawnsch:
I didn't wipe I just did the fastboot thing then went to recovery and flashed new build it has showed without build prop edits on the last two builds I have done since the fastboot thing
[Moto G Android Development] rgnicholas:
Ok... so you must have been on a previous build of "this" ROM first? I am thinking about coming from another ROM where I would need to wipe first.

----------------- edit -------------------------

maybe someone can tell me the proper way to do this if you are coming from another ROM... thanks
[Moto G Android Development] Shawnsch:
I'd flash the ROM then boot to fastboot and run the OEM config go to recovery and flash again
[Moto G Android Development] rgnicholas:
Ahhhhhhhhhhh... gotcha! That makes sense. Appreciate the help.
[Moto G Android Development] CodyF86:
Wait i'm confused. So you did the fastboot thing, flashed the ROM and the verizon props were set correctly? I need to know because I was about to go at it again, but if it is fixed then wooohoo!!! or did I read that wrong?
[Moto G Android Development] Shawnsch:
It worked correctly!!
[Moto G Android Development] CodyF86:
TTHHHAAANNNKKKK YOOOOUUUU JEEESSSSUUSSSSS!!!!!

lol sorry gonna do another build just to celebrate!

Now on to MMS.
[Moto G Android Development] Shawnsch:
Great job man!!
[Moto G Android Development] CodyF86:
I can set up page plus and Reliance also if anyone who is on those will provide me the usual build.prop edits you do once you flash. operator numeric. operator alpha etc etc.
[Moto G Android Development] rgnicholas:
I am pretty sure that PP will be the same as Verizon as they piggy back off the Verizon system... just fixing the name would be a sweet touch.
[Moto G Android Development] CodyF86:
The name would be based off the alpha numeric because of the ERI overlay. They doesn't use the same MNC MCC do they? operator numeric.?
[Moto G Android Development] CodyF86:
New build posted along with flashable MMS zip fix. Check OP.
[Moto G Android Development] narithlot:
i did the fastboot line on the previous build and everything runs great. Do i have to do again when i flash newer bulids?
[Moto G Android Development] CodyF86:
Nope one and done. :)
[Moto G Android Development] rgnicholas:
Sorry... hit the hay before I saw this one. I am not 100% sure about all of the build prop stuff, but these are my usual additions. I am on a Boost phone that I flashed to PagePlus several months ago.

ro.mot.build.customerid=verizon
ro.cdma.home.operator.alpha=Verizon
ro.cdma.home.operator.numeric=310004
ro.telephony.default_network=4
ro.cdma.home.operator.isnan=1
telephony.lteOnCdmaDevice=0
ro.cdma.homesystem=64,65,76,77,78,79,80,81,82,83
ro.cdma.data_retry_config=max_retries=infinite,0,0,10000,10000,100000,10000,10000,10000,10000,140000,540000,960000

Here is a PDF document that describes the process and some of the settings stuff... maybe it will be useful to know for people who are in the same boat as I am.

---------------------------------- edit ---------------------------------------------

Oh, I can also verify that I clean wiped (coming from another ROM), flashed your ROM, went back and did the fastboot things for verizon, then reflashed your ROM and got the desired result... Verizon Wireless as the carrier, 3G data, etc. Thanks for the work on this! The ROM is nice and smooth and snappy :)