yashsingh1/xdaforums huggingface dataset:
[X 2014 Original Android Development] lizaSB:
FC on rotate appears to be fixed in the official nightly build (didn't test your build from the 10th though crpalmer). Certainly looking forward to whatever 5.1 will bring us. Maybe, when the time comes, Moto will even give us a new radio ;)
[X 2014 Original Android Development] ATGardner:
Congratulations!

I'm switching over right now.

And thanks again for all your work.
[X 2014 Original Android Development] manrock:
Erase data to move to official nightlies? Or flash as is on top of existing build
[X 2014 Original Android Development] crpalmer:
You should switch to the official ones. They should be the same but you will get OTA updates when new nightlies are available and I will be turning off my unofficial nightlies.

Feel free to discuss either version here though.
[X 2014 Original Android Development] crpalmer:
Dirty flash should be fine. It's really just the same code but built on the official servers and using the official infrastructure for updates, changelogs, etc.
[X 2014 Original Android Development] manrock:
[MENTION=3857343]crpalmer[/MENTION]

Just an FYI.. I recently built the kernel sources from https://github.com/crpalmer/android_kernel_motorola_msm8974

Trying to bake in the dt2w feature into it..

I noticed that i had to fix a lot of tiny things. Stuff like "angle brackets vs quotes includes" etc. Also noticed that a lot of people face these issues while building android or even linux kernels. Is this a build environment thing?
[X 2014 Original Android Development] crpalmer:
Sounds like a build environment thing, but I have also never tried building the kernel outside of the full android build so it is possible something is wonky when you try to build it standalone.

If you want to post (in the DEV thread instead of this one) with the steps you are running to build the kernel and some specific errors, I can take a look and see if I have any suggestions.
[X 2014 Original Android Development] Tayrom:
Android 5.1 codes have been merged by CM team?

Thanks!
[X 2014 Original Android Development] TheMorpheus:
Theme FC are fixed on official build?
[X 2014 Original Android Development] crpalmer:
I saw a commit yesterday that fixed your crash. No idea if that was the only problem though.
[X 2014 Original Android Development] Shemploo:
Hope it's ok to post here, here is the link to the official builds.

http://download.cyanogenmod.org/?device=victara
[X 2014 Original Android Development] 0.0:
Nope, not yet. I am hoping it will be by the end of the week though

sent from my Moto X Pure Edition
[X 2014 Original Android Development] TheMorpheus:
Nice!!! dt2w is the only thing I'm missing from my previous phone!

Is it working? I'll looking forward to hear from you in the other thread
[X 2014 Original Android Development] RJQXCV:
GPS Fix

Hi,

http://forum.cyanogenmod.org/topic/105666-no-working-gps-in-moto-x-2013-xt1053/

Is there anyway this can be incorporated so we can get working GPS/why wasn't this incorporated earlier?

Not being rude, but I'm just interested in the technical side. :)
[X 2014 Original Android Development] crpalmer:
Technical side? I think he didn't acquire a gps lock in stock, had problems, installed a stock rom and now has a gps lock on CM. Same as anyone else...
[X 2014 Original Android Development] RJQXCV:
"I do not know if this in and of itself contributed to the fix, but I found a Brazil Moto X 4.4.2 ROM. I was able to install it. I obtained a lock, but before going back to CM, I, of course, obtained the GPS.conf"

No, it clearly states here that he grabbed the gps.conf from stock and replaced it when he flashed CM.
[X 2014 Original Android Development] crpalmer:
You just quoted: "I found a Brazil Moto X 4.4.2 ROM [aka stock]. I was able to install it. I obtained a lock".
[X 2014 Original Android Development] Alves-CA:
The LiveDisplay function is managed by the kernel or GPU? The Moto x 2014 CM kernel supports this function?

This can drain my battery ?
[X 2014 Original Android Development] 0.0:
A user tried flashing stock GPS.conf but it didn't work. You need to be on stock ROM, get a GPS lock then restore or flash cm

sent from my Nexus 7

---------- Post added at 05:38 PM ---------- Previous post was at 05:37 PM ----------

More so the kernel controls the live display. I have no clue if it'll drain battery, but I don't think it will

sent from my Nexus 7
[X 2014 Original Android Development] 0.0:
Does AudioFX work on the latest nightly?

Edit: it still doesn't work :(

sent from my Moto X Pure Edition
[X 2014 Original Android Development] crpalmer:
It does not drain the battery on our device because the colour control is done via hardware post processing not by manipulating the pixels like a userspace application would do. FYI, It require device specific changes to make that happen so there will be other (mostly older) devices running CM that may not be doing it via hardware so the answer that it doesn't drain battery is really specific to our device and the current state of our kernel/device support.
[X 2014 Original Android Development] manrock:
I wouldn't get my hopes up if I was you. I am only a beginner and the only experience i have with kernels is a driver i backported some time ago.. However i have isolated the commit in ElementalX kernel that added support for dt2w..

https://github.com/flar2/flo/commit/c7c564fb951720d2c157eda7f72434eb1cafd2f4

Hopefully I can integrate it and somebody more experienced with kernel release management can guide me make it available to the masses..

:)
[X 2014 Original Android Development] Tayrom:
thanks for your answer!

