More Reading

Post navigation

65 Comments

  • This is awful. Just continues the trend to the plain (as in plain boring) design.

  • Well I sure hope there is more to 4.4.3 than this, in my opinion, useless change (a few better dialers on the Play Store).

  • The new dialer seems impressive. Well, I still not updated my Nexus 5 with this much awaited 4.4.3 KitKat version. I am facing quick battery drainage problem from
    last 4 months due to camera bug. Once I fully charged my device on qi charger, I will definitely update this version in order to get rid of this issue.

  • can we do caller ID by google on non-nexus 5s with this? I guess there’s no way you would know, but wondering if theres rumors about that.

  • Deschutes makes some super tasty beers!
    I digg the search for epic brew!
    Oh, and the new dialer.

  • I wish they would bring back the swipe gesture to switch between contacts, dialer and history.

  • Would it be available for 4.4.2 kit Kat in the devices like moto g !!!!

  • i like the colour scheme of the dialer now, dont like the white. much rather have the black

    • Very interested to see how long Moto takes with this update. It’s one thing to get a couple quick updates out and impress some people, but to do it consistently for every update, now that’s really impressive.

      • yeah we shall see. I’d be surprised actually despite what happened the past couple updates.

        • I’d be surprised as well. The Moto X is pretty far into its life cycle and Motorola is probably hard at work on the X+1. I doubt they’ll give the X as much attention when no one’s watching as they did right after it was released.

          But like I said, if they do, then I’ll be really impressed.

      • I’m not counting on it. They took a while for 4.4.2, or at least the Verizon variant did. I’m wondering if they’ll get the Google Dialer as well, considering it wasn’t included in 4.4 initially.

          • No offense taken. You’re right, I just can’t remember if it took a while for other carriers to jump on it for the Moto X or not.

  • This helped take some of the sting out of the Blackhawks losing last night 🙂

  • This is what I get for not researching the locked bootloader on my VZW Note 3. Touchwiz makes my soft parts twitch. I miss AOSP on my GS3, but can’t have that back because my chick is loving CM11 over her now sold iPhone 5. Meh.

  • This update removes almost all similarity with the Ice Cream Sandwich dialer, which itself was radically different from the Gingerbread dialer. Each evolves in visual polish, yet they maintain (and even improve!) their ease of use.

    Over in Apple-land all they can manage is to back-port Android features and make every single UI element uncomfortably flat. lol

    • Wow I forgot about pre-ICS dialer/UI. Oh the uggliness, Oh the OG Droid..

    • In most ways the ICS dialer was a (good) skin of the GB dialer. Different tabs, but largely the same underpinnings.

      The KK dialer is a completely different beast.

  • Can’t wait for the OTA to flash via TWRP. However, I will miss omnirom until they catch up.

  • If you get rid of the “-w” in the “fastboot -w update image-hammerhead-ktu84m.zip” command in the flash-all.bat file then you will not wipe your phone clean and can update by flashing the recovery image.

    • Whoever made the nakasi script is a sadistic bastard. There is an extra “fastboot erase userdata” at the beginning of the script, in addition to the -w. This was not in the hammerhead script, and I don’t remember it in the nakasi script for other images either. Remember to read the entire script, you guys.

    • On different sites/forums, I’m reading different instructions on how to flash factory image and I’m all confused now. This is my current device status –

      Stock 4.4.2 ROM
      Unlocked, Rooted
      XPosed Framework + Modules
      Franco Kernel latest

      How do I flash the 4.4.3 factory image so that at the end, everything above remains same except I bump up to stock 4.4.3? Please help.

        • Thanks for the link. I had read that one already and found it more confusing than clarifying. The OP made so much effort to make everything clear though. I guess my brain is just overloaded today.

          Are factory image and update zip two different things? IIRC, when I had updated to 4.4.2, the zip was some 40-50 MB and I had just flashed it like any other flashable zip. I might be going crazy, what with both Android and ios worlds throwing party on the same day.

      • Piece of cake! If you have the SDK installed, with ‘this’ update all you need to do is flash the boot and system images. The bootloader did not change, the kernel (boot.img) and the system changed. Been updated for a little bit now. The boot.img and system.img need to be inside the platform-tools folder to make it easier. Boot into the boot loader or plug in your phone to your device, open a command prompt inside the platform-tools folder of the sdk (shift right click). Type adb reboot bootloader hit enter, then, fastboot flash boot boot.img, enter, fastboot flash system system.img, enter, fastboot reboot, but better yet before rebooting unplug your phone and use the volume button and power button to get to your recovery and flash the supersu zip that is in your storage, wipe cache and dalvik. ENJOY!

        • Thanks for the detailed explanation. I now read a post on AP that explains that flashing ota zip would be easier than trying to flash factory image. I will wait for that.

          • That will work! As long as there has not been any changes in the system, otherwise you will get an unexpected contents error or some such thing, even if flashing in recovery. If your stock not rooted then you ‘should’ be okay!

    • Also can extract the individual img files and flash them over the appropriate partitions, making sure to not flash the recovery image.

Comments are closed.

Related Posts

back to top