[ROM][4.4.4][AOSP][{Un,}Official] CM11.0 (KitKat)

Search This thread

Bobcus Leper

Senior Member
Feb 6, 2014
2,078
1,257
Moto X4
Moto G Stylus
uh oh!

The phone was running really well for a while, but today it went a bit haywire. When I was turning off the hotspot, it became unresponsive to the touch screen, and was also clicking things on it's own. I was eventually able to reboot, but then fell into a boot loop. It gets through one rotation of the Lineage loading Logo and then freezes and tries to reboot again.

I tried booting into safestrap and wiped the cache and dalvik, as well as installing the rom overtop without doing a data wipe, as has been recommended to others in this thread. But that didn't seem to have any affect.

Do I have any other recourse? Or should I just wipe and reinstall the Rom? Just got things tweaked the way I like it, don't really relish having to go through all the setup again.

Thanks.

Hi,
Try wiping everything but your data and then reflash the ROM.
 
  • Like
Reactions: sd_shadow

SuDoHack

Member
Dec 12, 2012
13
2
Hi,
Try wiping everything but your data and then reflash the ROM.

Thanks for the suggestion. I ended up doing the factory reset wipe, then reflashed and that got me back up and running. This time I made sure to make a safestrap backup.

It seems like I enountered the quirk a few more times that led to the initial crash. A few times, when I was on the lock screen the touchscreen would become unresponsive and then go crazy auto clicking things. Maybe a delay, combined with the wrong rotation or something? In any case the problem only seems to occur when the phone is fully charged and still plugged in. When I'm experiencing the delay, if I unplug, it goes right away.

For now I have disabled the lock screen and the phone continues to work amazingly well on Lineage 11 :good:
 

SuDoHack

Member
Dec 12, 2012
13
2
Wondering if anyone has any tips for getting Caller ID to work properly? I'm pretty certain in my original install of this ROM it was properly displaying the Caller ID of an incoming call. On this fresh install though it doesn't seem to be working. When a call comes in it just says "Pay Phone - Unknown caller". If I click on the message icon to send the unknown caller a text, it goes to the person in the contact list who called. So it does know who called, just seems to be having trouble connecting the dialer with my contacts list. Appreciate any thoughts.

I read someone solved a similar sounding problem relating to the contact list being set to International calling? Not quite sure.

I found the problem it was when you have your contacts using international dial, the phone doesnt associate with your phone contact on recent call or history screen...sorry 4 my bad english. - rblanca - 13th May 2015, 09:49 AM |#1667

Thanks!
 
Last edited:

ltpliers

Member
Oct 22, 2014
9
0
Snapchat doesn't currently work with the camera in CM11/lineageos, is there a fix so that it can record video? Currently using the 20170417 build.
 
Last edited:

aiamuzz

Senior Member
Dec 24, 2011
509
46
No.



Well you're both in luck. I wanted a more functional keyboard ever since I got the D4. I think I posted all about it before. Anyway, I had to do updates to my method since updating to KitKat, and I'm willing to share. Here are my keychar and keylayout files, also in flashable zip form... (also includes a ringtone and notification tone) that I use whenever I update CM.

These might take some getting used to, there are quite a number of changes. I'll try to list them all here.

Caps Lock ---> Shift
Shift ---> Alt

ALT+e = 0x0301 = combining acute accent = turns e to é, o to ó, etc
ALT+i = 0x0302 = combining circumflex accent = turns e to ê, o to ô, etc
ALT+k = [
ALT+l = ]
ALT+SHIFT+K = {
ALT+SHIFT+L = }
ALT+n = 0x0303 = combining tilde = turns n to ñ, o to õ, etc
ALT+o = ~
ALT+p = |
ALT+r = $
ALT+u = 0x0308 = combining diaeresis = turns e to ë, o to ö, etc

ALT+SHIFT+U ... this one is special, it is unicode 0xEF00, but that doesn't really mean anything. But to Android, it will take the previous 4 characters and try to turn them into the unicode character for that. With knowledge of unicode you should be able to type any character you want with it. Lets say you wanted to type the copyright symbol, 0x00A9 ... you'd type "A9" then hit ALT+SHIFT+U and it'd turn into ©