---------- Post added at 01:37 PM ---------- Previous post was at 01:34 PM ----------

@crpalmer

One question! His compilations, passed will be official in the Cyanogemod site?
[X 2014 Original Android Development] endursa:
I think there is something wonky/funky going on with the headphone port!

i had the problem, that my headphone sometimes where droping in volume, besides me not doing anything!

at first i thought it was the headphones, but i tried severals and also on different sources! so that is not the problem,

second i thought my physical headphone port was the problem, but it workst just fine with my studio headset

then i flashed back to stock, and the problems where gone,

it only happens if i use headset buds with built in mic, and if i wiggle around the cable! sometimes music goes lower in volume, sometimes it goes silent!

i also tired cm12 (unofficial and latest official) and also pa A1 ! problem seems to be kernel related maybe?
[X 2014 Original Android Development] armandocorti:
I just hope the video playback could be fix soon :(
[X 2014 Original Android Development] crpalmer:
With that helpful report, I should easily reproduce and fix some problem that I don't have or otherwise know about.

Aka, steps to reproduce, data to reproduce and logs or there is nothing I can do.
[X 2014 Original Android Development] lizaSB:
I believe he's talking about the "slow motion" videos in youtube. The only time I've gotten this is when using youtube's API to show a video in another app. For me, I use Sync for Reddit and any video opened within the app (without opening the YouTube app) plays in slow motion. When the video is opened externally by the YouTube app, I don't seem to have an issue

Was trying to get you a logcat of it happening but I can't seem to reproduce it now. Strange cause I definitely had the issue last night. I wonder if it's because I've opened the YouTube app now. Gonna try a reboot and see if the problem comes back
[X 2014 Original Android Development] lizaSB:
Managed to reproduce it on a reboot. Doesn't seem so much slow motion as a failed load -- the video plays slowly then stops. Upon reloading the video all is well. Not actually sure this is a problem with your rom, I feel like this could be a bug with the app, but I could be wrong...
[X 2014 Original Android Development] tanishque italia:
After performing the gps lock and then flashing cm can i perform a factory reset?
[X 2014 Original Android Development] michyall:
yes
[X 2014 Original Android Development] armandocorti:
Not only happen with you tube, happens with the videos i have on my SD Card.

CM12 Video Problem: https://youtu.be/P55bO4UrikE
[X 2014 Original Android Development] michyall:
i have no trouble with youtube videos perhaps sometimes with facebook videos. when i click play it hangs so i found a temporary solution, press power button to turn off screen the press it again and return to facebook and watch your video.

for other videos, like telegram whatapp i used to play the with mx player since a lot an no trouble.

with the last nightly i have sms app crash when creating new sms and no found hot to reproduce it, when typing number it FC, but strange fact is that it force close with random numbers. sometime with number 1, later for example with number 3.

:eek:

numebers that make com.android.mms crash are 0 1 3 4 only
[X 2014 Original Android Development] 0.0:
For SD card videos, have you tried using a different video player? MxPlayer is decent. You can also try VLC media player.
[X 2014 Original Android Development] da900:
I am sorry for asking. But why are there no new builds for victara since 11th of March?
[X 2014 Original Android Development] crpalmer:
Use the official builds, see the first post for the link.
[X 2014 Original Android Development] tanishque italia:
Thats the same for official builds! ?? Anyways this is not the proper place to say that..
[X 2014 Original Android Development] crpalmer:
I turned off the unofficial builds, which is what I thought your problem was. However, it seems like my servers and the official build servers don't agree on how to run lz4 compression. I reverted the commit that should be causing problems until we agree on how it should be run. Hopefully you'll get a build tomorrow.
[X 2014 Original Android Development] TheMorpheus:
Here my unofficial build if you guys want an update before official starts again https://www.androidfilehost.com/?fid=95916177934542382
[X 2014 Original Android Development] nerotix:
How screwed are you when your phone is dead and has no battery? Since u can't charge it when it's off.
[X 2014 Original Android Development] 0.0:
Huh? I thought you can charge the phone while it's off and has a dead battery...

sent from my Moto X Pure Edition
[X 2014 Original Android Development] nerotix:
Well I just tried it and my screen started flicker etc while showing the battery icon.. not sure if it was charging, but I also read on some other thread that offline didnt work there either. As almost every other custom rom here is based on CM12 I figured I try it and it was flicker etc so dunno.. either that or I should try a different adapter. Could you perhaps test it and see if it charges normally for you?
[X 2014 Original Android Development] 0.0:
I don't necessarily want to test it since I do need my phone. Perhaps crpalmer has an answer about the issue

sent from my Moto X Pure Edition
[X 2014 Original Android Development] BK553:
[/COLOR]

I've mentioned this twice, and never got a response. Really annoying.
[X 2014 Original Android Development] crpalmer:
I guess I haven't tested off mode charging. Most likely it works fine for charging the phone but the display is messed up. If someone wants to verify that before I have a chance, simply wait until your phone is >= 75% and then turn it off, plug it in and leave it alone for an hour. Then when you boot it you should see whether or not it charged.
[X 2014 Original Android Development] HeCareth:
I tested the battery charging while off today since my phone was completely dead when o woke up. Plugged it in at 6:30 am to the quick charger and came back at 7:45am and the phone was flickering. Turned it on and it was at 75% charge.

So seems to work for me.
[X 2014 Original Android Development] 0.0:
I can confirm that the phone does charge, but the display constantly flickers. I turned my phone off at 61% and turned it on to 95% charged after 40 minutes
[X 2014 Original Android Development] Flamehell:
Guys,i'm ready to try cm12....one question,is it stable as a dailydriver?I'm still in the middle to stay with stock or switch to cyanogenmod......suggestions?:)
[X 2014 Original Android Development] lizaSB:
Try it out and see for yourself? You don't have to perform an fdr anymore so you don't have much to lose. I've been using this rom over stock for 2 weeks now with no issues. If you are attached to the stock Moto features, you're gonna have a bad time as all we've got working is ambient display and camera double twist.
[X 2014 Original Android Development] Flamehell:
Tnx a lot mate!!!!Just one last question.....i saw that for now there are not every day builds......it will change after some days?we will have every day a new nightly?Tnx a lot!!!!:)
[X 2014 Original Android Development] lizaSB:
Don't mean to be rude, but this question was already asked and answered on the previous page.
[X 2014 Original Android Development] Flamehell:
Sorry,i was watching it now.....i have to wait for the next build....tnx!!!!:o
[X 2014 Original Android Development] nerotix:
Are you serious? I was waiting since last night for a new official build.. and than I'm watching jenkins and our build failed again.. argh :@ gotta compile myself I guess :(
[X 2014 Original Android Development] crpalmer:
Yeah, I'm fighting with the version of lz4 installed on the build is servers. Which is very annoying to debug. Sorry for the delay but there are some pretty good changes queued up in that build when it finally happens!
[X 2014 Original Android Development] Flamehell:
Tnx mate for your work!!!!:o

