yashsingh1/xdaforums huggingface dataset:
[X 2014 Original Android Development] invisiblek:
This broke it:

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

But it also fixed this:

https://jira.cyanogenmod.org/browse/CYAN-7675

Its on my list to fix...

FWIW: you can edit your build.prop and reboot (set that prop back to 'none') and it should be back to how it was.
[X 2014 Original Android Development] vok01:
First, sorry about my last reply and my grammatical mistakes. And now the important topic, this is my first time flashing a Moto X2, and I use CM13 nightly 24/05, stock gapps and twrp. I made a clean installation yesterday and, in the night, when my battery reached the 15%, battery saver turned ON, I deactivate this mode and I change the "Battery Mode" from Battery Saver to Balanced and then I change the % to 5, after that my screen started to flash and my touchscreen was unusable for 2 min, I had to power off the phone to get it working again. And with your bug, the speaker is working fine here.
[X 2014 Original Android Development] joseph_1802:
May 25 Nightly: I used the speakerphone with whatsapp call without problems, excepting for a couple of seconds after connecting. Talking about Whatsapp, I'm facing some sync issues. It looks like when the device gets into deep sleep, I don't receive any messages until I access Whatsapp myself. Using Balanced as Battery Profile, and whitelisted it for Doze. Could it be the Per-App battery settin?
[X 2014 Original Android Development] joseph_1802:
I correct myself. Speakerphone seems to work ok with Whatsapp calls, but not with regular phone calls. Also, I'm still seeing the Whatsapp sync issue.
[X 2014 Original Android Development] salaesp:
I'm having double battery life on stock (so it's not the battery) using exactly the same configuration and apps, but is seems strange because nobody is having this battery life. What gapps are you installing?
[X 2014 Original Android Development] testkeys:
Cool! Done and fixed! - I will check with the people I call to see how bad is the sound on their side when I'm not using the speakerphone and see what is the best option to use while waiting for your fix.

In any case, thank you very much for your reply and everything you do for our branch.

[and sorry to read on Jira that you don't use your MotoX much anymore]

Cheers.

No problem about the spelling; I trust Swiftkey a little too much myself and often post without proof-reading. I was not trying to correct you there (other than with the the capital "R"), but was rather describing what I did to try to reproduce your issue. And btw, it's "battery saver" and "power save" mode (probably why you missed the "r" in the previous post).

In regards to your problem, I'm afraid that you might have to wait for it to happen again and then (learn how to - if you don't already know) grab a logcat...

<Edit: where you using a custom theme by any chance when that happened? />

And also btw: it's not a problem with the sound coming out of your phone speaker itself; it's a problem with the sound heard by the person you're calling when you are using the speakerphone mode.

First of all: there was never a May 25th nightly built from the official CM site; so unless you've built it yourself, hard to say which one you're really on...

;)

I don't use Whatsapp, but considering a similar issue I've observed before with an app not switching airplane mode OFF while in the Doze mode, I'd say that even 'white listing' (or rather using the "do not optimize" in battery setting) will not help and most probably Whatsapp app itself will have to be adapted for Doze. I don't think that "Per-App" settings will change anything either -unfortunately- and I would just leave it turned ON.
[X 2014 Original Android Development] Felipolas:
Last time I check it up, any Custom Rom is unable to access the moto voice feature in Moto X's devices. I'm willing to taste a custom rom in xt1097, but I use that feature constantly (like 15x per day), and I'd like if the moto voice and others gestures are available in CM and other Custons roms?
[X 2014 Original Android Development] joseph_1802:
Interesting... I've been using CyanDelta to update CM, and it said there was a May 25th build. Now running May 26th... So CyanDelta isn't a recommended way to update this rom? Is clean flashing the only way to update without issues? I just don't want to go through the hazzle of restoring all my apps data every time I want to update CM...

By the way, what are your thoughts regarding the speakerphone fix?
[X 2014 Original Android Development] Gus Ghanem:
I did see a May 25 build for a few minutes, and then it was pulled. I was never able to download it though. It's fine to just update CM as long as you don't experience any "serious" issues or crashes. I've been updating every nightly with no problems.
[X 2014 Original Android Development] [] AL []:
[Q]: regarding that item (pic) from May 26th nightly:

