yashsingh1/xdaforums huggingface dataset:
[X 2014 Original Android Development] G4 Man2:
Reason for the loop is posted on the previous page. Nightlies are fine.
[X 2014 Original Android Development] WiCiO_MeDi:
hi, i've recently switched my moto G to X and straight out of box flashed this CM12 ;)

since few days have to problems to report:

- WakeOnWave doesn't always work. i see those red dots at the bottom (IR sensors) when i wave my hand but the screen remains off and silencing the call doesn't work either. It happens about 20-30% of the time,

- now a weird/freaking one.. i had an unanswered call, but I dialed another person. to my surprise phone showed that i'm calling the unanswered person! and I couldn't end the call 'cause the red button was unresponsive. to my surprise the person who I was calling was the one I dialed. But even during the call the screen was showing someone else (the unanswered person). Bizarre experience, i must say ;)

is there a way to disable hashtag (root) in the statusbar? you could do that on cm12 on moto g.

would be swell if the notification on lockscreen could also show battery status.

anyway, thanks for your support on cm for moto x,

cheers!

ps.

i'm on 20151009-nightly
[X 2014 Original Android Development] G4 Man2:
In regards to the wakeonwave, the ir sensors only flash when user-aware display is enabled (which is why I have it disabled). But the wakeonwave has been pretty hit or miss for me, some builds it works, some it doesn't, you may try a different one if it's a feature you're dependent on.

For the root symbol, the only solution I could find is an xposed module. I'm sure a number of them could do it but it was so long ago I don't remember which one I used.

Your other questions I don't have answers to.
[X 2014 Original Android Development] mcardielo:
very good news http://www.cmxlog.com/13/
[X 2014 Original Android Development] noemi.abril:
interesting... ;) and no official soak test available at date...
[X 2014 Original Android Development] :
Locale and Language Resources

Could the CM Devs. please default to "United States" language resources for those who setup their devices for "Canada". Selecting "Canada" at first setup still defaults to "Australia" language resources and settings. Thank You.
[X 2014 Original Android Development] kokotron:
I think I finally verified that a specific wifi issue I have is because of the rom and not because of the phone model. Explaining:

I have a Nikon camera (aw120) which can create an access point, so that you can download photos from it and remotely control it from your phone, using a specific application. This functionality works perfectly in every phone and tablet I've tried, one of them (an lg g tab 8.3) on cm12.1 as well. But it doesn't work on my MotoX: It's always stuck at "Obtaining IP address", and even if I manually enter IPs, the app won't see the camera. I tried with a different MotoX, unrooted with stock rom and it worked fine. So I think the issue lies in the rom. I would be glad if someone could tell me how to better troubleshoot this. I attach the working stock phone's info screen. WARNING: Some greek text inside!
[X 2014 Original Android Development] xavi23:
The same thing happens when I try to connect my GoPro 3. I thought it was me doing something wrong. Not cool.
[X 2014 Original Android Development] :
Wi-Fi region code

I have no clue, but have you tried changing the "Wi-Fi region code" under Settings, Wi-Fi, Advanced?
[X 2014 Original Android Development] aleksei87:
Now that I think about it, last time I tried I couldn't complete the initial configuration of my Chromecast after a reset, which also uses a connect to the device's own WiFi network. I ended up using a friend's iPhone. Maybe it is all related...
[X 2014 Original Android Development] xavi23:
Thanks Gus!

