yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) Android Development] Ken C:
OK, got the rom to download eventually. It's probably on my end where I'm getting these slowness issue. That being said. Flash went fine no issues there, options for everything got moved all over from where they were, also no big deal. Just got it going so let's see what happens. Thanks for the new 7.1 I'll probably be back later with impressions right now running great though. And I love it that pie controls are built in, makes life a little easier and it's appreciated.

Y'all be good✌️

Update : I can confirm Bluetooth not working for me, and for some reason Adaway gives me an issue when it gets to the copying hosts part of the app. No worries though going to see if the workarounds the app recommends will work

Update 2: lol I was on a version of Adaway that was 2 versions old so as I updated it, no problems
[X Style (Pure) Android Development] chris_dis:
[MENTION=4745578]sixohtew[/MENTION], I just reflashed the rom and surprisingly bluetooth is working now. Must have been something else that interferred. Thank you again for bringing us this rom, love the customizations.
[X Style (Pure) Android Development] Ken C:
You just reflashed the rom itself? Nothing else?
[X Style (Pure) Android Development] ACardAttack:
So glad this is getting updated! Favorite rom for the phone
[X Style (Pure) Android Development] chris_dis:
Well, I did a clean install. No clue why it wasn't working yesterday.
[X Style (Pure) Android Development] Ken C:
Cool I'll look into that later on but thanks for the info.

I did a clean install the first flash. Wiped everything but sdcard and internal storage
[X Style (Pure) Android Development] Ken C:
You use twrp for your recovery I'm guessing? If so did you do the default wipe? Not going into advanced wipe? Just trying to see the differences is all of there are any.
[X Style (Pure) Android Development] bashorungaa74:
Each time I tried to share picture through whatsapp it will give an error of "sharing failed. Try again later" and instead to displayed the picture to be shared it just blackout and the once the sent botton is clicked it then give the error above.

Another bug I also discovered today is that without using the phone today I discovered that it was extremely hot to the point that I can't handle the phone which is a sharp contrast to yesterday when the latest build was flashed. The phone was so cool. [MENTION=4745578]sixohtew[/MENTION]

---------- Post added at 12:05 AM ---------- Previous post was at 12:01 AM ----------

Would the details of the phone in about phone be showing Pixel or the correct phone name
[X Style (Pure) Android Development] sixohtew:
First let me say I just installed whatsapp and I cannot recreate the problem you're having, see attached pics... As for the phone getting hot, have you done anything to the kernel? I.e. over clocking under clocking changing governors anything like that? My phone has been cool to the touch with excellent battery life..I'm starting to think moto maker has some hand in this as all moto makers moto x pure edition's we made in American and each one personalized. So an Amazon version (with ads in the app drawer and whatnot) may not work the same as mine..last pic for battery life [edit] ALSO notice the alert that I sent as a pic message, whatsapp clearly states custom roms may cause problems with the app...twice...but like I said, there's the conversation with my mom and my buddy to test picture messaging and it works fine
[X Style (Pure) Android Development] capeorigins:
Hmm.. that actually would make a lot of sense. And yeah! The build is very stable IMO. the only thing that I've noticed really, is that no one can hear me on speakerphone, idk why. seems to be a CM bug or something.
[X Style (Pure) Android Development] sixohtew:
I just called my mom on speakerphone and she heard me clear as if I was talking through the headset, and side by side I could hear my voice just fine..not sure why you guys are having these issues except maybe depending on where you bought the pure from, your model number may be the same but their may be changes in the software. Maybe try a clean flash, but again if you do, you WILL lose wave and pickup to wake, as they will be greyed out. But you could test and see if it'll work better for you...if you do clean flash I recommend 1. Wipe data (except for scard and data/media) 2. Install ROM. 3. Wipe data again 4. Flash Gapps, 5. Reboot (which will take some time to boot so be patient) this is what I did with my 11/30 build then dirty flashed 7.1.1 on top and everything's working fine
[X Style (Pure) Android Development] capeorigins:
Well, I may try to clean flash, but it's the same on every CM rom for me. Although before that happened, I had a major echo which is still a problem on my end for some reason. They can hear themselves talking, and not me lmao. I atually had the same problem on cm13, the only rom that I found didn't have a echo, was Dirty Unicorns.

