yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] gt-kingz:
Thx for info, but i think it won't work anymore for the latest builds. Lets wait for ziddey to modify FK.
[Nexus 4 Android Development] Ajfink:
-Snip quote-

Are your builds appreciably different than what I'm rolling myself (i.e., straight from the repositories)?
[Nexus 4 Android Development] eris23:
No. No changes from the repo.
[Nexus 4 Android Development] Ajfink:
Sidebar - CM11 built this morning, w/ ART - power button doesn't lock the phone?

The switch to ART made this phone HOT! Thermally.

EDIT: Nevermind, it was just some FC's at startup holding up the button's functionality.

---------- Post added at 11:40 AM ---------- Previous post was at 11:03 AM ----------

Every reboot w/ ART enabled seems to go through the app optimization process for about half of the apps I have installed.
[Nexus 4 Android Development] acultr:
Guys?

Which one gapps can I use?
[Nexus 4 Android Development] Ajfink:
http://xdaforums.com/showthread.php?t=2397942
[Nexus 4 Android Development] gpvecchi:
No one can help me, please? :crying:
[Nexus 4 Android Development] Ajfink:
I advise NOT using ART right now.

Sent from my Nexus 5
[Nexus 4 Android Development] v12xke:
Reflash the ROM over the top of what you have, and if that doesn't work, simply restore to your latest nandroid. Takes 5 minutes. Now that new code and binaries are out for 4.4, it would seem a perfect opportunity to wipe and start fresh.... and then make a backup.

---------- Post added at 09:41 AM ---------- Previous post was at 09:25 AM ----------

Yeah, believe me I saw the link and do use FK, but I was using Colorfix before and it stopped working at one point. That and Franco has stated he has zero interest in changing his kernel to be compatible with CM. Ziddey stepped in and was making some modifications to the ramdisk? to make the kernels compatible. I'm gonna wait a while for Ziddey to do something (or not). If anyone else has the time to test and report back, it would be appreciated.

EDIT: Here is another thread with a FK based on r194

http://xdaforums.com/showthread.php?t=2413685
[Nexus 4 Android Development] eris23:
ziddey just made a kitkat kernel, but not for cm. http://xdaforums.com/showpost.php?p=47674291&postcount=1213
[Nexus 4 Android Development] eris23:
from cm's google+ page:

Android 4.4_r1.2 merged

For those that care about version numbers, we've updated CM 11 source for yesterday's code push.

Most notably, there is a fix for encryption/decryption for the 4.3 Nexus devices.

We are in the final preparation stages for CM 11 nightlies as well - you crackflashers will have something to play with soon.

It looks like the most common line in tonight's "repo sync" is:

* [new tag] android-4.4_r1.2 -> android-4.4_r1.2
[Nexus 4 Android Development] lilmeanz:
Cm11 does this update include Google dialer or should I flash zip ?
[Nexus 4 Android Development] RootTheMachine:
No, and nor does gapps. I haven't found a working zip yet either.
[Nexus 4 Android Development] 0.0:
Does cm11 still use caf?

sent from my Nexus 7
[Nexus 4 Android Development] eris23:
1st try to build 4.4 after all today's changes failed (in Gallery2). Running "repo sync" again.

2nd build try failed in "android-4.4/system/kernel/google/msm". Running "make clobber" for a full build.

3rd build try failed at same spot as 2nd. Will try again (with OpenJDK 7, just for curiosity) after tonight's 10.2/4.3.1 builds.

4th build try failed at android-4.4/system/out/target/product/mako/obj/STATIC_LIBRARIES/content_content_common_gyp_intermediates/content/common/android/hash_set.o

So, no cm-11/4.4 build. Alas.

5th build try worked (switched back to Oracle 6).
[Nexus 4 Android Development] v12xke:
Unfortunately, YES and I'm afraid that's not going to change. Many custom kernels that work on AOSP will not natively support CM due to the CAF libraries. Franco's FKU has a warning on r194 that it is not compatible with CM or its derivatives. I suspect that either the dev (or others) will modify the more popular kernels to be compatible... I hope.
[Nexus 4 Android Development] eris23:
20131121 build (4.3.1 - JLS36I)