ALT+0 = )
ALT+1 = !
ALT+2 = @
ALT+3 = #
ALT+4 = £
ALT+SHIFT+4 = ¥
ALT+5 = %
ALT+6 = ^
ALT+7 = &
ALT+8 = *
ALT+9 = (

ALT+, = <
ALT+. = >
ALT+/ = \
ALT+SHIFT+/ = |
ALT+' = `

http://2.ben64.com/d4/omap4-keypad.kcm

http://2.ben64.com/d4/omap4-keypad.kl

http://2.ben64.com/d4/kbr.zip

Any questions, please ask.

interesting ... need to try it ...
 
lineage-11-20170417-UNOFFICIAL-maserati.zip: Mediafire (Private Mirror)
Older Builds on Mediafire

Build with Uber Toolchain 4.9

Changes from Upstream:
- New LineageOS Bootanimation
- Can be installed to Safe slot (Info & Source)
- Localized keypad layouts based on AsantiKeypad from XT897 (Source)
- April security patch commits included.

Changes from March build:
- Keypad layouts renamed from Asanti to Maserati

If you are on GSM Network, you still need the GSM Patch.
If you want to use Xposed, you need to flash this fix and use this Xposed Installer.
If you have problems with Swype in AOSP Keyboard flash this fix after Gapps. (Usually happens if you use gapps newer than 2014, should also help if you don't use any gapps)

Thanks ^-^



I forked both device trees on github: maserati and omap4-common.
To change bootanimation, just replace /vendor/cm/prebuilt/common/bootanimation/480.zip with bootanimation.zip from my build or generate it by yourself using this script based on android_vendor_cm.
To find and include latest commits, take a look on review.lineageos.org

This is probably the best daily driver 4.4 ROM for the droid4 and should have its own thread for visibility.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 51
    CM11.0 (KitKat) unofficial builds for the Droid 4

    I'm now pushing my changes directly to CM, so nearly everyone can just use the official nightlies (except if you are still using BMM).

    CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4 (KitKat), which is designed to increase performance and reliability over stock Android for your device.

    Code:
    #include <std_disclaimer.h>
    /*
     * 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 any of us for messing up your device, we will laugh at you.
     * Collectively, and at the same time.
     */

    CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review.

    These are WIP builds of porting CM11.0 to the Droid 4 (and probably also other devices using the same device/motorola/omap4-common-infrastructure). They probably won't work, so don't expect too much. Use on your own risk!

    Builds:
    Final official build (XNG3C):
    http://download.cyanogenmod.org/ maserati spyder targa umts_spyder

    Current manual builds:
    http://droid.cs.fau.de/cm-11.0/unofficial/

    Official builds (for everyone not using BMM):
    http://download.cyanogenmod.org/?device=maserati

    Obsolete automatic nightly builds:
    http://droid.cs.fau.de/cm-11.0/maserati/

    Obsolete old/manual builds:
    http://bork.cs.fau.de/~michael/d4/cm11/

    Changes:
    • 2016-01-04:
    • 2015-11-15:
    • 2015-09-01:
    • 2015-06-26:
    • 2015-05-22:
    • 2015-04-26:
    • 2015-04-12:
    • 2015-04-05:
    • 2015-03-29:
    • 2015-03-2{7,8}:
    • 2014-02-21:
      • Switch to CM kernel, all relevant kernel-patches are now upstream
      • Added fixes for audio, usb and modem
    • 2014-02-18:
      • Add wakelocks to ALS/proximity-sensor to prevent I2C-stalls
    • 2014-02-04:
      • Enable camera-sensor calibration
    • 2014-01-26:
      • Fix permissions for sdcard0, fixes apps on sd-card
    • 2014-01-25:
      • Increased suspend-delay in USB-host, next try to fix the suspend_wakelock
    • 2014-01-24:
      • Re-add MDM6600 reset on boot, might fix signal-loss issues. Users with a SIM PIN get a PIN-dialog after flashing the GSM patch.
    • 2014-01-22:
      • Fixed wireless driver writing to foreign kernel memory
    • 2014-01-21:
      • Fixed permissions of the DRM device-files, enable playback of secure content
    • 2014-01-19:
      • Apply omapzoom-fix for the st_wake_lock and remove my hack. This improves powersaving on some devices, where UART4 would not get disabled
    • 2014-01-17:
      • Reverted a motorola-workaround for an USB bug as the upstream omapzoom-fix is already applied and seems to be more correct. Probably fixes suspend_backoff wakelock
      • Completely switch back to ti wpa_supplicant
      • Fix permissions of battd-files, now battd can even read and write its calibration information
    • 2014-01-16:
      • Added a possible fix for the display not always waking up
    • 2014-01-13:
      • More camera fixes. HD recording (and the camera itself) should be stable now.
    • 2014-01-11:
      • Updated domx and kernel rpmsg-interface. This fixed many camera problems (hangs/mediaserver crashes). Additionally it makes focal usable now
    • 2014-01-10:
      • Enabled HD video recording. If the camera app crashes after taking a video, just reopen it (sometimes twice), this will be fixed in a future update.
    • 2014-01-06:
      • Enabled KSM
    • 2014-01-02:
      • More fixes for USB-problems (suspend related)
    • 2013-12-30:
      • Merge upstream changes (enables BLE)
    • 2013-12-25:
      • More camera tweaks
    • 2013-12-24:
      • Workaround for CM now depending on QCOM camera and crashing with everything else
      • Emit set_perms in updater-script again
      • Don't mount / as ro, fixes sd-cards again
    • 2013-12-23:
      • More fixes for USB-erratas
      • 5s timeout for the st_wake_lock
    • 2013-12-22:
      • Cherry-picked fixes for USB-erratas on omap4430 (suspend/resume)
    • 2013-12-18:
      • set_perms-hack removed
    • 2013-12-17:
      • Don't hold st_wakelock until BT/GPS is used for the first time
      • Some power-management fixes cherry-picked from omapzoom
    • 2013-12-14:
      • set CMUpdater-URL to own backend
    • 2013-12-13:
      • Torch-tile (Quick Settings) fixed
    • 2013-12-11:
      • Use hostapd from wpa_supplicant_8_ti and wpa_supplicant from wpa_supplicant_8 (fixes WiFi-tether)
      • 3G fixed by setting the data registration-state
    • 2013-12-07:
      • Update to Android 4.4.1
    • 2013-12-05:
      • Just a build with the latest CM11.0-changes
    • 2013-12-01:
      • Re-enable building TI WPAN support (fixes bluetooth)
    • 2013-11-30:
      • Just a build with the latest CM11.0-changes
    • 2013-11-28:
      • Revert "Reset MDM6600 on bootup", this should be safe to flash again for users having a SIM-PIN
    • 2013-11-27: *DO NOT FLASH*
      • Respect "usevoicetechfordata" RIL-setting again
      • Reset MDM6600 on bootup, this leads to problems with SIM-PINs, do not flash!
    • 2013-11-26:
      • Merge upstream fixes
      • Enable new boot-animation
      • Fix a crash in the hwcomposer
    • 2013-11-24:
      • Disable fsck_msdos for now to see if this solves the sd-card-problems
    • 2013-11-23-2:
      • Revert sd-card changes, sd-cards are now writeable again
    • 2013-11-23:
      • Some more sd-card related changes, this now breaks sd-cards completely...
      • Unconditionally enable gsm-preferences
      • Revert new boot-animation, as it crashes the system on boot
      • Merge upstream kernel/motorola/omap4-common-commits by dhacker29
    • 2013-11-22:
      • Merge upstream devices/motorola/omap4-common-commits by dhacker29
    • 2013-11-21:
      • Fix black-boxes in chromium webview (using this patch)
    • 2013-11-19:
      • Use CPU-path for taking screenshots (Fixes graphical glitches on rotation, and probably hangs, but not black-boxes, they are a PowerVR/chromium bug)
      • Fixed internal and external sd-card mounting
    • 2013-11-18-2:
      • Enable (empty) methods used by audio-blob (fixes audio)
    • 2013-11-18:
      • Don't use TI wpa_supplicant but stock Android one (fixes WiFi)
    • 2013-11-17:
      • First booting build

    What's working:
    • Phone (tested on Verizon and on GSM/UMTS in Europe)
    • Mobile Data (tested on Verizon and on GSM/UMTS in Europe)
    • WiFi
    • WiFi-tethering
    • GPS
    • 3G and 1X mobile data (on Verizon)
    • Camera
    • HDMI, thanks to @lucize

    What's not working:
    Probably most everything else, including, but not limited to:
    • sd-card-location can not be swapped between internal and external sd-card
    • ART, as it is still in heavy development upstream (same as for all other 4.4-Roms)

    Differences to official builds:
    • USB-Host changes trying to fix suspend_backoff issues (integrated into CM)
    • Many power-saving related kernel-changes (integrated into CM as of 2014-01-18)
    • Updated display controller-driver to fix dead display on wakeup (integrated into CM as of 2014-01-20)
    • HD video recording, newer camera libraries (integrated into CM as of 2014-01-14)
    • Camera sensor DCC file-loading fixed (integrated into CM)
    • Working WiFi tethering (integrated into CM as of 2014-01-17)
    • Installable with older recoveries
    • Some other small omap4-common changes (integrated into CM)

    Gapps:
    There are currently multiple Gapps-versions floating around, which might or might not work.
    To install current Gapps-packages without errors, you should upgrade to SafeStrap 3.75.

    BasketBuild: https://basketbuild.com/gapps

    CM: http://wiki.cyanogenmod.org/w/Google_Apps

    Dhacker29 provides gapps which are compatible with recoveries not supporting set_metadata (like SafeStrap <= 3.73) (mirror):
    http://droid.cs.fau.de/cm-11.0/dhacker-gapps/

    Other gapps-versions from Dhacker29 (using set_metadata, which leads to an error during installation):
    http://d-h.st/EIM
    http://d-h.st/F0D

    Installation:

    GSM users:
    To use this CM11.0-ROM on GSM-networks you should install Mentor.37's GSM patch

    Source / Repositories:

    These builds are currently just test-builds, I don't know if I will find the time to continue maintaining device support for the Droid 4 on CM11.

    XDA:DevDB Information
    CM 11.0 on Motorola Droid4, ROM for the Motorola Droid 4

    Contributors
    stargo, Hashcode, Dhacker29
    Source Code: https://github.com/CyanogenMod

    ROM OS Version: 4.4.x KitKat
    ROM Kernel: Linux 3.0.x
    Based On: CyanogenMod

    Version Information
    Status: Stable
    Current Stable Version: XNG3C
    Stable Release Date: 2015-09-01
    Current Beta Version: 2016-01-04
    Beta Release Date: 2016-01-04

    Created 2014-11-23
    Last Updated 2016-01-04
    15
    Congrats to Stargo on being added as an official CM Motorola OMAP4 device maintainer!

    Thanks to you for all your help :)

    I'll try to fix the bugs and will keep maintaining the OMAPs :)

    This also means that I will shortly stop building my unofficial images, when I have merged all useful changes back into the CM repositories. The officials will then have all my fixes.

    Cheers,
    Michael
    7
    Hi,

    I've just updated the first post, added a small changelog for the new build and fixed gapps-links.
    There will be another build including this shortly.

    Cheers,
    Michael
    7
    I apologize for this non-ROM related post:

    Congrats to Stargo on being added as an official CM Motorola OMAP4 device maintainer!

    (probably long over due)

    Please refrain from posting "congrats" messages in this thread and maybe find one of his messages to add a "thanks" to.

    Sent from my XT1060 using Tapatalk
    7
    Nice job man!

    I was hoping devs would step in and continue on with these great devices. You don't know how happy I was to see this build.

    (I'm not just tossing this out there, I actually flashed this build and ran through it.)