[ROM] CyanogenMod 11.0 | Android 4.4.4 KitKat | [Developer-Nightlys]

Search This thread

andacro

Senior Member
Its compatible, your using an xposed apk that doesn't work on it.

Wrote in post #3516 that I had found a working version. Wrote also that the IR blaster didn't work, but was flabbergasted yesterday when I tried a different app. Doesn't work with IR Remote, but works with irplus. It's powerful too. Before it could be a bit troublesome to turn on the telly, but now it works perfectly from a longer distance too!

I'm pretty sure this ROM will stay on my phone until I have to buy a new one. :)
 
Last edited:

yohan4ws

Senior Member
Oct 23, 2012
532
183
Calgary
That's an interesting reason, as cm13 is considerably faster and smoother than cm11..
Just like Windows 10 blows Windows 7 away with speed and smoothness, no matter what you think of the new start menu.

I have to agree with @andacro , Windows 7 rules over Windows 10 (this coming from a Network Admin). Win10 has bugs as its still early development, and makes it way more cumbersome accessing some of the control panel and system config area's. Try doing remote support with a bunch of useless flash animations in the 3/4 of the page start menu now and you'll be quickly turned off ...... back to on topic

CM11 over CM13 , one simple pull down in the notification area to see everything instead of pulling down twice
CM13 thread has been littered with issues at nearly every nightly (especially bluetooth) I choose CM11 because it just works. Also I believe the reason I built the new version was Xposed wasn't working, which I did get working on my CM11 build. There were some other items in CM12 that I didn't love either like the transparent status bar and dorky preschool color themes ...

No right and wrong here, just preferences.

I just installed MM xXx No Limit Rom as I prefer the keyboard from Samsung's TW so we'll see how this goes... if I can't get it customized similarly (the gaudy blue/green quick toggles has always strayed me from TW) I will try CM12 before 13 until BT gets sorted.
 
  • Like
Reactions: andacro

andacro

Senior Member
Just fast before sleep, I have to mention that I love the "Aeroplane mode" :)

notification_zpsw4mtdjkk.jpg
 
Last edited:

hhello916

Senior Member
Jun 12, 2016
176
19
Gurgaon
Well then, I guess your only other option then is to follow the tutorial I also linked and build your own.... ("that guy using the w8" is me, by the way. )

The tree for KLTE was updated to 12, and then to 13 .. no one is maintaining the CM 11 tree or roms, but by using the tutorial you get all the CM11 updates and google security patches etc. It really wasn't that difficult to build an updated CM11 ...

My batter will last over 36 hours on light use BTW so not sure what the deal is with yours ..
Will this rom work on g900h.?
If not, can u provide me with a link of rom that is best for my stupid s5 exynos...:crying:
 

icenight89

Senior Member
Dec 18, 2010
2,727
778
Ok, so this in an update for all those too lazy to read a few pages back. Yohan4ws posted this:

http://forum.xda-developers.com/showpost.php?p=66309743&postcount=3504

Which is an up to date build of cm11 4.4.4. Both stock/aosp 5.1.1 LP and 6.0.1 MM were plagued with issues for me. Running alot of apps on a phone with 1.75 GB RAM presents multiple issues. CM11 with dalvik seems to run smoothly, while still being up to date enough to run all current apps. Security updates are present til April, so that isn't an issue either. Sometimes the latest and greatest OS isn't always that, especially given your hardware. A reminder the S5 made me painfully aware of.

For google apps and play store I used openapps pico, and it worked flawlessly (platform arm, version 4.4)

http://opengapps.org

Only issue I experienced was that the stock CM11 governor and hotplug use alot of battery by default. I strongly recommend the boeffla kernel and accompanying app:

http://kernel.boeffla.de/bcv2

http://kernel.boeffla.de/sgs5/boeff...le/boeffla-kernel-1.3-CM11-g900f.recovery.zip

Viper4android is also available and functional on CM11 (I needed to use viper fix 1.1 to get it fully functional however), as well as xposed.

