yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) Android Development] buggerritt:
Anyone have luck with themes? When i apply one, it ends up making the phone sluggish, causes extractions to fail, and makes file transfers between internal and external sd cards to move at a snail's pace. I've only tried the included hexolibre and sense black/blue. But both have reacted poorly.

Is three a way to enlarge the weather on the lockscreen? Maybe it's just mine that so small.

This is how I'm used to it being with Chronus.

Is this a possibility?

sent via Moto X Pure

over AT&T's crappy network
[X Style (Pure) Android Development] ban.codrut:
Are you saying they fixed it in an update?
[X Style (Pure) Android Development] flieswithhawks:
Is this because of a fix in this ROM build specifically, or in CM itself? I have been trying to figure out why on all the custom ROMs for this phone these audio bugs persist for me. I wonder if it is a hardware issue or just how the low-latency audio is coded in Marshmallow.

I am currently on RR latest weekly using A.R.I.S.E. audio mod and would switch to AICP if indeed the call quality (esp. speaker phone) is good. I've been having issues with VoLTE on Verizon as well. I would really like to be able to have simultaneous voice/data on the Pure. Can anyone help me with these problems?
[X Style (Pure) Android Development] ban.codrut:
Is the problem Hardware or Software ?

IMO is a bit of both. Motorola uses it's own proprietary noise-cancelling technology with 3 mics array, different from how Qlcms Fluence works. So that's why in any other custom rom, beside stock-based ones issues emerges with speakerphone especially.

In order to make up for it, again IMO, thy need to find the right configuration for the microphone array and the speaker of destination for speakerphone. In stock rom for example it doesn't use both speakers, but only the bottom one. A reason for this I can find is that one noise-cancelling microphone is on top of the device. Then software kicks in as the receiving microphone is near the bottom speaker, and it makes sure that echo doesn't happen I guess, while allowing your voice to go through by cancelling the sound of what DSP process and takes out through the speaker being the same as the one entering the microphone.
[X Style (Pure) Android Development] mrdunlop:
Someone discovered a change in the speakerphone code with our phone that reduced/eliminated the echo, reported it to hashbang and he implemented it into the rom update. It is greatly improved tho one reported still having a slight issue, but I can report that I am now using the speaker phone and dont get the *****ing about it!
[X Style (Pure) Android Development] timeline62x:
Can you elaborate what you mean by "*****ing"? I don't see how any of the replies you quoted can be considered rude or annoying. It seems like people are discussing a bug with the ROM and simply want to know whether it has been fixed or not.
[X Style (Pure) Android Development] flieswithhawks:
I'm the one who "discovered" a temp solution by changing build.prop and another member reported it from the RR thread here. I think what the "*****ing" being referred to is by the other party not being able to hear you in-call because of echo etc., not discussion in this thread.

Anyone able to share their experience with Verizon using this ROM? Specifically VoLTE?

---------- Post added at 06:51 PM ---------- Previous post was at 06:41 PM ----------

Here man, check this out:

http://xdaforums.com/android/software/r-s-e-sound-systems-auditory-research-t3379709/page1233
[X Style (Pure) Android Development] JoeNeckbone:
I believe they mean *****ing from people they are on the phone with who can't hear them because of the speakerphone issue.
[X Style (Pure) Android Development] Andvark:
The 0823 nightly reverted the fix? :confused:

Revert "clark: disable fluence during voicecall"
[X Style (Pure) Android Development] mrdunlop:
Wow... Read my friend, and realize not everything is a personal attack... I am not talking about anyone in the forums, only those on the other end of my phone line who I put on speaker phone and then ***** about the echo. They dont ***** about the echo anymore.

---------- Post added at 02:27 PM ---------- Previous post was at 02:23 PM ----------

Interesting, I have not updated to the 8/23 nightly. Due to work being incredibly busy, I dont get any desk time this time of year so my updates tend to take place towards then end of the week when I get a little breathing room. So I cannot report on the latest nightly, 8/21 all is good with speaker phone. If you update report back.

This is the change that was made:
[X Style (Pure) Android Development] Andvark:
Actually the fix was posted here, which changed persist.audio.fluence.voicecall from true to false. What you quoted was a response to another member that began having other problems after the change. It was a suggestion to revert the change to see if it fixed his problem.

