yashsingh1/xdaforums huggingface dataset:
[Moto G Android Development] CodyF86:
I'll look at it this weekend possibly, basically the weekends are when I can get most things done other than build. Try using another music player also just to make sure.

----------

[MENTION=4736776]Shawnsch[/MENTION] [MENTION=4658982]starkly_raving[/MENTION]

and @ whoever lol :)

Soooo falcon_3.img.gz is a symlink. It's suppose to link to the carrier you currently have but turns out that isn't the case. Boost is pushing out updated fsg partitions with a symlink to verizon for falcon_3.img.gz and the a GSM model or two for falcon_1.img.gz and falcon_6.img.gz.

So here's the deal and I think someone has already done this for me, but if someone still on the KitKat FSG partition, (so if you have KitKat bootloader more or less) and from an adb shell /system/bin/ls -la /fsg/falcon_3.img.gz returns a symlink to falcon_verizon_3.img.gz

...then basically the answer is that boost is pushing out / has been providing fsg partitions with a sym link to verizon instead of sprint and we're screwed and there is no way to differentiate between boost and verizon without everyone on boost rewriting their fsg partitions....lol :/

Unless fastboot oem config carrier <name> is what sets that symlink...

edit: turns out it actually does, but that would require everyone to issue that command...lol :/

double edit: nope issuing oem config carrier sprint still sets the symlink to verizon / doesn't do anything at all...starting to be one of those it's not that big of a deal to add a few build prop lines at this point. Boost Mobile / Sprint has their fsg partitions pointed to verizon..lol

hmm Actually fastboot oem config carrier sets androidboot.carrier apparently, which then is fed to the system property ro.boot.carrier. I could actually pull the values from there, but everyone on Verizon would have to issue

fastboot oem config carrier vzw

and everyone on boost

fastboot oem config carrier sprint

before flashing this rom to get init to setup properly. It doesn't actually effect the phone working...it works now I just like things to be right. I'll play with it more. :)
[Moto G Android Development] narithlot:
how do i update to the latest build? just dirty flash it or what?
[Moto G Android Development] Krizthian:
[MENTION=5337314]CodyF86[/MENTION]

Why do you disabled the CRC?.

Greatings.
[Moto G Android Development] Ignaciodnb:
Same with Shuttle+, JetAudio and PlayerPro

Thanks for you work with this rom is really smooth and fast :)
[Moto G Android Development] CodyF86:
/*

* Enabling software CRCs on the data blocks can be a significant (30%)

* performance cost, and for other reasons may not always be desired.

* So we allow it it to be disabled.

*/

Did I break something? :/ hehe
[Moto G Android Development] Krizthian:
My english it's so very bad, and i used the Google Traductor and it's most bad.

And i don't readed the full comment :(.

Right, if the CRC it's disabled the performance it's better?

Greatings.
[Moto G Android Development] CodyF86:
yes :)

edit: Actually the more I think about it...it scares me slightly because I'm always a fan of data integrity and the actual performance increase I haven't even tried to measure yet. My phone hasn't blown up yet, but will try to test at some point.

-----

Holy crap my eri files worked. Not sure if it's driven off the build.prop alpha numeric or what the network says, so if you are on Verizon and flash what I am uploading right now once I post it, do the build.prop additions in the OP.

Mines says Boost Mobile without reading from ro.cdma.home.operator.alpha but with the eri commit I just did to my source tree.
[Moto G Android Development] starkly_raving:
Mine said "Boost Mobile" on the lock screen but the network was "unknown" in network app posted a few pages back...but dropped the eri.xml in data and set permissions and got the desired effect. [emoji4]
[Moto G Android Development] CodyF86:
Check my source tree I added the ERI files during compilation now, so everything should be good to go, without my slight build.prop operator.alpha hack...yeah gonna call it a hack now that I fixed it correctly haha xD.

Also found a way to fix init_falcon.c but I need to test it this weekend. Can someone on Boost Mobile do a getprop ro.boot.carrier from adb shell and tell me the results. Don't worry if it doesn't say sprint we can set that ourselves permanently through fastboot oem config thing, just want to make sure boost is either sprint or just nothing / unknown. I set mine to sprint so before I move forward want to make sure they don't use a different name.

Also 2 new SMS/MMS cherry-picks (try MMS again let me know) check the OP...new build posted. =)

edit: err didn't think if you are on pageplus etc etc I'll need to add an ERI file for you also.

