yashsingh1/xdaforums huggingface dataset:
[X 2014 Original Android Development] nerotix:
Having trouble to get a good catlog for the slowmotion playback of videos. When using youtube it doesnt seem to bother me, but when watching a video in, for example, chrome, sometimes its slowmotioned and sometimes it isn't.. really odd. And with slowmotion I mean like 1 frame per few seconds.
[X 2014 Original Android Development] Flamehell:
Guys one question....cyanogen Os12 will be not available for our device right?tnx...

P.s:the build is uploading now.....;)
[X 2014 Original Android Development] tanishque italia:
This is getting really confusing! [emoji20] Sorry if this is already been answered! May i please know where the new build is being uploaded official or unofficial?

Thanks in advanced![emoji4]
[X 2014 Original Android Development] nerotix:
Official build finally succeeded; http://download.cyanogenmod.org/?device=victara
[X 2014 Original Android Development] Flamehell:
Yes!!!!!!:D:D
[X 2014 Original Android Development] tanishque italia:
Finally! I'm sure it's just uploaded because i kept on checking the whole day! And my hearty thanks to all the devs who made it possible and provide us the unofficial builds![emoji4] [emoji4] [emoji4]
[X 2014 Original Android Development] Flamehell:
Guys,why if i try to find the new build,the ota says that there are no updates?i have to wait?

Now i can see the new build...sorry :D
[X 2014 Original Android Development] Flamehell:
Guys,the new nightly is awesome!!fast and stable....tnx!!! [MENTION=3857343]crpalmer[/MENTION] you are great man!!!
[X 2014 Original Android Development] armandocorti:
I Think this is why the video playback have problems, the use NuPlayer (Experimental) in developer option have to be enable, if tou disable the video doesnt work. Look Vídeo Problem Moto X: https://youtu.be/nSJRLuAvkHI
[X 2014 Original Android Development] danger2u:
how is battery life?

thanks
[X 2014 Original Android Development] Flamehell:
For my personal usage,much more better than the stock.....one day is covered for me.....:)
[X 2014 Original Android Development] danger2u:
can u see the SOT time??

there are bugs or somethings like this?

thanks
[X 2014 Original Android Development] Flamehell:
Man,trust me....give it a try......you will be happy.....;)
[X 2014 Original Android Development] 0.0:
My SOT time is usually 2.5 hours. I get more battery with stock than CM, but I like CM so I compromised.

What do you do with your phone? I have quite a bit of background apps, like all the major social media apps and I listen to music quite often. If you're like me, expect 9 hrs or so of battery life
[X 2014 Original Android Development] alexnaoumi:
do you guys still have issues with video playback in the browser on the newest nightly? I do. Has there been any kind of fix we can do to the ROM
[X 2014 Original Android Development] Jazznax:
+1
[X 2014 Original Android Development] lizaSB:
Battery life has improved overall for me from stock. Though I just realized that there's a bug with version 7 of google play services and custom roms. Basically, the update service holds a 100% wakelock on the device because the service is failing to update (because the service is disabled on custom roms, it just keeps trying to update over and over -- it's a weird bug). Anyway, if you've noticed that your device isn't sleeping properly, you can solve the problem easily with Tasker (http://xdaforums.com/paranoid-andro...oogle-apps-t2943900/post59350828#post59350828) or an xposed module Wakelock Terminator (filter google play services for the wakelock "SystemUpdateService"), it might be possible to solve this issue with an init.d script as well. There is a very heavy handed approach if you don't own tasker or want to install root. Basically, find google play services in app ops and disable its ability to wake up the device and keep the device awake. Otherwise, you should stick with a gapps package that doesn't include version 7 (the gapps package in OP has version 6.5.xxx)

Anyway, I've gotten 4 hours of SoT consistently and I never have any issues getting through my day (even with this bug, which I just discovered was affecting my device last night). Overall, I'm extremely happy with CM12 and I don't miss the stock features crpalmer hasn't figured out how to give us one bit.
[X 2014 Original Android Development] crpalmer:
I don't...

If you have a problem, please provide specific steps to reproduce it (go to xxx.com and click on video yyy in browser zzz) and logs of the time you had a problem.
[X 2014 Original Android Development] benfiller:
Hi,

Thanks for the great work, this ROM is awesome, stable and fast.

The only bug I've encountered is the clock resetting after a reboot, it takes some time to get the right time. Not a huge bug that I can't live with, just wanted to point the issue.

Again thanks a lot for your work :)
[X 2014 Original Android Development] Flamehell:
New nightly running good!!!guys,are you updating every day your nightly?or one a week for exemple...?
[X 2014 Original Android Development] beelzebu:
I think the problem is with TWRP and not the ROM itself, Every time I enter into TWRP it has a new system time and date.
[X 2014 Original Android Development] armandocorti:
Same here