---------- Post added at 03:46 PM ---------- Previous post was at 03:28 PM ----------

[MENTION=3857343]crpalmer[/MENTION] in some hours do you think that we will see the new build?Tnx!!!!
[X 2014 Original Android Development] nerotix:
Mate, you're a bit too impatient. Compile a ROM yourself or let the man do the work in his own pace.
[X 2014 Original Android Development] Flamehell:
Sorry....was not my intention to be rude.....sorry :)
[X 2014 Original Android Development] nerotix:
[MENTION=3857343]crpalmer[/MENTION] trying to compile for myself again but for some reason when brunching I keep getting this error:

Looking for dependencies

Dependencies file not found, bailing out.

Looking for dependencies

Dependencies file not found, bailing out.

Done

build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/motorola/victara/cm.mk]]: "vendor/motorola/victara/victara-vendor.mk" does not exist. Stop.

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

** Do you have the right repo manifest?

Which is odd, cuz I just brunch and pick number 94 which is victara.. any idea?

Edit: I made a clean folder structure and fresh new sync. Didnt help.

Edit2: After cd-ing to android/system/device/motorola/victara and running extract-files.sh it seems to be going now.. not sure why the brunch doesnt execute the file itself?

Edit3: Well nvm that.. getting other error now: '

make: *** No rule to make target 'vendor/motorola/victara/proprietary/app/MotGeoFenceSvc/MotGeoFenceSvc.apk', needed by '/home/clemenzah/android/system/out/target/product/victara/obj/APPS/MotGeoFenceSvc_intermediates/package.apk'. Stop.