I bet it is difference in hardware, is there anything I can do on my end?
[X Style (Pure) Android Development] sixohtew:
For the echo? I don't think there's anything user wise you can do. If you were to tell me when you were on du I could see if I could find a commit that perhaps would stop it..if you're going to clean flash to test, I suggest flashing 7.1 first, let it boot all the way up (passed the upgrading and downloading of apps) after wiping the data twice, one first and one after flashing the 7.1 ROM, then when you'll all good and set dirty flash the 7.1.1 update and see, or like I said you can clean wipe the 7.1.1 build just do it twice. Once before flashing the ROM and once immediately after. Then flash Gapps. And you don't need to flash the new moto cam as this build includes it (the updated moto cam that didn't have video working now works fine, it's the moto g4 camera)
[X Style (Pure) Android Development] capeorigins:
Nice! I noticed the new camera, it's awesome. And yeah, would me going back to DU to test help at all? I can if it helps. I'll try clean flashing too, and see if it's better
[X Style (Pure) Android Development] sixohtew:
Flashing to du won't help, but if you can member when it was working for you I could check out their gerrit and see if they have a commit to stop echos.. cause again I'm not able to reproduce the issue, and I've been on this ROM since I built it and honestly, I haven't had any issues
[X Style (Pure) Android Development] capeorigins:
Sure thing, the last build that was working for me was the september 10th build:

https://download.dirtyunicorns.com/clark/Official/DU_clark_6.0.1_20160910-0038.v10.6-OFFICIAL.zip

Thanks [MENTION=4745578]sixohtew[/MENTION]! Lemme know if you need any testing for it
[X Style (Pure) Android Development] sixohtew:
https://plus.google.com/+GregKobey/posts/WWi4oigthMk

https://plus.google.com/+GregKobey/posts/6NptMmGiagm

Screenshots shared to google+ no issues
[X Style (Pure) Android Development] bashorungaa74:
I am using the kernel that came with your build no changes in form of under or over clocking. On the whatsapp issue my further test revealed that this only occur with picture taken when this os running on the phone meaning that I could load pictures taken prior to flashing RR N while I was still on my old CM 13.0 OS. in fact, I try to attached a screenshot but I couldnt giving me error. So you can try take new pictures and then try to send them through Whatsapp. Trying to narrow down the possible cause of the bug.

UPDATE: I could send the same screenshot through BBM, telegram but can't send the same pictures through Hangout, Google+

You're doing a fantastic job. Thank you.
[X Style (Pure) Android Development] chintandavda:
I stay in India, there is no Moto Maker here.

I could send the screenshots on Whatsapp if used any different camera and gallery app like Cymera, so i guess there is an issue somewhere in the stock gallery/camera.

Also when i started screen record from the power menu, it wont stop, when i press the stop button, and i had to restart my phone again just to make it stop.

And WiFi seams slow to me at times. And some times it works on its original speed.
[X Style (Pure) Android Development] ffonegod:
Lastest rom running nicely.. Battery life improved.. Only problem I have is I can't turn Bluetooth off from the status bar(grayed out but still on) unless I go in settings..
[X Style (Pure) Android Development] Sagar_1401:
[MENTION=4745578]sixohtew[/MENTION] please add volte patch for reliance jio
[X Style (Pure) Android Development] sixohtew:
You've seen my screenshots of whatsapp right? I can't recreate the issue cause it works fine for me...
[X Style (Pure) Android Development] sixohtew:
I found some commits that were different than mine..hopefully in the next build i'll fix it
[X Style (Pure) Android Development] sixohtew:
Bluetooth quick setting works fine for me..I can't recreate the issue
[X Style (Pure) Android Development] sixohtew:
This shows Bluetooth is working with quick tiles
[X Style (Pure) Android Development] Sagar_1401:
Thanks bro...
[X Style (Pure) Android Development] sixohtew:
I need a boardconfig line of code which I think I found.. So well see
[X Style (Pure) Android Development] ACardAttack:
Plans for being able to unlink ringtone and notification volume?
[X Style (Pure) Android Development] bmoses:
I backed up everything last night and wiped and reflashed everything. Installed the original build first, verified battery stats were good, then dirty flashed the 2nd over it. After doing that I'm back to battery stats not being reported correctly. Everything else about the ROM is working great and super smooth!

