yashsingh1/xdaforums huggingface dataset:
[Moto G Android Development] rgnicholas:
Quick question... well, 2... generally would you say dirty flashing these builds is ok? -and- When you do a dirty flash, would you suggest wiping the caches?
[Moto G Android Development] hitesh1:
8-may zip

did dirty flash without wiping cache .. no issues here...

but one issue which is long exists in cm, is no sim issue , after coming from airplane mode,

still exist in this build too.
[Moto G Android Development] CodyF86:
Weird I just went from airplane mode on to airplane mode off and it went straight back to 3G data connected.

edit: weird actually only does it to me when I have wifi off, when I had wifi on and did it it went back to 3G connected also.

I'll look at it this weekend try to make it restart up the RIL when coming back off airplane mode.
[Moto G Android Development] hitesh1:
Airplane mode

Even if you are in airplane mode for more than 10-15min, it will show no sim near airplane mode icon in status bar.

if you just turn on airplane mode and OFF it quickly (within 1-2min) it goes to 3G without any problem.

This is on dirty flash as well as clean flash
[Moto G Android Development] hitesh1:
Looks like everyone enjoying their weekend ! [MENTION=5337314]CodyF86[/MENTION]

For data pane I have observed that, when I move out of my city , data pane start working. And when I am back , data pane stops counting data
[Moto G Android Development] CodyF86:
Weird I'll have to roll that one around my head for a bit. Will do a build in a bit.
[Moto G Android Development] hhp_211:
Is that area normally a roaming area when you were on kitkat?

Like not native boost /sprint?

Prl issues maybe?

It seems like it would be related to the weirdness of whatever is messing up the initial setup of radio/modem
[Moto G Android Development] CodyF86:
05-10 posted. I have the airplane mode logcat and I basically know why it's freaking out, but i'm still playing around with it. Has more to do with CellBroadcastReceiver than actual airplane mode, but anyway still working on it.

edit: May have fixed it, but dual sim airplane mode will be wonked still because of this.

// FIXME on latest AOSP refresh, google removed PhoneStateListener and
// listening for SERVICE STATE intent. Same way for MSIM also we need
// to listen for intent.
// private PhoneStateListener[] mPhoneStateListener;

So I had to change this:

} else if (Intent.ACTION_AIRPLANE_MODE_CHANGED.equals(action)) {
boolean airplaneModeOn = intent.getBooleanExtra("state", false);
if (DBG) log("airplaneModeOn: " + airplaneModeOn);
if (!airplaneModeOn) {
if (MSimTelephonyManager.getDefault().isMultiSimEnabled()) {
for (int i = 0; i < MSimTelephonyManager.getDefault().getPhoneCount(); i++){
startConfigService(context, i);
}
} else {
startConfigService(context);
}
}

to

} else if (Intent.ACTION_AIRPLANE_MODE_CHANGED.equals(action)) {
boolean airplaneModeOn = intent.getBooleanExtra("state", false);
if (DBG) log("airplaneModeOn: " + airplaneModeOn);
if (!airplaneModeOn) {
startConfigService(context.getApplicationContext());
}

and we'll see what happens let me build it again.
[Moto G Android Development] CodyF86:
Sorry for the back to back. That fixed the logcat error, but the no sim thing still happens. I'll upload that to the code review because it needs to be added, but It looks like the modem is crashing and it just won't restart until you do a reboot.

Fixed one thing that was kind of related, but not the actual problem...now to try and fix the actual problem haha.
[Moto G Android Development] hitesh1:
I am not on sprint / boost

I am on Reliance India with XT1031.

Technically I am not on roaming in any city, as my operator don't have roaming contract with any other operator.

Operator charge us roaming charges on its own network in different network. [emoji12] [emoji53]

[MENTION=5337314]CodyF86[/MENTION] will flash latest build tomorrow and report back.
[Moto G Android Development] CodyF86:
Airplane mode I'll have to keep working on...they're are so many things that are still unimplemented (phonestatelistener) / being changed vastly MSIM...yeah I'll have to keep poking around.

In unrelated news I found out why the mobile network switch is disabled... no one ever thinks of CDMA... lol

https://github.com/CyanogenMod/andr...mmit/f1b6d3066e239b123375ecd5052b15db733e3e6f

Will build with this reverted and see if I can get it changed....
[Moto G Android Development] starkly_raving:
At this point I wish they'd deunify the build. :-/
[Moto G Android Development] CodyF86:
http://review.cyanogenmod.org/#/c/98073/

Building...

edit: [MENTION=4658982]starkly_raving[/MENTION] this may even be what's wonking airplane mode...maybe...we'll see.
[Moto G Android Development] rgnicholas:
thanks for remembering us cdma folks :)
[Moto G Android Development] hitesh1:
building....