make: *** Waiting for unfinished jobs....

and the search goes on :P
[X 2014 Original Android Development] mcardielo:
Maybe you should let the man to fix first the official release and after maybe you can bother him with your problem
[X 2014 Original Android Development] nerotix:
I was compiling from the official CM sources.. hence I could stumble upon the same problem as the build bot has. This would help eliminate the cause perhaps.
[X 2014 Original Android Development] jtxdriggers:
You're missing the vendor files for victara. The extract-files.sh script will extract them from a stock device connected through ADB, but the easiest way is to just clone his proprietary repo. Add this to your local_manifest and repo sync, then try a clean build.

<project name="crpalmer/proprietary_vendor_motorola" path="vendor/motorola" remote="github" revision="refs/heads/cm-12.0" />
[X 2014 Original Android Development] nerotix:
Oh O_O I removed my local manifest because I thought I didn't need them anymore now that it's all official by CM etc. Will try to build again with the local manifest included.

Thanks!
[X 2014 Original Android Development] jtxdriggers:
CM can't distribute closed source binaries like that, so they provide the extraction scripts so that users can extract the files from a running device that they own. In theory, you would only have to run that script once, and the files will stick around for each build. In practice, it's really convenient to let someone more experienced take care of it for you. This is why the proprietary repo is owned by crpalmer and not CyanogenMod.
[X 2014 Original Android Development] crpalmer:
Did you get any error messages when you ran the extract-files script? Try running

adb root

to make adb have permission to read all files before running the extraction script.
[X 2014 Original Android Development] nerotix:
I didnt get any errors, however, what was suggested earlier seems to be working, building for 30 mins atm, will let u know if the build was succesful.

Thanks
[X 2014 Original Android Development] Flamehell:
Sorry guys,i m watching on jenkins where is our build.....how it works the queue?Where is possible to see when our phone will be updated?Tnx guys :)
[X 2014 Original Android Development] nerotix:
Mate, After running for almost an hour it seems I have the same error as the build bot, check the pastie link with the error.. after all those warning and error lines it just stopped. If you look at the top, you'll see:

lz4c -9 < /home/clemenzah/android/system/out/target/product/victara/dt.img.raw > /home/clemenzah/android/system/out/target/product/victara/dt.img

/bin/bash: lz4c: command not found

device/motorola/victara/mkbootimg.mk:29: recipe for target '/home/clemenzah/android/system/out/target/product/victara/dt.img' failed

make: *** [/home/clemenzah/android/system/out/target/product/victara/dt.img] Error 127

make: *** Deleting file '/home/clemenzah/android/system/out/target/product/victara/dt.img'

make: *** Waiting for unfinished jobs....

Guess it has to do with lz4c thing? How can I revert that commit?
[X 2014 Original Android Development] crpalmer:
sudo apt-get install liblz4-tool

?
[X 2014 Original Android Development] nerotix:
Just noticed you merged a new commit regarding this.. ill sync again and try build again and ofc install the tool.
[X 2014 Original Android Development] crpalmer:
The commit I just pushed tries to use the more modern lz4 command line if it exists and if not tries to use the circa 2013 command line on the version that was installed on the build servers. You need to install one or the other for the build to work.
[X 2014 Original Android Development] mcardielo:
dude, you don't have the same error as the build bot, the error on the build bot was