Edit: I have not installed the 8/23 nightly, but I have downloaded it and can confirm that the speakerphone echo fix has been reverted in build.prop. I don't know why it was reverted, but anyone installing this nightly will (presumably) have the speakerphone echo problem return.
[X Style (Pure) Android Development] dlabadie:
Just curious - what were the "other problems" experienced by the initial change?

Sent from my Moto X Pure XT1575
[X Style (Pure) Android Development] Andvark:
See here and the following posts.
[X Style (Pure) Android Development] HPAR:
someone else with the problem to save pics directly to external sd card?

I can´t save to external sd since yesterday.

I guess somebody forgoten this permisison to the camera since build 22/08 when they changed something at camera.
[X Style (Pure) Android Development] pizzlewizzle:
It was probably reverted in AICP because it was reverted in CM Official nightlies with a comment saying "we can fix the echo some other way" tho I am unsure if another method has been figured out yet... I am unsure about you, but the change made my phone pretty much unusable. If you have no adverse effects I'd just suggest doing the build prop edit after flashing the latest nightly if it fixes your problem
[X Style (Pure) Android Development] buggerritt:
Is there a setting to change the color of the status bar icons? I found settings for clock color and nav bar buttons but not signal, battery, etc. Am I looking for something that's not there?

sent via Moto X Pure

over AT&T's crappy network
[X Style (Pure) Android Development] tonyc0642:
Home button not working for me since updating to 8/23. Thought 8/24 would fix it but nah. Also been having bluetooth issues, my Anker Soundcore will connect, but can no longer remotely pause/play/skip, only control volume. Also devs seems to have arbitrarily decided that the LTE icon in the status bar should now be a 4G icon by default. It's easily changed in AICP extras status bar settings.
[X Style (Pure) Android Development] pizzlewizzle:
Did you dirty flash maybe? I'm on clean install of 8/23(didn't flash 8/24 or 25 BC there was barely anything changed) and haven't encountered any of those problems...only thing I noticed was ambient display is kinda wonky/not working how I remembered it working in the past so I just turned it off
[X Style (Pure) Android Development] welingtonhs:
i'm with problem slow in WiFi, take a few 5 to 10 seconds to load the pages of the Internet. when I was using the stock ROM not happened this ... I am using moto x style xt1572

Enviado de meu XT1572 usando Tapatalk
[X Style (Pure) Android Development] DietDoubleDew:
Any idea what is going on with my lock screen? Cant seem to figure it out. Im using the dark material // blackout theme from the Play store. Here is the screen shot:

Edit: I did a quick reboot and the lock screen display returned to normal size. But something is causing it to randomly get enormous and makes me reboot my phone. I'm lost.
[X Style (Pure) Android Development] gmlogan:
Aicp extras, lock screen, font size, just change it, the default is messed up that's all
[X Style (Pure) Android Development] AllenRong:
Some problem with the wifi connection, shows saved but cannot connect. Works after reboot

通过我的 XT1570 上的 Tapatalk发言
[X Style (Pure) Android Development] Xanderghul:
Is anyone else having issues with data after the latest nightlies?
[X Style (Pure) Android Development] buggerritt:
I'm not. In fact, signal has improved for me.

sent via Moto X Pure

over AT&T's crappy network
[X Style (Pure) Android Development] Xanderghul:
I was using data fine on Wednesday but today data just doesn't work. I reflashed 831 and it's still not working.

Restored to a different ROM, as I was using RR before this. Data works just fine with that.
[X Style (Pure) Android Development] ban.codrut:
Go in aicp extra and look for clock text size .. and set/reset it
[X Style (Pure) Android Development] buggerritt:
Did you check to make sure your apn was right?

sent via Moto X Pure

over AT&T's crappy network
[X Style (Pure) Android Development] Xanderghul:
Sure did. Both ROMs had the same APN settings and network settings.

I did everything I could think of. A full wipe fixed it. Hopefully it doesn't happen again.
[X Style (Pure) Android Development] Xanderghul:
Okay the issue is somewhere in Developer Options.

It just did it again. I turned Dev Options on and set the thing to Advanced Reboot like I always do to skip a step in booting to recovery to make a backup in TWRP (ironically, because when I booted back up after the recovery, data stopped working again).

I turned on the Aggressive Handle to Cellular and a Always Keep Cellular Active and rebooted again.