---------- Post added at 12:08 PM ---------- Previous post was at 12:04 PM ----------

Hi, i posted a video yesterday.

Vídeo Problem Moto X: http://youtu.be/nSJRLuAvkHI
[X 2014 Original Android Development] crpalmer:
I looked at that. Don't disable nuplayer. You need to be use it.
[X 2014 Original Android Development] nerotix:
I cant think of a site atm.. but it seems this videoplayer slowmotion/stuttering/not loading happens when u few a video from a website that doesnt use youtube for example but has it's own version of a videoplayer. Youtube videos are perfectly fine for me.
[X 2014 Original Android Development] icedmayhem:
Anyone having just random reboots. Can literally be doing anything and bam, screen freezes, unresponsive, and reboot. Its happened but not limited to GPS, phone, text. Data, etc. Been having it for the last few nightlies ??
[X 2014 Original Android Development] nerotix:
Havent had that ever since Im using CM12, over 3 weeks now, never. Try a clean install.
[X 2014 Original Android Development] lizaSB:
Same here, not one random reboot. I second the suggestion of a clean flash
[X 2014 Original Android Development] 0.0:
The FFC has lag in low light. According to the Moto X 5.1 change log, lag in the FFC viewfinder is supposedly fixed. When the 5.1 stock ota releases, could it be possible to fix the lag?

sent from my Moto X Pure Edition
[X 2014 Original Android Development] crpalmer:
It depends on where the problem is located. Most likely it is in the camera blobs at which point it should be easy to fix.

FYI, when 5.1 is officially released as an OTA and cm-12.1 is building on victara, my plan is to return to stock, accept the OTA and then dump my own system partition to ensure I get a real clean version of all the blobs and then update them from that dump.

*edit* that is "selectively update" as there are blobs which we are using which may be newer than what motorola releases (adreno, for example).
[X 2014 Original Android Development] 0.0:
Thanks for the info. Can't wait for that

Also does this commit http://review.cyanogenmod.org/#/c/91946/ fix AudioFX? AudioFX doesn't work on this device for some odd reason...
[X 2014 Original Android Development] crpalmer:
Nope, that's not related to audiofx.
[X 2014 Original Android Development] murdok83:
Hi guys, i have the moto x 2014 European pure version (xt1092) and i would unlock the bootloader only for the ability to calibrate the display colors directly from the kernel (not using the apps available on the store) and to change the vibration intensity...

now, I have few questions.. I tried searching the tread without reasults:

1) can it be installed on the version Xt1092? It should but I ask just to be sure

2)does it have to option to change the color calibration or at least a kernel that supports that!?

3)can I change the vibration intensity!?

I have a nexus 6 and with cm12 I can do all those things...I'm wondering if this ROM has those option as well..

I imagine with this custom ROM I lose allnthe moto x functionalities (active display etc)

Thanks
[X 2014 Original Android Development] crpalmer:
The log and steps to reproduce were very helpful. It should be fixed in the next nightly (which will probably get built in about 2-5 hours). It turns out that we're doing a much better job of doing hardware decompression of audio than motorola and that broke their amp implementation. Hopefully I got it fixed correctly.

Let me know.
[X 2014 Original Android Development] murdok83:
Nobody that has tried the ROM can give me an answer... I haven't unlocked my phone yet and I would prefer not to "lose my warranty" without being sure I can get what I want...

Thanks
[X 2014 Original Android Development] Flamehell:
Edit
[X 2014 Original Android Development] Sdobron:
The only thing stopping me from going to cm is the lack of infrared sensor drivers. Is this a technical impossible task or just difficult? I'm hoping all the sensors will be 100% functional in non stock ROMs.
[X 2014 Original Android Development] danger2u:
someone who testing the rom can tell me if this one have this options:

2)does it have to option to change the color calibration or at least a kernel that supports that!?

3)can I change the vibration intensity!?