with "Don't announce RC4 as the default cipher." http://review.cyanogenmod.org/#/c/51799/

cm-10.2-20131121-UNOFFICIAL-mako.zip

https://drive.google.com/file/d/0BxYe-w599Fv6dnZoaDJZX1BWSzQ/edit?usp=sharing

https://app.box.com/s/wglxwky47qd36avxpiwu

https://mega.co.nz/#!2QQEFSKD!D2BHlTgPpiqkVQ6fRJ-XvBrVNr5xmN_I_KnHwhvBSBA

http://www.mediafire.com/download/ce8cigewivsewsb/cm-10.2-20131121-UNOFFICIAL-mako.zip

cm-10.2-20131121-UNOFFICIAL-mako.zip.ms5sum

https://drive.google.com/file/d/0BxYe-w599Fv6U1NNWlk0UlZBMlk/edit?usp=sharing

https://app.box.com/s/pzpuiy5wy6imbfsxmo6z

https://mega.co.nz/#!WAA3AJYC!BeqDNzIK6esVsoddxjJBaE-HuMo1q4GQMNQg689okLI

http://www.mediafire.com/view/6c7wuutuwwdu68f/cm-10.2-20131121-UNOFFICIAL-mako.zip.md5sum

Not a full build. I removed build.prop from below

-----------------------------------------------------

without "Don't announce RC4 as the default cipher." Stock CM source.

cm-10.2-20131121-UNOFFICIAL-mako.zip

https://drive.google.com/file/d/0BxYe-w599Fv6ZEIwWjZsMElzajQ/edit?usp=sharing

https://app.box.com/s/us35dvnszb1okh6jv2eu

https://mega.co.nz/#!WUxi1aIR!IGSBuyE0gxDHc5Uzrbo59zFNrtszxGWV-FV1aOpO65Q

http://www.mediafire.com/download/ux0yxy300qzxytq/cm-10.2-20131121-UNOFFICIAL-mako.zip

cm-10.2-20131121-UNOFFICIAL-mako.zip.ms5sum

https://drive.google.com/file/d/0BxYe-w599Fv6YlktRzNINWU1N00/edit?usp=sharing

https://app.box.com/s/j6wltayqme41wcwkbjgj

https://mega.co.nz/#!zIJy2Lqa!b8n5RREAsJOxdwCHpqq3cl0UMUt5rsNk4OwqKYfcWjI

http://www.mediafire.com/view/flvhvlfb1vkkhh2/cm-10.2-20131121-UNOFFICIAL-mako.zip.md5sum

Not a full build. I removed "build.prop" from previous.

Changes:

From git://github.com/CyanogenMod/android_packages_apps_Gallery2

9dabf53..3be9bbb cm-10.2 -> github/cm-10.2

From git://github.com/CyanogenMod/android_frameworks_base

58c5923..e30568c cm-10.2 -> github/cm-10.2

From git://github.com/CyanogenMod/ion

a19375d..9a448a3 cm-10.2 -> github/cm-10.2

From git://github.com/CyanogenMod/android_packages_apps_Email

c7e082d..357743c cm-10.2 -> github/cm-10.2

From git://github.com/CyanogenMod/android_packages_apps_CellBroadcastReceiver

1d859be..641a55f cm-10.2 -> github/cm-10.2
[Nexus 4 Android Development] eris23:
20131121 build (4.2.2 - JDQ39E)

with "Don't announce RC4 as the default cipher." http://review.cyanogenmod.org/#/c/51799/

cm-10.1-20131121-UNOFFICIAL-mako.zip

https://drive.google.com/file/d/0BxYe-w599Fv6QlBzTmtDX281bVk/edit?usp=sharing

https://app.box.com/s/h3cui1sbkdcu5unt8zyx