http://www.mediafire.com/download/ar5men9o5ar7inb/ViPER4Android_FX_v2401_A4.x-A6.x.apk

http://forum.xda-developers.com/showpost.php?p=61858278

http://forum.xda-developers.com/xposed/xposed-android-4-4-4-t3249895

For those camera and picture aficionados, I found the stock cyanogenmod camera to be severely lacking. To save others much time, I'm posting what I found to be the best camera alternative by far. HDR mode enhancements, high res support and others. I challenge anyone to find a better camera mod that supports cm11. I simply downloaded and installed the apk.

http://forum.xda-developers.com/oneplus-one/themes-apps/app-cameranext-modded-t2999275

Also, to enhance and ensure compatibility, I highly recommend on first boot and install you disable cm's built in root. Download SuperSU and reboot into recovery and install it.

https://download.chainfire.eu/696/supersu

All in all we get full functionality with a slightly older, more reliable base.


****BONUS****
If you want a more current feel, download and install one of these themes for a 5.1.1/6.0 experience

http://bit.ly/1GtSUru
 
Last edited:
  • Like
Reactions: yohan4ws

xAD3r1ty

Senior Member
Jun 24, 2013
384
95
Ok, so this in an update for all those too lazy to read a few pages back. Yohan4ws posted this:

http://forum.xda-developers.com/showpost.php?p=66309743&postcount=3504

Which is an up to date build of cm11 4.4.4. Both stock/aosp 5.1.1 LP and 6.0.1 MM were plagued with issues for me. Running alot of apps on a phone with 1.75 GB RAM presents multiple issues. CM11 with dalvik seems to run smoothly, while still being up to date enough to run all current apps. Security updates are present til April, so that isn't an issue either. Sometimes the latest and greatest OS isn't always that, especially given your hardware. A reminder the S5 made me painfully aware of.

For google apps and play store I used openapps pico, and it worked flawlessly (platform arm, version 4.4)

http://opengapps.org

Only issue I experienced was that the stock CM11 governor and hotplug use alot of battery by default. I strongly recommend the boeffla kernel and accompanying app:

http://kernel.boeffla.de/bcv2

http://kernel.boeffla.de/sgs5/boeff...le/boeffla-kernel-1.3-CM11-g900f.recovery.zip

Viper4android is also available and functional on CM11 (I needed to use viper fix 1.1 to get it fully functional however), as well as xposed.

http://www.mediafire.com/download/ar5men9o5ar7inb/ViPER4Android_FX_v2401_A4.x-A6.x.apk

http://forum.xda-developers.com/showpost.php?p=61858278

http://forum.xda-developers.com/xposed/xposed-android-4-4-4-t3249895

For those camera and picture aficionados, I found the stock cyanogenmod camera to be severely lacking. To save others much time, I'm posting what I found to be the best camera alternative by far. HDR mode enhancements, high res support and others. I challenge anyone to find a better camera mod that supports cm11. I simply downloaded and installed the apk.

http://forum.xda-developers.com/oneplus-one/themes-apps/app-cameranext-modded-t2999275

Also, to enhance and ensure compatibility, I highly recommend on first boot and install you disable cm's built in root. Download SuperSU and reboot into recovery and install it.

https://download.chainfire.eu/696/supersu

All in all we get full functionality with a slightly older, more reliable base.


****BONUS****
If you want a more current feel, download and install one of these themes for a 5.1.1/6.0 experience

http://bit.ly/1GtSUru

i lose audio in my g900f after flashing the camera, is there a fix?
 

icenight89

Senior Member
Dec 18, 2010
2,727
778
i lose audio in my g900f after flashing the camera, is there a fix?

If you noticed in the post, I mentioned I only downloaded and installed the apk. Flashing the camera replaces shared libs in the system partition. That flash is for the One+, which doesn't have identical hardware to our device.

Sadly, you may have to either restore a backup or reflash cm11
 

xAD3r1ty