looks like I should skip 10-may build and wait for this new one :o:cool:
[Moto G Android Development] CodyF86:
05-12 posted.
[Moto G Android Development] hitesh1:
12-may build

Flashed 12-may build,

Update-1 = Android is Starting.... optimizing app (LOLz I have more than 175 apps there...)

Update-2= Mobile network toggle is back and working fine. shows 1 update from CM official. will request Codyf86 to remove CM updater from our build. updated SuperSU binary (need to do this on every flash).

Update-3 = Shows Reliance mobile without any Build.prop mods. started getting calender pop-up now, it was not popping up in last builds.
[Moto G Android Development] rgnicholas:
You got my attention... I think I had better check this for my PagePlus setup ;)
[Moto G Android Development] methuselah:
I read you quote today. It will be amazing if you manage to make everything working by starting from scratch. Wish you luck.....
[Moto G Android Development] starkly_raving:
Could very well be...I'm sure you'll get it sorted out. [emoji106]
[Moto G Android Development] tarkin88:
I'm having the same issue with wifi and reboot dont work
[Moto G Android Development] vrienduinen:
XT1033 on Ting

Is anyone running this ROM on a XT1033 on Ting? If so can you let me know which version of this ROM works with data.
[Moto G Android Development] hitesh1:
This time there was no network when I went to airplane mode at first place.

In previous test it went back to 3G, but that time when going to airplane mode I was having good network.

Both tested on 12-may build.
[Moto G Android Development] hitesh1:
Looks like [MENTION=5337314]CodyF86[/MENTION] is cooking something big [emoji2]
[Moto G Android Development] CodyF86:
Lol I did one last night and was playing with some SElinux stuff and fell asleep before I could upload it, but nothing too crazy. Will do one tonight. It's suppose to rain all weekend here...more or less so i'll have time to look at airplane mode more. It still let's me turn it on and off once before it dies, so that's what makes it so weird.

There were some commits to framework_base yesterday that took care of some memory leaks and wake-lock issues so hopefully if anyone was having problems with that it will get better.
[Moto G Android Development] CodyF86:
Sorry for the back to back.

05-15 posted, will dig through the logcats more this weekend about airplane mode. Check CMs github / framework_base for some memory leak commits and wake0lock commits from yesterday that may help with deep sleep etc.
[Moto G Android Development] Ignaciodnb:
Thank you every build is so great and fast :)

PD: there's way to add to kernel selinux: permissive and e/s: sio?
[Moto G Android Development] hitesh1:
When ever I think of going back to stock, you throw something nice in ROM.

Downloading it.....
[Moto G Android Development] rgnicholas:
Thanks... I dirty flashed it over the previous build and so far, it is nice and smooth.
[Moto G Android Development] rgnicholas:
Question about Google Messaging MMS...

Hello everyone... just curious if anyone has made headway on making the default Messaging app work. I know some have got SMS functioning but not MMS (that I know of). I know there are alternatives (Textra, Chomp, etc.) and I usually fall back to Hangouts since it just works (but on this ROM, it always complains about no SIM card). I have done a little surfing around and found suggestions about deleting all the APN entries except the one you use... tried that but no go. Read somewhere that it worked f you turn off the WiFi... tried that too but still a no go.

Dunno, I just like the look of the Google Messaging app and the way it automatically changes accent colors for different users along with its simplicity. Any ideas why it still doesn't work? Maybe just an issue with CDMA derivatives? Just in case, I am attaching a log file if someone wants to dig deeper than I am capable of doing. Thanks for your thoughts.
[Moto G Android Development] iDynamics:
Does this rom have the notification sound crackle bug?

Thanks! :D
[Moto G Android Development] rgnicholas:
Hello again, I am not sure if this is a bug or an issue with a recovery or what, but I thought I would mention it. I am on the 05/15 build (clean flash) and with the phone completely off, if I plug it in to the computer to charge, it does not boot, kind of gets stuck at the flash screen (logo)... but if I start the phone and then plug it in, it is fine. I am using "TWRP-2.8.5.0-falcon-LPK" for my recovery and have moved up to 41.19 bootloader.
[Moto G Android Development] CodyF86:
Seems offline charging only works atm with it plugged into a wall charger and turned off.

