yashsingh1/xdaforums huggingface dataset:
[Moto G Android Development] starkly_raving:
Nice work [MENTION=5337314]CodyF86[/MENTION] ... Did you have any luck with the 3G indicator on boot or is a soft boot still required?
[Moto G Android Development] CodyF86:
Soft reboot is still required for signal indicator to work; didn't think this would take so long...lol It shouldn't have; I just did something silly without realizing it for half the day.

Going to try and look at that tomorrow.

edit: Link posted...I swear mine says Boost Mobile right now. Hopefully I don't get an email with a reply that says mine still says 000000 ;p lol
[Moto G Android Development] starkly_raving:
This is by and far the fastest ROM I've used since PA 4.6 beta 6 on this device. Thanks for the rom [MENTION=5337314]CodyF86[/MENTION]. I'm wondering what a clean 5.1 AOSP no frills built with Linaro would run like on the Moto G...
[Moto G Android Development] Pinktank:
All running well, I clean installed, didn't even restore backup. Quick question though, where did Ambient Display go?
[Moto G Android Development] CodyF86:
Whoops, Believe it or not if it's gone I think I know why. There was a setting I accidentally smoked a few days ago on accident...well kind of lol and I think it may have been that. Will add it back for the one I do tonight.

Also, I did a quick build with a few updated blobs from stock L. libril-qc-qmi-1.so and a few other QMI blobs. Well I managed to kill the signal indicator completely even after a soft reboot. So tonight after I do a normal one, I'm going to dump all the L blobs even the proprietary apps that are associated with them (a few RIL ones) and hopefully that is why I lost it completely and that might? lol fix the signal indicator completely...(or completely break it again).

There was one error message about QC-QMI that I got on a hard boot that didn't show up after a soft reboot, so I was thinking the dead signal indicator on a hard boot had to do with needing to update the blobs to L.

So we'll see later on tonight, but other than that, there was no other information in the logcats about the signal indicator (and that was only an indirect indication)
[Moto G Android Development] Pinktank:
So much to do about a dingbat indicator :D Thank you for all the work though, the ROM is great.

One thing that is super silly about CM12 is how they handle privacy guard notifications, I would push a commit if I knew any android development since slimkat already has it fixed but anyhow, the thing is, if you use privacy guard, there is a notice that says privacy guard is on, but if you touch it, it takes you to the general app info instead of privacy settings for the app, and leaves you wondering what the hell you are doing there. Would this be easy to change? I don't want to cause a whole slippery slope of feature requests, I'm sure people will come with viper etc and whole bunch of snakeoil speed boosters but this seems like a wonk in an existent bit of CM.
[Moto G Android Development] CodyF86:
Actually wouldn't be that hard to do I think. After I hash the signal indicator thing out I'm going to go back and work on this and the other thing someone mentioned as a request.

and actually check this out:

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

Think this might fix the signal indicator.

edit: actually I'm bored just going to test it now heh. :)
[Moto G Android Development] lurchi17:
What about the alarm bug? Is it fixed in 12.1? I'm not able to find anything about it..

And is this rom good for daily use?
[Moto G Android Development] Pinktank:
You mean the alarm not working in cm12? I thought that was not an issue in general anymore but anyhow, the alarm works on this one. The rom is stable and can be used on your daily phone, performs well benchmark and real life. The dev is fixing a couple things, wait for the next build if you need ambient display.

People are really addicted to flashing huh?
[Moto G Android Development] CodyF86:
My alarm works but I use timely...best alarm app ever.

Anyway signal indicator is fixed. 04-13-2015 will be on the OP In about 10 minutes.
[Moto G Android Development] Pinktank:
Thanks! Did you get a chance to chuck back the ambient display bit?

Stock alarm works too, just set it up to go off, snoozed it for ten minutes again, both worked fine. Did not try deep sleep.
[Moto G Android Development] CodyF86:
I did add the values back in. I checked on the rom I had already on my phone and I saw ambient lighting unless that is something different? But yeah I added the values back in. If it doesn't show up now then there is something else weird, but yeah just let me know. :)

edit: Posted.
[Moto G Android Development] Pinktank:
I'll put my phone to charge and flash it over. Are you confusing Active Lighting / Ambient Display? Active Lighting is the one that lowers color temperature in the evenings like the Lux app (though also causes some lag currently), Ambient Display is the one that turns on your display and shows you a preview of notification when you get one, like the Active Display app on the play store. Yay, name chaos.

