[ROM] [5.1.x] Official CM-12.1 nightly releases
- Thread starter crpalmer
- Start date
I think the first one is a known issue.
I've noticed slightly worse standby time on the latest nightlies.
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)
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 ).
these are the additional lines needed in media_profiles.xml for slowmo ( from motox2)
Code:
[COLOR="Red"]<!ATTLIST VideoEncoderCap maxHFRFrameWidth CDATA #REQUIRED>
<!ATTLIST VideoEncoderCap maxHFRFrameHeight CDATA #REQUIRED>
<!ATTLIST VideoEncoderCap maxHFRMode CDATA #REQUIRED>[/COLOR]
Code:
<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 ).
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
i am on nightly of the 26th i think it was and xposed works fine. Make sure your running 75
I thought the latest was 74
Nvm, different thread had only up to 74
Sent from my XT1095 using Tapatalk
Last edited:
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
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
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.
Downloading latest nightly then. Only installing camera right? No need to flash any mod?
Enviado desde mi XT1097 mediante Tapatalk
"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)
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)
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.
probably be a mistake in victara, in cm12.1 mako , what do I reported here work perfectly :/
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.
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
probably cm13 is doing tests to victara as we see below
http://www.cmxlog.com/13/
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
Sent from my Moto X 2014 Pure Edition using Tapatalk
Sent from my Moto X 2014 Pure Edition using Tapatalk
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
40Code:
#include /* * Your warranty is now void. * * We are not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in this ROM * before flashing it! YOU are choosing to make these modifications, and if * you point the finger at us for messing up your device, we will laugh at you. * */
When coming from any other ROM, you must do a factory reset / clean flash.
The first boot can take a very long time. Don't assume that it is a bad flash, boot loop, etc. until it has sat for at least 5 minutes.
Links
ROM: http://download.cyanogenmod.org/?device=victara
Changelog: http://www.cmxlog.com/12.1/victara
GAPPS: http://d-h.st/users/dhacker29/?fld_id=27426 (pick the latest gapps-lpmr1*)
Known Issues
* AudioFX doesn't work.
GPS Issues?
* Asked and answered, search the thread for more info. As of the 2015-06-07 build, there should be no remaining issues so please try a new version before posting about it!
Other Issues?
Before posting on this thread, make sure of a few things:
You've utilized the search function of the forums. Nothing irritates me more than lazy people who do not search for an answer before asking.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread. "I'm having problems rooting/unlocking" is NOT relevant here.
LOGS LOGS LOGS!!!! Use this: SysLog by Tortel15Just 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
15
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.13looks like the build failed for something that wasn't my fault this time =P
Code: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
@flitzjoy - cm-13.0 is coming along. victara is my slowest device since its my daily driver and i have to backup to test anything