You can flash the MMS_Update in the OP and it will work, but it won't have the material design for the messenger app. I just built one last night and cherry-picked this:

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

p.s. 4-17 posted in the OP.

Tell me if it changes anything for you.
[Moto G Android Development] hitesh1:
What's that ?

I am using this ROM from 15-apr and didn't see any notification sound issue .
[Moto G Android Development] rgnicholas:
Thanks, I'll give it a go and report back.
[Moto G Android Development] rgnicholas:
K... went back and did a clean install of the 5/17 build and it works well. The charging issue and the Google / Stock SMS Messenger still won't play nice with MMS. Hopefully CM or someone will figure this out in time. Thank you for your work on this ROM... overall, it is pretty sweet. :good:
[Moto G Android Development] CodyF86:
I can fix the charging issue now, thanks [MENTION=4480917]Alberto97[/MENTION]

I'll run a build real fast. I also was hoping someone else fixes the stock messaging app just because I use hangouts / google voice, so I don't even use the stock app.

I ended up having to do some crazy stuff for work this weekend, which isn't the norm...it's a long story lol.

Anyway can fix charging for now.
[Moto G Android Development] rgnicholas:
Hey, I knew that it seemed to be quiet here over the last few days -BUT- you gotta deal with life / work stuff too ;) I know that you can't be pinned down to fix every bug in the 'ole CM tree... but I certainly appreciate the things you do fix. I just want to help report back and if logs / screencaps help, let me know and I'll submit them. The stock messaging app is just a preference... Hangouts works ok for me too. Thanks again!
[Moto G Android Development] CodyF86:
5-19 posted with super sweet working offline charging lol.

They added ambient display to the CM repos, but still seems like the picking up the phone and it turning on part still doesn't work.
[Moto G Android Development] Shawnsch:
I saw ambient display was working on official nightlys but doesn't seem to be working for me can you confirm if it is working it not
[Moto G Android Development] rgnicholas:
Thanks again! Charging issue fixed :good:
[Moto G Android Development] narithlot:
ive notice that when i do a soft reboot, it wont connect a to a cell network until i fully reboot it
[Moto G Android Development] CodyF86:
I'm not dead; I just moved into a new house. Running a build now and we'll see where we are at from there, since it's been over a week.
[Moto G Android Development] hitesh1:
^^^

Good to see you back , who said you are dead ? Just we didn't poke you :)

Congrats for new home !
[Moto G Android Development] Lucas Eugene:
Thanks for your work on CDMA devices. I really appreciate it.

But is there a way to fix the data usage settings for xt1031 flashed to Page plus ( or other carriers ) for me it only shows WiFi usage and there is no option to set data limit
[Moto G Android Development] hitesh1:
^^^

This issue is not only in this ROM, almost all cm12 even asop got this issue. Tried asop by PA too. Same issue.
[Moto G Android Development] Lucas Eugene:
Yeah I know that's why I asked to fix it here as it is optimized for CDMA devices.
[Moto G Android Development] CodyF86:
Sorry for the delay Google Play Services started crashing on me a few days ago and was trying to see if a quick flash would fix it. Time for me to do a clean install.

Anyway was able to add more stuff in the mean time, adding the new commits to the OP now. (Give it 10 minutes) and the rom will be posted in about an hour.

edit: Also new PA Gapps in OP in about 5 minutes.
[Moto G Android Development] CodyF86:
05-31-2015 is posted. There are gesture controls now is settings, but I haven't tested them to see if they even work.
[Moto G Android Development] hitesh1:
^^^

Can you please upload your modified eri.XML which include reliance mobile carrier ?

Edit - was already have modified eri with me.

Thanks
[Moto G Android Development] Shawnsch:
OK so I keep having google play services crash. I even did a clean install any idea what to do
[Moto G Android Development] hitesh1:
Play service issue is 99% due to gapps, Change your gapps.

Request for this ROM users, can anyone pull stock launcher from zip and upload only launcher apk ?

I deleted it and installed nova, want to go back to cm12 stock launcher.

Thanks in advance.
[Moto G Android Development] Shawnsch:
What gapps would you recommend. I'm using the ones in op. And I can upload cm12 launcher after I get off work