thanks
[X 2014 Original Android Development] fuze_freak:
Unfortunately you can not change the vibration intensity and trust me I have try pretty much all the cm base ROMs for the moto x 2ndgen. I guess is something that has not been implemented on a kernel level.
[X 2014 Original Android Development] danger2u:
thank u
[X 2014 Original Android Development] Flamehell:
Guys one question....when 5.1 will be available on stock by ota,all the fixes that will be included,will be also included in cm 12.1 for our device?
[X 2014 Original Android Development] 0.0:
[MENTION=3857343]crpalmer[/MENTION] when in a phone call, the other person cannot hear me. Could it be from the kernel and/or device commits?

edit: I reverted two commits and it fixed the problem: http://review.cyanogenmod.org/#/c/91975/ and http://review.cyanogenmod.org/#/c/91946/. However, I do not know if both cause the problem or just one of them (but which one?)
[X 2014 Original Android Development] crpalmer:
I had that problem on Sunday but thought I had tracked it down to other changes I had made. After reverting those and doing a new build I have had no problems (including a dozen test calls and several "real" calls, all of which caused me problems on Sunday).

Got logs? logcat and dmesg?
[X 2014 Original Android Development] 0.0:
I would need to build with those two commits again to test. I will also get logs if the problem occurs
[X 2014 Original Android Development] crpalmer:
You can test the echo reference by just changing /system/etc/mixer_paths.xml on the device. No need for a new build to try that one out.
[X 2014 Original Android Development] 0.0:
I changed it and took out the new lines that were added and my voice was heard in a call. Before removing the lines, that wasn't the case

sent from my Moto X Pure Edition
[X 2014 Original Android Development] crpalmer:
It's weird that I can no longer reproduce it, but I reverted that commit anyway to be on the safe side. Thanks!
[X 2014 Original Android Development] 0.0:
Out of curiosity, what was that commit for?

sent from my Moto X Pure Edition
[X 2014 Original Android Development] crpalmer:
cmxlog tells you what's in the queue for the next build (red package names indicate that they are device specific packages). So assuming it builds, it will be in it:

http://www.cmxlog.com/12/victara
[X 2014 Original Android Development] KalenXI:
I had the same problem of whoever I called not being able to hear me and removing those lines also fixed it. I'm also able to reliably reproduce the issue by adding the lines back in.

I ran a log both with and without the lines. And the only significant difference I could find was that with the lines removed I get "E/audio_route( 336): unable to find path 'echo-reference'". Here's the logs in case you can find anything more interesting...

With Patch (Audio Not Working): http://pastebin.com/JNDUGLgU

Patch Reverted (Audio Working): http://pastebin.com/Z0837hq0
[X 2014 Original Android Development] Flamehell:
Last nighly is very stable and fast,tnx a lot for your great work!:)
[X 2014 Original Android Development] nsmart:
Does anyone use device encryption with cm12 and are there any issues that arise when I enable device encryption?

I have different devices with cm and device encryption enabled and therefore I know that encyption sometimes causes weird issues (breaks compass, wifi, etc).

Is the current twrp version 2.8.6.0 able to decrypt the encrypted data partition ?
[X 2014 Original Android Development] arzafran:
Hey great work everybody, is anyone working on the IR sensors? what's the status on that matter? i'm asking cuz I want to help, i've got limited knowledge about android kernel/rom, just builded a couple of them, but i'm willing to learn, if someone is willing to teach! and if there's anything I can contribute!
[X 2014 Original Android Development] tapan15in:
[MENTION=3857343]crpalmer[/MENTION].. i am compiling sokp unofficial. Now i am getting the below error. Is it something you can help me to resolve it please..

http://pastebin.com/H73MYDrr
[X 2014 Original Android Development] michyall:
for those concerning about battery take a look at these screens

4 hours screen time and still 23% battery.

cm = super nice rom
[X 2014 Original Android Development] crpalmer:
From a glance, it looks like your different repos are pulling from incompatible versions (aosp vs. Cm vs. Your ROM). That means you need to either change the repos or figure out which commits need to be added to the repos that you are using.
[X 2014 Original Android Development] tapan15in:
can you tell me the exact repo which i should use and should add in roomservice.xml?
[X 2014 Original Android Development] da900:
Could you describe where it could be activated? S