If you are on an operator other than Boost or Verizon please post your carrier and operator numeric (6 digit number) here and I can add the overlay ERI file.
[Moto G Android Development] starkly_raving:
"unknown" is what comes back.
[Moto G Android Development] CodyF86:
Yeah that's what I figured it would default to. Basically I can have people on boost do

fastboot oem config carrier sprint

and verizon do

fastboot oem config carrier vzw

and then have init getprop ro.boot.carrier

Assuming something else isn't breaking init then it should set properties correctly, it just sucks that the symlink on at least the boost FSG partitions doesn't even point to sprint because it makes it way harder than it should be.

Basically you'll have to run the fastboot command once then ro.boot.carrier is set to sprint or vzw and init reads off of that. I could even setup pageplus etc etc etc. Will be a weekend thing probably.
[Moto G Android Development] Shawnsch:
so i can confirm that with your edits to the build prob and the new build the network now shows verizon wireless as my current network so i would say your getting close

as for mms i still am unable to send them with stock cm messaging app or google messenger handcent still works tho
[Moto G Android Development] hhp_211:
Wow such awesome news! Thank you for this.

I've wondered why the removed the eri from frameworks.

Pageplus uses Verizon network, so no additional there.

Unless you just wanted to mod one to display pp instead of vzw...
[Moto G Android Development] Pinktank:
Ignore my previous comment about TWRP please, I just mistook its 'factory reset' option for a CWM 'clean to install a new rom' equivalent, alas, it does not erase the system. So do not to 'factory reset', instead, go to advanced and select system,data,cache,dalvik and you should be good.

04-16-2015 works well with no crashes etc, tried with pa pico apps of same date. Banks had a problem where aosp keyboard would not swipe, but he fixed it in today's build.

Stock Kernel and Optimus both work, for what it's worth, the stock kernel + rom gets the highest benchmark amongst the 5.1 roms that I have tested of the same build date.

---------- Post added at 04:24 PM ---------- Previous post was at 04:16 PM ----------

Quote:

Originally Posted by classic757

I suggest you try MX Player. It's in the google play store. I have been using it for years and it works really well for me.

It's a CM bug, not a shortcoming of the installed app, they were pointing out that the error was not only in the stock app.

---------

couple confirmed bugs/suggestions culled from previous posts so that you do not have to track back:

Common to cm12.1 sources: volume control does not control songs with screen off

the new Glade Rom (no device tree uploaded yet) and the official Liquidsmooth are the only ones that have it working confirmed: Ambient Display is not functional

not in cm12.1 source: jira here , grab slimrom source for tapping privacy guard notifications bringing up app permissions instead of app info

Is it possible to switch to google webview instead of android webview?the google one is updatable and therefore better for security here is the AOSP commit https://github.com/F-AOSP/platform_f...84538ce14fe24b

Thanks for all the work!
[Moto G Android Development] starkly_raving:
This ROM has come a long way very quickly, not nearly as many crashes and issues as stock 5.0.2. [MENTION=5337314]CodyF86[/MENTION] good job man! Once the remaining few bugs and native SMS/MMS is sorted this could be a RC (unofficial) nice work!
[Moto G Android Development] classic757:
I suggest you try MX Player. It's in the google play store. I have been using it for years and it works really well for me.
[Moto G Android Development] Pinktank:
Is it possible to switch to google webview instead of android webview, the google one is updatable and therefore better for security here is the AOSP commit https://github.com/F-AOSP/platform_frameworks_base/commit/8e860f44d54685012c93d0394a84538ce14fe24b

---------- Post added at 04:24 PM ---------- Previous post was at 04:16 PM ----------

It's a CM bug, not a shortcoming of the installed app, they were pointing out that the error was not only in the stock app.

--

[MENTION=5337314]CodyF86[/MENTION] , did some research on the Ambient Display, it seems that the new Glade Rom (no device tree uploaded yet) and the official Liquidsmooth are the only ones that have it working confirmed
[Moto G Android Development] hitesh1:
Thanks

Thanks CodyF86 for wonderful CM12.1 for CDMA moto G,

If possible please add operator 40400 - Reliance CDMA

this is XT1031 flashed to Indian operator called Reliance CDMA.

I am using 15-apr build, in which data tile dose not have on / off switch.

But as I am using on/off widget it dose not bother me.

Also want to ask, as I am on 15apr15 build, can I dirty flash 16apr or later build from you, or I have to do total wipe ?