Miraculously, data is working again. I'm almost afraid to turn my Wifi back on for fear it won't switch back once I leave it again.
[X Style (Pure) Android Development] mrdunlop:
Issue cropped up with latest flash;

Now says no sim card. And cannot get Wifi to turn on.

Tried flashing back same issue, nandriod restore same issue, full wipe and flash of latest nightly same issue. Also phone reboots shortly after powering on. Any idea?

I did accidentally move the fsg folder with file manager, however, I think I moved it back. May be causing the issue, in which case not sure how to recover. Perhaps a factory image flash (havent done one on this phone before)? This is the first real issue I have had with this phone that I couldn't recover from. Help would be greatly appreciated, thank you guys very much

Edit: Did a little research, fsg folder has all the stuff required for you phone to reach cell, modem ect. looks like I am hosed. Flashing stick firmware via adb hopefully that resolves it. Its been a good minuet since I have used adb, this is going to be fun, they say you never forget how to ride a bicycle....

Edit 2: Got it working, even better than before, most likely due to the factory reset. Flashed back to the May MM factory build, than flashed the latest nightly and all is well. Most likely could have gotten away with just flashing the fsg image.
[X Style (Pure) Android Development] Xanderghul:
Yeah I just spent a bit trying to get both Wifi and Cellular data working.

Turned airplane mode on and off. Data got back up but Wifi refuses to work, even when I roll back to yesterday's nightly (0903).

Edit: not having the sim card issue though.

Edit 2: restarting the router fixed my Wifi issues, not sure what caused it to refuse to work, but glad it's going again.
[X Style (Pure) Android Development] mrdunlop:
Any comments on the latest nightly?

Do you guys run SELinux: Permissive or Enforcing?

Any Performance issues with one or the other?
[X Style (Pure) Android Development] ausaras:
Lowering volume

The volume at the lowest setting/step is still too loud for me. Dirty Unicorn's volume at the lowest step is quieter but DU 10.5 is not as smooth as AICP for me.

I searched and tried the mixer-path.xml hack but the variables are not present. I tried to modify other variables in mixer-path.xml but still does not work.

Could someone tell me how to lower the volume at the lowest step even further?

Thanks!
[X Style (Pure) Android Development] Andvark:
Have you tried increasing the number of volume steps to say, 60? The default number of steps (7, if I recall correctly) was too low for my taste; 60 allows you to reach lower volume levels.
[X Style (Pure) Android Development] ausaras:
Yup, the first thing I tried but no matter how many number of steps, the lowest step all sound the same. I think number of steps is simply that; just dividing a preset range by the number of steps.

I also tried using ARISE sound mod. Still no good.

Any other ideas?

Thanks!
[X Style (Pure) Android Development] flieswithhawks:
If you're using ARISE, go into Viper and at the bottom in your master gate (limiter) output gain/limit threshold cut the db levels.
[X Style (Pure) Android Development] ausaras:
Thanks for the idea. I tried it before. It works with music apps but not system notification volume.

I would like to hear my notifications but at the lowest volume step, it is still pretty loud and my colleague beside me often glance at her phone out of instinct when my notification sound goes off. I would like it to be quieter so that only I will hear it.
[X Style (Pure) Android Development] *.jpg:
Hitting "Thanks" for being uncommonly considerate. I wish my co-workers would figure out how to turn their damn ringers off in the office.
[X Style (Pure) Android Development] buggerritt:
I've the same problem. No matter how low i set it, the notification sounds are blaring. I switched the notification sound to selenium. It seems to be the quietest. All the others actually make my ear crackle at the lowest setting.

sent via Moto X Pure

over AT&T's crappy network
[X Style (Pure) Android Development] ausaras:
I thought about changing ringtones but I use specific ringtones for specific accounts and apps for 5, 6 years so I really don't want to change ringtones.

I know DU and AICP have different bases but there has to be some way to lower the volume. DU's lowest volume step loudness is just perfect. I tried to stick with DU but it is laggy compared to AICP so switched back.

I am up for some hack-ish way to lower the volume.

---------- Post added at 11:38 PM ---------- Previous post was at 11:36 PM ----------