https://mega.co.nz/#!nRZBkC6K!GtN5VhO9dqZRYga0DrVjV3rkyqcD3qNuHuwNEAvjtHw

http://www.mediafire.com/download/gw27fl6nuzfq8k2/cm-10.1-20131121-UNOFFICIAL-mako.zip

cm-10.1-20131121-UNOFFICIAL-mako.zip.md5sum

https://drive.google.com/file/d/0BxYe-w599Fv6NGRVNFNfZFJ2M0U/edit?usp=sharing

https://app.box.com/s/1oycbsf6wvbvayqkxxxv

https://mega.co.nz/#!2ZYnkY5b!GgyG3AfQFaHEcyyB4L4BFyM6d4Qxrdl2tj5zqYEu-yU

http://www.mediafire.com/view/ah5fc86hwd2919w/cm-10.1-20131121-UNOFFICIAL-mako.zip.md5sum

removed build.prop from below

-----------------------------------------------------

without "Don't announce RC4 as the default cipher." Stock CM source.

cm-10.1-20131121-UNOFFICIAL-mako.zip

https://drive.google.com/file/d/0BxYe-w599Fv6eC1rOXB5bk1ucjQ/edit?usp=sharing

https://app.box.com/s/gzc52bzh30n7odx3cjip

https://mega.co.nz/#!GYxgERZR!Z6Q-9GstxlZiHOvGDtzzenA48c8MZq7-b5WR5lu8Iuc

http://www.mediafire.com/download/j8v2086occsvecq/cm-10.1-20131121-UNOFFICIAL-mako.zip

cm-10.1-20131121-UNOFFICIAL-mako.zip.md5sum

https://drive.google.com/file/d/0BxYe-w599Fv6TUpVUm50eWU0N3M/edit?usp=sharing

https://app.box.com/s/mz03ms4e7f9g5plwomwb

https://mega.co.nz/#!nc521YaA!DKPxsQINMrQ4YWpnR1Vtzn0wiMlM3zc2FMhPxxYSlj8

http://www.mediafire.com/view/xjya3r13bzly1of/cm-10.1-20131121-UNOFFICIAL-mako.zip.md5sum

Not a full build. I removed "build.prop" from previous.

Changes:

<no changes>
[Nexus 4 Android Development] myzar:
For me cm11 builds fine, we can finally use the new binaries but there are still big problems with the new radio, wifi doesn't work and it's very slow to boot
[Nexus 4 Android Development] gpvecchi:
Unluckily not working, and my latest backup has not the widget... :(
[Nexus 4 Android Development] R-Rizzo:
Banks has an add-on zip for Google Dialer that I'm running....

http://www.androidfilehost.com/?a=show&w=files&flid=9199

Down towards the bottom....
[Nexus 4 Android Development] tmorterlaing:
In an on going effort for stuff to be clarified- I still can't seem to find out why theyve done this and what CAF affects- can anyone shed ANY light at all?

- I mean, I can only assume that they must have deemed it 'worth it' regarding performance or battery life if theyve essentially rendered the majority of popular kernels useless? But for some reason they havent seemed to have clearly justified it...
[Nexus 4 Android Development] v12xke:
I'm really sorry for your loss... of ten minutes. Stop grieving and get on with it mate.
[Nexus 4 Android Development] Ajfink:
I just flashed older radios and it seems to be working.

Edit - I've got a build running now, I'll see if it works for me.

Edit 2 - Obviously, as always, AT YOUR OWN RISK: https://www.dropbox.com/s/fp0g2iue2l1l53f/cm-11-20131121-UNOFFICIAL-mako.zip
[Nexus 4 Android Development] Smallsmx3:
Cm has always had the motto of using stock cm kernel if you want things to work. Y would they care now if customs don't work. I know i dont. It works pretty dam well in its current state
[Nexus 4 Android Development] gpvecchi:
I'n not sure that CM have that handles: they are not there even with a full wipe. Probably that's yours problem...
[Nexus 4 Android Development] tmorterlaing:
In the ever customisable, flashable and kernelable world that is Android, that feels a little short sighted or restrictive, no? But also that doesn't answer the question of what is so good about CAF? Regardless of the user experience, why did they make the decision to go that way?
[Nexus 4 Android Development] Smallsmx3:
I think part of it was to attempt to fix the deadlocks in 4.3. I've used cm since the froyo days. It's not being restrictive. If you weren't using the cm kernel don't complain about features not working, that's what i learned first thing. When JB 4.1 dropped they stopped optimizing the kernel and only used the Google kernel with almost no changes. I'm glad that caf is being used. I mean the patches are to optimize our hardware right? So what's the difference between using this vs. Linaro and other buzzword optimizations ? That, IMHO do nothing in terms of real world. Oh well.
[Nexus 4 Android Development] shotta35:
I use it just fine. All you need is the GoogleDialer.apk and the TeleService.apk from either ODEX or a Deodex ROM.

GoogleDialer and TeleService goes in priv-app

Delete the other Dialer.apk

And all set.

I can probably make a flashable one but it's not so complicated.

http://xdaforums.com/showpost.php?p=47542185&postcount=1565

Actually there but he didn't include the GoogleDialer.apk in priv-app since his ROM already does. If you want again, i can make it easy peasy.

----------------

Now obviously this means you wont get CM custom stuff for the dialer included with CM. The vibrate and other options included with CM will be replaced by basic Google Dialer.
[Nexus 4 Android Development] shotta35:
FYI - Tried it and was getting GUI Graphic glitches all over. WIFI didn't work with the new radio as well.

Guess i'll chill on 11/17 till CM11 goes official. :)

Thanks for all your work so far though eris
[Nexus 4 Android Development] Ajfink:
I'm using one of the hybrid radios from 4.3 and did a clean wipe before installing yesterday's build, and I'm not experiencing those issues. The new radio just seems problematic right now.
[Nexus 4 Android Development] antreasrx8:
Any kernels compatible with cm?

Hi there after trying some 4.4 roms I came back to cm10.2, 4.3.1. I can't read all the pages so I have to ask... Are there any kernels compatible with this rom? I am interested for battery life and s/w s/sleep... Thanks for the answer in advance...
[Nexus 4 Android Development] EnginEAR:
KRT16S

FYI- November 21st build of 4.4 is actually KRT16S. Wi-Fi etc. didn't work for me with the 84 radio so I flashed the 97 radio.

Still don't work.

No Wi-Fi, Bluetooth, and sound from speaker...
[Nexus 4 Android Development] lilmeanz:
Cm11 latest has crazy screen flashes
[Nexus 4 Android Development] shotta35:
Prolly cause all the parts aren't included yet. That should be getting sorted out hopefully in time for tomorrow's build.
[Nexus 4 Android Development] v12xke:
+1

Here too. First time I have seen these pretty nasty video glitches. Running CM 11-20131121. I've avoided flashing the new radio until somebody figures out wth is going on. Everything else seems to be working. Using Nova betas for transparent bars. These fixed "quck" tiles are killing me though. We need to get some long press action rolling!
[Nexus 4 Android Development] eris23:
20131122 build (4.4 - KRT16M)

cm-11-20131122-UNOFFICIAL-mako.zip

https://drive.google.com/file/d/0BxYe-w599Fv6OW5LMlZjNjlUcGM/edit?usp=sharing

https://app.box.com/s/hl49lglxqhvb5458j5nb

https://mega.co.nz/#!mZJ1yYgR!JoIiIhQv8WgjyIbeo3ejn3ua8OktMU6fag3J7LGjlbM

http://www.mediafire.com/download/pwtpj49ig8a8p47/cm-11-20131122-UNOFFICIAL-mako.zip

cm-11-20131122-UNOFFICIAL-mako.zip.md5sum

https://drive.google.com/file/d/0BxYe-w599Fv6VnlWeWVyTFR2clE/edit?usp=sharing

https://app.box.com/s/wphtf0q0d7zxd5jk8zw3

https://mega.co.nz/#!mMYiyCpS!BgCyLVJIuFiqcYzajsZ4Uyqwqjx1rnA4n18qyLJjG0U

http://www.mediafire.com/view/oe4u8h1z5592tuk/cm-11-20131122-UNOFFICIAL-mako.zip.md5sum

Not a full build -- removed "build.prop".

Changes:

From https://gerrit.googlesource.com/git-repo

ce201a5..cbc0798 master -> origin/master

repo version v1.12.7 is current

From git://github.com/CyanogenMod/android_packages_apps_Settings

880c320..4128568 cm-11.0 -> github/cm-11.0

From git://github.com/CyanogenMod/android_frameworks_base

ff1a971..e1294d3 cm-11.0 -> github/cm-11.0

From git://github.com/CyanogenMod/android_frameworks_av

3e187eb..fe0cd1d cm-11.0 -> github/cm-11.0

From git://github.com/CyanogenMod/android_vendor_cm

918821b..3dbb565 cm-11.0 -> github/cm-11.0

From git://github.com/CyanogenMod/android_external_chromium_org

3311b27..dd37648 cm-11.0 -> github/cm-11.0

From git://github.com/CyanogenMod/android_device_lge_mako

224794f..4075eed cm-11.0 -> github/cm-11.0

From git://github.com/CyanogenMod/android_hardware_qcom_audio-caf

50803c9..8090ad4 cm-11.0 -> github/cm-11.0

From git://github.com/CyanogenMod/Superuser

+ 37c0b08...0135135 cm-11.0 -> github/cm-11.0 (forced update)

external/koush/Superuser/: discarding 1 commits
[Nexus 4 Android Development] eris23:
10.2 build failed at "android-4.3/system/kernel/google/msm". Same as yesterday's cm-11. I'm trying a "make clobber" then another "repo sync" (but no changes on that) for a full build. There were 29 changes that I can see offhand. The build seems to fail after the "error" for the non-existent kernel modules. I guess that the cm build scripts are fairly generic, allowing some of the previous generations of roms to be built.

Failed again. This time at "android-4.3/system/out/target/common/obj/JAVA_LIBRARIES/ion_intermediates/classes-full-debug.jar". Will try another "make clobber", "repo sync", then, just to be different, if that doesn't work, building with Oracle 6 (rather than OpenJDK 7).

I just checked http://jenkins.cyanogenmod.org/job/android/48565/console, the official build failed at the same spot. That being the case, I'll run "repo sync" later and try to build then.

5th "repo sync". Build failed. Same place. Will try again later.
[Nexus 4 Android Development] acultr:
the display is still flashing after build 13.11.22.
[Nexus 4 Android Development] zequav:
Hmm I'm not seeing any problem with .97 radio and my custom CM build from yesterday. Wifi, bluetooth, 3g, everything works.

I do have the screen flickering since 2 days ago, though.

(edit) Wait, I have another "minor" problem: no audio during calls :)
[Nexus 4 Android Development] eris23:
20131122 build (4.2.2 - JDQ39E)