Also, does gesture typing work on your keyboard?
[Moto G Android Development] drgopi1234:
I have successfully installed the ROM but I can't pass beyond initial setup . setup wizard force close this msg appears .on 12 April build.I have done clean flash.I am using xt 1033 dual sim
[Moto G Android Development] CodyF86:
Ah gotcha, yeah the setting I added back should make that work. It was the motodoze app / service, which I think is that. Let me know though. About the keyboard honestly not sure. lol :) It's just the default keyboard, but I would have to check.

edit: Looks like it showed back up, woo!

First try clean flashing the 04-13 build since it's the newest one now, but as retarded as this sounds, since it's probably hard to pull a logcat on firstboot in setup wizard. If it still does it, flash the CM nightly...if that doesn't cause a force close then dirty flash this over it and tell me if it starts working or still does the same thing.

That's my best idea to start with, about to go to sleep, but can check back when I get home from work tomorrow.
[Moto G Android Development] ncmz:
Yes, Gesture Typing work over here. That's why I left AICP cause any of the gapps I flashed could not activate that function on AOSP keyboard on that ROM. Here works just like it should :) (using mini SlimGApps).

Cheers.
[Moto G Android Development] Pinktank:
Regarding the keyboard, it does work if you install 'google keyboard' from play store so it must be a gapps issue, my bad, sorry. I'll give slim apps a chance, I used banks since PA apps development is dead and banks is what PA suggested.
[Moto G Android Development] zarac:
Just to let you know, PA GAPPS has been resurrected:

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