Edit here you go!
[Moto G Android Development] narithlot:
i used the gapps from http://xdaforums.com/paranoid-android/general/5-1-x-5-0-x-4-4-x-pa-gapps-mirror-t3069879 and i chose mini since it got everything i needed, also everything worked great
[Moto G Android Development] hhp_211:
Gapps packages change almost as often as ROMs do, and they are about as many different ones out there now too since tkruzze left, though now him and osmossis are teamed back up to bring TKgapps to all

I'v been using the ones from here without FC issue

http://www.slimdevs.com/Gapps/Lollipop/5.1/

but the AROMA Open GApps for Android 5.1 should be good too,

http://xdaforums.com/android/software/pa-gapps-continuation-t3098071

https://github.com/opengapps/opengapps/releases

TK Gapps

http://xdaforums.com/android/software/tk-gapps-t3116347

.
[Moto G Android Development] CodyF86:
Going to do another one tonight, sorry for the delay. I actually had Google Play Services go wonky on me the other day and I had to uninstall it from the app menu in Settings and it asked me if I wanted to install the factory one then it updated itself.

Like was mentioned above there are so many versions now / they can go wonky easily. If part of gapps is crashing even after a clean install, then go into apps under settings and uninstall it and it usually will ask you if you want to install the 'factory' version, but basically what it seems to do is force it to update itself / clean install it specifically.

And also feel free to use whatever gapps works best for you. I just have the 5.1 PA nano gapps listed in the OP, but that is just to provide minimal gapps, use whatever works best.

edit: Looks like I may change the OP link to TK Gapps looks nice and hopefully reliable.
[Moto G Android Development] Shawnsch:
Looks like mine is location related as I can get a lock when on Google maps but GPS status shows a GPS lock. And I cannot locate device with android device manager location history also shows can't connect
[Moto G Android Development] CodyF86:
[MENTION=4736776]Shawnsch[/MENTION]

I just turned mine on let me see what mine does. I am able to get a GPS lock, but had it turned off so waiting for it to update.

Also looks like CM redid the CM-12.1 kernel repo, so I had to readd my stuff on top of it, so we'll see if that changes anything also tonight.

There is now a CM12.1 and a CM12.1-old kernel repo.
[Moto G Android Development] CodyF86:
06-05-2015 posted. They redid the kernel repo, but all seems well. Still need to mess with airplane mode, starting to think there are just some firmware files the new OTA is using that need to be updated in the blob repos because of the way it dies the second time.

I actually took a few days off from work and have time to just mess around with stuff, so will be back tomorrow! :)
[Moto G Android Development] Shawnsch:
OK so I clean flashed last night new build and gapps in op and no force closes on play services till this morning and now its force closing

Also *228 to program says it can't program my phone
[Moto G Android Development] CodyF86:
It was doing that to me with the PA Gapps also last week also. The way I fixed it, and not sure which of these or if a combination, but go into apps under settings and click on Google Play Services, then wait a second or two and it will allow you to click uninstall. It should then ask you if you want to restore the factory version of that program then click yes. Once it's done doing all that go back into it and clear it's cache in settings under apps, then reboot into recovery and clear cache and dalvik cache and that finally fixed it for me.

Not really sure what the deal was tbh, but was able to get it fixed doing the above.
[Moto G Android Development] Shawnsch:
I don't get an uninstall option
[Moto G Android Development] CodyF86:
Try clearing the cache real fast. I had to let it sit there for a second before it would switch to uninstall. If it still won't clear the cache there in settings then reboot to recovery and clear cache and dalvik cache.

edit: Actually clear cache then click disable, then it should pop up uninstall.

edit2: Not sure why it's greyed out. I do remember it was doing the same thing to me and I had clear cache or something like that before it would ungray.

Like I said if it still won't clear cache in settings then clear both in recovery see what happens.
[Moto G Android Development] Shawnsch:
Cleared cache in settings and recovery seems to have fixed it

---------- Post added at 04:44 PM ---------- Previous post was at 04:39 PM ----------

Any word on ambient display? I see it works in official rom
[Moto G Android Development] CodyF86:
?

The device trees are exactly the same, anything that should matter anyway. Has anyone actually tried it on the CM nightly? or just someone said it is?

If it is working ill have to look and see if I missed a small change.

If it is working on CM nightly then hopefully Linaro isn't breaking a sensor or something. Haven't had any problems on Moto yet, but Linaro 4.8 use to break the Tab 2 camera. Let me know and I'll poke around with it.
[Moto G Android Development] Shawnsch:
In the op it is listed in latest features and there are people saying it works
[Moto G Android Development] CodyF86:
It's in the changelog because it was commited to github in the CM repo, just like in mine.

