• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[ROM][M7][KK][4.4.4] CyanogenMod 11 Official Nightly Builds

Search This thread

tiny4579

Inactive Recognized Developer
Jan 15, 2011
9,328
5,060
Welcome to the CyanogenMod11 HTC One M7/GSM ROM Thread :)

Flash the ROM at your own risk. Neither the Developers nor XDA assume the guarantee
in case of data loss or damage to the Device! Note the warranty provisions of the Manufacturer.


Credits: CyanogenMod team and their developers/contributors for their work. Without them this ROM would not exist.
PA ( TKruzze ) for the GApps as well.
Many thanks to XDA for this great forum.



The device must be unlocked and using a custom recovery (TWRP or CWM are the most common).
You need a ROM update.zip and optional Gapps. Links to Gapps and ROM zips are found here.
First take a nandroid backup of your existing system.
The first time you flash the ROM or switch from another ROM base (e.g. AOKP, Omni, Sense, AOSPA),
do a full wipe via recovery and flash the ROM and optionally the GApps (if you want Play Store and other Google apps).
Reboot to System. The first boot will take a while as it generates the dalvik cache (dexopting)


RECOVERY:

IMPORTANT!

A recovery update beginning with the Nightly ROM 20140501 will be required!
Guidance & Instructions can be found here
The easiest way to flash recovery is to use Flashify from the Play Store



Recovery Downloads:

TWRP 2.7.1.2

CWM Touch 6.0.4.8


ROM & GAPPS Downloads:

Read this before you flash a Milestone Build!

ROM Download

GAPPS ART suitable – Get one from the 4.4.4 Package


Changelogs:

CM11 Changelog

Android 4.4.3

Android 4.4.4


Further Information:

Exclusively M7 fixes/updates

Information about CM-Builds

CyanogenMod HomePage


Nightly regressions (bugs introduced in a new nightly but not present before) can be reported in JIRA.
Further information is found at the JIRA site: https://jira.cyanogenmod.org/browse/NIGHTLIES



Theme & Kernel Section


***Full Themes***

Themes will be integrated under:
- Settings
- Designs
Get the Cyanogen Theme Showcase App

Herathon Full Theme Android L Style

Themes Designed for the NEW Theme Engine look at #3


***Change single Icon / Change/Remove AppName***

Desktop Visualizer

***Keyboard Themes***
Please follow the instructions from the threads


Themed (New) Google Keyboards by Shaftamle
- Very good Autocorrect and word prediction with many color choices

Xperia Z1 Keyboard by gianton
- Very good Autocorrect and word prediction
- Return Key under Hangouts

***Kernel Collection***
Please note the instructions and notes in the Kernel Thread!

AOSP][CM][4.4.4]TinyKernel