[GAPPS][10-04-2015][5.x] PA-GOOGLE APPS Plus(All ROM's)
[Moto G Android Development] Pinktank:
[MENTION=5337314]CodyF86[/MENTION] Ambient display, though the option is there, does not work. I think they might have pinned it to the hardware like the motoX bit, will check with the cm team and let y'all know. I suppose I'll just install acdisplay again
[Moto G Android Development] nikky2u20:
I am not able to complete the setup after first boot.

I am getting error "Setup has stopped working" if I skip the Wifi connection.

Also at the language selection screen in setup I am getting error "com.android.phone has stopped working"

Could anyone help me here.

I am on Official CM12 latest nightly.

I used both Philz and TWRP recovery.

I always do clean wipe.

PS: I am actually getting this issue with all Android 5.1 based roms.
[Moto G Android Development] Pinktank:
Wait, you are not using this rom but asking here? This is not even CM12. No wonder developers burn out early
[Moto G Android Development] nikky2u20:
I downloaded this rom and flashed this rom and gapps.

And then at setup page i am getting the mentioned error.
[Moto G Android Development] Pinktank:
So you are not on official cm12 nightly..

What phone do you have, xt1032 / xt1028 etc?

Which dated build did you flash? Did you check the MD5 after download? it could be a bad download.

You flashed the gapps from the first post?
[Moto G Android Development] nikky2u20:
Hi,

I am having XT1033 Dual sim.

I used the PA gapps downloaded from here: http://xdaforums.com/android/software/reborn-gapps-5-t3074660

I flashed build named: cm-12.1-20150413-UNOFFICIAL-falcon.zip

And after getting error I restore my previously saved CM12 nandroid backup.
[Moto G Android Development] Pinktank:
From that thread, you definitely grabbed the 5.1 right, not the 5.0? Here is the direct link to the pa gapps nano

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

It could be that you are on the dual sim by the way, I don't know if anybody else tried this on the dual sim

Oh and btw, USB does not work for data it seems, only charging.
[Moto G Android Development] nikky2u20:
Thanks Man,

Will try once more by using the nano gapps.
[Moto G Android Development] drgopi1234:
I have same problem as yours on xt 1033 setup wizard stopped
[Moto G Android Development] nikky2u20:
Still facing the same issue. :(
[Moto G Android Development] classic757:
[MENTION=5337314]CodyF86[/MENTION], on your latest build (very nice btw! :good:) in the upper left hand corner of the lockscreen it says Boost Mobile. I am on the xt1028 Verizon variant of the Moto G. Is there any way to change the carrier name?
[Moto G Android Development] lurchi17:
Last question before flashing (Sry didn't flash for a long time, so I'm not up to date anymore): Is xposed running nice with this rom?
[Moto G Android Development] classic757:
Xposed for Lollipop is a work in progress at the moment. I would not recommend using it on any cm12 rom until more of the kinks are worked out and it is more stable.
[Moto G Android Development] starkly_raving:
I would say its safe to bump this from experimental to a solid Beta. [emoji106]
[Moto G Android Development] mortrackz:
Agreed. Blazing fast and bug free.
[Moto G Android Development] CodyF86:
Open up a terminal and type getprop ro.cdma.home.operator.alpha and tell me what it says. it's pulling from the build.prop so whatever that is set to is what it should say it was just a one line change. http://review.cyanogenmod.org/#/c/94331/

Maybe the init script isnt working right, but see what that value is set to and let me know.

As for the xt1033 thing. It's kind of hard to get a logcat stuck in setupwizard...i think?

edit: lol whoops yeah you said the nightly was crashing also nm. on the dirty flashing it.

Can anyone on xt1033 try flashing an older 5.1 rom and see if it's always been that way?
[Moto G Android Development] Lucas Eugene:
On your last build the screen wakes itself up every time I pit it to sleep.

I am using optimus kernel ( latest build)
[Moto G Android Development] Pinktank:
So it looks like the non-gyroscope part of ambient display should be working but could be something upstream as that is part of the wonky development areas for cm at the moment.
[Moto G Android Development] Lucas Eugene:
I have disabled ambient display
[Moto G Android Development] Pinktank:
This is bizarre but there is a bug with twrp, others have reported it on pa gapps, I would get error code 40 flashing on a clean install telling me I can only flash it on top of a pa gapps installation when I didn't have any gapps installed yet. Factory wiped, advanced wiped the same things as factory, factory wiped again and it works.... this is silly. Others reported force closes were resolved using the same problem and I thought that was wishy washy but I just couldnt flash, downloaded multiple times, md5 checked and all, and it only flashed after multiple wipes. Again, I know this sounds like voodoo..
[Moto G Android Development] Shawnsch:
I too have a xt1028 and it shows Verizon when I ran getprop ro.cdma.home.operator.alpha it comes back with boost Mobile
[Moto G Android Development] CodyF86:
[MENTION=4736776]Shawnsch[/MENTION]

Hmm then the init script isn't even running correctly for now if you have Verizon use system tuner or a text editor and adb if you know how and add an entry in the build.prop for ro.cdma.home.operator.alpha=Verizon I'll have to see why init is messing up.
[Moto G Android Development] Shawnsch:
I had made a flashable zip for cm 11 that still works it has a more complete APN list and build prop tweaks actually seemed to get data quicker but could just be me the link is http://xdaforums.com/showthread.php?t=2774325

---------- Post added at 10:51 AM ---------- Previous post was at 10:46 AM ----------

By the way build prop edits were pulled from stock Verizon build prop

---------- Post added at 10:56 AM ---------- Previous post was at 10:51 AM ----------

Sorry for multiple posts but just noticed that network shows as t-cdma 64 in network info not sure if it will help find anything or not but I used this app to get to it https://play.google.com/store/apps/details?id=de.mangelow.network[/url
[Moto G Android Development] sugarbuger70:
Just wanna confirm this kernel. http://xdaforums.com/moto-g/development/kernel-optimus-kernel-t3024697. Works flawlessly on this ROM. Thanks codyF86 for a smooth ROM best out there in my opinion

I'm on boost mobile xt1031 with lp bootloader and modem and dirty flashed the kernel after this rom and this ROM as is over soak without issues.

---------- Post added at 01:58 PM ---------- Previous post was at 01:54 PM ----------

And no more data/media/0/0/0/0/0/0/0 bs anymore lol
[Moto G Android Development] Pinktank:
The following install works flawlessly so far, no hiccups or force closes, see TWRP note before flashing if you are not using CWM/PhilzTouch

The only thing that does not work is the Ambient Display, and that could be an upstream problem, or one that needs some device linking

- h2o64's TWRP 2.8.60

I had force close with slim gapps, and PA gapps would not install until I cleared the system twice, others reported this on the PA gapps thread, It sounds cray-cray but I tested three times to make sure I wasn't having some placebo or download problem, MD5 check and all. So go to wipe, 'factory reset', go to advanced, and wipe all but internal storage again, then flash rom and apps. Possibly a TWRP bug? I had this once with the first nexus 7.

- [MENTION=5337314]CodyF86[/MENTION] CM-12.1 04-13-2015

- pico PA gapps: https://www.androidfilehost.com/?fid=95916177934552873

[from http://xdaforums.com/android/software/reborn-gapps-5-t3074660]

- stock kernel is perfectly fine, but others noted success with optimus as well, I won't speak to it since I don't know
[Moto G Android Development] CodyF86:
Err wait just want to make sure I read that right it displays Verizon in the upper left? But getprop shows boost mobile? Either way add the build prop line you can make it say anything you want.

I'll look at the init script. There is a file called init.c that runs on bootup that sets system properties and its suppose to set props depending on what radio what carrier etc then it reads the build.prop. the Verizon / boost mobile split must be wonky.

I'll also add an update PA gapps or something tonight if there is one (on phone till I get home only skimmed replys). I clean installed with the pa gapps, hopefully updated ones might be better.

Also new build tonight.
[Moto G Android Development] Shawnsch:
Wow not really sure what I was thinking ment that it is on Verizon but shows boost Mobile
[Moto G Android Development] CodyF86:
Yeah just add ro.cdma.home.operator.alpha=Verizon to build.prop for now. You could even do setprop ro.cdma.home.operator.alpha Verizon and it should change it till Verizon until you reboot just to test. I'll have to look at the init / logcats

They just merged android-5.1.0_r5 into the CM code, will do a new one tonight.

[MENTION=4736776]Shawnsch[/MENTION]

lol so I already looked into it and I'm slightly surprised by what I found.

fp = popen("/system/bin/ls -la /fsg/falcon_3.img.gz | /system/xbin/cut -d '_' -f3", "r");
fgets(cdma_variant, sizeof(cdma_variant), fp);
pclose(fp);

and then you have an else statement that defaults to boost mobile.

and then

INFO("CDMA variant=%s", cdma_variant);
if (ISMATCH(cdma_variant, "verizon")) {

The above is the code that runs to pull info from the fsg partition. That command actually returns verizon for me also, which is wrong...but something is breaking down where cdma_variant isn't getting set to verizon so it defaults to Boost Mobile. If init was working correctly...yours would be set to verizon everytime and mine would be backwards and set to verizon.

So there are two issues...lol...one is that the command returns verizon for me also, so that alone tells me how they are doing it just isn't going to work and the other issue is that cdma_variant isn't getting set to verizon even though the command returns verizon.

lol for now if you are on verizon you will need to add these to your build.prop I'll add it to the OP.

That just blew my mind it was so backwards.

ro.mot.build.customerid=verizon
ro.cdma.home.operator.alpha=Verizon
ro.cdma.home.operator.numeric=310004
ro.com.google.clientidbase.ms=android-verizon
ro.com.google.clientidbase.am=android-verizon
ro.com.google.clientidbase.yt=android-verizon

EDIT: I need a favor.

Someone who has Boost Mobile and preferably still on Kit Kat modem pull up an adb shell then

su to get root

then

/system/bin/ls -la /fsg/falcon_3.img.gz | /system/xbin/cut -d '_' -f3" > /sdcard/log.txt

then open up the log file and tell me what it says.

I know how to fix the init...(thanks to [MENTION=4480917]Alberto97[/MENTION] from early L)...I think, but then I think it's just going to set everything to verizon beause the way they have been checking the cdma variants isn't even correct.
[Moto G Android Development] CodyF86:
4-15-2015 is posted. If anyone see's my edit above and can run that command and post the results that would be awesome.

Sorry for the back to back, just an update.
[Moto G Android Development] ATTACK:
The line you wanted to run in shell just stalled out. So I ran the first half (before the "cut").

Stock Boost 210.12.57

/system/bin/ls -la /fsg/falcon_3.img.gz
lrwxrwxrwx root root 2014-08-07 20:21 falcon_3.img.gz -> falcon
_verizon_3.img.gz
[Moto G Android Development] Shawnsch:
So I just got a pic message and Evey time I click download it says download failed. I'm on xt 1028 with Verizon and ideas?
[Moto G Android Development] hhp_211:
Which messaging app?

Maybe try temp switching to another like hangouts or eight.sms and see if it received it then
[Moto G Android Development] Shawnsch:
Hangouts doesnt even show the sms and when i type a message and hit send it says insert sim to send. downloaded handcent and seems to be working with it also stock cm12 messaging app doesnt work but read it is a cm issue

ps i usually use googles messaging app which couldnt send or recieve pics either
[Moto G Android Development] Shawnsch:
ok so is it possible that it is the eri.xml from what i have read that will fix our T-CDMA 64 showing up

ok found this http://review.cyanogenmod.org/#/c/61010/ its for cm11 but i wonder if there is something similar for cm 12 might be worth a look CodyF86
[Moto G Android Development] CodyF86:
So wait T-CDMA 64 is showing up in the upper left part of your screen or just in network info? Sorry let me go back a reread the replys, just woke up to go to work lol. :) Will look at that commit though.

Did you add all of the build.prop entrys listed in the OP then reboot? Look below.

From the output of that ls command I'm not even sure there ever was a way to determine between Verizon or Boost on Boot up / init and it was all a pipe dream / broken to begin with / since CM11 lol :/

the fsg partition contains packed files for all the possible carriers, but it looks like it's the same between the two also. If someone with verizon can run the same command, don't worry about the additional cut command just run the ls command.

The MMS thing there is a patch they are working on. http://review.cyanogenmod.org/#/c/94451/ and yeah the stock sms app is wonked atm use hangouts.
[Moto G Android Development] Shawnsch:
T-Cdma sill shows in network info and after looking in the eri.XML it only has T-Cdma listed in it
[Moto G Android Development] ATTACK:
Shot in the dark, but...

Couldn't Verizon users run - fastboot oem config carrier vzw - to set the proper fsg?
[Moto G Android Development] PhurionN:
Hello, is it necessary to flash the ROM over Lollipop bootloader or I can flash it over Kitkat Bootloader? Thanks in advance :D
[Moto G Android Development] starkly_raving:
[MENTION=5337314]CodyF86[/MENTION] how hard would it be to apply the CDMA fixes such as they are from CM12.1 to a pure 5.1 AOSP rom?
[Moto G Android Development] Shawnsch:
I'm on KitKat boot loader and its working fine. You will get a screen flicker till it is booted up just lock the screen and unlock it and it goes away
[Moto G Android Development] CodyF86:
I can fix that but what I meant is that it shows boost or Verizon in the upper left and

Lock screen right?

Possibly but it would have to be boost users because currently the file the

Syntax check returns verizon even on boost. The fsg has the compressed files for all carriers

So I don't know if there is suppose to be significance to the falcon_3 file or

They didn't even know what they were doing I'll have to play with it.

5.1 aosp should already have the CDMA fixes. That's where it came from. The carrier

Text fix is just one line that's listed in a link in the OP.
[Moto G Android Development] Shawnsch:
With the build.prop edit it shows verizon
[Moto G Android Development] PhurionN:
Hi, I´vee trying the ROM for like and hour and what can i say, it´s amazing, the smoothest ROM i´ve tried in 5.1. I just wanted to thank you developer for your hard work. :D

Cheers
[Moto G Android Development] CodyF86:
Just got home and installed that app. Mine shows roaming indicator off for current network, so it's just a cosmetic issue with the ERI information. Probably from the one in the android/cm code, I'll check out that commit see if I can fix it anyway though.

Also, dove deeper into ERI files might be able to fix the Carrier name the slightly more awesome way with overlayed ERI files for boost and verizon. Verizon will still need to add those build prop lines in the OP until I can get init figured out / if it's possible to.

EDIT: Check this. We'll see if this works tonight. If it doesn't (which it should) I can still build it the way we are doing it now.

I'm just not sure if the overlay is driven from the build.prop operator numeric values or from the operator numeric the network tells it, so we will see. If it's driven from the build.prop operator numeric will still need to add the OP build.prop additions for Verizon.
[Moto G Android Development] Ignaciodnb:
Hi, today I found a little bug :( in settings i have activated Playback control with volume buttons, but when i have the screen off and listening music with default player or shuttle don't work volume keys for skip tracks