with "Don't announce RC4 as the default cipher." http://review.cyanogenmod.org/#/c/51799/

cm-10.1-20131122-UNOFFICIAL-mako.zip

https://drive.google.com/file/d/0BxYe-w599Fv6LThRTkpUZVJNSzA/edit?usp=sharing

https://app.box.com/s/293nwrbp9ntfx7u36t17

https://mega.co.nz/#!iY5jiArC!K_sXLHbKzxBfjnlcuKkdhjORulpnOQEZfj22woDRDUc

http://www.mediafire.com/download/xtowok9n56ju72c/cm-10.1-20131122-UNOFFICIAL-mako.zip

cm-10.1-20131122-UNOFFICIAL-mako.zip.md5sum

https://drive.google.com/file/d/0BxYe-w599Fv6VTRzNm8yQ3N0NHM/edit?usp=sharing

https://app.box.com/s/c7llxyls2qyfi4lr0wco

https://mega.co.nz/#!TYZgWazQ!WpfCaDhSLlCA-nxhy8I4eTuA34gqkabY0glZaIrwJOY

http://www.mediafire.com/view/735te283x9c7c33/cm-10.1-20131122-UNOFFICIAL-mako.zip.md5sum

removed build.prop from below

-----------------------------------------------------

without "Don't announce RC4 as the default cipher." Stock CM source.