Senior Member
Jun 24, 2013
384
95
If you noticed in the post, I mentioned I only downloaded and installed the apk. Flashing the camera replaces shared libs in the system partition. That flash is for the One+, which doesn't have identical hardware to our device.

Sadly, you may have to either restore a backup or reflash cm11

Yep i did try it after and indeed it works, i can definitely tell cm11 is faster than 13, but 13 is just more stable atm and with more features that we didn't have back in the cm11 era, so yeah
 

icenight89

Senior Member
Dec 18, 2010
2,727
778
Yep i did try it after and indeed it works, i can definitely tell cm11 is faster than 13, but 13 is just more stable atm and with more features that we didn't have back in the cm11 era, so yeah

More stable? I mean ya, opinions are subjective but CM13 isn't stable. It has many bugs and issues still to be ironed out. True stability to me points to something that out of the box just works. This CM11 build on the other hand doesn't randomly reboot, has no flashlight or her issues. And Bluetooth works flawlessly (granted they recently patched this).

As for the feature set, I'd disagree. I'd challenge you to point out a feature on CM13 I don't already have on 11 through a third party app or mod.

CM13 is where I'll eventually shift, but not before it's ready
 

xAD3r1ty

Senior Member
Jun 24, 2013
384
95
More stable? I mean ya, opinions are subjective but CM13 isn't stable. It has many bugs and issues still to be ironed out. True stability to me points to something that out of the box just works. This CM11 build on the other hand doesn't randomly reboot, has no flashlight or her issues. And Bluetooth works flawlessly (granted they recently patched this).

As for the feature set, I'd disagree. I'd challenge you to point out a feature on CM13 I don't already have on 11 through a third party app or mod.

CM13 is where I'll eventually shift, but not before it's ready

Actually yes i find it more stable, i'm not sure if you have the G900F? i never had random reboots with Cm13, it's pretty much really stable, I never cared about bluetooth (its fixed now anyways) and there's a simple app for flashlight, other than that i really can't say cm11 is better, it even has fingerprint support, custom kernels work nicely, Since yesterday i've had 3 random reboots in cm11, no xposed, only viper and boeffla kernel from your post, and there are times where it just slows down, i don't know, maybe its the kernel, can't tell, but i can understand you prefer cm11 over 13
 

icenight89

Senior Member
Dec 18, 2010
2,727
778
Actually yes i find it more stable, i'm not sure if you have the G900F? i never had random reboots with Cm13, it's pretty much really stable, I never cared about bluetooth (its fixed now anyways) and there's a simple app for flashlight, other than that i really can't say cm11 is better, it even has fingerprint support, custom kernels work nicely, Since yesterday i've had 3 random reboots in cm11, no xposed, only viper and boeffla kernel from your post, and there are times where it just slows down, i don't know, maybe its the kernel, can't tell, but i can understand you prefer cm11 over 13

I have a G900w8, but they're pretty much identical. I'm guessing it's some user configuration you did. Most likely with boeffla, I left it with interactive governor and row/cfq schedulers. You may also have over clocked or undercoated. This cm build has been rock solid for me since install. I have in excess of 180+ apps, and no issues whatsoever. In fact. It's the only ROM that still let's my phone run decent
 

icenight89

Senior Member
Dec 18, 2010
2,727
778
I prefer the old way of handling external storage in 5.1.1 and previous, MM plays too much to a locked down internal storage model, similar to iPhone.

With CM11 and Xposed + XInternalSD, I can move my 4gb whatsapp folder to external. On a phone with 11.5 GB internal, this is essential. I also store/organize my media in a very nonstandard format, and 4.4.4 plays nice for that.

Ultimately its choice. Ill be on cm11 at least for another month or two, until cm13 is stable to my standards, or a new phone. Whatever comes first. Ive been strongly eyeing the ZTE Axon 7.
 

andacro

Senior Member
I prefer the old way of handling external storage in 5.1.1 and previous, MM plays too much to a locked down internal storage model, similar to iPhone.