I've tried changing the region code, but my country is not listed. Tried with other countries and coudn't connect the camera.:(
[X 2014 Original Android Development] felipevsw:
I was using original pure edition firmware on my XT1097 for a while and yesterday I flashed CM again (latest snapshot) and I have no idea why or how but I can install all Motorola apps from the Play store, that is Motorola Camera, Gallery, Connect, Migrate, specially the firmwares Motorola Sensor and Motorola Modality.

Just wondering if it makes any difference in performance and/or stability... But it's nice to have Motorola Camera on CM :)
[X 2014 Original Android Development] xavi23:
Hi Felipe, does the Motorola camera video record works on your Moto X? I can take pics, but not recoed videos.

Regards!
[X 2014 Original Android Development] Tinchoska:
Guys are you using xposed? Does it works?

Enviado desde mi SM-T700 mediante Tapatalk
[X 2014 Original Android Development] felipevsw:
Yes, I can make videos in HD and 4K, only slowmo doesn't work as it says the mic is being used by another app (even after I restarted the phone)
[X 2014 Original Android Development] kokotron:
Indeed it seems it doesn't make a difference. :/ I've tried this in the past.
[X 2014 Original Android Development] flitzjoy:
I´ve been using just to the purpose to improve my battery life, I only use the modules greenify, amplify and boot manager. I cant speak about other modules and side effects. With these is all good, after we got Doze in 6.0 I probably will stop using Xposed.
[X 2014 Original Android Development] mikeoswego:
[MENTION=3857343]crpalmer[/MENTION] I'm having some trouble mounting /system r/w from init.d script. Is that intentional or something that could be changed? I also notice that by default, adb shell doesn't have write access to /system, but there a remount r/w is successful, (but not in the init.d script.)
[X 2014 Original Android Development] Tinchoska:
Thanks my friend,mi want it for that too...

Enviado desde mi SM-T700 mediante Tapatalk
[X 2014 Original Android Development] adm1jtg:
U need to add powernap to that list but yes is great for battery savings
[X 2014 Original Android Development] RunnersFoot:
Video works on mine using the moto camera.
[X 2014 Original Android Development] raptir:
Has anyone seen semi-freezes lately? I'm running into occasional cases where I will lose the notification bar and will be unable to manipulate the screen. I'm able to use the navigation buttons but nothing else works. I've seen it a couple times when using maps or on a call and I cannot move through the directions/hangup on a call. I can hit home to get back to the launcher but I can't do anything from there. If I turn the screen off for a minute it comes back.
[X 2014 Original Android Development] Tinchoska:
Guys, question, have you compare stock moto camera and stock cm camera?

Enviado desde mi SM-T700 mediante Tapatalk

---------- Post added at 06:18 PM ---------- Previous post was at 05:32 PM ----------

Another thing, I cant get my phone's clock saty on time, it always goes to -6 timezone..... any idea?

Enviado desde mi SM-T700 mediante Tapatalk
[X 2014 Original Android Development] xavi23:
I have the same issue but only when I reboot the phone with airplane mode on, after I connect it to the network the time goes back to normal. Always with automatic time zone and date enabled.

Regards!
[X 2014 Original Android Development] Tinchoska:
Yeap, every time it gets connection, wifi or signal, itgoes to the correct time set, but if i dont unlock sim card it stay on -6 time location.... by the way, is it me or battery is going out faster? And about camera quality its worst than few nightlies ornot?

Enviado desde mi SM-T700 mediante Tapatalk
[X 2014 Original Android Development] xavi23:
I can't really tell you about the camera quality, I use Manual Camera to take pics, and Cinema FV 5 to record videos.

The time set works pretty fine for me, except for what I wrote in the previous post.

Regards!

edit: battery life is great in my Moto X
[X 2014 Original Android Development] raptir:
I think the first one is a known issue.

I've noticed slightly worse standby time on the latest nightlies.
[X 2014 Original Android Development] kraatus90:
is it possible to merge this on cm sources ? it will fix slowmo recording issue.

these are the additional lines needed in media_profiles.xml for slowmo ( from motox2)

[COLOR="Red"]<!ATTLIST VideoEncoderCap maxHFRFrameWidth CDATA #REQUIRED>
<!ATTLIST VideoEncoderCap maxHFRFrameHeight CDATA #REQUIRED>
<!ATTLIST VideoEncoderCap maxHFRMode CDATA #REQUIRED>[/COLOR]

<VideoEncoderCap name="h264" enabled="true"
minBitRate="64000" maxBitRate="65000000"
minFrameWidth="176" maxFrameWidth="3840"
minFrameHeight="144" maxFrameHeight="2160"
minFrameRate="15" maxFrameRate="120"
[COLOR="Red"] maxHFRFrameWidth="1920" maxHFRFrameHeight="1080"
maxHFRMode="120" />
[/COLOR]
<VideoEncoderCap name="h263" enabled="true"
minBitRate="64000" maxBitRate="2000000"
minFrameWidth="176" maxFrameWidth="720"
minFrameHeight="144" maxFrameHeight="480"
minFrameRate="15" maxFrameRate="30"
[COLOR="red"]maxHFRFrameWidth="0" maxHFRFrameHeight="0"
maxHFRMode="0" />[/COLOR]

<VideoEncoderCap name="m4v" enabled="true"
minBitRate="64000" maxBitRate="65000000"
minFrameWidth="176" maxFrameWidth="1920"
minFrameHeight="144" maxFrameHeight="1080"
minFrameRate="15" maxFrameRate="60"
[COLOR="red"]maxHFRFrameWidth="1920" maxHFRFrameHeight="1080"
maxHFRMode="120" />[/COLOR]

slowmo will work with stock moto camera app, but there's a little problem. on stock firmware slowmo video is recorded at 120fps and runs at 15 fps (1/8 speed ) , and by this method it will record video at 120fps but it will run it at 30fps ( 1/4 speed ).
[X 2014 Original Android Development] likurik:
Try to uninstall the second camera app,let in your phone just moto camera app then the slomo work fine . Put this in the phone sistem http://xdaforums.com/moto-x-2014/themes-apps/moto-camera-slowmo-t3231606
[X 2014 Original Android Development] Amisuta:
Does anyone have xposed working on the latest nightlies?
[X 2014 Original Android Development] adm1jtg:
i am on nightly of the 26th i think it was and xposed works fine. Make sure your running 75
[X 2014 Original Android Development] Amisuta:
I thought the latest was 74

Nvm, different thread had only up to 74
[X 2014 Original Android Development] Tinchoska:
Guys two questions....

1. Wich nightly or snap you recommend? Battery related

2. Any of you know if installing Moto camera will gave the same quality than stock firmware?

Enviado desde mi XT1097 mediante Tapatalk
[X 2014 Original Android Development] kraatus90:
1. can't say , probably latest nightly. ( i update once a week , and battery is better than stock)

2. yes. and it's also installable from playstore.
[X 2014 Original Android Development] Tinchoska:
Downloading latest nightly then. Only installing camera right? No need to flash any mod?

Enviado desde mi XT1097 mediante Tapatalk
[X 2014 Original Android Development] kraatus90:
yep, no need to flash any mods.
[X 2014 Original Android Development] ezaias:
"OK Google" on any screen, not work, 5 different gapps package used in clean installation

Once configured, "confidence Face" stop work after unlocking my device, the same for any smart option lock

I using lasted build, and last open gapps pack

someone suffers from these same mistakes? (English sucks, google translator)
[X 2014 Original Android Development] raptir:
OK Google on any screen does not work for me either.

I haven't tried Face Unlock so I'm not sure about that but I've heard of issues with custom ROMs in general.
[X 2014 Original Android Development] ezaias:
probably be a mistake in victara, in cm12.1 mako , what do I reported here work perfectly :/
[X 2014 Original Android Development] raptir:
Keep in mind that the mako is a Nexus device. The Moto X is easier to unlock than most other phones, but it's still not quite a Nexus and so it's typically a little harder to squash some bugs.
[X 2014 Original Android Development] Tommebaas:
I saw that the Moto G 2014 got the cm13 alpha. A lot of stuff doesn't work but does anybody knows when we can expect it for our devices? I was hoping for this month :)

Sent from my Moto X
[X 2014 Original Android Development] ezaias:
probably cm13 is doing tests to victara as we see below

http://www.cmxlog.com/13/
[X 2014 Original Android Development] nanca:
seems that next build will bring us call recording.

"victara: enable call recording"

very handy n welcome feature.
[X 2014 Original Android Development] Amisuta:
Has anyone tried per-app battery profiles? How can I use them?
[X 2014 Original Android Development] xKroniK13x:
I was not able to get it to build after numerous attempts, but CM13 for Victara is definitely coming... https://plus.google.com/115397092534600785002/posts/cviDH2SJmVv
[X 2014 Original Android Development] flitzjoy:
another cm12.1 build failed. 4 days without a new nightly ;-(
[X 2014 Original Android Development] :
Damn, i wanted to install one last nightly to stay on until cm13 arrives
[X 2014 Original Android Development] craftyguy:
The reason it keeps failing seems fairly trivial.. just enable loadable module support in the kernel .config...
[X 2014 Original Android Development] Tommebaas:
My battery is pretty horrible since the latest nightly. It runs flat in about 6 hours. The only thing I got is a new Chromecast and I use it for a couple of minutes. How is it possible that my battery dies that quick? Everything else seems normal. I just update once a month to the latest nightly.

Sent from my Moto X
[X 2014 Original Android Development] craftyguy:
There are many factors that might result in your battery draining faster, and there are many articles written about it on Android. I suggest installing an app to view wakelocks (events that cause your device to wake up and stay awake) in order to get clues about which application on your phone is causing the battery to drain.
[X 2014 Original Android Development] Tommebaas:
I just installed wakelock detector and these are the results. Looks pretty bad...

Sent from my Moto X
[X 2014 Original Android Development] craftyguy:
Well, the worst offenders are not apps that come with CM... you should try uninstalling Vine, Fit, etc to see if your battery life improves..
[X 2014 Original Android Development] Tommebaas:
Just did that. Let's see what tomorrow brings.

Sent from my Moto X
[X 2014 Original Android Development] Lynse:
There are some cool changes on CM12.1 that we are not getting because the builds keeps failing.. CM13 is almost here so this is not a big deal, but i would love to update to a nightly with those changes, maybe tomorrow's build will be sucessful.
[X 2014 Original Android Development] invisiblek:
heh, sorry for the build failures guys, the fix is in for the next nightly (too much focus on M)
[X 2014 Original Android Development] thisguy23:
Been on this for a few weeks now. Anyone having camera reporting echo on speakerphone, even on the lowest volume? Looked here and online and haven't found a solution. Thoughts? Thanks for your help.
[X 2014 Original Android Development] flitzjoy:
thanks man!

any insider information about CM13 development? how is the overall progress?
[X 2014 Original Android Development] :
todays build failed again..
[X 2014 Original Android Development] craftyguy:
Weird, I was able to pull the update and build it without any issues... Jenkins has lost his mind!
[X 2014 Original Android Development] invisiblek:
looks like the build failed for something that wasn't my fault this time =P

error: /opt/jenkins/android/workspace/android/cm-12.1/out/target/product/victara/recovery.img too large (11384832 > [10813440 - 270336])
make: *** [/opt/jenkins/android/workspace/android/cm-12.1/out/target/product/victara/recovery.img] Error 1
make: *** Deleting file `/opt/jenkins/android/workspace/android/cm-12.1/out/target/product/victara/recovery.img'
make: *** Waiting for unfinished jobs...

i'll have a fix out for the next round....sorry :(

EDIT: well f....nothing i've changed should cause this....not sure what's going on, but i wonder if the build box is messed up or something. a couple other devices failed for random weird reasons too

[MENTION=1217620]flitzjoy[/MENTION] - cm-13.0 is coming along. victara is my slowest device since its my daily driver and i have to backup to test anything
[X 2014 Original Android Development] mikeoswego:
Must be a Jenkins problem, it built fine on my box.

overlay/packages/apps/Dialer/res/values/config.xml recently added in http://review.cyanogenmod.org/#/c/116602/ also needs the following to enable recording of both sides of the call at equal volume:

<integer name="call_recording_audio_source">4</integer>

This build has that fix and includes all the commits through "Add overlay config for phone switch (android_device_motorola_victara)": cm-12.1-20151105-UNOFFICIAL-victara.zip
[X 2014 Original Android Development] surrealjam:
Hi all

Just started to use this ROM a few days ago being a big CM user on previous devices. On nightly from 30th October.

Mostly it seems stable but today I got my phone out of my pocket and had "no service" showing. Tried airplane mode on/off trick, tried manually connecting to network - both failed. In the end I had to restart the device to get it to re-register.

Is this a common or known issue? I've come straight from the latest 5.1 official EU ROM so my radio should be the most recent.

Any info appreciated. I mostly need a stable system though I realise that a CM nightly always has its risks.

Thanks.
[X 2014 Original Android Development] AntsInMyPants:
Thanks for providing this. Flashed it with no issues and call recording works fine.
[X 2014 Original Android Development] nanca:
Another failure =/
[X 2014 Original Android Development] invisiblek:
Yea....really sorry about this everyone...it builds fine locally, but something with jenkins is making the recovery.img too big (we were already pretty close to the threshold )

My build: 9.7mb

Jenkins: 11.1mb

No idea why...the problem is, replicating it locally...since i can't it makes it tough to fix

The solution we came up with this morning was to compress the recovery ramdisk with lzma, rather than the default gzip, thereby saving valuable space in the recovery.img. When I built with this locally, my recovery.img was about 7.9mb, and incidentally so was this last jenkins failure.

"Why did jenkins fail then?" you may ask. Well, there's a process that uses a program called imgdiff to create a recovery_from_boot.p file. This is file is shipped in the rom so that if you wanted to update recovery (via the checkbox in development settings) it just has to patch your current boot.img with that file to create your new recovery (rather than shipping an entire recovery image). Unbeknownst to me, imgdiff can't create that file if we used anything other than the default gzip to create that recovery ramdisk. The new patch I just shipped will switch to using bsdiff rather than imgdiff to create this file. bsdiff has the capability of creating this recovery patch file while still using lzma to compress our recovery ramdisk.

PHEW!

Hopefully...finally...you guys can get a build again in the next round.

Again - sorry :(
[X 2014 Original Android Development] nanca:
Don't you worry buddy!

You must understand we are all addicted to this updating process. It's like a drug. :eek:

hahahahahaha

But we are not gonna die.

However let's pray for the next one... just in case

Cheers!
[X 2014 Original Android Development] tacosrdelicioso:
Just checked. I'm running 10/10. My crack flashing days must be fading :/
[X 2014 Original Android Development] :
Is it supposed to say...

"Android security patch level"?
[X 2014 Original Android Development] surrealjam:
Yes.
[X 2014 Original Android Development] Spin_spinning:
Hum, updated to the 1030 nightly and after a few days my Ambient Display doesn't work anymore. In Settings-Gestures both switches are "on", but greyed out so I can't even deactivate and re-activate it :crying:

Rebooted, same problem.

Cleared Cache and Dalvik (o.O), same problem..

Any ideas?

---------- Post added at 01:08 PM ---------- Previous post was at 12:37 PM ----------

Update: Flashed the nightly 1106, that didn't help at all :(

Furthermore, chop-chop gesture works (with display off), but twist-twist (set to camera) does not (even with display on).

Gnaa!
[X 2014 Original Android Development] NXghost:
probably you or the ROM (automatically) deactivated 'Ambient Display' on Display settings, that's why the switches are greyed out. Don't know about the camera gesture, maybe messing out on gesture settings can solve this problem.
[X 2014 Original Android Development] invisiblek:
Just a little update: M is coming along nicely. About the only thing left to fix is the camera (crashes when taking a pic). Looks like we're in pretty good shape! :good:

(seriously though, what a hack-fest to get L blobs working on M...I feel dirty about some of the patches I pushed for this :silly:)
[X 2014 Original Android Development] Spin_spinning:
Ugh, seems you're right. That helped! Thanks :)

(Strange that there are two places to activate this. Could've saved this thread the "spam" ;) )

Sounds great! Thanks for the update :)
[X 2014 Original Android Development] abhay6547:
So should we be seeing nightlies roll out within the next couple of weeks?
[X 2014 Original Android Development] invisiblek:
I expect victara to be among the devices that get the first round of nightlies. Whenever that happens (I honestly don't know yet)
[X 2014 Original Android Development] dictionary:
Even those of us who don't mind camera not working, would you still be holding off on a beta release? Itching to see improvements on my X2
[X 2014 Original Android Development] invisiblek:
I can't give you a build with a bad camera, I'd never be able to forgive myself.

So here's one with a working camera: http://www.invisiblek.org/roms/cm-13.0/victara/

;)

PS - its selinux permissive, so those with tinfoil hats: this build may not be for you.
[X 2014 Original Android Development] dictionary:
Time to rush home and download, :w00t:
[X 2014 Original Android Development] Tommebaas:
Wow, thanks a lot!

Are the gapps included?

I'm about to flash this after a backup of cm12.

Sent from my Moto X
[X 2014 Original Android Development] dictionary:
Running good so far. Using Banks Dynamic 6.0 gapps, and SuperSu 2.52 Beta. Any recommended governor settings? I know Doze will help with standby, but curious about improvements in use as well.

You're a champ, really appreciate the hard work you've put in.
[X 2014 Original Android Development] :
CM 13.0 Unofficial

I wiped all 5 partitions, flashed using TWRP 2.8.7.1, no errors, flashed Delta Gapps for M, booted normally, and quickly, with no issues.
[X 2014 Original Android Development] tanishque italia:
Now on tap working? ??
[X 2014 Original Android Development] G4 Man2:
Clean flash of the CM13 build is working fine here. FYI to anyone else that uses Open GApps, not working on this build due to commit that fixes compatibility missing from it. Gapps linked in the OP for MM had issues with Play services crashing during setup and perpetual "Loading...", trying to flash after setup causes a cluster of "has stopped". Banks Dynamic works fine though.

Also the non-compatibility mode V4A fix is working again on CM13

Fun fact, enabling advanced reboot and rebooting to recovery likes to say it's performing a "Factory data reset" instead of rebooting. Just thought that was funny.

Now on tap isn't working on this build for me.
[X 2014 Original Android Development] :
Secure lockscreen and apn settings not working, apart from that it's super smooth. Thanks!
[X 2014 Original Android Development] Tommebaas:
wow double pressing the power button to launch the camera is really nice!

cm13 will be amazing.
[X 2014 Original Android Development] nerotix:
Yeah I agree. The breathe happens to quickly after one another.