Anybody got this to work?

I still can only see Image selection...

EDIT: thanks to Gus Ghanem on next post, I've realized that I've downloaded the wrong nightly...

dang!
[X 2014 Original Android Development] Gus Ghanem:
May 27 Nightly: MMS 4 types of attachments, seem to work, first type a live camera for taking stills and video (video camera icon bottom left side), second type showed my gallery pics, third type showed .mp3 and .m4a but not .aac, fourth type press and hold to record an audio message. I didn't actually send an MMS, but all attacment types seem to be available (I haven't tried video files, and of course there's a size limit to attacments).

Edit: Check the Messaging app's permissions under Settings > Apps > Messaging > Permissions
[X 2014 Original Android Development] sascha6982:
Hello. I don't want flash every night or week. So can someone tell me what is the most stable or functionality nightly at time?
[X 2014 Original Android Development] testkeys:
OK, my bad about the May 25th build (although technically, I'm right about no official build that day). I've heard about delta updates before, but never looked into CyanDelta; so, good to know - thanks.

Speakerphone: well I'm not sure which fix you refer to, but if you do as Dan (invisiblek) said and change the fluence build.prop property back to "none" (and save + reboot), things should be as they were last month. That means that the person you're talking to while using the speakerphone should hear you properly. How exactly does this affect the sound quality for you and the other person when you're not using the speakerphone, that I don't really know yet as it's a little hard to get someone compare the two options since the (worsening) effect is definitely less problematic than how it is for speakerphone with fluence ON.

I guess an easier answer is: if you use the speakerphone sometimes, then you should do that revert; if you don't use it, then leave things unchanged since the voice quality (while no speakerphone is in use) should be slightly better.
[X 2014 Original Android Development] joseph_1802:
I've been using CyanDelta without issues, it usually notifies me when a new nightly has been released and creates a backup zip in case something goes wrong. Regarding the speakerphone, I guess I'll have to make the change in buil.prop, since I actually use it for some calls.

Couple of more questions... Do any of you use LiveDisplay? I was using it until I read a couple of articles saying that those kind of screen filters affected AMOLED screens. Also, is there any way of manually adjust the LED for Notifications (make it blink instead of staying on)?
[X 2014 Original Android Development] testkeys:
I sometimes use LD, but not that much. It would be interesting to see these articles you've referred to as I find it a little hard to believe that Motorola (among others) have chosen to use (and do marketing around) this if it was true...

As for the blinking of the notification light, I wouldn't know how to do it, but I do remember reading something on some LG G2 forum about using Tasker to do something very similar to this. So do a few searches and you might find a way. Personally though, I wouldn't bother buying (because that is a paid app) and installing such an app and have extra services running (and as little it could be, more battery consumption) just for that purpose... And btw, I'm not convinced that having it blinking (even discounting Tasker's part of it) would actually take less battery at all (not that it's what you've implied, but just as an extra comment - and for what it's worth...).

Cheers.
[X 2014 Original Android Development] joseph_1802:
I've found some articles and read in other forums about burnt-in AMOLED screens. Some people related that effect to the use of screen filters that actually don't turn off the leds, as it's intended in AMOLED screens to save power. Anyways, I agree with what you said about Motorola promoting AMOLED technology (as well as Samsung, just to mention another), and I just wanted to hear your experience with it as I sometimes find LiveDisplay interesting.
[X 2014 Original Android Development] sonsum:
I've read those too and it's kept me from using apps like Twilight. I started using LiveDisplay because it doesn't tint black pixels, just changes the colors of the whites, which maintains the advantage of an AMOLED screen.

I honestly couldn't find evidence aside from a few examples where people said not to use it. The CM implementation seems fine, where a lot of the non-root screen tinting apps out there might not do it correctly.

---------- Post added at 12:25 AM ---------- Previous post was at 12:23 AM ----------

For what it's worth, I've been using 5/6's nightly with no issues. I don't update unless I feel like there's a reason to (I used 1/26's nightly up until I finally flashed 5/6's).
[X 2014 Original Android Development] densets:
Facebook and messenger not working, but facebook lite does work. Disa works to relpace messenger but would be nice if it works eventually.
[X 2014 Original Android Development] Blakkheim:
Hey everybody

I just flashed the latest nightly but I can't change the behavior of holding the recents button, double tapping, etc. There is no option on the buttons menu, despite showing these options when I search settings.

So, does anyone know how can I change these settings or I can't at all?

Thanks in advance!
[X 2014 Original Android Development] zander21510:
Has anyone had any issues with sound? It seems like whenever the sound is routed somewhere different (I.e. plugging in headphones or engaging speakerphone during a call), strange things happen. Sometimes after a call, all notifications and rings play through the headset speaker, not the main speaker. Sometimes even stuff like audio from YouTube or an app only plays through the headset, or not at all, no matter what the volumes are set at. After a reboot, things fix for a while, but even if I do nothing eventually the sound gets messed up again.

Seems app agnostic and has been affecting the last couple months of nightlies (I update every week or two). Any ideas? I can try and upload a baseline logcat and then load one when the sound is misbehaving...dunno if that would help.
[X 2014 Original Android Development] joseph_1802:
I'm running May 28th nightly and so far I haven't experienced any sound issues. I've used the speakerphone in calls and YouTube, a bluetooth speaker, headphones... The only issue I faced happened when using the speakerphone during calls, but it looks it got fixed after changing fluencetype from fluence to none in build.prop.
[X 2014 Original Android Development] thousandecibels:
OK Google from any screen is not working.
[X 2014 Original Android Development] invisiblek:
Try using the current settings in the official nightlies, then making this change in your build.prop: https://github.com/CyanogenMod/andr...mmit/a8bad85717d9ae332dfd151bc34923c796c3545e
[X 2014 Original Android Development] joseph_1802:
What about fluencetype? Are you saying that it should be left as fluence instead of none?
[X 2014 Original Android Development] :
Just flashed cm-13.0-20160530 and everything is working fine so far. Any recommended kernels to partner with this release ?
[X 2014 Original Android Development] joseph_1802:
Anyone using WhatsApp experienced a reconnecting issue when switching to the speakerphone after the call is connected?
[X 2014 Original Android Development] testkeys:
Not sure why Dan's explanation is not clear enough for you, but here's what you need anyway:

"build.prop" file being located in the "/system" directory.
[X 2014 Original Android Development] joseph_1802:
I got that, but I was actually replying to invisiblek's post. His proposed solution is different from Dan's, so I wanted to know if modifying fluencetype would be necessary.
[X 2014 Original Android Development] testkeys:
Dan IS invisiblek.

And if you read his two answers and what he's quoted, it's all pretty obvious.

His first suggestion fixed the speakerphone, but reintroduces a bug with 'normal' calls that fluence fixes.

His second suggestion keeps fluence on for normal calls, but disables it for speakerphone calls: best if both worlds.

Sorry if I replied to a post not addressed to me, but I thought others might also benefit from a clarification.

Sent from

And btw, when someone takes the time to try to help you, hitting the 'thank' button never hurts...
[X 2014 Original Android Development] joseph_1802:
Thanks for clarifying this. When you mentioned Dan, I thought you were talking about someone else, as I only know him as invisiblek. I guess the changes he proposed weren't clear enough to me, but they're now. I'll apply them and see what happens.
[X 2014 Original Android Development] t0per666:
New to CM ROM for moto x 2nd gen pure build 06/03 no issues so far thanks. And crpalmer youre in zenfone 2 devs too i sold mine cos i think theres no way intel processor can develope more cos they dump it lol i bought new and this is it. sorry for the off topic and my english. Keep up the good work!
[X 2014 Original Android Development] testkeys:
06/04: how do we toggle the lock screen rotation that Dan (@invisiblek) implemented?

I'm missing anything or is it that it is just not live yet?

Thx
[X 2014 Original Android Development] Gus Ghanem:
Now that you mention it, I looked around the settings...

Settings > Display & lights > Rotation

It actually works.
[X 2014 Original Android Development] testkeys:
Ok, I've missed that sub-setting as I thought it'd be under a new entry of its own...

But great! thanks (and thanks to Dan also).
[X 2014 Original Android Development] Gus Ghanem:
I saw the feature in the changelog before the build was released, but I never looked into it (and forgot about it), as it's not a feature I would really use. But, yes, I first looked under the Lock Screen settings, then remembered the Rotation settings, figured it may be there.
[X 2014 Original Android Development] joseph_1802:
0601 nightly: Is there any way to enable/disable Expanded Desktop other than from Settings > Display & Lights > Expanded Desktop? Also, the per app settings for Expanded Desktop don't seem to be working. Even though I select "Hide Nothing" for a specific app, after enabling Expanded Desktop, both the Navigation and the Status bars automatically hide for that app.
[X 2014 Original Android Development] testkeys:
I've asked the same before here:

http://xdaforums.com/showthread.php?p=64718150

and I still believe that a QS tile or a Power Menu option for this would be very valuable. Mr Kondik might have some reasons for not implementing this... or it's just that no one ever got the time to port/implement it...

In regards to per-app settings, it's not how it works. The expanded desktop switch is a general one; that means you turn it ON and it is effective (one of its 3 options) for everything and you have to turn it OFF for all your individual apps settings to be in effect.
[X 2014 Original Android Development] joseph_1802:
Thanks, that really helped me to understand how it works. I had seen your post after searching for Expanded Desktop in the thread, but I thought that maybe there was something else that I was missing.
[X 2014 Original Android Development] zander21510:
Looks like victara got a TON of fixes in the 6/6 nightly according to the changelog, mostly to do with WiFi. Anybody notice any differences?
[X 2014 Original Android Development] Gabbro1010:
Moto x victara

I was stock.

* the cyano 13 requires the installation of a kernel?

My device is stuck on the message "Warning Bootloader unclocked"

I installed the TWRP 3.0 and works (beautiful)

I have the gapps and CM13 img into my device and the operations that I do are:

1) flash CM13 from .img (required 1 second installation)