Here are screen shots of the battery stats. As the battery gets used everything keeps going to Bluetooth, even if I turn off Bluetooth it still goes towards it.

http://i1102.photobucket.com/albums/g442/bradmoses/Mobile Uploads/Screenshot_20161213-072552.png

http://i1102.photobucket.com/albums/g442/bradmoses/Mobile Uploads/Screenshot_20161213-072556.png
[X Style (Pure) Android Development] Sagar_1401:
Bro i saw that in cm 14.1 official cmx log they just added the volte vpns for reliance jio here is the link for it

https://review.cyanogenmod.org/#/c/174539 (fixed reliance jio India apn)

https://review.cyanogenmod.org/#/c/174542 (add reliance jio ims volte apn`s)

Why not copy the same board config line code into ur build??

https://www.cmxlog.com/14.1/clark/

Check the 20161212 log. You will find that there
[X Style (Pure) Android Development] sixohtew:
ill look into that, i noticed with my newest build it was only showing bluetooth. prolly a cm bug but im gunna try to fix it.. the original 7.1.1. build my battery stats were on par
[X Style (Pure) Android Development] sixohtew:
i looked at it and hopefully these commits will allow volte to be enabled... i cherry picked them and we shall see
[X Style (Pure) Android Development] sixohtew:
you mean the sliders? or pressing volume down or up? because with me, if its a sound, when i press volume down the sound volume slider goes down, and just on the homescreen pressing volume down or up changes the ringtone level.. i know theres a commit somewhere on cm's gerrit that allows this, however i dont think its necessary
[X Style (Pure) Android Development] ffonegod:
Yes it turns off from the quick settings but when in Bluetooth settings it still shows ON
[X Style (Pure) Android Development] hartreim:
I think he means that ringer and notification volume are linked right now. Would be nice to be able to set different volume levels for each.
[X Style (Pure) Android Development] abense:
Themes yet?
[X Style (Pure) Android Development] sixohtew:
[youtube]dsEJjrhdLPM[/youtube] this shows the toggle works and turns on and off Bluetooth. I'm almost 100% positive that since this was a moto maker phone, some of the hardware and software are having issues. As I said before and proved with other issues with pics, since I cannot recreate your problem, I can't fix it
[X Style (Pure) Android Development] sixohtew:
Cm is close to merging the theme engine, once that is merged youll be able to theme like crazy
[X Style (Pure) Android Development] sixohtew:
Ah I see. I'll look into that
[X Style (Pure) Android Development] LBSpeller:
Does this ROM currently support system profiles?
[X Style (Pure) Android Development] sixohtew:
Yes it does. Right in the settings ;)
[X Style (Pure) Android Development] hartreim:
Thanks!
[X Style (Pure) Android Development] ffonegod:
Battery status showing incorrect data after all day used. In fact SOT up to 3hrs.. Here it show 1 percentage used
[X Style (Pure) Android Development] sixohtew:
And when you clicked the screen button did it tell you how long your sot was?
[X Style (Pure) Android Development] ffonegod:
Yes it did 3hrs SOT
[X Style (Pure) Android Development] LBSpeller:
Many thanks. Could you tell me if there is a QS tile for the power menu and system profiles. Also, is there the option to customise long press actions for the navbar soft keys, and is there the option to set a custom button in the navbar? Those are about the only things I use xposed for, and since that is not available for nougat I would be happy to use this ROM if those customisations are built in :)
[X Style (Pure) Android Development] sixohtew:
As of now there is no qs tile for power menu or system profiles (mostly because you can customize the power menu and just hit the power button. System profiles will probably be coming soon) and yes there is a way to customize the nav bar, go to Resurrection settings, go to buttons and click nav bar, then click the smartbar settings, and click toggle button editor. Once you do you can long press on each nav bar icon and chose its function, as well as add more icons to the nav bar
[X Style (Pure) Android Development] sixohtew:
That's odd, I went to my backup of 7.1.1 since I'm testing multiple Roms, and it's still showing battery stats as correct. Try wiping dalvik and cache in recovery.. again no matter what I do I can't recreate this small issues..But I'll look into it
[X Style (Pure) Android Development] LBSpeller:
Thanks again. The reason i like to have the power menu accessable from the Q's tile is because I had a bad experience in the past with a hardware button failure and since then have always made sure I have an alternative method. Besides, it saves wear and tear on the hardwear, lol. But I am sure I can live without it. I will probably wait until the system profiles have a QS tile though, as I use them a lot and need fast access. Other than that I think this ROM sounds pretty much perfect firm my needs.
[X Style (Pure) Android Development] ffonegod:
Wiping dalvik and cache worked
[X Style (Pure) Android Development] sixohtew:
Glad we figured it out
[X Style (Pure) Android Development] bmoses:
assuming i followed correctly and we are talking about the same issue i posted with having incorrect battery stats, i tried wiping cache/dalvik cache again in recovery and my battery stats are still not showing correctly. bluetooth is the only thing showing up and all "usage" is going towards it.
[X Style (Pure) Android Development] sixohtew:
And how often are you using Bluetooth? None and it's still showing only Bluetooth? Wiping dalvik and cache worked for someone..Not sure why you're still having the problem..You may want to do a backup and the clean flash the ROM and see if it helps... I've been using my phone for a little over an hour with constant use.. all my battery stats are fine
[X Style (Pure) Android Development] bmoses:
hmmmm.... i already attempted a complete wipe reinstall to see if that would correct it and it did not. i have bluetooth on all the time but only use it for music in my car about 30 minutes per day. even in the morning when i take it right off the charger, bluetooth on but not connected to anything, it starts out only showing bluetooth as using the battery. the original release of the ROM worked fine, its the 2nd release that seems to break the battery stats for me. i also tried turning bluetooth off for a bit and usage still went towards it with nothing else showing up. both times i tried doing the original ROM and then dirty flashed the 2nd release overtop, should i attempt to just install the 2nd release after a clean wipe?
[X Style (Pure) Android Development] sixohtew:
I'd say do a backup first then clean flash. They only problem I had with clean flashing was the gestures were greyed out..So give it a shot and wipe data, or you can wait until my super slow computer finishes compiling the next release
[X Style (Pure) Android Development] bmoses:
Lol :) I can wait, no hurry here. Everything else with the ROM has been great, battery life is good too, it was just the stat thing that's messed up. I'll try a dirty flash when you get the new build done first and I'd it's still wrong I'll try another clean wipe from the latest build. Thanks!
[X Style (Pure) Android Development] bob4al:
This rom continues to work quite well for me. Very happy all in all. Just relatively minor issues really. One has been discussed frequently and that's speakerphone volume issues. The other is my phone will randomly go into silent mode, no sound on notifications, and I will see that the quick tile has been put into do not disturb mode. I thought maybe i was hitting the tile by accident so I moved it to the second page which I never access but the phone still goes silent on seemingly random occasions. Anyone else experiencing this? Thanks.
[X Style (Pure) Android Development] bashorungaa74:
[MENTION=4745578]sixohtew[/MENTION] I can't wait for another update that will make the rom more buttery and possibly squashed some bugs that I am experiencing. Checking on...........
[X Style (Pure) Android Development] hartreim:
Something doesn't look right. Look at my stats.