Developer options/ root access/ Apps and adb is enabled.
[X 2014 Original Android Development] crpalmer:
If that is activated then you should have Superuser in the Settings list.
[X 2014 Original Android Development] da900:
http://review.cyanogenmod.org/#/c/82236/

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

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

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

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

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

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

Seems like Superuser is removed. It is rebased to Privacy Guard. ButbI do not have option in there for root access.
[X 2014 Original Android Development] kevdliu:
Is there a way to read values from all 4 proximity sensors on the 2014 x? The standard Android Java API only uses the top left one. The reason is that there's a way to manually activate ambient display or "doze" via an intent. If we can read the values of all the proximity sensors via sysfs or some other method we can recreate our own implementation of moto display.

Any help would be appreciated!
[X 2014 Original Android Development] da900:
Delete. :p
[X 2014 Original Android Development] micr0g:
Hello [MENTION=3857343]crpalmer[/MENTION] i think we lost some performance after the latest kernel commits as you disable the "always 4 cores online",i also see a bit lag (sometimes) when i scroll in settings and lower benchmarks.

Edit

So i did some tests reverted your commit http://review.cyanogenmod.org/#/c/83763/1/rootdir/etc/init.target.rc

and i saw 2000 points difference on antutu.

https://www.dropbox.com/s/5rhqmqezof9hgka/Screenshot_2015-01-07-23-48-54.png?dl=0 VS https://www.dropbox.com/s/qfeosw0nacud4zd/Screenshot_2015-01-07-23-48-57.png?dl=0
[X 2014 Original Android Development] Grondinm:
GPS not working for me either. That's the one thing i always forget to test. At first glance i'm not seeing any errors in logcat...i will try to investigate further tonight
[X 2014 Original Android Development] crpalmer:
I haven't looked into it at all yet (getting everything working first). But, my guess is that there is no reason why we can't have the sensors working for ambient display and that we can probably even hook into the "quickdraw" functionality to do a lighter weight update of the display for it as well.
[X 2014 Original Android Development] skulldreamz:
My pure arrived today. Just went to download the latest nightly and noticed it is 88mb compared to the other 260ish mb nightlies. Downloading the nightly from the 6th now :)
[X 2014 Original Android Development] crpalmer:
Looks like the copy from my build machine to my download server failed. I deleted that build so that no one else has to figure that out too.... Thanks for pointing it out.
[X 2014 Original Android Development] Maelfus:
Are the known issues still accurate?
[X 2014 Original Android Development] crpalmer:
Yes.
[X 2014 Original Android Development] da900:
Strange thing, but I can't get root functions in Privacy Guard. Is there any secret for this to work? Flashing SuperSU is the way but it's very interesting why any root app does not have root permissions in the list?
[X 2014 Original Android Development] fighting4fun:
Same Problem here the only Rom with su is liquid :D

Edit: Best running ROM!! =) just flashed the supersu.zip :P thx to crpalmer
[X 2014 Original Android Development] fighting4fun:
BTW Hotspot is working on my XT1092
[X 2014 Original Android Development] crpalmer:
So it is for me as well (xt1095). Looks like there must have been a CM-12.0 wide problem that someone magically fixed for us!

Thanks for letting us know, I updated the list of known issues.
[X 2014 Original Android Development] fighting4fun:
There are also no problems with phonecalls on my phone ;)

Is it possible that you add the supersu and binary in the settings? :)
[X 2014 Original Android Development] crpalmer:
Last time I checked, immediately after booting the phone an incoming call doesn't have audio until you toggle the speaker. Aside from that, yes, it has been working well.

I am not adding su packages because the goal is to fix the remaining problems and make this an official device.
[X 2014 Original Android Development] fighting4fun:
I had 15 calls today without an issue :) mabe you are right and its just immediatly after booting.

Ah OK then we have to flash it by ourself ;)
[X 2014 Original Android Development] crpalmer:
Actually, the in-call audio problem is even more specific than immediately after booting. I suspect, but I haven't tested, this may affect more than just our device and no one has noticed. I just noticed because of how I do my testing (aka, call my cell from my home phone and immediately mute my cell phone to avoid any chance of a feedback loop). The only problem with in-call audio is now:

During the first call that you receive after a boot, if you mute the microphone before you enable speaker-phone then your earpiece is silenced and to re-enable it you need to toggle the speaker on and off again. After that and after the first call, everything works normally. You can mute the microphone and make and receive calls without any problems.
[X 2014 Original Android Development] nerotix:
[MENTION=3857343]crpalmer[/MENTION] which trying to build CM12.1 but after repo syncing it together with your proprietaries and it syncs fine. However, when doing a breakfast and pick victara's number, I end up with this error:

ls: cannot access device/*/victara/cm.mk: No such file or directory

build/core/product_config.mk:234: *** Can not locate config makefile for product "cm_victara". Stop.

Device victara not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).

Found repository: android_device_motorola_victara

Default revision: staging/cm-12.1

Checking branch info

Default revision staging/cm-12.1 not found in android_device_motorola_victara. Bailing.

Branches found:

cm-12.0

Use the ROOMSERVICE_BRANCHES environment variable to specify a list of fallback branches.

ls: cannot access device/*/victara/cm.mk: No such file or directory

build/core/product_config.mk:234: *** Can not locate config makefile for product "cm_victara". Stop.

** Don't have a product spec for: 'cm_victara'

** Do you have the right repo manifest?

Any idea?
[X 2014 Original Android Development] Flamehell:
Guys i need to ask you one thing.....i m updating my phone every day with all the nightly....i want to know if i can only wipe cache and dalvik,or if i need to do something more,between one nightly and the other one.....i m using delta update....tnx guys....:)
[X 2014 Original Android Development] crpalmer:
That depends entirely on what that ROM did with their manifest and did in each of their repos. I can't help without sync'ing their repos and debugging what they have done. You'll need to start digging into it yourself to figure out why those symbols don't exist in their specific manifest / repos.
[X 2014 Original Android Development] crpalmer:
You should probably wait for the real cm-12.1 branches. The staging branches are still a little early and need special effort to work with...
[X 2014 Original Android Development] nerotix:
Thanks for the warning, however, im stubborn ;) I succesfully build CM12.1, gonna test it now and see what the bugs are, if any.

---------- Post added at 05:44 PM ---------- Previous post was at 05:19 PM ----------

Btw, would you mind if I share the 12.1 build here? I can understand if u prefer I wouldnt, since people might complain about bugs here. Tested quickly and runs well, everything seems to be working.
[X 2014 Original Android Development] crpalmer:
If I wanted a build here, I would have posted one....

WiFi has been hit or miss for me on boot. Some times I have to disable it and then enable it for it to work. a2dp sounds like crap. Telephony may still be a little flakey so it's still not quite ready yet. Otherwise though, it has been running pretty well for the last day or so (it was much more of WIP a few days ago).
[X 2014 Original Android Development] nerotix:
I did have the same issue with WiFi indeed, had to disable and enable in order to auto connect to my home network(only on boot ofc). Never use bluetooth so cant really test.

Edit: 1st boot after flashing I also noticed it didnt show that I was connected to 4g/network.. a reboot and it was fixed, however.
[X 2014 Original Android Development] Flamehell:
Guys,when cm 12.1 will be available,we need only to flash it over cm 12 like a normal nightly?Thanks...
[X 2014 Original Android Development] beelzebu:
I'm willing to try cm12.1 :)
[X 2014 Original Android Development] nerotix:
Im building a new CM12.1 now, and if ppl want to try cm12.1, drop me a pm instead of flooding this thread. Also, if u have problems, ignore it etc or make a useful log so people can find the bugs that are actually working on our device.
[X 2014 Original Android Development] raptir:
I did a little searching on this but all the posts I found were from over a year ago or were left unanswered.

Is apt-x supported in CM12? I have never owned an apt-x enabled device before so it has not been a concern for me. Most of the older posts I found said that it was not enabled, even on devices that support it, but those posts were about CM10.
[X 2014 Original Android Development] Joiner22:
The real racing 3 game does not work, no way, is to solve this?
[X 2014 Original Android Development] phanitej:
Post a log, not really sure if it is a ROM issue. Log might help us understand
[X 2014 Original Android Development] crpalmer:
Are you on the latest nightly? I feel like that was a themes bug that was fixed a week or so ago.
[X 2014 Original Android Development] JimYoung:
[MENTION=3826624]nerotix[/MENTION] I've sent you a pm :)
[X 2014 Original Android Development] Krishna563:
Data not working

Hey guys wondering if someone could help me. I cant connect to data. I have tried switching apns and resetting the apn but nothing seems to work. Any help would be useful. Thanks