2) fash gapps (required 5 second installation)

wipes ..

but I have not installed a Kernek.

help me

Thanks;)
[X 2014 Original Android Development] Gus Ghanem:
No, you don't need to flash a kernel, and it's impossible CM would take just one second to flash.

In bootloader mode:

fastboot flash recovery twrp-3.0.2-1-victara.img

Boot into recovery immediately.

Copy cm-13.0-20160608-NIGHTLY-victara.zip and Gapps.zip to the phone, tap Install, flash CM first, then tap Install again and flash Gapps.
[X 2014 Original Android Development] Gabbro1010:
I followed the same procedure and the result is always that. (See photo)
[X 2014 Original Android Development] Gus Ghanem:
Which exact version of TWRP did you flash? Earlier versions of TWRP 3.0 would sometimes corrupt the data partition, in that case, you would have to boot into recovery, tap Wipe, then Format Data, reboot into recovery, Advanced Wipe all partitions and start again.

If that doesn't work, you may have to reflash the latest stock firmware, and start over.

Also, in bootloader mode:

fastboot getvar all

And save all the info in a notepad file.
[X 2014 Original Android Development] mikeoswego:
Not sure where you got a .img file to flash but what you want is to download and install one of the nightly zip packages from here: https://www.cmxlog.com/13/victara/ The newest zip package as I write this is cm-13.0-20160608-NIGHTLY-victara.zip and you can click on that filename in the linked paged to download it.