Using a Style
[X Style (Pure) Android Development] jimlightner:
I'm having the same battery stats issue to..not really a big deal for me..I'll try a couple things and report back.I use my Bluetooth always though.. Galaxy gear s3..
[X Style (Pure) Android Development] sixohtew:
And everyone who is testing has the xt1575 clark Moto x pure edition? No one running with the style or xt1572? Just making sure cause I'm having trouble trying to fix something I don't have an issue for. Example: I have substratum support for one build and I have no issues with bootloops because of theming system UI..And Nexus 6p users on 7.1.1 stock rooted can't theme system UI without a bootloop. Don't worry I'm still hard at work trying to squash these bugs but without having the issues, it's very hard. Just wanted to throw that out there
[X Style (Pure) Android Development] ffonegod:
Yes I have the XT1575
[X Style (Pure) Android Development] sixohtew:
:emperor from star with: good...good lol
[X Style (Pure) Android Development] daniel.1983:
I have the xt1572 eu. Everything is great! :D Not encountered any single problem that has not been discussed here. Thank you for your support.
[X Style (Pure) Android Development] bashorungaa74:
Yes I have the XT1575
[X Style (Pure) Android Development] jimlightner:
Yes sir xt1575...sprint network..great work sixohtew thank you...

---------- Post added at 12:21 PM ---------- Previous post was at 12:19 PM ----------