With CM11 and Xposed + XInternalSD, I can move my 4gb whatsapp folder to external. On a phone with 11.5 GB internal, this is essential. I also store/organize my media in a very nonstandard format, and 4.4.4 plays nice for that.

Ultimately its choice. Ill be on cm11 at least for another month or two, until cm13 is stable to my standards, or a new phone. Whatever comes first. Ive been strongly eyeing the ZTE Axon 7.

I agree! Old way is much better, but apps have updated to work with the new way now, so there isn't much problem anymore. 4.4.4 is great, but as apps get updated... Backward compatibility is a problem in Android I guess.

ZTE Axon 7 looks like an awesome phone! Not available in my country. Only the Axon Elite. Enjoy it if you get it!
 

icenight89

Senior Member
Dec 18, 2010
2,727
778
I agree! Old way is much better, but apps have updated to work with the new way now, so there isn't much problem anymore. 4.4.4 is great, but as apps get updated... Backward compatibility is a problem in Android I guess.

ZTE Axon 7 looks like an awesome phone! Not available in my country. Only the Axon Elite. Enjoy it if you get it!

It has both a European and US model, between the two any bands in your country should be supported.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 102
    brand_reveal_1.jpg


    DO NOT REPORT BUGS UNLESS YOU HAVE DONE A FULL WIPE, INSTALLED THE GAPPS PROVIDED IN THE 2ND POST, AND ARE RUNNING STOCK KERNEL WITHOUT STUPID MODS OR YOUR BUG REPORT WILL BE IGNORED PERIOD.

    These are UNOFFICIAL/DEVELOPER builds of CM11 with test fixes for bugs in this thread that will eventually be merged into CM nightlys for klte (GSM), klteusc, kltedv, and kltevzw devices and by NO means this is my ROM. I am just compiling from
    CM Source and 100% credits goes to TeamDouche, and all other coders who contributed to CyanogenMod.


    For which devices, should work with all klte versions that are qualcomm

    Included in the Unified GSM build
    kltexx,kltelra,kltetmo,kltecan,klteatt,klteub,klteacg,kltedcm,klte

    Individual CDMA builds kltevzw,klteusc,kltespr

    Individual GSM builds kltedv

    If your device isn't listed in the "individual" lists then flash the generic "klte" build

    Code:
    [B]IMPORTANT[/B]
    
    * Do NOT expect daily builds. I'll build when I'm free.
    * Do NOT ask for support for flashing in this thread.
    * Do NOT use this unofficial build and ask for support at the official threads.
    * Do NOT be rude.
    * Respect all users
    * If I see a NOOB question and I don't feel like replying, I WONT.


    I personally am not fond of these kinds of threads, If it turns into my last one I WILL LEAVE and close the thread. We have started some momentum here. Let's keep it rolling :).


    c4ypvbf.png

    • Built from CM source
    • Service
    • Text
    • Data
    • Call
    • Audio
    • WiFi
    • Google Now
    • Bluetooth
    • GPS
    • MMS
    • Video playback
    • Audio playback
    • Internal/External SDcard mounting
    • Camera
    • Video recording
    • IR Blaster
    • NFC

    bJO9QqG.png

    • Touchscreen in some games....
    • General CM bug: newest instagram update results in black pics...Rollback the update to fix...Then email FB and tell them to fix their apps :p

    2jpqfKR.png

    • Do NOT use superwipes
    • Wipe data, cache, and dalvik cache
      ** (if you are simply applying an update to this rom base this might not always be required)
      *** ((but do not report bugs if you didn't full wipe))
    • Flash ROM
    • Flash GAPPS (in 2nd post) (No other gapps packages are officially supported!)
    • Reboot
    • ???
    • Profit
    To enable Developer Options and Performance go to Settings, About Phone and repeatedly press Build Number.
    If you use ADB read this: PSA by CM
    If you use reboot to recovery read this: PSA by CM
    Regarding new Superuser: PSA by CM
    Read the FAQ thread here before posting any questions in this thread: FAQ



    w5xnyz0.png

    • And any and all users in this thread who contirbuted or will contribute to making this ROM as stable as possible
    • Garwynn XDA
    • Tom Marshal (tdm)
    • Ethen Chen (intervigilium)
    • ktoonsez
    • Esa Laukkanen aka elelinux
    • Cyanogen Inc & Team-Kang
    • MrTrip
    • albinoman887

    cvU6373.png


    so here is a donation link if you want to buy me a coffee or pack of smokes (I go through a lot sitting on the PC messing around lol) go ahead. But not required or expected by any means :)

    Note: The name on the paypal account may say patricia, this is because it's a family paypal account. :)



    Thanks and happy flashing!

    DOWNLOAD LINK + CHANGELOG in 3nd post

    XDA:DevDB Information
    [ROM] CyanogenMod 11.0 | Android 4.4.4 KitKat, ROM for the Samsung Galaxy S 5

    Contributors
    albinoman887, ktoonsez
    ROM OS Version: 4.4.x KitKat
    ROM Kernel: Linux 3.4.x

    Version Information
    Status: Beta

    Created 2014-09-01
    Last Updated 2014-10-16
    64
    Reserved

    do not report bugs unless you have done a full wipe, installed the gapps provided in the 2nd post, and are running stock kernel without stupid mods or your bug report will be ignored period.

    BUG REPORT TEMPLATE, IF YOU WANT A RESPONSE FOLLOW THIS!!!

    Device:: T-Mobile G900T kltetmo
    Baseband: ENTER_VERSION_HERE
    Bootloader: ENTER_VERSION_HERE
    EFS: ENTER_VERSION_HERE
    ROM Ver: ENTER_VERSION_HERE
    Description: Wiped, flashed 9/8 build, correct Gapps loaded. Everything loaded fine.

    BEFORE YOU POST....WORDS FROM A SMART MAN....

    Hey all, I'd just like to throw this out there for those of you having random bugs.

    This is a development tree. Its not stable or even RC. Its testing. While all the testing and bug reports are appreciated, some of these bugs can be solved with the following troubleshooting steps..

    1. Make sure you have a clean install. This is most important. Dirty flashing can cause issues even from one build to the next days build. Some apks are changed and if you don't do a full clean flash these settings are not refreshed. Please do a clean flash and test this way.

    2. Some issues may arise from using titanium backup to restore apps + data. Unless you absolutely positively need to restore data with these apps I'd advise against it. Albinoman887 had me to a restore of apps without data and things got much smoother.

    3. I can't stress this enough from my own experience, xposed modules can and will break CM11. You might think you are making a minor change but it might be the wrong way to make this change.

    4. Some apps do interfere with each other. Camera crashes can occur when a GPS fix app is running because the camera cannot geo tag a photo and it just crashes the camera. This is one that albinoman887 noticed the other day. THIS MAY NOT ALWAYS BE THE CASE. But its good to check that for yourself.

    5. I know we all want to use our phone for 10 hours constantly no charge and be left with 99% but this simply cannot happen. It would be great if people could just test the rom vanilla and report issues that arise from that. I promise you i have no third party app "saving my battery" and my battery life is great.

    6. When submitting a bug report please always mention your carrier and phone model. It helps to narrow down the issue. This is a unified build so an issue on a Verizon wireless s5 and a us cellular s5 might be different or not exist at all on the other units. This I cannot stress enough. Even if you noted your model before, we don't keep a database of users and their models so we do forget when looking for solutions what model this is broken on.

    Being a part of this is like an open beta. Opt in or out it is your choice but help us, especially Albinoman887, help you by having the information he needs to find and squish these bugs.

    I'm currently helping build a solid bug list with models and information but its hard to maintain when some bugs are because of a dirty flash or a third party app.

    Let's make CM11 on the Galaxy S5 be the best it can be!

    Thank you for your time, support, and any donations given to the developers during this process. Nobody would be here if it wasn't for a good solid team effort. :)

    Sent from my SM-G900R4 using XDA Free mobile app
    40
    sB7atuO.png


    Fixes NOT YET MERGED into OFFICIAL CM branch.
    * UNOFFICIAL kltedv specific builds with fixed NFC

    Old Changelogs

    Sep-27
    * Synced with upstream
    ** The following changes have not been merged into main CM source yet! **
    * Fixed NFC for G900I device
    * Added proximity wake up support
    * Merged a fix from hlte to help with VOIP choppiness

    Sep-24
    * This will be the last build compiled by me since nightlys are turned on.
    * we now are using the stock GSM ril libs....
    * Upstream updates

    Sep-19
    * First release with split up builds....
    * Initial klteusc build
    * initial klte gsm only build
    * GSM: switched to KK HLTE RIL libs so we can use the new custom RIL class
    * CDMA uses all official STOCK KK RIL libs
    * Any and all upstream updates at time of compile
    ** VZW coming soon **

    Sep-14
    * Fixed touchscreen staying on while screen is off
    * Updated vibration strength code (upstream) if dirty flashing and you have changed intensity settings PLEASE RESET TO DEFAULT as the scale has changed
    * HighTouchSensitivity (glove mode) now actually works (tested by checking sysfs entry and using my shirt over my finger)
    * Updated GPS HAL source to caf branch kk_3.5
    * All upstream changes at time of compile

    Sep-10
    * Removed key disabler support because there are kernel side changes I haven't implemented yet.
    * Fixed capacitive keys staying on during a phone call

    Sep-8
    * Did a bit more tweaking to high-gain-stereo recording mic
    * Enabled vibration strength settings (Settings>Sound>Vibration Intensity)
    * Enabled high touch sensitivity (Settings>Language & Input)
    * Enabled key disabler for when switching to nav bar mode but I can't find it in settings. I might be missing a change...
    * Upstream updates

    Sep-6
    * This is mainly a maintenance update. I went back through the source and double and checked and tested reported bugs.
    * Tested phone calls: Dialer works, dialing pad works, no lag when pressing call, called people in and not in my phone book by tapping and by dialing, and people can hear each other. Tested 3 times. from a cold boot. Issues with phone include: capactive keys are still responding when in a call and the screen is off so it is possible to back out of the phone app while on the call and start pressing things with your face
    * Tested touchscreen in Snes9x EX+: Still the same issues. No response from touchscreen
    * Attempted fix for G900I users and NFC but obviously I can't test since I don't have the device.
    * Cherry-picked about 4 coomits from gerrit dealing with audio routing improvements.
    * Synced with upstream

    Sep-5
    * PLEASE ONLY USE THE GAPPS PROVIDED IN THE 2ND POST. NO OTHER GAPPS PACK IS SUPPORTED AND IS KNOWN TO CAUSE ODD ISSUES
    * Reverted back to old ril stack since we weren't using 100% stock libs anyways and it was breaking cdma. Will revisit at a later date
    * Fixed CDMA (obviously)
    * Tried reverting "enable denoise by default" for camera to see if it fixes instagram. Please let me know as I don't use the app
    * Any and all upstream updates at time of compile
    * Working Sprint NC
    * Kernel: merged back ONE change we had in the old bringup branch to see if it fixes audio issue reported by "some" users

    Sep-4
    * Fixed screw up on my part for NFC. Should be working now
    * Added subjective NFC driver loading support so one build can work for sprint and all others (untested on sprint)
    * Corrected partition sizes (ktoonsez)
    * Enable denoise in camera by default
    * Any and all upstream changes at time of compile
    * GSM is now using 98% stock RIL libs.
    ^^ in a nutshell, we were before using all HLTE jellybean RIL libs. If we used ours we would get no data and could not make phone calls. Now with a recent patch to cm we are able to make calls with our ril. what was done was (not by me) digging into the TW framework and finding calls that we don't have. That's what ixed the calling issue. HLTE is now using KK ril blobs due to this fix. They don't have any data issues. we still do unless I swap out libsec-ril.so and then because they tie together also libqmiservices.so to the HLTE KK one (before we were also swapping libril.so to HLTE JB before the patch). Now the reason I think this swap is needed is because of the download booster option in TW. Since AOSP doesn't offer this we most likely need to set something on code that always returns "0" or off for that feature. It will take some digging though. This still gets us a lot closer to stock. there are about 15 files related to the "ril stack" only 2 aren't from our device now. Also I've read through many logs and don't see any regressions from using these two libs

    Sep-2
    * Fixed NFC (won't work on sprint models until I make a special build just for sprint later today)
    * Fixed IR blaster (at least on TMO)
    * Switched to newest libqmiservices.so that can be used with the old GSM ril libs (CDMA is using stock KLTE)
    * Any upstream changes by CM at time of build

    Sep-1
    * Attempted to fix issue some were having with wifi password resetting
    * Now using about 99% stock NG3 libs. Only swapped libs are the rils from hlte as well as an older version of libqmiservices (NE5) to work with the older RIL libs. Rest 100% stock
    * Slowly re-adding some kernel fixes to test battery drain
    * Searching for contacts in dialer works
    * Low recording mic gain fixed (I fixed this i think yesterday or the day before but forgot to mention it)
    ** This wasn't really mentioned and I don't know if Esa has added it but right when CM added sources Ethan re-wrote the audio routing code. So now all audio issues should be fixed and small ones that aren't like above should be easy fixes from here on out
    *** The next changes may or may not have already been in place in the last builds but I want them to be documented ***
    * 100% stock keylayouts
    * 100% stock mixer paths
    * Enabled dock settings
    * GPS should be pretty stable now. We are now using all the correct configurations and libs




    lSuV72q.png


    Team Hydra Github (main): https://github.com/Team-Hydra
    CyanogenMod Github: https://github.com/CyanogenMod



    l5SakBJ.png


    kltedv :KLTEDV Nightlys
    kltespr : KLTESPR Nightlys
    klteusc : KLTEUSC Nightlys
    kltevzw : KLTEVZW Nightlys

    If your specific model isn't listed above and is a CDMA device it is not supported. Otherwise flash the unified GSM build below....

    Unified-GSM : KLTE Nightlys
    ----------------------------------------------------------------------------------------------------------------
    GAPPS: : HERE
    ----------------------------------------------------------------------------------------------------------------
    BUILDBOT MIRROR : DOWNLOAD MIRROR
    29
    dear god i'm gonna regret this tomorrow when i have to read 500 posts but..... :p

    http://d-h.st/u4f

    * All hardware should be working,
    * for GSM only right now
    * Do a full wipe
    * attaching pictures to a hangouts msg or MMS results in a force close of "documents"
    * Gapps are somewhere. i googled gapps android 5.0 i think but they are def around. dont get PA GAPPS if you have the choice. just get regular gapps or the mini modular of pa gapps NEVER the full one
    * when you flash the rom it might say something about userdata partition being busy....dont worry about it
    * Try and keep the posting to a minimum until i open a cm12 thread in the morning
    * There are gonna be plenty of bugs....i mean plenty.....until this latest build flac audio didnt even friggin play because ffmpeg wasnt merged into CM yet. so dont come telling me some random feature is gone or doesnt work. its most likely missing code upstream and me and other devs are well aware of it and are adding it all back...

    good luck and god speed :p

    as always all sources can be found on my github:

    https://github.com/Team-Hydra

    The following repos:
    klte-common
    klte
    msm8974-common
    samsung_qcom-common
    kernel/klte
    24
    new build posted.......and guess what







    I fixed NFC!

    It won't work on sprint models until I do a build for them specifically which I will later today. I've been up all night and need sleep

    heres the full changelog, check the 2nd post for download link :)

    * Fixed NFC (won't work on sprint models until I make a special build just for sprint later today)
    * Fixed IR blaster (at least on TMO)
    * Switched to newest libqmiservices.so that can be used with the old GSM ril libs (CDMA is using stock KLTE)
    * Any upstream changes by CM at time of build