https://github.com/codyf86/android_device_motorola_msm8226-common/commits/cm-12.1

All off the MotoDoze commit around May 19thishs. Someone needs to flash the CM nightly and actually see, where / is there a link to people saying it works at?

If it is working in the nightly then it's Linaro being wonky with something, but I kind of have this feeling it was commited, but it still borked somehow.

I could be wrong though.

If anyone is bored and can flash the latest CM nightly and let me know, that would be awesome.
[Moto G Android Development] Shawnsch:
I can do it I a minute
[Moto G Android Development] CodyF86:
Sweeet, thanks man. Will make it real easy to tell if it's still broken or Linaro finally made something not work correctly...lol :)
[Moto G Android Development] Shawnsch:
i can confirm it does indeed work on official nightly
[Moto G Android Development] CodyF86:
Ok cool, I guess the next step is for me to build with the normal tool chain and see if it's Linaro, or something else. I can do that tonight to test, will let you guys know here in a bit. :)
[Moto G Android Development] Shawnsch:
We appreciate your work man!
[Moto G Android Development] CodyF86:
[MENTION=4736776]Shawnsch[/MENTION]

Fixed Ambient Display and was able to still build with Linaro. Forgot to reincorporate the oem carrier config code I wrote, so have to rebuild it real fast also...lol.

Please make sure the ERI still works fine when I post it for those on Verizon, Reliance anad Page Plus. Will try and post it here in a bit when its done.
[Moto G Android Development] CodyF86:
06-06-2015 posted with working Ambient Display! Good'night! =)
[Moto G Android Development] CodyF86:
06-08-2015 posted.

Tapping the screen while in a day dream should now wake up the screen instead of bugging out for a second then turning the screen off.

PowerManagerService: Fix updating of mUserActivitySummary
[Moto G Android Development] Chikoow1:
Im using the 06/06 and i really like, very fast, im using nova launcher because is the best launcher, you need to switch the google now to nova or add.

Good work cody!

What is the difference with 06/08 build from 06/06?

How do i update to 06/08 from 06/06? Wipe dalvik and cache and flash? Or need a dirty flash?
[Moto G Android Development] narithlot:
dirty flash should be fine, i do it with every update. it works everytime :good:
[Moto G Android Development] drive2droad:
This build is really smooth & fast when compared to other Non Linaro Builds out there !!
[Moto G Android Development] narithlot:
maybe its just me but ive notice that this recent build is little laggy, with apps taking a lot longer to startup
[Moto G Android Development] Shawnsch:
Is this rom still being updated?
[Moto G Android Development] bfldworker:
Most likely not. Shame this rom had promise.
[Moto G Android Development] josip-k:
I will finally try this one.
[Moto G Android Development] starkly_raving:
Could anyone running this please post the telephony manager apk and the init scripts? Thanks in advance
[Moto G Android Development] CodyF86:
From the post above I would say yeah you might have to flash stock 5.0 first. I jumped in head first and flashed the L modem and bootloader from the start so I never had that happen.

Also I just had one of those whoops moments and apparently I don't know how to type correctly. Have to rebuild it haha, but will be done in an hour and a half and should work.
[Moto G Android Development] Ignaciodnb:
thanks so much for this rom compiled with linaro, works flawlessly :) :)

pd: you recommend some kernel like optimus or attacked? or is better with the included in cm12.1?
[Moto G Android Development] CodyF86:
Honestly it's probably just as fast if not more so with the one included, it's not completely the stock CM kernel. Look at the first half a dozen ARM commits in my source tree, but just try all of them see what you think.

...and without further adieu...after making the same mistake pretty much twice...even though it wasn't very apparent... (Thank god for the SDK and being able to read). There will be a download link in the OP in about 10 minutes with 04-12 with a working operator name. If you're on page plus add ro.cdma.home.operator.alpha=whatever to the build.prop and it should change to that.

Meticulous had the idea also, but it's basically what the first half of CM-11.0 did. There is no hidden bug or covered up bug from doing it like this. Cell Carriers just aren't providing ERI txt over their network, they are just adding an alternative ERI.xml file to their framework-res.apk because getOperatorAlphaLong() only returns a string of roaming indicator on or off if that isn't returned it's showing your operator number / 000000 (for CDMA) which is a bug in the android framework ( / the 000000 return of that function getOperatorAlphaLong() ) if a bug at all / not an issue.

So we are pulling the operator name from ro.cdma.home.operator.alpha during init (for CDMA variants only).