android 4.4 kitkat
July 3, 2018

Android 4.4 KitKat (API 19)

Android 4.4 KitKat was released on September 3, 2013. It appeared on Google’s Nexus 5 on October 31, 2013, and was streamlined to keep running on a more noteworthy scope of gadgets than prior Android forms, having 512 MB of RAM as a suggested least; those enhancements were known as “Task Svelte” inside at Google. On June 24, 2014, a version of Android KitKat elite to Android Wear gadgets was released.

The required least measure of RAM accessible to Android is 340 MB, and all gadgets with under 512 MB of RAM must report themselves as “low RAM” gadgets. KitKat propelled with another Nexus gadget, the Nexus 5. The new lead had the greatest display yet: a five-inch, 1920×1080 LCD. Regardless of the greater screen measure, LG—again the producer for the gadget—could fit the Nexus 5 into an indistinguishable measurements from a Galaxy Nexus or Nexus 4.

android 4.4

The Nexus 5 was specced similarly to the most elevated end phone at the time, with a 2.3Ghz Snapdragon 800 processor and 2GB of RAM. The phone was again sold opened on the Play Store, however while most phones with specs like this would go for $600-$700, Google sold the Nexus 5 for just $350.

A standout amongst the most critical upgrades in KitKat was one you couldn’t see: fundamentally bring down memory utilization. For KitKat, Google began a purposeful push to bring down memory utilization over the OS and packaged applications called “Undertaking Svelte.” After huge amounts of enhancement work and a “low memory” mode that debilitated costly graphical impacts, Android could now keep running on as meager as 340MB of RAM. Lower memory prerequisites were a major ordeal, since gadgets in the creating scene—the greatest development markets for cell phones—frequently kept running on just 512MB of RAM.

layout 4.4

KitKat not just disposed of the disagreeable lines to one side and right sides of the bolt screen—it totally handicapped bolt screen gadgets of course! Google clearly felt various lock screens and different home screens were a little to confused for new clients, so bolt screen gadgets currently should have been empowered in the settings. The unbalanced time here and in the clock application was changed to a symmetrical weight, which looked a ton more pleasant.

In KitKat, applications had the capacity to make the framework and status bars directly , which fundamentally changed the look of the OS. The bars presently mixed into the backdrop and whatever other application that empowered direct bars. The bars could likewise be totally covered up by any application by means of another component called “immersive” mode.

dialer 4.4

Google totally redid the dialer in KitKat, making a wild new plan that changed the way clients pondered a telephone. Real numbers in the new dialer were covered up however much as could reasonably be expected—there wasn’t even a dial cushion on the fundamental screen. The essential interface for influencing a telephone to call was currently an inquiry bar! In the event that you needed to call somebody in your contacts, simply type their name in; in the event that you needed to call a business, simply type the business name in and the dialer would seek through Google Maps’ broad database of phone numbers. It worked unfathomably well and was something no one but Google could pull off.

If hunting down numbers wasn’t your thing, the application additionally astutely showed a posting for the past phone call, your most-reached individuals, and a connection to all contacts. At the base were connections to your call history, the now old school number pad, and the standard flood button containing a settings page.

google drive 4.4

Google+ Photos and the Gallery at first transported together on the Nexus 5, however in a later form of KitKat on Google Play gadgets, the Gallery was hacked out and Google+ totally assumed control photograph obligations. The new application changed the photograph application from a light topic to a dull topic, and Google+ Photos brought an advanced route cabinet outline.

google now

Android Wear smartwatches were generally warning machines. With new APIs incorporated with Android 4.3 and up, any notice your telephone got would likewise be appeared on the watch—no application bolster required. The warning activity button were delivered to the look too, giving users a little method to collaborate with notices from the watch. Rejecting a notice on the watch would clear it from the phone, enabling users to oversee notices without whipping out another gadget. There was likewise a voice charge framework and a receiver incorporated into each watch, enabling users to simply lift their wrist to wake the watch, say “OK Google,” and after that issue an order. You could answer by-voice to messages, as well. There was even an application cabinet for local watch applications.

