yashsingh1/xdaforums huggingface dataset:
[Moto G Android Development] rgnicholas:
Gotcha... the reason I know it is baked in is because after booting up, I enabled "root explorer" in ES File Manager and the ROM asked me if I wanted to give it root access. It may not matter one way or another...
[Moto G Android Development] pico hackr:
Thanks for your reply yes go on with CDMA variants
[Moto G Android Development] rgnicholas:
Just a report of an oddity that I experienced with the April Fools build :) Ok, I wiped everything but the sdcard and the ROM seemed to be working well. Data, SMS, and voice worked, but MMS did not. I am on a Boost flashed to PagePlus phone. I use Philz touch recovery.

the "roaming indicator off" message was replaced by 0000000 (several zeros)

regular messenger app still was not working, greyed out send button

Hangouts would send sms but not mms... before I could add some build.prop tweaks (as I have been doing), I got stuck in a boot loop

I installed all my normal apps manually and things seemed to work smooth until I decided to try Apex launcher... not sure if that was the culprit, but soon after I installed it, I decided to reboot because I got a message saying that I was out of storage space... so, I remember reading on a post that if you did a soft boot, this would fix the space error report... this is when I got the boot loop

the boot loop was odd... it kept rebooting and trying to optimize the apps (like when you wipe the cache / dalvik cache)... it did this 3 or 4 times and would never completely boot to the home screen

sorry, I couldn't get a log because I never got to the home screen again and had to restore

Not entirely sure what happened, if it was Apex or whatever... just wanted to add to the tread while Meticulus is developing things here. Normally, I use Nova launcher with no issues... oh, and to confirm... I did not add Xposed to the ROM either
[Moto G Android Development] :
They must have, because I tried the latest Broken rom yesterday and data works. I lose it most of the time after a reboot, and have to reboot and wipe dalvik and cache, but it works.
[Moto G Android Development] classic757:
Just a few things: I also got the "000000" in place of "roaming indicator off" in the upper left hand corner of the lockscreen(still there btw).

I also use Apex Launcher( I have tried Nova Launcher several times but I like Apex better) and got a few reboots and "optimizing apps" a few times. Not sure if Apex was the cause.

I clean wiped and re-flashed the rom about three times and now it is working fine. No lag or random reboots at all. Apex working fine. (Oh, I did have a problem with MX Player. Had to stop and re-start it several times before it would play my music videos correctly. No problems with it now though.

Oh, and when I did a soft reboot, it caused an empty signal bar and constant random reboots. No problems with hard reboots.

What bootloader are you on btw?

I am on 41.13. Lollipop is really for an updated bootloader so if you are on an older one, some of these issues may be caused by that.

xt1028
[Moto G Android Development] rgnicholas:
41.13 here too. When you say you flashed it 3 times... do you mean literally 3 times in a row before booting? Also, did you wipe the sdcard?
[Moto G Android Development] classic757:
Yep, 3 times in a row because I kept having problems with the rom until after the third flash.

Oh, and I did not wipe the sd card(internal storage). The ONLY time I wipe internal storage is when I do an adb fastboot flash of the original 4.4.4 factory firmware, which automatically wipes everything on the phone.

It is wise to always keep a backup of another rom(stock or custom) on your phone when flashing in case something goes wrong.

---------- Post added at 11:17 AM ---------- Previous post was at 11:02 AM ----------

Anyone else notice that in Settings>About phone> Cyanogenmod version it says 12.1-20150329-UNOFFICIAL-falcon ?

I downloaded the 20150401 build but it has 3/29 as the build date.

:confused:
[Moto G Android Development] hhp_211:
he mentioned in the other thread http://xdaforums.com/showpost.php?p=59552137&postcount=1028
[Moto G Android Development] :
Just a note fella's... You guys are of course welcome to discuss anything related to development of this ROM and share your experiences, tip, and tricks. However, if you have a bug that you want fixed/me to look into, please submit it to the bug tracker with a proper log and any other helpful info. (screen shots etc...):highfive:
[Moto G Android Development] toasterboy1:
Nice work! Glad to have someone working on the CDMA versions. Was able to place calls with 4/1 build but no luck with SMS with stock, textra, handcent, or hangouts. I was off wifi and do not have data enabled, because of my plan limit. ROM seemed smooth and the Microsoft stuff was funny. Also had the zeros. Would probably have stuck it out if I could have worked around the SMS. Will keep an eye on this build.
[Moto G Android Development] :
You can work around sms issue with 8sms. MMS will work also.
[Moto G Android Development] wahid536:
Hey bro big thanks to you for helping me with getting root and my recovery back. :) I appreciate the help man thanks
[Moto G Android Development] toasterboy1:
Do you have to make any setting changes? Like setting MMSC or APN.
[Moto G Android Development] :
It should already be there. But if it isn't, just google it and you'll find the right info.
[Moto G Android Development] toasterboy1:
Not sure why the others did not work but just reflashed 4/1 build and tried chomp sms and it worked. Thanks for making me try again. Feels like a new phone!
[Moto G Android Development] alex_is_the_1:
Has anyone tried this on a gsm version? I love meticlous's work and would love to try this. Btw I'm still on jb boot loader would that cause any problems if this rom works for gsm?