cm-10.1-20131122-UNOFFICIAL-mako.zip

https://drive.google.com/file/d/0BxYe-w599Fv6cEdZSFlKb1hCcFU/edit?usp=sharing

https://app.box.com/s/lo4wnj9707uxyr7a56px

https://mega.co.nz/#!rUQUWQAA!I20JYEA2Jb986PGsHS8CVU4hnG9c5ZTeVGcFJi6O6sM

http://www.mediafire.com/download/cce91eoy1em1o77/cm-10.1-20131122-UNOFFICIAL-mako.zip

cm-10.1-20131122-UNOFFICIAL-mako.zip.md5sum

https://drive.google.com/file/d/0BxYe-w599Fv6eFhiOTNfak5felE/edit?usp=sharing

https://app.box.com/s/zvlt3s6p1p2e3qbu48tf

https://mega.co.nz/#!XU4xFbzZ!O2i6hmYMioarYhDq8Dy3JXJTVBdge85vzABz6OnKitM

http://www.mediafire.com/view/pd2e1ninkqebfmk/cm-10.1-20131122-UNOFFICIAL-mako.zip.md5sum

Not a full build. I removed "build.prop" from previous.

Changes:

<no changes>
[Nexus 4 Android Development] myzar:
I've audio during calls , everything is working fine but the flickering , i've solved that with this kernell

http://xdaforums.com/showpost.php?p=47721152&postcount=146

Looks like default cm kernel is very buggy atm
[Nexus 4 Android Development] Ajfink:
A commit was JUST pushed out that enables the quick settings pane! Finally. Build:

https://www.dropbox.com/s/vfqu2w72s3e7ney/cm-11-20131122-UNOFFICIAL-mako.zip
[Nexus 4 Android Development] gpvecchi:
I confirm flickering is kernel related, solved using AK. So now just .97 modem has issues? Thanks!
[Nexus 4 Android Development] myzar:
no issues with latest nightly
[Nexus 4 Android Development] gpvecchi:
? Strange, I'm stuck at Google logo with .97 modem...
[Nexus 4 Android Development] dugzino:
Tried this? If yes, read at least a little bit before posting about zombies, human sharks and ****...
[Nexus 4 Android Development] myzar:
are we talking about eris23 nightly ? I havent tested that one, I'm running a build compiled myself one hour ago with the kitkat blobs and 0.97 modem without problems