p.s.-- English is my 3rd lang.
[Moto G Android Development] Pinktank:
Finally google wakelock craze has been patched http://review.cyanogenmod.org/#/c/94759/
[Moto G Android Development] CodyF86:
I will add it but I need a 6 digit number that is only 5. Can you check again for me and yes dirty flash away. Will do a build tonight. You either mean 040 400 or 404 000 probably.
[Moto G Android Development] Pinktank:
If you are asking for the MSL/SPC, 4044** is the country+operator code for reliance delhi, so they will be wondering why it does not work if you use that as a code.
[Moto G Android Development] CodyF86:
This is why I ask. Look at the directory names; How should I format that?

https://github.com/codyf86/android_...mmit/752e7228a4aaa449293ea30c03f37f9ec525a3e1

xml-mcc404-mnc4** ?
[Moto G Android Development] Pinktank:
I believe you pad it with 0, so if it really is 404 - 4, that would be 404 004

but reliance doesn't have 404-4, so maybe he is from Rajasthan where it's 0 according to one list so it would be 404 - 000, hopefully they will reply before you build, if not, someone else from reliance Pune says it's MCC : 404 MNC : 013, and wikipedia says otherwise https://en.wikipedia.org/wiki/Mobile_country_code

...
[Moto G Android Development] CodyF86:
Hmmm he seems pretty confident it was 404 4** and a Google search shows 404 04 but says IDEA Celluar - Delhi just gonna go with 404 004 for now can always change it if it doesn't work.

edit actually it can be mnc04 according to some directories that are already there.
[Moto G Android Development] Pinktank:
I had checked other repos and they had 004 notation, hence the suggestion. I winner of it make a difference
[Moto G Android Development] CodyF86:
New build up. Just let me know, haven't even flashed it yet lol...Gonna get my weekend on tonight, see ya'll in the mornin'! Check the OOOOPPPPPPPP!!!! (I may stil even be awake haha in the morning =) )
[Moto G Android Development] hitesh1:
404 as India country code and 00 as all India reliance cdma operator code.

For GSM each state of India will have different operator code but for CDMA it is zero for all.

Hope its clear, look at screenshot attached

Thanks for considering my request.
[Moto G Android Development] CodyF86:
[MENTION=2492839]hitesh1[/MENTION]

whoops gonna do a special rebuild for ya lol will literally take 2 seconds, but yeah I gotcha now!

edit: https://github.com/codyf86/android_...mmit/504ce497459e3bd996935cb923447b692f0c143d

Now it just has to upload lol check back in 20 minutes. :)

doubled edit haha:

Of course I say that...the one time my virtual machine crashes with a big fireball of doom haha.

Updated build with Reliance ERIs will be posted sometime in the next hour, I promise. :)
[Moto G Android Development] moha07:
i am extremly sorry if its asked before .

will this rom supports dual sim . dont have enough data to check:confused:
[Moto G Android Development] starkly_raving:
[MENTION=5337314]CodyF86[/MENTION] so at this point are you synced and current with the official 12.1 nightlies? I only ask because I like keeping up with the cmx logs lol.
[Moto G Android Development] CodyF86:
[QRCODE][/QRCODE]

Yep always do a repo sync right before I build, and then once I do build, I upload it here whole process is < 3 hours.

I need more dual SIM testing to be honest, esecially after I just fixed the giant breakage in the GPE init check, don't think they've merged it yet, but its sitting on the code reivew.

https://github.com/codyf86/android_...mmit/e04afda43d24b8127f0c0f5ed11263c5e9d4d9c6

That could have been part of why there were some random FCs.

I couldn't use " as a deliminator or I could have just done /cut -d '"' -f2 but having an " as a deliminiator in the middle of C code would have made things break / fall down go boom again, so I just -c7-10ed it, were only check for 4 character file systems anyway so if it returns a 3 file system name with an extra " to th name that still rules it out lol. lol.

edit: bump / edit / I've made changes CF -4/18/15
[Moto G Android Development] starkly_raving:
You know I thought they were deunifying all the unified device builds starting with 12.1 ... If they're looking for a CDMA falcon maintainer I know CodyF86 would get my vote. Nice job man. [emoji106]
[Moto G Android Development] CodyF86:
Alright guys haha, forgot the most important part, edit my post saying you can redownload the OP, literally the only difference is the Reliance ERI file, so if you've already installed it don't worry about it unless you're [MENTION=2492839]hitesh1[/MENTION] then let me know if your carrier name is working after you flash.
[Moto G Android Development] Pinktank:
Hope you enjoyed your night out, I thought I'd preempt people yelling what is not working with the list below. Sorry I can't comment on CDMA stuff, I'm GSM.