Sent from Moto G
[Moto G Android Development] :
Hey fella's, I've been working on the RIL some more and I think that I may have SMS on the stock app worked out. Even though my device is not activated, the stock app is allowing me to attempt to send a text, without direct modification of the Stock app. I am also seeing that the SMS requests are making it to the RIL.

D/SmsNumberUtils( 1495): enter filterDestAddr. destAddr="+1800XXXXXXX"
D/SmsNumberUtils( 1495): leave filterDestAddr, new destAddr="null"
D/RIL_ImsSms( 1495): sendText
V/CdmaSMSDispatcher( 1495): No carrier package.
D/CdmaSMSDispatcher( 1495): sendSms: isIms()=false mRetryCount=0 mImsRetry=0 mMessageRef=0 SS=0
D/RILJ ( 1495): [3959]> RIL_REQUEST_CDMA_SEND_SMS [SUB0]
D/RILC ( 2823): SOCKET RIL_SOCKET_1 REQUEST: CDMA_SEND_SMS length:152
D/use-Rlog/RLOG-RILC( 2823): dispatchCdmaSms
D/RilRequest( 1495): [3959]< RIL_REQUEST_CDMA_SEND_SMS error: com.android.internal.telephony.CommandException: SMS_FAIL_RETRY ret={ mMessageRef = 5, mErrorCode = 97, mAckPdu = null}

This repeats a few times and, of course, still fails because, I assume, my device is not activated...

I've been studying the RIL log closely for awhile now and have never seen this.... So, I'll be posting a build with these changes sometime today and I am going to need feed back on ANY change in the way SMS/MMS is working particularly on the stock app but also on third party apps... Also, please note any odd behavior related to telephony...

EDIT: The new build will still have the April 1rst code base....

EDIT2: NEW BUILD POSTED!
[Moto G Android Development] benutne:
I wonder if you could get a Ting account and activate the phone on that. It would cost less than $10/month if you keep your usage super low. Hell, if it will let you activate, I'll even put you on my bill and pay the $6/month it would cost me as long as you don't screw me over on usage. :)
[Moto G Android Development] :
I appreciate the offer but I have already explored this option and it's not do-able. According to Ting, I will have to activate it on Boost for a year before I could switch to Ting...:(
[Moto G Android Development] benutne:
That is what I was worried about as well. Sprint really screwed a bunch of people over on that one. Really backwards thinking move on their part, IMO.
[Moto G Android Development] classic757:
[MENTION=4400604]Meticulus[/MENTION],

I downloaded and flashed your latest build (04/03/15) and it is very nice! :good:

Better and smoother than the previous build. Also have the 3g icon in the signal bar! :victory:

Still the 000000 in the upper left hand corner of the lockscreen. :(

Also the phone says it's Roaming when not on wifi. Does that mean the phone is in constant roaming status?

See srceenshots below.
[Moto G Android Development] :
I'm not sure, that "000000" is the "operatornumber" (operator) taken from the service state. On mine it says "31000" but mine is not active. If you have a Boost Moto G and you are connected to operator 311870 it should say "Boost Mobile". Likewise if you are connected to operator 310004 it should say "Verizon". If the operator is not one of those, it shows the operator number. If you are on Ting or Page Plus, I have no idea what happens?:confused:

SMS/MMS on the stock app?
[Moto G Android Development] classic757:
I am on Verizon. Do I have to enter the apn info manually?

Also, yes! Stock SMS is working! :highfive: I did a test message.

Not sure about MMS. Didn't try to send picture. I'll try it and see.

Also no way to edit apn. No APN settings under Mobile Networks.

xt1028

---------- Post added at 04:41 PM ---------- Previous post was at 04:36 PM ----------

@Meticulus,

When I tried MMS I got the error "No APN Specified on the device" and I could not send it.
[Moto G Android Development] :
No, the APN is supposted to be worked out by init here:

https://github.com/CyanogenMod/android_device_motorola_falcon/blob/cm-12.1/init/init_falcon.c#L88

You might actually be... roaming... :confused:
[Moto G Android Development] classic757:
I thought I was in roaming status. Don't want that. If I am not on wifi that will eat up all my data! :eek:

I do not see any way to edit apn in Wireless & Networks>Mobile Networks>More.

See screenshot below.
[Moto G Android Development] :
Can you get me the output of "getprop"?:

adb root
adb shell
getprop > /sdcard/props.txt
adb pull /sdcard/props.txt

The post that here...:highfive:
[Moto G Android Development] classic757:
Okay, tried both adb from my pc and in terminal emulator and I am getting "device not found" error. However,when I type in adb devices with phone connected to pc it list my device but when I type in adb root command it says device not found. :confused:
[Moto G Android Development] :
The adb commands are not necessary from terminal emulator on the device...:laugh:

just:

getprop > /sdcard/props.txt

The post the file @/sdcard/props.txt :good:
[Moto G Android Development] classic757:
Okay, here we go:
[Moto G Android Development] :
Your device is being detected as a Boost Mobile device..... I will have to come up with a way to allow this to be overridden...:highfive:
[Moto G Android Development] classic757:
Yeah, I saw it in the getprop as the operator number is the one for Boost Mobile and I am on Verizon.
[Moto G Android Development] hhp_211:
Not on newest build yet...

yeah I've been trying for days to get that info

it hasn't happened on anyone's builds

mine shows same way

it doesn't see/find the radio 0x3 there

but i'm definitely not actually roaming when it says I am

even manually adding some things to the build.prop don't remedy this
[Moto G Android Development] starkly_raving:
Have you tried throwing the eri.xml in data and chmod 0444?
[Moto G Android Development] :
OK, wrote some code to allow these 2 properties to be overridden in the build.prop:

ro.cdma.home.operator.numeric=310004

ro.cdma.home.operator.alpha=Verizon

You can put whatever you want for those values in the build.prop . Tested, all looks good. This change will be in the next build but for those who do not want to wait; flash the attached boot.img
[Moto G Android Development] classic757:
Okay, flashed the boot.img. Here is the props.txt after doing so. (btw still have the 000000 on the lockscreen.). Phone still seems to be detected as a Boost Mobile phone.
[Moto G Android Development] :
Did you add these lines to your build.prop?

ro.cdma.home.operator.numeric=310004

ro.cdma.home.operator.alpha=Verizon
[Moto G Android Development] classic757:
Oooops, Silly me! :silly: I forgot to do that. Will do that now. My bad. Sorry.
[Moto G Android Development] classic757:
[MENTION=4400604]Meticulus[/MENTION],

Here is the getprop after I flashed the boot.img and made the changes to the build.prop. Everything looks good in the props however I still have the 000000 on the lockscreen. I wonder why the carrier name is not showing up there?
[Moto G Android Development] uruhakurosaki:
the latest build seems work really well.....will flash it.....

is okay to flash with mini gaaps?
[Moto G Android Development] classic757:
As long as they are specifically for Lollipop 5.1 they should be fine. Any other gapps may cause problems.
[Moto G Android Development] uruhakurosaki:
got it....

will download mini gaaps 5.1 from meticulus web...

any major issue for latest build?
[Moto G Android Development] classic757:
No major issues at the moment. Stock SMS is fine. Stock MMS maybe not. Everything else working well. Restored all my apps with Titanium Backup with no problem. Rom is progressing very well thanks to [MENTION=4400604]Meticulus[/MENTION].

xt1028 Moto G
[Moto G Android Development] dirty_smurf45:
Is this a continuation of this thread?

http://xdaforums.com/showthread.php?t=3036120

Sent from my Boost Mobile Moto G (xt1031) with Tapatalk. Running Android 5.0.2 stock soak test with root

EDIT: Nevermind I saw your post in the other thread.
[Moto G Android Development] rgnicholas:
log attached / out of space

I am attaching a log and a couple of screen caps. I clean wiped, flashed the last 4/3 build and the boot.img Meticulus provided a couple of posts back. I added the build.prop tweaks and when I tried to add my normal round of apps (not an automatic restore), I got most of them added back then hit a barrier where Play Store told me that I was out of space... however, as the screen shot shows, I still had about 500mb free.

The ROM seems much smoother that previous builds.

Just to note, it did take longer that before to get first boot after initial flash... about 6 1/2 min.

Stock SMS worked but MMS not.

Hangouts sent both SMS and MMS... after I added the build.prop tweaks.

Data was fine, the 3G indicator showed back up.

Still have the "000000" instead of carrier label in the notification bar.

I am on 41.13 bootloader, use Philz touch, and PagePlus.

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

Ok, the space issue went away after I went into recovery and wiped cache / dalvik cache. after that, I could finish installing my apps.. including Apex. Everything reboots clean now, thank goodness. Thanks.
[Moto G Android Development] classic757:
If you have not already, I think you should try this rom. 5.1 is a lot smoother and less buggy than 5.01 and 5.02. [MENTION=4400604]Meticulus[/MENTION] has done/is doing a great job with cdma on the Moto G.
[Moto G Android Development] starkly_raving:
I'm on Boost Mobile and have the 00000 network issue

**EDIT**

Seems from my reading its PRL related. Going to try and reprogram the phone and see if it updates my profile/PRL
[Moto G Android Development] Sik-1:
I agree, samething ova here also boost
[Moto G Android Development] rgnicholas:
awesome... let us know the result... I have the 000000 too but I "think" it is just a cosmetic thing
[Moto G Android Development] starkly_raving:
Because ##72786# doesn't work with CM/AOSP I called Boost and had them manually refresh my services on their end...no dice. PRL and network still shows 00000...

**EDIT**

OK so looking in settings about phone under IMEI the PRL is in fact there and correct and everything seems to be as it should...I do notice data drops from time to time intermittently...
[Moto G Android Development] rgnicholas:
Just to add tot he discussion... I am on PagePlus and just updated roaming (*228), but it didn't change the 000000... in the end, calls are working fine so I guess I can live with it considering this build is much smoother than the previous one. ;)
[Moto G Android Development] starkly_raving:
[MENTION=4400604]Meticulus[/MENTION] Could something have borked our IMEIs?
[Moto G Android Development] dirty_smurf45:
Expect some prank calls lol

Not from me though, I don't even have service right now.
[Moto G Android Development] classic757:
[MENTION=4658982]starkly_raving[/MENTION],

What bootloader are you on?
[Moto G Android Development] CodyF86:
It shows my IMEI the same, it's just a bug / bad formatting of a call to output a variable. If you go back a screen then click SIM status I think it is, it shows the correct values.
[Moto G Android Development] benutne:
FYI, my network says 31000. I'm on Ting. It is only a cosmetic issue, as everything else works.
[Moto G Android Development] starkly_raving:
41.19 and all partitions and the modem were updated.

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

Yeah I see it in the other screen. Panicked when I saw the 0000 lol. I know what that used to mean..trouble lol
[Moto G Android Development] classic757:
Oh, okay. And is your phone xt1031 or xt1028?
[Moto G Android Development] benutne:
I'm waiting for a user/pass from your build server so in the meantime, I'll post a bug here. I cannot change my voicemail number and my phone constantly tells me I have a VM when I have none. Is this a CM issue or something specific to this build. Also, has anyone gotten the stock VM app to work at all?
[Moto G Android Development] starkly_raving:
Boost XT1031...its an issue across the board apparently.
[Moto G Android Development] benutne:
OK, the voicemail is getting out of hand. My phone will tell me I have a voicemail several times an hour. I cannot even set the voicemail sound to "none" and have a silent pop up. The only way I can not have my phone blow up every few minutes is to turn the ringer/notifications off.

Not ideal, to say the least.
[Moto G Android Development] starkly_raving:
Can't you dial your own number and access your voicemail like that?
[Moto G Android Development] benutne:
Yes, and this isn't my issue. CM is never very good with voicemail apps. My problem is my phone is getting a notification every fifteen minutes or so saying I have a voicemail. I don't. Even if I dismiss the notification, it comes back. Worse, if I don't dismiss the notification, it STILL makes the default notification sound and the only notification up there is voicemail.

Edit: Found a workaround. Told the voicemail/phone app to FO in terms of notifications by pressing and holding on the notification and hitting the "silence" icon (a bell with a line through it). Then I installed Google Voice and set it up as my voicemail. Not perfect, but works OK.
[Moto G Android Development] dirty_smurf45:
What do I look for to find compatible kernels for this ROM? I tried something and had a hell of a mess lol it's my first time with kernels. it doesn't seem difficult in any way.
[Moto G Android Development] :
Wait for a 5.1 kernel or use a 5.0.1/2 ROM. There's no 5.1 kernels yet as far as I know.
[Moto G Android Development] Sik-1:
Attack kernel is working perfect for me on 5.1
[Moto G Android Development] itslels:
Running Optimus on 5.1, myself. Runs really well.
[Moto G Android Development] :
Well that's weird, I tried both of those and it wouldn't boot.
[Moto G Android Development] dirty_smurf45:
Same. I tried one and I only got to the lock screen; then a message saying com.something.phone had stopped. I would get consecutive soft reboots after all. I think it was for kitkat, even though I downloaded a version that was for CM12. Now I believe that it was for 5.0.1/2. Then I tried Attack Kernel (withouth reflashing ROM since i sidn't know how to backup kernel. Now i do) and it wouldn't boot.

Tapatalked with Boost Mobile Moto G (xt1031). Running Android 5.1 on CM12 by Meticulus.??the smoothness
[Moto G Android Development] itslels:
Odd. They are made for CM 12/12.1, so I'm not sure what's going on. I am not running meticulus' build, but I haven't had any issues with either kernel. Are these clean installs you guys are trying them on?
[Moto G Android Development] jglm4u:
Just wanna confirm that after installing does two kernels, my phone boot up without issues.
[Moto G Android Development] sugarbuger70:
Guys, figured out my spotify issue. Not rom related so sorry, it was the update they did on play store (4-1) so i installed an eariler version of spotify and all is good.

I get 31000 on the network oper in pulldown menu. I heard this is alltell, idk, but I'm on boost mobile but not an issue for me got data etc so am happy.

When someone asks, I just play smart give techinal crap bout the # haha

Like its on purpose

By the way if version bought out alltell, could it be that I'm roaming on version?
[Moto G Android Development] starkly_raving:
Having sporadic data drops. Its too intermittent to be able to grab a log but just thought I'd mention it.

Calls are good, gps is good, Bluetooth is good on my jabra headset, WiFi is good there's some Google apps wonkiness from time to time but it's apparently a play services issue. I mean aside from the "000000" and the occasional data drop I'd say this is more of a definite Beta versus Alpha. Good job [MENTION=4400604]Meticulus[/MENTION]!!!
[Moto G Android Development] benutne:
I seem to have borked my root. I've gone into Pillz recovery and reinstalled SU but when I open SuperSU it says "There is no SU binary installed and SuperSU cannot install it." How can I get root back? I've also tried uninstalling and reinstalling SuperSU.

Edit: Never mind. I seem to have taken care of it. I found the SuperSU zip from Chainfires website and installed that. Root restored.
[Moto G Android Development] benutne:
Installing the Optimus kernel (R11 since we're still on KK bootloader) hosed my WiFi. Left it in a state of perpetually "turning on".
[Moto G Android Development] AaronCompNetSys:
Root is built in and managed by CM now, found in developer settings. You can still install normal SuperSU from Play store (zip flashing not needed) or flashing zip.
[Moto G Android Development] sugarbuger70:
Great ROM! Okay the YouTube and other videos acting up is cause of hardware decoding by default. If I download the videos instead, open in MX player, then choose sw decoding and plays well. Otherwise its choppy no sound in MX with hw decoding.

Tried couple build props to no avail. Is there a way to turn off hardware decoding across the board so other apps can play videos (sw by default)?
[Moto G Android Development] dirty_smurf45:
Guys I'm having a problem with the themes. I'm currently using Vault theme (found in image) and it's been working like it should be. Then I try to install another theme and right after play store says application installed, I get the notification in the image attached. Does anybody know why? Anyone going through this too?

Tapatalked with Boost Mobile Moto G (xt1031). Running Android 5.1 on CM12 by Meticulus.??the smoothness
[Moto G Android Development] starkly_raving:
I don't know if its ROM related or just a fluke...but I was running the latest build here...switched back to a nandroid of stock 5.0.2 and couldn't make calls or send texts, however data was working... Had a "error 16 switch 696" Boost CS was useless had to go through Sprint customer service to get the voice network reactivated. May have been a fluke but thought it was noteworthy.

**EDIT**

If anyone has this issue call Boost "tech support" [emoji23] ... (Lol well we know their limits)...anyway tell them to transfer you to someone who can handle error 16 messages then once you're transferred to Sprint tell Tech Support to do a*"CHLS Refresh".*Then you'll be squared away. Hopefully it was a fluke but knowing every fix is a good thing.
[Moto G Android Development] parkerlreed:
One thing I noticed in the 4/3 build is that in Settings under About it still lists 3/29 as the ROM date. I just reflashed thinking I wasn't up to date.