Yes xt1575 sprint network
[X Style (Pure) Android Development] fierogt42:
VoLTE support?
[X Style (Pure) Android Development] hartreim:
Using a XT1572
[X Style (Pure) Android Development] bmoses:
XT1575 here as well.

Also i did some more testing on the battery stats last night and before when i tested with turning bluetooth off i must not have left it off long enough or something because last night i tried turning it off again and more things started showing up as using the battery other than bluetooth.
[X Style (Pure) Android Development] sixohtew:
Right now no, I have a build going right now that hopefully has volte fixed..When it finishes I'll test and report back
[X Style (Pure) Android Development] Sagar_1401:
But it is very difficult to add volte driver...

In cm14.1 they did try but it didnt workout... Indeed

None of the rom has a volte driver for reliance jio ....

It does has that band which jio also have but the driver is the main issue..
[X Style (Pure) Android Development] ban.codrut:
This was an issue started from CM merging some Code Aurora commits ( or something into the headers, my memory getting low).

It has been fixed after some commits emerged about cleaning up the merged code.
[X Style (Pure) Android Development] hartreim:
Same process. I'm getting bootloops when trying to boot. Only the first boot after dirty flashing the newest build goes OK. Battery stats look weird. 36 hours with one charge?
[X Style (Pure) Android Development] sixohtew:
I have a new build made, again dirty flashing is recommended (the initial setup won't restore apps) but the Bluetooth needing selinux switching is fixed, so privacy is secured. Volte still doesn't work after a lot of time trying to get it fixed :/ but it's resynced and features that weren't sticking now, well, stick lol. This build does support substratum, if you didn't notice it from the last build. You may also see a new application in your app drawer called "chop assistant". What this does is allow google assistant to work by saying 'ok google' and not have the retaining voice prompt pop up first. I didn't want to mess with the build.prop because some people may have issues, but I spoke with the developer of the app and he gave me permission to put chop assistant in the ROM. I haven't heard back from the developer of 'get assistant' yet so if you want google assistant, you can either manually edit the build.prop or use 'get assistant' from the playstore, enable google assistant then open up chop assistant and you'll have the ok google trigger word working. As for the other issues the users have brought up I'm still working on because I can't reproduce the problem so I'm just working blindly.. Hopefully this build will have working battery stats for everyone but again, I'm not 100% positive. I'll update the OP with the new build as soon as it's done uploading to afh. Happy flashing! Oh and of course do a backup before flashing just to be sure nothing goes wrong, initial boot does take some time the first shot around but is quick after, so don't think you've got a bootloop if it takes a bit longer. If it does bootloop on you (which I doubt will happen) I ask that you pull a logcat for me so I can see what the issue is. Thanks all

[EDIT] Just got the OK to use get assistant in the ROM, so next build you will have the option of using a fully functional Google assistant, or using Google now on tap
[X Style (Pure) Android Development] tech_infinity:
I have never installed this rom, so do I have to flash the previous two builds and then dirty flash the latest build?
[X Style (Pure) Android Development] Randy3011:
No, you don't

It is not necessary to flash previous builds. Just download the latest along with Gapps for ARM64 version for 7.1. Recommend either nano or micro for the Gapps. Then you can add whatever Google stuff you want rather than installing everything and going back and undoing. Flash in TWRP the RR build and Gapps in that order. Always back up existing first. Full wipe...advanced setting and choose everything but microSD which is where you copy RR and Gapps. First boot takes a few minutes (about 3-4).

Hope this helps. Good Luck.
[X Style (Pure) Android Development] bmoses:
Flashed the latest build last night and charged to full overnight. So far today battery stats are reporting correctly! Thanks!
[X Style (Pure) Android Development] unitz0mbie:
Thank you for the ROM working well here!!! Was wondering if we may see kcal support in the near future?
[X Style (Pure) Android Development] TalionDread:
In terms of substratum support the latest build is using legacy. Is that correct?
[X Style (Pure) Android Development] sixohtew:
Correct, it's faster and easier the only thing is you have to reboot to apply
[X Style (Pure) Android Development] jimlightner:
Is anybody else's video wonky?you tube works but nothing Else.. Just wondering it may just be me
[X Style (Pure) Android Development] sixohtew:
I just tested Netflix and Hulu and fxnow and all videos play perfectly on my end..