Hahaha thank you for the "Thanks". There really needs to be a written etiquette on mobile phones in the office. :D
[X Style (Pure) Android Development] Andvark:
You could always lower the volume of the ringtones you use with an audio editor (Android or PC based). ;)
[X Style (Pure) Android Development] buggerritt:
Well, i just turned off V4A and Dolby Atmos and the problem is gone. So, it's from using those. If there is a way to not have notifications effected by it, that would be great. But, it's not an AICP thing. It's definitely the audio mod.

sent via Moto X Pure

over AT&T's crappy network
[X Style (Pure) Android Development] ausaras:
I do not have ARISE or any sound mod installed.

I only flashed ARISE to see if I could lower the notification volume but lowering the gain only affected music apps, not system volume itself. So, I nandroid back to before ARISE was installed.
[X Style (Pure) Android Development] flieswithhawks:
I think that's funny that you experienced lag on DU which is AOSP based whereas this ROM is CM based. In what way did you experience it? I've been running it almost a month now and think it's smoother/faster than both AICP and RR.
[X Style (Pure) Android Development] iamshobhit:
100% true. DU is the the smoothest Rom i have flashed on Moto x. Can you please tell me which weekly you are running??? I am running official build which is a battery hog. Loosing 15% overnight. Any recommendations???
[X Style (Pure) Android Development] Trafalgar Square:
Wait. You're coming into an AICP chat to tell us that DU is the smoothest ROM.
[X Style (Pure) Android Development] iamshobhit:
Yeah because someone was saying that he experienced lag in DU as compared to AICP. And i have recently installed DU after 6 months of AICP.
[X Style (Pure) Android Development] ausaras:
I ran 10.5 latest weekly for two weeks. When scrolling, the list animation is choppy. I changed LCD density to 480, by the way. I tried 10.4 a while back and it was smooth but 10.4 lacked the wave gesture so I ran AICP, instead.

Tried DU 10.5 out of boredom and was pleasantly surprised to see they finally included the moto wave gesture. But as I mentioned, the scrolling is rather choppy. I found a partial solution by turning on "Disable HW overlays" in the developer option. I was hoping that subsequent weekly would fix the choppy scrolling but then I found out that DU is not going to work on Marshmallow, anymore, so any hope of fixing the choppiness is gone. Also, noticed that DU 10.5 drains battery faster but this is a subjective view...I didn't do any tests.

Anyhow, I am back on AICP, again, after a two week break.

---------- Post added at 07:47 PM ---------- Previous post was at 07:45 PM ----------

I took your advice and lowered the ringtone volume gain using a audio software (Audacity, to be specific). It works but I would have preferred to mod the system, instead, so I don't have to keep two versions of ringtones.

Thank you!

---------- Post added at 07:51 PM ---------- Previous post was at 07:47 PM ----------

It was not my intention to compare one ROM to another. Just saying DU has the perfect volume range but couldn't stay with it because the scrolling is choppy and there is no hope of it being fix because DU team is stopping work on Marshmallow.

Not here to start a ROM war. Both are good, each has their own quirks. And I am a flash-holic.
[X Style (Pure) Android Development] flieswithhawks:
I was actually going to suggest this painstaking method as well. Manually cutting the volume in an editor.:)

We know you aren't a traitor to one ROM or the other. I think all of us have slightly different uses/preferences for our devices as well as the desire to hack them, which is why we are here on XDA anyways right!?

It's OK. The first step is admitting you have a problem... Haha;)
[X Style (Pure) Android Development] tonyc0642:
Tried to flash to stock yesterday, and it was a complete mess. So I decided to go back to AICP. Full wipe, installed TWRP, installed 09/09 nightly, installed 09/09 pico gapps. Reboots within 30 seconds of booting up, sometimes immediately, sometimes not. Managed to make it all the way through the setup, but it sill reboots. I'm at a complete loss here.
[X Style (Pure) Android Development] Xanderghul:
Have you tried a different Gapps, like OpenGapps?

The official site links straight to OpenGapps only, so you might have to go with that.
[X Style (Pure) Android Development] tonyc0642:
Pico is OpenGapps. It's the smallest package. Got it straight from their site.
[X Style (Pure) Android Development] Xanderghul:
Ah gotcha.

Coincidentally, I updated to 9/09 and the latest OpenGapps as well and had no issues.

Until three hours later. Then unending boot loops happened. While just sitting there charging.