Then use TWRP to install (flash) the nightly zip and gapps zip and you should be up and running.

---------- Post added at 12:03 PM ---------- Previous post was at 11:55 AM ----------

To add to my previous reply, now that your phone won't boot, there is no easy way to get the files you need to install/flash onto the phone. You will need to get a USB OTG drive (a cheap small one will do) and put the nightly zip on that, plug it into the phone and then you can install/flash it from there and then flash the gapps from wherever you have them stored or from the OTG drive if you put a copy there. When you plug in the OTG drive, you may/will have to use the TWRP mount menu option to access it.

---------- Post added at 12:09 PM ---------- Previous post was at 12:03 PM ----------

One last comment... It looks like you have good enough files but are you using the install image option? You don't want that, just install the zip.
[X 2014 Original Android Development] pedp4000:
Anyone familiar with the mixer_paths.xml file?

my speaker MIC is no good (also used for video camera mode)

I've made changes to the mixer_paths to make it work, but I was wondering if anyone has detailed info on which mics are represented by what.

Moto x 2014 is supposed to have 4 mics: I'm just wondering if anyone knows which mic belongs to what path

I know ADC3 = handset mic (i'm guessing front bottom)

ADC2 = the headphone jack mic line (not included as one of the mics)

ADC4 = speaker mic (mine is blown)

ADC1 = location?

ADC5 = location?

Thanks
[X 2014 Original Android Development] joemossjr:
OR you could adb side load depending on the version he's on and flash it like that. Or if his phone mounts in adb then just copy over the files like that
[X 2014 Original Android Development] flitzjoy:
Hi guys, I come back to cm from stock last Sunday and can't do or receive calls. The android interface reboots when I click to call someone or receive a call. I was unable to determine the cause and was hoping to be a nightly bug, as no one mentioned and after 3 flashes the problem remains I think is something specific to my scenario. There's a log I can dig for answer?
[X 2014 Original Android Development] cogie:
Change the default phone app to the phone app installed on your phone.

Settings

Apps

Hit the gear

Default Apps

Phone App

Phone
[X 2014 Original Android Development] flitzjoy:
It worked like a charm, thank you. Its sound like a bug / know issue to be advised. For a new user it's frustrating and could lead to removing cm. Opening the default app prompt or select a default one should be the right path.

Thank you again.
[X 2014 Original Android Development] flitzjoy:
OK guys, a new problem, maybe someone know a solution. Waze map layer didnt appear to me. Tryed changing themes without success. Anyone are using Waze normally?
[X 2014 Original Android Development] A2Trip:
I honestly wanna know what's up with MMS ??? I cannot get it to work for life of me...no APN options either? I'm confused
[X 2014 Original Android Development] testkeys:
Have you verified that CM's Messaging is the default SMS/MMS app? A bit like it was mentioned below:

Personally, I've had 2 different issues with it (Messaging's MMS) lately:

1- Even though I had the advanced option set to group multi-recipients MMS messages, replies seemed to still come on separate conversation threads;

2- I sent someone a picture 4 times (trying different things like first turning cell data ON or leaving it off) and each time, that person would get the "Download MMS" notification but could never actually download it - which is pretty annoying. BUT, when I cc'd myself, I could download the message/picture properly... So I don't know at which end the problem really is but that used to work just fine with that recipient before and nothing rom-wise was changed on that phone I'm sure...

And lastly, I also noticed during those recent MMS attempts that I no longer need to turn cell data on to send them; it would do it automatically for me (although the data switch seemed to remain OFF, I could still see a little "E" for 2G-Edge service on the status bar.

And one more just for the sake of cleaning the bag of recent issues;

- I've been experiencing a little more frequently during the last week or so [still running on the June 11th nightly] my rather long-standing issue where for no apparent reason (or no trigger yet found), the notification drawer/shade/QT tiles would suddenly start being displayed screen-wide while in landscape mode [and only a reboot would fix that].

And one more although this could be a 3rd party app issue:

While playing Walking War Robots game [highly recommended btw] all the game's sound would just stop after I'd get a notification. So I'd hear the cricket notification sound, then boom, no more sound in that app [but rest of system is fine - hence why if tend to point the finger towards the game itself].
[X 2014 Original Android Development] AntsInMyPants:
Same issue here. Is this another 32gb variant issue all over again? :eek:

By default the phone is using Global and will not let me switch to 4G (I know switching is a known issue).
[X 2014 Original Android Development] FabianFR:
Chromecast working?

Is the Chromecast-connection or casting in general working for you?

Thanks in advance :)
[X 2014 Original Android Development] Lebo-Wog:
Sorry i don't use it, and i don't have a Chromecast.

Had anyone figured out how to turn off the quick settings showing up when you swipe from the right?

I found a bug, if you're calling someone and they hang up on you, the phone displays "invalid number" instead of "number busy".