*** LZ4 Compression CLI , by Yann Collet (May 31 2013) ***
Wrong parameters
Usage :
lz4c [arg] input output
Arguments :
-c0/-c : Fast compression (default)
-c1/-hc: High compression
-d : decompression
-y : overwrite without prompting
-H : Help (this text + advanced options)
make: *** [/opt/jenkins/android/workspace/android/cm-12.0/out/target/product/victara/dt.img] Error 1
make: *** Deleting file `/opt/jenkins/android/workspace/android/cm-12.0/out/target/product/victara/dt.img'
make: *** Waiting for unfinished jobs....
[X 2014 Original Android Development] nerotix:
Just a quick fyi; the build was completed succesfully. Thanks for letting me know that I needed the old proprietary and lib4 tools!
[X 2014 Original Android Development] crpalmer:
I kicked off an unofficial build including changes made up to about 2.5 hours ago:

http://download.crpalmer.org/nightlies/victara/cm-12-20150317-UNOFFICIAL-victara.zip

Hopefully that will tide people over until the next official builds makes it through the build servers.
[X 2014 Original Android Development] Flamehell:
Tnx mate!!!!can we flash this one,and after flash the official one?sorry but i m a noob on cm...(dirty flash?)but tnx for your work!!!
[X 2014 Original Android Development] crpalmer:
Yes. This is built using all the same repos that the official builds use, it just uses my server instead of their servers. It should be safe to dirty flash to this and then to the next official nightly. You probably won't be able to do an OTA install to the next official nightly though.
[X 2014 Original Android Development] jtxdriggers:
It looks like crpalmer has a more up-to-date branch in his proprietary repo called cm-12.0-adreno. You can probably build with that if you want the latest and greatest but I can only assume there's a reason it's not in the cm-12.0 branch yet.
[X 2014 Original Android Development] nerotix:
You mean this one?

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

It was merged this morning I believe, I synced up like 2/3 hours ago. Probably same as [MENTION=3857343]crpalmer[/MENTION] 's build.
[X 2014 Original Android Development] jtxdriggers:
The cm-12.0-adreno branch contains the updated adreno blobs as well as some missing mm-dd-daemon blobs. Syncing your device tree with that commit won't make your build contain those blobs unless you use the cm-12.0-adreno branch for the proprietary_vendor_motorola repo in your local_manifest.
[X 2014 Original Android Development] nerotix:
I tried looking for it on crpalmer's github but couldnt find it.. any link perhaps? or just the full line I can add to my local manifest.
[X 2014 Original Android Development] jtxdriggers:
Link to Github: https://github.com/crpalmer/proprietary_vendor_motorola/tree/cm-12.0-adreno

local_manifest.xml:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="crpalmer/proprietary_vendor_motorola" path="vendor/motorola" remote="github" revision="refs/heads/cm-12.0-adreno" />
</manifest>
[X 2014 Original Android Development] Flamehell:
Are you already try the unofficial build guys,or are you waiting for the official one?
[X 2014 Original Android Development] jtxdriggers:
The only reason to wait is if you want easy OTA's. Otherwise, the unofficial build is exactly the same, and there's no other reason not to flash it.

That said, it seems as though most people in this thread are building for themselves and don't care much for the OTA's anyway.
[X 2014 Original Android Development] Flamehell:
But

when you think that the official ota will be ready?Today or this night?Tnx!!!!:)
[X 2014 Original Android Development] jtxdriggers:
The answer is always "it depends". If the commit crpalmer pushed earlier works, we'll have a nightly available at the next build, which is currently 10th in queue according to Jenkins. If you NEED the latest build, then flash what crpalmer posted earlier, and then flash the next successful official build when it's out, then you should continue to get OTA's. If you want the least amount of work and don't mind the delays, then flash the latest official and you'll get an OTA when the next nightly is available (if you select nightly in your OTA settings).
[X 2014 Original Android Development] ticoticox3000:
Where can I find the unofficial builds?
[X 2014 Original Android Development] Flamehell:
http://download.crpalmer.org/nightli...AL-victara.zip
[X 2014 Original Android Development] ticoticox3000:
It doesn't work for me, the link is wrong

Here it is: http://download.crpalmer.org/nightlies/victara/ (:
[X 2014 Original Android Development] Flamehell:
If we are number ten in the queue of upload....in 3 or 4 hours we should get the new build right?:)
[X 2014 Original Android Development] nerotix:
Thanks for the link :) Not sure why I couldnt find it.

[MENTION=3857343]crpalmer[/MENTION] any input? Whats the difference between this branch and your normal branch? Just new adreno blobs or? And is there a reason we shouldnt use it?
[X 2014 Original Android Development] Hardtron:
4K viedo in CM12?

Hey guys, it's possible to get 4K recording videos in CM12?