I'm not sure that today posted build has every change needed, tomorrow build should work for sure
[Nexus 4 Android Development] gpvecchi:
Both eris and Bruce versions. I'm now on AK kernel...
[Nexus 4 Android Development] acultr:
confirmed
[Nexus 4 Android Development] myzar:
This is my personal build http://d-h.st/DC2 , it should boot without problems i'm using it on my phone. The screen will flicker alot use Faux kernel i'm not sure that AK kernel works
[Nexus 4 Android Development] dragonzsoul:
I searched the thread, but didn't find any info on this. Is PIE controls on CM11? I know CM10 builds have it. Thanks!
[Nexus 4 Android Development] zagzag99:
Not yet
[Nexus 4 Android Development] jawz101:
[MENTION=286165]eris23[/MENTION] are you using the latest binaries in the kk rom? Reason I ask is they're now in themuppets repo as of 2 days ago
[Nexus 4 Android Development] eris23:
When I set up the 4.4 build environment I created a ".repo/local_manifests/local_manifest.xml" (after reading http://xdaforums.com/showthread.php?t=2515305 or an equivalent) with the following:

<?xml version="1.0" encoding="UTF-8"?>

<manifest>

<project name="TheMuppets/proprietary_vendor_lge.git" path="vendor/lge" remote="github" revision="cm-10.2"/>

</manifest>

So, I think my builds have whatever proprietary blobs TheMuppets have.
[Nexus 4 Android Development] Ajfink:
I've been using revision="cm-11.0" and it's worked fine.
[Nexus 4 Android Development] myzar:
You are using the olds i just checked , you have adreno200 blobs in the egl folder the new are named simply adreno without the 200 part , that's why it doesn't boot at all with the new radio
[Nexus 4 Android Development] eris23:
I'll change that right away.

Changed.

The "mako" entry at https://github.com/TheMuppets/proprietary_vendor_lge still maps to https://github.com/TheMuppets/proprietary_vendor_lge/tree/cm-10.2/mako (notice the cm-10.2).

https://github.com/TheMuppets/proprietary_vendor_lge/tree/cm-10.2/mako/proprietary/vendor/firmware still shows only JWR66V and 4.2.2 updates.

https://github.com/TheMuppets/proprietary_vendor_lge/pulls shows a KRT16S related pull request (https://github.com/TheMuppets/proprietary_vendor_lge/pull/24). With luck it will be merged soon.
[Nexus 4 Android Development] Smallsmx3:
Ok so do we have in call audio working? And what about the screen flickering
[Nexus 4 Android Development] gpvecchi:
Downloading now for testing, thanks! I tried Faux, but I got bad colors because of CAF... Which version, please?
[Nexus 4 Android Development] Smallsmx3:
Well [MENTION=4046170]myzar[/MENTION] for some reason your build is the only one that has in call audio working on recent builds. For me anyway. Still has weird flickering going on though
[Nexus 4 Android Development] myzar:
this one http://xdaforums.com/showpost.php?p=47721152&postcount=146
[Nexus 4 Android Development] shotta35:
I wont say I know GIT but I just changed the branch to CM-11 and here:

https://github.com/TheMuppets/proprietary_vendor_lge/tree/cm-11.0/mako which were all updated "a day ago"

I just think the 10.2 is the default one (if that's the way it works) as it always loads that one instead of CM-11.

YOu could prolly specify that specific tree and go from there.
[Nexus 4 Android Development] Smallsmx3:
No idea what any of that means
[Nexus 4 Android Development] gorilla p:
I think for best results with these CM11 nightlies...

Use latest PA Gapps

Use latest AK CM kernel

Use 27(or)33/84 hybrid radio via AIO LTE enabler v2 zip

Use trickster to customize kernel
[Nexus 4 Android Development] eris23:
I've updated my local manifest with revision="cm-11.0" from themuppets repository. I ran a "make clobber", so the next build will be a "full build". Tell me if I still have the old blobs in tonight's rom. If they are I'll re-init a fresh build directory for cm-11.
[Nexus 4 Android Development] gorilla p:
Hybrid radio and AK kernel will have to be reflashed after each update because rom overwrites with cm kernel and 97 radio
[Nexus 4 Android Development] Smallsmx3:
Using bruces odexed most recent and everything is amazing
[Nexus 4 Android Development] ciano865:
Short test with CM11 Nov 22 with full PA GAPPS works fine, delvick enabled, default radio and kernel.

Back to 10.2 because home shortcuts not available yet.

Tapatalked with Nexus 4
[Nexus 4 Android Development] elgar:
This thread has way too much of information. It's this only for developers? Couldn't find anything useful that I understood about the 4.4 Rom. Please make this thread user-friendly.
[Nexus 4 Android Development] eris23:
As it stands now, CyanogenMod's KitKat builds are less polished than their JellyBean builds. They have yet to release an official build. This being the case, discussion is bound to be occasionally technical. Their are non-CyanogenMod threads for KitKat on the Nexus 4 such as http://xdaforums.com/showthread.php?t=2486641.

And of course: http://xdaforums.com/showthread.php?t=2527705
[Nexus 4 Android Development] eris23:
I'm sticking to cm-10.2 until Trebuchet, cLock (and the Magic Smoke live wallpaper) are working.