(look#4) Joey Kernel CM for HTC One / CM/AOSP based ROMs


XDA:DevDB Information
[ROM][M7][KK][4.4.4] CyanogenMod 11 Official Nightly Builds, ROM for the HTC One

Contributors
tiny4579
ROM OS Version: 4.4.x KitKat

Version Information
Status: Testing

Created 2014-07-21
Last Updated 2014-07-20
 

Attachments

  • CM11.jpg
    CM11.jpg
    121 KB · Views: 107,418
  • Logo.jpg
    Logo.jpg
    130.5 KB · Views: 103,795
  • config1.png
    config1.png
    85.1 KB · Views: 25,801
  • config2.png
    config2.png
    101.3 KB · Views: 26,000
  • config3.png
    config3.png
    94.2 KB · Views: 24,954
Last edited by a moderator:

tiny4579

Inactive Recognized Developer
Jan 15, 2011
9,328
5,060
Heinz, are you going to be the new maintainer?

I believe @intervigil technically is as I was just posting on the CM10.2 thread.

Since we have a CM11 thread now, I wanted to ask if anyone is having Bluetooth crash when connecting to MAP/phone audio with a car handsfree system for instance. It pairs fine the first time but after connecting again, BT will force close repeatedly unless the phone audio profile is disabled. I wonder if it's due to CM using their own Bluedroid from qcom and it conflicting with the MAP that Google added in 4.4.
 

KaZo58

Senior Member
Nov 13, 2009
247
97
Germany
Xiaomi Mi 11
I believe @intervigil technically is as I was just posting on the CM10.2 thread.

Since we have a CM11 thread now, I wanted to ask if anyone is having Bluetooth crash when connecting to MAP/phone audio with a car handsfree system for instance. It pairs fine the first time but after connecting again, BT will force close repeatedly unless the phone audio profile is disabled. I wonder if it's due to CM using their own Bluedroid from qcom and it conflicting with the MAP that Google added in 4.4.

can confirm this issue too.

Gesendet von meinem One mit Tapatalk
 
  • Like
Reactions: Sonic7

Nick281051

Senior Member
May 5, 2010
4,803
1,365
Northport, NY
Not trying to be rude but if you are not the official maintainer for cyanogenmod then you should not be starting a thread about it, at least in either of the development sections. For now I'd say having one in the general section would be better. That's my opinion though, moderators can do whatever they think is best though

Sent from my HTC One using Tapatalk
 
  • Like
Reactions: Mildan and yankele

cschmitt

Senior Member
Feb 24, 2012
1,716
1,914
Not trying to be rude but if you are not the official maintainer for cyanogenmod then you should not be starting a thread about it, at least in either of the development sections. For now I'd say having one in the general section would be better. That's my opinion though, moderators can do whatever they think is best though

Basically there is no maintainer, as evidenced by the 'official' thread's subject still referencing 4.3.0 and no maintainer activity in that thread for months.

So we created a separate thread to track current cm11 4.4.2 issues.
 

Nick281051

Senior Member
May 5, 2010
4,803
1,365
Northport, NY
Basically there is no maintainer, as evidenced by the 'official' thread's subject still referencing 4.3.0 and no maintainer activity in that thread for months.

So we created a separate thread to track current cm11 4.4.2 issues.

I do understand that but Heinz isn't actually doing any development, that's the only reason I said it.

Sent from my HTC One using Tapatalk
 

David111jr

Senior Member
Feb 5, 2011
485
63
Hows the camera? And does this use Google experiance launcher?

Sent from my HTC One using XDA Premium 4 mobile app
 

tiny4579

Inactive Recognized Developer
Jan 15, 2011
9,328
5,060
hi guys, any major bugs related to this rom?

also any idea if it is possible to use SENSE 5.5 camera on this one?
not for the effects, but quality.

This thread doesn't really list known issues since it's not truly an official thread. There are nightlies so its always changing. Please check this and other threads for known issues.

No to the sense 5 camera.

Sent from my HTC One using Tapatalk
 

Top Liked Posts

  • There are no posts matching your filters.
  • 10
    While I like the new interface, this is still garbage as long as something as basic as speaker phone remains so inexplicabley broken... People I'm speaking to over speaker phone are still complaining it sounds like I'm in a wind tunnel. Pretty impressive how this issue continues to be unadressed.

    Wake me up at the next stop. I'll be on a working sense Rom...

    Sent from my HTC One using Tapatalk 2

    Frankly if that's the attitude you have about Android development you should stay on stock because there's always the chance for something to break. Especially when you're talking Cyanogenmod nightlies. So take your bad attitude elsewhere it will not be missed.

    Sent from my One using Tapatalk
    9
    Everyone:

    Starting tomorrow the m7ul, m7tmo, m7att builds will no longer be updated. They are now (finally) commonized to "m7". Please keep that in mind going forward.

    Thanks,
    -h8rift
    8
    Have just submitted my first patch. I have found little mistake in our amp code that made left channel not being played at all. Instead we had right channel played through two speakers.
    http://review.cyanogenmod.org/#/c/57093/
    Hope it will be merged :)
    8
    I'm thinking the microphone issue people are experiencing seems to be subjective, or I have a very high tolerance for bad quality audio.

    I have not heard anything about the haptic feedback. What issue is this?

    Proximity sensor performance seems to vary from device to device. Some people have reported that the sensor is basically non-functional, others have reported no issues.

    I have not heard anything about memory management.

    I'm not sure what you mean when you say CyanogenMod should have enough respect, but for me personally, I simply do not frequent XDA, nor do I plan to do so more than perhaps once or twice a month.
    You can file bug reports using JIRA (but only against stable and M builds), however those are also taken care of on an ad-hoc basis, subject to maintainer schedule.
    Easiest way to get into actual contact with people is to use IRC.
    Try the #cm-htc, or the main #cyanogenmod or #cyanogenmod-dev channels.

    The speakerphone mic issue is subjective in the sense that people who rely on speakerphone say it's broken and those of us (like me) who rarely use it, except to listen to voice mail, say it works fine. My testing shows that only the rear microphone is used for speakerphone, so depending on how you hold the phone it's easy to cover the mic in a way that it doesn't pickup correctly and the remote party cannot hear you. It's flaky, at best.

    Proximity sensor work fine on my device (screen goes off with my hand about 2" from the sensor), by I remember a bunch of tweaking on 10.2 because the correct values vary among devices and their sensitivity.

    Haptic feedback does occasionally stutter since the switch to msm8960 kernel. I only have it enabled for hardware keys, but those that have it enabled for keyboard use notice the stutter more frequently.

    Also, since msm8960 kernel the notification LED sometimes get stuck on solid amber vs flashing, unlocking the device gets it flashing again.

    As for support, until M5 the stable builds were based on m7 kernel, so it wasn't possible to report these msm8960 bugs on JIRA.

    Also, I'd say that it would make sense to frequent XDA more often if you are a device maintainer because 99% of the casual CM users are going to come to these forums to report bugs and resolve issues, most will never open a bug on JIRA or hop on the IRC channel.

    I agree with @sabret00the regarding the development model for CM, it has worked in the past but there's much room for improvement if CM wants to make a move to a widely used product. A wide tester base that includes many casual users is key, so there needs to be a (user friendly) mechanism for those users to report issues on incremental builds. Maybe that means abandoning nightlies for weekly builds that are more stable and feature targeted so that users can report issues.

    Maybe an app built into CM to report issues directly from the device, uploading logcat and last_kmsg and other state that's helpful to debugging the issues.

    We do appreciate the work you and other's have put into CM on m7 to bring it to this point, but I'm sure you can see the frustration that exists from long standing issues which are known to the user base but the maintainers aren't aware of or have the appearance of being ignored.
    6
    Not just on the latest, but on every nightly so far, especially if you try setting a lower Max frequency.

    Yup, I'm working on a fix. Hopefully will commit in the next couple days.