04-18-2015 reportback

banks gapps 04-16

stock kernel, default settings

bugs confirmed:

-Ambient Display still not functioning

-Volume rocker (holding while screen off) does not skip/revert tracks

requests:

-Bring up app ops instead of app info when privacy guard notification is tapped, I believe volume buttons should not even be working when screen is off, apart from controlling tracks when enabled, according to recent JIRA commits where CM people decided volume should not be controlled when screen off - JIRA

-Use google webview instead of android webview for incremental security updates - JIRA
[Moto G Android Development] hitesh1:
Trying to download from Google drive, My net connection is little bit slow now...... downloading at 10kb/s :eek:

thanks again for considering my request :good:
[Moto G Android Development] starkly_raving:
Yeah drive has been slow for me too lately.
[Moto G Android Development] doomwithdon:
Setup wizard FC after wifi screen...XT1033 dual sim..
[Moto G Android Development] starkly_raving:
What gapps are you using? Someone had similar issues in the official nightlies because of the gapps package.
[Moto G Android Development] hitesh1:
Flashed latest zip, operator shows as boost mobile.
[Moto G Android Development] CodyF86:
Oh right right, the whole init thing is still wonked, you'll need to add the build.prop lines listed in the OP minus the last 3 lines, but change your operator numeric accordingly. You can change alpha to whatever you want but it doesn't even use that anymore after I started adding the ERI files. Reboot then let me know.
[Moto G Android Development] hitesh1:
ro.mot.build.customerid=Reliance

ro.cdma.home.operator.alpha=Reliance

ro.cdma.home.operator.numeric=40400

Did above in build.prop still it shows boost mobile.

It just a name for me , you can focus on more important things. As of now data is working fine for me. So no worries.

Edit - mistyped home as hime , now corrected , now showing as "Roaming Indicator Off"
[Moto G Android Development] starkly_raving:
[MENTION=5337314]CodyF86[/MENTION] the fastboot init isn't required for boost users correct?
[Moto G Android Development] doomwithdon:
Bancs gapps...but seems more like a dual sim issue than gapps issue
[Moto G Android Development] hitesh1:
[MENTION=4180797]doomwithdon[/MENTION] this is cdma build.
[Moto G Android Development] starkly_raving:
[MENTION=5337314]CodyF86[/MENTION] do you have a devhost or android file host account? Drive is even being slow over wifi. Not sure what's going on.
[Moto G Android Development] doomwithdon:
I thought this was unified build even for dual sim...anyways if its only for cdma then i suggest the same be mentioned in the OP..
[Moto G Android Development] Pinktank:
It is not only for cdma, I'm using on GSM, people are getting carried away :)
[Moto G Android Development] CodyF86:
Sorry about that, had to do a few things yesterday. I can try dev-host, I use to use them actually. That's weird about the reliance ERI file. I'll try to change the directory name so mnc is 000 instead of 00 and see if that does anything. Wil ltry and get a few things done tonight.
[Moto G Android Development] hitesh1:
^^^

Ready to flash anything you post ! [emoji2]
[Moto G Android Development] hitesh1:
Just notice this, data option dose not show which app is using how much data or how much data I have used till date. But other app which I use shows how much data I am using per day, per week per month etc..

Is it with me only or something in this ROM ?
[Moto G Android Development] starkly_raving:
Its a ROM issue. I've noticed in several CM12 ROMs.
[Moto G Android Development] CodyF86:
Weird i'm starring at mine right now and it's working fine, showing the apps and everything. Will do another one tonight. I'm sure you have but clear your cache's just for fun. If that doesn't fix it you may need a clean install.

Edit: I forgot you are on Reliance mobile or whatever. That shouldn't have anything to do with it, but maybe? A clean install would tell you a lot unless you already clean installed recently.

edit: some more code review fun tonight also and i'll play around with getting Reliant mobile to show up.

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

[MENTION=2492839]hitesh1[/MENTION]

Pull up that MCC MNC checker program you posted a pic of a few pages ago. What overlay does it say it's using now that you fixed the word home. It may be using the correct overlay but the position Reliance is in needs to be in a different spot for that carrier.

I'll see if I can do xml-mcc404 for now.
[Moto G Android Development] hitesh1:
^^^

Did wipe cache after every flash, and did now again, but still same. It might be due to my network provider is different. But all other ROM I tested was not having this issue. Recently I checked blisspop 5.1, it was showing network as "Roaming Indicator Off" all the time but data was counted and shown properly in data pane.