So yeah I rolled back using a restore I made. I just installed the latest Gapps without the 9/09 nightly. So far so good.
[X Style (Pure) Android Development] flieswithhawks:
Have you tried Nano? I think I remember reading somewhere that might help with that sort of thing.
[X Style (Pure) Android Development] tech_infinity:
10/09 bulid seems to have no reboot issues, been using it for more than 12 hours. Everything looks great.
[X Style (Pure) Android Development] kunal kayal:
Sir can you please help me out to ROOT my MOTO X STYLE (XT1572) ( INDIAN VARIANT ) running MARSHMALLOW which is fully BOOTLOADER UNLOCKED ..i have tried every single version of SU ....when i tried to install it in my phone gets Brick(it stuck on big M logo while booting) each n every time i do this process .sir do you have a strong solution to this problem please help me out﻿...
[X Style (Pure) Android Development] Jimi Mack:
You have made 6 posts in 6 threads, a Rom thread is not where you would go and ask for this help. Check the Q&A Help Thread.
[X Style (Pure) Android Development] Xanderghul:
Just a heads up, the latest nightly will send you into boot loops unless you update Gapps.
[X Style (Pure) Android Development] buggerritt:
This did not happen to me. I've been dirty flashing every update for a month with no issues. Today was no exception.

sent via Moto X Pure

over AT&T's crappy network
[X Style (Pure) Android Development] Xanderghul:
Weird. It seems to happen to me every other nightly or so.

I updated, it finished booting, count to three and it's back at the AICP swirl and didnt go any further. Update Gapps to 9/12 and it's all better. It's done that with like three nightlies so far.

Edit: Which version of TWRP are you using?
[X Style (Pure) Android Development] buggerritt:
3.0.2

I would assume that your gapps should be updating via play store when updates are available.

sent via Moto X Pure

over AT&T's crappy network
[X Style (Pure) Android Development] Xanderghul:
Including OpenGapps? I'm not sure, to be honest.

I just know that it worked.

I'm more annoyed about this damned wifi issue that causes my connection to drop suddenly. I've killed almost a gig of my cell data because it would drop while watching stuff on YouTube on full screen at home.
[X Style (Pure) Android Development] buggerritt:
Yeah. Open gapps is just Google apps. Google updates everything through play store.

I don't have the wifi problem either.

sent via Moto X Pure

over AT&T's crappy network
[X Style (Pure) Android Development] Xanderghul:
Damn.

Have you had Bluetooth connected while being on wifi and cellular data?

It seems most likely to happen while all three are active.
[X Style (Pure) Android Development] buggerritt:
Yeah. No issues.

sent via Moto X Pure

over AT&T's crappy network
[X Style (Pure) Android Development] Xanderghul:
Dangit. I guess I'm just bad at phone.
[X Style (Pure) Android Development] buggerritt:
Are you flashing anything else with it? I'm flashing ARISE with it every time. Maybe you need to update the modem and BT? Or, maybe it's your router and BT device?

sent via Moto X Pure

over AT&T's crappy network
[X Style (Pure) Android Development] Xanderghul:
Nope just OpenGapps mini and the nightly.

I saw that "flash m modem" on the first page. Do you flash anything like that?
[X Style (Pure) Android Development] mrdunlop:
Clean or dirty flash?

If you are doing clean flash you may want to consider re flashing to factory, then flashing twrp again and starting fresh with the latest nightly. I was having all sorts of issues even with clean flashes, flashed back to stock and started from there, all is now good.

Of course I would do a backup of you launcher, widgets, titanuim and nandroid as a just in case.

Refer to this thread for flashing stock OTAs

Edit:

You can skip a lot of them, flash boot and recovery img, system may be optional (I flashed it anyways but couldnt get phone to boot) flash modem, erase modemst(s) flash fsg and bt. Then flash twrp, boot into recovery and flash latest nightly, gapps, xposed ect and you should be good to go. Restore goodies once booted. Thats what I did, phone is running smoother than it has in some time now.
[X Style (Pure) Android Development] Xanderghul:
Will look into this. I immediately installed TWRP when I received the phone, for fear of an updated stock firmware would give me unlocking issues. I inherited a Maxx that I updated beyond the ability to unlock and didn't want that happening again.

At least, I think I did. I just booted into my stock backup and there is a tiny update that might be the updated modem. Of course now I've gotta figure out how to install it because (I'm generally not used to going back to stock) evidently TWRP and stock don't play well together.