Android 4.4 KitKat (API 19) includes following features:

  • Revived interface with white components rather than blue
  • Clock never again demonstrates strong hours; all digits are thin. The H, M, and S markings for the stopwatch and clock have been evacuated, leaving only the numbers.
  • Capacity for applications to trigger translucency in the route and status bars
  • Capacity for applications to utilize “immersive mode” to keep the route and status bars covered up while keeping up client interaction
  • Action overflow menu buttons are constantly unmistakable, even on gadgets with a “Menu” key, which was formally belittled by Android 4.0.
  • Restriction for applications while getting to outer capacity, with the exception of their own catalogs
  • Advancements for execution on gadgets with bring down particulars, including zRAM support and “low RAM” gadget API
  • Remote printing capability
  • NFC have card imitating, empowering a gadget to supplant shrewd cards
  • WebViews currently in light of Chromium motor (highlight equality with Chrome for Android 30)
  • Extended usefulness for warning audience services
  • Open API for creating and overseeing content informing clients
  • Capacity Access Framework, an API enabling applications to recover records in a reliable way. As a feature of the structure, another framework document picker enables clients to get to records from different sources (counting those uncovered by applications, for example, online capacity services).
    New structure for UI changes
  • Sensor bunching, step identifier and counter APIs
  • Settings application presently makes it conceivable to choose default content informing and home (launcher) application
  • Sound burrowing, sound observing and commotion enhancer
  • Worked in screen recording highlight (essentially for designers, as use of ADB is required)
  • Local infrared blaster API
  • Confirmed boot
  • Upholding SELinux
  • Extended openness APIs and framework level shut inscribing settings
  • Android Runtime (ART) presented as another exploratory application runtime condition, not empowered of course, as a swap for the Dalvik virtual machine
  • Bluetooth Message Access Profile (MAP) support
  • Incapacitated access to battery measurements by outsider applications
  • Settings application never again utilizes a multi-sheet format on gadgets with bigger screens
  • Wi-Fi and versatile information action (TX/RX) markers are moved to fast settings
  • Cripples content enveloping by the WebView program component
  • Revived interface with white components rather than blue
  • Clock never again demonstrates striking hours; all digits are thin. The H, M, and S markings for the stopwatch and clock have been expelled, leaving only the numbers.
  • Capacity for applications to trigger translucency in the route and status bars
  • Capacity for applications to utilize “immersive mode” to keep the route and status bars covered up while keeping up client interaction
  • Activity flood menu catches are constantly noticeable, even on gadgets with a “Menu” key, which was formally deplored by Android 4.0.
  • Limitation for applications while getting to outside capacity, with the exception of their own catalogs
  • Enhancements for execution on gadgets with bring down details, including zRAM support and “low RAM” gadget API
  • Remote printing capability
    NFC have card copying, empowering a gadget to supplant brilliant cards
    WebViews presently in view of Chromium motor (include equality with Chrome for Android 30)
  • Extended usefulness for notice audience services
  • Open API for creating and overseeing content informing clients
  • Capacity Access Framework, an API enabling applications to recover documents in a predictable way. As a component of the structure, another framework document picker enables clients to get to records from different sources (counting those uncovered by applications, for example, online capacity services).
  • New structure for UI advances
  • Sensor clustering, step identifier and counter APIs
    Settings application presently makes it conceivable to choose default content informing and home (launcher) application
  • Sound burrowing, sound observing and clamor enhancer
  • Worked in screen recording highlight (principally for designers, as utilization of ADB is required)
  • Local infrared blaster API
  • Confirmed boot
  • Upholding SELinux
  • Extended openness APIs and framework level shut subtitling settings
  • Android Runtime (ART) presented as another test application runtime condition, not empowered of course, as a swap for the Dalvik virtual machine
  • Bluetooth Message Access Profile (MAP) support
  • Incapacitated access to battery insights by outsider applications
  • Settings application never again utilizes a multi-sheet format on gadgets with bigger screens
  • Wi-Fi and portable information action (TX/RX) markers are moved to speedy settings
  • Handicaps content enclosing by the WebView program component
  • Facilitate security upgrades and bugfixes
  • Evacuation of the “Application Ops” application authorizations control framework, presented in Android 4.3
  • Revived Dialer application interface
  • Refreshed the Chromium-based WebView to rendition 33 (screencasting to DevTools, HTML5 Canvas equipment speeding up execution upgrades, vibration API, HTML5 shape approval, HTML5 datalist)
  • Random enhancements and bugfixes
  • CVE-2014-0224 settled, wiping out an OpenSSL man-in-the-center vulnerability