After build.prop edit overlay shows as none. And network MNC MCC still as 40400.
[Moto G Android Development] CodyF86:
New one posted. I tried to get Ambient Display to work, but it didn't heh so I'll work on that more tomorrow.

[MENTION=2492839]hitesh1[/MENTION]

What does it say now? I changed the directory just to xml-mmc404 so it should work for all 404's let me know. See if it shows anything for the overlay config. Also if you could pull a logcat maybe, just want to see what the network is telling you the MMC and MNC are because it can actually be way different than the build.prop sometimes. Just post it as a .txt file if you can. Will upload to dev-host tomorrow. I fell asleep while it was building and it was luck I woke back up lol.

Check the OP!
[Moto G Android Development] hitesh1:
Thanks for the efforts !!

Downloading new zip from OP, will get log cats as soon as flashed may be in few hrs. I am on slower network.:rolleyes:

EDIT - OP Link says need permission , you might have forgot to make it public.
[Moto G Android Development] CodyF86:
Whoops link fixed. :)
[Moto G Android Development] hitesh1:
Link fixed

Downloading 251MB now..... with 10Kb/s :eek:
[Moto G Android Development] hitesh1:
This is latest zip from OP,

Now pulling logcat...

Without any modification in build.prop it shows as Boost Mobile.

EDIT - Attaching logcat.. let me know if it is correct time of logcat. [its in rar file]
[Moto G Android Development] hitesh1:
After adding build.prop lines , now it is showing as Reliance Mobile.

In build.prop cdma.operator.alpha is only Reliance.

Big big thanks [MENTION=5337314]CodyF86[/MENTION]

Is there any way to put date in status bar clock ? Something like this - (21-Apr Tue 12:45 pm)
[Moto G Android Development] hitesh1:
Note - apk saved from 5.0.2 soak test will install on this 5.1 ROM, but all may not function , need to install them again from play store.

E.g. - pushbullet, hangout, gmail app etc.. Basically almost all apps require Google services.
[Moto G Android Development] rgnicholas:
k folks... I am giving this a try and it does seem pretty smooth. I have a couple of questions though:

the stock sms / mms messaging app does not work properly... receives but will not send... I figured this might be the case but want to verify I am not missing something... Hangouts works well for sms / mms though

is it typically safe to do dirty flashes for updated builds with this ROM?

I am on a Boost flashed to PagePlus (verizon), KK bootloader (41.13 I think), and use Philz Touch recovery 6.58.7... thanks!
[Moto G Android Development] hitesh1:
1- hangout works for sms, also other sms apps like GoSms and textra works perfectly, I am using txtra.

2- You can dirty flash updates of this rom.

As you are on KK bootloader, there will be small flicking on screen , but when you turn off your screen and turn on again, this flickering will go away. this is common problem for LP rom on KK bootloader.
[Moto G Android Development] rgnicholas:
Hey, thanks for the quick reply! Already dirty flashing the update...
[Moto G Android Development] starkly_raving:
For those who haven't read this it'll fill in a lot of blanks.

http://www.cyanogenmod.org/blog/all-about-l-part-2

**Edit**

Exciting stuff. [emoji106]

https://android.googlesource.com/platform/build/+/android-5.1.1_r1
[Moto G Android Development] hitesh1:
Any one tested Xposed on this ROM ?
[Moto G Android Development] Pinktank:
5.1.1 really nipped the google play wakelocks issue, sweet stuff, should work well once you sync to 04/22 point

so regarding the privacy guard notifications I did the legwork and found the changes in slim that load up app ops and posted them as a comment on the jira

https://jira.cyanogenmod.org/browse/CYAN-6077?jql=text ~ "privacy guard"
[Moto G Android Development] nardow:
Testing the last build right now...
[Moto G Android Development] hitesh1:
^^^

You won't be disappointed.
[Moto G Android Development] narithlot:
i tired it and installed some modules, but i get a bootloop. i would hold off on it until xposed for 5.1 gets more stable

---------- Post added at 07:50 PM ---------- Previous post was at 07:48 PM ----------

get build! been using it as my daily driver for about a week now, and everything is running great
[Moto G Android Development] CodyF86:
Think I got the app ops thing in there correctly. This one will be 5.1.1 should be done in a few hours.
[Moto G Android Development] Pinktank:
Whoa super, I'll be happy to test it in the morning, or before sleep if it is done. If it indeed works, could you post it to gerrit for review to merge?

btw I think alberto dropped "msm8226-common: Update and Fix Offline Charging for Lollipop" that you have linked in the op